4.1.22 Example of creating an Easy Setup definition file

This subsection describes an example of creating an Easy Setup definition file to set up a system used for allocating the Web Servers to different hosts. The following table describes the settings used in the example.

Table 4‒11: Settings used in the example (example of creating an Easy Setup definition file)

Classification	Item	Set up example
Entire system	Name of the Easy Setup definition file	MyWebSystemDef.xml
	Web system name	MyWebSystem
	Service unit name	unit1
Host for allocating the Web Server	Host name	apsv1
	IP Address (Management IP address)#	192.168.100.11
	Name of the logical Web Server	MyWebSystem_HTTP01
	Name of the logical performance tracer	MyWebSystem_PRF01
Host for allocating the J2EE server	Host name	apsv2
	IP Address (Management IP address)#	192.168.100.12
	Name of the logical J2EE server	MyWebSystem_J2EE01
	Name of the logical performance tracer	MyWebSystem_PRF02

Example of creating MyWebSystemDef.xml

<?xml version="1.0" encoding="UTF-8"?>
<model-definition xmlns="http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5">
  <web-system>
    <name>MyWebSystem</name>
    <display-name>MyWebSystem</display-name>
    <description>This is a sample.</description>
 
    <!--Specify the configurations for the Tier.-->
    <tier>
      <tier-type>http-tier</tier-type>
    </tier>
    <tier>
      <tier-type>j2ee-tier</tier-type>
    </tier>
 
    <!--Specify the hosts for each Service Unit.-->
    <unit>
      <name>unit1</name>
      <allocated-host>
        <host-ref>apsv1</host-ref>
        <hosts-for>http-tier</hosts-for>
        <define-server>
          <logical-server-name>MyWebSystem_HTTP01</logical-server-name>
          <logical-server-type>web server</logical-server-type>
        </define-server>
        <define-server>
          <logical-server-name>MyWebSystem_PRF01</logical-server-name>
          <logical-server-type>performance-tracer</logical-server-type>
        </define-server>
      </allocated-host>
      <allocated-host>
        <host-ref>apsv2</host-ref>
        <hosts-for>j2ee-tier</hosts-for>
        <define-server>
          <logical-server-name>MyWebSystem_J2EE01</logical-server-name>
          <logical-server-type>j2ee-server</logical-server-type>
        </define-server>
        <define-server>
          <logical-server-name>MyWebSystem_PRF02</logical-server-name>
          <logical-server-type>performance-tracer</logical-server-type>
        </define-server>
      </allocated-host>
    </unit>
  </web-system>
 
  <!--Specify the settings for the host.-->
  <host>
    <host-name>apsv1</host-name>#
    <agent-host>apsv1</agent-host>#
  </host>
  <host>
    <host-name>apsv2</host-name>#
    <agent-host>apsv2</agent-host>#
  </host>
</model-definition>

# To reduce the impact caused by change in IP address, we recommend that you specify the host name and not the IP address for the <host-name> tag and the <agent-host> tag. However, if the host name changes, specify the IP address for the <host-name> tag and the <agent-host> t tag. If you use the Smart Composer functionality to change the host name of a set up system, you need to set up the system again.

To Page Top