After the project is configured and ready for deployment, you configure physical deployment settings in BusinessEvents Studio using the Site Topology diagram. In this diagram, you assign the processing units and other resources you configured in the CDD editor to physical hosts. It is important to know the details of the physical servers you will deploy to.Before you begin, configure the CDD file and the EAR file for your project. You will reference the processing units defined in the CDD file when configuring the site topology (see Chapter 2, CDD Configuration Procedures).
•
• Add deployment units (DUs) and connect them to the cluster (the blue bar).
• Add one or more processing unit configurations (PUCs) to each deployment unit. Each PUC references one processing unit, and adds deploy-time information. One processing unit can be used in multiple PUCs. One PUC can be used in multiple DUs according to your deployment plan.
• Add hosts (machines) and connect them to the deployment units. Two or more machines can use the same deployment unit, as long as the information, such as file paths, is valid on those machines.One machine can have more than one deployment unit, but this is not the usual use case: one deployment unit per host is the normal model.When you configure the topology file you reference three locations for the CDD and EAR files. The files in each location must be exact copies:
• Project CDD: In the cluster configuration tab, you specify project CDD and EAR files that are locally available to BusinessEvents Studio. They are used for configuring the topology files. If you specify a CDD location in the New Site Topology wizard, it appears in the Project CDD field in the Cluster Configuration tab.
• Master CDD and EAR files: Also in the cluster configuration tab, you specify the location of the master CDD and EAR files. These copies must be available to the machine where MM is running, for use in deployment.
• In the Deployment Unit settings, you specify where MM will place the deployed CDD and EAR files.If you are using the same machine to configure the topology and to run MM server, the project and the master files can be in the same location. These two sets of fields are available in case you are configuring the topology on a different machine from the MM server machine.
In general, you can use one processing unit multiple times to create different processing unit configurations. Similarly you can use one PUC multiple times in different deployment units. However some processing units have deployment-specific settings, as noted next, and cannot be used in this flexible manner.If a processing unit contains agent-instance-specific properties such as agent key and priority settings, you must use that PU in only one PUC, and you must use that PUC in only one DU that is itself used only once in the deployment.PUs with the property tangosol.coherence.localhost set are host-specific. If a deployment unit contains a PUC based on such a PU, you must link it only to the appropriate host.If a PUC contains global-variable overrides, then that PUC is limited in use to the host or hosts in which those override values apply.
Copyright © TIBCO Software Inc. All Rights Reserved.