Settings related to the application and resources assigned to the consumer associated with the application.
Name of the application associated with the consumer. The application name must be unique within the cluster.
Enclose the application name in double quotes if it contains spaces, for example, name="Commodity Derivatives App".
In the Platform Management Console: Accepts "a-z, A-Z, 0-9 or spaces. Do not use "all" as an application name—it is a reserved word.
On the command line: Accepts all ASCII printable characters except "\ / : * ? ’ | & < or >". Does not accept leading or trailing spaces in application names. Do not use "all" as an application name—it is a reserved word.
Name and path of the consumer with which to associate this application. The consumer must already exist in Symphony. The consumer you associate with the application determines how Symphony allocates resources to the application.
The consumer ID includes the path to the consumer within the consumer tree.
The consumer must be a leaf consumer. A leaf consumer always resides at the lowest level of the consumer tree.
A unique consumer ID must be specified in Symphony, but it is not required to be pre-defined in SymphonyDE. SymphonyDE uses the consumer ID to associate applications and service packages. Only one application can be enabled within a consumer ID and service packages must be deployed to the same consumer ID.
Specifies the criteria for selecting the resources. The selection string filters out the resources that do not meet the criteria, resulting in a list of one or more eligible resources.
Specifies the sort order for selecting the best resource from the list of eligible resources. The most appropriate resource is listed first, the least is listed last.
The selection string is a logical expression used to select one or more resources to match one or more criteria. Any resource that satisfies the criteria is selected.
The following resources can be used as selection criteria.
Static resources are built-in resources that represent host information that does not change over time, such as the maximum RAM available to user processes or the number of processors in a machine. Most static resources are determined at start-up time, or when hardware configuration changes are detected.
Static resources can be used to select appropriate hosts based on binary architecture, relative CPU speed, and system configuration.
The CPU factor is the speed of the host’s CPU relative to other hosts in the cluster. If one processor is twice the speed of another, its CPU factor should be twice as large. CPU factors are defined by the cluster administrator. For multiprocessor hosts, the CPU factor is the speed of a single processor.
The server static resource is Boolean. It has the following values:
Specifies the value to be used as criteria for selecting a resource. Value can be numerical, such as when referring to available memory or swap space, or it can be textual, such as when referring to a specific type of host.
Sorts the selected resources into an order of preference according to the values of the resources.
The order string acts on the results of a select string, sorting the selected resources to identify the most favorable resources, and eliminate the least desirable resources.
Resources are sorted into ascending order based on the result of an arithmetical expression.
Specifies the workload scheduling policy used. The scheduling policy determines how and when Symphony allocates resources to run services for the application.
taskHighWaterMark—Defines the maximum ratio of unprocessed tasks to CPU slots before more resources are requested.
taskLowWaterMark—Defines the minimum ratio of unprocessed tasks to CPU slots before unused resources are released.
resourceBalanceInterval—Defines when Symphony next checks to determine whether resources need to be requested or released from Platform EGO.
sessionSchedulingInterval—Determines when resources are balanced among sessions.
Applies to the whole application. Ratio is used to determine whether more CPU slots need to be requested to meet the service level agreement of the application. The ratio is the total number of pending and running (unprocessed) tasks in open sessions to CPU slots allocated.
If an application has a taskHighWaterMark of 5, it means that for every 5 unprocessed tasks, 1 CPU slot is requested.
In Symphony DE, the number of CPU slots on a host is configured in the conf/vem_resource.conf file under the Symphony DE installation directory.
In Symphony, the number of CPU slots on a host is configured in the ResourceGroups.xml file and can be configured from PMC.
Applies to the whole application. Ratio is used to determine whether idle CPU slots are released and made available for other applications to use. The ratio is the total number of pending and running (unprocessed) tasks in open sessions to CPU slots allocated.
This enables the application to be configured to avoid charges for unnecessary or unused resources.
For example, you set taskLowWaterMark to 2.0. You have thousands of unprocessed tasks. 100 CPU slots are allocated to the Session Manager.
When the number of unprocessed tasks reaches 400, the ratio of unprocessed tasks to CPU slots is 400/100= 4.0. Session Manager does not release any CPU slots.
When the number of unprocessed tasks reaches 200, the ratio of unprocessed tasks to CPU slots is 200/100=2.0. Session Manager does not release any CPU slots.
When the number of unprocessed tasks drops below 200, Session Manager releases slots until the ratio becomes 2.0 or greater.
The value of the low-water mark should be less than or equal to the high-water mark.
If taskLowWaterMark is 1.0 or less, any resources the application releases must be idle. If taskLowWaterMark is equal to 0, the application never returns resources voluntarily.
Minimum number of seconds between checks to determine whether the session manager should release unused resources or request additional resources for the application.
resourceGroupName—Defines the resource groups available to an application
sessionSchedulingInterval—Determines when resources are balanced among sessions
taskHighWaterMark—Defines the maximum ratio of unprocessed tasks to CPU slots before more resources are requested
taskLowWaterMark—Defines the minimum ratio of unprocessed tasks to CPU slots before unused resources are released
Minimum number of milliseconds between checks to determine whether compute resources need to be reallocated among sessions.
The system reallocates resources according to application session priority, scheduling policy, and pending tasks.
Specifies whether the session manager, service instance manager, and service instances are prestarted for enabled applications when Symphony is started, or when an application is enabled.
Number of seconds the session manager waits for the client to reconnect when the connection between the client and session manager is broken.
When abortSessionIfClientDisconnect is true, sessions which are open on the client connection are aborted if a disconnected client does not reconnect to the session manager.
The transientDisconnectionTimeout counter is reset when a client connects or re-connects to the session manager. Reconnection is done by the Symphony Client API, which is transparent to the client application.
Used for recoverable sessions. Specifies whether or not the session manager caches data before writing to disk.
When set to true, data is not cached, it is immediately written to disk. When set to false, data is cached before it is written to disk. Note that the setting in flushDataAsap does not affect any operating system configuration. You need to disable write-behind caching for your operating system. On Windows, see http://support.microsoft.com/kb/247485 for more details. On Linux, contact your system administrator.