Sessions

No matter which transport type of session you select, JMS or Rendezvous, the general information of the session is displayed in a generic configuration panel at the top of the Configuration panel. Apart from the generic configuration, most sessions have more configuration options. These options are displayed in one or more configuration panels.

Rendezvous sessions include the following options:

Rendezvous Configuration
Rendezvous Options: Reliable Session
Rendezvous Options: Certified Session
Rendezvous Options: Distributed Queue Session
For more information, see the TIBCO Rendezvous documentation.

JMS sessions include the following options:

JMS Configuration
More Options Reference
For more information, see the TIBCO Enterprise Message Service documentation.

Rendezvous Configuration

The Rendezvous Configuration panel contains the following fields:

Name	Description
Name	Name of the TIBCO Rendezvous transport.
Description	(Optional) Description of the transport.
Daemon	Specifies the TIBCO Rendezvous daemon for this session.
Network	Specifies the network for this transport. By default, the property is an empty string, which is interpreted as the primary network. Using this attribute only makes sense on computers with more than one network interface.
Service	Specifies the service for this transport. By default, the property is defined to be the default TIBCO Rendezvous service (`7500`).
Connection Type	The type of the connection includes: Reliable Certified Distributed Queue

Rendezvous Options: Reliable Session

No additional configuration is required for the Reliable sessions.

Rendezvous Options: Certified Session

The Certified sessions contains the following fields:

Name	Description
CM Name	Used to identify the delivery tracking session. The CM name must be unique across the entire network.
Ledger File	Points to a ledger file. If the value of the property value is a valid file name, the transport uses a file-based ledger.
Sync Ledger File	This check box controls the behavior when updating the ledger file. When the check box is selected, operations that update the ledger file do not return until the changes are written to the storage medium. When the check box is cleared, the operating system writes changes to the storage medium asynchronously.
Relay Agent	Relay agent for this transport.
Require Old Message	This check box indicates whether a persistent correspondent requires delivery of messages sent to a previous transport with the same name for which delivery is not confirmed. Its value affects the behavior of other delivery-tracking senders. When the check box is selected, if the name attribute is non-NULL, the transport requires certified senders to retain unacknowzledged messages sent to this persistent correspondent. When the check box is cleared, messages are not retained.
Message Timeout (sec)	Maximum time (in seconds) that this call can block while waiting for a reply.

Rendezvous Options: Distributed Queue Session

The Distributed Queue sessions contains the following fields:

Name	Description
CMQ Name	Sequence of module properties that specify the name of the queue.
Worker Weight	Relative worker weights assist the scheduler in assigning tasks. When the scheduler receives a task, it assigns the task to the available listener with the greatest listener weight. The default value is `1`.
Worker Tasks	Worker tasks for this session. The default value is `1`.
Worker Complete Time (sec)	If the complete time is non-zero, the scheduler waits a worker member to complete an assigned task. If the complete time elapses before the scheduler receives completion from the worker member, the scheduler reassigns the task to another worker member. The default value is `0`.
Scheduler Weight	Represents the ability of this session to fulfill the role of scheduler, relative to other members in the same queue. The queue members use relative scheduler weight values to elect one member as the scheduler. Members with higher scheduler weight take precedence. The acceptable values range from `0` to `65545`. The default value is `1`.
Scheduler Heartbeat (sec)	The scheduler session sends heartbeat messages at this interval (in seconds). All member sessions in the queue must specify the same value for this parameter. The acceptable values are unsigned decimals. The default value is `1000`.
Scheduler Activation (sec)	When the heartbeat signal from the scheduler has been silent for this interval (in seconds), the queue member with the greatest scheduler weight takes its place as the new scheduler. All member sessions in the queue must specify the same value for this parameter. The acceptable values are unsigned decimals. The default value is `3000`.

JMS Configuration

The JMS Configuration panel contains the following fields:

Name	Description
Name	Name of the JMS transport.
Description	(Optional) Description of the transport.
Connection Type	The available connection types include: Direct The connection is direct. JNDI A JNDI Server is used.
Provider URL	(Direct connection type only) URL of the server.
Connection Factory	(Direct connection type only) The available connection factory types include: TopicConnectionFactory A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is called publish-subscribe. QueueConnectionFactory A message sent to a queue is received by one and only one receiver. Each message has only one receiver, though multiple receivers might connect to the queue. The first receiver to access the queue receives the message. The other receivers do not. This messaging model is called point-to-point.
Test Connection	(Direct connection type only) Used to test connection to the server at the specified Provider URL.
JNDI Reference	(JNDI connection type only) JNDI server information.

More Options Reference

The More Options panel contains the following fields:

Name	Description
Client ID	ID of the client.
User Identity	Detailed information of the user.

Note: You have to configure the JMSConnection parameters in JMSSharedResources (in the Resources folder) when the TIBCO ActiveMatrix BusinessWorks activities use JMS transport in TIBCO Business Studio. The JMSConnection parameters are configured in the Advanced tab in TIBCO Business Studio.