The SOAM section contains configuration related to system behavior such as session manager, service instance manager, and how Symphony writes data to disk.
The version of the Symphony middleware.
Configuration related to session manager behavior.
Number of seconds to wait for the session manager to start up before the session director considers it as timed out.
When the process times out, the session director requests EGO to replace the session manager host and tries again to start a new session manager.
The session manager is started when Symphony is started if prestartApplication is true for the enabled application. Otherwise, the session manager is started when a client connects to an enabled application, which does not have running session manager and prestartApplication is false.
String that describes criteria for selecting resources allocated to the session director to start the session manager.
A resource requirement string describes the criteria for defining a set of resources to run session managers. Session managers should run on management hosts. If you have changed the default value of resourceGroupName, you must indicate the select string
"select(mg)"so that only management hosts are selected to run the session managers. Running the session manager on a management host is essential for reliability and recovery.
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.
Resource group from which resources are requested to run session managers. The resource group should be a management host resource group and must be an existing resource group in EGO.
Absolute path in which the session manager process stores data for operations, including paging, journaling and history files.
Paging, journaling, and history data files are saved in subdirectories under the workDir if a relative path is configured for the paging, journaling, and data history paths.
This is not applicable in Symphony DE. In Symphony DE the working directory of the session manager is:
Any accessible absolute path on the network or local disk. To facilitate the session manager recovery, workDir should be set to a directory on a shared file system.
By default, the session manager working directory is the same for all applications. If applications are configured to write to the same directory, the operating system user accounts assigned to start the session manager must have access to that directory. It is recommended that all operating system execution users who start the session managers be in the same primary user group.
If a shared directory is configured in the cluster, the default working directory for the session manager points to the shared location in the host on which session manager runs:
If there is no shared directory configured in the cluster, then the default working directory points to the local location in the host on which session manager runs:
For internal system use only.
Specifies how the system responds to changes in the amount of virtual memory or virtual address space on the session manager host.
AvailableMemory—The boundary manager monitors the amount of virtual memory available on the host. Virtual memory is physical memory plus swap memory that is available on the host.
AvailableVirtualAddressSpace—The boundary manager monitors the amount of virtual address space the session manager can use to map memory. It is possible for the host to have more than enough memory available, which is physical memory plus swap memory, but the process cannot access anymore because it has no available address space to map this memory to.
Specifies the name of the boundary event that triggers a system response when the value of the event is reached.
The system monitors the boundaries defined, available memory, and available virtual address space, to ensure the robust functionality of the session manager. Messages are logged to the session manager log file and administrators are notified through event notification when new event are triggered..
Memory low conditions can be caused by:
The following describes system reactions when a boundary limit is reached:
Specifies the value of a boundary event as a percentage of the entire resource available.
When the availability of the resource monitored falls below the boundary event value, it triggers a system response to ensure the session manager has enough memory to function.
Used with the startUpTimeout (SOAM > SIM) attribute. Defines whether to block this host for the application when the service instance manager times out on process startup. If set to true, when the service instance manager times out on startup, the host is added to the blocked host list and is no longer used for the application unless the host is explicitly unblocked through the Platform Management Console.
Number of seconds to wait for the service instance manager to start up before the session manager considers it as timed out. This parameter works in conjunction with blockHostOnTimeout.
Parameters related to sessions and tasks historical data storage.
Maximum size, in megabytes, the history file can reach before the file is archived at the next polling interval.
When the history file reaches the maximum size specified, the file is renamed by appending a time stamp to the file name.
Maximum number of hours that can elapse before the history file is archived at the next polling interval.
When the history file reaches the maximum age specified, the file is renamed by appending a time stamp to the file name.
Data history file names have the following format:
applicationName_session.soamdb or applicationName_task.soamdb
After renaming the file names would be similar to the following:
Absolute or relative path in which session and task historical files are stored. If relative path is specified, the directory is located under session manager working directory. The path should be accessible by both session director and session manager, so that the session and task historical data can be retrived by command line and PMC.
By default, history files are saved under the following locations:
If you specify an absolute path, all the history files are saved in the specified path. An absolute path must be accessible by both session director and the session manager for this application.
Any absolute or relative path on network or local disk which can be accessed by both session director and session manager.
Parameters related to task input message paging configurations.
Directory where paging files for task input are stored. The path to the file can be specified as a relative or absolute path. If a relative path is specified, paging files are saved in a subdirectory relative to the session manager working directory. The specified directory must be accessible from all management hosts to facilitate session manager failover.
Any accessible absolute or relative path on network or local disk that can be accessed from all management hosts.
Specifies the number of bytes per block for paging. The block size should be large enough to contain the largest message. If the block size is not large enough, the data is spread across multiple blocks, which can slow down paging processes.
Parameters related to task output message paging configurations.
Directory where paging files for task output are stored. The path to the files can be specified as a relative or absolute path. If a relative path is specified, paging files are saved in a subdirectory relative to the session manager working directory. The specified directory must be accessible from all management hosts to facilitate session manager failover.
Data files can be stored on any storage device accessible on the network. To facilitate failover, Symphony working files should be stored on a shared file system.
Specifies the number of bytes per block for paging. The block size should be large enough to contain the largest message. If the block size is not large enough, the data is spread across multiple blocks, which can slow down paging processes.
Parameters related to common data paging configurations.
Directory where the files are stored for common data. The path to the files can be specified as a relative or absolute path. If a relative path is specified, common data files are saved in a subdirectory relative to the session manager working directory. The specified directory must be accessible from all management hosts to facilitate session manager failover.
Data files can be stored on any storage device accessible on the network. To facilitate failover, Symphony working files should be stored on a shared file system.
Specifies the number of bytes per block for paging. The block size should be large enough to contain the largest message. If the block size is not large enough, the data is spread across multiple blocks, which can slow down paging processes.
Parameters related to common data updates paging configurations.
Directory where the files are stored for common data updates. The path to the files can be specified as a relative or absolute path. If a relative path is specified, common data update files are saved in a subdirectory relative to the session manager working directory. The specified directory must be accessible from all management hosts to facilitate session manager failover.
Data files can be stored on any storage device accessible on the network. To facilitate failover, Symphony working files should be stored on a shared file system.
Specifies the number of bytes per block for paging. The block size should be large enough to contain the largest message. If the block size is not large enough, the data is spread across multiple blocks, which can slow down paging processes.