Community articleSetting the Java Process Definitions
Added by IBM contributorIBM on November 25, 2011
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

If you are using the Classic API, you must set the Java™ process definitions. If you are using the Streaming API, you do not need to set the Java process definitions.



If you are using the Classic API, you must set the Java™ process definitions. If you are using the Streaming API, you do not need to set the Java process definitions.

To set the Java process definitions:
  1. In the WebSphere® Integrated Solutions Console, go to the Environment Entries page for the server to which you are deploying the API.
  2. WebSphere versionEnvironment Entries page location
    6.1Servers -> Application servers -> <server_name> -> Java and Process Management -> Process Definition -> Environment Entries
    7.0Servers -> Server Types -> WebSphere application servers -> <server_name> -> Java and Process Management -> Process Definition -> Environment Entries

  3. Add or update the location of the API library files.
  4. The resource name depends on the operating system.
    Operating systemResource name
    WindowsAdd a PATH resource and point it to the API directories that contain .dll files. For example:

    ${LFS_API_DIR};${LFS_API_DIR}/PureEdge/80/system
    AIX®Add a LIBPATH resource and point it to the API directories that contain .so files. For example:

    ${LFS_API_DIR}:${LFS_API_DIR}/PureEdge/80/system
    SolarisAdd a LD_LIBRARY_PATH resource and point it to the API directories that contain .so files. For example:

    ${LFS_API_DIR}:${LFS_API_DIR}/PureEdge/80/system
    LinuxAdd a LD_LIBRARY_PATH resource and point it to the API directories that contain .so files. For example:

    ${LFS_API_DIR}:${LFS_API_DIR}/PureEdge/80/system
    IBM® iAdd a LIBPATH resource and point it to the API directories that contain .so files. For example:

    ${LFS_API_DIR}:${LFS_API_DIR}/PureEdge/80/system


    Note: If the PATH, LIBPATH, or LD_LIBRARY_PATH resources have already been defined, then append the API directories to the existing paths. Remember to use the correct separator; Windows uses a semicolon, but AIX, Linux, and Solaris platforms use a colon.
Parent topic: Configuring WebSphere Application Server to use IBM Forms API
Previous topic: Setting the Shared Libraries
Next topic: Setting the server class loader