Enable JMS Message Logging

Enterprise Administration > Windchill ESI > Administering Windchill ESI in an ORACLE Applications Environment > Administration Tasks > Configuring and Administering JMS Queues > Enable JMS Message Logging

It may be helpful for you to turn on logging for all JMS queues so that you can look at every message that is being exchanged across the Windchill ESI interface.

Shutdown the JMS server and purge any messages on the queues before performing the following steps.

1. Enable logging on the server by following these steps:

a. Locate the tibemsd.conf file in the <Tibco_Home>/ems/<version>/tibco/cfgmgmt/ems/data directory and open it using a text editor, such as Notepad.

b. Locate the following properties related to logging and make the changes:

Property

Description

Example

logfile

Specifies the path and name of your JMS log file.

C:\tibco\jms\jms.log

logfile_max _size

Specifies the maximum size of the log file before it is rotated. Specified as KB and MB.

1MB

log_trace

Specifies what you want logged to the log file. Possible tracing options are:

INFO, WARNING, ACL, LIMITS, SSL, SSL_DEBUG, ROUTE, ROUTE_DEBUG, ADMIN, RVADV, CONNECT, CONNECT_ERROR, PRODCONS, DEST.

A value called DEFAULT logs the following: INFO, WARNING, ACL, LIMITS, ROUTE, ADMIN, RVADV, CONNECT_ERROR. You can add or remove from the default by using a + or a — in front of the property.

log_trace= DEFAULT,-LIMITS, -ACL,+SSL,+ROUTE,+ROUTE_DEBUG

The above setting provides for default logging without LIMITS and ACL, but adds SSL, ROUTE and ROUTE_DEBUG

console_ trace

Determines what you want logged on the console window.

This can impact performance. It is recommended that you log to a file rather than to the console.

See log_trace, described earlier in this table, for values and examples.

The next time you start your EMS server, the changed properties take effect.

2. Specify what should be logged on each queue:

a. Locate the queues.conf file in the <Tibco_Home>/ems/<version>/tibco/cfgmgmt/ems/data directory and open it using a text editor, such as Notepad.

b. Add one of the following properties to the list of properties for each queue you would like to trace, separating each property with commas.

Property	Description	Example
trace	Logs the time the message was put on the queue, the user that sent the message onto the queue, the time the message was taken off of the queue and the user that received the message from the queue.	Tracing messages on the DataResponse queue, you would have the following line in your queues.conf file: SAP com.ptc.windchill.esi.DataResponse.<ESISAPAdapter/SystemID>.<ESISAPAdapter/Client>secure,trace Oracle com.ptc.windchill.esi.DataResponse.<DSN> secure,trace
trace=body	Logs everything that the trace property logs, but also the actual content of the JMS message.	Tracing the DataResponse queue and collecting the actual content of the JMS message, you would have the following line in your queues.conf file: SAP com.ptc.windchill.esi.DataResponse.<ESISAPAdapter/SystemID>.<ESISAPAdapter/Client>,trace=body Oracle com.ptc.windchill.esi.DataResponse.<DSN> ,trace=body

3. Restart your EMS server.

You can also use the EMS Administration tool to perform these steps. For more information, see the TIBCO Enterprise Message Service User's Guide. To get more information about each command, you can also type “help” in the Administration tool.

Isto foi útil?