Skip Headers
Oracle® Identity Manager Connector Guide for PeopleSoft Employee Reconciliation
Release 9.0.2
Part Number B32166-01
Go to Documentation Home
Home		 Go to Table of Contents
Contents		 Go to Index
Index
Go to previous page
Previous		 Go to next page
Next
View PDF

2 Deploying the Connector

Deploying the connector involves the following steps:

If you want to configure the connector for multiple installations of PeopleSoft Employee Reconciliation, then perform the following procedure:

Step 1: Verifying Deployment Requirements

To verify deployment requirements for the PeopleSoft Employee Reconciliation connector:

  1. Ensure that your environment meets the requirements listed in the following table.

    Item Requirement
    Oracle Identity Manager Oracle Identity Manager release 8.5.3 or later
    Target system The target system can be any one of the following:

    • PeopleSoft HRMS 8.3 SP 1

    • PeopleSoft HRMS 8.9

    Ensure that the following components are installed and configured:

    • Tuxedo and Jolt (the application server)

    • PeopleSoft Internet Architecture

    • PeopleSoft Application Designer (2-tier mode)
    External code The external code requirement consists of the following files:

    • HRMSBulkRecon.txt

    • HRMSCBRecon.txt

    Refer to "Step 2: Copying the Connector Files and External Code" for more information about these files.

  2. Ensure that you have administrative rights on the PeopleSoft Employee Reconciliation server to perform the following procedures:

    • Create a new message node

    • Configure PeopleSoft Enterprise Portal

    • Add a routing rule to publish messages

Step 2: Copying the Connector Files and External Code

The files to be copied and the directories to which you must copy them are given in the following table.


Note:

The directory paths given in the first column of this table correspond to the location of the connector files in the following ZIP file on the installation media: 
Enterprise Applications\PeopleSoft Enterprise Applications\PeopleSoft Employee Reconciliation Rev 3.2.0.zip

Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.

File in the Installation Media Directory Destination Directory
Files in the XML directory 
OIM_home\xlclient

lib\peopleSoftApp.war

OIM_home\xlclient\lib

lib\xlPSFTHRRecon.jar

OIM_home\xellerate\ScheduleTask

lib\ThirdParty\csv.jar

OIM_home\xellerate\ThirdParty
Files in the test directory 
OIM_home\xellerate\test
For PeopleTools 8.22, copy the files from the PeopleCode\PT822 directory

For PeopleTools 8.4x, copy the files from the PeopleCode directory

 
OIM_home\xellerate\Scripts
Note: You must copy the files for either PeopleTools 8.22 or PeopleTools 8.4x, not both.
For PeopleTools 8.22, copy the files from the resources\PT822 directory

For PeopleTools 8.4x, copy the files from the resources directory

 
OIM_home\xellerate\connectorResources
Note: You must copy the files for either PeopleTools 8.22 or PeopleTools 8.4x, not both. For PeopleTools 8.22, the resources\PT822 directory contains resource bundles only for the English locale. This issue is discussed in the Known Issues list in Chapter 4.		 
docs\B32166_01.pdf

OIM_home\xellerate\docs\PeopleSoftEmp


Note:

While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.

Step 3: Configuring the Oracle Identity Manager Server

Configuring the Oracle Identity Manager server involves the following procedures:


Note:

In a clustered environment, you must perform this step on each node of the cluster. Then, restart each node.

Changing to the Required Input Locale

Changing to the required input locale involves installing the required fonts and setting the required input locale.

To set the required input locale:


Note:

Depending on the operating system used, you may need to perform this procedure differently.

  1. Open Control Panel.

  2. Double-click Regional Options.

  3. On the Input Locales tab of the Regional Options dialog box, add the input locale that you want to use and then switch to the input locale.

Clearing Content Related to Connector Resource Bundles from the Server Cache

Whenever you add a new resource bundle file in the OIM_home\xellerate\connectorResources directory or make a change in an existing resource bundle file, you must clear content related to connector resource bundles from the server cache.

