Configuring Validation of Data during Reconciliation -PSFT_ER-11.1.1.5.0

Configuring Validation of Data during Reconciliation -PSFT_ER-11.1.1.5.0

You can configure validation of reconciled single-valued data according to your requirements. 

For example, you can validate data fetched from the First Name attribute to ensure that it does not contain the number sign (#). 

In addition, you can validate data entered in the First Name field on the user form so that the number sign (#) is not sent to Oracle Identity Manager during reconciliation operations. 

To configure validation of data:

1.   Write code that implements the required validation logic in a Java class. You must create a class with the following signature: 
      public boolean validate(HashMap arg0, HashMap arg1, String arg2 )
        In this signature code

•    arg0 contains primary table field values
•    arg1 contains child table field values
•    arg2 is the field on which validation needs to be done     

The following sample validation class checks if the value in the First Name attribute contains the  number sign (#):

package com.validate;

import java.util.*;

 public class MyValidation { public boolean validate(HashMap hmUserDetails, HashMap hmEntitlementDetails, String field) 
{
/* * You must write code to validate attributes. Parent
* data values can be fetched by using hmUserDetails.get(field)
* For child data values, loop through the
 * ArrayList/Vector fetched by hmEntitlementDetails.get("Child Table")
* Depending on the outcome of the validation operation,
* the code must return true or false.
*/
/* * In this sample code, the value "false" is returned if the field
* contains the number sign (#). Otherwise, the value "true" is * returned.
*/
boolean valid=true;
 String sFirstName=(String) hmUserDetails.get(field);
 for(int i=0;i<sFirstName.length();i++){
 if (sFirstName.charAt(i) == '#'){
 valid=false;
 break;
 }
 }
 return valid;
 }
 } /* End */

2. Create a JAR file to hold the Java class.
3. Run the Oracle Identity Manager Upload JARs utility to post the JAR file created in Step 2 to the Oracle Identity Manager database. This utility is copied into the following location when you install Oracle Identity Manager: 

For Microsoft Windows:

OIM_HOME/server/bin/UploadJars.bat

For UNIX:

OIM_HOME/server/bin/UploadJars.sh 

When you run the utility, you are prompted to enter the login credentials of the Oracle Identity Manager administrator, URL of the Oracle Identity Manager host computer, context factory value, type of JAR file being uploaded, and the location from which the JAR file is to be uploaded. Specify 1 as the value of the JAR type.

4. If you created the Java class for validating a process form field for reconciliation, then:

• Log into the Design Console.
• Search for and open the message-specific configuration lookup definition. For example, locate the Lookup.PSFT.Message.WorkForceSync.Configuration lookup definition for the WORKFORCE_SYNC message. 
• Check for the parameter Validation Lookup Definition in this lookup definition. The Decode value specifies the name of the validation lookup. In this example, the Decode value is  Lookup.PSFT.HRMS.WorkForceSync.Validation

 

In the Code Key column, enter First Name. In the Decode column, enter com.validate.MyValidation. Here, the Code Key value specifies the column name of the field you  want to validate. The Decode value is the complete package name of the Java class that  has the   validation logic.

•  Save the changes to the lookup definition.
•  Search for and open the message-specific configuration lookup definition, in this example, the  Lookup.PSFT.Message.WorkForceSync.Configuration lookup definition.
•  Set the value of the Use Validation  entry to yes.
•  Save the changes to the lookup definition.

5.  Remove the PeopleSoftOIMListener.ear file from the application server.
6. Copy the validation JAR file created in Step 2 to the following directory:
 
     CONN_HOME/listener/deployable-archive/PeoplSoftOIMListener.ear/PeoplSoft OIMListener.war/WEB-INF/lib

 
7. Redeploy the PeopleSoftOIMListener.ear file on the application server. To do so, run the following command: 

          ant redeploy  (or)

   Redeploy the application in the web logic console 

1.   Login web logic console and Lock & Edit
2.   Go to Services - Deployments- PeopleSoftOIMListener - Update
3.    Activate Lock and Edit