Specifying Analytic Server Instance Quantities

Before you boot the application server domain, specify the appropriate minimum and maximum number of allowed analytic server instances. The values you specify depend on your assessment of how many users you expect to be using applications that process analytic instances.

Consider the typical number of analytic instances in a domain that are being processed at any given moment as your minimum, and the possible total number of analytic instances that might simultaneously require processing as your maximum. The most appropriate values produce the fastest system response without unused server instances consuming memory unnecessarily.

To specify analytic server instances:

  1. On the Quick-Configure menu for the domain, enter the menu number for Custom Configuration.

    The Custom Configuration environment launches, and prompts you to indicate whether you want to change any configuration values.

  2. Enter y to indicate that you want to change configuration values.

    Custom Configuration prompts you to decide whether to change any values for each configuration item in turn.

  3. Press Enter to accept the default answer for each item presented, until the following entry appears: 

    Values for config section - PSANALYTICSRV

  4. Enter y to change the values for PSANALYTICSRV.

    You're prompted for each value in turn.

  5. Specify the minimum number of instances.

    This defines the number of analytic server instances that start when you boot the application server domain. There are always at least this number of instances running. The default value of this parameter is 3.

  6. Specify the maximum number of instances.

    This defines the maximum number of analytic server instances that can result from spawning new processes. The default value of this parameter is 3.

  7. Press Enter to accept the default answer for each subsequent item presented. When you respond to the last item, PSADMIN loads the new configuration and the PeopleSoft Domain Administration Menu appears.

    You now can boot the domain normally.

Notice that one analytical server can load only one analytic instance. If no analytical server is available to access analytical instance, you may experience one of these two scenarios:

  • Only one tuxedo domain is available.

    This scenario happens when analytical instance accesses 'n+1' th analytical server where n is the maximum number of analytical servers configured. In this scenario, a message appears to alert you that no analytical server is currently available.

  • More than one tuxedo domains are available.

    This scenario happens when analytical instance accesses 'n+1' th analytical server. Analytical instance checks for available tuxedo domains and redirects the request to the domain where analytical server is available. If no analytical server is available in these tuxedo domains, a message appears to alert you that no analytical server is currently available.

Related Topics