WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Interoperating

WebSphere Application Server Version 6.1 is interoperable with other WebSphere Application Server versions under certain conditions.

Before you begin

See Overview of migration, coexistence, and interoperability and Premigration considerations.

[AIX HP-UX Linux Solaris Windows] WebSphere Application Server Version 6.1 is generally interoperable with WebSphere Application Server Version 5.x and Version 6.0.x. However, there are specific requirements to address for each version. In general, you should apply the latest fix level to support interoperability. If this is not possible, then the following interim fixes can be used to support your environment.

[i5/OS] WebSphere Application Server Version 6.1 is generally interoperable with WebSphere Application Server Version 5.x and Version 6.0.x. However, there are specific requirements to address for each version. In general, you should be at the most recent group PTF level to support interoperability.

[z/OS] WebSphere Application Server Version 6.1 is generally interoperable with WebSphere Application Server Version 5.x and Version 6.0.x. 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 take the following steps:

Procedure

  1. [AIX HP-UX Linux Solaris Windows] Apply required interim fixes.
    Table 1. Interim fixes to apply to Version 5.0.x
    Interim fix Version 5.0 Version 5.0.1 Version 5.0.2
    PQ89426 (which requires PQ88653)     Apply (or move to 5.0.2.8)
    Table 2. Interim fixes to apply to Version 5.1.x
    Interim fix Version 5.1.0 Version 5.1.1
    PQ84384 Apply (or move to 5.1.0.4 or higher)  

    All fixes are available on the Support site for WebSphere Application Server products.

    Interim fixes PQ89426 (Version 5.0.2) and PQ84384 (Version 5.1.0):
    The transaction service is changed so that when a transaction is marked for rollbackOnly in a subordinate server, the superior server will be informed.

    This will allow applications running in the superior server to detect this status change.

  2. [AIX HP-UX Linux Solaris Windows] [i5/OS] Follow the required guidelines for WebSphere Application Server Version 5.x.
    Guideline 1 (for Version 5.0.2 or earlier):
    To send requests from application servers that are WebSphere Application Server Version 5.0.2 or earlier to application servers that are Version 6.0 or later, set the following JVM properties:
    com.ibm.ejs.jts.jts.ControlSet.nativeOnly=false
    com.ibm.ejs.jts.jts.ControlSet.interoperabilityOnly=true
    [AIX HP-UX Linux Solaris Windows] Important: Apply this guideline in addition to applying interim fixes or moving to Version 5.0.2.8.
    [i5/OS] Important: Apply this guideline in addition to moving to Version 5.0.2.8.

    You do not need to set these properties to receive requests on application servers that are WebSphere Application Server Version 5.0.2 or earlier from application servers that are Version 6 or later.

    Guideline 2:
    Be aware of the level of WebSphere Application Server in which each function you use is supported. Applications that you intend to be interoperable must only use function that is supported by all levels of WebSphere Application Server in the cluster. For example, applications that use the commonj.timer.TimerManager resource, which was new in Version 6.0, should not be deployed to a cluster including both Version 5.1 and Version 6.1 servers.
    Guideline 3:
    If you run related cross-domain interoperating applications (one server is in rtp.raleigh.ibm.com and the other is in cn.ibm.com for example), you need to use fully qualified host names (host9.rtp.raleigh.ibm.com instead of just host9 for example) when installing WebSphere Application Server Version 6.1.
    Guideline 4:
    If you want to interoperate WebSphere Application Server Version 6.1 with Version 5.0, you must be at or above the Version 5.0.2.7 level. If you want to interoperate Version 6.1 with Version 5.1, you must be at or above the Version 5.1.1.1 level. Older levels of Version 5.0 and Version 5.1 do not support interoperability with Version 6.1.
  3. [z/OS] 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.
  4. [z/OS] 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.
  5. [z/OS] 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.
  6. Upgrade the Software Development Kit (SDK) used to one supported by Version 6.1.x.

    See Recommended fixes for WebSphere Application Server.

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    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tmig_interop.html