Web Services Provisioning Transport Provider

19-16 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager The following procedure describes how to add a concatenation transformation provider while creating a generic technology connector: On the Step 2: Mapping page in the pop-up window, perform the following steps:

1. From the Dataset list in the Input 1 region, select the data set containing the first

field that you want to concatenate. From the Field Name list, select the first field. Alternatively, you can use the Literal option to specify a literal or fixed value as the first concatenation input. For the example described earlier, from the Dataset list in the Input 1 region, select the data set containing the First Name field. Then, from the Field Name list, select First Name .

2. From the Dataset list in the Input 2 region, select the data set containing the

second field that you want to concatenate. Then, from the Field Name list, select the second field. Alternatively, you can use the Literal option to specify a literal or fixed value as the second concatenation input. For the example described earlier, from the Dataset list in the Input 2 region, select the data set containing the Last Name field. Then, from the Field Name list, select Last Name .

19.5.2 Translation Transformation Provider

A translation operation involves accepting a certain literal value as input and converting it into another value. The following example illustrates a translation operation: Suppose the Source data set contains the Country field and data values stored in this field can take one of the following values: ■ Austria ■ France ■ Germany ■ India ■ Japan When these values are propagated to the reconciliation staging data set, you want to convert these values to the following: ■ AT ■ FR Note: As shown in the preceding example, the concatenation transformation provider adds a space between the values of the two input fields. Note: This procedure explains in detail the instruction given in Step 5 of Section 21.2.4.3.1, Adding or Editing Fields in Data Sets . It is assumed that you have already selected the Concatenation option from the Mapping Action list on the Step 1: Field Information page and that you have performed Steps 2 and 3 given in that section. Predefined Providers for Generic Technology Connectors 19-17 ■ DE ■ IN ■ JP To automate this translation, you can use the translation transformation provider. To use the translation transformation provider: 1. Use the Design Console to create a lookup definition that stores the input and decoded values. For the Country field example described earlier, the Code Key and Decode values are as shown in the following table. 2. Define a transformation translation mapping between the input field and output field for the translation. As mentioned earlier, a transformation can be set up between the following pairs of data sets: ■ Source and Reconciliation Staging ■ Oracle Identity Manager and Provisioning Staging

a. On the Step 3: Mapping page, from the Dataset list in the Input region, select

the data set containing the field that will provide the input value for the translation operation. Then, from the Field Name list, select the field itself. For the Country field example described earlier, select the data set containing the Country field and select the Country field.

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

lookup definition that you create in the preceding step. See Also: Section 15.2.1, Creating a Lookup Definition Note: While creating a lookup definition in the Lookup Definition form, you must select the Lookup Type option, and not the Field Type option. Code Key Decode Austria AT France FR Germany DE India IN Japan JP Note: This procedure explains in detail the instruction given in Step 5 of Section 21.2.4.3.1, Adding or Editing Fields in Data Sets . It is assumed that you have already selected the Concatenation option from the Mapping Action list on the Step 1: Field Information page and that you have performed Steps 2 and 3 given in that section. 19-18 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager For the Country field example described earlier, select Literal and select the lookup definition you create in Step 1.

19.5.2.1 Configuring Account Status Reconciliation

User account status information is used to track whether or not the owner of a target system account is to be allowed to access and use the account. If required, you can use the translation transformation provider to reconcile account status information. You need to use the translation transformation provider only if account status values used in the target system are not the same as the values used in Oracle Identity Manager. For a target resource, Oracle Identity Manager uses the following values: ■ Enabled state: Enabled ■ Disabled state: Disabled For a trusted source, Oracle Identity Manager uses the following values: ■ Enabled state: Active ■ Disabled state: Disabled The procedure to configure account status reconciliation can be summarized as follows: 1. Create a lookup definition that maps the status values used in the target system with the values used in Oracle Identity Manager. 2. While creating the generic technology connector, use the translation transformation provider to create a transformation mapping between the fields that hold account status values in the Source data set and the reconciliation staging data set. The following example describes the action that you must perform: Suppose the following fields are used to hold account status values: ■ The User Status field of the Source data set holds the values True for a user in the Enabled state and False for a user in the Disabled state. ■ The User Status field of the reconciliation staging data set must hold one of the following pairs of values: Note: You must not specify a data set name and field in the Lookup Code Name region. Although there is no validation to stop you from selecting a data set name and field, the translation operation would fail during actual reconciliation or provisioning operations. This point is also mentioned in the Mappings section . Note: The Design Console offers an alternative method to configure account status reconciliation. This method does not involve the use of a generic technology connector. Section 12.3.2.2.1, User Account Status Reconciliation describes this method. Note: Detailed instructions to perform these steps are provided later in this section. Predefined Providers for Generic Technology Connectors 19-19 – For target resource reconciliation, the field must hold Enabled or Disabled . – For trusted source reconciliation, the field must hold Active or Disabled . You must create a transformation mapping that converts the TrueFalse values in the User Status field of the Source data set into corresponding EnabledDisabled or ActiveDisabled values. During reconciliation, these converted values are sent to the User Status field of the reconciliation staging data set. 3. Create a mapping between the field that holds account status values in the reconciliation staging data set and one of the following fields: ■ The OIM Object Status field of the OIM – Account data set, for target resource reconciliation ■ The Status field of the OIM – User data set, for trusted source reconciliation During reconciliation, this mapping is used to propagate status values from the reconciliation staging data set to the OIM – Account or OIM – User data set. Detailed steps to configure account status reconciliation are as follows: 1. Create a lookup definition that maps the status values used in the target system with the values used in Oracle Identity Manager. The Code Key values in the lookup definition must be the same as the values used to represent the account status in the target system. The Code Key and Decode values for both trusted and target resource reconciliation are as shown in the following table: Examples of Code Key values are TrueFalse, YesNo, and 10. The Decode values must be set to the exact value, including the case uppercase and lowercase, shown in the table. 2. The procedure to create the generic technology connector is described in Chapter 21, Creating and Managing Generic Technology Connectors . While creating the generic technology connector, perform the following steps on the Step 3: Modify Connector Configuration page: See Also: Section 15.2, Lookup Definition Form Code Key Decode for Trusted Source Reconciliation Decode for Target Resource Reconciliation Target system status value for a user account that is in the Enabled state Active Enabled Target system status value for a user account that is in the Disabled state Disabled Disabled Note: While creating the lookup definition in the Lookup Definition form, you must select the Lookup Type option, and not the Field Type option.