TIBCO Rendezvous Adapter

The TIBCO Rendezvous adapter connects Sterling B2B Integrator to the TIBCO Rendezvous server, which is the message path for TIBCO ActiveEnterprise.

The following table provides an overview of the TIBCO Rendezvous™ adapter:

Category Description
System name Tibco
Graphical Process Modeler (GPM) category All, Queuing
Description Connects Sterling B2B Integrator to the TIBCO Rendezvous server, which is the message path for TIBCO ActiveEnterprise™. TIBCO ActiveEnterprise is the TIBCO integration platform that allows applications, services, and third-party systems to be linked together into an integrated system.
Preconfigured? No
Requires third-party files? Yes. See Required Files.
Platform availability Sun Solaris
Related services No
Initiates business processes? Yes
Invocation Runs as part of a business process.
Restrictions The TIBCO Rendezvous adapter works only in the Solaris environment.

Requirements

The TIBCO Rendezvous adapter works only in the Solaris environment.

How the TIBCO Rendezvous Adapter Works

The TIBCO adapter supports publish (send) and subscribe (receive) transactions. These transactions are linked by using the subject, which is a TIBCO Rendezvous server location where publisher applications can publish messages and subscriber applications can subscribe to messages. Publishers are decoupled from subscribers. That is, they do not coordinate data transmission with each other, except by using the subject.

When used as an outbound adapter, the TIBCO adapter publishes transactions to the subject that the TIBCO Rendezvous applications use for subscribe transactions.

When used as an inbound adapter, the TIBCO adapter subscribes to transactions for the subject that the TIBCO Rendezvous applications use for publish transactions.

The TIBCO Rendezvous daemon supports efficient network communications by acting as the pathway for the TIBCO Rendezvous business processes running across the network. The TIBCO Rendezvous daemon arranges the details of data transport, packet ordering, receipt acknowledgment, retransmission requests, and data dispatching for the appropriate business processes.

Data Flow of an Outbound Adapter

Following is the data flow for the TIBCO Rendezvous adapter when it functions as an outbound adapter:
  1. The TIBCO adapter outputs data in XML format, which is encoded in a TibrvMsg_XML wire format. A wire format is a universal format independent of hardware, operating system, and programming language architecture that provides a common language to connect diverse programs.
  2. After the data is encoded in a TibrvMsg_XML wire format, it is sent to the TIBCO Rendezvous server and processed by the TIBCO API.
  3. The TIBCO API provides the TibrvXML object, which accepts the XML message as a byte array and compresses it, reducing the number of bytes sent over the network.
  4. The TibrvXML object is stored in the TibrvMsgField data field object.
  5. The TibrvMsgField data field object is added to the TibrvMsg object, which is transmitted to the TIBCO Rendezvous server.

Data Flow of an Inbound Adapter

Following is the data flow for the TIBCO Rendezvous adapter when it functions as an inbound adapter:
  1. The TIBCO Rendezvous adapter accepts the TibrvMsg object. The TibrvMsg object contains the TibrvMsgField, which contains the compressed TibrvXML.
  2. The incoming XML data is converted into a byte array and is passed to the business process context, which is passed to Sterling B2B Integrator.

Implementing the TIBCO Rendezvous Adapter

To implement the TIBCO Rendezvous adapter, complete the following tasks:
  1. Activate your license for the TIBCO Rendezvous adapter. For information, see An Overview of Implementing Services.
  2. Create a TIBCO Rendezvous adapter configuration. For information, see Managing Services and Adapters.
  3. Configuring the TIBCO Rendezvous adapter. For information, see Configuring the TIBCO Rendezvous Adapter.
  4. Use the TIBCO Rendezvous adapter in a business process.

Configuring the TIBCO Rendezvous Adapter

To configure the TIBCO Rendezvous adapter, you must specify settings for the following fields in Sterling B2B Integrator:

Field Description
Name Unique and meaningful name for the adapter configuration. Required.
Description Meaningful description for the adapter configuration, for reference purposes. Required.
Select a Group Select one of the options:
  • None – You do not want to include this configuration in a group at this time.
  • Create New Group – You can enter a name for a new group in this field, which will then be created along with this configuration.
  • Select Group – If you have already created one or more groups for this service type, they are displayed in the list. Select a group from the list.
Service number User Datagram Protocol (UDP) service number. The default value is 7500.
Network IP address of the server running the TIBCO Rendezvous daemon.
Daemon Name of the background process that completes the information pathway between TIBCO Rendezvous processes across the network. The name has one format, rvd, with rvd indicating the process name.
Action One of the following modes of EAI communications:
  • async publish (outbound communication)
  • async subscribe (inbound receiver of events)
  • sync send (request/response outbound communication)
