Skip Headers
Oracle® Identity Manager Connector Guide for Novell GroupWise
Release 9.0.4

E10433-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Using the Connector

After you deploy the connector, you must configure it to meet your requirements. This chapter discusses the following connector configuration procedures:

Note:

These sections provide both conceptual and procedural information about configuring the connector. It is recommended that you read the conceptual information before you perform the procedures.

3.1 Performing First-Time Reconciliation

First-time reconciliation involves synchronizing lookup definitions in Oracle Identity Manager with the lookup fields of the target system, and performing full reconciliation. In full reconciliation, all existing user records from the target system are brought into Oracle Identity Manager.

The following is the sequence of steps involved in reconciling all existing user records:

Note:

In Oracle Identity Manager release 11.1.x, a scheduled job is an instance of a scheduled task. In this guide, the term scheduled task used in the context of Oracle Identity Manager release 9.1.0.x is the same as the term scheduled job in the context of Oracle Identity Manager release 11.1.x.

See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about scheduled tasks and scheduled jobs.

  1. Perform lookup field synchronization by running the scheduled tasks provided for this operation.

    See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about the attributes of the scheduled tasks for lookup field synchronization.

    See Section 3.4, "Configuring Scheduled Tasks" for information about running scheduled tasks.

  2. Perform user reconciliation by running the scheduled task for user reconciliation.

    See Section 3.3.4, "User Reconciliation Scheduled Task" for information about the attributes of this scheduled task.

    See Section 3.4, "Configuring Scheduled Tasks" for information about running scheduled tasks.

After first-time reconciliation, depending on the mode in which you configure the connector, the Last Recon TimeStamp parameter of the GroupWise IT Resource IT resource is automatically set to the time stamp at which the reconciliation run began.

See Also:

Section 2.3.2, "Configuring IT Resources" for information about the parameters of the IT resource

From the next reconciliation run onward, only target system user records that are added or modified after the time stamp stored in the IT resource are considered for incremental reconciliation. These records are brought to Oracle Identity Manager when you configure and run the user reconciliation scheduled task.

3.2 Scheduled Task for Lookup Field Synchronization

The following scheduled tasks are used for lookup fields reconciliation:

Table 3-1 describes the attributes of both scheduled tasks. See Section 3.4, "Configuring Scheduled Tasks" for information about configuring scheduled tasks.

Note:

  • Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.

  • Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.

Table 3-1 Attributes of the Scheduled Tasks for Lookup Field Synchronization

Attribute Description

LookupCodeName

This attribute holds the name of the lookup definition that contains mappings between the lookup fields of the target system and corresponding lookup definitions created in Oracle Identity Manager.

The default value is one of the following:

  • For distribution list lookup synchronization: Lookup.NGW.DistributionLists

  • For post office list lookup sycnhronization: Lookup.NGW.PostOffices

ITResourceName

Enter the name of the Novell eDirectory IT resource.

Default value: eDirectory IT Resource

SearchContext

Enter the Novell Groupwise search context to be used for fetching lookup field values from the target system.

Default value: O=glob

ObjectClass

Enter the name of the object class. The default value is:

  • For distribution lists: groupWiseDistributionList

  • For post office list: groupWisePostOffice

ReconMode

Enter Refresh if you want to completely refresh the existing lookup. Existing values in the lookup definition are deleted and then new values are added.

Enter update if you want to update the lookup definition with new values. Existing values in the lookup definition are left untouched.

The default value of this attribute in the Groupwise DistributionList Lookup Recon Task scheduled task is update.

The default value of this attribute in the Groupwise PostOffice List Lookup Recon Task scheduled task is Refresh.


3.3 Configuring Reconciliation

As mentioned earlier in this guide, reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. This section discusses the following topics related to configuring reconciliation:

3.3.1 Full Reconciliation

Full reconciliation involves reconciling all existing user records from the target system into Oracle Identity Manager. After you deploy the connector, you must first perform full reconciliation. In addition, you can switch from incremental reconciliation to full reconciliation whenever you want to ensure that all target system records are reconciled in Oracle Identity Manager.

To perform a full reconciliation run:

  • Ensure that the Last Recon TimeStamp parameter of the GroupWise IT Resource IT resource does not contain a value.

  • Specify All Available as the value of the NumberOfBatches attribute of the user reconciliation scheduled task.

At the end of the reconciliation run, the Last Recon TimeStamp parameter of the GroupWise IT Resource IT resource is automatically set to the time stamp at which the run started. From the next reconciliation run onward, only records created or modified after this time stamp are considered for reconciliation. This is incremental reconciliation.

3.3.2 Limited Reconciliation

By default, all target system records that are added or modified after the last reconciliation run are reconciled during the current reconciliation run. You can customize this process by specifying the subset of added or modified target system records that must be reconciled. You do this by creating filters for the reconciliation module.

For this connector, you create a filter by specifying values for the CustomizedReconQuery parameter of the GroupWise IT Resource IT resource while performing the procedure described in one of the following sections:

The following table lists the Novell GroupWise attributes, and the corresponding Oracle Identity Manager attributes, that you can use to build the query condition. You specify this query condition as the value of the CustomizedReconQuery parameter.

Oracle Identity Manager Attribute Novell GroupWise Attribute

User ID

cn

File ID

nGWFileID

Account ID

nGWAccountID

Gateway Access

nGWGatewayAccess


The following are sample query conditions:

  • Value assigned to the CustomizedReconQuery parameter: cn=JOHN|cn=JANE

    The user with user ID JOHN and JANE are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: nGWFileID=f06|nGWFileID=s1z

    The users with File ID f06 and s1z are reconciled.

If you do not specify values for the CustomizedReconQuery parameter, then all the records in the target system are compared with existing Oracle Identity Manager records during reconciliation.

The following are guidelines to be followed while specifying a value for the CustomizedReconQuery parameter:

  • For the target system attributes, you must use the same case (uppercase or lowercase) as given in the table shown earlier in this section. This is because the attribute names are case-sensitive.

  • You must not include unnecessary blank spaces between operators and values in the query condition.

    A query condition with spaces separating values and operators would yield different results as compared to a query condition that does not contain spaces between values and operators. For example, the output of the following query conditions would be different:

    cn=John

    cn= John

    In the second query condition, the reconciliation engine would look for first name and last name values that contain a space at the start.

  • You must not include special characters other than the equal sign (=), ampersand (&), and vertical bar (|) in the query condition.

    Note:

    An exception is thrown if you include special characters other than the equal sign (=), ampersand (&), and vertical bar (|).

  • The query condition must be an expression without any braces.

  • Searching users based on more than three user attributes is not supported. For example, if the query condition is cn=JOHN&nGWFileID=f06&nGWGatewayAccess=Sublm|nGWAccountID=23, then the query generates an error.

3.3.3 Batched Reconciliation

During a reconciliation run, all changes in the target system records are reconciled into Oracle Identity Manager. Depending on the number of records to be reconciled, this process may require a large amount of time. In addition, if the connection breaks during reconciliation, then the process would take longer to complete. You can configure batched reconciliation to avoid such problems.

To configure batched reconciliation, you must specify values for the following user reconciliation scheduled task attributes:

  • StartRecord: Use this attribute to specify the record number from which batched reconciliation must begin.

  • BatchSize: Use this attribute to specify the number of records that must be included in each batch.

  • NumberOfBatches: Use this attribute to specify the total number of batches that must be reconciled. If you do not want to use batched reconciliation, specify All Available as the value of this attribute.

    Note:

    If you specify All Available as the value of this attribute, then the values of the StartRecord and BatchSize attributes are ignored.

You specify values for these attributes by following the instructions described in Section 3.3.4, "User Reconciliation Scheduled Task."

After you configure batched reconciliation, if reconciliation fails during a batched reconciliation run, then refer to the log file for information about the batch at which reconciliation has failed. The log file provides the following information about batched reconciliation:

  • Serial numbers of the batches that have been successfully reconciled

  • User IDs associated with the records with each batch that has been successfully reconciled

  • If the batched reconciliation run fails, then the serial number of the batch that has failed

3.3.4 User Reconciliation Scheduled Task

When you run the Connector Installer or import the connector XML file, the Groupwise User Recon Task reconciliation scheduled task is automatically created in Oracle Identity Manager. This scheduled task is used to reconcile user data from the target system.

