Skip Headers
Oracle® Application Server TopLink Application Developer's Guide
10g Release 2 (10.1.2)
Part No. B15901-01
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

OracleAS TopLink CMP Configuration

OracleAS TopLink provides a CMP integration for:

IBM WebSphere Application Server 4.0

To enable the OracleAS TopLink CMP integration for IBM WebSphere 4.0, configure OracleAS TopLink J2EE support for WebSphere as described in "IBM WebSphere Application Server 4.0".

BEA WebLogic Application Server (6.1, 7.0, and 8.1)

To enable the OracleAS TopLink CMP integration for BEA WebLogic Server 6.1, 7.0 and 8.1, use the following procedures. These procedures assume you have already installed OracleAS TopLink.

To configure OracleAS TopLink support for WebLogic, follow these steps:

  1. Locate the persistence directory, located above the installation drive and root directory of your BEA WebLogic Server executable, as follows:

    Version Persistence Directory (above <WebLogic_INSTALL_DIR>)
    6.1 \wlserver6.1\lib\persistence
    7.0 \weblogic700\server\lib\persistence
    8.1 \weblogic81\server\lib\persistence

    Do one of the following:

    • Use a text editor to open the persistence.install file in the BEA WebLogic Server persistence directory, and add a new line that references TopLink_CMP_Descriptor.xml.

    • Replace the WebLogic persistence.install file with the OracleAS TopLink persistence.install file found in the <ORACLE_HOME>\toplink\config directory.

  2. Add the following JAR files to the application server classpath:

    <ORACLE_HOME>\toplink\jlib\toplink.jar
    <ORACLE_HOME>\lib\xmlparserv2.jar
    

    Note:

    When you add the toplink.jar and xmlparserv2.jar files in the application server classpath, ensure they are placed before the weblogic.jar file.

  3. Start the container, and then start the OracleAS TopLink application. Where supported, use a startup script to start the server. If you write your own startup script, ensure that its classpath includes any files that you added to the application server classpath.