Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Integration - Transports, Messaging, and ESB

Updated on September 10, 2021

 This presentation is part of the Services and Connectors Self-Study Course.


Integration transports are used to provide connectivity to an underlying data source or message source in a consistent way.  Guaranteed message delivery is a key feature of products that support messaging and is usually achieved by having the calling application wait until the message has been successfully placed in a message queue (usually implemented as a database table in a relational database).  This is often used as the backbone of an SOA's Enterprise Service Bus. Even though these messaging transports are inherently asynchronous, the messages can be implemented synchronously. 

A synchronous transport means the calling application is blocked until the called application has completed its processing.

An asynchronous transport means the calling application can continue processing while the called application is in the middle of its processing.

Some popular integration transports are:

  • HTTP, which stands for Hypertext Transfer Protocol, is the means by which one communicates using web browsers. Its transmission is inherently synchronous.
  • SMTP or Simple Mail Transport Protocol is also a synchronous transmission.  It is usually used to support email messages.
  • JMS (Java Messaging Service) and WebSphere MessageQueue support asynchronous and synchronous messaging.  That way, you get synchronous processing if you need it, but with better guaranteed message delivery than over HTTP.

PRPC supports all these transports as part of the protocols used in PRPC services and connectors.

There are two types of messaging:

  • Point-to-point:  one sender of the message and one receiver (or consumer)
  • Publish-subscribe:  one sender (or publisher) of the message with multiple receivers (or subscribers)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us