Administer the bus-enabled web services resources

Use the administrative console to configure the main service integration bus-enabled web services resources: endpoint listeners; JAX-RPC handler lists; WS-Security bindings and configurations; references to UDDI registries.

When we configure a bus-enabled web service you associate it with one or more of the following resources:

• The endpoint listeners on which we want the service to be available.

• Any JAX-RPC handler lists that apply to the service.

• Any WS-Security bindings and configurations that apply to the service.

• Any references to UDDI registries in which entries for the service are created.

You choose each of these resources from a list of resources that we have previously configured.

Use the administrative console to administer the bus-enabled web services resources as described in the following topics:

Subtopics

• Create a new endpoint listener configuration
  An endpoint listener is the point (address) at which messages for an inbound service are received. The endpoint listeners that are supplied with WebSphere Application Server support SOAP over HTTP and SOAP over JMS bindings.
• Work with JAX-RPC handlers and clients
  The Java API for XML-based remote procedure calls (JAX-RPC) provides you with a standard way of developing interoperable and portable web services. Use JAX-RPC handlers, handler lists and client applications with your service integration bus-enabled web services.
• Work with mediations
  Use a mediation to change the content of a message, or the way in which a message is handled.
• Create a new UDDI reference
  Create a reference (a pointer) to a UDDI registry for use with service integration bus-enabled web services.

Configure secure transmission of SOAP messages using WS-Security