3 6 3 Service Program Tracing

LANSA Integrator

3.6.3 Service Program Tracing

Client command tracing does not need to be enabled for service program tracing to work.

To allow tracing into the service program being called by a client program, add an entry to the service.properties file.

The structure of this entry is:

 

     trace.<service>=<value>

 

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

 

     trace.FTPService=137.76.2.202

 

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

 

     trace.FTPService=*all

 

When service tracing is enabled, a JSMTrace object is available from the JSMContainer object.

Normally this JSMTrace object is null. If the trace object is not null then text messages can be written to the associated SERVICE.TXT trace file.

 

Reminder: In order for changes to the service.properties file to take effect, you must stop and start the JSM or use the Java Service Manager Console or the Integrator Studio to refresh the loaded services.