Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Bus enabled web services > Enable web services through the service integration bus > Configure web services for a service integration bus
Work 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.
If we have a web services gateway running on a WAS v5.1 application server that is part of a network deployment cell, and to migrate the cell from a v5.1 to a v6 dmgr, first preserve the gateway configuration as described in Preserving a v5.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 Enable web services through the service integration bus.
Before you can work with the web services gateway 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 Configure 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 admin console are only available in WAS Network Deployment if you are working with a dmgr profile. The panels are not available in a WAS Network Deployment stand-alone server profile. The gateway administrative commands are available in WAS Network Deployment under both the stand-alone and dmgr profiles. For more information see Web services gateway troubleshooting tips.
In WAS 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. 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 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 admin console, or from the command line.
Tooling is also provided to migrate an existing gateway configuration from WAS v5.1.
Detailed instructions on how to enable web services through the gateway are provided in the following tasks:
Procedure
- Web services gateway.
- Create a new gateway instance.
- Create a new gateway service configuration.
- Create a new proxy service configuration.
- WSGateway command group .
- Preserving a v5.1 gateway when migrating a cell.
- Migrate a v5.1 Web services gateway configuration.
- Web services gateway troubleshooting tips.
Web services gateway: Frequently asked questions
What is new and changed: Web services gateway
Web services gateway
Related
Specifications and API documentation