WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Working with outbound services

Why and when to perform this task

How an existing external (target) service is mapped to an outbound service at a service destination. Each message is passed from the outbound service to the target service through an outbound port. A separate outbound port is created for each available binding. You can  apply JAX-RPC handlers and WS-Security settings at the ports.

An outbound service provides access, through one or more outbound ports, to a Web service that is hosted externally. An outbound service can be used by any of your internal systems that can access the service integration bus on which it is hosted.

Requests and responses to an outbound service are sent across any transport binding (for example SOAP over HTTP, SOAP over JMS, EJB binding) that is available to both the target service and the service integration bus. Each available binding type is represented by an outbound port configured at a port destination. For more information, see Outbound ports and port destinations.

You can control and monitor access to the target service in the following ways:

You use the WebSphere Application Server administrative console to work with outbound services. Choose one of the following actions:

Related tasks
Working with inbound services
Publishing a Web service to a UDDI registry

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjw_out.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)