Sessions and Endpoints

Both sessions and endpoints are concepts in TIBCO Adapter SDK, the fundamental class library used in the adapter implementation.

Endpoints send or receive data. They represent the service that an adapter configuration provides. Each endpoint is associated with a session that is used to communicate with the source or target application. A session encapsulates the transport information of an adapter service.

The primary task of an adapter configuration is to retrieve or send data. When you add an adapter service to an adapter configuration, the corresponding sessions and endpoints are created by default to encapsulate transport information necessary for data communication, depending on the transport protocol and delivery mode being used.

See TIBCO Adapter SDK Programmer’s Guide for more information about these concepts.

Supported Sessions

For the TIBCO Rendezvous transport, TIBCO ActiveMatrix Adapter for SAP supports sessions of the following kinds of Quality of Service:

Reliable (RV)
Reliable Message Delivery ensures that each multicast or broadcast message is received as long as the physical network and packet recipients are working. It also ensures that the loss of a message is detected.

Reliable Message Delivery can compensate for brief network failures, because it can retransmit a message on request if the first attempt fails. This option is appropriate when message delivery is expected but some loss can be tolerated. When this Quality of Service is chosen, an RV session is used.
Certified (RVCM)
Certified Message Delivery guarantees that every certified message reaches its intended recipient in the order sent. A message can be sent across network boundaries, and if a network fails, delivery attempts continue until delivery is successful or until the time limit of the message expires. This is often called guaranteed delivery. When this Quality of Service is chosen, an RVCM session is used.
Distributed Queue (RVCMQ)
Distributed Queue delivers a message to one of many service listeners (workers). It contains features of both Certified Messaging and Fault Tolerance.
Note: This session type is only supported by the Subscription Service and the Request-Response Service services.

For more information about the supported TIBCO Rendezvous types of Quality of Service, see TIBCO Rendezvous Concepts.

For the JMS transport, TIBCO ActiveMatrix Adapter for SAP supports sessions of the following standard connection factory types:

Topic
A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.
Queue
A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver, though multiple receivers may connect to the queue. The first receiver to access the queue receives the message. The other receivers do not. This messaging model is known as point-to-point.

For more information about connection factories, see TIBCO Enterprise Message Service User’s Guide.

Supported Endpoints

TIBCO ActiveMatrix Adapter for SAP supports the following four types of endpoints:

Publisher
A Publisher endpoint is added to the default session automatically when you add a Publication Service service to the adapter configuration.
Subscriber
A Subscriber endpoint is added to the default session automatically when you add a Subscription Service service to the adapter configuration.
Client
A Client endpoint is added to the default session automatically when you add a Request-Response Invocation Service service to the adapter configuration.
Server
A Server endpoint is added to the default session automatically when you add a Request-Response Service service to the adapter configuration.