MicroStrategy ONE

1. Upgrade Preparation

Before you begin the upgrade to MicroStrategy ONE take care of the following items:

  • Log in as root user.

  • Backup the current configuration files for Intelligence Server, Web, Mobile, Library, and Collaboration.

    Intelligence Server

    • MSIReg files
    • odbcinst.ini
    • odbc.ini

    MicroStrategy Library

    • ../webapps/MicroStrategyLibrary/images/
    • ../webapps/MicroStrategyLibrary/plugins/
    • ../webapps/MicroStrategyLibrary/WEB-INF/classes/auth/
    • ../webapps/MicroStrategyLibrary/WEB-INF/classes/config/configOverride.properties
    • ../webapps/MicroStrategyLibrary/WEB-INF/classes/logback.xml
    • Any other customizations including SSL configurations

    MicroStrategy Collaboration

    When upgrading the Collaboration Server, the MicroStrategy Installer preserves the config.json file for the service; however, it does not back up the notification config.json file. If you have modified any notification properties, you need to backup the following and restore it once the upgrade is complete:

    When upgrading the Collaboration Server, the MicroStrategy Installer preserves the config.json file for the service; however, it does not back up the notification config.json file. If you have modified any notification properties, you need to backup the following and restore it once the upgrade is complete:

    Back up the Collaboration Server notification files in the following directory:

    Copy 
    <INSTALL_PATH>\MicroStrategy\Collaboration Server\node_modules\mstr-collab-svc\pluginConfig\dossier

    List of files:

    • config.json
    • email-Invite.template
    • email-Mention.template

    The Collaboration Server utilizes MongoDB as its repository database. MongoDB has a built-in command for database backup, transfer, and restoration.

    MicroStrategy recommends that the MongoDB database be backed up on a regular basis.

    Gather the following information from the dburl field in the config.json file from each server:

    • Username
    • Password
    • Collaboration database name
    • Admin database name

    1. Stop the Collaboration Server and the MongoDB service.

    2. Execute the following command from the destination server: 

      mongodump --host <source_server_name> --db <source_db_name> --username <source_username> --password <source_password> --authenticationDatabase admin --excludeCollection sessions --archive | mongorestore --username <target_username> --password<target_password> --authenticationDatabase admin --drop --archive
    3. Restart the Collaboration Service and the MongoDB service.
  • Send an email to your users to inform that Intelligence Server and Web Server will be down during the upgrade process.
  • Halt any monitoring alerts in case false alarm triggered during upgrades.
  • Check the MicroStrategy Web Administration page and delete any defined Trust Relationships.
  • Restart all services for the machines to be upgraded.
  • Execute service mstr stop to stop Tomcat, MicroStrategy Listener, and Intelligence Server.

  • Unmounting is necessary to prevent the installer from attempting to remove other items in the mounted locations such as the image shares.

    • To view the related mounts and locations, run:

      mount | grep MicroStrategy

    • To unmount each folder, run umount /<path>/<to>/<folder>. For example:

      umount /opt/mstr/MicroStrategy/install/images

  • Use the following commands:

    • Stop puppet: service puppet stop
    • Get process id for any additional puppet processes: ps -ef | grep puppet
    • Kill any remaining processes: kill -9 <processID>
    1. cd /opt/apache/tomcat/latest/webapps/
    2. rm -rf MicroStrategy*
    3. cd /opt/apache/tomcat/latest/work/Catalina/localhost
    4. rm -rf MicroStrategy*
  • Use df -h to check that at least 5GB of disk space is available under /opt/mstr