2.4 Java Service Manager Administration for Linux

The Java Service Manager runs in its own shell or as a background process.

Starting the JSM

The Java Service Manager on Linux is started using the strjsm program found in $LANSAXROOT/integrator/sh. It should be run by the LANSA owner, in its own shell. It can also be run as a background process.

After running strjsm, the following should be sent to standard output:

    Starting JSM

        Instance directory : /lansa/integrator/instance

        Process ID         : 18621


Ending the JSM

You should use Integrator Studio to stop accepting clients to avoid disconnecting any clients in the middle of a transaction and to also shut down the JSM.

Instance Location

By default, strjsm uses the LANSAXROOT environment variable to find the JSM instance to execute. The instance location, in this case, is $LANSAXROOT/integrator/instance. There are two ways to override this:

Supply another instance location on the command line. For example, this code will use the instance found at jsm/instance in the current directory:
    strjsm jsm/instance

If LANSAXROOT and JSM_INSTANCE_DIR are both undefined and no instance directory is specified on the command line, strjsm will fail with an error.

Clear Trace Directory

If you run strjsm with the -c (lowercase c) option, it will clear the instance's trace directory before starting the JSM server. The trace directory will be empty except for a directory for the current JSM server's process.

If the JSM_CLEAR_TRACE environment variable is set to a non-empty string, the trace directory will be cleared by default. In this case, it can be turned off with the -C (uppercase C) option.