B Configuring the Connector Messages

You can configure the connector messages of release 9.1.0.x.y with that of the current release as follows:

To configure the messages:

1. Add the following lookup definitions:

   • Lookup.PSFT.Message.XellerateUser.Configuration

   • Lookup.PSFT.HRMS.XellerateUser.EmpStatus

   • Lookup.PSFT.HRMS.XellerateUser.EmpType

   • Lookup.PSFT.HRMS.XellerateUser.AttributeMapping

   • Lookup.PSFT.HRMS.XellerateUser.Recon

   To add a lookup definition:

   1. Log in to the Oracle Identity Manager Design Console.

   2. Expand Administration and then double-click Lookup Definition.

   3. In the Code field, enter the name of the lookup definition, for example, Lookup.PSFT.Message.XellerateUser.Configuration.

   4. In the Group field, enter the name with which you want to associate the lookup definition, for example, PSFT HRMS.

   5. Click the Save icon.

   6. Add the Code Key and Decode values specified in "Lookup Definitions to Configure the Messages" section. To do so:

      i) Click Add.

      A new row is added.

      ii) Enter the following values:

      Code Key: Attribute Mapping Lookup

      Decode: Lookup.PSFT.HRMS. XellerateUser.AttributeMapping

      iii) Repeat Steps i) and ii) to add the remaining entries in the lookup definition.

      iv) Click the Save icon.

2. Modify the Lookup.PSFT.Configuration lookup definition as follows:

   1. Add the following entry in the lookup definition:

      Code Key: Name of the message sent by PeopleSoft, for example, XELLERATE_USR_MSG

      Decode: Lookup.PSFT.Message.XellerateUser.Configuration

   2. Modify the value of the following entry in the lookup definition:

      Code Key: Ignore Root Audit Action

      Decode: Yes

   3. Click the Save icon.

3. Write code that implements the required message handler or message parser logic in a Java class. See the following files in the /samples directory of the installation media for more information about the Java code.

   • PSFTXellerateUserReconMessageHandlerImpl.java

   • XellerateUserMessageParser.java

4. Create a JAR file to hold the Java class.

5. Copy the JAR file into the JavaTasks directory.

   
   

   Note: If you are using Oracle Identity Manager release 11.1.1, then see Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for steps to import the contents of JavaTasks directory into the Oracle Identity Manager database.

   
   

6. Remove PeopleSoftOIMListener.war file from the application server.

7. Depending on the Oracle Identity Manager release that you are using, perform one of the following steps:

   • If you are using Oracle Identity Manager release 9.1.0.x, then:

     1. Copy the OIM_HOME/xellerate/XLIntegrations/PSFTER/ WAR/PeopleSoftOIMListener.war file into a temporary folder. Enter the following command to extract the contents of the PeopleSoftOIMListener.war file:

        jar -xvf PeopleSoftOIMListener.war
        

     2. Copy the validation JAR file created in Step 4 to the following directory of the extracted PeopleSoftOIMListener.war file:

        WEB-INF/lib

     3. Delete the PeopleSoftOIMListener.war file from the temporary directory into which you extracted its contents.

     4. Use the following command to re-create the file:

        jar -cvf PeoplesoftOIMListener.war .
        

   • If you are using Oracle Identity Manager release 11.1.1, copy the validation JAR file created in Step 4 to the following directory:

     PeoplSoftOIMListener.ear/PeoplSoftOIMListener.war/WEB-INF/lib

8. Add the message name and the implementation class in the web.xml file as follows:

   1. Search for the </servlet> tag in the file.

   2. Edit the following lines above the </servlet> tag:

      <init-param>
      <!-- Specify Message Handler Impl classes -->
      <param-name>IT_RESOURCE_NAME</param-name>
      <param-value>MESSAGE~IMPLEMENTATION_CLASS;MESSAGE~IMPLEMENTATION_CLASS;MESSAGE~IMPLEMENTATION_CLASS</param-value>
      </init-param>
      

      Replace IT_RESOURCE_NAME with the name of the IT Resource, for example, PSFT Server.

      Replace MESSAGE~IMPLEMENTATION_CLASS with the actual message name~message handler implementation class of the respective message.

9. Depending on the Oracle Identity Manager release that you are using, perform one of the following steps:

   • If you are using Oracle Identity Manager release 9.1.0.x, then redeploy the PeopleSoftOIMListener.war file on the application server. See Section 2.2.1.4.1, "Deploying the PeopleSoft Listener on Oracle Identity Manager Release 9.1.0.x" for the procedure.

   • If you are using Oracle Identity Manager release 11.1.1, then redeploy the PeopleSoftOIMListener.ear file on the application server. See Section 2.2.1.4.2, "Deploying the PeopleSoft Listener on Oracle Identity Manager Release 11.1.1" for the procedure.

