4.1.20 Setting the Easy Setup definition file

This subsection describes the procedure to set up the Easy Setup definition file. For notes on setting the Easy Setup definition file, see 4.1.21 Notes on setting the Easy Setup definition file (when using J2EE applications).

1. Copy the template file of the Easy Setup definition file (cmxdefcombinedmodel.xml) to any location.

   The template file of the Easy Setup Definition file is available in the following location:

   For Windows

   Cosminexus-installation-directory\manager\config\templates\cmxdefcombinedmodel.xml

   For UNIX

   /opt/Cosminexus/manager/config/templates/cmxdefcombinedmodel.xml

   Important note

   When using compatibility mode, read cmxdefcombinedmodel.xml as cmxdefcombinedmodel_V9.xml.

   Reference note

   The character encoding of the template file is UTF-8. The system configuration described in the template file is same as the one set up by selecting Standard Setup in the Setup Wizard; without setting the database connection environment.

2. Rename the template file in step 1. with any name.

   Use the text editor to define the information from step 3 to step 7 in the Easy Setup definition file.

3. Define the name, and the display name of the Web system operating on the Management Server.

   Define 1 Web system in the range from the <web-system> tag to the </web-system> tag.

4. When using the load balancer, add the <load-balancer> tag, and define the type of load balancer, or the IP address for management.

   For systems not using the load balancer, definition of the load balancer is not required.

5. Define the physical tier according to the functions used in the system configuration and the J2EE application. Define the common configuration for all logical servers, as and when required.

   The logical servers that are required for the realization of those functions are determined depending on the functions used in the system configuration and the J2EE application, The Smart Composer functionality defines the set of hosts (server) with the same deployment (logical server allocations, and definition setting) for each physical tier. The physical tier defines the type of physical tier and common configuration for all logical servers, in the range from the <tier> tag to the </tier> tag.

6. Define the hosts for allocating the logical servers (service units). Define the configuration for each logical server, as and when required.

   The Smart Composer functionality defines a set of logical servers for each service unit. For service units, define the host for allocating the service unit, the physical tier to which the host belongs, and the configuration of each logical server, in the range from the <unit> tag to the </unit> tag.

7. Define the host.

   Define the names of the hosts belonging to the physical tier, and the host of the Administration Agent. The hosts do not depend on the Web system. When using the hosts defined in the Management Server, you can opt not to define the host. Define the hosts in the range from the <host> tag to the </host> tag.

8. Save the information defined in step 3 to step 7.

To Page Top