Integration Channels

To provide maximum flexibility for exposing services to the enterprise, service implementation is separated from the interface. This allows services to be invoked from different transport mechanisms. The following transports are supported:

  • SOAP Over HTTP
    SOAP over HTTP service calls use the standard synchronous web services message format.
  • SOAP Over JMS
    SOAP works over a variety of transports and is not restricted to HTTP web services. JMS provides a highly available transport mechanism that delivers messages over and above what HTTP provides. SOAP over JMS service calls use the TIBCO proposed specification extension for sending SOAP messages over JMS. TIBCO Fulfillment Subscriber Inventory supports calling SOAP over JMS synchronously using the standard SOAP Request/Reply activity.