You must specify values for the following attributes of the Groupwise User Recon Task scheduled task. Table 3-2 describes the attributes of this scheduled task.

Note:

  • Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.

  • Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.

Table 3-2 Attributes of the User Reconciliation Scheduled Task

Attribute Description

ITResourceName

Enter the name of the IT resource for the Novell GroupWise installation from which you want to reconcile user records.

Default value: GroupWise IT Resource

eDirITResourceName

Enter the name of the Novell eDirectory IT resource.

Default value: eDirectory IT Resource

RemoteResourceName

Enter the name of the IT resource in which the remote service name and URL are specified.

Default value: GroupWise XRM

ResourceObjectName

Enter the name of the resource object against which reconciliation runs must be performed.

Default value: Groupwise User

XLDeleteUsersAllowed

If this attribute is set to true, then the Delete reconciliation event is started. Users who are deleted from the target system are removed from Oracle Identity Manager. This requires all the users on the target system to be compared with all the users in Oracle Identity Manager.

If this attribute is set to false, then the users are not deleted.

Default value: true

Note: This process affects performance.

TrustedSource

Enter true if you want to configure the connector for trusted source reconciliation.

Enter false if you want to configure the connector for target resource reconciliation.

Default value: true

Xellerate Type

Enter the role that must be set for OIM Users created through reconciliation. You can enter one of the following values:

  • End-User

  • End-User Administrator

Default value: End-User Administrator

Organization

Enter the name of the Oracle Identity Manager organization in which reconciled users must be created.

Default value: Xellerate Users

Role

Enter the employee type that must be set for OIM Users created through reconciliation. You can enter one of the following values:

  • Full-Time Employee

  • Part-Time Employee

  • Temp

  • Intern

  • Consultant

Default value: Consultant

StartRecord

Enter the number of the target system record from which a batched reconciliation run must begin.

Default value: 1

This attribute is used in conjunction with the BatchSize and NumberOfBatches attributes. All three attributes are discussed in Section 3.3.3, "Batched Reconciliation."

BatchSize

Enter the number of records that must be included in each batch fetched from the target system.

Default value: 3

This attribute is used in conjunction with the NumberOfBatches and StartRecord attributes. All three attributes are discussed in Section 3.3.3, "Batched Reconciliation."

NumberOfBatches

Enter the number of batches that must be reconciled.

Default value: All Available

Sample value: 50

This attribute is used in conjunction with the BatchSize and StartRecord attributes. All three attributes are discussed in detail in Section 3.3.3, "Batched Reconciliation."

If you accept the default value (All Available), then batched reconciliation is not performed.


3.4 Configuring Scheduled Tasks

You can apply this procedure to configure the scheduled tasks for lookup field synchronization and reconciliation.

Table 3-3 lists the scheduled tasks that form part of the connector.

Table 3-3 Scheduled Tasks for Lookup Field Synchronization and Reconciliation

Scheduled Task Description

Groupwise DistributionList Lookup Recon Task

This scheduled task is used to synchronize the values of distribution list lookup fields between Oracle Identity Manager and the target system. See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about this scheduled task.

Groupwise PostOffice List Lookup Recon Task

This scheduled task is used to synchronize the values of post office list lookup fields between Oracle Identity Manager and the target system. See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about this scheduled task.

Groupwise User Recon Task

This scheduled task is used for user reconciliation. See Section 3.3.4, "User Reconciliation Scheduled Task" for information about this scheduled task.


Depending on the Oracle Identity Manager release that you are using, perform the procedure described in one of the following sections:

3.4.1 Configuring Scheduled Tasks on Oracle Identity Manager Release 9.0.1 through 9.0.3.x

To configure a scheduled task:

  1. Open the Oracle Identity Manager Design Console.

  2. Expand the Xellerate Administration folder.

  3. Select Task Scheduler.

  4. Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.

  5. For the first scheduled task, enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the FAILED status to the task.

  6. Ensure that the Disabled and Stop Execution check boxes are not selected.

  7. In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.

  8. In the Interval region, set the following schedule parameters:

    • To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option. If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.

    • To set the task to run only once, select the Once option.

  9. Provide values for the attributes of the scheduled task.

  10. Click Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.

