In the Lookup Code Name region, select Literal and enter the name of the

Predefined Providers for Generic Technology Connectors 19-21 a. For target resource reconciliation, click the edit icon for the OIM Object Status field of the OIM - Account data set. For target resource reconciliation, click the edit icon for the Status field of the OIM - User data set. b. On the Step 1: Field Information page, specify values for the following GUI elements: – Mapping Action: Select Create Mapping Without Transformation from this list. – Matching Only : Ensure that this check box is deselected.

c. Click Continue.

d. In the Input region on the Step 3: Mapping page, select the status field of the reconciliation staging data set. e. Click Continue, Continue, and click Close. f. To add or edit other fields displayed on the Step 3: Modify Connector Configuration page, continue with the procedure described in Section 21.2.4.3.1, Adding or Editing Fields in Data Sets .

19.6 Validation Providers

Table 19–1 describes the validation providers that are shipped with this release of Oracle Identity Manager. Note: These steps are a condensed version of the procedure described in Section 21.2.4.3.1, Adding or Editing Fields in Data Sets . Note: If a mapping already exists between the status field of the reconciliation staging data set and the OIM Object Status field or Status field, apply the instructions given in this step only where required. Note: Except for the Validate Date Format provider, all the providers in this table are implementations of methods of the GenericValidator class in the Apache Jakarta Commons API. Table 19–1 Validation Providers Validation Provider Description IsBlankOrNull Returns true if the field value is null and is not blank IsInRange Returns true if the field value is within a range specified by a minimum and maximum value pair IsByte Checks if the field value can be converted to a byte primitive IsDouble Checks if the field value can be converted to a double primitive IsFloat Checks if the field value can be converted to a float primitive IsInteger Checks if the field value can be converted to an integer primitive 19-22 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager IsLong Checks if the field value can be converted to a long primitive IsShort Checks if the field value can be converted to a short primitive MatchRegexp Checks if the field value matches the specified regular expression Note: A regular expression is a string that is used to describe or match a set of strings according to specific syntax rules. MaxLength Checks if the length of the field value is less than or equal to the specified value MinLength Checks if the length of the field value is greater than or equal to the specified value Validate Date Format Validates date values in target system records before these records are reconciled into Oracle Identity Manager The value of the Source Date Format parameter is used as the basis for validation. This validation provider is applied if you specify a value for the Source Date Format parameter on the Step 2: Specify Parameter Values page, regardless of whether or not you select this provider on the Step 3: Modify Connector Configuration page. Note: Unlike the other providers in this table, the Validate Date Format is not an implementation of a method of the GenericValidator class in the Apache Jakarta Commons API. Table 19–1 Cont. Validation Providers Validation Provider Description 20 Creating Custom Providers for Generic Technology Connectors 20-1 20 Creating Custom Providers for Generic Technology Connectors You will need to create custom providers to address provider requirements that cannot be addressed by the predefined providers. This chapter discusses the steps to create custom providers. Topics in this chapter include: ■ Role of Providers ■ Creating Custom Providers ■ Reusing Providers ■ Deploying the Custom Providers

20.1 Role of Providers

The following sections discuss the role of providers during generic technology connector creation and use: ■ Role of Providers During Generic Technology Connector Creation ■ Role of Providers During Reconciliation ■ Role of Providers During Provisioning

20.1.1 Role of Providers During Generic Technology Connector Creation

You create a generic technology connector by using the Administrative and User Console. Defining data sets and the flow of data between these data sets is one of the tasks of the connector creation procedure. The metadata detection process facilitates this task. In the generic technology connector context, the term metadata refers to the set of identity fields that constitute the user account information. The term metadata detection refers to the reading and parsing of target system metadata by the providers. The metadata detection feature is supported for all the provider types. In other words, when you create a custom provider, you can incorporate into the provider the capability to read metadata. Note: The Javadocs use the term metadata definition instead of metadata detection . 20-2 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager Figure 20–1 shows the metadata detection process. Figure 20–1 Metadata Detection Process The following sequence of steps describe the process of metadata detection. This sequence of steps is based on the assumption that you select both the Reconciliation and Provisioning options while creating the generic technology connector. If you do not select either option, the corresponding steps are not performed. 1. The initialize method of the reconciliation transport provider is called to create an instance of that provider. 2. The initialize method of the reconciliation format provider is called to create an instance of that provider. See Also: Oracle Fusion Middleware Java API Reference for Oracle Identity Manager for detailed information about the SPI methods and value objects mentioned in the following steps. In the Javadocs, the terms metadata detection and metadata definition have been used interchangeably.