Message Services

A message service enables interaction with external messaging systems by allowing applications to create, send, receive, and read messages.

Message services can be defined using simple parameters to describe the message content or by associating the message service with one or more schemas, xsd files, that describe the content of an xml document.

A service is developed and is associated with a messaging endpoint either during development or package definition. The association with the messaging endpoint can be subsequently changed without the need to change the message service interface.

During development, a message service is defined as a one way call to a service implementation via the service interface. The service operations are bound as defined in the services package profile or deployment profile.

When a message service is developed to send data to a transport (outbound service), the message service is defined using Input style parameters. During deployment, the message service sends the message using the transport to which the service is bound. A message service can be deployed independently or used to develop a composite service, such as a business process.

Note: Retrieval of data from a transport using a message service is handled according to what is defined in the services package profile or deployment profile. The service interface is configured to listen for messages arriving via a designated HTTP or other messaging transport, such as file, JMS, or POP3. This creates a notification as a call to the message service using a one-way operation where the service is publicly accessible over the transport enabled as a public protocol.

The following messaging types are supported for a message service:

FTP
Email
SMS (Short Message Service)
JMS (for EAServer, WebSphere MQ, OpenJMS, TIBCO JMS and generic JMS)
File