KB38537: How to set up SAP BW connectivity with MicroStrategy Intelligence Server Universal, using JCo 3.x connectors.

Prerequisites for SAP BI connectivity
Strategy requires the following 2 files to be installed on the Strategy Intelligence Server machine, when using JCo 3.x connector files. These files are proprietary to SAP and must be obtained from the download area of the SAP One Support Launchpad : SAP One Support Launchpad. The version of the connector files is dependent on the version of the SAP BW server. Strategy does not certify/support a specific version of the connector files. Customers should use their own logins to access the SAP Service Marketplace.

• libsapjco3.so
• sapjco3.jar

For all supported UNIX/Linux platforms, the JCo 3.x connector files should be 64-bit.
Strategy uses an additional Java executable, JCO.jar, as the bridge between the Strategy database connection process and SAP's Java Connector. JCO.jar is installed as part of the normal Strategy installation under /jar, where is the installation directory chosen during the installation procedure.
Configuration of the Strategy system environment 
Perform the following steps to prepare the Strategy Intelligence Server machine for SAP BI connectivity. 

1. Copy the

   sapjco3.jar

   library to the

   /jar

   location. For example, if the Strategy install directory is

   opt/mstr/MicroStrategy/install

   , copy the

   sapjco3.jar

   library to

   /opt/mstr/MicroStrategy/install/jar

   .
   If desired, a copy or symbolic link to sapjco3.jar can be saved in

   /jar.

   
   
   Note: Do not modify the path to

   JCO3.jar

   . The Strategy installer places it in the

   jar/

   directory automatically and configures the registry accordingly. Changes to the

   JCO3.jar

   path will cause connectivity errors.
    
   
2. Copy the

   libsapjco3.so

   file to the

   /lib

   location. For example, if the Strategy install directory is

   /opt/mstr/MicroStrategy/install

   , copy the

   libsapjco3.so

    file to 

   /opt/mstr/MicroStrategy/install/lib.

   
   
3. (Optional) Strategy requires access to a Java Virtual Machine library. A Java runtime environment is installed by the Strategy installer, and the location of its jvm.so (or jvm.a etc.) is automatically populated into the MSIReg.reg key HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\JNI Bridge\Config for DataServices\64-bit JVM\JavaVM Path. Normally there should be no need to modify this path; however, if the system administrator prefers to use another JVM version, the location may be configured here.
   

Database instance configuration for SAP BW
This is comparable to the Database Instance definition for SQL databases. Database Instance configuration takes place in Strategy Developer, which runs only in Microsoft Windows.

• Create a new database instance. In the Database Instance editor, set the "Database connection type" to "SAP BW," as shown below. (Strategy distinguishes between SAP BW 3.x and SAP BW 7.x.).
   
  

• Define a new database connection and database login using the connection details specific to the environment. The following is just a sample. Use the parameters provided by the SAP system administrator.
   
  

• Ensure that the "JCO;" is indicated as an additional string parameter. Strategy Developer should populate the connection string with "JCO;" but it may need to be supplied manually.
  
  Database Connections > Advanced > Additional connection string parameters
   
  

• Set the Strategy Database Instance to use JCo 3.x. In Strategy Intelligence Server, when a new database instance is created for SAP BW, by the default, the java connector version is set to 'Use JCo 3.x' as shown below (Database Instances > Advanced > Java Connector Version)