Configuring an Inbound Load-Balanced Service

This section outlines the steps to configure inbound load-balanced services containing Subscription Services and Request-Response Services. During the configuration of the services, the quality of service must be configured as a distributed queue.

This section outlines the steps used to configure inbound load-balanced services containing Subscription Services and/or Request-Response Services.

During the configuration of the adapter services, the quality of service must be configured as type distributed queue.

Configuration of inbound load-balanced services can be done either by:
  • Creating multiple inbound services where the CMQ names are the same across the services.
  • Creating one inbound service that can be invoked multiple times.

RVCMQ Session Attributes

The behavior of RVCMQ is complex and attributes for RVCMQ sessions must be set with care. For more detailed information, see the TIBCO Rendezvous Concepts manual and TIBCO Designer SDK Resource Guide for details on configuring an RVCM Session.

It is good practice that you have a good grasp of the following concepts and discussed in TIBCO Rendezvous Concepts before you finalize the configuration of any inbound service running in RVCMQ mode.
  • Understanding Rank and Weight
  • Weight Values
  • Assigning Weight
  • Rank among members with different weight
  • Rank among members with equal weight
  • Status quo among members with equal weight
  • Adjusting Weight
  • Understanding and setting heartbeats
Note: Before changing the quality of service, make sure that no network sinks have asession reference, referring to the default sessions (DefaultRVSession, DefaultRVCMSession, DefaultRVCMQSession) created by the palette. To avoid this, have a custom session associated with the network sink. To avoid message loss after activation of a suspended RVCMQ service, assign CompleteTime to a value greater than Zero.When the completeTime is assigned Zero the scheduler does not set a timer and does not reassign tasks when the task completion confirmation is not received. So after activation of a suspended service the scheduler does not reassign the task to the worker member. For more information on RVCMQ parameters, refer to TIBCO Rendezvous documentation.