To clear content related to connector resource bundles from the server cache:

  1. In a command window, change to the OIM_home\xellerate\bin directory.

  2. Enter one of the following commands:


    Note:

    You must perform Step 1 before you perform this step. If you run the command as follows, then an exception is thrown: 
    OIM_home\xellerate\bin\batch_file_name

    • On Microsoft Windows:

      PurgeCache.bat ConnectorResourceBundle

    • On UNIX:

      PurgeCache.sh ConnectorResourceBundle

    In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:

    OIM_home\xellerate\config\xlConfig.xml

Note:

You can ignore the exception that is thrown when you perform Step 2.

Step 4: Configuring the Target System

To configure the PeopleSoft Employee Reconciliation server, use an administrator account to perform the following procedures:

Creating and Publishing the Message

The procedure to create and publish the message depends on the release of PeopleTools that you are using:

Creating and Publishing the Message on PeopleTools 8.22

Creating and publishing the message on PeopleTools 8.22 involves the following steps:

  1. To create the message channel:

    1. Click Start, Programs, and Application Designer. The Application Designer window is displayed in the 2-tier mode.

    2. Select New from the File menu. The New Definition dialog box is displayed.

    3. Select Message Channel, and then click OK.

    4. Save the new message channel as PERSON_BASIC.

    5. Select Object Properties from the File menu. The Message Channel Properties dialog box is displayed.

    6. Select the Run option, and then select Archive Messages.

    7. Click OK and save the message.

  2. To create the message:

    1. In the Application Designer, select New from the File menu. The New Definition dialog box is displayed.

    2. Select Message from the list, and then click OK.

    3. Select Object Properties from the File menu. The Message Properties dialog box is displayed.

    4. Click the Use tab.

    5. On the Use tab, select the PERSON_BASIC message channel and the version of the message that you just created.

    6. Select Active to make the message an active message, and then click OK.

    7. Right-click VERSION_1, and select the Insert Child Record option. The Insert Record window is displayed.

    8. Enter PERSONAL_DATA in the Name field, click Insert, and then click Close.

    9. Click PERSONAL_DATA under VERSION_1. All the fields comprising PERSONAL_DATA records are displayed.

      By default, all the fields appear as selected. Deselect the fields that are not required for the message XML file to be generated. Refer to the OIM_home\xellerate\test\psft_xellerate_msg.xml file for information about the fields in the message XML file.

    10. Repeat Steps g through i for the PS_PERS_NID, EMPLOYMENT, and JOB records.

    11. Save the message as PSFT_XELLERATE_MSG.

  3. To publish the message:

    1. Select Open from the File menu. The Open Definition dialog box is displayed.

    2. Select Component from the Definition list, enter PERSONAL_DATA in the Name Selection Criteria field, and then click Enter. All component names starting with the text PERSONAL_DATA are displayed.

    3. Select PERSONAL_DATA from the list, and then click Open. The details of the PERSONAL_DATA component are displayed.

    4. Click the Structure tab, right-click PERSONAL_DATA, and then select View PeopleCode. The PeopleCode for the PERSONAL_DATA component is displayed.

    5. Select the SavePostChange event from the list in the upper-left corner of the window. The PeopleCode for this event is displayed.

    6. Copy the code given in the following file immediately after the import definitions in the PeopleCode for the SavePostChange event:

      OIM_home\xellerate\Scripts\HRMSCBRecon.txt

    7. Select Save from the File menu to save the changes to the PERSONAL_DATA component.

After you complete this procedure, proceed to the "Configuring PeopleSoft Enterprise Portal" section.

Creating and Publishing the Message on PeopleTools 8.4x

Creating and publishing the message on PeopleTools 8.4x involves the following steps:

  1. To create the message channel:

    1. Click Start, Programs, Peoplesoft8.9hcm, and then Application Designer. The Application Designer window is displayed in 2-tier mode.


      Note:

      The reconciliation process requires the Application Engine program to be run in 2-tier mode. To open the Application Designer in 2-tier mode, you must have the database client, which is the client of the database that PeopleSoft is using, installed on the server. In addition, you must select the appropriate database type from the Connection Type field (for example, Oracle Database) while providing sign-on information in the PeopleSoft Application Designer Signon window.

    2. Select New from the File menu. The New Definition dialog box is displayed.

    3. Select Message Channel, and then click OK.

    4. Save the new message channel as PERSON_BASIC.

    5. Select Definition Properties from the File menu. The Message Channel Properties dialog box is displayed.

    6. Select the Run option, and then select Archive Messages.

    7. Click OK and save the message.

  2. After creating the message channel, create the message as follows:

    1. In the PeopleSoft Application Designer, select New from the File menu. The New Definition dialog box is displayed.

    2. Select Message from the list and then click OK.

    3. Select Definition Properties from the File menu. The Message Properties dialog box is displayed.

    4. Click the Use tab.

    5. On the Use tab, select the PERSON_BASIC message channel and the version of the message that you create in Step 2 of this procedure.

    6. Select Active to make the message an active message.

    7. Save the message as PSFT_XELLERATE_MSG.

  3. To publish the message:

    1. Select Open from the File menu. The Open Definition dialog box is displayed.

    2. Select Component from the Definition list, enter PERSONAL_DATA in the Name Selection Criteria field, and then press Enter. All component names starting with the text PERSONAL_DATA are displayed.

    3. Select PERSONAL_DATA from the list, and then click Open. The details of the PERSONAL_DATA component are displayed.

    4. Click the Structure tab, right-click PERSONAL_DATA, and then select View PeopleCode. The PeopleCode for the PERSONAL_DATA component is displayed.

    5. Select the SavePostChange event from the list in the upper-right corner of the window. The PeopleCode for this event is displayed.

    6. Copy the code given in the following file after the import definitions in the PeopleCode for the SavePostChange event:

      OIM_home\xellerate\Scripts\HRMSCBRecon.txt

    7. Add the following function call code at the end of the PeopleCode for the SavePostChange event:


      Note:

      Perform this step after you copy the code from the HRMSCBRecon.txt file.      		 

      /**********************************************************************/
/*  Calling the Generate function to generate the 
PSFT_XELLERATE_MSG message*/
/**********************************************************************/
Local string &emplid;
&emplid = PERSON.EMPLID;
GENERATE(&emplid);

    8. To save the changes to the PERSONAL_DATA component, select Save from the File menu.

Configuring PeopleSoft Enterprise Portal

PeopleSoft Enterprise Portal provides a single gateway to critical information in PeopleSoft Employee Reconciliation and other PeopleSoft applications.

The procedure to configure PeopleSoft Enterprise Portal depends on the release of PeopleTools that you are using:

Configuring PeopleSoft Enterprise Portal on PeopleTools 8.22

