This utility copies supplied resources into the Sterling Warehouse Management System directory structure, and can append added third-party, custom jar files to the global classpath, agent classpath, or application server EAR file.
Following is the syntax for the install3rdParty script:
./install3rdParty.sh vendorName vendorVersion <-d | -j | -l | -p | -r > filelist
[-targetJVM EVERY | NOWHERE | DCL | APP | AGENT | [-uninstall]
Here
For example, ./install3rdParty.sh jboss 4_2_0 -j /ais_local/share/vbhat/sandbox/fairlopmaint/install/jar/jboss/4_2_0/jboss-j2ee.jar -targetJVM APP –uninstall. In this example, the jboss-j2ee.jar file will be removed from both the JAR directory, and the APPDynamicClasspath.cfg file.
Pass the appropriate argument based on the file type. You can pass the following arguments:
<filelist> refers to the path to your custom file.
For example, to install the wlclient.jar to the dynamic classpath of the agent, use the following command:
<INSTALL_DIR>/bin/install3rdParty.sh weblogic 10 -j
<BEA_HOME>/wlserver_10.0/server/lib/wlclient.jar -targetJVM AGENT
This command causes the wlclient.jar file to be copied from the WebLogic installation location into the product installation location (<INSTALL_DIR>/jar/welogic/10/wlclient.jar). The utility then updates the <INSTALL_DIR>/properties/AGENTDynamicclasspath.cfg.in file with the new jar file and invokes the <INSTALL_DIR>/bin/setupfiles.sh utility to regenerate the AGENTDynamicclasspath.cfg file from the modified ".in" file.
If you want to make this new JAR available to the Application Server and Agents when running the install3rdParty utility, pass the following arguments based on your requirements:
If the argument for -targetJVM is not specified, the new jar file is then added to the Dynamicclasspath.cfg file.
Keep the following in mind when using the install3rdParty utility to update a classpath:
For help in using install3rdParty, enter the command, including the -help option, on the command line. The install3rdParty utility prints a usage message.