To trace the commands being sent from the client program to the JSM instance, you need to uncomment the trace.connections keyword in the manager.properties file.
The property trace.connections will turn on tracing for all services.
When a client program connects to the JSM instance and connection 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 can stop and start the JSM or use the Java Service Manager Console or the Integrator Studio to refresh the loaded services.
Example trace directory listing
Example file listing of a client trace sub-directory