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 you can use it 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.1 application server that is part of a network deployment cell, and you want to migrate the cell from a Version 5.1 to a Version 6 deployment manager, first preserve the gateway configuration as described in Preserving a Version 5.1 gateway when migrating a cell.

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 the service integration bus.

Before you can work with the web services gateway you must Plan your bus-enabled web services installation, ensure that every stand-alone server or cluster that is to play a bus-enabled web services role is a member of a service integration bus (refer to Configuring the members of a bus) and create a Service Data Objects (SDO) repository on every stand-alone server or cluster that is to play a bus-enabled web services role.

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 stand-alone server profile. The gateway administrative commands are available in WebSphere Application Server Network Deployment under both the stand-alone 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 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 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 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.1.

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

Procedure




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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 30, 2014 9:17:32 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=twsg_ep
File name: twsg_ep.html