If you plan to use IBM® Content
Navigator to
access IBM Content
Manager OnDemand repositories,
you must add the IBM Content
Manager OnDemand Web Enablement Kit ODApi.jar file
to the Oracle WebLogic Server startup
script.
Before you begin
You must install Content Manager OnDemand Web Enablement Kit (ODWEK) before you can complete
this task.
Locate the
ODWEK installation
directory. By default,
ODWEK is
installed in the following directory:
Table 1. Default ODWEK installation
directoryOperating system |
Directory |
AIX® |
- Version 9.0: /opt/IBM/odwek/V9.0
- Version 9.5: /opt/IBM/ondemand/V9.5/www
|
Linux |
- Version 9.0: /opt/ibm/odwek/V9.0
- Version 9.5: /opt/ibm/ondemand/V9.5/www
|
Linux for System z® |
- Version 9.0: /opt/ibm/odwek/V9.0/
- Version 9.5: /opt/ibm/ondemand/V9.5/www
|
Windows |
- Version 9.0: C:\Program Files\IBM\OnDemand Web Enablement Kit\V9.0
- Version 9.5: C:\Program Files\IBM\OnDemand\V9.5\www
|
About this task
You must complete this task to
IBM Content
Navigator to access
IBM Content
Manager OnDemand repositories.
Remember: If you deployed
IBM Content
Navigator in a highly available
cluster, you must complete the following steps for each node in the
cluster.
Procedure
To enable IBM Content
Navigator to access IBM Content
Manager OnDemand repositories:
- Open the Oracle WebLogic Server startup
script, startWebLogic.cmd or startWebLogic.sh,
by default, the startup script is in the following directory:
- AIX: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
- Linux: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
- Linux for System z: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
- Windows: C:\Oracle\Middleware\user_projects\domains\domain_name\bin\startWebLogic.cmd
- Add the ODApi.jar file to the startup
script:
- On AIX, add the following lines to the startup script:
ODWEK=/opt/IBM/odwek/V9.0/api/ODApi.jar
LIBPATH=/opt/IBM/odwek/V9.0
CLASSPATH=$ODWEK:$LIBPATH:$CLASSPATH
PATH=/opt/IBM/odwek/V9.0/lib64:/opt/IBM/odwek/V9.0:$PATH
- On Linux, add the following lines to the startup script:
ODWEK=/opt/ibm/odwek/V9.0/api/ODApi.jar
LD_LIBRARY_PATH=/opt/ibm/odwek/V9.0
CLASSPATH=$ODWEK:$LD_LIBRARY_PATH:$CLASSPATH
PATH=/opt/ibm/odwek/V9.0/lib64:/opt/ibm/odwek/V9.0:$PATH
- On Linux for System z, add the following lines to the startup
script:
ODWEK=/opt/ibm/odwek/V9.0/api/ODApi.jar
LD_LIBRARY_PATH=/opt/ibm/odwek/V9.0
CLASSPATH=$ODWEK:$LD_LIBRARY_PATH:$CLASSPATH
PATH=/opt/ibm/odwek/V9.0/lib64:/opt/ibm/odwek/V9.0:$PATH
- On Windows, add the following lines to the startup
script:
set ODWEK=C:\Progra~1\IBM\ONDEMA~1\V9.0\api\ODApi.jar
set CLASSPATH=%ODWEK%;%CLASSPATH%
set PATH=C:\PROGRA~1\IBM\ONDEMA~1\V9.0;C:\PROGRA~1\IBM\ONDEMA~1\V9.0
\lib64;%PATH%
Important: On Windows, do not enter the path with
spaces. For example:
- If the ODApi.jar file is in the C:\Program Files
(x86)\IBM\OnDemand Web Enablement Kit\V9.0\api directory, specify
C:\Progra~2\IBM\OnDema~1\V9.0\api\ODApi.jar
- If the ODApi.jar file is in the C:\Program Files\IBM\OnDemand Web
Enablement Kit\V9.0\api directory, specify
C:\Progra~1\IBM\OnDema~2\V9.0\api\ODApi.jar
- Save your changes to the startup script.
- Restart the application server and verify that the application
server starts without errors.