Configuration Tab

You can specify values for the following fields on the Configuration tab:

Subscription Service: Configuration Tab

Field

Description

Name

You can use the default name or replace it with a name of your choice.

• An instance name must use alphanumeric characters, and the length of the name must be less than 80 characters. An underscore (_) can be used in an instance name, but the space character cannot be used.
• An instance name cannot use global variables.

Transport Type

Select the transport type (JMS or Rendezvous) to be used by the runtime adapter. This selection determines which options to be displayed in the rest of the Configuration tab.

The transport type can be configured to use a trusted store and identity resource for use in SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field that uses a dialog to perform SSL configuration. See Transport Type for enabling and configuring the SSL.

Note:

If you select JMS as the transport type, you must reset the durable name in the sessions setting. For more information, see Required and Optional Settings.

Quality of Service

(Only available when Rendezvous is selected as the transport type) Select the level of service that determines how messages are sent. See Quality of Service for a description of these options.

• Certified
• Reliable
• Distributed Queue

Note: If you have installed TIBCO Rendezvous 8.4.0 or higher, Subscription Service with RVCMQ enabled remains hung after reconnection to the database.

Wire Format

The wire format in which data will be sent. Note that the wire format for both the publisher and subscriber must be the same, otherwise an error will occur. See Wire Formats for a description of these formats.

• ActiveEnterprise Message (TIBCO Rendezvous transport type only)
• XML Message

Connection Factory Type

Only available when JMS is selected as the transport type. Connection Factory objects create JMS connections for sending and receiving messages. Available choices are:

• Topic
• Queue

See Connection Factory Type for a description of connection factory type.

Delivery Mode

Only available when JMS is selected as the transport type. The delivery mode for each message sending operation.

• Durable
• Non-Durable

See Delivery Mode for a description of each mode.

Use Separate Session

This feature is used with Subscription Service multithreading. When you select this check box, the useSerial check box and the Number of Subscription Service Threads field are displayed. After you set a value in the Number of Subscription Service Threads field, the multiple threads can share the same session and dispatcher. By default, the Use Separate Session check box is not selected.

useSerial

This check box is displayed only when the Use Separate Session check box is selected. This option is designed for ensuring that all messages are executed in order.

Note:

• The primary key related in the destination table cannot be null.
• If the destination table has no primary key, you have to select the User Key check box instead of the primary key. When processing the application requests, messages are handled in order.
• If the destination table has no primary key, and the User Key check box is cleared, it is good practice to clear the useSerial check box.

Number of Subscription Service Threads

This field is displayed only when the Use Separate Session check box is selected. Threads are allocated on demand. Valid values are from 1 through n. The number of threads you set in Subscription Service indicates the number of subscription threads that will connect to the database. See Multithreading in Subscription Service for more information.

 

Note 

Note the following conditions regarding Subscription Service threads:

• TIBCO Hawk statistics display all Subscription Service threads information and operation count.
• Debug messages provide the Subscription Service thread name to distinguish which message is from which Subscription Service thread.
• If a Subscription Service thread encounters fatal errors, such as failing to roll back a transaction or failing to update the exception table, the adapter terminates.
• At startup the Subscription Service dispatchers wait for all components to start before dispatching subscriber messages.
• Subscription Service can automatically identify group messages and process them within a single transaction. Processing group messages in turn helps improve the performance of Subscription Service.