1 About the Connector

Oracle Identity Manager automates access rights management, security, and provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications.

This guide discusses the procedure to deploy the PeopleSoft Employee Reconciliation connector that is used to integrate PeopleSoft HRMS/HCM with Oracle Identity Manager. This connector provides a means to exchange real-time data between the target system and Oracle Identity Manager.

Note:

In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.

In this guide, PeopleSoft HRMS/HCM has been referred to as the target system.

The PeopleSoft Employee Reconciliation connector enables the target system as an authoritative identity source of Oracle Identity Manager through trusted source reconciliation. The connector supports trusted source reconciliation in two ways:

• Full reconciliation

  Full reconciliation involves reconciling records of employees by using a flat file. A PeopleCode event is activated when employee information is updated in the target system. The PeopleCode then extracts the required employee information. A PeopleSoft Application Engine program then populates the flat file with this information. The flat file is read by an Oracle Identity Manager scheduled task that generates reconciliation events.

  The PeopleSoft Application Engine program is run using PeopleSoft Application Designer or PeopleSoft Internet Architecture (PIA).

  To reconcile all existing target system records into Oracle Identity Manager, you must run full reconciliation the first time you perform a reconciliation run after deploying the connector. This is to ensure that the target system and Oracle Identity Manager contain the same data. In subsequent reconciliation runs, only data that is modified since the last reconciliation is reconciled. Oracle recommends that you run full reconciliations periodically to ensure that all the employee records are reconciled into Oracle Identity Manager. See "Configuring the Target System for Full Reconciliation" for more information.

• Incremental reconciliation

  Incremental reconciliation involves real-time reconciliation of newly created or modified employee information. Usually, this type of reconciliation is used for reconciling individual data changes after an initial reconciliation is performed using full reconciliation. The PeopleCode captures changes to the same PeopleSoft components as applicable for full reconciliation and forwards these changes in real time to a Java Servlet listener running on the Oracle Identity Manager server through an HTTP POST request. Incremental reconciliation is performed using PeopleSoft application messaging. See "Configuring the Target System for Incremental Reconciliation" for more information.

  The synchronization process from the target system to Oracle Identity Manager involves the following steps:

  1. When employee information is added or updated in the target system, a PeopleCode event is activated.

  2. The PeopleCode event generates an XML message containing the added or updated employee information and sends it to the connector by using HTTP.

  3. The connector parses the XML message and sends a reconciliation event to Oracle Identity Manager.

This chapter contains the following sections:

• Employee Data Reconciliation

• Supported Functionality

• Multilanguage Support

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

1.1 Employee Data Reconciliation

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about reconciliation configurations

The following target system fields must be reconciled:

• EmplID

• First Name

• Last Name

• Organization

• User Type

• Employee Type

You can also configure reconciliation for the following fields of the target system. To do so, you must define custom attributes for each field in Oracle Identity Manager.

• BirthDate

• Sex

• City

• SSN

• Phone

• Country

• Address

• State

• DeptId

• JobCode

• Postal

• HireDate

For information about adding custom attributes, see "Adding Custom Attributes for Full Reconciliation".

1.2 Supported Functionality

Table 1-1 lists the functions that are available with this connector.

Table 1-1 Supported Functionality

Function	Type	Description
Trusted Employee Reconciliation	Reconciliation	Reconciles newly added or modified employee data from the target system to Oracle Identity Manager.

See Also:

Appendix A for information about attribute mappings between Oracle Identity Manager and the target system.

1.3 Multilanguage Support

The connector supports the following languages:

• Arabic

• Chinese Simplified

• Chinese Traditional

• Danish

• English

• French

• German

• Italian

• Japanese

• Korean

• Portuguese (Brazilian)

• Spanish

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

1.4 Files and Directories That Comprise the Connector

The files and directories that comprise this connector are compressed in the following directory on the installation media:

Enterprise Applications/PeopleSoft Enterprise Applications/PeopleSoft Employee Reconciliation

These files and directories are listed in the following table:

File in the Installation Media Directory	Description
config/configureReconciliation.properties	This file contains the date format used for full reconciliation. The date format is used on both the PeopleSoft server and Oracle Identity Manager.
config/attributemapping_recon.properties	This file lists the target system attributes and their mappings to corresponding fields in Oracle Identity Manager.
ext/csv.jar	This file is a third-party library that is used to read comma-separated files.
lib/xlPSFTHRRecon.jar	This JAR file contains the class files that are used to implement full reconciliation.
lib/peopleSoftApp.war	This Web Archive (WAR) file contains the classes and configuration files required to implement incremental reconciliation.
For PeopleTools 8.22, the following file in the lib/MsgPublisher directory: xliMsgPublisher.jar	This JAR file contains the class file that transfers the XML messages generated by the PeopleTools 8.22 file handler on the PeopleSoft Web server to the PeopleSoft connector.
For PeopleTools 8.22, the following file in the scripts directory: publish.bat	The publish.bat file is used to trigger message transfers on a periodic basis. Refer to the "Configuring PeopleSoft Integration Broker" section for more information.
For PeopleTools 8.22: PeopleCode/PT822/HRMSCBRecon.txt For PeopleTools 8.45 through 8.47: PeopleCode/HRMSCBRecon_8.45-8.47.txt For PeopleTools 8.48: PeopleCode/HRMSCBRecon_8.48.txt	This file contains the PeopleCode that you must add to the SavePostChange event while performing the procedure described in the "Publishing the Message" section.
For PeopleTools 8.22: PeopleCode/PT822/HRMSBulkRecon.txt For PeopleTools 8.45 through 8.48: PeopleCode/HRMSBulkRecon.txt	This file contains the PeopleCode that gets executed during full reconciliation to generate the flat file.
Files in the resources directory	Each of these resource bundle files contains language-specific information that is used by the connector. Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.
test/cbrecon/psft-xel-test.vbs	This VBScript file can be used to test the incremental reconciliation functionality of the connector by creating a dummy XML message similar to the ones created by the target system.
test/cbrecon/pingRequest.xml test/cbrecon/pingResponse.xml test/cbrecon/publishRequest.xml test/cbrecon/publishResponse.xml	These XML files are required by the psft-xel-test.vbs file for communicating with the connector by using XML over HTTP.
test/cbrecon/psft_xellerate_msg.xml	This XML file is used by the psft-xel-test.vbs file to define the template of the XML message that is received from the target system.
xml/adpPSFT_RECON_DM.xml	This XML file contains definitions for the following components of the connector: Resource object Process definition IT resource type Reconciliation rules Scheduled tasks Process form
xml/adpPSFT_XellerateUser_RECON_DM.xml	This XML file contains the configuration information for the Xellerate User resource object. You must import this file after you import the adpPSFT_RECON_DM.xml file. This XML file contains definitions for the following components of the connector: Resource object Process definition Scheduled tasks Process form

The "Step 2: Copying the Connector Files and External Code Files" section provides instructions to copy these files into the required directories.

1.5 Determining the Release Number of the Connector

You can use the following method to determine the release number of a PeopleSoft Employee Reconciliation connector.

1. Extract the contents of the xlPSFTHRRecon.jar file. This file is in the following directory on the installation media:

   Enterprise Applications/PeopleSoft Enterprise Applications/PeopleSoft Employee Reconciliation/lib
   

2. Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the xlPSFTHRRecon.jar file.

   In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.

Note:

If you maintain a copy of the xlPSFTHRRecon.jar file after deployment, you can use this method whenever you want to determine the release number of the connector. After you deploy the connector, Oracle recommends that you use the "After Deployment" method, which is described in the following section.