WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Writing a WS-Notification application that does not expose a Web service endpoint

Write a J2EE application that can be run outside of the application server to make Web service invocations against an external Web service. This application acts as a lightweight publisher, or a pull type consumer by invoking Web service operations against another Web service such as the NotificationBroker provided by WebSphere Application Server.

Before you begin
This task assumes that you have the following resources:
About this task
To write a WS-Notification application that does not expose a Web service endpoint, follow the method provided by your tooling for creating a Web service implementation from a WSDL file. The following steps follow the method provided by Rational Software Architect:

Procedure

  1. Get the WSDL for the service that you wish to invoke. If the target service is the notification broker inbound service that was generated by WebSphere Application Server, use the administrative console to navigate to Service integration > Web services > WS-Notification services > [Content Pane] service_name > [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file or Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file, then use the publish WSDL files property to export the template WSDL for this inbound service to a ZIP file.
  2. Create a Dynamic Web Project with a name of your choice.
  3. Choose File > New > Other > Web services > Web services Client.
  4. Select Java Proxy.
  5. Enter or select the WSDL you obtained earlier.
  6. Choose a Client Type of "Application Client" or "Java" depending upon your requirements.
  7. Select your required security configuration.
  8. Click Finish.
  9. Use the generated proxy and stubs to make calls against the remote Web service. For detailed coding examples, see Developing applications that use WS-Notification.
What to do next
You are now ready to deploy the application for use in the J2EE application client container as described in Running application clients.
Related tasks
Writing a WS-Notification application that exposes a Web service endpoint
WS-Notification - publish and subscribe messaging for Web services
Learning about WS-Notification
Securing WS-Notification
Related reference
Example: Subscribing a WS-Notification consumer
Example: Pausing a WS-Notification subscription
Example: Publishing a WS-Notification message
Example: Creating a WS-Notification pull point
Example: Getting messages from a WS-Notification pull point
Example: Registering a WS-Notification publisher
Example: Notification consumer Web service skeleton
Sharing event notification messages with other bus client applications
WS-Notification roles and goals
WS-Notification troubleshooting tips

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjwsn_task_adev2.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)