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

Working with the Web services gateway

If you have a Web services gateway running on a WebSphere Application Server Version 5 application server that is part of a network deployment cell, and you want to migrate the cell from a Version 5 to a Version 6 deployment manager, first preserve the gateway configuration as described in Co-existing with previous gateway versions.

When you install WebSphere Application Server , the installation program does not install the service integration bus Web services enablement (SIBWS) and associated applications (including the Web services gateway). Before you can work with the Web services gateway, complete the installation of the SIBWS.

The gateway panels in the administrative console are only available in WebSphere Application Server Network Deployment if you are working with a deployment manager profile. The panels are not available in a WebSphere Application Server Network Deployment standalone server profile. The gateway administrative commands are available in WebSphere Application Server Network Deployment under both the standalone and deployment manager profiles. For more information see Tips for troubleshooting the Web services gateway.

You use a Web services gateway to map an existing target service to a new Web service that seems to be provided by the gateway. The gateway provides you with a single point of control, access and validation of Web service requests, and allows you to control which Web services are available to different groups of Web service users. You can also map multiple target services to a single gateway service, and configure proxy services.

In WebSphere Application Server Versions 4 and 5, the Web services gateway was a separable component with its own user interface. In this version, the gateway is fully integrated with IBM service integration technologies and - although providing similar functionality - has become primarily an administrative entity. It no longer has its own user interface, and it uses IBM service integration technologies for its configuration and run-time support. For more information, see What is new and changed: Web services gateway.

Within each service integration bus you can create multiple gateway instances to partition the total set of gateway and proxy services into logical groups to allow simpler management.

To create and configure gateway instances, you can use the WebSphere Application Server administrative console. For core administrative tasks (for example creating a new gateway service configuration) you can use a set of configuration wizards. These wizards can be accessed from within the administrative console, or through the wsadmin scripting client. Tooling is also provided to migrate an existing gateway configuration from WebSphere Application Server Version 5.

Detailed instructions on how to enable Web services through the gateway are provided in the following tasks:

Related concepts
Web services gateway - frequently asked questions
What is new and changed: Web services gateway
Related tasks
Working with inbound services
Working with outbound services
Related reference
Web services: Resources for learning

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\twsg_ep.html

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