Defining outbound connectivity
Define the outbound bindings and endpoints that Decision Server Insights uses when sending outbound events in the form of messages.
- Adding outbound bindings
Define an outbound binding that specifies the message format, the protocol, and the events to be delivered. - Identifying outbound messages that require transformation
Add a transformation to outbound messages that are destined for endpoints that have specific format requirements. - Setting headers and message properties for event types
If you are already familiar with JMS and HTTP, you can set the JMS message properties or HTTP headers of outbound messages for individual event types. For example, you might want to specify the values of JMS message properties that enable subscribers to identify messages by using a message selector. - Developing transformations for outbound messages
Develop an .xsl transformation that Decision Server Insights can apply to outbound messages that do not conform to the event schema. - Adding outbound endpoints
Define an outbound endpoint that represents the destination for HTTP or Java™ Message Service (JMS) messages. When you define the endpoint, you must ensure that it references an outbound binding, and either a URL, or a JMS connection factory and destination. If necessary, you can also set advanced properties on an outbound endpoint. - Retiring outbound endpoints and bindings
It might happen that you need to change the connectivity configuration of your solution. To avoid leaving incoming events without anywhere to go or without the required binding, you must consider what happens as a result of your change.
Parent topic: Defining solution connectivity