Container interoperability describes the ability of WebSphere Application Server clients and servers at different versions to successfully negotiate differences in native Enterprise JavaBeans (EJB) finder methods support and Java 2 Platform, Enterprise Edition (J2EE) compliance.
The product uses interoperable versions of some class types to enable interoperability. However, older 4.0.x client and application server versions do not support the interoperability classes, which makes them uninteroperable with versions that use the classes. The system property com.ibm.websphere.container.portable remedies this situation by enabling newer versions of the application server to turn off the interoperability classes. This lets a more recent application server return class types that are interoperable with an older client. Depending on the value of com.ibm.websphere.container.portable, application servers at versions 5 and later, and 4.0.3 and later, return different classes for the following:
If the property is set to false, application servers return the old class types, to enable interoperability with 4.0.2 and earlier. If the property is set to true, application servers return the new classes.
The following tables show interoperability characteristics for various version combinations of application servers and clients as well as default property values for each combination.
Interoperability of Version 4.0.x client with Version 5 (and later) application server
Ideally, all 4.0.x clients that use Version 5 or later application servers should be at Version 4.0.3 or later.
Version 5 and later application servers return the interoperability class types by default (true). This can cause interoperability problems for distributed clients at versions 4.0.1 or 4.0.2. In particular, problems can occur with collections and enumerations returned by Enterprise JavaBeans Version 1.1 finder methods. Although it is strongly discouraged, you can set com.ibm.websphere.container.portable to false on a Version 5 and later application server. This causes the application server to return the old class types, providing interoperability with clients at Version 4.0.2 and earlier. This is discouraged because:
If you would like to use updated Handle classes in EJB 2.x-compliant beans but have one of the older clients (versions 4.0.2 and earlier) installed, set the system property com.ibm.websphere.container.portable.finder to false . With this setting in place, the Version 5 and later application server uses the updated handles but returns the enumerations and collections that were used in the earlier clients.
Interoperability of client at Version 4.0.2 and earlier with Version 5 (and later) application server
| Client at Version 4.0.2 and earlier, using this function | Application server at Version 5 and later, property true (default) | Application server at Version 5 and later, property false |
|---|---|---|
| EJBMetaData | Does not work | Works for 4.0.2 client |
| Handle to session bean | Does not work | Works |
| Handle to entity bean | Does not work | Does not work across cells |
| Enumeration returned by EJB 1.x finder method | Does not work | Works |
| Collection returned by EJB 1.x finder method | Does not work | Works |
| Handle to home interface | Does not work | Does not work across cells |
If you would like to use updated Handle classes in EJB 2.x-compliant beans but have one of the older clients (versions 4.0.2 and earlier) installed, set the system property com.ibm.websphere.container.portable.finder to false. With this setting in place, the Version 5 and later server uses the new Handle classes but returns the older enumeration and collection classes.
Interoperability of client at Version 4.0.3 and later with Version 5 and later application server
Clients at Version 4.0.3 and later work well with Version 5 and later application servers. However, if you set the com.ibm.websphere.container.portable to false, client handles to entity beans and home interfaces do not work across domains for the server you set to false.
| Client at Version 4.0.3 and later, using this function | Application server at Version 5 and later, property true (default) | Application server at Version 5 and later, property false |
|---|---|---|
| EJBMetaData | Works | Works |
| Handle to session bean | Works | Works |
| Handle to entity bean | Works | Does not work across cells |
| Enumeration returned by EJB 1.x finder method | Works | Works |
| Collection returned by EJB 1.x finder method | Works | Works |
| Handle to home interface | Works | Does not work across cells |
Interoperability of Version 5 and later client with Version 4.0.x application server
Clients at Version 5 and later work well with Version 4.0.3 application servers if you set com.ibm.websphere.container.portable to true. Client handles to entity beans and home interfaces do not work across domains for any Version 4.0.3 server with com.ibm.websphere.container.portable at the default value, false. Version 5 client handles to application servers at Version 4.0.2 and earlier also have restrictions.
| Client at Version 5 and later, using this function | Application server at Version 4.0.3, property true | Application server at Version 4.0.3, property false (default) | Application server at Version 4.0.2 or earlier |
|---|---|---|---|
| EJBMetaData | Works | Works | Works for 4.0.2 server only |
| Handle to session bean | Works | Works | Works |
| Handle to entity bean | Works | Does not work across domains | Does not work across domains |
| Enumeration returned by EJB 1.x finder method | Works | Works | Works |
| Collection returned by EJB 1.x finder method | Works | Works | Works |
| Handle to home interface | Works | Does not work across domains | Does not work across domains |
Interoperability of zSeries Version 4.0.x client with Version 5 and later application server
The only valid configuration for container interoperability with zSeries Version 4.0.x clients is the default configuration for the Version 5 application server.
Interoperability of Version 5 and later client with zSeries Version 4.0.x application server
Version 5 clients should work with a zSeries Version 4.0.x application server with the correct interoperability fixes described in the zSeries documentation. The interoperability characteristics should be the same as for a Version 4.0.3 distributed application server with the property set to true.
| Client at Version 5 and later, using this function | zSeries application server at Version 4.0.x |
|---|---|
| EJBMetaData | Works |
| Handle to session bean | Works |
| Handle to entity bean | Works |
| Enumeration returned by EJB 1.x finder method | Works |
| Collection returned by EJB 1.x finder method | Works |
| Handle to home interface | Works |
Interoperability of the handle formats in WebSphere Application Server, Version 5 and Version 5.0.1
Applications that attempt to persist handles to enterprise beans and EJBHome needed to subclass ObjectInputStream in WebSphere Application Server, Version 5. This action was required so that the subclass ObjectInputStream could utilize the context class loader to resolve the classes for enterprise beans and EJBHome stubs.
In addition, handles created and persisted in WebSphere Application Server, Version 5 only work with objects that have an unchanged remote interface. If the remote interface is changed, the handle is no longer valid because the stub is serialized inside the handle and its serial Version UID changes if the remote interface changes.
This release introduces a new handle persistence mechanism that avoids the implementation drawbacks of the previous version. However, if handles are used for this WebSphere Application Server deployment, you should consider the following issues when applying this update, future WebSphere Application Server Fix Packs and EJB Container cumulative fixes for WebSphere Application Server, Version 5.
If a WebSphere Application Server, Version 5 persisted handle or home handle is encountered by a WebSphere Application Server, Version 5.0.1 system, it can be read and utilized. In addition, it will be converted to WebSphere Application Server, Version 5.0.1 format if it is re-persisted. The WebSphere Application Server, Version 5.0.1 format cannot be read by a WebSphere Application Server, Version 5 system unless PQ72184 is applied.
Problems arise when handles are persisted and shared across systems that are not at the WebSphere Application Server, Version 5.0.1 level or later. However, a Version 5 system can receive a handle from Version 5.0.1 remotely through a call to get a handle on an enterprise bean or a getHomeHandle on an EJBHome . The remote call will succeed, however, any attempt to persist it on the Version 5 system will have the same limitations regarding the use of ObjectInputStream and changes in remote interface invalidating the persisted handle.
When your application stores handles persistently and shares this persistence with multiple clients or application servers, apply WebSphere Application Server, Version 5.0.1 or PQ72184 to both the client and server systems at the same time. Failure to do so can result in the inability of these systems to read the handle data stored by upgraded systems. Also, handles stored by the WebSphere Application Server, Version 5 can force the applications of the updated system to still subclass ObjectInputStream . Applications using the WebSphere Application Server Enterprise, Version 5 scheduler and process choreographer, are affected by these changes. These users should update their Version 5 systems at the same time with either Version 5.0.1 or PQ72184.
If the
applications store handles in the session context, or locally in a file on the same system, that is not shared by other applications, on different systems,
they might be able to update their systems individually, rather than all at once. If Client Container and thin client applications do not share persisted handle data, they can be updated as needed as well. However, handles created and persisted in WebSphere Application Server, Version 5, Version 4.0.3 and later (with the property flag set), or Version 3.5.7 and later (with the property flag set) are not usable if either the home or the remote interface changes.
If any WebSphere Application Server, Version 3.5.7 or Version 4.0.3 and later enables the system property com.ibm.websphere.container.portable to true , any handles to objects on that server have the same interoperability limitations. In addition, if any WebSphere Application Server, Version 3.5.7 and later or Version 4.0.3 applications store a handle obtained from a WebSphere Application Server, Version 5 or Version 5.0.1, the same restrictions apply, regarding the need to subclass ObjectInputStream and the usability of handles after a change to the remote interface is made.
Replication of the Http Session and Handles
This note applies to you if you place Handles to Homes or Enterprise JavaBeans, or EJB or EJBHome references in the Http Session in your application and you use Http Session Replication. If you intend to replicate a mixed environment of Version 5.0.0 and Version 5.0.1 or 5.0.2 machines you should first apply the latest Version 5.0.0 container cumulative e-fix to the Version 5.0.0 machines before allowing the Version 5.0.1 or 5.0.2 server into the typology. The reason for this is that Version 5.0.0 servers are not able to understand the persisted Handle format used on the Version 5.0.1 and 5.0.2 server. This is similar to the case of Version 5.0.0 and Version 5.0.1 or 5.0.2 systems trying to use a shared database, mentioned above. But in this case, it is the Http Session object and not the database providing the persistence.
Top Down Deployment Mapping
The size of the Handle objects has grown due to the fix put in to allow serialization and deserialization to occur without the previous requirements of subclassing the ObjectInputStream and so on. Top down deployment of an object that contains EJB and EJBHome references create a database table ddl that has a field of 1000 bytes of VARCHAR for BITDATA which will contain the Handle. It might be that your object's Handle does not fit in the 1000
byte default field, and you might need to adjust this to a higher value. You might try increments of 250 bytes, that is, 1250, 1500, and so on.
Related concepts
EJB containers
Related tasks
Managing EJB containers
Related reference
EJB container settings