Fix (APAR):  JR29655

Status:  Fix

Release:  6.1.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  6694

Date: 2008-08-13

Abstract:  Incorrect setting of databaseName for BusinessSpace datasource when Monitor or Publishing Server installed because of different naming convention.

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

ERROR DESCRIPTION:?                                             
DB2 on zOS will not work for BSpace after profile creation is   
done. The variable used for defining the 'databaseName' is      
different for WebSphere Process Server and Monitor and the code 
needs to handle both sets of parameters.                        

LOCAL FIX:?                                                     
Set the databaseName manually after the profile creation is done
and before the BSpace is accessed                               

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server v6.1.2 users

PROBLEM DESCRIPTION:
Incorrect setting of databaseName for
BusinessSpace datasource when Monitor
or Publishing Server installed
because of different naming convention.

RECOMMENDATION:
None

Upon accessing BusinessSpace, I received the following error:
500: CWMDS6560E: Unexpected system error. Possible causes
include a SQL exception, database error, incorrect or
insufficient credentials to connect to the  database.

PROBLEM CONCLUSION:?                                            
The corrected value is set at BusinessSpace datasource for      
connectivity during runtime.                                    


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: