Creating a Request To Create a User

14-4 Oracle Fusion Middleware Users Guide for Oracle Identity Manager 7. In the Resource Details page, specify values for the attributes of the resource. In this example, you can select the life span of the E-Business resource being provisioned to the selected user or users. In the Life Span Type lookup, select a life span type, such as Short term, Mid term, or Long term. In the Server lookup, select the name of the E-Business server to connect to. For the Oracle Apps User Responsibilities parent attribute, you can enter multiple sets of values for the Responsibility Start Date, Responsibility End Date, and Responsibility Name child attributes. To do so, select values in the fields, and then click Add. Repeat entering another set of values in the Responsibility Start Date, Responsibility End Date, and Responsibility Name fields, and then click Add. For information about defining parent and child attributes, see Creating a Request Template Based on the Provisioning Resource Request Type on page 17-10. Specify values for all other resource attributes, and then click Next. If you select multiple resources in the Select Resources page, then the Resource Details page for each selected resource is displayed one by one. For instance, in the Select Resources page, you select the E-Business and Active Directory resources. The Resource Details page for the E-Business resource is displayed. Enter values for all attributes of the E-Business resource, and click Next. Then, the Resource Details page for the Active Directory resource is displayed. Specify values for all attributes of the Active Directory resource, and click Next. 8. If the selected resource has dependent resources, then the steps to select the dependent resources are displayed. Select the dependent resources, click Next. A resource object can have a dependency on other resource objects. During creation of provision resource request for self or others, if the dependent resources are not already provisioned, then these dependent resources are automatically added to the request. This is applicable to the Provision Resource and Self Provision Resource request types. Dependent resources can of the following types: ■ Single beneficiary: During creation of a provision resource request for single user, if the dependent resources are not already provisioned, then those dependent resources are automatically added to the request. Suppose the resource objects DB, AD, and Exchange are created in such a way that Exchange has dependency on AD, and AD has dependency on DB. Single beneficiary dependent resources is described with the help of the following examples: Note: Only the E-Business RO resource is displayed in the Selected Resources list because the Provision E-Business Resource request template is created only for provisioning the E-Business resource. The resources are displayed in the Available Resources list based on the resource selection in the request template. Note: In this page, the attributes are picked up from the request dataset. See Step 1: Creating a Request Dataset for the Resources in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about request datasets. Creating and Searching Requests 14-5 Example 1: User Jane does not have any of the resources. During self provision resource request, Jane selects Exchange as a resource in the Select Resources step. Because Jane does not have the dependent resources AD and DB, the request UI automatically adds the resource details collection steps for the resources AD and DB along with the resource Exchange. Example 2: User John has DB resource provisioned. You want to provision the resource Exchange to John. During the provision resource request, you select John in the Select Users step and Exchange in the Select Resources step. Because John does not have the dependent resource AD provisioned, the request UI automatically adds the resource details collection step to the resource AD along with the resource Exchange. Resource DB is not added because John already has DB provisioned. Example 3: User Brad does not have any resources. During self provision resource request, Brad selects DB as a resource in the Select Resources step. Resource details collection step for only the resource DB is shown because the DB resource does not have any dependency. ■ Multiple beneficiary: During creation of a provision resource request for multiple users, if any of the users doesnt have dependent resources provisioned, then those dependent resources will be automatically added to the request. These dependent resources will be added to only to those beneficiaries that doesnt already have these resources provisioned. Suppose the resource objects DB, AD, and Exchange are created in such a way that Exchange has dependency on AD, and AD has dependency on DB. Multiple beneficiary dependent resources is described with the help of the following examples: Example 1: Users Jane and John do not have any resources provisioned. You want to provision the resource Exchange to Jane and John. During the provision resource request, you select Jane and John in the Select Users step and Exchange in the Select Resources step. Because both the beneficiaries do not have the dependent resources AD and DB provisioned, the request UI automatically adds the resource details collection step to the resources AD and DB along with the resource Exchange. In this request, the resources AD and DB are added to both the beneficiaries Jane and John. Example 2: User Jerry does not have any resource provisioned. User Katie has resource DB provisioned. You want to provision the resource Exchange to Jerry and Katie. During the provision resource request, you select Jerry and Katie in the Select Users step and Exchange in the Select Resources step. Because Jerry one of the beneficiaries does not have the dependent resources AD and DB provisioned, the request UI automatically adds the resource details collection step for the resources AD and DB along with the resource Exchange. In this request, the resource AD is added to both the beneficiaries Jerry and Katie. However, the resource DB is added to only Jerry but not to Katie because Katie already has the resource DB provisioned. 9. In the Justification page, you can specify values for the following fields, and then click Finish to submit the request. ■ Effective Date: Enter the date when you want the underlying operation of the request to be executed after approval. For example, if you specify September 15 as the effective date for provisioning a laptop to a user, then the laptop is 14-6 Oracle Fusion Middleware Users Guide for Oracle Identity Manager not provisioned to the user before September 15 even if the request is approved. The resource is provisioned on September 15. If the request is approved after September 15, then the resource is provisioned with immediate effect. ■ Justification: Enter a justification for creating the request. If you have selected a user to provision the resource, then the request is available for approval. If you have selected multiple users to provision the resource, then the request is broken into multiple child requests for operation level approval, and each child request can be approved or rejected independently.

14.1.3 Creating a Request to Deprovision Resources

To create a request to deprovision one or more resources:

1. In the Welcome page of Oracle Identity Manager Advanced Administration, under

Administration, click Search Requests. Alternatively, you can click the Administration tab, and then click Requests. 2. From the Actions menu, select Create Request. Alternatively, you can click the create request icon on the toolbar. The Select Request Template page of the Create Request wizard is displayed. The steps in this wizard are dynamically generated based on the selection of the request template in the first step.

3. From the Request Template list, select De-Provision Resource. Then, click Next.

4. In the Select Users page, search for the users. Select one or more users from the

Available Users list from whom you want to deprovision a resource. Click Move to move the users to the Selected Users list, and then click Next.

5. In the Select Resources page, search for the resources. Select one or more resources

that you want to deprovision. Click Move to move the resources to the Selected Resources list. Then, click Next. The Justification page is displayed.

6. In the Effective Date field, specify a date on which you want the resource to be

deprovisioned.

7. In the Justification field, enter a justification for the deprovisioning operation.

8. Click Finish. The request to deprovision one or more resources is created.

Note: The following request types are similar in nature in terms of request creation and execution: ■ Enable Provisioned Resource ■ Disable Provisioned Resource ■ De-Provision Resource Note: Resource search in Select Resources page lists all the resources provisioned to user selected in Select Users page. If multiple users are selected, then search shows common resources provisioned to all selected users.