Topology for WS-Notification as an entry or exit point to the service integration bus
除了能夠在 WS-Notification 生產端和消費端之間傳遞資訊以外,WebSphere® Application Server 中所提供的 WS-Notification 支援也用來作為服務整合匯流排的進入點或結束點。 WS-Notification 應用程式所發佈的事件通知會插入服務整合匯流排中,在這裡,任何連接匯流排的其他應用程式都可以修改、重新遞送或消費這些事件通知。 同樣地,WS-Notification 消費端也可以接受服務整合匯流排用戶端(如 JMS 之類)所傳送的發佈資訊。
You can configure WS-Notification so that web service applications receive event notifications generated by other clients of the service integration bus such as JMS clients. Similarly web service applications can generate notifications to be received by other client types. You achieve this configuration by creating a permanent topic namespace that allows messages to be shared between web service and non web service clients of the bus, as described in 提供 WS-Notification 應用程式對於現有匯流排主題空間的存取.
In the following figure a WS-Notification publisher inserts an event notification into the notification broker that is received by a JMS message consumer. Conversely a JMS message producer can publish a message that is received by a notification consumer. Messages pass from the publisher into the notification broker, using SOAP over HTTP , and travel through a WebSphere Application Server, to the JMS provider, and out to the JMS message consumer using JFAP. Conversely, messages pass from the JMS message producer into the JMS provider using JFAP, and travel through a WebSphere Application Server to the notification broker, and out to the notification consumer using SOAP over HTTP.

Interacting with JMS message types
The WS-Notification service is responsible for both inserting messages into the service integration bus (in response to Notify operations received from Web services) and receiving messages from the bus (in order to pass messages to a web service as a result of a Subscribe operation).
Messages inserted by the WS-Notification service are of the JMS BytesMessage type, so when a web service invokes the Notify operation against a WS-Notification service point, the application content of the message is inserted into the body of a JMS BytesMessage by using the UTF-8 encoding.
For messages received by the WS-Notification service in response to a subscription the reverse conversion is applied. The received message is converted to the appropriate JMS message type. If the appropriate type is determined to be a BytesMessage type, then the body of the message is converted to a string by using the UTF-8 encoding and proceeds through the code for checking before being sent to the requesting web service.
If the converted BytesMessage string does not contain an XML element when converted to a string then this message is ignored as having been originated by a non WS-Notification aware (JMS) application.
If the received message is determined to be a TextMessage then the body content of the message is extracted and processing proceeds in the same way as for the converted BytesMessage content. This means that JMS applications that want to provide event notifications to a WS-Notification application can choose to send the content as either a BytesMessage or a TextMessage depending upon which is more convenient to the application.
If the received message is neither a BytesMessage nor a TextMessage then it is discarded as having been originated by a non WS-Notification aware (JMS) application.