The Simulated Scalable Environment fails to deploy for WebSphere Process Server (WPS) 7.0.0 Fix Pack 2 (7.0.0.2)

Technote (troubleshooting)


Problem(Abstract)

When you use the default cell name and node name, the Simulated Scalable Environment Pattern fails to deploy for WebSphere Process Server Version 7.0.0 Fix Pack 2.

Symptom

In the /opt/IBM/AE/AR/ConfigWPS.out file, you can see the following errors:

WASX7023E: Error creating "SOAP" connection to host "hostname.ibm.com"; exception information: com.ibm.websphere.management.exception.
ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:
Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException:
com.ibm.jsse2.util.g: PKIX path validation failed: java.security.cert.
CertPathValidatorException: The certificate expired at Wed May 11 18:58:
48 EDT 2011; internal cause is:
java.security.cert.CertificateExpiredException: NotAfter: Wed May 11
18:58:48 EDT 2011; targetException=java.lang.IllegalArgumentException:
Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.
jsse2.util.g: PKIX path validation failed: java.security.cert.
CertPathValidatorException: The certificate expired at Wed May 11 18:58:
48 EDT 2011; internal cause is:
java.security.cert.CertificateExpiredException: NotAfter: Wed May 11
18:58:48 EDT 2011]

Cause

The Hypervisior Edition has some pre-configured profiles that were created with the virtual images at the product release time. For every pre-configured profile, the default expiration period for the default personal certificate is one year. The profiles encounter the certificate expiration problem and need to be refreshed.

Resolving the problem

These pre-configured profiles are used when you keep the default cell name and node names during the pattern deployment. You can specify new cell name and node names when you deploy these patterns. If you use new values in the profiles instead of the values in the pre-configured profile, you will not see the issue. However, you might see a 30% to 50% increase in deployment time due to the profile creation process.

If you still want to use the pre-configured profiles with the default cell and node names to reduce the profile creation time, you might need to extend a virtual image using the WebSphere CloudBurst Appliance. Extending a virtual image is the process of starting with a copy of an existing virtual image, making modifications to that image, and then storing that the modified image as a new virtual image in the catalog.

See the Extending virtual images topic in the WebSphere CloudBurst Appliance information center to extend the virtual image.

In the step 6 of the previous link, you need to login to the virtual system and replace the old activation scripts with the scripts in the /opt/IBM/AE/AS/ directory. To avoid a file permission issue, run the following command with root user for these script files:

chmod 777 scriptName

The new scripts will refresh the expired keys during the next activation time. After the replacement done, you need capture the virtual system and create a new virtual image based on the deployed virtual system that you modified. Then, you can use the new virtual image to deploy different patterns.

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Process Server Hypervisor Edition
General

Software version:

7.0

Operating system(s):

AIX, Linux, Linux on System z

Reference #:

1504163

Modified date:

2012-12-03

Translate my page

Machine Translation

Content navigation