Defining inbound connectivity

To specify the manner in which Decision Server Insights handles inbound messages, you must first define the inbound bindings (that is, the message format and protocol). For messages that do not conform to the event schema, you define how to transform the messages into events. And then, you must define your outbound endpoints.

Adding inbound bindings
Specify the message format and protocol for inbound messages that are received from an HTTP or JMS endpoint.
Message context
The MessageContext API enables a classifier or transformation to obtain information about inbound messages that is not available in the message content. You can use the MessageContext to inspect the context in which inbound messages are delivered.
Classifying inbound messages for transformation
You can extend an inbound binding so that Decision Server Insights classifies and transforms inbound messages.
Creating transformation files for inbound messages
Develop an .xsl transformation that Decision Server Insights can apply to inbound messages that do not conform to the event schema.
Using the message context to transform messages
If you develop transformations for inbound messages, you can define a namespace in the *.xsl file for the com.ibm.ia.connectivity.MessageContextProvider class to use the message context when transforming the inbound message into an event. You can use the predefined namespace prefix, or your can define a new classifier namespace prefix.
Adding inbound endpoints
Define an inbound endpoint that represents the origin of inbound HTTP or Java™ Message Service (JMS) messages. When you define the endpoint, you must ensure it references an inbound binding. If required, you can also specify additional advanced properties on the HTTP or JMS protocol.

Parent topic: Defining solution connectivity

Related concepts:

Connectivity

Events, entities, and agents

Related tasks:

Creating a solution connectivity file

Defining outbound connectivity