Check Modeling Services in Workstation and Library Logs

If you see error messages appear in the Modeling service, there may be more than one Modeling service running in your environment and/or some services may not be working properly. Starting in MicroStrategy ONE Update 11, you can check the amount of Modeling services running in your environment and see which one is causing the error.

Checking Modeling Services in Workstation

To check how many Modeling Services are running in your environment:

1. Open Workstation.
2. In the Navigation pane, click Monitors.
3. In the left panel, click Services and expand the Intelligence service.

4. The amount of available Modeling services appears in parenthesis next to Modeling.

   

Check Modeling Services in the Library Log File

Starting in the MicroStrategy ONE Update 10 August monthly release, you can check the Modeling service IP and port to find out which modeling service is in-use, and which one is not working.

1. Configure /MicroStrategyLibrary/WEB-INF/classes/logback.xml and add the following code snippet:

Copy

<logger name="com.microstrategy" additivity="false" level="DEBUG">
    <appender-ref ref="FILE"/>
</logger>
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>${LOG_HOME}/MSTRRest.log</file>
    <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
        <!-- daily rollover -->
        <fileNamePattern>${LOG_HOME}/backup/MSTRRest.%d{yyyy-MM-dd}.log</fileNamePattern>
        <!-- keep 30 days' worth of history capped at 3GB total size -->
        <maxHistory>30</maxHistory>
        <totalSizeCap>3GB</totalSizeCap>
    </rollingPolicy>
    <encoder class="net.logstash.logback.encoder.LogstashEncoder"/>
</appender>

2. Restart MicroStrategy Library.

3. The Modeling service IP and port appears in /Apache Software Foundation/Tomcat x.0/logs/MSTRRest.log.

   

Specify the Modeling Service in a Cluster Environment

You can define the Modeling service base URL (services.MicroStrategy-Modeling-Service.baseURL) in configOverride.propertieswithin Library. This forces Library to work with a specific Modeling service.

The configOverride.properties file is located in: