Configuring and Administering JMS Queues
Windchill ESI services subscribe to and use JMS queues to communicate with Windchill EAI software components. The only queue that Windchill ESI services subscribe to is the one that the middleware uses for sending Result messages to Windchill. This is named com.ptc.windchill.esi.Result by default.
|
|
The other JMS queue used by Windchill ESI is named com.ptc.windchill.esi.DataResponse.<SystemID>.<Client> by default. ESI services place the ESI response messages on this queue.
|
The following lists the various tasks associated with the JMS Queues.
Windchill ESI Services Tasks:
• Subscribe to JMS queues
• Authenticate JMS queues
• Configure JMS queue performance
Windchill EAI Software Components Tasks:
|
|
Refer to the following chapters in the TIBCO Enterprise Message Service User Guide for detailed information on the following tasks:
• Running the EMS Server
• Using the EMS Administration Tool
|
These sections provide detailed information on how to:
• Start and connect to the JMS server
• Administer and configure JMS queues
• Set administrator password
• Create the JMS queues
• Enable authentication
• Secure JMS queues
• Create an ESI user
• Create a Windchill user
• Set permissions
• Set QueueConnectionFactory
• Enable JMS message logging
Properties are available to control certain performance aspects of the JMS queues and to enable or disable the startup of the JMS queues. The following describes the tasks associated with maintaining and administering the JMS queues.
