Interoperating multiple application server versions

WebSphere® Application Server Version 8.0 is interoperable with other versions of the product under certain conditions.

Before you begin

Supported configurations Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

sptcfg

Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

WebSphere Application Server Version 8.0 is generally interoperable with Version 6.x and 7.0. You should apply the latest fix level to support interoperability. In order to interoperate between WebSphere Application Server for z/OS® and a WebSphere Application Server product on a non-z/OS machine, however, you must follow this procedure.

You can upgrade a portion of the nodes in a cell to WebSphere Application Server Version 8.0 while leaving others at the older release level. This means that, for a period of time, you might be administering servers that are at the current release and servers that are running the newer release in the same cell.
Restrictions on using mixed-release cells:
  • A mixed-release environment where some members are at an older release level might have some restrictions. For details, read the "Creating application servers" article in the information center.
  • A WebSphere Application Server, Network Deployment cell can contain mixed releases of Version 6.x nodes, but there is no mixed-node management support for Version 6.0.1.x.
    The Version 8.0 migration tools still migrate these nodes during deployment-manager migration, but they issue a warning message that the nodes cannot be managed by the Version 8.0 deployment manager. You can then do one of the following based on your needs:
    • Upgrade all Version 6.0.1.x nodes to at least Version 6.0.2. This will allow them to be administered by a Version 8.0 deployment manager.
    • Migrate these nodes to Version 8.0.

Procedure

  1. On the non-z/OS machine, the property -Dcom.ibm.CORBA.ORBCharEncoding=ASCII should be set in the administrative console under server_name > Java and Process Management >Process Definition > Java Virtual Machine > Generic JVM arguments.
  2. On the non-z/OS machine, the property com.ibm.CORBA.ORBWCharDefault = UCS2 should be defined in the administrative console under server_name > Container Services > ORB Service > Custom Properties.
  3. If you are running WebSphere Application Server for z/OS with security enabled, you must set the property com.ibm.CORBA.validateBasicAuth=false in sas.client.props on the non-z/OS machine. It is set to true by default.
  4. Upgrade the Software Development Kit (SDK) used to one supported by Version 8.0.

    Read Recommended fixes for WebSphere Application Server for more information.

What to do next

This information is dynamic and might be augmented by information in technical articles that are available on the IBM® DeveloperWorks WebSphere site. Check the site for the latest information.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 20, 2011 12:50:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=tmig_interop
File name: tmig_interop.html