By selecting business objects available from the enterprise application, users can specify which data fields should be displayed in your portlet. When the portlet is created, the portlet can be made available to portal end users.

JCA adapters allow connections to multiple versions of PeopleSoft and Siebel servers on the same WebSphere Application Server machine. This adapter also allows markup-based configuration so that users can select and modify fields for each supported markup. In addition, portlets that are WML-enabled allow you to search and retrieve information through your WAP-enabled device.

Note:

• If you create Click-to-Action wirings between two portlets, these wirings will not be persisted. After you log out of WebSphere Portal, the wirings will be lost. You will have to recreate wirings with the wiring tool if you still want to use them.
• IBM WebSphere Application Integrator no longer supports Cick-to-Action on IBM WebSphere Portal Version 4.1.x.
• Support for PeopleSoft 7.5 portlet builder has been removed.
• Due to the display limitations on a WAP enabled device, you can only display one field per record on the summary screen.
• The catalog version of the IBM Application Portlet Builder is not supported on WebSphere Portal 5.1.x. All of the Portlet Builders are included in WebSphere Portal 5.1.0.1. Please refer to the Information Center for installation and configuration instructions.

• 21 June 2005: Added (in the Note section above) that the catalog version of the IBM Application Portlet Builder is not supported on WebSphere Portal 5.1.x. All of the Portlet Builders are included in WebSphere Portal 5.1.0.1. Refer to the WebSphere Portal 5.1.0.1 Information Center for more information.
• 31 March 2004: Added feature enhancements to the IBM Application Portlet Builder and the run-time portlet (for WebSphere Portal v5.0.x only). For more details, refer to WPAI Enhancements.pdf, which is included in the download file, 1wp10003t.zip .
• 3 March 2004: Added Click-to-Action install instructions for WebSphere Everyplace Access 4.3.x .
• 4 February 2004: Added information for Unix platforms to the Configure for SAP section.
• 14 January 2004: Added a section under Deployment/Installation on removing the previous version of Portlet Builders (for WebSphere Portal 5.0.x only).
• 16 December 2003: Changed Domino Server requirements.
• 3 December 2003: Added Additional references section; Clarified databases supported by JDBC Builder; Changed name of the download zip file to 1wp10003t.zip .
• 18 November 2003: Added support for the SAP Business Object Editor; Added component interface list retrieval for PeopleTools 8.42.
• 21 October 2003: Added WebSphere Portal v5 support for WPAI Profile Service.
• 7 October 2003: Added WebSphere Portal v5 support for PeopleSoft 8, Siebel, SAP, and WebSphere Portal content publishing portlet builders. Domino now has attachment support. Enhanced the PeopleSoft 8 JCA adapter.
• 19 August 2003: Added WPAI Profile Service installation steps and reference documentation in the download zip file, 1wp10003t.zip. When you unzip 1wp10003t.zip you will can find user guides in the doc subdirectory.
• 08 July 2003: Added Domino installation steps.
• 03 June 2003: See the Portlet Installation for new installation instructions.
• 20 May 2003: Added support for Domino builder and for WebSphere Portal Content Publishing builder; Added support for Struts templates.
• 17 April 2003: New WPAIPortletBuilders.war file added.
• 25 March 2003: A new JDBC adapter allows general connections with databases that support a JDBC interface. Using this interface, normal Create, Retrieve, Update, and Delete (CRUD) operations are permitted. The JDBC adapter plugs into the WebSphere Portal Application Interface framework to allow portlets to be generated quickly and easily to work with database information.

  Note: The update and delete operations are supported only for tables with primary keys.

Back to top

