Fix (APAR):  JR26596

Status:  Fix

Release:  6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR26596

Byte size of APAR:  78408

Date: 2007-07-06

Abstract:  Mail session is not created in clustered 6.0.2 environment when using htm container installation wizard in the admin console.

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

ERROR DESCRIPTION:                                              
The HTM container installation was done by the HTM container    
installation wizard of the WebSphere Process Server             
administrative console. It created a mail session in the default
mail provider in the cell scope. But the same mail session JNDI 
name could not be seen in the HT runtime page of the            
administrative console.                                         
When a process with e-mail escalation is triggered it will not  
deliver the escalation mails and the logs do not show any       
exception.                                                      
alerts, its not delivering the mails.                           
                                                                
The only warning during server startup is                       
                                                                
CWTKE0012I: HTM mail function will be disabled.                 
                                                                
The same behaviour is not seen in non-clustered environment.    

LOCAL FIX:                                                      
use the bpeconfig.jacl script with the parameter -cluster to    
install the HTM container                                       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2 users

PROBLEM DESCRIPTION:
Mail session is not created in
clustered 6.0.2 environment when using
htm container installation wizard in
the admin console.

RECOMMENDATION:
None

The HTM container installation was done by the HTM container
installation wizard of the WebSphere Process Server
administrative console. It created a mail session in the default
mail provider in the cell scope. But the same mail session JNDI
name could not be seen in the HTM runtime page of the
administrative console.
When a process with e-mail escalation is triggered it will not
deliver the escalation mails and the logs do not show any
exception.

PROBLEM CONCLUSION:                                             
Apply ifix to resolve the stated problem.                       


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.2 is installed on the system.
Also 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) When the pak file is installed, please run /bin/iscdeploy.sh -restore.

5) Restart WebSphere

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. 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

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: