vem_resource.conf reference

Defines the hosts in the IBM® Spectrum Symphony Developer Edition cluster. This file is not used with IBM Spectrum Symphony on the grid.

Location

The vem_resource.conf configuration file exists on each host in the IBM Spectrum Symphony Developer Edition cluster, including the management host, and all compute hosts.

The default locations for the vem_resource.conf file are as follows:

Windows: %SOAM_HOME%\conf
Linux®: $SOAM_HOME/conf

Structure

Each line defines a single host.

The vem_resource.conf file must be updated on each host whenever hosts are added or removed, or when the configuration parameters of any host in the network changes.

There are five types of hosts you configure: session manager, compute host, session director, repository service, and GUI service.

Session manager host:

AGENT: port_number:host_name:max_SSMs:0:osType:CPU_factor

Compute host:

AGENT: port_number:host_name:0:max_SIMs:osType:CPU_factor

Session director host:

SD_SDK: port_number:host_name:sd_startCmd

SD_ADMIN: port_number:host_name:sd_startCmd

Repository service host:

RS_DEPLOY: port_number:host_name:rs_startCmd

Attributes

port_number

For AGENT, specifies the port number the EGO emulator (start_agent) uses. The start_agent process runs on each IBM Spectrum Symphony host.

For SD_SDK, SD_ADMIN, specifies port numbers used by the session director.

For RS_DEPLOY, specifies the port number used by the repository service.

host_name

Specifies localhost in single-host environment.

In a multi-host environment, specify using dotted-decimal notation or as a DNS name. Hosts can also have dynamic IP addresses (DHCP).

max_SSMs

Specifies the maximum number of session managers that can be started on this host. For a compute host, specify 0.

max_SIMs

Specifies the maximum number of service instance managers that can be started on this host. Each service instance manager requires one (virtual) slot to run on, therefor the maximum number of SIMs the compute host can run is equal to the number of CPU slots on the machine. For a dedicated session manager host, specify 0 to prevent work from running on this host.

osType

Specifies the operating system type the host runs:

LINUX86: A Linux-based environment.
NTX86: A Windows-based environment.

CPU_factor

Default is 1.

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.

sd_startCmd

Specifies the command that starts the session director.

Specify sd unless you have changed the name of the command or moved the session director executable from the installation directory. In this case, specify the absolute path to the session director executable.

rs_startCmd

Specifies the name of the command that starts the repository service.

Specify rs unless you have changed the name of the command or moved the repository service executable from the installation directory. In this case, specify the absolute path to the repository director executable.

GUI_startcmd

Specifies the name of the command that starts the WEBGUI service.

Specify startguiservice unless you have changed the name of the command or moved the startguiservice script from the installation directory. In this case, specify the absolute path to the startguiservice script.

SOAM_SESSION_NAME_COMPATIBILITY

Specifies if the IBM Spectrum Symphony v4.1 client is supported.

If set to ON, this allows any characters to be used for the session name except for \, /,:, *, ?, ', |, &, <, or >. Additionally, the name cannot start with a hyphen (-).

If set to OFF, only alphanumeric characters, -, _, ,, ., and single spaces are allowed. Additionally, the name cannot start with a hyphen (-).

Examples

Management host also runs workload

In the following example, host1 runs the session director, repository service, GUI service, five session manager processes, and five service instance manager processes per application.

 # Resource configuration file
   #
   # File format:
   # <service name>:<port_number>:<host_name>:<max number of SSMs SD can start>:linebreak pdf<max number of SIMs SSM can start>:<OS_type>:<CPU_factor>
   #
   AGENT:8000:host1:5:5:LINUX86:1
   #
   # SD service information
   # <service name>:<port_number>:<host_name>:<sd startcmd>
    SD_SDK:15051:host1:sd
    SD_ADMIN:15050:host1:sd
    #
   # RS service information
   # <service name>:<port_number>:<host_name>:<rs startcmd>
    RS_DEPLOY:15052:host1:rs

One management host and one compute host

In the following example, the host myfirsthost runs the session director, the repository service, five session manager processes and GUI service. The compute host, mysecondhost runs five service instance manager processes per application.

 # Resource configuration file
   #
   # File format:
   # <service name>:<port_number>:<host_name>:<max number of SSMs SD can start>:linebreak pdf<max number of SIMs SSM can start>:<OS_type>:<CPU_factor>
   #
   AGENT:8000:myfirsthost:5:0:LINUX86:1
   AGENT:8000:mysecondhost:0:5:LINUX86:1
   #
   # SD service information
   # <service name>:<port_number>:<host_name>:<sd startcmd>
    SD_SDK:15051:myfirsthost:sd
    SD_ADMIN:15050:myfirsthost:sd
    #
   # RS service information
   # <service name>:<port_number>:<host_name>:<rs startcmd>
    RS_DEPLOY:15052:myfirsthost:rs