• Using Application Portlet Builder
• Setting up Application Portlet Builder
  • Client requirements
  • Server requirements
  • Deployment/Installation
    • Remove previous version of Portlet Builders (for WebSphere Portal 5.0.x only)
    • Install Struts (for WebSphere Portal 4.1.x only)
    • Install Click-to-Action (for WebSphere Everyplace Access 4.3.x only)
    • Verify JCA support (for WebSphere Portal 4.x)
    • Configure for PeopleSoft
      • WebSphere Portal 4.x
      • WebSphere Portal 5.0.x
    • Configure for Siebel
      • WebSphere Portal 4.x
      • WebSphere Portal 5.0.x
    • Configure for SAP
      • WebSphere Portal 4.x
      • WebSphere Portal 5.0.x
    • Configure for SAP Business Object Editor
    • Configure the JDBC adapter
      • WebSphere Portal 4.x
      • WebSphere Portal 5.0.x
    • Configure for Domino
    • Configure for WebSphere Portal content publishing
    • Portlet Installation
    • WPAI Profile Service
      • WebSphere Portal 4.x
      • WebSphere Portal 5.0.x
  • Additional references

Back to top

Users can view and modify the information from their enterprise application in the view mode of portlets created with Application Portlet Builder. Users may have to supply the user ID and password they use to access the enterprise application. Administrators can specify connection information and vault slot preference in configure mode.

Back to top

WebSphere Portal 4.x:

If you have a previous version of Application Builder installed, you must first remove the existing JCA adapters before continuing. Use the following steps to remove the PeopleSoft 8 JCA adapter:

1. Open the WebSphere Application Server Administrative Console.
2. Remove any existing connection factories under the PeopleSoft adapters.
3. Remove the PeopleSoft adapters.
4. Close the Administrative Console.
5. Remove the following files from was_root\lib\ if you installed the adapters prior to April 2003:
   • psft_impl.jar
   • psft_client.jar
   • psjoa.jar
6. Remove the file was_root\lib\psft8adapter.jar if you installed the adapters in April 2003 or later.
7. Remove the directory and directory's contents from was_root\installedConnectors\psft.rar.
8. Restart WebSphere Application Server.

After removing any existing PeopleSoft 8 connection factories and adapters, install the updated adapter using the following steps:

1. Extract the contents of the download file to a directory of your choice, referred to as peoplesoft_home.
2. Create a new empty directory in your hard drive, referred to as peoplesoft_lib_dir.
3. Copy the following file from the PeopleSoft 8 server to peoplesoft_lib_dir:

   psjoa.jar, pstools.properties

4. Deploy the PeopleSoft 8 JCA adapter in WebSphere Application Server
   1. Ensure that the WebSphere Application Server Administration Server service is running.
   2. Start the WebSphere Application Server Administrator's Console.
   3. Double-click WebSphere Administrative Domain in the tree view.
   4. Double-click Resources in the tree view.
   5. Right-click on J2C Resource Adapters, and select New.
   6. On the General tab of the J2C Resource Adapters Properties window, enter the following:
      • A name for the resource adapter, such as PeopleSoft 8.
      • A description, such as PeopleSoft 8 JCA Connector.
   7. In the Archive file name field, click the button labeled "..." to display the Install Driver window.
   8. Select the node where you want to deploy the resource adapter and specify the path and file name of the RAR file, peoplesoft_home\psft.rar, by doing one of the following steps:
      • Enter the path and file name directly in the Rar file field.
      • Click Browse to locate the file.
   9. Click Install. The J2C Resource Adapters Properties window is updated to display the name of the RAR file you specified.
   10. Click OK to install the resource adapter. A confirmation message is displayed when the resource adapter is installed.
   11. Click OK to dismiss the message. The Administrator's Console is updated to display information about the resource adapter.
5. Define a connection factory for the PeopleSoft JCA adapter.
   1. Double-click on J2C Resource Adapters in the tree view.
   2. Double-click on the resource adapter you just deployed. For example, PeopleSoft 8.
   3. Right-click on J2C Connection Factories, and select New.
   4. On the General tab of the J2C Connection Factories Properties window, enter the following:
      • A name for the connection factory, such as PeopleSoft 8 Connection Factory.
      • The JNDI binding path. The convention for this value is eis/psft. However, you can specify any JNDI binding path as long as it does not conflict with another JNDI path name. Note that this value must also be specified as the JNDI binding path configuration parameter in configuration mode for each PeopleSoft portlet.
   5. Click the Connections tab.
   6. 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:

      hostName

      The host name of the PeopleSoft server to which you want to connect. For example, myserver.mycompany.com. The port number is for the JOLT Listener port. You can obtain the JOLT Listener port number from the PeopleSoft application server configuration file, psappsrv.cfg. An example location for that file is C:\PSFT_HRMS8.3\appserv\HR8DMO\psappsrv.cfg. An example hostName setting is //myserver.mycompany.com:9210. If you do not specify the port number, the default port number of 9000 is used.

      jarPath

      Enter the value peoplesoft_lib_dir, the directory where you placed the PeopleSoft libraries.

   7. Click OK.
6. Copy server-specific files.
   1. Extract psft8adapter.jar from peoplesoft_home\psft.rar.
   2. Copy this file to the was_root\lib directory, where was_root is the directory where WebSphere Application Server is installed. For example, C:\WebSphere\AppServer.
   3. Restart WebSphere Application Server.
7. The final step is importing the component interface list retrieval definition into PeopleSoft. There are two versions of the component interface: one for PeopleTools 8.18 and another for PeopleTools 8.42. If you are running PeopleTools 8.42 skip to step 8.
   Note: The component interface in the project, WPS_PS_CILIST, has been created and tested on PeopleTools 8.18, and is in general limited to that version of PeopleTools. If you attempt to import a component interface definition into another version of PeopleTools, you may crash the PeopleSoft Application Designer.
   1. Extract the contents of peoplesoft_home\wps_ps_cilist.zip to a directory of your choice (referred to as ci_home).
   2. Start the PeopleSoft Application Designer. To ensure that you can perform the steps below, log in to the Application Designer in two-tier mode.
   3. Select File > New to create a new project.
   4. Select File > Copy Project from File and specify the CI_home directory in the Import Directory field. You can enter the path directly or click "..." to browse to it.
   5. Verify that WPS_PS_CILIST is selected in the Project Name field.
   6. Click Copy.
   7. Select File > Save Project As, and enter a project name of your choice.
   8. Click OK.
   9. Exit the PeopleSoft Application Designer.
   10. Log into the PeopleSoft Web application.
   11. Select PeopleTools > Maintain Security > Use > Permission Lists .
   12. Add the imported component interface, WPS_CI_LIST to a permission list. You can use an existing permission list or create a new one. Select the Component Interface tab on the permission list to display the panel for adding the component interface.
   13. Edit the component interface to allow full access to all methods in it.
   14. Click Save to save your permission list changes.

       Note: Ensure that the intended user of the portlets participates in at least one role that contains this permission list.

   15. Skip step 8.

   Note: The component interface in the project, WPS_PT842_CILIST, has been created and tested on PeopleTools 8.42 and is in general limited to that version of PeopleTools. If you attempt to import a component interface definition into another version of PeopleTools, you may crash the PeopleSoft Application Designer.

   1. Extract the contents of peoplesoft_home\wps_pt842_cilist.zip to a directory of your choice (referred to as ci_home).
   2. Start the PeopleSoft Application Designer. To ensure that you can perform the steps below, log in to the Application Designer in two-tier mode.
   3. Select File > New to create a new project definition.
   4. Select Tools > Copy Project > From File and specify ci_home\WPS_PT842_CILIST\WPS_PST842_CILIST.ini directory in the filename field. You can enter the filename directly or browse to it.
   5. Verify that WPS_PT842_CILIST is selected in the Projects field.
   6. Click Open.
   7. Click Copy on the Copy from File dialog box.
   8. Select File > Save Project As and enter a project name of your choice.
   9. Click OK.
   10. Exit the PeopleSoft Application Designer.
   11. Log in to the PeopleSoft Web application.
   12. Select PeopleTools > Security > Permissions and Roles > Permission Lists.
   13. Add the imported component interface, WPS_CI_LIST, to a permission list. You can use an existing permission list or create a new one. Select the Component Interface tab on the permission list to display the panel for adding the component interface.
   14. Edit the component interface to allow full access to all methods in it.
   15. Click Save to save your permission list changes.

       Note: Ensure that the intended user of the portlets participates in at least one role that contains this permission list.

WebSphere Portal 5.0.x:

Install the JCA adapter using the following steps:

1. Extract the contents of the download file to a directory of your choice, referred to as peoplesoft_home.
2. Create a new empty directory in your hard drive, referred to as peoplesoft_lib_dir.
3. Copy the following files from the PeopleSoft 8 server to peoplesoft_lib_dir:
   • psjoa.jar, pstools.properties
4. Deploy the PeopleSoft 8 JCA adapter in WebSphere Application Server
   1. Ensure that the WebSphere Application Server Administration Server service is running.
   2. Start the WebSphere Application Server Administrator's Console.
   3. Click Resources in the navigation tree.
   4. Click on Resource Adapters
   5. In the console workspace area, click on the Install RAR button.
   6. Specify the path and the file name of the RAR file by doing one of the following:
      • Entering the path and file name directly to psft.rar
      • Clicking Browse to locate the local file.
   7. Select the node where you want to deploy the resource adapter and click Next.
   8. Enter a name for the resource adapter such as PeopleSoft 8 and click OK.
   9. Save the configuration changes.
5. 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 just deployed in Step 4. For example, PeopleSoft 8.
   3. Under Additional Properties, click on J2C Connection Factories, and click New.
   4. Enter the following:
      • A name for the connection factory, such as PeopleSoft 8 Connection Factory.
      • The JNDI binding path. The convention for this value is eis/psft. However, you can specify any JNDI binding path as long as it does not conflict with another JNDI path name. Note that this value must also be specified as the JNDI binding path configuration parameter in configuration mode for each PeopleSoft portlet.
   5. Click OK then click on the connection factory you just created.
   6. Under Additional Properties, click on Custom Properties.
   7. 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:

      hostName

      The host name of the PeopleSoft server to which you want to connect. For example, myserver.mycompany.com. The port number is for the JOLT Listener port. You can obtain the JOLT Listener port number from the PeopleSoft application server configuration file, psappsrv.cfg . An example location for that file is C:\PSFT_HRMS8.3\appserv\HR8DMO\psappsrv.cfg. An example hostName setting is //myserver.mycompany.com:9210. If you do not specify the port number, the default port number of 9000 is used.

      jarPath

      Enter the value peoplesoft_lib_dir, the directory where you placed the PeopleSoft libraries.

   8. Click OK.
6. Copy server-specific files.
   1. Extract psft8adapter.jar from peoplesoft_home\psft.rar.
   2. Copy this file to the was_root\lib directory, where was_root is the directory where WebSphere Application Server is installed. For example, C:\WebSphere\AppServer.
   3. Restart WebSphere Application Server.
7. The final step is importing the component interface list retrieval definition into PeopleSoft. There are two versions of the component interface: one for PeopleTools 8.18 and another for PeopleTools 8.42. If you are running PeopleTools 8.42 skip to step 8.
   Note: The component interface in the project, WPS_PS_CILIST, has been created and tested on PeopleTools 8.18, and is in general limited to that version of PeopleTools. If you attempt to import a component interface definition into another version of PeopleTools, you may crash the PeopleSoft Application Designer.
   1. Extract the contents of peoplesoft_home\wps_ps_cilist.zip to a directory of your choice (referred to as ci_home).
   2. Start the PeopleSoft Application Designer. To ensure that you can perform the steps below, log in to the Application Designer in two-tier mode.
   3. Select File > New to create a new project.
   4. Select File > Copy Project from File and specify the CI_home directory in the Import Directory field. You can enter the path directly or click "..." to browse to it.
   5. Verify that WPS_PS_CILIST is selected in the Project Name field.
   6. Click Copy.
   7. Select File > Save Project As, and enter a project name of your choice.
   8. Click OK.
   9. Exit the PeopleSoft Application Designer.
   10. Log into the PeopleSoft Web application.
   11. Select PeopleTools > Maintain Security > Use > Permission Lists .
   12. Add the imported component interface, WPS_CI_LIST, to a permission list. You can use an existing permission list or create a new one. Select the Component Interface tab on the permission list to display the panel for adding the component interface.
   13. Edit the component interface to allow full access to all methods in it.
   14. Click Save to save your permission list changes.

       Note: Ensure that the intended user of the portlets participates in at least one role that contains this permission list.

   15. Skip step 8.

   Note: The component interface in the project, WPS_PT842_CILIST, has been created and tested on PeopleTools 8.42 and is in general limited to that version of PeopleTools. If you attempt to import a component interface definition into another version of PeopleTools, you may crash the PeopleSoft Application Designer.

   1. Extract the contents of peoplesoft_home\wps_pt842_cilist.zip to a directory of your choice (referred to as ci_home).
   2. Start the PeopleSoft Application Designer. To ensure that you can perform the steps below, log in to the Application Designer in two-tier mode.
   3. Select File > New to create a new project definition.
   4. Select Tools > Copy Project > From File and specify ci_home\WPS_PT842_CILIST\WPS_PST842_CILIST.ini directory in the filename field. You can enter the filename directly or browse to it.
   5. Verify that WPS_PT842_CILIST is selected in the Projects field.
   6. Click Open.
   7. Click Copy on the Copy from File dialog box.
   8. Select File > Save Project As and enter a project name of your choice.
   9. Click OK.
   10. Exit the PeopleSoft Application Designer.
   11. Log in to the PeopleSoft Web application.
   12. Select PeopleTools > Security > Permissions and Roles > Permission Lists.
   13. Add the imported component interface, WPS_CI_LIST, to a permission list. You can use an existing permission list or create a new one. Select the Component Interface tab on the permission list to display the panel for adding the component interface.
   14. Edit the component interface to allow full access to all methods in it.
   15. Click Save to save your permission list changes.

       Note: Ensure that the intended user of the portlets participates in at least one role that contains this permission list.

WebSphere Portal 4.x:

If you have a previous version of Application Builder installed, you must first ensure that you have the current JCA adapter. To determine if the JCA adapter is out-of-date, open ra.xml in <was_root>\installedConnectors\siebel.rar\META-INF\. The current version number is 1.1. There should be four configuration properties: connectString, jarPath, traceLevel, and language. If any of these properties are missing, you must remove the JCA adapter and install the new version.

Use the following steps to remove the Siebel JCA adapter:

1. Open the WebSphere Application Server Administrative Console.
2. Remove any existing connection factories under the Siebel adapters.
3. Remove the Siebel adapter.
4. Close the Administrative Console.
5. Stop the Application Server.
6. Remove the following files from was_root\lib\app:
   • SiebelJI_enu.jar
   • SiebelJI_common.jar
7. Remove the siebeladapter.jar from was_root\lib\app\.
8. Start the Application Server.

Install the JCA adapter siebel.rar using the following steps:

1. Extract the contents of the download file (1wp10003t.zip) to a directory of your choice, referred to as siebel_home.
2. Create a new empty directory in your hard drive, referred to as siebel_lib_dir.
3. Copy the following files from the Siebel server to siebel_lib_dir:
   • SiebelJI_enu.jar
   • SiebelJI_common.jar
4. Deploy the Siebel JCA adapter in WebSphere Application Server
   1. Ensure that the WebSphere Application Server Administration Server service is running.
   2. Start the WebSphere Application Server Administrator's Console.
   3. Double-click WebSphere Administrative Domain in the tree view.
   4. Double-click Resources in the tree view.
   5. Right-click on J2C Resource Adapters, and select New.
   6. On the General tab of the J2C Resource Adapters Properties window, enter the following:
      • A name for the resource adapter, such as Siebel.
      • A description, such as Siebel JCA Connector.
   7. In the Archive file name field, click the button labeled "..." to display the Install Driver window.
   8. Select the node where you want to deploy the resource adapter and specify the path and file name of the RAR file by doing one of the following:
      • Entering the path and file name directly in the Rar file field.
      • Clicking Browse to locate the file.
   9. Click Install. The J2C Resource Adapters Properties window is updated to display the name of the RAR file you specified.
   10. Click OK to install the resource adapter. A confirmation message is displayed when the resource adapter is installed.
   11. Click OK to dismiss the message. The Administrator's Console is updated to display information about the resource adapter.
5. For each Siebel application, define a connection factory for the Siebel JCA adapter.
   1. Double-click on J2C Resource Adapters in the tree view.
   2. Double-click on the resource adapter you just deployed. For example, Siebel.
   3. Right-click on J2C Connection Factories, and select New.
   4. On the General tab of the J2C Connection Factories Properties window, enter the following:
      • A name for the connection factory that references the Siebel application, such as Siebel Call Center. The applications to create a connection factory for may include:
        • Siebel Call Center
        • Siebel eChannel Partner Portal
        • Siebel ERM
        • Siebel Marketing
        • Siebel Sales
      • The JNDI binding path. The convention for this value is based on the application for which you are creating the connection factory, such as eis/siebel/SCCObjMgr for the Siebel Call Center connection factory. However, you can specify any JNDI binding path as long as it does not conflict with another JNDI path name. Note that this value must also be specified as the JNDI binding path configuration parameter in configuration mode for each Siebel portlet. Recommended JNDI binding path values include:
        • Siebel Call Center: eis/siebel/SCCObjMgr
        • Siebel eChannel Partner Portal: eis/siebel/eChannelObjMgr
        • Siebel ERM: eis/siebel/ERMObjMgr
        • Siebel Marketing: eis/siebel/eMarketObjMgr
        • Siebel Sales: eis/siebel/SSEObjMgr
   5. Click the Connections tab.
   6. Specify the properties for the Siebel system you want to connect to by selecting the property from the list and entering a value in the entry field:

      connectString

      The connection string used to contact the Siebel server.

      The general format for this value is siebel://[machine name]/[enterprise name]/[object manager]/[servername]. The [object manager] value in the connection string should correspond to that specified in the JNDI binding path. For example, if you are defining a connection factory with a JNDI binding path of eis/siebel/ERMObjMgr, you would specify a connection string like siebel://machine1.mycompany.com/siebel/ERMObjMgr/server1. For details on the connection string format, refer to the Siebel documentation.

      jarPath

      Enter the value siebel_lib_dir, the directory where you placed the Siebel libraries.

   7. Click OK.
   8. Repeat the steps to create a connection factory for the remaining Siebel applications.
6. Copy server-specific files.
   1. Extract the siebeladapter.jar file from the siebel_home\siebel.rar file, and copy it to the was_root\lib directory.
   2. Restart WebSphere Application Server.

If you have a previous version of Application Builder installed, you must first ensure that you have the current JCA adapter. To determine if the JCA adapter is out-of-date, open ra.xml in <was_root>\installedConnectors\siebel.rar\META-INF\. The current version number is 1.1. There should be four configuration properties: connectString, jarPath, traceLevel, and language. If any of these properties are missing, you must remove the JCA adapter and install the new version.

Use the following steps to remove the Siebel JCA adapter:

1. Log in to the administrative console using a Web browser.
2. Remove any existing connection factories under the Siebel adapters.
3. Remove the Siebel adapter.
4. Stop the Application Server.
5. Remove the following files from was_root\lib\app:
   • SiebelJI_enu.jar
   • SiebelJI_common.jar
6. Remove the siebeladapter.jar from was_root\lib\app\.
7. Start the Application Server.

Install the JCA adapter siebel.rar using the following steps:

1. Extract the contents of the download file (1wp10003t.zip) to a directory of your choice, referred to as siebel_home.
2. Create a new empty directory in your hard drive, referred to as siebel_lib_dir.
3. Copy the following files from the Siebel server to siebel_lib_dir:
   • SiebelJI_enu.jar
   • SiebelJI_common.jar
4. Deploy the Siebel JCA adapter in WebSphere Application Server
   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 directly to siebel.rar.
      • Clicking Browse to locate the local file.
   6. Select the node on which to install the RAR file and click Next.
   7. Enter a name for the resource adapter, such as Siebel. Click OK.
   8. Save the configuration changes.
5. For each Siebel application, define a connection factory for the Siebel JCA adapter.
   1. Click on Resource Adapters in the navigation tree.
   2. Click on the resource adapter you deployed in step 4. (For example: Siebel.)
   3. Under Additional Properties, click on J2C Connection Factories.
   4. Click New.
   5. Enter the following:
      • A name for the connection factory that references the Siebel application, such as Siebel Call Center. The application to create a connection factory may include:
        • Siebel Call Center
        • Siebel eChannel Partner Portal
        • Siebel ERM
        • Siebel Marketing
        • Siebel Sales
      • The JNDI binding path. The convention for this value is based on the application for which you are creating the connection factory, such as eis/siebel/SCCObjMgr for the Siebel Call Center connection factory. However, you can specify any JNDI binding path as long as it does not conflict with another JNDI path name. Note that this value must also be specified as the JNDI binding path configuration parameter in configuration mode for each Siebel portlet. Recommended JNDI binding path values include:
        • Siebel Call Center: eis/siebel/SCCObjMgr
        • Siebel eChannel Partner Portal: eis/siebel/eChannelObjMgr
        • Siebel ERM: eis/siebel/ERMObjMgr
        • Siebel Marketing: eis/siebel/eMarketObjMgr
        • Siebel Sales: eis/siebel/SSEObjMgr
      • Click OK.
      • Click on the connection factory just created.
      • Under Additional Properties, click on Custom Properties.
      • Specify the properties for the Siebel system you want to connect to by selecting the property from the list and entering a value in the entry field:

        connectString

        The connection string used to contact the Siebel server.

        The general format for this value is siebel://[machine name]/[enterprise name]/[object manager]/[server name]. The [object manager] value in the connection string should correspond to that specified in the JNDI binding path. For example, if you are defining a connection factory with a JNDI binding path of eis/siebel/ERMObjMgr, you would specify a connection string like siebel://machine1.mycompany.com/siebel/ERMObjMgr/server1. For details on the connection string format, refer to the Siebel documentation.

        jarPath

        Enter the value siebel_lib_dir, the directory where you placed the Siebel libraries.

      • Click OK.
      • Repeat the steps to create a connection factory for the remaining Siebel applications.

The WebSphere Portal content publishing Runtime server and the Application Portlet Builder must be installed on the same WebSphere Portal. The builder obtains metadata from content resources that have been published to the WebSphere Portal content publishing Runtime server.

Portlet installation

Once you have completed the configuration steps, deploy the Application Portlet Builder in your portal environment using the following files from the extracted contents of the download file:

• WebSphere Portal 4.1.x
  • WPAIPortletBuilders41.war
  • WPAIDefaultTemplate41.war
  • WPAIDominoTemplate41.war
• WebSphere Portal 4.2.x
  • WPAIPortletBuilders.war
  • WPAIDefaultTemplate.war
  • WPAIDominoTemplate.war
• WebSphere Portal 5.0.x
  • WPAIPortletBuilders50.war
  • WPAIDefaultTemplate50.war
  • WPAIDominoTemplate50.war

See the WebSphere Portal documentation for portlet installation instructions.

Configuration parameters

There are no configuration parameters for this portlet.

WPAI Profile Service

Large enterprise applications such as SAP have certain pieces of information which are frequently needed by users when querying information. The WPAI Profile Service expands upon the already existing user profile provided by WPAI (first name, last name, etc.) by allowing application-specific attributes which are frequently used during queries to be retrieved and cached on a per user basis. These attributes are retrieved "on demand" by the profile service and cached until the user logs out. In addition, since the profile service is actually a portlet service, these cached attributes are available to all WPAI portlets which are accessing the same account on an application.

Installing the WPAI Profile Service

Unzip the install file and perform the following steps to install and configure the profile service:

1. Copy the files WEB-INF/lib/wpai_profile_service.jar and /WEB-INF/lib/boframework.jar to the <WAS_HOME>/lib/app directory.
2. Copy the wpai_profile_service directory to <WAS_HOME>/lib/app
3. Add the following three lines to the file <WAS_HOME>/lib/app/config/services/PortletServiceRegistryService.properties exactly as they appear below:

   com.ibm.wps.portlets.wpai.profileservice.WPAIProfileService= com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl.factory= org.apache.jetspeed.portletcontainer.service.PortletServiceCacheFactory com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl.BASE_CONFIG= wpai_profile_service.base_config

4. Restart the WebSphere Application Server.

Configuring the WPAI Profile Service for Use with SAP

1. Copy the sap_config folder to <WAS_HOME>/lib/app.
2. Restart the WebSphere Application Server.

Setting up Logging for the Profile Service

1. Add the following two lines to the file <WAS_HOME>/lib/app/config/services/LogService.properties exactly as they appear below.
   • messagelogger.com.ibm.wps.portlets.wpai.profileservice = MessageLogger
   • tracelogger.com.ibm.wps.portlets.wpai.profileservice = WPAIProfileServiceTraceLogger
2. Add the following three lines to the file <WAS_HOME>/lib/app/config/jlog.properties exactly as they appear below.

   baseGroup.WPAIProfileServiceTraceLogger.parent=TraceLogger baseGroup.WPAIProfileServiceTraceLogger.isLogging=true

   #comment second out the line above this one to turn off logging for the WPAI Profile Service

   Note: To turn logging off, simply comment out the following statement from the file <WAS_HOME>/lib/app/config/jlog.properties by placing a number sign (#) at the front of the line.

3. Restart the WebSphere Application Server.

Installing the WPAI Profile Service

Unzip the install file and perform the following steps to install and configure the profile service:

1. Copy the files WEB-INF/lib/wpai_profile_service.jar and /WEB-INF/lib/boframework.jar to the <WPS_HOME>/shared/app directory.
2. Add the JAR files to the application server's WPSLib shared library. You can edit WPSLib in the Administrative Console by selecting Environment > Shared Libraries > WPSLib.
3. Copy the wpai_profile_service directory to <WPS_HOME>/shared/app.
4. Add the following three lines to the file <WPS_HOME>/shared/app/config/services/PortletServiceRegistryService.properties exactly as they appear below:

   com.ibm.wps.portlets.wpai.profileservice.WPAIProfileService= com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl.factory= com.ibm.wps.pe.pc.legacy.service.PortletServiceCacheFactory com.ibm.wps.portlets.wpai.profileservice.WPAIProfileServiceImpl.BASE_CONFIG= wpai_profile_service.base_config

5. Restart the WebSphere Portal.

Configuring the WPAI Profile Service for Use with SAP

1. Copy the sap_config folder to <WPS_HOME>/shared/app.
2. Restart the WebSphere Portal.
3. Enable logging for the com.ibm.wps.portlets.businessobject package

Additional references

Additional documentation is included in the download file, 1wp10003t.zip. When you unzip 1wp10003t.zip, you will find the following references in the doc subdirectory:

• WPAI Domino Reference.pdf
• WPAI Implementation Guide.pdf
• WPAI JDBC Reference.pdf
• WPAI PeopleSoft Reference.pdf
• WPAI Profile Service Reference.pdf
• WPAI Runtime Template Reference.pdf
• WPAI SAP Reference.pdf
• WPAI Siebel Reference.pdf
• WPAI WPCP Reference.pdf