Configuring PeopleSoft Enterprise Portal on PeopleTools 8.22 involves the following steps:

  1. To create the XL_NODE remote node:

    1. In the Application Designer, select New from the File menu. The New Definition dialog box is displayed.

    2. Select Message Node from the list, and then click OK.

    3. Right-click anywhere in the white space, and then select Insert Location. The Location dialog box is displayed.

    4. Enter the URL for the PeopleSoft Application Gateway in the following format:

      http://hostname:port/servlets/gateway

    5. Select Object Properties from the File menu. The Message Node Properties dialog box is displayed.

    6. Select the Use tab. Ensure that Local Node is not selected.

    7. Save the remote node as XL_NODE.

  2. To configure the PERSON_BASIC message channel:

    1. From the File menu, select Open and then click Message Channel.

    2. To open the PERSON_BASIC message channel, select PERSON_BASIC.

    3. Click the Routing Rules tab.

    4. Right-click anywhere in the empty area of the right pane, and then select Insert Message Node. The Insert Message Node dialog box is displayed.

    5. Select the XL_NODE message node, and then click Insert.

    6. Click Cancel to close the dialog box.

    7. Right-click the message node displayed on the Routing Rules tab.

    8. Point to Routing Direction, and then select Publish To.

    9. Save the message channel.

  3. To configure the PeopleSoft Enterprise Portal gateway so that messages can be sent through the gateway to third-party systems:


    Note:

    The Simple File Handler is a utility in PeopleTools 8.22 that can receive messages published by a PeopleSoft node and write these messages to a file that can be used by third-party systems.

    1. In a Web browser, use a URL with the following format to launch the PeopleSoft configuration servlet interface (handler directory):

      http://hostname:port/servlets/gateway.administration

      In this URL, hostname is the application server that hosts PeopleSoft and port is the port number at which the application server is listening.

    2. Click Add Handler. The Add Handler window is displayed.

    3. Enter the full name of the Simple File Handler class, psft.pt8.filehandler.SimpleFileHandler.

    4. Click Save. The Handler Directory window is displayed.

    5. To load the handler, click Load. After the handler loads, the "Loaded successfully" message is displayed in the Status column.

    6. Click Configure.

    7. Click Add a file handler node. The Add File Handler Node window is displayed.

    8. In the Node Name field, enter the name of the message node that you create, XL_NODE.

    9. Specify the output directory in which the published messages are to be stored.

    10. Select Include Header.

    11. Click Save.

  4. XML messages are generated by the PeopleTools 8.22 Simple File Handler. To publish these messages to the PeopleSoft Connector Listener servlet, you must create a scheduled task as follows:


    Note:

    The scheduled task calls a Java program that communicates with the servlet deployed on the Oracle Identity Manager server. The servlet parses the message and sends reconciliation events to Oracle Identity Manager.

    The servlet then sends a return code based on the status of reconciliation event. If the reconciliation event is successfully sent, then the message is deleted or archived. Otherwise, the message file is left unchanged. The next time the scheduled task is run, another attempt is made at sending the message.

    1. Copy the publish.bat and xliMsgPublisher.jar files from the OIM_home\xellerate\MsgPublisher directory to a directory on the PeopleSoft Employee Reconciliation server.

    2. Use a text editor to open the publish.bat file, and then make the following changes in the file:

      i. Change the value of the JAVA_HOME variable so that it points to the JDK installation directory on the PeopleSoft Web server.

      ii. Specify the following values in the Java command given at the end of the file:

      - PeopleSoft_listener_servlet_URL

      - Output_directory_for_XML_messages

      - XML_message_name

      - console_log_file_path

      The command is in the following format:

      java com.thortech.xl.Integration.msgpublisher.PeopleSoftPublisher "PeopleSoft_listener_servlet_URL" "Output_directory_for_XML_messages" XML_message_name >> console_log_file_path

      For example:

      java Com.thortech.xl.Integration.msgpublisher.PeopleSoftPublisher "http://host:port/peopleSoftApp/do/peopleSoftAction" "C:/test/file" PSFT_XELLERATE_MSG >> c:/test/consolelog.log

    3. Save and close the batch file.

    4. On the PeopleSoft Web server, click Start, Settings, and Control Open.

    5. Double-click Scheduled Tasks.

    6. Click Add Schedule Task, and then click Next.

    7. Click Browse, and then select the publish.bat file from the directory in which you save it.

    8. Select Daily, click Next, and then click Next again.

    9. Enter the user ID and password for the scheduled task to run.

    10. Select the Open Advance properties check box.

    11. Click Finish.

    12. On the Schedule tab, click Advanced.

    13. Select Repeat Task.

    14. Select the frequency at which you want the task to run.

    15. Click OK, and then click OK again to close the window.

Configuring PeopleSoft Enterprise Portal on PeopleTools 8.4x

Configuring PeopleSoft Enterprise Portal on PeopleTools 8.4x involves the following steps:

To configure the PeopleSoft Enterprise Portal gateway so that messages can be sent through the gateway to the connector:

  1. Open a Web browser and enter the URL for PeopleSoft Enterprise Portal. The URL for PeopleSoft Enterprise Portal is in the following format:

    http://servername/psp/Databasename/?cmd=login

    For example:

    http://psftserver.acme.com/TestDB/?cmd=login

  2. Expand PeopleTools, Integration Broker, and then Gateways. The Gateway component details are displayed.

  3. Enter LOCAL in the Integration Gateway ID field, and then click Search. The LOCAL gateway is a default gateway that is created when you install PeopleSoft Enterprise Portal.

  4. Ensure that the IP address specified in the URL of the PeopleSoft listening connector is the IP address of the Web server on which PeopleSoft Employee Reconciliation is installed. The PeopleSoft listening connector is a module provided by PeopleSoft. The URL of the PeopleSoft listening connector is in the following format:

    http://computer_name/PSIGW/PeopleSoftListeningConnector

    For example:

    http://172.19.151.53/PSIGW/PeopleSoftListeningConnector

  5. Click Load Gateway Connectors to load all target connectors that are registered with the LOCAL gateway.

  6. Click Save.

