Creating Additional Log and Payload Services

A log service and a payload service are created on the SystemNode node when you create an Administrator server. If you want to create logs or payload services on other nodes, you can do so explicitly.

Note: For instructions to deploy the logging and payload services to the SystemNode if they were not deployed when creating the Administrator server using TIBCO Configuration Tool, refer to TIBCO_HOME\administrator\version\scripts\logging\readme.txt.

Procedure

Create a JMS queue that will be used by the log service and a JNDI name for the queue.
Create the resource templates used by the log service. Refer Log Service Property Reference. Additionally create the resource templates for the referenced resource instances.
Create resource instances for the resource templates created in the previous step. Creating Resource Instances on Nodes.
Create a new log service application using the log service application template. Creating an Application.
Distribute the application. Refer Distributing an Application.
Update the properties for the application using the previously created resource instances. Setting a Property Value.
Deploy the application. Deploying Applications.

What to do next

Create a payload service using the above procedure. Refer Payload Service Properties Reference for the required resource templates.

The log and payload services cannot monitor the same JMS queue. However, more than one log service can monitor the same JMS queue and store logs to the same database. This feature can be used to achieve high availability of the log service.
If multiple log services monitor the same queue, the log service data should be saved to the same database. Similarly, If multiple payload services monitor the same queue, the payload data should be saved to the same database.
The log and payload services cannot share an HTTP Connector.