Oracle Web Services Manager Architecture (OWSM)
Oracle Web Services Manager (OWSM) is component of Oracle SOA Suite . This component is used to secure Web Services and to monitor activities performed on protected Web Services.
Architecture of OWSM
Oracle Web Service Manager consist of following components
A) Policy Enforcement Points (PEP) – Agents and Gateway
B) OWSM Policy Manager
C) OWSM Monitor
D) OWSM Control
E) OWSM Database
A. Policy Enforcement Points (PEP)– PEP are used to manage and enforce security of Web Services. Two type of PEPs are
i) OWSM Gateway – Gateways are deployed on J2EE container and acts as proxy to Web Service Client.
ii) OWSM Agents– These are further subdivided in to two kind Client Agent & Server Agent.
Client Agent intercept request from Web Service Client and enforces policy steps like encryption or signatures.
Server Agent intercept web service request before it reaches to protected web service and enforces access control like authentication and authorization.
B. OWSM Policy Manager– This component is installed on J2EE container and used for Web Service Registration, Policy Configuration and Policy Communication. OWSM manager uses OWSM database to store policies and upload it to all PEPs (Agents and Gateways)
C. OWSM Policy Monitor– This further consist of two components Collector and Aggregator. Collector collect information from PEP and Aggregator applies aggregation rules so that information can be defined in graphical format. OWSM Policy monitor manages collection and aggregation of data for monitoring Web Service Traffic.
D. OWSM Control – This is Web Based console to administer OWSM (Oracle Web Services Manager) components like Policy Manager and Policy Monitor.
E. OWSM Database – This is used to store policy data, monitoring data and system configuration.
URL for Oracle WSM Control is http ://hostname.domainname:port/ccore
Username & Password for ccore (owsm) is admin/oracle (This is different from other SOA comnponent where username is oc4jadmin)