To create the XL_NODE node to serve as the remote node:

  1. In the PeopleSoft Enterprise Portal window, expand PeopleTools, Integration Broker, and Node Definitions.

  2. Click the Add a New Value tab.

  3. On the Add a New Value tab, enter XL_NODE as the node name and then click Add. The Node Definition page is displayed.

  4. Enter a description for the node in the Description field.

  5. Make this node a remote node by deselecting the Local Node check box and selecting the Active Node check box.

  6. On the Connectors tab, enter the following information and then perform a lookup:

    Gateway ID: LOCAL

    Connector ID: PSFT81TARGET

  7. On the Properties tab, enter the following information:

    Property ID: PSFT81TARGET

    Property Name: URL

    Required value: Enter the URL of the PeopleSoft servlet that is supposed to receive the XML message. This URL must be in the following format:

    http://computer_name:port/peopleSoftApp/do/peopleSoftAction

    For example:

    http://myserver:8080/peopleSoftApp/do/peopleSoftAction

  8. Click Save.

  9. On the Transactions tab, click Add Transaction. The Add Transaction dialog box is displayed.

  10. Enter the following details to define a new transaction:

    Transaction Type: Outbound Asynchronous

    Request Message: PSFT_XELLERATE_MSG

    Request Message Version: VERSION_1

  11. Click Add.

  12. To keep the status as active, select Active.

  13. Click Save to save the changes.

To secure the PERSON_BASIC message channel:

  1. In PeopleSoft Enterprise Portal, expand PeopleTools, Security, Permission & Roles, and Permission Lists.

  2. Select AEAE1000. The AEAE1000 permission list is displayed.

  3. Select the Message Monitor tab, and then click the '+' button to add a channel name.

  4. Specify PERSON_BASIC as the channel name, and select FULL as the access level.

  5. Click Save.

  6. To verify that the PERSON_BASIC message channel is in running mode:

    1. Expand PeopleTools, Integration Broker, Monitor, and Monitor Message.

    2. Click the Channel Status tab.

    3. Verify that the PERSON_BASIC message channel is running. If it is paused, then click Run.

Preparing the Flat File for Bulk Reconciliation

Preparing the flat file for bulk reconciliation involves the following steps:

Creating the Application Engine Program

The bulk reconciliation process requires creating the Application Engine program. To create this program:

  1. Click Start, Programs, Peoplesoft8.9hcm, and then Application Designer. The Application Designer window is opened in 2-tier mode.

  2. Select New from the File menu. The New Definition dialog box is displayed.

  3. Select Application Engine from the Definition list. The App Engine Program window is displayed.

  4. Click the plus sign (+) that is displayed before the MAIN section in the Application Engine Program under which there may be multiple steps and in each step there may be some PeopleCode to be run. By default, a step titled Step01 is created and added to MAIN.

  5. Rename Step01 to Populate.

  6. In the App Engine Program window, select Action from the Insert menu. An action is added to the Populate step.

  7. Select PeopleCode from the list for the new action.

  8. Click Save from the File menu to save the Application Engine program with the name BLKPRCS_HR.

  9. Double-click the PeopleCode action. A new PeopleCode window is displayed.

  10. In the PeopleCode window, copy the code from the OIM_home\xellerate\Scripts\HRMSBulkRecon.txt file. A sample directory path for the output file is given in this code. Change the sample directory path to a directory path on the PeopleSoft Employee Reconciliation server.

  11. Save the Application Engine program and close the window.

Running the Application Engine Program

The procedure to run the Application Engine program depends on the release of PeopleTools that you are using:

Running the Application Engine Program on PeopleTools 8.22

