Web services gateway - What is new in this release
The Web services gateway was first released on AlphaWorks on 21 December
2001. Here is a list of the main differences between the AlphaWorks edition
and this version:
- The gateway is now built using enterprise beans. This new construction
supports the Web services gateway only in an application server that has
an EJB container. The gateway no longer runs in the Tomcat server.
- The gateway includes UDDI integration, therefore you can deploy and remove
Web services to a UDDI registry as well as to a Web address.
In addition to the Apache SOAP channel, the
following channels now exist:
- The gateway supports bidirectional interactions (that is, both inbound
and outbound requests) directly, by deploying two instances of each type of
channel. To achieve this configuration with the AlphaWorks version, you deployed
two instances of the Web services gateway; one for inbound communication and
one for outbound communication.
Note:
- Interceptors have been renamed as filters.
- Channels, filters and UDDI references are deployed to the Web services
gateway, then associated with individual Web services. When you configure a Web service, you choose the following entities:
- The channels on which the Web service is available.
- Any filters that apply.
- Any UDDI references to which the Web service is deployed.
Any security bindings that apply.
- You can change the channels, filters, handlers and UDDI references that
are associated with a deployed service without removing the service.
- You can deploy multiple targets for a single service (that is, more than
one implementation of a service that has the same service interface).
You can back
up and restore a gateway configuration.
You can scale
the Web services gateway.
You can configure
the gateway for secure transmission of SOAP messages using tokens,
keys, signatures and encryption in accordance with the emerging Web Services Security (WS-Security)
specification.
- You can set security
(basic authorization) on the individual methods of a Web service, and
on the whole gateway.
- The gateway can invoke
Web services over HTTPS.
You can configure
the gateway to work with authenticating proxies.

Enabling Web services through the Web services gateway
Searchable topic ID:
cwsg_new
Last updated: Jun 21, 2007 4:55:42 PM CDT
WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cwsg_new.html