Automating the Testing of SOA Composite Applications

Managing SOA Composite Applications 8-45

2. Click AttachDetach To.

If multiple services or components are available, you are prompted to select the service or component for which to perform the attachment or detachment.

3. Select the component to which to attach or detach a policy.

This invokes a dialog for attaching or detaching policies. Currently attached policies appear in the Attached Policies section. Additional policies available for attachment appear in the Available Policies section. 8-46 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 4. Select policies to attach that are appropriate to your environment.

5. Click Attach.

The attached policy appears in the Attached Policies section. 6. Attach additional policies as needed.

7. When you are finished attaching policies, click Validate.

8. If an error message appears, make the necessary corrections until you no longer have any validation errors.

9. Click OK.

The attached policy is displayed in the policies table. Managing SOA Composite Applications 8-47 For more information about policies, see the following documentation: ■ Section 1.4.3.2, Introduction to Policies ■ Oracle Fusion Middleware Security and Administrators Guide for Web Services for definitions of available policies and details about which ones to use for your environment

8.8.1 WS-RM Sessions

Multiple requests from Oracle SOA Suite in a single WS-RM session are not currently supported. Each request is in an individual WS-RM session.

8.8.2 Policy Attachments and Local Optimization in Composite-to-Composite Invocations

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 SOAPnormalized 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:

1. In the navigator, expand the WebLogic Domain folder.

2. Right-click WLS_SOAWC, and select Web Services Policies.

3. Select a policy and click Export to File.

4. 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. 8-48 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ check-identity: If a JAAS subject exists in the current thread, local optimization is used. Otherwise, local optimization is not used. For information on the default local optimization settings for security policies, see Oracle Fusion Middleware Security and Administrators Guide for Web Services. You can override the local optimization setting for a policy by adding the oracle.webservices.local.optimization property in the binding section of the composite.xml file. The following values are supported: ■ true default value: Local optimization is used, and the policy is applied if it is applicable to optimized calls details are defined in the individual policy file. ■ false: Local optimization is not used, regardless of the default setting for the local-optimization property at the OWSM policy level. This setting forces the policy to be applied. For example, the following setting of false causes oraclewss_username_ token_client_policy to be applied. binding.ws port=http:xmlns.oracle.comCalledBPELProcessApp_ jwsCalledBPELProcessCalledBPELProcesswsdl.endpointcalledbpelprocess_client_ epCalledBPELProcess_pt location=http:sta00634.us.oracle.com:8001soa-infraservicesdefaultCalledBPEL Process1.0calledbpelprocess_client_ep?WSDL wsp:PolicyReference URI=oraclewss_username_token_client_policy orawsp:category=security orawsp:status=enabled wsp:PolicyReference URI=oraclelog_policy orawsp:category=management orawsp:status=enabled property name=oracle.webservices.local.optimizationfalseproperty binding.ws

8.9 Exporting a Running SOA Composite Application

You can export the contents of a running SOA composite application to an archive JAR file. The file can include some or all of the following data: ■ The original design-time composite ■ Postdeployment changes in the rules dictionary and domain value maps DVMs ■ Postdeployment property changes such as binding component properties, composite properties such as audit level settings and payload validation status, and policy attachments To export a running SOA composite application: 1. Go to the home page of the SOA composite application to export. Notes: ■ SOA composite application exporting is currently only allowed at the individual SOA composite level. ■ Shared metadata is not exported as part of the composite export SOA archive SAR.