Based on the Microsoft Azure HDInsight platform, with infrastructure based on Apache Kylin, Kyligence Cloud provides an elastic computing architecture and a pay-as-you-go price model, suiting dynamic computing use cases, and reducing operational costs to accelerate business development through cloud technology.
The Kyligence Cloud connector enables connectivity to Strategy Web, enhancing the Strategy product with support for Kyligence Cloud.
For more information please refer to http://kyligence.io/
Table of Contents
- Prerequisites
- Installation
- Update Database Object
- Update data type mapping on Intelligence Server
- Install Connector in all MicroStrategy Web Machines in the Cluster
- Install connector in MicroStrategy Workstation/Desktop
- Validating Correct Installation
- Uninstall
- Remove Database Object
- Remove connector from MicroStrategy Web
1. Prerequisites
- Strategy Secure Enterprise should be installed and configured, including an instance of Strategy Developer, Strategy Web, and the Strategy Intelligence Server.
- The Kyligence ODBC driver has been installed on the machine containing your Strategy Intelligence Server.
- Download and decompress the KyligenceConnectorFiles.zip file attached to this article below.
Please refer to the following links to download and install Kyligence ODBC driver:
2. Installation
The installation of this connector comprises of 4 steps.
- Update DBMS object
- Update data type mapping
- Install connector in Strategy Web
- Install connector in Strategy Workstation and/or Strategy Desktop
2a. Update DBMS object
- Copy DATABASE_KAP.PDS file onto a machine with Strategy Developer installed.
- Follow the steps in KB43537 to load the DBMS object in the DATABASE_KAP.PDS file into Strategy metadata.
KB43537: How to install DBMS objects provided by Strategy Technical Support
2b. Update data type mapping on Intelligence Server
- Copy the file DTMAPPING.xslt and AddConnector.jar files to all the Intelligence Server machines that need to be upgraded
- Find the location of the DTMAPPING.pds file of the Intelligence Server installation
- On Windows the default location is C:\Program Files (x86)\Common Files\Strategy, also referred to in the $MSTR_CLASSPATH environment variable
- Run the following command replacing <location> with the folder where dtmapping.pds file is located.
- Note: Running the command requires the privileges to copy and modify the existing dtmapping.pds file.
- Note: the command will create a backup of the original file in <location>.
java -jar AddConnector.jar --target “<location>\ DTMAPPING.pds” --file DTMAPPING.xslt
- Restart Intelligence Server.
2c. Install connector in all Strategy Web machines in the cluster
- Copy the file DBproperties.xslt and AddConnector.jar files to all the machines that run Strategy Web. Use the location of the files to replace <location1> for the command in step 3.
- Find the location of the DBProperties.xml file. Use this location to replace <location2> as the path to the DBProperties.xml file in the command in step 3. The file can be found in the directory where Strategy Web is deployed. This path will be different depending on the application server used. The following are common examples:
- Microsoft IIS: C:\Program Files (x86)\MicroStrategy\Web ASPx\WEB-INF\xml\DBproperties.xml
- Tomcat (on Windows): C:\Program Files (x86)\Common Files\MicroStrategy\Tomcat\apache-tomcat-8.0.30\webapps\MicroStrategy\WEB-INF\xml\DBProperties.xml
- Tomcat (on Linux): /opt/apache/tomcat/apache-tomcat-8.0.43/webapps/MicroStrategy/WEB-INF/xml/DBproperties.xml
- Run the following command replacing <location2> with the folder where DBProperties.xml file is located.
- Note: Running the command requires the privileges to copy and modify the existing DBproperties.xml file
- Note: on Windows the <location> needs to finish with a backslash (“\”) on Linux with a forward slash (“/”) character
- Note: the command will create a backup of the original DBProperties file in <location2>.
java -jar <location1>AddConnector.jar --target <location2>DBProperties.xml --file <location2> DBproperties.xsl
- After running the above command, please restart your application server.
- For configuring the connector icon:
- By default, the icon in Data Import home page is general icon for Database like below