Oracle TopLink Developer's Guide
10g Release 3 (10.1.3) B13593-01 |
|
![]() Previous |
![]() Next |
To integrate a TopLink application with IBM WebSphere Application Server, you must consider the following:
In addition to configuring these IBM WebSphere application server-specific options, you must also consider the general application server integration issues in "Application Server Integration Concepts".
You configure the IBM WebSphere application server classpath differently depending on what version of this server you are using:
Configuring Classpath for IBM WebSphere Application Server 4.0
Configuring Classpath for IBM WebSphere Application Server 5.0 and Later
TopLink provides CMP support for IBM WebSphere application server 4.0. To configure the classpath for this version, do the following:
Add the following JAR files to the application server classpath directory (see Table 7-9):
<ORACLE_HOME>\toplink\jlib\toplink.jar
Ensure that your TopLink application defines an XML parser platform (see "XML Parser Platform Configuration").
Table 7-9 lists the default application classpath directories for IBM container components in IBM WebSphere application server 4.0.
Table 7-9 Classpath Directories for IBM WebSphere 4.0 Container Components
Container | Default Application Classpath |
---|---|
WebSphere Application Server 4.0 (for Windows) |
|
WebSphere Studio Application Developer 4.0 (for Windows) |
|
TopLink provides JTA and general integration support for IBM WebSphere application server 5.0 and later. To configure the classpath for this version, do the following:
Create a shared library that contains the following Toplink JAR files and associate the shared library with the application:
<ORACLE_HOME>\toplink\jlib\toplink.jar
Ensure that your TopLink application defines an XML parser platform (see "XML Parser Platform Configuration").
To enable TopLink CMP integration in IBM WebSphere application server, use the following procedure. This procedure assumes you have already installed TopLink.
Ensure that all necessary deployment descriptor files are in place (see "Creating TopLink Files for Deployment" and "Packaging a TopLink Application").
Optionally, consider the EJB customization options that TopLink provides ("Configuring Miscellaneous EJB Options").
For applications that require JTA integration, specify the external transaction controller when you configure the server platform in your session (see "Configuring the Server Platform").
For more information, see "Integrating the Unit of Work With an External Transaction Service".
For more information on integrating a TopLink application with an application server cluster, see "Clustering".