Interoperating multiple application server versions

WebSphere® Application Server Versão 9.0 is interoperable with other versions of the product under certain conditions.

Before you begin

Configurações suportadas Configurações suportadas:

Este artigo trata da migração da configuração de perfil. Para migrar seus aplicativos para a versão mais recente, use o Kit de Ferramentas de Migração do WebSphere Application Server. Para obter mais informações, consulte o Kit de ferramentas de migração no WASdev.

sptcfg

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

Interoperability applies to WebSphere administrative actions, administrative communication and to application client requests. WebSphere Application Server Versão 9.0 is generally interoperable with Versão 7.0 ou posterior. 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 Versão 9.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. See Creating application servers for more information.

For web application clients, interoperability is provided by employing the HTTP server plug-in at the highest version of all of the application servers in the cell. For example, a cell comprised of WebSphere Application Server Version 9.0 and Version 8.0 application servers would use a supported HTTP server with a Version 9.0 plug-in. See Technote Web server plug-in policy for WebSphere Application Server for more information.

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 Versão 9.0.

    Read Recommended updates 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.


Ícone que indica o tipo de tópico Tópico de Tarefa



Ícone de registro de data e hora Última atualização: June 20, 2016 0:09
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-zos&topic=tmig_interop
Nome do arquivo: tmig_interop.html