Configuring WebSphere Portal for SAP data sources

You must be deploying to WebSphere Portal server v5.1.

1. Deploy the SAP JCA adapter in the WebSphere Portal server's root installation directory.

   1. Ensure that the WebSphere Portal server's Administration Server service is running.

   2. Start the WebSphere Portal Administrator's Console.

   3. Click Resources in the navigation tree.

   4. Click Resource Adapters.

   5. In the console workspace area, click Install RAR.

   6. Specify the path and the file name of the RAR file by doing one of the following steps:
      • Entering the path and file name of wpai.sap.rar which is located in <wps_root>/installableConnectors, where <wps_root> is the installation directory of WebSphere Portal.

      • Clicking Browse to locate the local file.

   7. Select the node where you want to deploy the resource adapter. Click Next.

   8. 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 "SAP". Click OK.

   9. Save the configuration changes.

2. Define a connection factory for the SAP 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, SAP.

   3. Under Additional Properties, click J2C Connection Factories; then click New. There must be exactly one J2C connection factory created for each connection used to connect to the SAP server.

   4. Enter the following information:
      • A name for the connection factory, such as SAP Connection Factory. The name for the connection factory must be the same as the connection name which was defined in the SAP wizard.

      • The JNDI binding path. The convention for this value is eis/SAP/, which is based on the connection name defined by the SAP wizard. The name is comprised of the prefix "eis/SAP/" and the connection name, such as eis/SAP/mySAPConnection1.

        If the JNDI binding path names do not follow the naming convention, they must be mapped to the internal JNDI names used by the SAP portlets. For additional information on mapping resource references for web applications please refer to ../../com.ibm.etools.j2eeapp.doc/topics/tjaddrefresource.html.

   5. Click OK; then click on the connection factory you just created.

   6. Under Additional Properties, click Custom Properties.

   7. Specify the properties for the SAP 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 SAP server to which you want to connect. For example, mysap.mycompany.com.

      • clientNumber: Enter the SAP client number.

      • systemNumber: Enter the SAP system number.

      • language: Enter the two letter country code. The default value is EN for English.

      • traceLevel: Enter the trace level (None=0, error=1, warning = 2, debug = 3, and entry and exit=4). The default value is 1.

   8. Click OK.

3. Restart the WebSphere Portal server.

 

Related concepts

SAP data access
Siebel data access

 

Related tasks

WPAI data access portlets to a WebSphere Portal server. This is the recommended method of publishing to the production server.">Manually deploying WPAI data access portlets