| Oracle® Identity Manager Connector Guide for PeopleSoft Employee Reconciliation Release 9.0.4 Part Number E10166-02 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for PeopleSoft Employee Reconciliation Release 9.0.4 Part Number E10166-02 |
|
|
View PDF |
Deploying the connector involves the following steps:
To verify deployment requirements for the PeopleSoft Employee Reconciliation connector:
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:
You must ensure that the following components are installed and configured:
|
| Target system host platform | Microsoft Windows |
| External code | The external code requirement consists of the following files:
Refer to "Step 2: Copying the Connector Files" for more information about these files. |
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
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 directory on the installation media:Enterprise Applications/PeopleSoft Enterprise Applications/PeopleSoft Employee Reconciliation
Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.
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.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 (language and country setting) involves installing the required fonts and setting the required input locale.
You may require the assistance of the system administrator to change to the required input locale.
While performing the instructions described in the "Step 2: Copying the Connector Files" section, you copy files from the resources directory on the installation media into the OIM_home/xellerate/connectorResources directory. Whenever you add a new resource bundle in the connectorResources directory or make a change in an existing resource bundle, 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:
In a command window, change to the OIM_home/xellerate/bin directory.
Note:
You must perform Step 1 before you perform Step 2. If you run the command described in Step 2 as follows, then an exception is thrown:OIM_home/xellerate/bin/script_file_name
Enter one of the following commands:
On Microsoft Windows:
PurgeCache.bat ConnectorResourceBundle
On UNIX:
PurgeCache.sh ConnectorResourceBundle
Note:
You can ignore the exception that is thrown when you perform Step 2.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
When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
ALL
This level enables logging for all events.
DEBUG
This level enables logging of information about fine-grained events that are useful for debugging.
INFO
This level enables logging of informational messages that highlight the progress of the application at coarse-grained level.
WARN
This level enables logging of information about potentially harmful situations.
ERROR
This level enables logging of information about error events that may still allow the application to continue running.
FATAL
This level enables logging of information about very severe error events that could cause the application to stop functioning.
OFF
This level disables logging for all events.
The file in which you set the log level depends on the application server that you use:
BEA WebLogic
To enable logging:
Add the following line in the OIM_home/xellerate/config/log.properties file:
log4j.logger.Adapter.PSFTEmpRecon=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.Adapter.PSFTEmpRecon=INFO
After you enable logging, log information is written to the following file:
WebLogic_home/user_projects/domains/domain_name/server_name/server_name.log
IBM WebSphere
To enable logging:
Add the following line in the OIM_home/xellerate/config/log.properties file:
log4j.logger.Adapter.PSFTEmpRecon=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.Adapter.PSFTEmpRecon=INFO
After you enable logging, log information is written to the following file:
WebSphere_home/AppServer/logs/server_name/startServer.log
JBoss Application Server
To enable logging:
In the JBoss_home/server/default/conf/log4j.xml file, locate the following lines:
<category name="Adapter.PSFTEmpRecon">
<priority value="log_level"/>
</category>
In the second XML code line, replace log_level with the log level that you want to set. For example:
<category name="Adapter.PSFTEmpRecon"> <priority value="INFO"/> </category>
After you enable logging, log information is written to the following file:
JBoss_home/server/default/log/server.log
OC4J
To enable logging:
Add the following line in the OIM_home/xellerate/config/log.properties file:
log4j.logger.Adapter.PSFTEmpRecon=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.Adapter.PSFTEmpRecon=INFO
After you enable logging, log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log
To configure the PeopleSoft Employee Reconciliation server, use an administrator account to perform the following procedures:
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 involves the following steps:
To create the message channel:
Click Start, Programs, and Application Designer. The Application Designer window is displayed in the 2-tier mode.
Select New from the File menu. The New Definition dialog box is displayed.
Select Message Channel, and then click OK.
Save the new message channel as PERSON_BASIC.
Select Object Properties from the File menu. The Message Channel Properties dialog box is displayed.
Select the Run option, and then select Archive Messages.
Click OK, and then save the message.
To create the message:
In the Application Designer, select New from the File menu. The New Definition dialog box is displayed.
Select Message from the list, and then click OK.
Select Object Properties from the File menu. The Message Properties dialog box is displayed.
Click the Use tab.
On the Use tab, select the PERSON_BASIC message channel and the version of the message that you create.
Select Active to make the message an active message, and then click OK.
Right-click VERSION_1, and select the Insert Child Record option. The Insert Record window is displayed.
Enter PERSONAL_DATA in the Name field, click Insert, and then click Close.
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/cbrecon/psft_xellerate_msg.xml file for information about the fields in the message XML file.
Repeat Steps g through i for the PS_PERS_NID, EMPLOYMENT, and JOB records.
Save the message as PSFT_XELLERATE_MSG.
To publish the message:
Select Open from the File menu. The Open Definition dialog box is displayed.
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.
Select PERSONAL_DATA from the list, and then click Open. The details of the PERSONAL_DATA component are displayed.
Click the Structure tab, right-click PERSONAL_DATA, and then select View PeopleCode. The PeopleCode for the PERSONAL_DATA component is displayed.
Select the SavePostChange event from the list in the upper-left corner of the window. The PeopleCode for this event is displayed.
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
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.45 through 8.47 involves the following steps:
To create the message channel:
Click Start, Programs, Peoplesoft8.x, 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.Select New from the File menu. The New Definition dialog box is displayed.
Select Message Channel, and then click OK.
Save the new message channel as PERSON_BASIC.
Select Definition Properties from the File menu. The Message Channel Properties dialog box is displayed.
Select the Run option, and then select Archive Messages.
Click OK and save the message channel.
After creating the message channel, create the message as follows:
In the PeopleSoft Application Designer, select New from the File menu. The New Definition dialog box is displayed.
Select Message from the list and then click OK.
Select Definition Properties from the File menu. The Message Properties dialog box is displayed.
Click the Use tab.
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.
Select Active to make the message an active message.
Save the message as PSFT_XELLERATE_MSG.
Select Open from the File menu. The Open Definition dialog box is displayed.
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.
Select PERSONAL_DATA from the list, and then click Open. The details of the PERSONAL_DATA component are displayed.
Click the Structure tab, right-click PERSONAL_DATA, and then select View PeopleCode. The PeopleCode for the PERSONAL_DATA component is displayed.
Select the SavePostChange event from the list in the upper-right corner of the window. The PeopleCode for this event is displayed.
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
If the Peoplesoft server is running on Microsoft SQL Server, then:
Replace TO_CHAR(BIRTHDATE, 'ddmmyy') with convert (varchar, BIRTHDATE, 104)
Replace TO_CHAR(HIRE_DT, 'ddmmyy') with convert (varchar, HIRE_DT, 104)
If the Peoplesoft server is running on IBM DB2 UDB, then:
Replace TO_CHAR(BIRTHDATE, 'ddmmyy') with CHAR (BIRTHDATE, EUR)
Replace TO_CHAR(HIRE_DT, 'ddmmyy') with CHAR (HIRE_DT, EUR)
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 theHRMSCBRecon.txt file./**********************************************************************/ /* Calling the Generate function to generate the PSFT_XELLERATE_MSG message*/ /**********************************************************************/ Local string &emplid; &emplid = PERSON.EMPLID; GENERATE(&emplid);
To save the changes to the PERSONAL_DATA component, select Save from the File menu.
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.45 Through 8.47
Configuring PeopleSoft Enterprise Portal on PeopleTools 8.22 involves the following steps:
To create the XL_NODE remote node:
In the Application Designer, select New from the File menu. The New Definition dialog box is displayed.
Select Message Node from the list, and then click OK.
Right-click anywhere in the white space, and then select Insert Location. The Location dialog box is displayed.
Enter the URL for the PeopleSoft Application Gateway in the following format:
http://hostname:port/servlets/gateway
In this URL, hostname is the application server that hosts PeopleSoft and port is the port number at which the application server is listening.
Select Object Properties from the File menu. The Message Node Properties dialog box is displayed.
Select the Use tab. Ensure that Local Node is not selected.
Save the remote node as XL_NODE.
To configure the PERSON_BASIC message channel:
From the File menu, select Open and then click Message Channel.
To open the PERSON_BASIC message channel, select PERSON_BASIC.
Click the Routing Rules tab.
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.
Select the XL_NODE message node, and then click Insert.
Click Cancel to close the dialog box.
Right-click the message node displayed on the Routing Rules tab.
Point to Routing Direction, and then select Publish To.
Save the message channel.
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 mentioned in this procedure 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.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.
Click Add Handler. The Add Handler window is displayed.
Enter the full name of the Simple File Handler class, psft.pt8.filehandler.SimpleFileHandler.
Click Save. The Handler Directory window is displayed.
To load the handler, click Load. After the handler loads, the "Loaded successfully" message is displayed in the Status column.
Click Configure.
Click Add a file handler node. The Add File Handler Node window is displayed.
In the Node Name field, enter the name of the message node that you create, XL_NODE.
Specify the output directory in which the published messages are to be stored.
Select Include Header.
Click Save.
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 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 to send the message.
Copy the publish.bat and xliMsgPublisher.jar files from the OIM_home/xellerate/MsgPublisher directory to a directory on the PeopleSoft Employee Reconciliation server.
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
Save and close the batch file.
On the PeopleSoft Web server, click Start, Settings, and Control Open.
Double-click Scheduled Tasks.
Click Add Schedule Task, and then click Next.
Click Browse, and then select the publish.bat file from the directory in which you save it.
Select Daily, click Next, and then click Next again.
Enter the user ID and password for the scheduled task to run.
Select Open Advance properties.
Click Finish.
On the Schedule tab, click Advanced.
Select Repeat Task.
Select the frequency at which you want the task to run.
Click OK, and then click OK again to close the window.
Configuring PeopleSoft Enterprise Portal on PeopleTools 8.45 through 8.47 involves the following steps:
To configure the PeopleSoft Enterprise Portal gateway so that messages can be sent through the gateway to the connector:
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
Expand PeopleTools, Integration Broker, and then Gateways. The Gateway component details are displayed.
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.
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
Click Load Gateway Connectors to load all target connectors that are registered with the LOCAL gateway.
Click Save.
To create the XL_NODE node to serve as the remote node:
In the PeopleSoft Enterprise Portal window, expand PeopleTools, Integration Broker, and Node Definitions.
Click the Add a New Value tab.
On the Add a New Value tab, enter XL_NODE as the node name and then click Add. The Node Definition page is displayed.
Enter a description for the node in the Description field.
Make this node a remote node by deselecting the Local Node check box and selecting the Active Node check box.
On the Connectors tab, enter the following information and then perform a lookup:
Gateway ID: LOCAL
Connector ID: PSFT81TARGET
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
Click Save.
On the Transactions tab, click Add Transaction. The Add Transaction dialog box is displayed.
Enter the following details to define a new transaction:
Transaction Type: Outbound Asynchronous
Request Message: PSFT_XELLERATE_MSG
Request Message Version: VERSION_1
Click Add.
To keep the status as active, select Active.
Click Save to save the changes.
To secure the PERSON_BASIC message channel:
In PeopleSoft Enterprise Portal, expand PeopleTools, Security, Permission & Roles, and Permission Lists.
Select AEAE1000. The AEAE1000 permission list is displayed.
Select the Message Monitor tab, and then click the '+' button to add a channel name.
Specify PERSON_BASIC as the channel name, and select FULL as the access level.
Click Save.
To verify that the PERSON_BASIC message channel is in running mode:
Expand PeopleTools, Integration Broker, Monitor, and Monitor Message.
Click the Channel Status tab.
Verify that the PERSON_BASIC message channel is running. If it is paused, then click Run.
Preparing the flat file for bulk reconciliation involves the following steps:
To create the Application Engine program:
Click Start, Programs, Peoplesoft8.x, and then Application Designer. The Application Designer window is opened in 2-tier mode.
Select New from the File menu. The New Definition dialog box is displayed.
Select Application Engine from the Definition list. The App Engine Program window is displayed.
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.
Rename Step01 to Populate.
In the App Engine Program window, select Action from the Insert menu. An action is added to the Populate step.
Select PeopleCode from the list for the new action.
Click Save from the File menu to save the Application Engine program with the name BLKPRCS_HR.
Double-click the PeopleCode action. A new PeopleCode window is displayed.
In the PeopleCode window, copy the code from the OIM_home/xellerate/Scripts/HRMSBulkRecon.txt file. You must make the following changes in this code:
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.
Depending on the database that the Peoplesoft server is running on, you may need to make changes in the code that you copy from the HRMSBulkRecon.txt file:
If the Peoplesoft server is running on Microsoft SQL Server, then:
Replace TO_CHAR(BIRTHDATE, 'ddmmyy') with convert(varchar, BIRTHDATE, 104)
Replace TO_CHAR(HIRE_DT, 'ddmmyy') with convert(varchar, HIRE_DT, 104)
If the Peoplesoft server is running on IBM DB2 UDB, then:
Replace TO_CHAR(BIRTHDATE, 'ddmmyy') with CHAR(BIRTHDATE, EUR)
Replace TO_CHAR(HIRE_DT, 'ddmmyy') with CHAR(HIRE_DT, EUR)
Depending on the database that the PeopleSoft server is running on, you may need to change the value of the XelServerDate property in the following file:
OIM_home/xellerate/XLIntegrations/PSFTHR/config/configureReconciliation.properties
For Microsoft SQL Server, change the value of this property to the following:
dd.mm.yy
For IBM DB2 UDB, change the value of this property to the following:
dd.mm.yyyy
Save the Application Engine program and close the window.
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:
Log in to the PeopleSoft Enterprise Portal.
Click People Tools, Process Scheduler Manager, Use, and Process Definitions. The Process Definitions page is displayed.
Click Add a New value.
Select Application Engine from the Process Type list.
Enter the name of the Application Engine program as the process name, for example, BLKPRCS_HR.
Click Add.
Select the Application Engine Program from the search results that are displayed when you click Add.
On the Process Definition Options tab, specify the following values:
Run Location: Server
Server Name: PSNT
Component: PRCSMULTI
Process Groups: ALLPANLS
Click Save.
Return to the home page.
Click People Tools, Process Scheduler Manager, Process, and Sample Processes. The Sample Processes page is displayed.
Click Add a New value.
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.Click Run. The Process Scheduler Request page is displayed
Specify the server name.
Select the Application Engine program name, and then click OK.
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.45 Through 8.47
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.45 through 8.47:
Click Start, Programs, Peoplesoft8.x, and then Application Designer. The Application Designer window is opened in 2-tier mode.
Specify the connection type, user ID, and password.
To open the Application Engine program that you create:
From the File menu, select Open and then select Application Engine Program from the Object Type list.
Select BLKPRCS_HR, and then click Open.
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.
This section describes how to configure the listener for the connector. In the following procedure, OIM_home refers to the local Oracle Identity Manager installation directory.
To configure the PeopleSoft listener:
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 thepeopleSoftApp.war file.Edit the deployment.properties file. This file contains the message property that 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.
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. For nontrusted source 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 the "Encrypting a New Oracle Identity Manager Password" section for information about encrypting a plaintext password.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.
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
dd.mm.yy (for Microsoft SQL Server)
dd.mm.yyyy (for IBM DB2 UDB)
xellerateOrganization: This property specifies 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 specifies 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: This property specifies the year 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 property.
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
Note:
You must not change this date format.Copy the following files from the OIM_home/xellerate/lib directory to the WEB-INF/lib directory:
Note:
If required, delete the existing JAR files in theWEB-INF/lib directory before you copy the JAR files from the OIM_home/xellerate/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
Delete the peopleSoftApp.war file from the temporary directory into which you extract it, and then use the following command to re-create the file:
jar –cvf peopleSoftApp.war .
Ensure that the old version of the peopleSoftApp.war file is removed from the application server (JBoss Application Server, IBM WebSphere, BEA WebLogic, or OC4J) deployment directory and the OIM_home/xellerate/webapp directory.
Copy the newly created peopleSoftApp.war file into the application server deployment directory and the OIM_home/xellerate/webapp directory.
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 the "Adding Custom Attributes for Reconciliation" section for information about the procedure to add custom attributes for reconciliation.
To import the connector XML file into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for locating files is displayed.
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.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation window is displayed.
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. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and then selecting Remove.
Click Import. The connector file is imported into Oracle Identity Manager.
You must specify values for the PSFT Base Server IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
NumberOfRetries |
Number of times the connection to the target system must be retried before the InvocationTargetException is thrown
Default value: 2 Note: The timeout feature is enabled only for bulk reconciliation and provisioning. It is not applied during change-based reconciliation. |
DelayBetweenRetries |
Time difference between subsequent retries (in milliseconds)
Default value: 20000 |
IndexOfLastReconciledRecords |
Stores the index of last successful reconciled record
Default value: |
