Policy Attachments and Local Optimization in Composite-to-Composite Invocations in Oracle SOA Suite:
OWSM supports an Oracle SOA Suite local optimization feature for composite-to-composite invocations in which the reference of one composite specifies a web service binding to a second composite. Local optimization enables you to bypass the HTTP stack and SOAP/normalized message conversions during runtime. Local optimization is not used if the composites are in different containers. If a policy is attached to the web service binding, the policy may not be invoked if local optimization is used.By default, an OWSM security policy includes a local-optimization property that identifies if the policy supports local optimization. You can view the setting for a policy in Oracle Enterprise Manager Fusion Middleware Control.
To view the local optimization setting for policies:
- Login to EM console.
- In the navigator, expand the WebLogic Domain folder.
- Right-click on the Domain, and select Web Services > Policies.
- Select a policy and click Export to File.
- Open the file with a text editor and search for local-optimization to identify the value. This property supports the following values:
- on: Local optimization is used in the attached policy, and the policy is not applied at runtime.
- off: Local optimization is not used in the attached policy, and the policy is applied at runtime.
- check-identity: If a JAAS subject exists in the current thread, local optimization is used. Otherwise, local optimization is not used.
Local optimization is not used (the
value for local-optimization is specified as off) for the policy oracle_wss_username_token_service_policy,
the policy will be applied at runtime even though the Local Optimization is
enabled.
Local optimization is used (the value
for local-optimization is specified as on) for the policy oracle_wss11_message_protection_service_policy,
the policy will not be applied at runtime when the Local Optimization is
enabled.
No comments:
Post a Comment