Configuring JMS Transport Properties

The JMS Transport Properties table shows the properties you must define to use the JMS transport for the Central Logger. The JMS transport properties are defined in the Core Engine properties asg.properties file as well as in the Central Logger properties asg_cl.properties file.

To set the JMS transport properties, follow these steps:

Procedure

  1. Navigate to the ASG_CONFIG_HOME directory.
  2. Open the asg.properties file in a text editor.
  3. Set the properties defined in the JMS Transport Properties table.
  4. Save the changes to the file.
  5. Open the asg_cl.properties file in a text editor.
  6. Set the properties defined in the JMS Transport Properties table.
  7. Save the changes to the file.
    JMS Transport Properties
    Property Description
    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSProviderURL Specifies the URL to connect to the Enterprise Message Service (EMS) or a JMS server.

    Example: tcp://localhost:7222

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIContextURL Specifies a JNDI connection URL to look up a JMS server.

    Example:

    tibjmsnaming://localhost:7222

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TopicConnectionFactoryName Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with JMS server for the Central Logger.

    The default value is TopicConnectionFactory

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/QueueConnectionFactoryName Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with JMS server for the Central Logger.

    The default value is QueueConnectionFactory

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIUsername Specifies the user name to use when logging into the JNDI server. If the JNDI provider does not require access control, this field can be empty.

    Example, admin

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIPassword Specifies the password for logging into the JNDI server. If the JNDI provider does not require access control, this field can be empty.
    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSUsername Specifies the user name to use to authenticate to the JMS server.
    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSPassword Specifies the password to use to authenticate to the JMS server.
    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TransactionReportDestinationName Specifies the name of the JMS destination to which the transaction reports are sent to the Central Logger by the Core Engine.

    For example, asg.cl.transaction.queue

    tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TransactionReportDestinationType Specifies the type of the JMS destination to which the transaction reports are sent to the Central Logger by the Core Engine.

    Possible values are queue or topic.

    The default value is queue

    The Central Logger always listens on a queue. If the value of destination type set to topic, the JMS administrator must configure a bridge between the topic and the queue.

    Note: You must restart the Core Engine and Central Logger instance after setting the properties in the asg.properties and asg_cl.properties file, if they are running.