Developing an Approval Process for Oracle Identity Manager

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. 25-4 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager

25.1.3 Prerequisites for Communication to Oracle Identity Manager Through SSL Mode

If the communication to Oracle Identity Manager is through the SSL mode, then you must: ■ Set the TRUSTSTORE_LOCATION environment variable, where TRUSTSTORE_LOCATION is the trusted key store file location. ■ Use t3s protocol instead of t3. For example, the URL for Oracle Identity Manager is: t3s:HOST_NAME:PORT

25.1.4 Registering a SOA Composite with Oracle Identity Manager

The SOA composite must be registered with Oracle Identity Manager before it can be used as an approval process. To register a SOA composite with Oracle Identity Manager: 1. Create the COMPOSITE_NAME.props property file in the OIM_HOMEworkflowsregistration directory with the following content: name=COMPOSITE_NAME category=Approval providerType=BPEL serviceName=REQUEST_APPROVAL_SERVICE domainName=DOMAIN version=REVISION_ID payLoadID=PAYLOAD operationID=OPERATION_ID listOfTasks=HUMAN_TASK_NAMES Where: ■ Replace COMPOSITE_NAME with the name of the SOA composite as specified in the composite.xml file. ■ Replace REQUEST_APPROVAL_SERVICE with the name of the service exposed in the composite. This service is invoked while instantiating the composite for approval. ■ Replace OPERATION_ID with the name of operation to be invoked on the service mentioned for the serviceName property. ■ Replace PAYLOAD with the part name of the operation specified as the value of the operationID property. ■ Replace REVISION_ID with the SOA composite revision as specified in the composite.xml file. Note: If a composite is redeployed in SOA, then all the pending approvals in Oracle Identity Manager initiated by the composite becomes stale and are removed from the users TaskList. See Deploying an Existing SOA Archive in Oracle JDeveloper in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite for information about deploying existing SOA composites. Note: For a non-SSL connection, skip this section.