To run the Application Engine program on PeopleTools 8.22:

  1. Log in to the PeopleSoft Enterprise Portal.

  2. Click People Tools, Process Scheduler Manager, Use, and Process Definitions. The Process Definitions page is displayed.

  3. Click Add a New value.

  4. Select Application Engine from the Process Type list.

  5. Enter the name of the Application Engine program as the process name, for example, BLKPRCS_HR.

  6. Click Add.

  7. Select the Application Engine Program from the search results that are displayed when you click Add.

  8. On the Process Definition Options tab, specify the following values:

    • Run Location: Server

    • Server Name: PSNT

    • Component: PRCSMULTI

    • Process Groups: ALLPANLS

  9. Click Save.

  10. Return to the home page.

  11. Click People Tools, Process Scheduler Manager, Process, and Sample Processes. The Sample Processes page is displayed.

  12. Click Add a New value.

  13. Specify a run control ID, and then click Add.


    Note:

    A run control ID is used as a key for records that contain the parameters required by a process at run time. If the parameters are stored in a table that the process can query using the run control ID and user ID, then the process can run without user intervention.

  14. Click Run. The Process Scheduler Request page is displayed

  15. Specify the server name.

  16. Select the Application Engine program name, and then click OK.

  17. Click Process Monitor to verify the status of the process.

    After the process status changes to Success, the comma-separated file is created at the location specified in the code that you copy from the HRMSBulkRecon.txt file.

Running the Application Engine Program on PeopleTools 8.4x


Note:

For the Application Engine program to run in 2-tier mode, the database client must be installed on the server used for accessing the application designer. To switch to the 2-tier mode, you select Connection Type as the database on the PeopleSoft sign-on screen.

To run the Application Engine program on PeopleTools 8.4x:

  1. Click Start, Programs, Peoplesoft8.9hcm, and then Application Designer. The Application Designer window is opened in 2-tier mode.

  2. Specify the connection type, user ID, and password.

  3. To open the Application Engine program that you create:

    1. From the File menu, select Open and then select Application Engine Program from the Object Type list.

    2. Select BLKPRCS_HR, and then click Open.

  4. Click the RUN PROGRAM control on the toolbar below the menu bar. The code for the PeopleCode action is run. The comma-separated file containing employee records is created at the location specified in the code.

Step 5: Configuring the PeopleSoft Listener for Change-Based Reconciliation

This section describes how to configure the listener for the connector. In the following instructions, OIM_home refers to the local Oracle Identity Manager Server installation directory.

To configure the PeopleSoft listener:

  1. Enter the following command to extract the contents of the peopleSoftApp.war file. This file is in the OIM_home\xlclient\lib directory.

    jar –xvf peopleSoftApp.war

    Note:

    All the files mentioned in the remaining steps of this procedure are extracted from the peopleSoftApp.war file.

  2. Edit the deployment.properties file. This file contains the message property, which corresponds to the name of the XML message from the PeopleSoft feed. The default value of this attribute is PSFT_XELLERATE_MSG. Obtain the correct value for this attribute from the PeopleSoft administrator.

  3. Edit the xlsession.properties file. This file contains the following Oracle Identity Manager connection parameters:

    • ObjectName: This is the name of the resource object in Oracle Identity Manager against which the reconciliation event is created. The default value is PSFT_HR_RO. However, for nontrusted reconciliation, you can change it to the name of any other resource object.

    • Username: This is the user name for logging in to Oracle Identity Manager. The default value is xelsysadm.

    • Password: This is the password for logging in to Oracle Identity Manager. You must enter the encrypted value for the default password:

      Kk3821YZhIoG36lvDH2YTw==

      Note:

      If the password for Oracle Identity Manager is different from the default password, then refer to Appendix B for information about encrypting a plaintext password.

  4. Edit the xlclient.properties file. This file contains the following system properties that enable an API client to communicate with Oracle Identity Manager:

    • xl.homedir: This property specifies the Oracle Identity Manager client directory. Typically, the Oracle Identity Manager client directory is OIM_home\xlclient.

    • java.security.policy: This property specifies the path of the security policy file. Typically, this file is located in the OIM_home\xlclient\config directory.

    • java.security.auth.login.config: This property specifies the path of the authentication configuration file. Typically, this file is located in the OIM_home\xlclient\config directory.

      Each application server uses a different authentication configuration file:

      IBM WebSphere: authws.conf

      BEA WebLogic: authwl.conf

      JBoss Application Server: auth.conf

    • java.naming.provider.url: This property specifies the JNP URL of the application server. This URL is given in the <Discovery><CoreServer><java.naming.provider.url> tag of the OIM_home\xlclient\config\xlconfig.xml file.

  5. Edit the following properties in the configureReconciliation.properties file:

    • reconciliationMode: This property can accept one of two possible values:

      • If you want to perform reconciliation in trusted mode, then set this property to trusted.

      • If you want to perform reconciliation in nontrusted mode, then set this property to nontrusted.

    • Serverdateformat: This property specifies the date format that is used by the PeopleSoft Employee Reconciliation server. You can select one of the following date formats:

      • dd-mmm-yy

      • ddmmyy

      • yyddmm

      • yymmdd

    • xellerateOrganization: This property contains the name of the Oracle Identity Manager organization. The default value of this property is Xellerate Users. The value that you assign to this property must exist in Oracle Identity Manager.

    • nullDate: This property contains the default value for a date field. The value is 2200/01/01 00:00:00 PST. This value is used if the date field is left empty.

    • PeoplesoftstartingYEAR: The year is specified in two digits. If the number represented by these two digits (xx):

      • Is greater than or equal to 50, then it is assumed that the year is 19xx.

      • Is less than 50, then it is assumed that the year is 20xx.

      This specifies a range of 1950 to 2049 for the year.

    • XelServerDate: This property contains the date format that is used for the Oracle Identity Manager server.

      Current value of the XelServerDate property: yyyy/MM/dd hh:mm:ss z

  6. Copy the following files from the OIM_home\xellerate\lib directory to the WEB-INF\lib directory:

    • wlXLSecurityProviders.jar

    • xlAPI.jar

    • xlAuthentication.jar

    • xlBackOfficeBeans.jar

    • xlBackofficeClient.jar

    • xlCache.jar

    • xlCrypto.jar

    • xlDataObjectBeans.jar

    • xlDataObjects.jar

    • xlLogger.jar

    • xlUtils.jar

    • xlVO.jar

    Copy the following files from the OIM_home\xellerate\ext directory to the WEB-INF\lib directory:

    • oscache.jar

    • javagroups-all.jar

  7. Delete the peopleSoftApp.war file from the temporary directory in which you extract it, and then use the following command to re-create the file:

    jar –cvf peopleSoftApp.war .

  8. Ensure that the old version of the peopleSoftApp.war file is removed from the application server (JBoss, IBM WebSphere, or BEA WebLogic) deployment directory and the OIM_home\xellerate\webapp directory.

  9. Copy the newly created peopleSoftApp.war file into the application server (JBoss, IBM WebSphere, or BEA WebLogic) deployment directory and the OIM_home\xellerate\webapp directory.

  10. Restart the Oracle Identity Manager server and client.


Note:

You can add custom attributes to be reconciled during change-based reconciliation. However, you must complete the deployment procedure before you can add custom attributes.

Refer to Appendix C for information about the procedure to add custom attributes for reconciliation.

Step 6: Importing the Connector XML File

To import the connector XML file into Oracle Identity Manager:

  1. Open the Oracle Identity Manager Administrative and User Console.

  2. Click the Deployment Management link on the left navigation bar.

  3. Click the Import link under Deployment Management. A dialog box for locating files is displayed.

  4. Locate and open the adpPSFT_RECON_DM.xml file, which is in the OIM_home\xlclient directory. Details of the XML file are shown on the File Review page.

  5. Click Add File. The Substitutions page is displayed.

  6. Click Next. The Confirmation window is displayed.

  7. Click View Selections.

    The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. Remove these nodes by right-clicking each node and then selecting Remove.

  8. Click Import. The connector file is imported into Oracle Identity Manager.

Step 7: Configuring Reconciliation

Configuring reconciliation involves the following steps:

Configuring Trusted Source Reconciliation


Note:

Perform this step of the procedure only if you want to configure trusted source reconciliation. Only one connector can be configured for trusted source reconciliation. If you import the adpPSFT_XellerateUser_RECON_DM.xml file while you have another trusted source configured, then both connector reconciliations would stop working.

Refer to Oracle Identity Manager Connector Framework Guide for conceptual information about reconciliation configurations.

To configure trusted source reconciliation, you must first import the XML file for trusted source reconciliation as follows:

  1. Open the Oracle Identity Manager Administrative and User Console.

  2. Click the Deployment Management link on the left navigation bar.

  3. Click the Import link under Deployment Management. A dialog box for locating files is displayed.

  4. Locate and open the adpPSFT_XellerateUser_RECON_DM.xml file, which is in the OIM_home\xlclient directory. Details of this XML file are shown on the File Preview page.

  5. Click Add File. The Substitutions page is displayed.

  6. Click Next. The Confirmation page is displayed.

  7. Click Import.

  8. In the message that is displayed, click Import to confirm that you want to import the XML file and then click OK.

