Publishing the WSDL files for a WS-Notification application to a compressed file
Use the administrative console to download a compressed file with a .zip file extension that contains the published WSDL files for a WS-Notification application.
About this task
- Writing a WS-Notification application that invokes web service operations against the NotificationBroker application, as described in Writing a WS-Notification application that does not expose a web service endpoint.
- Running the wsimport command against the exported PublisherRegistrationManager.wsdl file to generate a client stub for the PublisherRegistrationManager.
- Viewing the endpoint URLs to which WS-Notification applications connect, by looking in the WSDL file for the NotificationBroker application for Version 7.0 services, or the inbound service for Version 6.1 services.
Note:
When you run the wsimport command against the exported PublisherRegistrationManager.wsdl file you must include the ibm-wsn-jaxws.xml file as an argument to wsimport. If you omit this bindings file, the wsimport command fails with a naming conflict error concerning the ResourceNotDestroyedFault elements referred to in the PublisherRegistrationManager.wsdl file. For more information about why this exception occurs, see the following troubleshooting tip: The PublisherRegistrationManager.wsdl file is not successfully parsed by wsimport unless you include a JAX-WS bindings file.
The ibm-wsn-jaxws.xml file is located in the app_server_root/util directory. For example: c:\was\util\ibm-wsn-jaxws.xml. This bindings file expects to find the WSDL file to which it refers in the same directory as itself, so before you run the wsimport command you must copy the bindings file to the directory that holds your PublisherRegistrationManager.wsdl file. Here is an example of how to run the wsimport command to include the ibm-wsn-jaxws.xml file:
c:\was\bin\wsimport -b ibm-wsn-jaxws.xml -keep PublisherRegistrationManager.wsdl