WS Profile through WS Routing

The OSS/J Order Management WS-Profile is based on the Web Service Notification (WSN) standard for event notifications. The common pattern to use the OSS/J Order Management – WS Profile is:

  1. Publish a NotificationConsumer port.

  2. Subscribe for a desired topic to a NotificationProducer port (server side). The response contains data required for later reference to the subscription (subscriptionID).

  3. Send requests to a JVTOrderManagementSession port (server side). Events are potentially published on the application specific topic.

  4. Unsubscribe to a SubscriptionManager port (server side) using the subscription reference that it was given initially.

On its side the server receives requests, fulfilling them and sending events on the application topic, events that are dispatched to the concerned NotificationConsumers. The format of the SOAP message payloads is exactly the same as the JMS Profile except that events are embedded into a Notify operation.

WSN Specific Schema

A simple XML schema is provided at the following location:

$SW_HOME/distrib/kabira/kpsa/xsd/ossj/FP-WebServiceNotification-v1-0.xsd

This schema defines a subscriptionID element that is used by the WS Routing component as a WS-Addressing Reference Parameter, which is a standardized element specified by the WS-Addressing specification.

Deployment Example

A deployment example is provided at the following location: 

$SW_HOME/distrib/kabira/kpsa/samples/ca/ossjomws
The example contents are as follows:
File Description
README Self description file
pom_dl_deps.xml A Maven pom to ease dependency downloading
jetty-admin.ksh

A KSH script which setup a Jetty web server instance with the WS Routing component and starts it