| Oracle® Identity Manager Generic Technology Connector Administrator's Guide Release 9.0.3.1 Part Number B32445-02 |
|
|
View PDF |
| Oracle® Identity Manager Generic Technology Connector Administrator's Guide Release 9.0.3.1 Part Number B32445-02 |
|
|
View PDF |
This chapter discusses the following steps involved in creating generic technology connectors:
Step 2: Identifying the Predefined Providers That Meet the Provider Requirements
Step 3: Addressing Requirements to Create the Generic Technology Connector
Step 4: Using the Administrative and User Console to Create the Generic Technology Connector
You must identify the combination of providers that you want to include in the connector. This decision must be based on the following factors:
Outgoing and incoming data formats and data transport mechanisms that are supported by the target system
Predefined providers shipped with Oracle Identity Manager
See Also:
The "Introduction to Generic Technology Connectors" section for conceptual information about providersBased on your knowledge of the data formats and data transport mechanisms supported by the target system, identify the providers that must be included in the generic technology connector that you create. If the target system supports multiple data formats and data transport mechanisms, then you must select a single combination of the transport and format providers discussed in the first chapter. You cannot include, for example, multiple Reconciliation Format providers in a single generic technology connector.
The following predefined providers are shipped with this release of Oracle Identity Manager:
Shared Drive Transport Provider for Reconciliation
CSV Format Provider for Reconciliation
SPML Format Provider for Provisioning
Web Services Transport for Provisioning
Various Validation Providers
Refer to Appendix A for information about these predefined providers. You must check if these providers meet the provider requirements that you determine in the preceding step.
You must address the following requirements:
Connectivity between the target system server and the Oracle Identity Manager server
You must ensure that connectivity can be established between the target system server and the Oracle Identity Manager server. For example, in a Linux environment, you must enter the fully qualified host name of the Oracle Identity Manager server in the /etc/hosts file on the target system server.
User account used to create the generic technology connector
All users belonging to the SYSTEM ADMINISTRATORS group of Oracle Identity Manager can create generic technology connectors. Alternatively, members of a group to which you assign the required menu items and permissions can create generic technology connectors.
See Also:
The "User Groups" chapter of Oracle Identity Manager Administrative and User Console Guide for information about creating groups and assigning menu items and permissions to themThe required menu items are as follows:
Create Generic Technology Connector menu item
Manage Generic Technology Connector menu item
The required permissions are as follows:
Form Designer (Allow Insert, Write Access, Delete Access)
Structure Utility.Additional Column (Allow Insert, Write Access, Delete Access)
Meta-Table Hierarchy (Allow Insert, Write Access, Delete Access)
If these permissions are not correctly assigned to the group, then an error is thrown when a user belonging to this group starts creating a generic technology connector.
The user that you assign to this group is, by default, also a member of the ALL USERS group. Besides these two groups, if the user is a member of any other group to which these menu items and permissions have not been assigned, then an error may be thrown when the user clicks the Create button on the final Administrative and User Console screen for creating generic technology connectors. This problem is described in the "User Account Used to Create Generic Technology Connectors" section of the "Known Issues" chapter.
You use the Oracle Identity Manager Administrative and User Console to create the generic technology connector.
Note:
To fully understand the concepts explained in this section, you would need to view the Administrative and User Console screens that are used to create generic technology connectors. Therefore, it is recommended that you perform a trial run of the procedure described in this section.At the start of the trial run, the generic technology connector name that you specify must be one that you do not plan to use when you actually start creating generic technology connectors. On the last screen, you can end the trial run by selecting the Cancel option.
In addition, refer to Chapter 6 for information about known issues and limitations that you may encounter while creating generic technology connectors.
To navigate to the first Administrative and User Console screen for creating a generic technology connector, open the Administrative and User Console, expand Generic Technology Connector, and then click Create.
From this point onward, screen-wise instructions are provided in the following sections:
To select the reconciliation and provisioning providers that you want to include in the generic technology connector, use this screen as follows:
In the Name field, specify a name for the generic technology connector.
You must ensure that the name you specify is not the same as:
The name of any other connector (application-specific connector or generic technology connector) on this Oracle Identity Manager installation
The name of any other connector object (such as resource objects, IT resources, and process forms) on this Oracle Identity Manager installation
An error is thrown if you specify a name that is the same as the name of an existing connector. However, an error is not thrown if you specify a name that is the same as the name of an existing connector object. Therefore, you must ensure that the name you want to specify is not the same as the name of any existing connector object.
Refer to Appendix B for more information about automatically created connector objects.
In addition, you must not enter non-ASCII characters in the Name field because Oracle Identity Manager does not support non-ASCII characters in connector names.
See Also:
The "Names of Generic Technology Connectors and Connector Objects" section of the "Known Issues" chapter for more information about both these limitationsIf you want to use the generic technology connector for reconciliation, select Reconciliation and then perform the following steps:
From the Transport Type list, select the Reconciliation Transport provider that you want to use for this connector. This list displays the predefined Reconciliation Transport providers.
From the Payload Format list, select the Reconciliation Format provider that you want to use for this connector. This list displays the predefined Reconciliation Format providers.
The payload format is the format of the target system data. The Reconciliation Format provider parses and converts this data into a format that is supported by Oracle Identity Manager.
If you want to use the generic technology connector for provisioning, select Provisioning and then perform the following steps:
Note:
You can choose only Reconciliation, only Provisioning, or both Reconciliation and Provisioning.From the Transport Type list, select the Provisioning Transport provider that you want to use for this connector. This list displays the predefined Provisioning Transport providers.
From the Payload Format list, select the Provisioning Format provider that you want to use for this connector. This list displays the predefined Provisioning Format providers.
This payload format is the format into which provisioning data is converted by the Provisioning Format provider. The Provisioning Transport provider carries the output of the Provisioning Format provider to the target system.
Click Continue.
Use this screen to specify values for the parameters of the providers that you select on the previous screen.
On this screen, the parameters are divided into two categories:
The GUI elements displayed on this screen represent the run-time parameters for the providers that you select on the previous screen. A run-time parameter represents a value that you specify at run time. For example, the location of the directories containing the data files that you want to reconcile is a run-time parameter value.
Refer to Appendix A for information about the values to be specified for the parameters of the predefined providers.
The parameters listed in this section are either design parameters of providers or reconciliation-specific parameters that are common to all generic technology connectors. A design parameter represents a value or set of values that is defined while the provider is being designed. For example, the format of data files that can be parsed by a Format provider is a design parameter for that provider.
The following are reconciliation-specific design parameters:
Note:
If you do not select the Reconciliation option on the previous screen, then these reconciliation-specific design parameters are not displayed on this screen.Use this parameter to specify a batch size for the reconciliation run. The batch size represents the number of records per batch that is reconciled. By specifying a batch size, you can break into batches the total number of records that the reconciliation engine fetches from the target system.
The default value of this parameter is All.
During reconciliation, data that is passed by the Reconciliation Format provider is accepted as input by the Validation provider. This provider checks the data on the basis of the validation rules that you define. Some of the reconciliation data records may not clear the validation checks. You can use the Stop Reconciliation Threshold parameter to automatically stop reconciliation if the percentage of records that fail the validation checks to the total number of reconciliation records processed exceeds the specified value.
The following example illustrates how this parameter works:
Suppose you specify 20 as the value of the Stop Reconciliation Threshold parameter. This means that you want reconciliation to stop if the percentage of the number of failed records to the total number of records processed becomes equal to or greater than 20. Suppose the second and eighth records fail the validation checks. At this stage, the number of failed records is 2 and the total number of records processed is 8. The percentage of failed records is 25, which is greater than the specified threshold of 20. Therefore, reconciliation is stopped after the eighth record is processed.
If reconciliation is stopped because the actual percentage of failed records exceeds the specified percentage, then the records that have already been reconciled into Oracle Identity Manager are not removed.
The default value of this parameter is None. This default value specifies that during any particular reconciliation run, you want all the target system records to be checked, regardless of the number of records that fail the checks.
Stop Threshold Minimum Records
If you use the Stop Reconciliation Threshold parameter, then there may be a problem when several invalid records are encountered at the beginning of the reconciliation run. For example, suppose you specify a value of 40 for the Stop Reconciliation Threshold parameter. When reconciliation starts, suppose the first record fails the validation checks. At this stage, the percentage of records failed to total records processed has reached 100. Therefore, reconciliation would stop.
To avoid such situations, you can use the Stop Threshold Minimum Records parameter in conjunction with the Stop Reconciliation Threshold parameter. The Stop Threshold Minimum Records parameter specifies the number of records that must be processed by the Validation provider before the Stop Reconciliation Threshold validation is automatically activated.
The following example illustrates how this parameter works:
Suppose you specify the following values:
Stop Reconciliation Threshold: 20
Stop Threshold Minimum Records: 80
With these values, from the eighty-first record onward, the Stop Reconciliation Threshold validation is activated. If any record fails the validation check, then the reconciliation engine calculates the percentage of failed records to total records processed.
Note:
The default value of this parameter is
None. You must specify a value for this parameter if you specify a value for the Stop Reconciliation Threshold parameter.Use this parameter to specify whether you want the reconciliation engine to perform full or incremental reconciliation.
In incremental reconciliation, only those target system records that have changed after the last reconciliation run are reconciled (stored) into Oracle Identity Manager.
In full reconciliation, all the reconciliation records are extracted from the target system. However, the optimized reconciliation feature identifies and ignores records that have already been reconciled in Oracle Identity Manager. This helps reduce the space occupied by reconciliation data. If this feature were not present, then the amount of data stored in the Oracle Identity Manager database would increase rapidly with each reconciliation run.
You must select incremental reconciliation if either one of the following conditions is true:
The target system time-stamps or uniquely marks (in some way) files or individual data records that it generates and the Reconciliation Transport provider can recognize records that have been time-stamped or marked by the target system.
For example:
Suppose you can configure the target system to append "NEW_" to each new data file that it generates. If you select the Shared Drive Transport provider, then you can specify "NEW_" as the value of the File Prefix parameter. During reconciliation, this provider will copy only files that have "NEW_" appended to their names.
The target system only provides data records that have changed after the last reconciliation run.
If neither of these conditions is true, then you must select full reconciliation. In this case, as mentioned earlier, the optimized reconciliation feature identifies and ignores records that have already been reconciled.
After you specify values for the run-time and design parameters, click Continue.
Note:
If the values that you provide on this screen are not correct, then the following error is displayed at the top of the screen when you submit the information:"Problem encountered during metadata detection. Please check the server logs for more details."
This problem and its solution is discussed in the "Step 2: Define Parameters Screen" section of the "Known Issues" chapter.
Use this screen to define data sets and mappings between the fields of the data sets. In other words, you use this screen to specify the identity data fields that you want to:
Propagate from the target system to Oracle Identity Manager during reconciliation
Propagate from Oracle Identity Manager to the target system during provisioning
After you click the Continue button on the second (previous) screen, the elements displayed on the Modify Connector Configuration screen depend on the input provided on the first and second screens:
If you select the Reconciliation-only option or the Reconciliation and Provisioning option, then:
If there are no data files in the staging directories, then an error message is displayed. This issue is discussed in the "Modify Connector Configuration Screen" section of the "Known Issues" chapter.
If this error occurs, then you must restart the procedure from the first step onward. To restart the procedure, you can specify a different name for the generic technology connector on the first screen and then continue. Alternatively, if you want to use the same generic technology connector name, you must restart the application server and then start from the first screen onward.
See Also:
The "Names of Generic Technology Connectors and Connector Objects" section of the "Known Issues" chapter for information about why you must follow one of these methods to restart the procedureIf there are data files in the staging directories, then Oracle Identity Manager automatically reads metadata from the data files. This metadata is prepopulated in the data set fields displayed on the Modify Connector Configuration screen.
If you select the Provisioning-only option on the first screen, then the data set fields displayed are empty.
However, if there are default fields defined for any of the provisioning-specific providers that you select, then these fields are displayed. For example, the ID field of the Account data set and the objectClass and containerID fields of the Provisioning Staging data set are displayed by default. These fields are discussed later in this guide.
See Also:
The "Multilanguage Support" section of the "Known Issues" chapter for information about limitations related to the display of non-ASCII characters on this screenData Set Categories
The data sets displayed on this screen are categorized as follows:
This category contains the Source data set and its child data sets. This category is displayed only if you select the Reconciliation option on the first screen, regardless of whether or not you select the Provisioning option.
This category contains the Reconciliation Staging data set and its child data sets. This category is displayed only if you select the Reconciliation option on the first screen, regardless of whether or not you select the Provisioning option.
This category contains the User data set, Account data set, and child data sets of the Account data set. This category is displayed, regardless of whether you select only Reconciliation, only Provisioning, or both Reconciliation and Provisioning on the first screen.
The ID field appears by default in the Account data set. This field is used to store the value that uniquely identifies individual records in Oracle Identity Manager and in the target system. For a particular user, this unique field is used to direct other operations, such as modify, delete, enable, disable and child data operations.
During reconciliation, the value of the ID field must come from the corresponding unique field of the Reconciliation Staging data set. To set this up, you must create a mapping between the two fields. The procedure to create a mapping is discussed later in this section.
This category contains the Reconciliation Staging data set and its child data sets. This category is displayed only if you select the Provisioning option on the first screen, regardless of whether or not you select the Reconciliation option.
See Also:
The "Introduction to Generic Technology Connectors" section for conceptual information about these data setsField Mappings
The flow lines displayed on this screen represent the mappings that are based on the metadata detected by the generic technology connector framework. A mapping represents a link between two fields of different data sets. It serves one of the following purposes:
Establishes a data flow path between fields of two data sets, for either provisioning or reconciliation
Creates a basis for comparing (matching) field values of two data sets
The following are examples of matching-only mappings:
Mappings created between fields of the Reconciliation Staging data set and the User data set form the basis of reconciliation rules.
A mapping between the unique field of the Reconciliation Staging data set and the ID field of the Account data set helps identify the key field for reconciliation matching. Along with the ID field, other fields of the Account data set can be (matching-only) mapped to corresponding fields of the Reconciliation Staging data set to create a composite key field for reconciliation matching.
Caution:
Suppose you select both the Provisioning and Reconciliation options while creating a generic technology connector and you do not create a mapping between the ID field and the unique field of the target system. Without this mapping, the records that are linked through reconciliation cannot be used for further provisioning operations, such as modify, delete, enable, disable, and child data operations. This is because the ID field is not populated in the linked records.You can perform the following actions on this screen:
To add a field to a data set:
Click the Add icon for the data set.
Specify values for the following GUI elements:
Field Name: Specify a name for the field. The field name that you specify must not contain non-ASCII characters.
Matching Only: Select this check box if the field is to be used only for matching, and not to propagate values during reconciliation.
Create End-to-End Mapping: Select this check box if you want the same field to appear in the corresponding data sets of all the categories that are displayed to the right of the current category.
Multi-Valued Field: Select this check box if you want to add a child data set.
Data Type: Select the data type of the field.
Length: Specify the character length of the field.
Refer to the "Modify Connector Configuration Screen" section for information about a known issue related to the entry of non-numeric values in this field.
Required: Select this check box if you want to ensure that the field always contains a value.
Encrypted: Select this check box if the value of the field must be encrypted.
Click Continue.
If required, select a validation check for the field and then click Add.
Note:
The screen on which you select a validation check is displayed only when you are adding a field to a data set of the Source category.The validation options displayed in this list are based on the predefined validation providers.
Click Continue, and then click Close.
If you do not want to perform any other action on the Modify Connector Configuration screen, then click the Close button that is displayed at the top of the screen. You must perform Step 5 before you click the Close button.
To edit a field of a data set:
Caution:
The following Caution notice applies if you are performing this procedure to modify a generic technology connector that you have already created.If you modify the field size or field data type value of the Account data set or its child data sets, then corresponding changes are not made in the Oracle Identity Manager database entries for these data sets. At the same time, no error message is displayed.
Therefore, for this release of Oracle Identity Manager, it is recommended that you do not modify the fields or child data sets of the Account data set.
This point has also been discussed in the "Modify Connector Configuration Screen" section of the "Known Issues" chapter.
Click the Edit icon for the field.
Specify values for the following GUI elements:
Note:
The list of GUI elements displayed on this screen depends on the data set to which the field belongs. Some of the following GUI elements may not appear for some data set fields. For example, for fields of the User data set, only the Matching Only GUI element is displayed.Matching Only: Select this check box if the field is to be used only for matching, and not to propagate values during reconciliation.
This check box is selected by default for fields of the User data set.
Data Type: Select the data type of the field.
Length: Specify the character length of the field.
Refer to the "Modify Connector Configuration Screen" section for information about a known issue related to the entry of non-numeric values in this field.
Required: Select this check box if this is a mandatory field.
Encrypted: Select this check box if the value of the field must be encrypted.
Click Continue.
Because it is assumed that you do not want to create a mapping, you need not perform any action on this screen. Alternatively, you can assign a literal value to the field.
Click Continue, and then click Close.
If you do not want to perform any other action on the Modify Connector Configuration screen, then click the Close button that is displayed at the top of the screen. You must perform Step 5 before you click the Close button.
To create or modify a mapping:
Note:
All the fields of data sets in the Provisioning Staging category must be mapped to corresponding fields of data sets in the OIM category.Click the Edit icon for the mapping destination field (not the mapping source field).
For example, if you want to create a mapping between a field of the Source data set and a field of the Reconciliation Staging data set, then click the Edit icon for the field of the Reconciliation Staging data set.
On this screen, you can create one of the following types of mappings:
If you want to use the mapping to define a path for the data to flow from the source field to the destination field, then you need not specify any input.
If you want to use the mapping to compare (match) the values of the source field and the destination field, then select Matching Only. This check box is selected by default for fields of the User data set. You must select this check box while mapping the ID field of the Account data set and the unique field of the Reconciliation Staging data set.
Because you only want to create a mapping, you do not need to specify values for any other GUI elements on this screen.
Click Continue.
Select the source data set and field to which you want to map the field.
Click Continue, and then click Close.
If you do not want to perform any other action on the Modify Connector Configuration screen, then click the Close button that is displayed at the top of the screen. You must perform Step 5 before you click the Close button.
When you create a mapping between two fields, a flow line is displayed between the fields on this screen.
To remove a mapping:
Delete either the source or destination field of the mapping.
Re-create the field that you delete in the previous step.
Re-create any other mapping that may have been removed when you perform the first step.
If you do not want to perform any other action on the Modify Connector Configuration screen, then click the Close button that is displayed at the top of the screen. You must perform Step 5 before you click the Close button.
To remove a field from a data set:
Click the Delete icon for that field.
If you do not want to perform any other action on the Modify Connector Configuration screen, then click the Close button that is displayed at the top of the screen.
Use this screen to specify form names for the process forms corresponding to data sets of the OIM category.
The generic technology connector framework automatically creates certain objects after you submit all the information required to create a generic technology connector. Parent and child process forms corresponding to the data sets of the OIM category are examples of objects that are automatically created. Each process form on a particular Oracle Identity Manager installation must have a unique name.
On this screen, the generic technology connector framework displays default names for these process forms. You must verify and, if required, change the names of these forms to ensure that they are unique for this installation of Oracle Identity Manager. In addition, you must not include non-ASCII characters in the form names. An error message is displayed if you submit non-unique form names or if any name contains non-ASCII characters.
After you specify the form names, click Continue.
Use this screen to review information that you have provided for the creation of the generic technology connector. The following is a screen-wise explanation of the changes that are permitted on the earlier screens:
Step 1: Basic Information screen
You can use either the Change or Back button to reopen this screen. However, due to limitation explained in the "Names of Generic Technology Connectors and Connector Objects" section of the "Known Issues" chapter, you must not revisit this screen to make changes. To make changes in information on this screen, restart the procedure from the beginning and specify a new name for the generic technology connector. Alternatively, if you want to use the same name, then you must restart the application server before you start creating the generic technology connector a second time.
Note:
The User Reconciliation field may be displayed along with the rest of the fields in the Basic Information table. Ignore this field. In future releases, this field will be used to indicate the reconciliation type (trusted/nontrusted) for the connector.Step 2: Define Parameters screen
You can use either the Change or Back button to reopen this screen. You can change parameter values on this screen. However, metadata detection does not take place when you submit the changed values.
Modify Connector Configuration screen
You can use the Change button to reopen this screen and then change data set fields and mappings.
Step 3: Verify Connector Form Names screen.
You cannot revisit this screen.
After you verify all the information displayed on the Step 4: Verify Connector Creation Information screen, click Create.
At this stage, the generic technology connector framework creates all the standard connector objects on the basis of the information that you provide. The list of these objects includes the connector XML file, which is created and imported automatically into Oracle Identity Manager. The names of these objects are the same as the name that you specify for the generic technology connector.
At the end of the process, a message stating that the connector has been successfully created is displayed on the screen.
Note:
If the creation process fails, then objects that are created are not automatically deleted.This point is discussed in the "Connector Objects" section of the "Known Issues" chapter.
Note:
If you select only the Provisioning option on the first screen, then you can skip this section because you need not configure reconciliation.A reconciliation scheduled task is created automatically when you create the generic technology connector. During reconciliation, this scheduled task performs the following steps:
Calls the Reconciliation Transport provider
Calls the Reconciliation Format provider to parse the transported data
Calls the Validation provider on the parsed data
Runs the function that processes the data flow based on mappings defined between the Source category and the Reconciliation Staging category.
Runs the function that generates reconciliation events for the data
You use the Design Console to set up the scheduled task that is created when you create a generic technology connector.
Note:
You can perform this procedure only after you create the generic technology connector.To set up the reconciliation scheduled task:
Open the Design Console.
Expand Administration.
Double-click Task Scheduler.
Click the Search icon.
Click the Task Scheduler Table tab.
To locate the scheduled task that was created as one of the objects of the generic technology connector, click the Scheduled Task column to sort the contents of that column in ascending or descending order.
The name of the scheduled task is the same as the name that you specify for the generic technology connector.
Select the row corresponding to the scheduled task for the generic technology connector.
To specify that you do want to save any changes, click Yes.
Click the Task Scheduler tab.
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 ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are not selected.
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.
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.
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 12.
Refer to the "Other Known Issues" section for information about a known issue related to the status of scheduled tasks.
In the generic technology connector context, configuring provisioning involves the following procedures:
Note:
If you select only the Reconciliation option on the first screen, then you can skip these procedures because you need not configure provisioning.In an application-specific connector, there is one adapter for each provisioning function that the connector supports. For a generic technology connector, there is only one adapter for all the provisioning functions. This adapter is known as a generic adapter. It is one of the objects that are automatically created when you create a generic technology connector. It is created only if you select the Provisioning option, regardless of whether or not you select the Reconciliation option, on the Step 1: Basic Information screen.
During provisioning, the generic adapter performs the following steps:
Runs the function that retrieves process instance data, IT resource data, and user and group assignment data
Calls the Provisioning Format provider to change the format of the data
Runs the function that processes the data flow based on mappings defined between the OIM category and the Provisioning Staging category.
Calls the Provisioning Transport provider to transport the formatted data to the target system
You must compile the generic adapter before it can be used for provisioning.
Note:
You can perform this procedure only after you create the generic technology connector.To compile the generic adapter:
Open the Design Console.
Expand Development Tools.
Double-click Adapter Factory.
Use the Search icon to locate the generic adapter. The name of the generic adapter is the same as the name that you specify for the generic technology connector.
To compile the adapter, click Build.
After the adapter is compiled, the Compile Status field shows the OK status.
If Oracle Identity Manager is installed in a clustered environment, then copy the compiled generic adapter from the OIM_home\xellerate\Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.
Note:
This is an optional step.Refer to Oracle Identity Manager Design Console Guide for conceptual information about process tasks and assignments.
A process definition is one of the objects that are automatically created when you create a generic technology connector. This process definition has the same name as the generic technology connector. The process tasks that constitute this process definition can be divided into two types:
System-defined process tasks
These process tasks are included by default in all newly created process definitions.
Framework-defined process tasks
The generic technology connector framework includes these process tasks in a process definition only if you select the Provisioning option on the "Screen 1: Basic Information" screen, regardless of whether or not you select the Reconciliation option.
The following are framework-defined process tasks:
Create User
Delete User
Enable User
Disable User
Updated Field_Name
This task is created for each field of the Account data set, except the ID field.
In addition, the following framework-defined process tasks are created for each child data set of the Account data set:
Child Table Child_Form_Name row Inserted
Child Table Child_Form_Name row Updated
Child Table Child_Form_Name row Deleted
All framework-defined process tasks have the following default assignments:
Target Type: Group User With Highest Priority
Group: SYSTEM ADMINISTRATORS
User: XELSYSADM
If required, you can modify these default assignments by following the instructions given in the "Modifying Process Tasks" section in Oracle Identity Manager Design Console Guide.