10. Modify the PeopleSoft Integration Broker configuration as follows:

    1. In PeopleSoft Internet Architecture, expand PeopleTools, Integration Broker, Integration Setup, and then click Nodes.

    2. On the Find an Existing Value tab, enter the node name, for example, OIM_ER_NODE, and then click Search.

    3. On the Connectors tab, search for the following information by clicking on the Lookup icon:

       Gateway ID: LOCAL

       Connector ID: HTTPTARGET

    4. On the Properties page in the Connectors tab, enter the following information:

       Property ID: HEADER

       Property Name: sendUncompressed

       Required value: Y

       Property ID: HTTP PROPERTY

       Property Name: Method

       Required value: POST

       Property ID: HEADER

       Property Name: Host

       Required value: Enter the value of IT Resource name as configured for PeopleSoft HRMS

       Sample value: PSFT Server

       Property ID: PRIMARYURL

       Property Name: URL

       Required value: Enter the URL of the PeopleSoft listener that is configured to receive XML messages. This URL must be in the following format:

       http://ORACLE_IDENTITY_MANAGER_SERVER_IPADDRESS:PORT/PeopleSoftOIMListener
       

       The URL depends on the application server that you are using. For an environment on which SSL is not enabled, the URL must be in the following format:

       For IBM WebSphere Application Server:

       http://10.121.16.42:9080/PeopleSoftOIMListener
       

       For JBoss Application Server:

       http://10.121.16.42:8080/PeopleSoftOIMListener
       

       For Oracle WebLogic Server:

       http://10.121.16.42:7001/PeopleSoftOIMListener
       

       For an environment on which SSL is enabled, the URL must be in the following format:

       https://COMMON_NAME:PORT/PeopleSoftOIMListener
       

       For IBM WebSphere Application Server:

       https://example088196:9443/PeopleSoftOIMListener
       

       For JBoss Application Server:

       https://example088196:8443/PeopleSoftOIMListener
       

       For Oracle WebLogic Server:

       https://example088196:7002/PeopleSoftOIMListener
       

       
       

       Note: The ports may vary depending on the installation that you are using.

       
       

    5. Click Save to save the changes.

    6. Click the Ping Node button to check whether a connection is established with the specified IP address.

Lookup Definitions to Configure the Messages

You must add the following lookup definitions to configure the messages of release 9.1.0:

• Lookup.PSFT.Message.XellerateUser.Configuration

• Lookup.PSFT.HRMS.XellerateUser.EmpStatus

• Lookup.PSFT.HRMS.XellerateUser.EmpType

• Lookup.PSFT.HRMS.XellerateUser.AttributeMapping

• Lookup.PSFT.HRMS.XellerateUser.Recon

Lookup.PSFT.Message.XellerateUser.Configuration

Code Key	Decode
Attribute Mapping Lookup	Lookup.PSFT.HRMS. XellerateUser.AttributeMapping
Custom Query	Enter a Value
Custom Query Lookup Definition	Lookup.PSFT.HRMS.CustomQuery
Data Node Name	Transaction
Employee Status Lookup	Lookup.PSFT.HRMS.XellerateUser.EmpStatus
Employee Type Lookup	Lookup.PSFT.HRMS.XellerateUser.EmpType
Recon Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Recon
Message Handler Class	oracle.iam.connectors.psft.common.handler.impl.PSFTXellerateUserReconMessageHandlerImpl
Message Parser	oracle.iam.connectors.psft.common.parser.impl. XellerateUserMessageParser
Organization	Xellerate Users
Resource Object	Peoplesoft HRMS
Transformation Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Transformation
User Type	End-User
Use Transformation	No
Use Validation	No
Validation Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Validation

Lookup.PSFT.Message.XellerateUser.Configuration

Code Key	Decode
Attribute Mapping Lookup	Lookup.PSFT.HRMS. XellerateUser.AttributeMapping
Custom Query	Enter a Value
Custom Query Lookup Definition	Lookup.PSFT.HRMS.CustomQuery
Data Node Name	Transaction
Employee Status Lookup	Lookup.PSFT.HRMS.XellerateUser.EmpStatus
Employee Type Lookup	Lookup.PSFT.HRMS.XellerateUser.EmpType
Recon Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Recon
Message Handler Class	oracle.iam.connectors.psft.common.handler.impl.PSFTXellerateUserReconMessageHandlerImpl
Message Parser	oracle.iam.connectors.psft.common.parser.impl. XellerateUserMessageParser
Organization	Xellerate Users
Resource Object	Peoplesoft HRMS
Transformation Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Transformation
User Type	End-User
Use Transformation	No
Use Validation	No
Validation Lookup Definition	Lookup.PSFT.HRMS.XellerateUser.Validation

Lookup.PSFT.HRMS.XellerateUser.EmpStatus

Code Key	Decode
A	Active
I	Inactive

Lookup.PSFT.HRMS.XellerateUser.AttributeMapping

Code Key	Decode
Department	DEPTID~JOB
Emp Type	EMPLOYEETYPE~JOB
First Name	FIRST_NAME~PERSONAL_DATA
Last Name	LAST_NAME~PERSONAL_DATA
Job ID	JOBCODE~JOB
Status	STATUS~JOB
User ID	EMPLID~PERSONAL_DATA~None~None~PRIMARY

Lookup.PSFT.HRMS.XellerateUser.Recon

Code Key	Decode
Department	Department
Employee Type	Emp Type~Employee Type Lookup
First Name	First Name
Last Name	Last Name
Job Code	Job ID
Status	Status~Employee Status Lookup
User ID	User ID