Copyright © Cloud Software Group, Inc. All Rights Reserved

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, for example 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.

• 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, you must recreate the site topology file using the updated CDD. • If you change the site topology, you must restart the MM server.

1. Configure Cluster Properties 

2. Add Deployment Units (DUs)  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’ll 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  Here you specify the host configuration, including the software used on the remote hosts to start remote Core Engine (processes). You must map the DU's to the hosts where you want to deploy them. Multiple hosts can reuse the same deployment unit configuration.

In the topology file, you reference two locations for the CDD and EAR files. The files in each location must be exact copies:

•	Master CDD and EAR files: You specify the location of the master CDD and EAR files. These copies must be manually copied to the specified location on the MM server host, for use in deployment.

•	Deployed CDD and EAR files: In the deployment unit settings, you specify where MM will place the CDD and EAR files when it performs deployment to a remote host.

The project and master CDD can have the same location if you configure the site topology file and run the MM server in the same host. These two sets of fields are available in case you are configuring the topology file on a different machine from the MM server machine.

• All locations specified must already exist. The software does not create directories. • Use the correct path for the operating system of the host (For example, linux versus Windows). • Limitation: One CDD and EAR file per Cluster Machine: Currently deployment is at the Machine level and each machine can have only one copy of the deployed CDD and EAR files. If you specify multiple DUs for the same host, problems may occur because CDD and EAR files are copied only to the location specified for the first DU.

Deployment-Specific Processing Units

In general, you can reference one processing unit multiple times to create different processing unit configurations (PUCs). However processing units that have deployment-specific settings cannot be used in this flexible manner.

Agent-Instance-Specific Properties

If a processing unit contains agent-instance-specific properties (such as agent key and priority settings), you must use it in only one PUC, which must be used in only one DU, that must itself used only once in the deployment.

Host-Specific Processing Units

Processing units can have host-specific settings. If a deployment unit contains a PUC that references such a processing unit, you must link it only to the appropriate host, for deployment.

 

Copyright © Cloud Software Group, Inc. All Rights Reserved