Oracle Socket Adapter Configuring Properties for Oracle JCA Adapters

35-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite To manage binding component policies: 1. Access this page through one of the following options: The list of currently deployed SOA composite applications appears.

2. In the Composite list, select an application.

The Dashboard page for the selected SOA composite application appears. The Services and References section of this page displays the binding components being used in the application.

3. In the Services and References section, select a service or reference.

4. Click Policies.

The Policies page enables you to view the globally-attached and directly-attached policies, and to detach or detach security policies to and from a service or reference binding component: ■ The Globally Attached Policies table displays the globally-attached policy name, the policy set, the category Management, Reliable Messaging, MTOM Attachment, Security, or WS Addressing, the violations since the SOA Infrastructure was last restarted, and the authentication, authorization, confidentiality, and integrity failures since the SOA Infrastructure was last restarted. Policy sets provide a means to attach policies globally to a range of endpoints of the same type. Attaching policies globally using policy sets enables an administrator to ensure that all subjects are secured in situations in which the developer, assembler, or deployer did not explicitly specify the policies to attach. Policies that are attached using a policy set are considered externally attached. For information about creating and managing policy sets, see chapter Creating and Managing Policy Sets of Oracle Fusion Middleware Security and Administrators Guide for Web Services. ■ The Directly Attached Policies table displays the directly-attached policy name, the policy reference status enabled or disabled, the category, the violations since the SOA Infrastructure was last restarted, and the authentication, authorization, confidentiality, and integrity failures since the SOA Infrastructure was last restarted. Note: Before attaching policies, see Oracle Fusion Middleware Security and Administrators Guide for Web Services for definitions of available policies and details about which ones to use in your environment. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Home. 2. Select the Deployed Composites tab. 3. In the Composite section, select a specific SOA composite application. 1. Under soa-infra, select a specific SOA composite application. Managing Service and Reference Binding Components 35-3

5. In the Directly Attached Policies section, click AttachDetach.

If multiple components are available, you are prompted to select the service or component for which to perform the attachment or detachment. 6. Select the service or component to which to attach or detach a policy. This invokes a dialog for attaching or detaching policies. Policies currently attached appear in the Attached Policies section. Additional policies available for attachment appear in the Available Policies section. 7. Select policies to attach that are appropriate to your environment.

8. Click Attach.

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

10. If an error message appears, make the necessary corrections until you no longer have any validation errors. The attached policy is displayed in the policies table.

11. Click OK.

Note: If you attach a policy to a service binding component client and initiate an instance of the SOA composite application in the Test Web Service page, and the policy attachment fails, an Oracle Web Services Manager OSWM policy error is not generated and viewable in Oracle Enterprise Manager Fusion Middleware Control. If the same SOA composite application instance is initiated externally, a policy error is generated and viewable in Oracle Enterprise Manager Fusion Middleware Control. For service components such as a BPEL process or reference binding components, the policy error is always generated and viewable, regardless of whether the application instance was initiated externally or internally through the Test Web Service page.