Installing third-party JAR files

This utility copies supplied resources into the Sterling Order Management System Software 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

  • <vendorName> refers to the name of the vendor such as WebLogic, WebSphere®, and JBoss.
  • <vendorVersion> refers to the version of the vendor's product.
  • [-uninstall] is used to remove a JAR from the JAR directory or the classpath files. Be sure to run setupfiles.sh right after using this option.

    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:

  • -d for database jar/compressed files
  • -j for jar/compressed files
  • -l for shared libraries
  • -p for properties files
  • -r for resource properties files

<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 12.1.2 -j
<BEA_HOME>/wlserver_12.1.2/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/12.1.2/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:

Argument
Description
EVERY
Adds the new JAR to all the dynamic classpath files (for example, APPDynamicclasspath.cfg, AGENTDynamicclasspath.cfg, and dynamicclasspath.cfg.
NOWHERE
Adds the new JAR to the <INSTALL_DIR>/jar directory and do not want to update any of the dynamic classpath files
DCL
Adds the new JAR to the main Dynamicclasspath.cfg file only
APP
Adds the new JAR to the EAR file
AGENT
Adds the new JAR to the AgentDynamicclasspath.cfg file
Note: Sterling Order Management System Software supports only the options listed above for the install3rdParty utility. Any other options that are displayed with the -help message command are not supported.

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:

  • The order of lines in the dynamic classpath files determine the order of the classpath for the application server or agent.
  • Whatever is in the beginning of the file is analogous to the jar being in the beginning of the classpath.

For help in using install3rdParty, enter the command, including the -help option, on the command line. The install3rdParty utility prints a usage message.