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. The connector for PeopleSoft Employee Reconciliation is used to integrate Oracle Identity Manager with PeopleSoft Employee Reconciliation.

Note:

Oracle Identity Manager connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.

This chapter contains the following sections:

• Supported Functionality

• Multilanguage Support

• Employee Data Reconciliation

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

Note:

In this guide:

• Each occurrence of "PeopleTools 8.22" refers to the entire range of PeopleTools releases from 8.10 through 8.22.

• Each occurrence of "PeopleTools 8.4x" refers to the entire range of PeopleTools releases from 8.40 through 8.46.

Supported Functionality

The following table lists the functions that are available with this connector.

Function	Type	Description
Trusted Employee Reconciliation	Reconciliation	Reconciles employee data from PeopleSoft Employee Reconciliation to Oracle Identity Manager. A corresponding user is created in Oracle Identity Manager. If the user already exists in Oracle Identity Manager, then this user is updated.
Nontrusted Employee Reconciliation	Reconciliation	Reconciles employee data from PeopleSoft Employee Reconciliation to Oracle Identity Manager. A user is not created in Oracle Identity Manager.

See Also:

Appendix A for information about attribute mappings between Oracle Identity Manager and PeopleSoft Employee Reconciliation.

Multilanguage Support

This release of the connector supports the following languages:

• English

• Brazilian Portuguese

• French

• German

• Italian

• Japanese

• Korean

• Simplified Chinese

• Spanish

• Traditional Chinese

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

Employee Data Reconciliation

The connector supports employee data reconciliation in two ways:

• Bulk reconciliation (first-time reconciliation)

  Bulk reconciliation involves reconciling records of existing employees using a flat file. The flat file is generated using an Application Engine program written in PeopleCode. This program is run using PeopleSoft Application Designer.

• Change-based reconciliation

  In change-based reconciliation, data for any newly created or updated employee is reconciled instantaneously. This type of reconciliation is performed using the PeopleSoft Application Messaging mechanism.

  Change-based reconciliation involves the use of:

  • A PeopleCode trigger, which generates an XML message containing updated information

  • Attribute definitions (usually resource parameters) to be synchronized

  • A Web service that acts as a passive listener for XML messages from PeopleSoft

  • An XML file, psft_xellerate_msg.xml, that defines the schema of the XML message received from PeopleSoft

  The synchronization process from PeopleSoft Employee Reconciliation to Oracle Identity Manager involves the following steps:

  1. Employee information is updated in PeopleSoft Employee Reconciliation. This activates a PeopleCode trigger.

  2. The PeopleCode trigger generates an XML message containing the updated employee information and sends it to the listener for the PeopleSoft Employee Reconciliation connector.

  3. The listener forwards the XML message to the PeopleSoft Employee Reconciliation connector using HTTP.

  4. The PeopleSoft Employee Reconciliation connector receives the XML message and sends a reconciliation event to the Oracle Identity Manager.

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

The following table lists the files and directories that comprise the connector.

File in the Installation Media Directory	Description
lib\xlPSFTHRRecon.jar	This JAR file contains the class files that are used to implement bulk reconciliation.
lib\peopleSoftApp.war	This WAR file contains the classes and configuration files required for the PeopleSoft listener Web application. This file is used to implement change-based reconciliation.
For PeopleTools 8.22, the following files in the MsgPublisher directory: xliMsgPublisher.jar publish.bat	The 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 listener servlet. The publish.bat file is a Windows batch file that triggers the message transfer on a periodic basis. Refer to the "Configuring PeopleSoft Enterprise Portal" section for more information.
For PeopleTools 8.22: PeopleCode\PT822\HRMSCBRecon.txt For PeopleTools 8.4x: PeopleCode\HRMSCBRecon.txt	This file contains the code that you must add to the PeopleCode for theSavePostChange event while performing the "Publishing the Message" procedure described in the "Creating and Publishing the Message" section.
For PeopleTools 8.22: PeopleCode\PT822\HRMSBulkRecon.txt For PeopleTools 8.4x: PeopleCode\HRMSBulkRecon.txt	This file contains the code for the Application Engine program. It is used to generate the flat file for bulk reconciliation.
properties\configureReconciliation.properties	This file is used to specify the date format used for reconciliation.
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\psft-xel-test.vbs	This VBScript file can be used to test the PeopleSoft listener Web service by creating XML messages similar to the ones created by PeopleSoft Employee Reconciliation.
test\pingRequest.xml test\pingResponse.xml test\publishRequest.xml test\publishResponse.xml	These XML files are required by the psft-xel-test.vbs file for communicating with the PeopleSoft listener Web service using XML over HTTP.
test\psft_xellerate_msg.xml	This XML file is used by the psft-xel-test.vbs file to define the schema of the XML message that is received from PeopleSoft Employee Reconciliation.
ThirdParty\csv.jar	The csv.jar file is a third-party library that is used to read comma-separated files.
XML\adpPSFT_RECON_DM.xml	This XML file contains definitions of the following components of the connector: Resource object Process definition Process tasks Custom Process Form
XML\adpPSFT_XellerateUser_RECON_DM.xml	This XML file contains the configuration for the Xellerate User. You must import this file only if you plan to use the connector in trusted source reconciliation mode.

Note:

The files in the test directory are used only to run tests on the connector.

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

Determining the Release Number of the Connector

To determine the release number of the connector that you have deployed:

1. Extract the contents of the xlPSFTHRRecon.jar file. For a connector that has been deployed, this file is in the following directory:

   OIM_home\xellerate\JavaTasks
   
   

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.

See Also:

Oracle Identity Manager Design Console Guide