Bus-enabled web services

Use these concepts to explore service integration bus-enabled web services.

Bus-enabled web services: Frequently asked questions
A set of frequently asked questions about service integration bus-enabled web services are collected together in this topic.
Planning your bus-enabled web services installation
Consider how your environment will be configured to support service integration bus-enabled web services. Determine which of the bus-enabled web services roles you want each server to perform.
Endpoint listeners and inbound ports: Entry points to the service integration bus
An endpoint listener is a web service-enabled entry point to one or more service integration buses. An endpoint listener carries requests and responses between web service clients and buses.
Outbound ports and port destinations
A set of outbound ports and associated port destinations provides the mechanism through which an outbound service communicates with the externally-hosted target web service.
Service integration technologies and JAX-RPC handlers
A JAX-RPC 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. Handlers monitor messages at ports, and take appropriate action depending upon the sender and content of each message.
Non-bound WSDL
When developing a client application following best practices, you can develop against a WSDL document that contains only a port type definition, and no specific bindings or port addresses. Such a WSDL document is known as a non-bound WSDL document.
UDDI registries: Web service directories that can be referenced by bus-enabled web services
The Universal Description, Discovery and Integration (UDDI) specification defines a way to publish and discover information about web services. UDDI registries use the UDDI specification to publish directory listings of web services.
SOAP with attachments: A definition
You can associate a SOAP message with one or more attachments in their native format (for example GIF or JPEG) by using a multipart MIME structure for transport.
Operation-level security: Role-based authorization
When you build an EAR file, you can define roles and apply them to methods. When you deploy the EAR file, you can assign individual users or groups to roles.
Service integration technologies and WS-Security