Stopping Reconciliation

Suppose the user reconciliation scheduled task for the connector is running and user records are being reconciled. If you want to stop the reconciliation process:

  1. Perform Steps 1 through 4 of the procedure to configure reconciliation scheduled tasks.

  2. Select the Stop Execution check box in the task scheduler.

  3. Click Save.

3.4.2 Configuring Scheduled Tasks on Oracle Identity Manager Release 9.1.0.x or Release 11.1.x

To configure a scheduled task:

  1. Depending on the Oracle Identity Manager release you are using, perform one of the following steps:

    • For Oracle Identity Manager release 9.x or 11.1.1:

      1. Log in to the Administrative and User Console.

      2. On the Welcome to Oracle Identity Manager Self Service page, click Advanced in the upper-right corner of the page.

    • For Oracle Identity Manager release 11.1.2:

      1. Log in to Oracle Identity System Administration.

      2. In the left pane, under System Management, click Scheduler.

  2. Depending on the Oracle Identity Manager release you are using, perform one of the following steps:

    • If you are using Oracle Identity Manager release 9.x, expand Resource Management, and then click Manage Scheduled Task.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. On the Welcome to Oracle Identity Manager Self Service page, click Advanced.

      2. Click the System Management tab, and then click Scheduler.

      3. On the left pane, click Advanced Search.

  3. On the page that is displayed, you can use any combination of the search options provided to locate a scheduled task. Click Search after you specify the search criteria.

    The list of scheduled tasks that match your search criteria is displayed in the search results table.

  4. Depending on the Oracle Identity Manager release you are using, perform one of the following steps:

    • If you are using Oracle Identity Manager release 9.1.0.x, then in the search results table, click the Edit icon in the Edit column for the scheduled task.

    • If you are using Oracle Identity Manager release 11.1.x, then select the link for the scheduled task from the list of scheduled tasks displayed in the search results table.

  5. Modify the details of the scheduled task. To do so:

    1. If you are using Oracle Identity Manager release 9.1.0.x, then on the Edit Scheduled Task Details page, modify the following parameters, and then click Continue:

      • Status: Specify whether you want to leave the task in the enabled state. In the enabled state, the task is ready for use.

      • Max Retries: Enter an integer value in this field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task. The default value is 1.

      • Next Start: Use the date editor to specify the date when you want the task to run. After you select a date value in the date editor, you can modify the time value that is automatically displayed in the Next Start field.

      • Frequency: Specify the frequency at which you want the task to run.

    2. If you are using Oracle Identity Manager release 11.1.x, then on the Job Details tab, you can modify the following parameters:

      • Retries: Enter an integer value in this field. This number represents the number of times the scheduler tries to start the job before assigning the Stopped status to the job.

      • Schedule Type: Depending on the frequency at which you want the job to run, select the appropriate schedule type.

      Note:

      See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for detailed information about schedule types.

      In addition to modifying the job details, you can enable or disable a job.

  6. Specify values for the attributes of the scheduled task. To do so:

    Note:

    • If you are using Oracle Identity Manager release 9.1.0.x, then on the Attributes page, select the attribute from the Attribute list, specify a value in the field provided, and then click Update.

    • If you are using Oracle Identity Manager release 11.1.x, then on the Job Details tab, in the Parameters region, specify values for the attributes of the scheduled task.

  7. After specifying the attributes, perform one of the following:

    • If you are using Oracle Identity Manager release 9.1.0.x, then click Save Changes to save the changes.

      Note:

      The Stop Execution option is not available in the Administrative and User Console. If you want to stop a task, then click Stop Execution on the Task Scheduler form of the Design Console.

    • If you are using Oracle Identity Manager release 11.1.x, then click Apply to save the changes.

      Note:

      The Stop Execution option is available in the Administrative and User Console. You can use the Scheduler Status page to either start, stop, or reinitialize the scheduler.

3.5 Performing Provisioning Operations

Provisioning a resource for an OIM User involves using Oracle Identity Manager to create a target system account for the user.

When you install the connector on Oracle Identity Manager release 11.1.1, the direct provisioning feature is automatically enabled. This means that the process form is enabled when you install the connector.

