Database Reference
In-Depth Information
Managing OWSM policies at runtime
In this section, we will discuss how to manage OWSM policies at runtime.
Attaching and removing policies
As an administrator, you have a number of options available to attach/remove
OWSM-based security policies to web service components deployed in your in-
frastructure. If you have a standard web service available inside a WAR applic-
ation, policies can be attached to it from even the Oracle WebLogic Server Ad-
ministration Console. For SOA composites, from Oracle Enterprise Manager Fu-
sion Middleware Control, you can navigate to the particular service, component,
or reference and attach a predefined or custom policy to them. Then, you have
your reliable friend, that is, WLST, which offers handy and convenient ways to list,
attach, detach, enable, and/or disable security policies for your service artifacts.
Having said this, the question on which you can deliberate is when to use which
approach. If you like scripting things out once and then applying them whenever
and wherever you like, WLST would be the ideal choice for you. If you prefer us-
ing web-based configuration screens, you have the WebLogic Server and Fusion
Middleware consoles at your disposal. In this section, you will learn to exercise all
the available options.
Attaching/removing OWSM policies to composite artifacts
Policies can be attached to services or references at runtime through Oracle En-
terprise Management Fusion Middleware Control. Even after attaching them, they
can be enabled and/or disabled, giving you complete flexibility, at runtime, on
whether you want the policies to take effect or not. The following steps demon-
strate how to attach a client policy to a reference of an already deployed compos-
ite:
1.
Log in to Oracle Enterprise Manager Fusion Middleware Control and navigate
to your deployed composite that you want to secure with OWSM.
