Strategy One

Administering Intelligence Servers and other Strategy Services

Intelligence Server and other Strategy services must be operational to complete certain processes that are part of a System Manager workflow. To support this requirement, you can include the administration of Intelligence Server and other Strategy services as part of a workflow.

Starting, Stopping, or Restarting Strategy Services

You can start, stop, or restart Strategy services as part of a System Manager workflow. This helps to ensure Intelligence Server is operational, which is required to perform various processes. You can also stop Intelligence Server to make system-wide updates and then restart Intelligence Server once all updates are made.

To perform these types of configuration, in System Manager, from the Connectors and processes pane, add the Manage Strategy Service process to your workflow. The following information is required to start, stop, or restart a Strategy service:

  • Action: Determines whether to start, stop, or restart the Strategy service. Select the required action from this drop-down list.
  • You can determine which machine to administer its services for using one of the following options:
    • Local machine: This option performs the start, stop, or restart action for the service of the machine used to deploy the workflow.
    • Remote machine: This option lets you specify the machine that hosts the service to perform the start, stop, or restart action for. You must provide the information listed below:
      • Machine Name: The name of the machine that hosts the service.
      • Login: The name of a valid user to administer the service.
      • Password: The password for the user name that you provided to administer the service. You can use the button to the right of the Password field to determine whether the password characters are shown or asterisks are displayed instead.

  • Service Type: Determines the service to start, stop, or restart. From this drop-down list, you can select one of the following MicroStrategy services:

    • MicroStrategy Intelligence Server: The main service for your MicroStrategy reporting environment. It provides the authentication, clustering, governing, and other administrative management requirements for your MicroStrategy reporting environment.

    • MicroStrategy Listener: Also known as Test Listener. A ping utility that allows you to check the availability of an Intelligence Server on your network, whether a DSN can connect to a database, and whether a project source name can connect to a project source. From any machine that has the Test Listener installed and operational, you can get information about other MicroStrategy services available on the network without having to actually go to each machine.

    • MicroStrategy Enterprise Manager Data Loader: The service for Enterprise Manager that retrieves data for the projects for which statistics are being logged. This data is then loaded into the Enterprise Manager lookup tables for further Enterprise Manager reporting and analysis.

    • MicroStrategy Distribution Manager: The service for Narrowcast Server that distributes subscription processing across available Execution Engines.

    • MicroStrategy Execution Engine: The service for Narrowcast Server that gathers, formats, and delivers the content to the devices for a subscription.

    • Notes: Information to describe this process as part of the workflow.

Determining the Status of Strategy Services

You can retrieve the status of a Strategy service as part of a System Manager workflow. This can help to ensure that required Strategy services are operational, which can be required to perform various processes.

To retrieve this information, in System Manager, from the Connectors and processes pane, add the Get Service Status process to your workflow. The following information is required to retrieve the status of a Strategy service:

You can determine the machine for which to retrieve the service status by using one of the following options:

  • Local machine: Retrieves the status for the service of the machine used to deploy the workflow.
  • Remote machine: Lets you specify the machine that hosts the service to retrieve the status for the service. If you select this option, you must type the name of the machine that hosts the service.

  • Service Type: Determines the service to start, stop, or restart. From this drop-down list, you can select one of the following MicroStrategy services:

    • MicroStrategy Intelligence Server: The main service for your MicroStrategy reporting environment. It provides the authentication, clustering, governing, and other administrative management requirements for your MicroStrategy reporting environment.

    • MicroStrategy Listener: Also known as Test Listener. A ping utility that allows you to check the availability of an Intelligence Server on your network, whether a DSN can connect to a database, and whether a project source name can connect to a project source. From any machine that has the Test Listener installed and operational, you can get information about other MicroStrategy services available on the network without having to actually go to each machine.

    • MicroStrategy Enterprise Manager Data Loader: The service for Enterprise Manager that retrieves data for the projects for which statistics are being logged. This data is then loaded into the Enterprise Manager lookup tables for further Enterprise Manager reporting and analysis.

    • MicroStrategy Distribution Manager: The service for Narrowcast Server that distributes subscription processing across available Execution Engines.

    • MicroStrategy Execution Engine: The service for Narrowcast Server that gathers, formats, and delivers the content to the devices for a subscription.

    • Notes: Information to describe this process as part of the workflow.