Sun Java Enterprise System 7 Release Notes

Chapter 2 Product Interoperability in Java ES 7

This chapter provides information about the interoperability of the products in Java ES 7 Base. The term interoperability refers to the ability of two products to operate together without conflict. Examples of interoperability include:

Cohabitation – Two products can be installed and run on the same system, each without interfering with the operation of the other.
Data Sharing – Two products can operate on the same data stores, each without invalidating the changes made by the other and without interfering with the operation of the other.
Dependency – A product that requires another product can use the required product without either product interfering with the other. For example, a particular web application can be deployed to a particular web container, and both the web application and the web container operate normally.

This chapter does not provide information about cohabitation unless the cohabitation of two products is in some way limited or restricted, or it requires special configuration.

This chapter presents two kinds of interoperability information for the products in Java ES 7 Base:

Interoperability Notes shows how the product versions in the Java ES 7 release work with each other.
Product Version Backward Compatibility shows how each product in Java ES 7 works with previous versions of itself and with previous versions of the products it depends on.

Interoperability Notes

Table 2–2 in Interoperability Matrix summarizes the interoperability of the products in Java ES 7. Before using this matrix, it may be useful to refer to Table 2–1 to understand the product abbreviations used.

To use this matrix, locate the row for the product you are interested in, and then read across to see its interoperability with the other products in Java ES 7. A "Yes" indicates that the product is interoperable, "No" indicates that it is not, and a blank indicates that there is no interaction with the product. A number following the "Yes" or "No" indicates that a note regarding interoperability applies, as described in Technology Notes.

Product Abbreviations

To accommodate the large number of products in Java ES 7, Table 2–2 uses the product abbreviations listed in Table 2–1.

Table 2–1 Java ES Component Product Abbreviations


Abbreviation	Product
DSEE	Sun Java System Directory Server Enterprise Edition
ESB	Sun GlassFish Enterprise Service Bus
GFES	Sun GlassFish Enterprise Server
GFWS	Sun GlassFish Web Stack
GFWSS	Sun GlassFish Web Space Server
HADB	Sun GlassFish HADB
IDM	Sun Identity Manager
JCAPS	Sun Java Composite Application Platform Suite (Java CAPS)
MQ	Sun Java System Message Queue
NB	NetBeans
OSSOE	Sun OpenSSO Enterprise
SC	Solaris Cluster including Solaris Cluster Agents and Solaris Cluster Geographic Edition
WPS	Sun Java System Web Proxy Server
WS	Sun Java System Web Server

Refer to Table 1–1 for the latest product version numbers in Java ES 7 Base.

Note that not all of the products listed above are included in the Java ES Base offering, but are instead included in Sun GlassFish Portfolio 2009.12 or other optional Java ES product suites. Information about their interoperability is included here because they have bearing on components in Java ES Base. Refer to Products in GlassFish Portfolio 2009.12 in Sun GlassFish Portfolio Release Notes for the latest products and version in GlassFish Portfolio 2009.12.

Interoperability Matrix

Note that this table presents only interoperability information about pairs of products. It does not present information about general issues the products might have. To form a complete picture of interoperability and feature availability, use this table together with the release notes for the products in which you are interested.

Table 2–2 Interoperability of the Product Versions in Java ES 7


	DSEE 6.3.1	GFES 2.1.1	GFWSS 10.0U6	MQ 4.3	OSSOE 8.0U1P2	SC 3.2 1/09	WPS 4.0.11	WS 7.0U6
DSEE 6.3.1	—	Yes (1)	Yes	Yes	Yes	Yes		No (1)
GFES 2.1.1	Yes (1)	—	Yes	Yes	Yes	Yes	Yes (2)	Yes (2)
GFWSS 10.0U6	Yes	Yes	—		Yes		Yes	No
MQ 4.3	Yes	Yes		—	Yes	Yes		Yes
OSSOE 8.0U1P2	Yes	Yes	Yes	Yes	—		Yes	Yes
SC 3.2 1/09	Yes	Yes		Yes		—	Yes	Yes
WPS 4.0.11		Yes (2)	Yes		Yes	Yes	—	Yes (2)
WS 7.0U6	No (1)	Yes (2)	No	Yes	Yes	Yes	Yes (2)	—
GFWS 1.5	Yes (1)	Yes (2)	Yes	Yes	Yes		Yes (2)	Yes (2)
IDM 8.1	Yes	Yes	Yes	Yes	Yes		Yes	No (3)
JCAPS 6.2	Yes	Yes	Yes	Yes	Yes		Yes	No (3)

Refer to the Technology Notes section, below, for notes corresponding to the parenthetical numerical references in the above table.

Technology Notes

DSEE 6.3.1 and web containers.

The Directory Server Control Center component of Directory Server Enterprise Edition must be deployed to a web container. It supports deployment on GlassFish Enterprise Server and Apache Tomcat (part of GlassFish Web Stack), but does not support deployment on Web Server. Because the other components of Directory Server Enterprise Edition do not interact with web containers, interoperability of them with web containers is not an issue.
Cohabitation of web servers, containers, and proxies.

