XI Adapter 4.6 | webMethods XI Adapter Documentation | webMethods XI Adapter Installation and User’s Documentation | Overview | Exchanging MessageObjects Through the PI/PO Environment | MessageObject Routing | Sender Endpoints
 
Sender Endpoints
A sender endpoint has three parts, as follows:
*Business system name. The first part is the name of the business system that is sending the MessageObject. For example, a travel agency might have a business system named RequestFlightInfo and another named RequestFlightBooking.
*Interface name. The second part is the name of an interface that is defined in the PI Integration Repository. The interface describes the data types, direction (inbound or outbound), and delivery mode (synchronous or asynchronous) of the MessageObject.
*Interface namespace. The third part is an interface namespace. You can use the namespace to differentiate multiple interfaces that have the same name but different signatures and meanings. Suppose you have several interfaces named RequestsforFlightBookings; you would differentiate the interfaces by using a different namespace for each interface. Typically, the interface namespace is a URI.
Each sender endpoint is globally unique within a PI integration landscape.
An example of a sender endpoint is as follows: