Role of Providers During Provisioning

Creating Custom Providers for Generic Technology Connectors 20-9 target system supports the output data format of Oracle Identity Manager, you must include the provisioning format provider when you create the generic technology connector. ■ You must create custom providers only to address provider requirements that are not addressed by the predefined providers. The types of providers you must include in the generic technology connector depend on the data formats and data transport mechanisms that your target system supports. If any combination of the data formats and data transport mechanisms are compatible with any combination of the predefined providers, you need not create custom providers. For example, if your target system is a Web service that can accept and parse SPML-based provisioning requests packaged in SOAP messages, you can use the SPML provisioning format provider and Web Services provisioning transport provider. You need not create custom provisioning providers.

20.2.2 Identifying the Provider Parameters

Provider parameters are the values that a provider must have in order to perform its intended function. For example, a provisioning transport provider that copies provisioning request files to a target system server will need the connection parameters required to connect to the target system. While creating a generic technology connector, you specify values for the parameters of the providers that you select for the generic technology connector. For the custom provider that you are creating, you must identify all the parameters required for the provider to function. You must also categorize these parameters as run-time and design parameters. A run-time parameter represents a value that is not constrained by the design of the provider. For example, the location of the directories containing data files that you want to reconcile is a run-time parameter. A design parameter represents a value or set of values that is defined as part of the provider design. For example, the character set encoding formats that can be parsed by a reconciliation format provider are a design parameter for that provider.

20.2.3 Developing Java Code Implementations of the Value Objects

Develop the Java code implementations of the value objects listed in Table 20–1 . As described earlier, these value objects are used at various stages of provider operations. See Also: Reusing Providers on page 20-15 Note: You need not develop Java code implementations of the value objects that you are not going to include in the generic technology connector. Table 20–1 Value Objects Used During Provider Operations Area of Use Value Object Javadocs Package Metadata Detection TargetSchema com.thortech.xl.gc.vo.designtime OIMSchema com.thortech.xl.gc.vo.designtime Provisioning TargetOperation com.thortech.xl.gc.vo.runtime 20-10 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager

20.2.4 Developing Java Code Implementations of the Provider SPI Methods

Develop the Java code implementations of the SPI methods that are used during provider operations. As described earlier, these SPI methods are called at various stages of provider operations. See the Package com.thortech.xl.gc.spi page of the Javadocs for links to information about the SPI methods of each provider.

20.2.5 Developing Java Code for Logging and Exception Handling

Oracle recommends that you to incorporate logging in the Java code implementations of the value objects and SPI methods. By doing this, you can simplify troubleshooting errors that may occur when you use the providers. The logging modules for the generic technology connector framework are an extension of the logging functionality of Oracle Identity Manager. Table 20–2 lists the modules that are specific to the supported provider types. See Oracle Fusion Middleware Java API Reference for Oracle Identity Manager for information about incorporating exception handling in the custom provider.

20.2.6 Creating the Provider XML File

The provider XML file contains the data required to register the provider with the generic technology connector framework. You must create the provider XML file. Table 20–3 describes the elements that you can include in the provider XML files for custom providers. Reconciliation TargetRecord com.thortech.xl.gc.vo.runtime OIMRecord com.thortech.xl.gc.vo.runtime Note: You need not develop Java code implementations of SPI methods for the providers that you are not going to include in the generic technology connector. Table 20–2 Logging Modules Specific to the Supported Provider Types Logging Module Functional Module of the Generic Technology Connector Framework XELLERATE.GC.PROVIDER.PROVISIONINGFORMAT Provisioning format provider XELLERATE.GC.PROVIDER.PROVISIONINGTRANSPORT Provisioning transport provider XELLERATE.GC.PROVIDER.RECONCILIATIONTRANSPORT Reconciliation transport provider XELLERATE.GC.PROVIDER.RECONCILIATIONFORMAT Reconciliation format provider XELLERATE.GC.PROVIDER.TRANSFORMATION Transformation Provider XELLERATE.GC.PROVIDER.VALIDATION Validation Provider Note: You can use a single provider XML file to define any number of providers. Alternatively, you can create a provider XML file for each provider that you create. Table 20–1 Cont. Value Objects Used During Provider Operations Area of Use Value Object Javadocs Package