If you have configured the connector for request-based provisioning, then the process form is suppressed and the object form is displayed. In other words, direct provisioning is disabled when you configure the connector for request-based provisioning. If you want to revert to direct provisioning, then perform the steps described in Section 3.5.3, "Switching Between Request-Based Provisioning and Direct Provisioning on Oracle Identity Manager Release 11.1.1."

The following are types of provisioning operations:

See Also:

Oracle Identity Manager Connector Concepts for information about the types of provisioning

This section discusses the following topics:

3.5.1 Direct Provisioning

To provision a resource by using the direct provisioning approach:

  1. Log in to the Administrative and User Console.

  2. If you want to first create an OIM User and then provision a target system account, then:

    • If you are using Oracle Identity Manager release 8.5.3.1 through 9.0.3.x or release 9.1.0.x, then:

      1. From the Users menu, select Create.

      2. On the Create User page, enter values for the OIM User fields and then click Create User.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. On the Welcome to Identity Administration page, in the Users region, click Create User.

      2. On the Create User page, enter values for the OIM User fields, and then click Save.

  3. If you want to provision a target system account to an existing OIM User, then:

    • If you are using Oracle Identity Manager release 8.5.3.1 through 9.0.3.x or release 9.1.0.x, then:

      1. From the Users menu, select Manage.

      2. Search for the OIM User and select the link for the user from the list of users displayed in the search results.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. On the Welcome to Identity Administration page, search for the OIM User by selecting Users from the list on the left pane.

      2. From the list of users displayed in the search results, select the OIM User. The user details page is displayed on the right pane.

  4. Depending on the Oracle Identity Manager release you are using, perform one of the following steps:

    • If you are using Oracle Identity Manager release 8.5.3.1 through 9.0.3.x or release 9.1.0.x, then:

      1. On the User Detail page, select Resource Profile from the list at the top of the page.

      2. On the Resource Profile page, click Provision New Resource.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. On the user details page, click the Resources tab.

      2. From the Action menu, select Add Resource. Alternatively, you can click the add resource icon with the plus (+) sign. The Provision Resource to User page is displayed in a new window.

  5. On the Step 1: Select a Resource page, select Groupwise User from the list and then click Continue.

  6. On the Step 2: Verify Resource Selection page, click Continue.

  7. On the Step 5: Provide Process Data for GroupWise User page, enter the details of the account that you want to create on the target system and then click Continue.

  8. On the Step 5: Provide Process Data for User Nicknames page, if required, enter details of the nicknames and then click Continue.

  9. On the Step 5: Provide Process Data for User Distribution Lists page, if required, enter details of the distribution list, and then click Continue.

  10. On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.

  11. The "Provisioning has been initiated" message is displayed. Perform one of the following steps:

    • If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, click Back to User Resource Profile. The Resource Profile page shows that the resource has been provisioned to the user.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. Close the window displaying the "Provisioning has been initiated" message.

      2. On the Resources tab, click Refresh to view the newly provisioned resource.

3.5.2 Request-Based Provisioning

Note:

The information provided in this section is applicable only if you are using Oracle Identity Manager release 11.1.1.

A request-based provisioning operation involves both end users and approvers. Typically, these approvers are in the management chain of the requesters. The following sections discuss the steps to be performed by end users and approvers during a request-based provisioning operation:

Note:

The procedures described in these sections are built on an example in which the end user raises or creates a request for provisioning a target system account. This request is then approved by the approver.

3.5.2.1 End User's Role in Request-Based Provisioning

The following steps are performed by the end user in a request-based provisioning operation:

See Also:

