Interoperating with previous product versionsIBM WebSphere Application Server, Version 5 interoperates with the previous product versions (such as Version 4 and Version 3.5). Interoperability is achieved only when the Lightweight Third Party Authentication (LTPA) authentication mechanism and Lightweight Directory Access Protocol (LDAP) user registry are used. Credentials derived from Simple Websphere Authentication Mechanism (SWAM) are not forwardable.
- Enable security with the LTPA authentication mechanism and the LDAP user registry.Verify that the same LDAP user registry is shared by all the product versions.
- Extract and add Version 5 server certificates into the server key ring file of the previous version.
- Open the Version 5 server key ring file using the key management utility (iKeyman) and extract the server certificate to a file.
- Open the server key ring of the previous product version, using the key management utility and add the certificate extracted from product Version 5.
- Extract and add Version 5 trust certificates into the trust key ring file of the previous product version.
- Open the Version 5 trust key ring file using the key management utility and extract the trust certificate to a file.
- Open the trust key ring file of the previous product version using the key management utility and add the certificate extracted from Version 5.
- If single signon (SSO) is enabled, export keys from the Version 5 product and import them into the previous product version. The Version 4 product requires the fix, PQ61779, and the Version 3.5 product requires the fix, PQ59667, for SSO to function.
- Verify that the application uses the correct JNDI name.In Version 5, the enterprise beans are registered with long JNDI names like, (top)/nodes/node/servers/server/HelloHome. Whereas in previous releases, enterprise beans are registered under a root like, (top)/HelloHome. Therefore, EJB applications from previous versions perform a lookup on the Version 5 enterprise beans.
You can also create EJB name bindings in Version 5 that are compatible with the previous version. To create an EJB name binding at the root Version 5, start the administrative console and click Environment > Naming > Naming Space Bindings > New > EJB > Next. Complete all the fields and enter a short name (for example, -HelloHome) as the JNDI Name. Click Next and Finish.
- Stop and restart all the servers.
- Verify that the correct naming bootstrap port is used to perform naming lookup.In previous product versions, the naming bootstrap port is 900. In Version 5, the bootstrap port is 2809.