KB18482: How to use the HelloSAP utility to verify connectivity to SAP systems in MicroStrategy Intelligence Server

When connecting Strategy 9.4.1 to a SAP BW/BI system, it may be desired to test the connection parameters outside of Strategy itself. For relational databases, this may be done using DB Query Tool; for XMLA, XMLATest should be used.
 
Connection testing may be carried out using the Java utility HelloSAP provided with Strategy installations.
This document provides instructions for using this tool on Windows operating systems. Refer to the following Strategy Knowledge Base document for steps to use this tool on UNIX/Linux:
KB41594 - How to use the HelloSAP utility to verify connectivity to SAP systems in Strategy Intelligence Server Universal 9.x
 
Note: If it is possible to import cubes from SAP, then connection parameters are already established and there is no need to use HelloSAP.

1. Navigate to the Strategy Common Files folder, typically C:\Program Files\Common Files\Strategy.
2. If using JCo 2.x connector files, locate the file HelloSAP.ini and open it in a text editor. If using the JCo 3.x connector files, locate the HelloSAP3.ini file.
    
   Refer to the following technical notes for information on how to setup Strategy connectivity with SAP BW using JCo 3.x or JCo 2.x.
   
   KB38435 - How to setup SAP BW connectivity with Strategy Intelligence Server 9.0.2 - 9.2.x running on Windows, using JCo 3.x connectors. 
   
   
   KB11063 - How to set up SAP connectivity with the Strategy Intelligence Server 9.x on Windows, using JCo 2.x connector files.
   
   
3. Supply the connection parameters as given by the SAP administrator.
   USER=
   PASSWORD=
   APPSERVER=
   ROUTERSTRING=
   SYSNR=
   LANG=EN
   CLIENT=
   
4. Save the changes to this file.
5. If using JCo 2.x connectors, edit the file HelloSAP.bat; If using JCo 3.x connector files, edit the HelloSAP3.bat file. Do not run it immediately. HelloSAP.bat file contains one line in the following form. HelloSAP3.bat also has similar content referring to the required executables and paths. 
   "path\tojava" -classpath "<replace_by_sapjco.jar_location>;HelloSAP.jar" com/MicroStrategy/Database/JCO/HelloSAP/HelloSAP HelloSAP.ini
   
6. For "\path\to\java," substitute the location of the Java virtual machine executable on the machine. In Windows environments, if the Java runtime environment is included in the system PATH environment variable, it may not be necessary to supply the full path here. If using JCo 2.x connectors use 32 bit java while if using JCo 3.x connectors use 64 bit java. 
7. For "<replace_by_sapjco.jar_location>" or "<replace_by_sapjco3.jar_location>", substitute the location of the sapjco.jar or sapjco3.jar files.
8. From the command line, navigate to the folder that contains the HelloSAP.bat or HelloSAP3.bat script. Execute the required script.

A successful connection will produce results such as the following: 
Reading connection info ...
User: -----
PassWord: -----
Application Server: -----
Router String:
System Number: --
Language: --
Client: ---
Trying to connect to SAP system ...
Created JCO Client
Connected to SAP system
Closed connection
HelloSAP succeeded in connecting to SAP system
 
Otherwise, an error will be displayed. Errors observed here should be addressed prior to connecting to the SAP system via Strategy Intelligence Server 
Consult the following Strategy Knowledge Base technical note for information on the errors that may be seen when confirming connectivity to SAP BW/BI.
KB18481: Typical connectivity errors that may be encountered when connecting to SAP BW/BI systems in MicroStrategy Engine