WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Telecom Web Services Access Gateway

The Telecom Web Services Access Gateway provides policy-driven traffic monitoring, message capture, authorization, and management capabilities. These services are provided at the application layer, and is enforced for each Web service request using knowledge of the requester, target service, and invoked operation.

The Access Gateway provides flexibility for the construction of tailored message processing logic, in accordance with your enterprise's network policies. This logic can be customized to meet your network requirements.

All Web service requests and responses pass through and are inspected by the Access Gateway. It acts as an intermediary for all communications between client and service endpoints by processing both incoming and outgoing requests. Mediation primitives within the Access Gateway have access to the SOAP message in its entirety in the form of a Service Message Object (SMO), including headers and body. This allows mediation primitives to determine the initiating requester, target service, and invoked operation. In addition, policy data is passed between mediation primitives in the form of additional XML elements within the SOAP header.

The Access Gateway extends WebSphere® ESB by adding policy-driven processing elements and new components to monitor Web service traffic. Using WID tooling, you can model your network policies, enable new features, and deploy customized logic into the Access Gateway.

The Access Gateway exchanges data with Service Platform applications and Web service implementations that connect to the network; it interacts with the Service Policy Manager, with the user registry, and with your applications.

Configuration options

The Access Gateway now runs co-resident with WebSphere Enterprise Service Bus, version 6.2.0.2 or 7.0.0.1. It also provides Performance Monitoring Infrastructure (PMI) metrics for support.The following are the Access Gateway supported metric types:
  • Startup Time Metrics on a per service context
  • Successful and failed incoming request counts
  • Authorized or denied request counts
Note: If you are running WebSphere Application Server version 6.1.0.29, the TWSS Access Gateway can coexist in the same cluster with the Service Platform components. However, when the Service Platform components are deployed in a cluster running WebSphere Application Server version 7.0.0.7, the Access Gateway must be deployed in a separate cluster.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.