Predefined SOA Composites Oracle Fusion Middleware Online Documentation Library

25-2 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager

25.1 Creating New SOA Composites

To create a new SOA composite that can be used as an approval process, you must perform the following steps: 1. Creating a New SOA Composite 2. Deploying a SOA Composite in Oracle SOA Server 3. Prerequisites for Communication to Oracle Identity Manager Through SSL Mode 4. Registering a SOA Composite with Oracle Identity Manager

25.1.1 Creating a New SOA Composite

To use a SOA composite as an approval process, it must adhere to certain standards. These standards ensure that the request service is able to instantiate and manage such composites correctly. These standards are: ■ The following attributes are mandatory for BPEL process: – RequestID of type String – RequestModel of type String – RequestTarget of type String – URL of type String – RequesterDetails of XML Element – BeneficiaryDetails of XML Element – ObjectDetails of XML Element – OtherDetails of XML Element The RequestID, RequestModel, RequestTarget, and URL attributes are always set with valid values for all types of requests. RequesterDetails is an XML element. This element is filled up with valid values for all requests that requires authentication. Requester details is empty for the requests of type Self-Register User because the requester is anonymous user. BeneficiaryDetails is an XML element. This element is filled up with valid values for all requests that have a beneficiary, for example, Provision Resource and Assign Roles. This is filled up only if the request is associated with single beneficiary. If the request is associated with multiple beneficiaries, then BeneficiaryDetails is empty. BeneficiaryDetails element always has valid value for simple requests and child requests that have a beneficiary. Therefore, it is recommended to use this XML element in SOA composites that are used as approval processes at the operational level of approval. This is because at the operational level of approval, the request is associated with only one beneficiary. ObjectDetails is an XML element. This element is filled up with valid values for all requests that are associated with the Resource entity. This is filled up only if the request is associated with single resource. If the request is associated with multiple resources, then ObjectDetails is empty. The ObjectDetails element always has valid value for simple and child requests that are associated with resource. Therefore, it is recommended to use this XML element in SOA composites that are used as approval processes at the operational level of approval. This is because at the operational level of approval, the request is associated with only one resource. Developing SOA Composites 25-3 ■ All the attributes that are mandatory for the BPEL process are referred from RequestDetails.xsd and ApprovalProcess.xsd. These files are present in the template SOA composite, which must not de modified or deleted. Oracle Identity Manager provides a helper utility for creating custom SOA composites. This utility creates a template SOA project that adheres to all the necessary standards. This utility is located in the OIM_HOMEworkflowsnew-workflow directory. To create a custom SOA composite by running the helper utility: 1. Run the following commands: cd OIM_HOMEworkflowsnew-workflow ant -f new_project.xml 2. Enter the JDeveloper application name when the following prompt is displayed: Please enter application name 3. Enter the JDeveloper project name when the following prompt is displayed: Please enter project name 4. Enter the name of the ADF binding service for the composite when the following prompt is displayed: Please enter the service name for the composite. This needs to be unique across applications The new application is created in the OIM_HOMEworkflowsnew-workflowprocess-template directory. You can open the new application in JDeveloper for modification. Human task in the template SOA composite is configured to send notifications to the assignee of the human task. In the custom composite that is created, the notification message can be modified based on the requirement. All the notifications to be sent to the approver must be configured in the SOA composite. For configuring Oracle SOA server to send notifications, refer to Configuring Oracle User Messaging Service in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite. Human task in the template SOA composite is configured to be assigned to the SYSTEM ADMINISTRATORS role.

25.1.2 Deploying a SOA Composite in Oracle SOA Server

For information about deploying the workflow composite in BPEL, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Note: ■ JAVA_HOME environment variable must be set before running this utility. ■ This utility requires Apache Ant version 1.7 or later.