Working with the Web services gateway

Use the Web services gateway to map an existing service - either an inbound or an outbound service - to a new Web service that appears to be provided by the gateway. The gateway acts as a proxy: your gateway service users need not know whether the underlying service is being provided internally or externally. 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.

Before you begin

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.

For a high-level task view of how you configure the Web services gateway as part of an overall bus-enabled Web services configuration, see Enabling Web services through service integration technologies.

Before you can work with the Web services gateway you must install the bus-enabled Web services applications and resources.

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 Web services gateway troubleshooting tips.

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.

About this task

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 from the command line. 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:




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=twsg_ep
File name: twsg_ep.html