Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Notification (WS-Notification) > Develop applications that use WS-Notification

Example: Registering a WS-Notification publisher

Use this task to write the code for a subscriber client application that can subscribe a consumer application with a broker, based on the example code extract provided.

This example is based on using the Java API for XML-based remote procedure calls (JAX-RPC) APIs with code generated by using the WSDL2Java tool (run against the Notification Broker WSDL generated as a result of creating your WS-Notification service point) and WAS APIs and SPIs.

In WAS there are two implementations of the WS-Notification service: v6.1 and v7.0. This JAX-RPC example can interact successfully with v6.1 or v7.0 WS-Notification service points. However to use WS-Notification with policy sets, for example to enable composition with WS-ReliableMessaging, then your WS-Notification applications must be encoded to use the Java API for XML-based Web Services (JAX-WS) programming model and must interact with v7.0 WS-Notification service points. If you are new to programming JAX-WS client applications, see the following topics:

• JAX-WS

• JAX-WS client programming model

• Implement static JAX-WS web services clients

• Write JAX-WS applications for WS-Notification

• Web services hints and tips: JAX-RPC versus JAX-WS, Part 1

To write the code for a subscriber client application that can subscribe a consumer application with a broker, complete the following steps, referring to the example code extract for further information.

Procedure

1. Look up the JAX-RPC service. The JNDI name is specific to your web services client implementation.
2. Get a stub for the port on which to invoke operations.
3. Create a reference for the publisher (producer) being registered. This contains the address of the producer web service.
4. Create a list (array) of topic expressions to describe the topics to which the producer publishes messages.

5. Indicate that you do not want the publisher to use demand based publishing.

6. Set a value for the initial termination time of the registration. For example, you could set a value 1 year in the future.
7. Create holders to hold the multiple values returned from the broker:
   • PublisherRegistrationReference defines the endpoint reference for use in lifetime management of the registration.
   • ConsumerReference defines the endpoint reference for use in subsequent publishing of messages.

8. Invoke the RegisterPublisher operation by calling the associated method on the stub.
9. Retrieve the PublisherRegistrationReference.
10. Retrieve the ConsumerReference.

Example

The following example code represents a JAX-RPC client acting in the publisher registration role, registering a publisher (producer) application with a broker.

// Look up the JAX-RPC service. The JNDI name is specific to your web services client implementation InitialContext context = new InitialContext();
javax.xml.rpc.Service service = (javax.xml.rpc.Service) context.lookup(
    "java:comp/env/services/NotificationBroker");

// Get a stub for the port on which to invoke operations NotificationBroker stub = (NotificationBroker) service.getPort(NotificationBroker.class);

// Create a reference for the publisher (producer) being registered. This contains the address of the // producer web service.
EndpointReference publisherEPR =
    EndpointReferenceManager.createEndpointReference(new URI("http://myserver.mysom.com:9080/Producer"));

// Create a list (array) of topic expressions to describe the topics to which the producer publishes
// messages. For this example you add one topic Map prefixMappings = new HashMap();
prefixMappings.put("abc", "uri:mytopicns");
TopicExpression topic =
    new TopicExpression(TopicExpression.SIMPLE_TOPIC_EXPRESSION, "abc:xyz", prefixMappings);         
TopicExpression[] topics = new TopicExpression[] {topic};

// Indicate that you do not want the publisher to use demand based publishing Boolean demand = Boolean.FALSE;

// Set a value for the initial termination time of the registration. For example, set a value 1 year in // the future
Calendar initialTerminationTime = Calendar.getInstance();
initialTerminationTime.add(Calendar.YEAR, 1);

// Create holders to hold the multiple values returned from the broker:
// PublisherRegistrationReference: An endpoint reference for use in lifetime management of // the registration
EndpointReferenceTypeHolder pubRegMgrEPR = new EndpointReferenceTypeHolder();

// ConsumerReference: An endpoint reference for use in subsequent publishing of messages
EndpointReferenceTypeHolder consEPR = new EndpointReferenceTypeHolder();

// Invoke the RegisterPublisher operation by calling the associated method on the stub
stub.registerPublisher(publisherEPR, topics, demand, initialTerminationTime, null, pubRegMgrEPR, consEPR);

// Retrieve the PublisherRegistrationReference
EndpointReference registrationEPR = pubRegMgrEPR.value;

// Retrieve the ConsumerReference
EndpointReference consumerReferenceEPR = consEPR.value;

JAX-RPC
Brokered notification
JAX-RPC
Brokered notification
WS-Notification
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification

Related

WSDL2Java command for JAX-RPC applications
http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-os.pdf
WSDL2Java command
WS-Notification troubleshooting tips
http://www.ibm.com/developerworks/websphere/techjournal/0811_partridge/0811_partridge.html

+

Search Tips   |   Advanced Search