Click Apply. Enabling Oracle Identity Manager to Connect to SOA

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. Developing SOA Composites 25-5 ■ Replace DOMAIN with name of SOA partition in which the composite is deployed. By default, SOA has one partition named default. ■ Replace HUMAN_TASK_NAMES with the names of the approval tasks associated with the SOA composite. Separate the names with colon :. 2. Run the following command from the OIM_HOMEworkflowsregistration directory: ant -f registerworkflows-mp.xml register 3. Enter Oracle Identity Manager administrator username when prompted. 4. Enter Oracle Identity Manager administrator password when prompted.

5. Enter Oracle Identity Manager server t3 URL when prompted.

6. Enter the complete path of the property file name that you created in step 1 when

prompted.

25.2 Modifying Existing SOA Composites

To modify an existing SOA composite that can be used as an approval process, you must perform the following:

1. Modifying a SOA Project in JDeveloper

2. Disabling a SOA Composite on Oracle Identity Manager

3. Deploying a SOA Composite in Oracle SOA Server

4. Enabling a SOA Composite with Oracle Identity Manager

Note: Do not add any extra spaces in the properties file. Note: ■ JAVA_HOME environment variable must be set before running this utility. ■ This utility requires Apache Ant version 1.7 or later. ■ For a connection over SSL, you must meet the prerequisites mentioned in Prerequisites for Communication to Oracle Identity Manager Through SSL Mode on page 25-4. Note: When you login to the SOA server by using the Oracle Identity Manager administrator credentials, the login attempt fails if your challenge questions and answers and password are not reset in Oracle Identity Manager. You must reset the challenge questions and answers and password when you first login to Oracle Identity Manager. 25-6 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager

25.2.1 Modifying a SOA Project in JDeveloper

You can modify SOA composites by using JDeveloper. If you want to modify the default SOA composites, then you can access the respective JDeveloper projects in the paths listed in Table 25–1 : For information about using JDeveloper to build applications with Oracle SOA Suite, see Oracle® Fusion Middleware Developers Guide for Oracle SOA Suite.

25.2.2 Disabling a SOA Composite on Oracle Identity Manager

You can disable a SOA composite on Oracle Identity Manager by using the registerworkflows-mp utility located in the OIM_HOMEworkflowsnew-workflow directory. To disable a SOA composite on Oracle Identity Manager: Note: If the SOA composite modification involves adding or removing human tasks, then perform the following steps: 1. Modify the SOA composite in JDeveloper. While modifying the composite, make sure that the SOA composite version ID is changed. The existing SOA composite version ID, which is already registered with Oracle Identity Manager, cannot be used. 2. Disable the existing SOA composite in Oracle Identity Manager. 3. Deploy the SOA composite in Oracle SOA Server with new version ID. 4. Register the SOA composite with the new version to Oracle Identity Manager. Table 25–1 Location of Default SOA Composites SOA Composite Path BeneficiaryManagerApproval OIM_HOMEworkflowscompositesBeneficiaryManagerApproval.zip DefaultOperationalApproval OIM_HOMEworkflowscompositesDefaultOperationalApproval.zip DefaultRequestApproval OIM_HOMEworkflowscompositesDefaultRequestApproval.zip DefaultRoleApproval OIM_HOMEworkflowscompositesDefaultRoleApproval.zip ResourceAuthorizerApproval OIM_HOMEworkflowscompositesResourceAuthorizerApproval.zip ResourceAdministratorApproval OIM_HOMEworkflowscompositesResourceAdministratorApproval.zip RequesterManagerApproval OIM_HOMEworkflowscompositesRequesterManagerApproval.zip DefaultSODApproval OIM_HOMEworkflowscompositesDefaultSODApproval.zip Note: ■ JAVA_HOME environment variable must be set before running this utility. ■ This utility requires Apache Ant version 1.7 or later. ■ For a connection over SSL, you must meet the prerequisites described in Prerequisites for Communication to Oracle Identity Manager Through SSL Mode on page 25-4. Developing SOA Composites 25-7 1. Using a command prompt, go to the OIM_HOMEworkflowsregistration directory. 2. Run the following command: ant -f registerworkflows-mp.xml disable 3. When prompted to enter username, enter the Oracle Identity Manager administrator username. 4. When prompted to enter password, enter the Oracle Identity Manager administrator password. 5. When prompted to enter the server t3 URL, enter the Oracle Identity Manager server t3 URL, for example, t3:localhost:7001. 6. Specify the domain of the workflow. By default, this is set to the default domain. 7. When prompted for the name of the workflow, enter the SOA composite name. 8. When prompted for the version of the workflow, enter the SOA composite version.

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

25.2.4 Enabling a SOA Composite with Oracle Identity Manager

To enable a SOA Composite with Oracle Identity Manager: 1. Run the following command: ant -f registerworkflows-mp.xml enable 2. Perform steps 3 through 8 in listed Disabling a SOA Composite on Oracle Identity Manager on page 25-6. Note: ■ JAVA_HOME environment variable must be set before running this utility. ■ This utility requires Apache Ant version 1.7 or later. ■ For a connection over SSL, you must meet the prerequisites described in Prerequisites for Communication to Oracle Identity Manager Through SSL Mode on page 25-4.