SAP Connector Guide > Part II: SAP Connector Administration > SAP Connector Administration > SAP BW Reader Administration
  

SAP BW Reader Administration

Before users can use an SAP BW Reader connection to read SAP BW data, an SAP administrator must perform the following tasks:
  1. 1. Download and configure the SAP libraries to read SAP BW data.
  2. 2. Install transport files.
  3. 3. Configure HTTPS.

Step 1. Downloading and Configuring the Libraries for SAP BW Data Extraction

Before you can use an SAP BW Reader connection, you must download the SAP JCo libraries from the SAP Service Marketplace and configure them on the machine where the Secure Agent runs.
Contact SAP Customer Support if you encounter any issues when you download the libraries.
    1. Go to the SAP Service Marketplace: http://service.sap.com/connectors
    Note: You will need SAP credentials to access the Service Marketplace.
    2. Download the appropriate installer for 32-bit or 64-bit SAP JCo libraries and unzip the file:
    Secure Agent System
    SAP File Name
    Windows
    sapjco3-NTintel-3.0.11.zip
    Linux
    sapjco3-linuxintel-3.0.11.tgz
    Note: If the Secure Agent runs on a 32-bit machine, download the 32-bit SAP JCo libraries. If the Secure Agent runs on a 64-bit machine, download the 64-bit SAP JCo libraries. Verify that you download the most recent version of the libraries.
    3. Set the PATH environment variable to the location of the unzipped file.
    4. Copy the sapjco3.jar file to the following directory: <Informatica Secure Agent installation directory>\main\bin\rdtm-extra\tpl\sap
    Before you copy the jar file, you must create the tpl\sap directory within the rdtm-extra directory if the tpl\sap directory does not already exist.
    Note: If you had created the 447900 plugin folder earlier, you must delete the sapjco3.jar file from the plugin folder after you upgrade the SAP Connector. The 447900 folder will contain the tpl.properties file. You must retain the tpl.properties file in the plugin folder.
    5. Configure the JAVA_LIBS property in Informatica Cloud.
    1. a. Log in to Informatica Cloud.
    2. b. Click Configure > Runtime Environments to access the Runtime Environments page.
    3. c. To the left of the agent name, click Edit Secure Agent.
    4. d. From the Type list, select Tomcat JRE.
    5. e. Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.
      6. Operating System
      Value
      Windows
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar;../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Linux
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar:../bin/rdtm/javalib/sap/sap-adapter-common.jar
    6. f. Click OK to save the changes.
    7. g. Restart the Secure Agent.
    8. h. Repeat steps a through g on every machine where you installed the Secure Agent.
    6. Restart the Secure Agent.

Step 2. Installing SAP BW Reader Transport Files

Install the SAP BW Reader transport files on the SAP machines that you want to connect to. Before you install the transports on the production system, install and test the transports in a development system.

Installing Transport Files

Install transport files from a Secure Agent directory to read data from a Unicode SAP system. The transport files are for SAP NetWeaver BW version 7.x. To install transport files for an earlier version, contact Informatica Global Customer Support.
    1. Find the transport files in the following directory on the Secure Agent machine:
    <Informatica Secure Agent Installation Directory>\main\bin\rdtm\sap-transport\SAPBWReader
    2. Copy the cofile transport file to the Cofile directory in the SAP transport management directory on each SAP machine that you want to access.
    The cofile transport file uses the following naming convention: RUN_BWRDR_K<number>.g00
    3. Remove "RUN_BWRDR_" from the file name to rename the cofile. For example, for a cofile transport file named RUN_BWRDR_K900723.g00, rename the file to K900723.g00.
    4. Copy the data transport file to the Data directory in the SAP transport management directory on each SAP machine that you want to access.
    The data transport file uses the following naming convention: RUN_BWRDR_R<number>.g00
    5. Remove "RUN_BWRDR_" from the file name to rename the file. For example, for a data transport file named RUN_BWRDR_R900723.g00, rename the file to R900723.g00.
    6. To import the transports to SAP, in the STMS, click Extras > Other Requests > Add and add the transport request to the system queue.
    7. In the Add Transport Request to Import Queue dialog box, enter the request number for the cofile transport.
    The request number inverts the order of the renamed cofile as follows: g00K<number>.
    For example, for a cofile transport file renamed as K900723.g00, enter the request number as g00K900723.
    8. In the Request area of the import queue, select the transport request number that you added, and click Import.

Step 3: Configuring HTTPS

To connect to SAP through HTTPS and read data from SAP BW sources, you must configure the machine that hosts the Secure Agent and the machine that hosts the SAP system. You must also enable HTTPS when you configure an SAP BW Reader connection in Informatica Cloud.
Perform the following configuration tasks on the Secure Agent and SAP systems:
HTTPS Configuration on the Secure Agent System
To configure HTTPS on the machine that hosts the Secure Agent, perform the following tasks:
  1. 1. Create a certificate using OpenSSL and JAVA KeyTool.
  2. 2. Convert the OpenSSL certificate (PKCS#12 certificate) to SAP specific format (PSE) using the SAPGENPSE tool.
Currently, self-signed certificates are supported.
HTTPS Configuration on the SAP System
To configure HTTPS on the machine that hosts the SAP system, perform the following tasks:
  1. 1. Enable the HTTPS service on the SAP system.
  2. 2. Import the certificate in PSE format to the SAP system trust store.