Validation Providers Oracle Fusion Middleware Online Documentation Library

Creating Custom Providers for Generic Technology Connectors 20-3 3. The getMetadata method of the reconciliation transport provider is called to fetch metadata from the target system. The output of this method is the TargetSchema value object containing metadata fetched from the target system. 4. The parseMetadata method of the reconciliation format provider is called to parse metadata fetched from the target system. The output of this method is the OIMSchema value object containing metadata fetched from the target system. 5. The initialize method of the provisioning transport provider is called to create an instance of that provider. 6. The initialize method of the provisioning format provider is called to create an instance of that provider. 7. If the reconciliation transport provider and reconciliation format provider are not able to detect metadata, Steps 1 through 4 are repeated for the provisioning transport provider and provisioning format provider. The shared drive reconciliation transport provider and CSV reconciliation format provider can detect metadata from the target system. However, this function is not supported for the Web Services provisioning transport provider and SPML provisioning format provider.

20.1.2 Role of Providers During Reconciliation

Figure 20–2 shows the role of providers during reconciliation. Note: The OIMSchema value object corresponds to the Source data sets discussed in Section 18.2.1, Providers and Data Sets of the Reconciliation Module . Note: After a provider is initialized, it is stored in the Oracle Identity Manager cache until any one of the following events occurs: ■ Cache is purged. ■ Oracle Identity Manager is restarted. ■ The generic technology connector is modified after it is created. The validation providers and transformation providers are instantiated only when they are needed. They are not stored in cache. 20-4 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager Figure 20–2 Role of Providers During Reconciliation The following steps describe the role of providers during reconciliation:

1. If an instance of the reconciliation transport provider is not available in cache, the

initialize method is called to create an instance of that provider.

2. If an instance of the reconciliation format provider is not available in cache, the

initialize method is called to create an instance of that provider.

3. While using the Administrative and User Console to create a generic technology

connector, you can specify a batch size for the reconciliation run. By using this parameter, you break the total number of records that the reconciliation engine fetches from the target system, during each reconciliation run, into batches. The default value of this parameter is All. Creating Custom Providers for Generic Technology Connectors 20-5 If you do not specify a batch size, at this stage of reconciliation, the getFirstPage method of the reconciliation transport provider is called to fetch the entire set of target system records that are ready for reconciliation. If you specify a batch size, the getFirstPage method of the reconciliation transport provider is called to fetch the first batch of target system records for reconciliation. The getNextPage method of the same provider is called multiple times, if required if there are more batches of target system records for reconciliation. 4. The parseRecords method of the reconciliation format provider is called to process each record of the TargetRecord value objects array. The output of this method is an array of OIMRecord value objects. 5. While creating the generic technology connector, if you select validation providers to validate data while it is in transit from the Source data sets to the reconciliation staging data sets: a. An instance of the validation provider is created. b. The validate method of each validation provider is run on the specified attribute of each record of the OIMRecord value objects array. If you do not select validation providers while creating the generic technology connector, Step 5 is not performed and each element of the OIMRecord value objects array is passed on to Step 6. 6. While creating the generic technology connector, if you selected transformation providers to modify data that is in transit from the Source data sets to the reconciliation staging data sets: a. An instance of the transformation provider is created. b. The transformData method of the transformation providers processes the OIMRecord value objects array that was generated as the output of one of the following: – The validate method of each validation provider if you selected validation providers – The parseRecords method of the reconciliation format provider if you did not select validation providers If you do not select transformation providers while creating the generic technology connector, Step 6 is not performed and each element of the OIMRecord value objects array from the previous step Step 4 or 5 is passed on to Step 7. 7. At this stage, the OIMRecord value objects array corresponds to the reconciliation staging data sets discussed in Section 18.2.1, Providers and Data Sets of the Reconciliation Module . Each element of the OIMRecord value objects array is passed on to the reconciliation engine. 8. At the end of the reconciliation procedure, the end method of the reconciliation transport provider is called. This method returns a string value, which the generic technology connector framework stores in the Timestamp parameter of the IT resource. The framework uses the Timestamp parameter to track the stage at which the reconciliation run was completed.

20.1.3 Role of Providers During Provisioning