WAS v8.5 > Administer applications and their environment > Administer web services - Notification (WS-Notification) > Use WS-Notification for publish and subscribe messaging for web services > Configure WS-Notification resources > Configure WS-Notification resources

Publishing the WSDL files for a WS-Notification application to a compressed file

Use the dmgr console to download a compressed file with a .zip file extension containing the published WSDL files for a WS-Notification application.

The ability to publish these WSDL files to a compressed file is particularly useful in the following circumstances:

• 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 v7.0 services, or the inbound service for v6.1 services.

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 we 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 running 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

1. Start the dmgr console.
2. cd "Publish WSDL files to .zip file [Settings]" form for the WS-Notification application.

   For JAX-WS based v7.0 WS-Notification services, click one of the following paths:

   • Service integration -> WS-Notification -> Services -> service_name -> [Additional Properties] WS-Notification service points -> point_name -> [Additional Properties] Publish WSDL files to zip
   • Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Additional Properties] WS-Notification service points -> point_name -> [Additional Properties] Publish WSDL files to zip

   For JAX-RPC based v6.1 WS-Notification services, click one of the following paths:

   • Service integration -> WS-Notification -> Services -> service_name -> [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file
   • Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Related Items] Notification broker inbound service settings > [Additional Properties] Publish WSDL files to ZIP file

3. Click on the file name to download a zip file containing the application's published WSDL files.
   

Related concepts:

WS-Notification

Related

Create a new v7.0 WS-Notification service
Create a new v6.1 WS-Notification service
Create a new v7.0 WS-Notification service point
Create a new v6.1 WS-Notification service point
Create a new WS-Notification administered subscriber
Create a new WS-Notification permanent topic namespace
Applying a WS-Notification topic namespace document
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Modify a v7.0 WS-Notification service point
Writing a WS-Notification application that does not expose a web service endpoint
Develop a JAX-WS client from a WSDL file
Providing access for WS-Notification applications to an existing bus topic space
Configure a WS-Notification service for use only by WS-Notification applications

Reference:

WS-Notification troubleshooting tips
wsimport command for JAX-WS applications
createWSNServicePoint command

Related information:

Configure JAX-WS handlers

+

Search Tips   |   Advanced Search