Site Topology Overview

The site topology file contains deployment time information such as which processing units to deploy to specific hosts in your environment. You need to know information about the computers that will host the agents you plan to deploy, such as the operating system and IP address.

The MM server uses the SSH software as the remote invocation software to start remote processes on UNIX machines.

Note:
  • Changes to the EAR file do not affect the topology configuration. However if the cluster, processing unit, or agent definitions in the CDD file change, recreate the site topology file using the updated CDD.
  • If you change the site topology, you must restart the MM server.

Procedure

  1. Configure Cluster Properties.
  2. Add Deployment Units (DU’s).

    Add DUs as needed. For each DU, specify the following:

    • The deployment location of the CDD and EAR files. MM copies the files to the specified location at deploy time.
    • One or more processing unit configurations (PUCs). You will configure the PUCs in the next step.
  3. Add Processing Unit Configurations (PUCs) to DUs.

    For each PUC, select one processing unit (PU) from the list of PUs defined in the CDD file. Set deploytime properties such as the JMX ports used by MM to communicate with the deployed engine.

  4. Add Hosts.

    Specify the host configuration, including the software used on the remote hosts to start remote Core Engine (processes). Map the DU's to the hosts where you want to deploy them. Multiple hosts can reuse the same deployment unit configuration.