Fix (APAR):  JR29800

Status:  Fix

Release:  6.1.2,6.1.0.2,6.1.0.1,6.1

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR29800

Byte size of APAR:  29968

Date: 2008-08-11

Abstract:  WebSphere Process Server users when they try to do map Webmdule, Application Module to respective servers in their Network Deployement environment might get failures at the time of

Description/symptom of problem:  
JR29800 resolves the following problem:

ERROR DESCRIPTION:?                                             
Failed to map EJB modules to a web server and a cluster if there
is a web module with the same mapping. Duplicate EJB bindings   
with incorrect values created through offline app installation. 

LOCAL FIX:?                                                     
None                                                            

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server and
WebSphere Enterprice Service Bus
v6.1.0.1 and v6.1.2 users

PROBLEM DESCRIPTION:
WebSphere Process Server users when
they try to do map Webmdule,
Application Module to respective
servers in their Network Deployement
environment might get failures at the
time of the deploymnet.

When a user deploys an application
that contains an EJB module and a web
module in ND environment through
offline installation, SCA will create
duplicate EJB mapping entries with
incorrect data. This later leads to
EJB lookup failure due to the
duplicate EJB binding. Users will see
an UnknownException in the logs as a
result.

RECOMMENDATION:
None

Due to incorrect logic, deploymnet contents are not getting
parsed properly.

PROBLEM CONCLUSION:?                                            
This iFix will address the problems while deploying the         
application which has webmodule and application module in a     
clustered scenario and as well stand alone scenario.            


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: