Configuring WebSphere Portal for PeopleSoft data sources

These instructions will help you configure your WebSphere® Portal server for portlets that use PeopleSoft SDO.

Install the JCA adapter using the following steps:
  1. Create a new empty directory in your hard drive, referred to as PeopleSoft_lib_dir.
  2. Copy the psjoa.jar from the PeopleSoft server to PeopleSoft_lib_dir.
  3. Deploy the PeopleSoft JCA adapter in the WebSphere Portal server's root installation directory
    1. Verify that the application server for the administrative console is running.
    2. Point a Web browser to the URL for the administrative console and log in.
    3. Browse the administrative console using the navigation tree. Expand the Resources tab in the navigation tree and click on Resource Adapters.
    4. In the console workspace area, click on Install RAR.
    5. Specify the path and file name of the RAR file by doing one of the following:
      • Entering the path and file name of wpai.psft8.rar which is located in <rad_root>/portal/eclipse/plugins/com.ibm.etools.webtools.eis.peoplesoft_6.0.0.1/lib, where rad_root is the installation directory of Rational® Developer.
      • Clicking Browse to locate the local file.
    6. Select the node on which to install the RAR file. Click Next.
    7. Enter a name for the resource adapter. To make the resource adapter work with the WPAI mediators correctly the name of the resource adapter must be the same as the EIS type, namely "PeopleSoft". Click OK.
    8. Save the configuration changes.
  4. For each PeopleSoft application, define a connection factory for the PeopleSoft JCA adapter.
    1. Click on Resource Adapters in the navigation tree.
    2. Click on the resource adapter you deployed in step 4. (For example: PeopleSoft)
    3. Under Additional Properties, click on J2C Connection Factories. There must be exactly one J2C connection factory created for each connection used to connect to the PeopleSoft server.
    4. Click New.
    5. Enter the following:
      • A name for the connection factory that references the PeopleSoft application, such as PeopleSoftServer. The name for the connection factory must be the same as the connection name which was defined in the PeopleSoft wizard.
      • The JNDI binding path. The convention for this value is based on the connection name defined by the PeopleSoft wizard. The name is comprised of the prefix "eis/PeopleSoft/" and the connection name, such as eis/PeopleSoft/myPSConnection1. However, you can specify any JNDI binding path as long as it does not conflict with another JNDI path name. If the JNDI binding path names does not follow the naming convention, they must be mapped to the internal JNDI names used by the PeopleSoft portlets. For additional information on mapping resource references for web applications please refer to the related information in the help.
      • Click OK.
      • Click on the connection factory just created.
      • Under Additional Properties, click on Custom Properties.
      • Specify the properties for the PeopleSoft system you want to connect to by selecting the property from the list and entering a value in the entry field:
        • connectionString: The connection string used to contact the PeopleSoft server. The Type is java.lang.string

          The general format for this value is //[host name]:[port number]. For details on the connection string format, refer to the PeopleSoft documentation.

        • jarPath: Enter the value PeopleSoft_lib_dir, the directory where you placed the PeopleSoft libraries. The Type is java.lang.string
        • traceLevel:Enter the trace level (Valid values are 1, 2, 3). The default value is 1. The Type is java.lang.Integer
      • Click OK.
      • Repeat the steps to create a connection factory for the remaining PeopleSoft applications.

Upon configuring the JCA resource adapters, you will have to restart the WebSphere Portal server.

Related concepts
SAP data access
Siebel data access
PeopleSoft data access
Related tasks
Manually deploying EIS data access portlets

(C) Copyright IBM Corporation 2002, 2005. All Rights Reserved.