To manage BPMN process service component policies:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPMN.	Select soa-infra. Right-click and select Service Engines > BPMN.

2. Go to the Composites column of the View table and select a specific SOA composite application to access its Dashboard page.

3. Click Policies.

   The Policies page enables you to attach and detach policies to and from BPMN process service components. The policies table displays the attached policy name, the policy reference status (enabled or disabled) that you can toggle, the category (Management, Reliable Messaging, MTOM Attachment, Security, or WS Addressing), the violations, and the authentication, authorization, confidentiality, and integrity failures since the SOA Infrastructure was last restarted.

   
   Description of the illustration bpmn_se_policies.png

4. Click Attach/Detach.

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

5. 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.

6. Select to attach policies appropriate to your environment.

7. Click Attach.

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

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

10. Click OK.

    The attached policy is displayed in the policies table.

For more information, see the following documentation:

• Introduction to Policies

• Managing SOA Composite Application Policies for the dialogs that display during policy attachment.

• Administering Web Services for definitions of available policies and details about which ones to use for your environment.

Recoverable activities are activities that failed and can be recovered. For example, if you are using the file adapter to initiate an asynchronous BPMN process and your system crashes while the instance is processing, you can manually perform recovery when the server restarts to ensure that all message records are recovered.

To perform BPMN process service engine message recovery:

1. Access this page through one of the following options:

   From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...
   Select Service Engines > BPMN.	Right-click soa-infra. Select Service Engines > BPMN.

2. Click Recovery.

   The Recovery page displays the following details:

   • A utility for searching for a specific message failure by specifying criteria and clicking Search. Click the Help icon for details.

   • Message failure in the service engine, including the conversation ID, whether you can recover from the message failure, the service component and composite application in which the failure occurred, and the time at which the fault occurred.

   
   Description of the illustration bpmn_se_recovery.png

3. Select a fault in the table.

4. Select one of the following options:

   Action	Description
   Recover	Retries the message in which the fault occurred. If an asynchronous BPMN process encounters a transaction rollback scenario because of any underlying exception error, it rolls back to the last dehydration activity. If this is a new instance, and a receive activity was the first dehydration activity, the BPMN process service engine creates a recoverable invoke. When you click Recover to recover the invoke, the service engine creates a new instance. This instance may run to completion with no exception error. However, you continue to see the older instance identified as faulted.
   Mark Cancelled	Marks the message so it is never delivered.

Once a message is submitted for recovery, the BPMN process service engine may take time to complete the action. This typically takes less than several seconds. During this time, the message remains visible in the Recovery page. Duplicate attempts to recover the same message in that period are ignored. Refresh the page every few seconds to receive the latest recovery status.