What Symphony daemons/processes are running on my cluster?

The Symphony daemons running on cluster hosts depend on the role of the host. Symphony consists of two components: SOAM and EGO.

All hosts

On all hosts in cluster, the following system services will be generally available:

  • lim

  • elim

  • pim (Linux only)

  • pem

Master host

On a master host, the following processes or system services are running:

  • vemkd: The enterprise cluster kernel is a process automatically started on one of the hosts within the cluster. It provides a core set of centralized functions that leverage the capabilities of host-level agents. The kernel integrates the resources of all hosts and performs many-to-one virtualization so that mixed physical resources appear to clients as a single virtual computer.

  • melim: The master elim (external load information manager)

  • egosc: The service controller is always started on the EGO cluster kernel host. It is responsible for starting other system services. Acting as a client to the EGO cluster kernel, it requests resource allocations for running services. It ensures that services are running by detecting failures and restarting service instances based on availability plans.

Management host

On management hosts, the following eight system services, can be found per cluster.

  • SD: SOAM session director

    Corresponds to session director process.

  • RS: Repository service

    Corresponds to repository service process.

  • WEBGUI: The WEBGUI service (Platform Management Console) is a web-based graphical user interface for administrators and operations staff. The Console is extensible to enable higher-order services to add functionality for managing workload- or application-specific interfaces.

    Corrsponds to WSM and Java processes.

  • purger: The purger service is used by the reporting feature, and manages the relational database size by deleting old data at regular intervals.

    Corresponds to Java process.

  • plc: The plc service is used by the reporting feature, and manages the data loader plug-ins.

    Corresponds to Java process.

  • derbydb: This Apache Derby service runs as a system service when first installed. It is used primarily for demo clusters. The derbydb service is only enabled if an environment variable is set prior to installation (Linux) or during the Windows installation

    Corresponds to Java process.

  • WebServiceGateway: The web service gateway (WebServiceGateway) service is a runtime component of EGO. The gateway provides a standards-based web services interface for web service clients to access EGO functionality. The web service client sends its request to the gateway via SOAP protocol. The gateway calls the EGO C APIs to perform the required operations on behalf of the web service client and returns the results.

    Corresponds to wsgserver process.

  • ServiceDirector: Services are dynamically started and can therefore run on any host. This means that clients have to dynamically locate services to access them. Clients can locate services explicitly via API calls to the service controller that starts and tracks those services; alternatively, the service director provides a mechanism, based on standard DNS, for redirecting client requests to the physical instance of that service.

    Starts named.

On management hosts, one SOAM daemon per application can be found.

  • SSM: Session Manager

Compute host

On a compute host when you start workload, following SOAM daemons can be found:

  • SIM

  • <service-instance>, which is the user’s application