When installing any two web servers, containers, or proxies on the same system, you must ensure that no port conflicts arise as a result of the two products trying to provide the same listener service on an industry-standard port, such as an HTTP listener service bound to port 80. This potential port conflict arising from cohabitation applies to these products:
- GlassFish Enterprise Server
- Web Proxy Server
- Web Server
- GlassFish Web Stack (several components, including Apache Server and Apache Tomcat)
IDM 8.1 or JCAPS 6.2 and WS 7.0U6.

Neither Identity Manager nor Java CAPS support Web Server as a web container. However, services and administrative interfaces for both products can be available through the reverse proxy plug-in feature of Web Server, provided that the services and administrative interfaces are deployed on a supported web container.

Product Version Backward Compatibility

The following sections provide information about the backward compatibility of each product in Java ES 7, covering both compatibility with previous versions of the product itself and compatibility with previous versions of any products the product requires or depends on to operate.

Solaris Cluster 3.2 1/09 and Solaris Cluster Geographic Edition 3.2 1/09

Solaris Cluster 3.2 1/09 is not compatible with previous versions of Solaris Cluster. All nodes in a cluster must be running the same version of Solaris Cluster.
Solaris Cluster Geographic Edition 3.2 1/09 is not compatible with previous versions of Solaris Cluster Geographic Edition. All nodes in a Solaris cluster must be running the same version of Solaris Cluster Geographic Edition.

Solaris Cluster Product Dependencies

Solaris Cluster does not depend on any other Java ES products.

Solaris Cluster Geographic Product Dependencies

Solaris Cluster Geographic Edition depends on Solaris Cluster.
Solaris Cluster Geographic Edition 3.2 1/09 is supported on the following versions of Solaris Cluster:
- Solaris Cluster 3.2 2/08
- Solaris Cluster 3.2 1/09

Sun GlassFish Enterprise Server 2.1.1

Sun GlassFish Enterprise Server 2.1.1 is binary compatible with Sun Java System Application Server versions 9.1, 8.2, 8.1, 8.0 and 7.x.
Java applications that run on Application Server 9.1 run on GlassFish Enterprise Server 2.1.1. Additionally, Java applications that run on Application Server versions 8.2, 8.1, 8.0 and 7.x also run on GlassFish Enterprise Server 2.1.1, except for certain incompatibilities, which are described in Chapter 1, Enterprise Server Compatibility Issues, in Sun GlassFish Enterprise Server v2.1.1 Upgrade Guide.

Table 2–3 provides compatibility information about the Java ES products on which GlassFish Enterprise Server 2.1.1 depends.

Table 2–3 GlassFish Enterprise Server Product Dependencies


Product	Dependency	Supported Versions
Message Queue	Required Dependency: Provides reliable asynchronous messaging.	Version 4.3 (version 4.4 included in GlassFish Enterprise Server 2.1.1)
Web Server	Optional Dependency: Provides load balancing between instances.	Version 6.1 and newer minor versions that are backward compatible with 6.1; version 7.0 and newer minor versions that are backward compatible with 7.0

Sun GlassFish Web Space Server 10.0 Update 6

Version 10.0 Update 6 is the sixth update of the first release of Sun GlassFish Web Space Server. All Web Space Server Update releases are backward compatible.

Table 2–4 provides compatibility information about the Java ES products on which GlassFish Web Space Server 10.0 Update 6 depends.

Table 2–4 GlassFish Web Space Server Product Dependencies


Product	Dependency	Supported Versions
GlassFish Enterprise Server	Required Dependency: Provides J2EE web container runtime services.	Version 2.1
OpenSSO Enterprise	Optional Dependency: Provides authentication and authorization services.	Version 8.0

Sun Java System Directory Server Enterprise Edition 6.3.1

Directory Server Enterprise Edition 6.3.1 is generally compatible with Directory Server Enterprise Edition versions back to version 6.0, but certain compatibility limitations do exist. For detailed information about compatibility of Directory Server, Directory Proxy Server, Identity Synchronization for Windows, Directory Server Resource Kit, and Directory Editor, see Chapter 1, Compatibility Issues, in Sun Java System Directory Server Enterprise Edition 6.3.1 Release Notes.

For information about compatibility of the plug-in API, see Chapter 2, Changes to the Plug-In API Since Directory Server 5.2, in Sun Java System Directory Server Enterprise Edition 6.3 Developer’s Guide and Chapter 3, Changes to the Plug-In API From Directory Server 4 to Directory Server 5.2, in Sun Java System Directory Server Enterprise Edition 6.3 Developer’s Guide.

Table 2–5 Directory Server Enterprise Edition Product Dependencies


Product	Dependency	Supported Versions
GlassFish Enterprise Server	Optional Dependency: Applies to the Directory Service Control Center (DSCC); to manage DSEE instances using DSCC, DSEE must be deployed to a J2EE web container. Because DSCC supports multiple J2EE web containers, the dependency on GlassFish Enterprise Server specifically is optional.	Version 2.1 or later, Sun Java System Application Server 8.2 or later

