Atomia Automation Server

Resource description

65 views 0

Describing the resources which Atomia Automation Server knows about by binding a resource with a specific module.

Resource description elements

The resource description describes resources Atomia Automation Server knows about, where it will configure simple services and binds a resource with a specific module.

resourceDescription is the root element and it has no attributes. It contains one or more resourcesAndPolicieselements.

<resourceDescription>
<resourcesAndPolicies>
<!-- ... -->
</resourcesAndPolicies>
</resourceDescription>

resourcesAndPolicies has no attributes and contains a list of one or more services and their policies and related resources.

<resourcesAndPolicies>
<serviceAndPolicyList>
<!-- ... -->
</serviceAndPolicyList>
<resourceList>
<!-- ... -->
</resourceList>
</resourcesAndPolicies>

serviceAndPolicyList  has no attributes and contains a list of one or more service elements. The  service element defines a service name and the associated resource assignment policy.

<service name="IIS" resourceAsignmentPolicy="RoundRobin" />

service element attributes are:

  • name – service name. Required attribute.
  • resourceAsignmentPolicy – defines which policy is used for the service. Required attribute.

The resourceList element has no attributes and contains a list of one or more resource elements.

<resource name="IISWebServer1">
<property name="IPAddress">212.200.163.10</property>
<property name="ServerName">s10.troxo.com</property>
<property name="Password" encrypt="true">#####</property>
</resource>

resource element has the following attributes:

  • name – defines a resource name and is a required attribute. resource also has one or more property elements that define resource properties.
    <property name="IPAddress">212.200.163.10</property>
    <property name="ServerName">s10.troxo.com</property>
    <property name="Password" encrypt="true">#####</property>
    

    property elements have a  name attribute to identify a property. The body of this element defines a property value. If the value of the property is kept encrypted in the resource file, the additional attribute is set encrypt so that Automation Server knows to decrypt property value before it uses it. Property encryption can be performed in the Automation Server Client Tool menu.

Keep in mind

Changes made to the resource description file won’t be visible until the Provisioning service is restarted.

Example

Example of a resource description is:

<resourceDescription>
<resourcesAndPolicies>
<serviceAndPolicyList>
<service name="IIS" resourceAsignmentPolicy="RoundRobin"/>
</serviceAndPolicyList>
<resourceList>
<resource name="IISWebServer1">
<property name="IPAddress">212.200.163.10</property>
<property name="ServerName">s10.troxo.com</property>
</resource>
<resource name="IISWebServer2">
<property name="IPAddress">212.200.163.11</property>
<property name="ServerName">s11.troxo.com</property>
</resource>
<resource name="IISWebServer3">
<property name="IPAddress">212.200.163.12</property>
<property name="ServerName">s12.troxo.com</property>
</resource>
</resourceList>
</resourcesAndPolicies>
<resourcesAndPolicies>
<serviceAndPolicyList>
<service name="Dns" resourceAsignmentPolicy="SpecificResource"/>
</serviceAndPolicyList>
<resourceList>
<resource name="PrimaryDNS">
<property name="IPAddress">212.200.163.2</property>
<property name="ServerName">ns1.troxo.com</property>
</resource>
<resource name="SecondaryDNS">
<property name="IPAddress">212.200.163.4</property>
<property name="ServerName">ns2.troxo.com</property>
</resource>
</resourceList>
</resourcesAndPolicies>
<resourcesAndPolicies>
<serviceAndPolicyList>
<service name="Ftp" resourceAsignmentPolicy="SpecificResource"/>
</serviceAndPolicyList>
<resourceList>
<resource name="FtpServer">
<property name="IPAddress">212.200.163.20</property>
<property name="ServerName">120.troxo.com</property>
</resource>
</resourceList>
</resourcesAndPolicies>
</resourceDescription>

In this example, we can see that IIS service can be located on 3 resources: IISWebServer1, IISWebServer2 and IISWebServer3. Each of those resources are described with two properties:

  • IPAddress
  • ServerName

The list of properties can be custom for any group of similar resources. From this example, we can see that RoundRobin resource assignment policy will be used for IIS services. In the resource description, it is enough to define the resource policy and available resources for a root simple service. All child simple services are by convention located on the same resource as their parent.

Was this helpful?