Content Platform Engine, Version 5.2.1       Application server:  WebLogic Application Server     

Creating a shared library definition for Tivoli Storage Manager native API library files

The shared library definition specifies the location of the Tivoli® Storage Manager JAR file.

Procedure

To create a shared library definition for Tivoli Storage Manager native API library files:

  1. Open in an edit window the WebLogic Server script that sets up the domain environment. The following are example paths to this script:
    Option Description
    AIX®, Solaris, HPUX, HPUXi, Linux, Linux for System z /opt/bea/user_projects/domains/base_domain/bin/setDomainEnv.sh
    Windows C:\bea\user_projects\domains\base_domain\bin\setDomainEnv.cmd
  2. Edit the WebLogic Server script by adding the lines shown below, for your operating system, just before the line in which the WL_HOME variable is set. Substitute your version identifier in place of weblogic92 as appropriate. There is no carriage return after any line that ends with /, \, :, or _.
    Option Description
    AIX
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    LIBPATH=${LIBPATH}:${TSMAPILIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export LIBPATH EXT_POST_CLASSPATH
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    HP-UX (32-bit)
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    SHLIB_PATH=${SHLIB_PATH}:${TSMAPILIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export SHLIB_PATH EXT_POST_CLASSPATH
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    HP-UX (64-bit) and HP-UXi
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    SHLIB_PATH=${SHLIB_PATH}:${TSMAPILIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export SHLIB_PATH EXT_POST_CLASSPATH
    JAVA_OPTIONS="${JAVA_OPTIONS} -d64"
    export JAVA_OPTIONS
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    Linux
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:
    ${TSMAPILIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export LD_LIBRARY_PATH
     EXT_POST_CLASSPATH
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    Solaris (32-bit)
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    TSMCLIENTLIB=/opt/tivoli/tsm/
    client/api/bin
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:
    ${TSMAPILIB}:${TSMCLIENTLIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export LD_LIBRARY_PATH
     EXT_POST_CLASSPATH
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    Solaris (64-bit)
    TSMAPILIB=/opt/IBM/FileNet/
    ContentEngine/tsm100
    TSMCLIENTLIB=/opt/tivoli/tsm/
    client/api/bin64
    LD_LIBRARY_PATH_64=
    ${LD_LIBRARY_PATH_64}:
    ${TSMAPILIB}:${TSMCLIENTLIB}
    EXT_POST_CLASSPATH=
    ${EXT_POST_CLASSPATH}:
    ${TSMAPILIB}/TsmJavaApi.jar
    export LD_LIBRARY_PATH_64
     EXT_POST_CLASSPATH
    JAVA_OPTIONS="${JAVA_OPTIONS} -d64"
    export JAVA_OPTIONS
    WL_HOME="/opt/bea/weblogic92"
    export WL_HOME
    Windows
    set TSMAPILIB=C:\Program Files\IBM\
    FileNet\ContentEngine\tsm100
    set PATH=%PATH%;%TSMAPILIB%
    set EXT_POST_CLASSPATH=%EXT_POST_
    CLASSPATH%;%TSMAPILIB%\TsmJavaApi.jar
    set WL_HOME=C:\bea\weblogic92
  3. If you are using WebLogic Server Node Manager to start and stop managed servers in a clustered environment, you must enable Node Manager to use the appropriate start script:
    1. Open for editing the node manager configuration file WL_HOME/common/nodemanager/nodemanager.properties.
    2. Set the StartScriptEnabled property to true (default is false).
    3. Set the StartScriptName to match the script name used by Node Manager to start the managed server, depending on your operating system:
    Option Description
    AIX, Solaris, HPUX, HPUXi, Linux, Linux for System z StartScriptName=startManagedWebLogic.sh
    Windows StartScriptName=startManagedWebLogic.cmd
    Important: If the managed server is not on the same machine as the WebLogic Server Administration Server and you have an alternate script matching the name of the managed server in the domain bin directory, make sure to specify that script name instead of the more generic "startManagedWebLogic" script.
  4. Save your edits in nodemanager.properties and restart the Node Manager.


Last updated: October 2015
p8pin190.htm

© Copyright IBM Corporation 2013, 2015.