| Installation Name
|
Yes
|
The name of the TIBCO BusinessConnect installation.
|
| Subject Prefix
|
Yes
|
The subject prefix from the TIBCO BusinessConnect installation.
|
| Service
|
Yes
|
Either the name of the Rendezvous service or its port number. If left blank, TIBCO Rendezvous uses the Rendezvous service, if it exists; otherwise it uses
7500 port.
|
| Network
|
Yes
|
The network to be used by the Rendezvous daemon. This is optional.
|
| Daemon
|
Yes
|
The client socket used for the Rendezvous daemon. The default value is
7500.
|
| Quality of Service
|
No
|
Specifies the quality of service for messages transmitted to the TIBCO BusinessConnect server. This quality of service corresponds to TIBCO Rendezvous protocols.
The available options are:
- Reliable
- Certified
- Distributed-Queue
The remaining fields vary based on the quality of service you select. If you select
Reliable, you are done.
|
| Server to PP CM Auto Confirm
|
No
|
If this check box is selected, it configures the certified listener transport to automatically confirm delivery of messages from the TIBCO BusinessConnect server to the private process. Otherwise, the private process is responsible for confirming delivery. You need to add a Confirm activity in the private process and specify which event to confirm. See
TIBCO Designer User’s Guide for more information.
Note: If this check box is selected and any listener using this BC Connection is loaded, all messages for this BC Connection are confirmed even though there is no active listener loaded in the panel for these messages (messages are not dispatched successfully to any listener). To avoid this behavior, clear the
Server to PP CM Auto Confirm check box and use the explicit confirmation; in such a case, the TIBCO Rendezvous messages are confirmed only if the Confirm activity is executed for the event.
|
| Local CM Name
|
Yes
|
The name of the local certified messaging transport.
|
| Preregistered BC Queue Name
|
Yes
|
A comma-separated list of certified messaging sessions to register at TIBCO BusinessWorks.
|
| Use Process Based Ledger
|
No
|
If this check box is selected, a process-based ledger is used for interaction between TIBCO BusinessWorks and the TIBCO BusinessConnect server.
If the
Use Process Based Ledger check box is selected, the value in the
File Based Ledger field is ignored.
|
| File Based Ledger
|
Yes
|
TIBCO Rendezvous certified ledger file name for interaction between TIBCO BusinessWorks and the TIBCO BusinessConnect server.
|
| QOS (Quality of Service) Properties specific for TIBCO Rendezvous
|
| Local Distributed Queue
|
Yes
|
The name of the distributed queue. This name must be different from the name specified in the
Local CM Name field (otherwise there is a name collision exception at runtime).
|
| Queue Settings
|
No
|
Specify the properties of the distributed queue.
Selecting this field causes the
Worker Weight,
Worker Tasks,
Scheduler Weight,
Scheduler Heartbeat,
Scheduler Activation and
Worker Complete Time fields to appear.
|
| Worker Weight
|
Yes
|
The weight to assign to this worker member of the distributed queue. See the TIBCO Rendezvous documentation for more information about assigning worker weight.
|
| Worker Tasks
|
Yes
|
The maximum number of tasks this worker can accept. When the number of accepted tasks reaches this maximum, the worker cannot accept additional tasks until it completes one or more of them. See TIBCO Rendezvous documentation for more information about setting the number of tasks.
|
| Scheduler Weight
|
Yes
|
Weight represents the ability of this member to fulfill the role of scheduler, relative to other members with the same name. See the TIBCO Rendezvous documentation for more information about setting the scheduler weight.
|
| Scheduler Heartbeat (seconds)
|
Yes
|
The scheduler sends heartbeat messages at this interval (in seconds). All members with the same distributed queue name must specify the same value for this parameter. See the TIBCO Rendezvous documentation for more information about setting the scheduler heartbeat.
|
| Scheduler Activation (seconds)
|
Yes
|
When the heartbeat signal from the scheduler has been silent for this interval (in seconds), the member with the greatest scheduler weight takes its place as the new scheduler. See the TIBCO Rendezvous documentation for more information about setting the scheduler activation.
|
| Worker Complete Time
|
Yes
|
The complete time property influences scheduler behavior.
If the complete time is non-zero, the scheduler waits for 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.
Zero is a special value, which specifies no limit on the completion time—that is, the scheduler does not set a timer, and does not reassign tasks when task completion is lacking. All members implicitly begin with a default complete time value of zero.
The complete time must be non-negative.
|
