Click Continue. If required, select a validation check for the field and click Add. In other Click Continue, and click Close.

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. 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.