Subject TIBCO Rendezvous server location to which the messages are published or subscribed.

Required Files

The following table identifies required files for the TIBCO Rendezvous adapter. These files must be located on the server where the TIBCO Rendezvous applications reside.

Path Requirement
CLASSPATH Include the tibrvj.jar file, which contains the TIBCO API class files
LD_LIBRARY_PATH Include the following library (*.so) files (provided by TIBCO):
  • librv.so
  • librvcm.so
  • librvcmq.so
  • librvcst.so
  • librvft.so
  • librvjcms11.so
  • librvjfts11.so
  • librvjs11.so
  • librvts.so
  • librvXt.so
  • libtibrv.so
  • libtibrv64.so
  • libtibrvcm.so
  • libtibrvcm64.so
  • libtibrvcmq.so
  • libtibrvcmq64.so
  • libtibrvft.so
  • libtibrvft64.so
  • libtibrvj.so

TIBCO Rendezvous Publisher Transaction

To publish messages to the TIBCO Rendezvous server, you must configure the adapter to the appropriate subject.

Publisher Configuration

The following table describes the configuration required to run a TIBCO Rendezvous publisher transaction:

Field Description
Name Unique and meaningful name for the service configuration. Required.
Description Meaningful description for the service configuration, for reference purposes. Required.
Service number User Datagram Protocol (UDP) service number. The default value is 7500.
Network IP address of the server running the TIBCO Rendezvous daemon.
Daemon Name of the background process that completes the information pathway between TIBCO Rendezvous processes across the network. The name has one format, rvd, with rvd indicating the process name.
Action Of the modes of EAI communications listed, select either:
  • Async publish (outbound communication)
  • Sync send (request/response outbound communication)
Subject TIBCO Rendezvous server location to which the messages are published or subscribed.
User Timeout Field displays when you select sync send from the Action field. This is the time designated for a response to the transmission. Required.

Publisher Transaction Process

Following is the publisher transaction process for the TIBCO Rendezvous adapter:
  1. When run as part of a business process, the TIBCO Rendezvous publisher extracts the document from the business process context and converts it into a message.
  2. The publisher uses the adapter to publish (send) the message to the specified TIBCO Rendezvous server.
  3. If the transmission is synchronous, the adapter waits for a document from the TIBCO Rendezvous server. The document is returned as the primary document. If the transmission is asynchronous, the adapter does not wait for a document but does receive a status indicating whether the transmission was a success or failure.
  4. The publisher returns the status of the TIBCO Rendezvous message generation to the business process.

TIBCO Rendezvous Subscriber Transaction

To subscribe to messages from the TIBCO Rendezvous server, you must configure the adapter to the appropriate subject:

Subscriber Configuration

The following table describes the fields used to configure the TIBCO Rendezvous server for a subscriber transaction:

Field Description
Name Unique and meaningful name for the adapter configuration. Required.
Description Meaningful description for the adapter configuration, for reference purposes. Required.
Select a Group Select one of the options:
  • None – You do not want to include this configuration in a group at this time.
  • Create New Group – You can enter a name for a new group in this field, which will then be created along with this configuration.
  • Select Group – If you have already created one or more groups for this service type, they are displayed in the list. Select a group from the list.
Service number User Datagram Protocol (UDP) service number. The default value is 7500.
Network IP address of the server running the TIBCO Rendezvous daemon.
Daemon Name of the background process that completes the information pathway between TIBCO Rendezvous processes across the network. The name has one format, rvd, with rvd indicating the process name.
Action Of the modes of EAI communications listed, select async subscribe (inbound receiver of events)
Subject TIBCO Rendezvous server location to which the messages are published or subscribed.
FileName File name of the incoming XML document.
Business Process Name Name of the business process to start.

Subscriber Transaction Process

Following is the subscriber transaction process for an asynchronous transaction:
  1. The subscriber subscribes to a particular TIBCO Rendezvous message.
  2. When the subscription operation is complete, the TIBCO Rendezvous server sends the subscriber an instance of the message.
  3. The subscriber passes the incoming XML document to the initial business process context and runs the specified business process.
  4. In the case of an asynchronous subscriber, the subscriber sends an acknowledgment to the TIBCO Rendezvous application that sent the response.
  5. The subscriber listens for additional TIBCO Rendezvous messages.