EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

How to Use APIs to Build and Customize Enterprise Analytics With MicroStrategy SDK


Diego Patterson

Account Executive • MicroStrategy


With the MicroStrategy Web SDK, organizations can easily extend, customize, and integrate MicroStrategy Web in order to meet their unique business needs.

Summary

J2EE based Portal servers support the deployment of third party portlets through a WAR file similar to a normal application server. The Strategy Portlet is deployed using this method. However, when using this deployment method it is hard to keep track of the deployed version, since no actual version number is included in any of the files for the WAR file.
 

How to check the Strategy Portlet version

There is no direct way to check the exact Strategy version, however, a file modification date comparison can be made following this procedure:

  • Locate the Strategy Installation where the Portlets component was installed. This will typically be in the following location:
     
    
    C:\Program Files (x86)\MicroStrategy\Portlets

    Note: The Portlets component of Strategy could have been installed in a different place than the Strategy Web component. 
     
  • In this location, locate the Modification Date for the Portlet WAR file in question, for example, the WAR file for Liferay under the location shown below:

ka04W000000OfmOQAS_0EM4400000025m2.jpeg
  • In the Portal Server locate the Java Archive (JAR) for the Strategy Portlet with the following name: MSTRPortlet.jar

    For Liferay typically in the following location:
     
    
    liferay-portal-6.2-ce-ga3\tomcat-7.0.42\webapps\MSTRPortlet_Liferay\WEB-INF\lib\MSTRPortlet.jar

  • Locate the Modification Date for the Java Archive mentioned in step 3, as shown below:

ka04W000000OfmOQAS_0EM4400000025lr.jpeg
  • Compare both modification dates, and verify that they match. With help of the Strategy Administrator, the version of the installation path in step 1 can be derived from License Manager.

    In this example, the modification time shown above (2/12/2015) corresponds to Strategy 9.4.1 HF8. This method determines that the Strategy Portlet version deployed in the Liferay server above is Strategy 9.4.1 HF8.

    Important Note: If the Strategy administrator does not know the Strategy Version for the installation path mentioned in step 1 contact Strategy Technical Support with the Modification Date located in step 3. 

Comment

0 comments

Details

Knowledge Article

Published:

May 18, 2017

Last Updated:

May 18, 2017