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

Working with inbound services

Use this topic to make an internal service available as a Web service.

Why and when to perform this task

How a client request is received by an endpoint listener, then passed through an inbound port to an inbound service destination. You can also apply JAX-RPC handlers and WS-Security bindings at the ports.

An inbound service is the Web interface for a service that is provided internally (that is, a service provided by your own organization and hosted so as to be directly available at a service destination). Web service requests and responses to an inbound service can be sent across any binding (for example SOAP over HTTP or SOAP over JMS) that is available to the service integration bus. Each available binding type is represented by an inbound port, and each inbound port is associated with a binding-specific endpoint listener. For more information, see Endpoint listeners and inbound ports - entry points to the service integration bus.

You can control and monitor access to your Web services in the following ways:

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

Related tasks
Working with outbound 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_in.html

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