Web Services Manager

From Oracle FAQ
Jump to: navigation, search

Oracle Web Services Manager (WSM) is a solution for securing and managing service-oriented architectures (SOA) by allowing enterprises to control and visualize their SOA deployments.

WSM allows IT managers to centrally define policies that govern web services operations such as access control (authentication, authorization), logging, and content validation, and then attach these policies to one or multiple web services, with no modification to existing web services required. In addition, Oracle WSM collects runtime data to monitor access control, message integrity, message confidentiality, quality of service (defined in service-level agreements) and displays that information in graphical charts.

Contents

[edit] History

Oracle WSM was formerly called Oblix COREsv. Oblix was acquired by Oracle in March 2005.

[edit] Licensing

Oracle WSM ships both as a standalone product running on Oracle Application Server and as part of the Oracle SOA Suite.

This is changed in 11g. WSM not shipped as standalone product since October 2009. In 11g WSM is bundled as part of Weblogic Server, and WSM gateway component is not available.

[edit] Key features

  • Centralized gateway for all web service requests
  • Policy Manager
  • Policy Enforcement
  • Monitoring Dashboard

[edit] Network traffic

Inbound traffic: WSM gateways support the reception of both SOAP messages and standard XML message requests over HTTPS, JMS and MQ. HTTPS is enabled by default and cannot be disabled.

Outbound traffic: When configuring the outgoing transport protocol (protocol on which the Web service is invoked) you need specify one of the following protocols: HTTP, HTTPS, JMS, MQ, or even a custom protocol.

Load balancing: Inbound traffic can be load balanced to more than one WSM gateway. This provides fail-over support and greater scalability.

[edit] External links