MicroStrategy ONE

Specifying Default Connection, Load Balance, and Timeout Settings

You can specify default connection, load balance, pool size, and timeout settings for all connections to Intelligence Servers.

These default settings can be changed for an individual server. However, certain settings can be specified only at this default Intelligence Server level that apply to all server connections. For example, timeout settings cannot be applied to specific Intelligence Server connections, but can be applied to all Intelligence Server connections.

To Specify Default Connection, Load Balance, and Timeout Settings

  1. Access the Mobile Server Administrator page:
    • In Windows: Choose Start > Programs > MicroStrategy Tools > Mobile Administrator. The Mobile Server Administrator web page opens.
    • In UNIX/Linux: After you deploy MicroStrategy Mobile Server Universal and log on to the mstrMobileAdmin servlet using proper credentials, the Mobile Server Administrator web page opens. The default location of the Administrator servlet varies depending on the platform that you are using.
  2. From the pane on the left, select Default properties. The Default Server Properties page opens.
  3. Select one of the following to determine when and how Mobile Server connects to Intelligence Servers.
    • To ensure that the Mobile Server automatically reconnects to Intelligence Servers when the Mobile Server is started or restarted, select Automatically connect to Intelligence Server when Mobile Server or Intelligence Server is restarted.
    • To ensure that the administrator must manually create a connection to Intelligence Servers by clicking the Connect button, select the User manually connects Mobile Server to Intelligence Server. This is the default option.
  4. In the Port field, specify the default port number for all Intelligence Server connections.
  5. If the Intelligence Servers are in a cluster, you can determine the number of connections within the "pool" of connections. The pool is the number of connections between Mobile and the Intelligence Servers. This is defined at the Intelligence Server level, not at the cluster level. This allows you to grant more or fewer initial connections depending on the size of the Intelligence Server machines.
    • Define the pool size for each Intelligence Server in the cluster in the Initial pool size field. The default initial pool size is 5.
    • Define the maximum pool size for the Intelligence Servers in the Maximum pool size field. The default maximum pool size is 50.
  6. Specify how jobs are balanced between Intelligence Servers in a cluster by entering a value in the Load balance factor field. For more powerful servers in a cluster, this value can be increased to provide an appropriate balance. A larger load balance factor means the server supports a greater load in the server cluster in which it resides. For example, if two servers make up a cluster, one server has a balance factor of 3 and the other has a balance factor of 2, and 20 users log in, 12 are supported by the first server and 8 by the second. The default Load balance factor value is 1.
  7. Establish default server and request timeout settings, as follows:
    • Specify the length of time (in seconds) that a Mobile request should wait for a connection from the connection pool, if the maximum number of connections are all busy. Enter this value in the Server busy timeout field. The default value is 10.
    • Specify the length of time (in seconds) that Mobile waits to receive a response from Intelligence Server. Enter this value in the Request timeout field. The default value is 40.
  8. If there is a firewall between Mobile Server and Intelligence Server, you can ensure that the firewall does not remove connections between Mobile Server and Intelligence Servers. To do this, select the Keep the connection alive between the Mobile Server and Intelligence Server check box. When this setting is enabled, Mobile Server sends a signal to Intelligence Server on each open TCP connection periodically, so that the firewall does not see the connection as idle. For detailed information, see Maintaining TCP/IP connections through firewalls.
  9. Click Save.