Fix (APAR):  JR28266

Status:  Fix

Release:  6.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  26619

Date: 2008-02-21

Abstract:  If user uses Tivoli Access Manager (TAM) as the user registry to enable global security and also java 2 security, they will run into Java 2 Access denied security exception when em

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

ERROR DESCRIPTION:                                              
event can't be sent if java 2 security is enabled and TAM is    
used.                                                           

LOCAL FIX:                                                      
NONE                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1 Users

PROBLEM DESCRIPTION:
If user uses Tivoli Access Manager
(TAM) as the user registry to enable
global security and also java 2
security, they will run into Java 2
Access denied security exception when
emitting Common Event Infrastructure
(CEI) events. As a result, those CEI
events can't be emitted.

RECOMMENDATION:
None

The problem happens only if TAM is used and Java 2 is enabled.
Before emitting events, CEI component will try to get the
event emitter skeleton by JNDI lookup. The lookup process will
trigger TAM to check current security context and then Java 2
security will be triggered to check whether those classes on
the calling stack have the right permission to execute
protected actions.

PROBLEM CONCLUSION:                                             
Since Business Process Execution code is generated during       
servicedeploy time, there is no need to know which Java 2       
security permission it should have. So monitoring component     
need not do the security check.                                 


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: