Progress Sonic ESB Configuration and Management Guide

Chapter 3: ESB Endpoints and Connections
Entry Endpoint
An entry endpoint always uses an endpoint address, a destination associated with an
underlying JMS topic or queue used as the entry into an ESB process or service. You can
use intra-container messaging to bypass the entry endpoint if the caller is in the same
container (see “ESB Container Intra-container Messaging” on page 61). Services that
must be accessed from remote JMS or HTTP clients or from itineraries that start in other
containers should have a JMS-capable entry endpoint.
Exit Endpoint
An exit endpoint can be any type of ESB address (or list of addresses.) It is the configured
last destination of an ESB process or service. The exit endpoint is typically configured as
REPLY_TO, a specially named endpoint that uses as the reply to destination name set on the
message that started the service operation or ESB process. The exit endpoint setting can
be overridden by an ESB process.
Fault Endpoint
A fault endpoint can be any type of ESB address. It is an endpoint to which application
messages with recoverable errors are sent. Messages are sent to the fault endpoint if
requested by the service.
Each service can have an optional fault endpoint for those messages it cannot handle. The
service decides which messages are sent to the fault endpoint as part of normal
processing. The fault endpoint can contain any valid message
The fault endpoint handles recoverable processing errors (for example, an out-of-stock
notice), and interruptions in the normal process that must be handled at the application
level.
The fault endpoint inherits the Quality of Service (QoS) settings of the service application
or ESB process.
The fault endpoint is often set as an address to another service or ESB process. It might
also be an endpoint (Progress SonicMQ destination) or a REPLY_TO destination.
95 Progress Sonic ESB Configuration and Management Guide 8.5