Sun Java System Message Queue 4.3

Message Queue 4.3 is generally compatible with Message Queue versions back to version 3.6, but certain compatibility limitations do exist. For detailed information about compatibility in the areas of brokers, clients, administered objects, and the administration tool, see Compatibility Issues in Sun Java System Message Queue 4.3 Installation Guide.

For information about the stability of the public interfaces that Message Queue 4.3 provides, see Appendix B, Stability of Message Queue Interfaces, in Sun Java System Message Queue 4.3 Administration Guide.

Message Queue has no mandatory dependencies on other Java ES products, but it can optionally use several other Java ES products to provide enhanced functionality. Refer to the individual component product documentation for any additional information about Message Queue dependencies.

Table 2–6 Message Queue Product Dependencies


Product	Enhanced Functionality	Supported Versions
Directory Server	To store administered objects and user data in an LDAP directory rather than locally.	Version 6.0 and newer minor versions that are backward compatible with 6.0
GlassFish Enterprise Server	To support HTTP messaging between clients and brokers.	Version 2.1 and any newer versions that are backward compatible with 2.1.
Sun Java System Application Server	To support HTTP messaging between clients and brokers.	Version 9.1 and any newer versions that are backward compatible with 9.1.
Solaris Cluster	To provide high availability support.	Version 3.2 and newer minor versions that are backward compatible with 3.2
Web Server	To support HTTP messaging between clients and brokers.	Version 7.0 Update 3 and newer updates that are backward compatible with 7.0 Update 3

Note –

GlassFish Enterprise Server 2.1.1 ships with Message Queue 4.4. Sun OpenSSO Enterprise 8.0 Update 1 Patch 2 is shipped with Message Queue 4.3 (with Session Failover capabilities).

Sun Java System Web Proxy Server 4.0.11

Web Proxy Server 4.0.11 is backward compatible with Web Proxy Server versions back to 4.0.

Web Proxy Server has no mandatory dependencies on other Java ES products, but it can optionally use Directory Server (in Directory Server Enterprise Edition) to provide LDAP-based authentication. When Directory Server is used, Web Proxy Server 4.0.11 supports Directory Server versions 5.2 and 6.x.

Sun Java System Web Server 7.0 Update 6

Web Server 7.0 Update 6 is backward compatible with Web Server versions back to 7.0.

Web Server has no mandatory dependencies on other Java ES products, but it can optionally use Directory Server (in Directory Server Enterprise Edition) to provide LDAP-based authentication. When Directory Server is used, Web Server 7.0 Update 4 supports Directory Server versions 6.x.

Sun OpenSSO Enterprise 8.0 Update 1 Patch 2

OpenSSO Enterprise 8.0 U1P2 maintains compatibility with versions of its precursor product, Sun Java System Access Manager. More specifically:

OpenSSO Enterprise 8.0U1P2 supports backward compatibility for all Access Manager 7.1 and Access Manager 7 2005Q4 existing features including the full SDK and the client SDK APIs. Backward compatibility is not supported for:
- Access Manager 6 2005Q1 (6.3) and earlier releases.
- Liberty ID-FF schema metadata: Liberty ID-FF profiles do not work unless you upgrade the Access Manager or Federation Manager schema in Directory Server.
OpenSSO Enterprise 8.0U1P2 can coexist with Access Manager 7.1, but only when instances of OpenSSO Enterprise and Access Manager 7.1 access the same Directory Server schema. This coexistence usually occurs when multiple instances of Access Manager 7.1 that access the same Directory Server are being upgraded sequentially. Coexistence is not supported for:
- Access Manager 7 2005Q4
- Access Manager 6 2005Q1 (6.3) and earlier releases
- Federation Manager 7.0

For more information about backward compatibility, see Backward Compatibility with OpenSSO Enterprise 8.0 in Sun OpenSSO Enterprise 8.0 Upgrade Guide.

For more information about coexistence, see Coexistence with OpenSSO Enterprise 8.0 in Sun OpenSSO Enterprise 8.0 Upgrade Guide.

OpenSSO Enterprise has no mandatory dependencies on other Java ES products, but it can use multiple Java ES products to satisfy its required dependency on a web container, and it can use other Java ES products to provide enhanced functionality. Table 2–7 provides information about these optional dependencies for OpenSSO Enterprise 8.0.

Table 2–7 OpenSSO Enterprise Product Dependencies


Product	Dependency	Supported Versions
Directory Server Enterprise Edition	OpenSSO Enterprise can optionally use an LDAP server to store its configuration and user data.	Versions 5.2, 6.0, 6.3, and 6.3.1; note that DSEE 6.2 has been deprecated per Sun Alert.
GlassFish Enterprise Server	OpenSSO Enterprise requires a web container.	Version 2.1; also Sun Java System Application Server versions 9.1 Update 1 and Update 2
Message Queue	OpenSSO Enterprise requires Message Queue if session failover capabilities are enabled.	Version 4.1 and newer minor versions that are backward compatible with 4.1
Web Server	OpenSSO Enterprise requires a web container.	Version 7.0 Update 3 and newer