Oracle WSM Component Characteristics Oracle WSM Startup and Shutdown Lifecycle

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-51 Figure 5–27 Oracle WSM Single-Instance Architecture

5.8.1.1 Oracle WSM Component Characteristics

The Oracle WSM Agent is a set of .jar files available on every Oracle Fusion Middleware managed server in a Web services stack. Policy Manager is contained in the wsm-pm.ear file. None of the services provided by Oracle WSM are singletons, therefore, it can run in full active-active mode. Oracle WSM services can be validated by http:SOAHOSTx:portwsm-pmvalidator. This validator displays Oracle WSM policies. The Oracle WSM Agent and Oracle Enterprise Manager interact with Policy Manager using the EJB interfaces. The EJBs used in Oracle WSM are stateless and can be deployed in a clustered environment. Therefore, there is no requirement to enable state replication in the cluster. The Oracle WSM Agent and Policy Manager need not be co-located. However, the Agent expects Policy Manager to be deployed on at least one node of the domain. The Oracle WSM Agent has capabilities to auto-discover Policy Managers deployed in the domain. Neither the Oracle WSM Agent nor Policy Manager use JTA or JMS messaging. The MDS-based policy store also does not support JTA. External Dependencies Oracle WSM Policy Manager depends on the following components: ■ MDS repository for storing the policies ■ Oracle WSM Agent depends only on Oracle WSM Policy Manager. Both components must be available for Oracle WSM to start and run properly. WebLogic Server Web Application WebLogic Server Oracle WSM Policy Manager EM Control UI Web Service Client Browser Oracle WSM Agent Oracle WSM Database 5-52 Oracle Fusion Middleware High Availability Guide

5.8.1.2 Oracle WSM Startup and Shutdown Lifecycle

The following key Oracle WSM components are involved in the startup lifecycle for Oracle WSM: ■ Oracle WSM Policy Manager ■ Oracle WSM Agent Policy Manager is a stateless application which does not perform any caching. There is no special application level startup sequence performed when the managed server where Policy Manager is deployed starts up. Policy Manager communicates with the MDS repository to retrieve policies. The MDS repository can be stored in an Oracle RAC database to provide MDS high availability. When a managed server on which an Agent is configured comes up, the Agent connects to Policy Manager to get latest revision of policies. If it succeeds, the changes to the policies are downloaded and cached. Once the Agent is up and running, it periodically attempts a cache refresh at a configurable interval. The default time is every one minute. Oracle WSM Agent communicates with the Policy Manager through EJB invocations over T3 or T3s if SSL is enabled protocol. If Policy Manager is deployed on different nodes and some of them have SSL enabled and others dont, Agent communicates only with the nodes with SSL connections. If the Policy Manager to which the Oracle WSM Agent is connected becomes unavailable, the underlying infrastructure automatically connects to another Policy Manager instance running elsewhere in the cluster. This is achieved through Oracle WebLogic EJB clustering. For high availability scenarios, if an Oracle WSM application is targeted to multiple nodes, it should be targeted to a cluster rather than to individual managed servers. If a managed server has Web services deployed which are protected by Oracle WSM, and the Oracle WSM Agent is not able to communicate with any of the Policy Managers at startup time, Web service invocation fails.

5.8.1.3 Oracle WSM Request Flow