Installing third-party JAR files

This utility copies supplied resources into the IBM® Sterling Order 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:

./ vendorName vendorVersion <-d | -j | -l | -p | -r > filelist 
[-targetJVM EVERY | NOWHERE | DCL | APP | AGENT | [-uninstall]


  • <vendorName> must be yfsextn.
  • <vendorVersion> must be 1_0.
  • [-uninstall] is used to remove a JAR file from the JAR directory or the classpath files. Be sure to run right after using this option.

    For example, if you want to add the custom JAR file to the AGENTDynamicclasspath.cfg file, run the install3rdparty command with following arguments:

    ./ yfsextn 1_0 -j <Path_to_your_custom_JAR> -targetJVM AGENT

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 wsogclient.jar to the dynamic classpath of the agent, use the following command:

<runtime_sandbox>/bin/ yfsextn 1_0 -j
<WAS_HOME>/lib/wsogclient.jar -targetJVM AGENT

<WAS_HOME> is typically in /opt/IBM/WebSphere/AppServer

This command causes the wsogclient.jar file to be copied from the WebSphere installation location into the product installation location (<runtime_sandbox>/jar/yfsextn/1_0/wsogclient.jar). The utility then updates the <runtime_sandbox>/properties/ file with the new JAR file and invokes the <runtime_sandbox>/bin/ utility to regenerate the AGENTDynamicclasspath.cfg file from the modified ".in" file.

If you want to make this new JAR file available to the Application Server and Agents when running the install3rdParty utility, pass the following arguments based on your requirements:

Adds the new JAR file to all the dynamic classpath files (for example, APPDynamicclasspath.cfg, AGENTDynamicclasspath.cfg, and dynamicclasspath.cfg.
Adds the new JAR file to the <runtime_sandbox>/jar directory and do not want to update any of the dynamic classpath files
Adds the new JAR file to the main Dynamicclasspath.cfg file only
Adds the new JAR file to the EAR file
Adds the new JAR file to the AgentDynamicclasspath.cfg file
Note: IBM Sterling Order Management System 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 file 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.