3 6 2 Client Command Tracing

LANSA Integrator

3.6.2 Client Command Tracing

To trace the commands being sent from the client program to the JSM instance, you need to uncomment the trace.transport.address, trace.transport.error.address, trace.service.address or trace.service.error.address keyword in the manager.properties file.

The property trace.transport.address will turn on transport tracing for all services.

The property trace.transport.error.address will turn on transport tracing for all services and if no errors occur then the trace files will be deleted.

The property trace.service.address will turn on transport and service tracing for all services.

The property trace.service.error.address will turn on transport and service tracing for all services and if no errors occur then the trace files will be deleted.

The format of this keyword is:

 

     trace.transport.address=<value>,<value>

     trace.transport.error.address=<value>,<value>

     trace.service.address=<value>,<value>

     trace.service.error.address=<value>,<value>

 

where <value> is the client IP address that needs to be traced, as in this example:

 

     trace.transport.address=137.76.2.202

     trace.transport.error.address=137.76.2.202

     trace.service.address=137.76.2.202

     trace.service.error.address=137.76.2.202

 

or *ALL, to trace all clients, as in this example:

 

     trace.transport.address=*all

     trace.transport.error.address=*all

     trace.service.address=*all

     trace.service.error.address=*all

 

When a client program connects to the JSM instance and transport or service tracing is enabled, trace files are created in the JSM instance trace/jobnumber/date/CLIENTnnnnnnnn sub-directory.

The client directory sequence number is a unique incremental number assigned to each client thread.

The client communication trace records are written to a TRANSPORT.TXT file and the service trace records are written to a SERVICE.TXT file in this client trace directory.

Reminder: In order for changes to the manager.properties file to take effect, you must stop and start the JSM. The manager properties are loaded when the JSM starts.

Example trace directory listing

 

Directory: /jsm/instance/trace/123456

 

     MANAGER.TXT            STMF

     STDOUT.TXT             STMF

     STDERR.TXT             STMF

     2005-06-22             DIR

 

Directory: /jsm/instance/trace/123456/2005-06-22

 

     CLIENT00000001         DIR

     CLIENT00000002         DIR

     CLIENT00000003_NAME    DIR

 

Example file listing of a client trace sub-directory

 

Directory: /jsm/instance/trace/123456/2005-06-22/CLIENT00000001

 

     SERVICE.TXT            STMF

     TRANSPORT.TXT          STMF