Extracting and Customizing an Oracle Traffic Director Move Plan

There are few elements in the Oracle Traffic Director server.xml that you can customize using the move plan. These elements are listed below:

Table C-1 Oracle Traffic Director Elements for Customization

Element	Editable Properties
http-listener	ip, port and server-name
tcp-listener	ip and port
failover-group	virtual-ip
origin-server-pool	origin-servers

You should also modify the following properties of the domain:

• Create a new schema for the target domain and update the schema prefix in the move plan, valid only when domain is full JRF.

• Update the Password file for node manager element. By default the value is </value> which you should modify to <value>/scratch/T2P/password.txt</value>. The password file you provide must exist on the file system.

The following in an example Oracle Traffic Director move plan:

<movableComponent>
  <componentType>OTD</componentType>
  <componentName>test</componentName>
  <Description>otd component</Description>
  <moveDescriptor>
    <configGroup>
      <type>http-listeners</type>
      <configProperty id="http-listener-1">
        <configProperty>
          <name>Ip</name>
          <value>*</value>
          <itemMetadata>
            <dataType>INTEGER</dataType>
            <scope>READ_WRITE</scope>
          </itemMetadata>
        </configProperty>
        <configProperty>
          <name>Port</name>           
          <value>7011</value>
          <itemMetadata>
            <dataType>INTEGER</dataType>
            <scope>READ_WRITE</scope>
          </itemMetadata>
        </configProperty>
        <configProperty>
          <name>ServerName</name>
          <value>abc1234.example.com</value>
          <itemMetadata>
            <dataType>STRING</dataType>
            <scope>READ_WRITE</scope>
          </itemMetadata>
        </configProperty>
      </configProperty>     
    </configGroup>
    <configGroup>
      <type>tcp-listeners</type>
    </configGroup>
    <configGroup>
      <type>origin-server-pool</type>
      <configProperty id="origin-server-pool-1">
        <configProperty id="origin-server-1">
          <name>origin-server-1</name>
          <value>abc1234.example.com:7010</value>
          <itemMetadata>
            <dataType>STRING</dataType>
            <scope>READ_WRITE</scope>
          </itemMetadata>
        </configProperty>
        <configProperty id="origin-server-2">
          <name>origin-server-2</name>
          <value>abc1234.example.com:7015</value>
          <itemMetadata>
            <dataType>STRING</dataType>
            <scope>READ_WRITE</scope>
          </itemMetadata>
        </configProperty>
      </configProperty>
    </configGroup>
    <configGroup>
      <type>failover</type>
      <configProperty id="failover-group-1">
        <name>virtual-ip</name>
        <value>10.100.10.1</value>
        <itemMetadata>
          <dataType>STRING</dataType>
          <scope>READ_WRITE</scope>
        </itemMetadata>
      </configProperty>
    </configGroup>
  </moveDescriptor>
</movableComponent>
</movableComponent>