Oracle Fusion Middleware User's Guide for Oracle Identity Manager for detailed information about these steps

  1. Log in to the Administrative and User Console.

  2. On the Welcome page, click Advanced in the upper-right corner of the page.

  3. On the Welcome to Identity Administration page, click the Administration tab, and then click the Requests tab.

  4. From the Actions menu on the left pane, select Create Request.

    The Select Request Template page is displayed.

  5. From the Request Template list, select Provision Resource and click Next.

  6. On the Select Users page, specify a search criterion in the fields to search for the user that you want to provision the resource, and then click Search. A list of users that match the search criterion you specify is displayed in the Available Users list.

  7. From the Available Users list, select the user to whom you want to provision the account.

    If you want to create a provisioning request for more than one user, then from the Available Users list, select users to whom you want to provision the account.

  8. Click Move or Move All to include your selection in the Selected Users list, and then click Next.

  9. On the Select Resources page, click the arrow button next to the Resource Name field to display the list of all available resources.

  10. From the Available Resources list, select iPlanet User, move it to the Selected Resources list, and then click Next.

  11. On the Resource Details page, enter details of the account that must be created on the target system, and then click Next.

  12. On the Justification page, you can specify values for the following fields, and then click Finish.

    • Effective Date

    • Justification

    On the resulting page, a message confirming that your request has been sent successfully is displayed along with the Request ID.

  13. If you click the request ID, then the Request Details page is displayed.

  14. To view details of the approval, on the Request Details page, click the Request History tab.

3.5.2.2 Approver's Role in Request-Based Provisioning

The following are steps performed by the approver in a request-based provisioning operation:

The following are steps that the approver can perform:

  1. Log in to the Administrative and User Console.

  2. On the Welcome page, click Self-Service in the upper-right corner of the page.

  3. On the Welcome to Identity Manager Self Service page, click the Tasks tab.

  4. On the Approvals tab, in the first section, you can specify a search criterion for request task that is assigned to you.

  5. From the search results table, select the row containing the request you want to approve, and then click Approve Task.

    A message confirming that the task was approved is displayed.

3.5.3 Switching Between Request-Based Provisioning and Direct Provisioning on Oracle Identity Manager Release 11.1.1

Note:

It is assumed that you have performed the procedure described in Section 2.5.8, "Configuring Oracle Identity Manager for Request-Based Provisioning."

On Oracle Identity Manager release 11.1.1, if you want to switch from request-based provisioning to direct provisioning, then:

  1. Log in to the Design Console.

  2. Disable the Auto Save Form feature as follows:

    1. Expand Process Management, and then double-click Process Definition.

    2. Search for and open the Groupwise User process definition.

    3. Deselect the Auto Save Form check box.

    4. Click the Save icon.

  3. If the Self Request Allowed feature is enabled, then:

    1. Expand Resource Management, and then double-click Resource Objects.

    2. Search for and open the Groupwise User resource object.

    3. Deselect the Self Request Allowed check box.

    4. Click the Save icon.

On Oracle Identity Manager release 11.1.1, if you want to switch from direct provisioning back to request-based provisioning, then:

  1. Log in to the Design Console.

  2. Enable the Auto Save Form feature as follows:

    1. Expand Process Management, and then double-click Process Definition.

    2. Search for and open the Groupwise User process definition.

    3. Select the Auto Save Form check box.

    4. Click the Save icon.

  3. If you want to enable end users to raise requests for themselves, then:

    1. Expand Resource Management, and then double-click Resource Objects.

    2. Search for and open the Groupwise User resource object.

    3. Select the Self Request Allowed check box.

    4. Click the Save icon.

3.6 Configuring Provisioning in Oracle Identity Manager Release 11.1.2

To configure provisioning operations in Oracle Identity Manager release 11.1.2:

Note:

The time required to complete a provisioning operation that you perform the first time by using this connector takes longer than usual.

  1. Log in to Oracle Identity Administrative and User console.

  2. Create a user. See the "Managing Users" chapter in Oracle Fusion Middleware User's Guide for Oracle Identity Manager for more information about creating a user.

  3. On the Account tab, click Request Accounts.

  4. In the Catalog page, search for and add to cart the application instance, and then click Checkout.

  5. Specify values for fields in the application form and then click Ready to Submit.

  6. Click Submit.

  7. If you want to provision a resource to an existing OIM User, then:

    1. On the Users page, search for the required user.

    2. On the user details page, click Accounts.

    3. Click the Request Accounts button.

    4. Search for the Novell GroupWise application instance in the catalog search box and select it.

    5. Click Add to Cart.

    6. Click Checkout.

    7. Specify values for fields in the application form and then click Ready to Submit.

    8. Click Submit.