Then, set the value of the IsTrusted reconciliation scheduled task attribute to YES while performing the procedure described in the following section.

Creating the Reconciliation Scheduled Tasks

To create the scheduled tasks for lookup fields and user reconciliations:

  1. Open the Oracle Identity Manager Design Console.

  2. Expand the Xellerate Administration folder.

  3. Select Task Scheduler.

  4. Click Find. The details of the predefined scheduled tasks are displayed.

  5. Enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task.

  6. Ensure that the Disabled and Stop Execution check boxes are not selected.

  7. In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.

  8. To set the task to run only once, select the Once option in the Interval region.

  9. Provide values for the attributes of the scheduled task. Refer to the "Specifying Values for the Scheduled Task Attributes" section for information about the values to be specified.

  10. Click Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.

  11. Repeat Steps 5 through 10 to create the second scheduled task.

After you create the scheduled task, proceed to the "Configuring the Connector for Multiple Installations of the Target System" section.

Specifying Values for the Scheduled Task Attributes

You must specify values for the following attributes of the employee reconciliation scheduled task.


Note:

Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.

Attribute Name Description Sample Value
FolderPath Directory path where employee reconciliation files generated by PeopleSoft Employee Reconciliation are stored C:\PSFTHR\UserRecon
TargetSystem Name of the resource object PSFT_HR_RO
IsTrusted Specifies whether or not reconciliation is to be performed in trusted mode YES or NO

The default value is NO.
XellerateOrganization Default name for the Oracle Identity Manager organization

This value is used to create the Xellerate User in trusted mode.

 Xellerate Users
DateFormatFolderPath Directory path where the configureReconciliation.properties file is stored C:\PSFTHR\DateFormat\configureReconciliation.properties
isDebug Debug feature YES or NO

The default value is NO.

After you specify values for these task attributes, go to Step 10 of the procedure to create scheduled tasks.

Configuring the Connector for Multiple Installations of the Target System


Note:

Perform this procedure only if you want to configure the connector for multiple installations of PeopleSoft Employee Reconciliation. Refer to Oracle Identity Manager Design Console Guide for detailed instructions on performing each step of this procedure.

To configure the connector for multiple installations of the target system:

  1. Create and configure one resource object for each target system installation.

    The Resource Objects form is in the Resource Management folder. The PSFT_HR_RO resource object is created when you import the connector XML file. You can use this resource object as the template for creating the remaining resource objects.

  2. Design one process form for each resource object.

    The Form Designer form is in the Development Tools folder. The UD_PSFT_HR process form is created when you import the connector XML file.

    You can use this process form as a template for creating the remaining process forms.

  3. Create and configure one process definition for each resource object.

    The Process Definition form is in the Process Management folder. The PSFT_HR Process process definition is created when you import the connector XML file. You can use this process definition as the template for creating the remaining process definitions.

    While creating process definitions for each target system installation, the following steps that you must perform are specific to the creation of each process definition:

    • From the Object Name lookup field, select the resource object that you create in Step 1.

    • From the Table Name lookup field, select the process form that you create in Step 3.

  4. Configure reconciliation for each target system installation. Refer to the "Step 7: Configuring Reconciliation" section for instructions. Note that only the values of the following attributes are to be changed for each reconciliation scheduled task:

    • TargetSystem

    • IsTrusted

    Set the IsTrusted attribute to YES for the PeopleSoft Employee Reconciliation installation that you want to designate as a trusted source. You can designate either a single or multiple installations of PeopleSoft Employee Reconciliation as the trusted source. For the remaining PeopleSoft Employee Reconciliation installations, set this attribute to NO.

  5. If required, modify the fields to be reconciled for the Xellerate User resource object.

Additional Steps for Configuring Change-Based Reconciliation

For change-based reconciliation, you must perform the procedure described in the "Step 4: Configuring the Target System" section and in the "Step 5: Configuring the PeopleSoft Listener for Change-Based Reconciliation" section.

The following are actions that you must perform differently from the procedure described in these sections:

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Table of Contents
Contents		 Go to Index
Index