Use the administrative console to configure individual WS-Notification services, service points, administered subscribers, permanent topic namespaces, topic namespace documents and JAX-WS handlers.
Decide which method to use to configure these resources. You can configure WS-Notification resources by using the administrative console as described in this task, or by using the commands in the WSNotificationCommands command group for the AdminTask object.
WS-Notification enables web services to use the publish and subscribe messaging pattern. For more information, see WS-Notification: Overview and WS-Notification.
For high-level configuration of WS-Notification, see Accomplishing common WS-Notification tasks. Use the steps for this task to configure individual instances of each type of WS-Notification resource.
To configure specific WS-Notification resources, use the administrative console to complete any of the following tasks:
Create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. Use this type of service if you want to compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or if you want to apply JAX-WS handlers to your WS-Notification service. This is the recommended type of service for new deployments. This WS-Notification option has been available in WebSphere Application Server from Version 7.0.
Create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. Use this type of service if you want to expose a JAX-RPC WS-Notification service that uses the same technology provided in WebSphere Application Server Version 6.1, including the ability to apply JAX-RPC handlers to the service. This WS-Notification option has been available in WebSphere Application Server from Version 6.1.
You can add an additional Version 7.0 WS-Notification service point to an existing Version 7.0 WS-Notification service. A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service. The existence of a WS-Notification service point on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.
You can add an additional Version 6.1 WS-Notification service point to an existing Version 6.1 WS-Notification service. A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service. The existence of a WS-Notification service point on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.
As part of the configuration of a WS-Notification service point you can configure any number of administered subscribers for that service point. An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.
Create a new permanent topic namespace. A topic namespace is a grouping of topics that allows information to be shared between applications. You use a permanent topic namespace to statically define the association between a WS-Notification topic namespace URI and a service integration bus topic space destination.
A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace. Use the administrative console to apply a topic namespace document to an existing topic namespace.
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.
A JAX-WS handler is a Java class that performs a range of handling tasks. For example: logging messages, or transforming their contents, or terminating an incoming request. You can create JAX-WS handlers, chain them together in the form of a handler list, then apply the handler list to a JAX-WS based Version 7.0 WS-Notification service point (for inbound invocation handling) or WS-Notification service (for outbound invocation handling).
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |