search cancel

R12 SP2 Application Server Agent for WebSphere (TAI) fails to initialize after Java upgrade on WebSphere.

book

Article ID: 42478

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Issue:

R12 SP2 Application Server Agent (TAI) fails to initialize after Java upgrade on WebSphere.

 

Environment:

R12 SP2 Application Server Agent for WebSphere

 

Cause:

A base install of WebSphere will include a version of java located in the "<WAS_HOME>/java" directory. The R12 SP2 Application Server Agent installs the "sm_cryptoj.jar" file into the "<WAS_HOME>/java/jre/lib/ext" directory to provide the cryptographic extension class files coupled with the Java Cryptography Extensions (JCE) patch for Java required by the Application server Agent for establishing the connection with the Policy Server.

 

When you upgrade Java on the WebSphere Application Server, the existing version of java in the "<WAS_HOME>/java" directory is not upgraded. Instead a new directory structure is created under the "<WAS_HOME>" location for the new version of Java.

 

eg. "<WAS_HOME>/java_1.7.0_59/"

 

The runtime "JAVA HOME" for WebSphere will now use the updated java path, which does not contain the "sm_cryptoj.jar" file resulting in a failure for the Application Server Agent to make the connection to the Policy Server to obtain it's HCO and ACO to initialize.

 

 

Resolution:

If you upgrade the version of Java on your WebSphere Application Server, you need to follow the steps below to ensure the Application Server Agent can create the connection to the Policy Server to allow the Application Server Agent (TAI) to initialize;

 

1.) Patch the new version of Java with the compatible Java Cryptography Extensions (JCE) patch.

2.) Copy the "sm_cryptoj.jar" file located in the "<WAS_HOME>/java/jre/lib/ext" directory into the "/jre/lib/ext" directory of the new runtime version of java.

eg. "<WAS_HOME>/java_1.7.0_59/jre/lib/ext"

3.) If you are upgrading from Java 1.6 to Java 1.7 you will need to re-register the Application Server Agent with the smreghost.bat or smreghost.sh script configured to utilize the new higher version of Java.

Environment

Release:
Component: SMIBW