Transports

The primary task of an adapter is to retrieve or send data. When you add an adapter service to an adapter, the adapter user interface automatically creates the corresponding session and endpoint to encapsulate transport information necessary for data communication, depending on the transport protocol and delivery mode being used.

You cannot create sessions explicitly or add endpoints to the session. However, you can create a service, and create the session and endpoint in the adapter user interface. If you cannot change the setting directly, you can change the corresponding session or endpoint in the Transport tab. The information is grouped in panels.

Endpoints and Sessions

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

Endpoints send or receive the data. They represent the service provided by an adapter. 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.

For more information about these concepts, see TIBCO Adapter SDK Programmer’s Guide.

Supported Endpoints

Publishers, Subscribers, Clients, or Servers are the endpoints that are available in an adapter. An adapter service encapsulates both an endpoint and the corresponding session. TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) supports the following services:
  • Publication Service

    A Publisher endpoint and associated session.

  • Subscription Service

    A Subscriber endpoint and associated session.

Supported Sessions

Both TIBCO Rendezvous and JMS transport types are supported.
  • For TIBCO Rendezvous transports, sessions of the following kinds of quality of service are available:
    • Reliable (RV)

      Reliable Message Delivery ensures that each multicast or broadcast message is received if 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 is tolerated. When you select this quality of service, 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 succeeds or until the time limit of the message expires. This is often called guaranteed delivery. When you select this quality of service, an RVCM session is used.

    • Distributed Queue (Subscription Service only) (RVCMQ)

      Distributed Queue delivers a message to one of many service listeners (workers). It contains features of both Certified Messaging and Fault Tolerance.

    For more information about the available TIBCO Rendezvous types of quality of service, see TIBCO Rendezvous Concepts.
  • For JMS transports, sessions of the following standard connection factory types are available:
    • 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 called 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 might connect to the queue. The first receiver to access the queue receives the message. The other receivers do not. This messaging model is called point-to-point.

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