Configuration Tab

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

Select the transport type (JMS or TIBCO 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 resources for use in SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field which uses a dialog to perform SSL configuration. See Transport Type for enabling and configuring the SSL.

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.

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 occurs. See Wire Formats for a description of these formats.

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

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

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

See Delivery Mode for a description of each mode.

Publication Service uses the following two methods to monitor changes to a database table.

It is used to retrieve the records from the database in a specified time. This specified time can be set in the Polling Interval field.

It is used to asynchronously notify running instances of database changes. Use the alerter only when database changes are infrequent.

Type a specific polling interval in milliseconds. This is how often an adapter with Publication Service checks the publishing table for new rows. The default value is 5000 milliseconds or 5 seconds.

Note:

If you select Alerter from the Polling Method list, the Polling Interval field is not displayed.

Select this check box to determine whether you want to poll rows in a batch or not. By default, the Use Polling Batch Size check box is selected.

This field is displayed when the Use Polling Batch Size check box is selected. This field specifies the maximum number of messages that are retrieved at each polling interval. The adapter returns to the event loop when it finishes sending messages. Using this option helps process TIBCO Rendezvous events in an efficient manner. For example, when polling a large number of rows, the adapter works best if a fixed number of rows is specified in this field.

If the Use Polling Batch Size check box is selected, the default value of the Polling Batch Size (Maximum Rows) field is 1000.

In the previous release, the Use Polling Batch Size check box is not selected by default. The default value of the Polling Batch Size (Maximum Rows) field is 0, which indicates that all new rows are fetched. If you use the default value, when the adapter receives a large number of messages from a database within a short period, in which the receiving speed exceeds the processing speed of the adapter, an OutOfMemory error might occur.

To resolve this issue, the default value is changed to 1000 in this release. Even within a short time, the adapter fetches only 1000 rows, which contributes to a reasonable performance of the adapter.

Note:

This check box is displayed when the Use Polling Batch Size check box is selected. Do not use this option when messages are published using a parameterized subject name.

Select this check box to optimize publishing performance by batching message status updates to the publishing table.

If an adapter stops before a batch update is performed, the status column is not updated. As a result, duplicate messages might be published when the adapter is restarted.

Specifies the number of messages that require their status to be updated in a single batch. The default value is 0.

This field is used only for the TIBCO Rendezvous Certified transport type. Do not use this option when messages are published using a parameterized subject name.

Entering a value in this field optimizes performance. However, if an adapter instance stops before a batch update is performed, the status column is not updated. As a result, messages that were successfully published might still have a status of P (pending) in the publishing table when the adapter is restarted. In this case, the ledger file contains the correct status information. Smaller values in this field decrease this risk.