CA Client Automation - 14.0

PDF
English

How to Configure Network Routes for Transferring Software Package Delivery

The Software Delivery registered packages need to be transferred from one machine to another for distribution, deployment, or staging jobs. Package transfer from one machine to another uses the following technologies:
cla140
The Software Delivery registered packages need to be transferred from one machine to another for distribution, deployment, or staging jobs. Package transfer from one machine to another uses the following technologies:
  1. Data Transport Service (DTS)
  2. File Transfer Pug-in.
When a SD Package is transferred between the following nodes, only DTS technology is used:
  1. Enterprise Manager to Domain Manager
  2. Domain Manager to Enterprise Manager
  3. Domain Manager to Scalability Server
  4. Domain Manager to DTS Agent with DTS as download method
The given DTS transfer combinations are on wide-area network (WAN) and customers may want to define special network routes for package transfer.
CA Client Automation
 earlier used Worldview CCS component like 2D map for achieving the same functionality. From the current release,
CA Client Automation
 will have in-house capability of defining the routes between two machines or set of machines when using DTS technology for transfer along with extended route properties.
Consider a use case when a network administrator wants to distribute a package from Enterprise Manager to the Domain Managers in different geographical locations. The package will generally be transferred from one continent to others. As a network administrator or
CA Client Automation
 administrator, you would like to configure the routing nodes for the packages to be transferred from enterprise manager to each of the domain manager, which will otherwise be a point to point transfer. In addition to the routes, you may also like to configure properties such as best route, alternative routes, protocols, throttle size, maximum parcel size and so on.
For customizing the transfer routes, you must configure them first in
CA Client Automation
. Configure the domain manager or enterprise manager to follow specific routes and properties.
Follow these steps:
Only on Enterprise Manager and Domain Manager:
  1. Navigate to Control Panel, Configuration, and the configuration policy applied on the manager machine.
  2. Navigate to Data Transport Service (DTS), Transfer Object Server and set the parameter “Use CCNF Hop links” to true.
  3. Restart a DTS component to pick up these new settings using the following commands:
    1. Caf stop dtstos
    2. Caf start dtstos
    3. caf stop dtsnos
    4. caf start dtsnos
Define the details of the network paths that
CA Client Automation
 might use in transfer of the packages. DTS Manager uses this information for the network routes and properties.
Setting-up Links in
CA Client Automation
You can configure the network paths by setting up the links using DSM Explorer.
Follow these steps:
  1. Navigate to Control Panel, Configuration, and Configuration Views.
  2. Select the DTS Hop Node configuration node and then the policy which is applied on the manager machine. Unseal the policy if required.
    The following tabs appear:
    • Hop Node links
      Defines the link between the machines or a group of machines defined in the container tab. Combination of the links makes a route from a source machine to destination machine. The Administrator has the provision of defining the machine label defined in
      CA Client Automation
       or choosing the container defined in the container tab. Each entry in this tab also provides the link properties.
      The Administrator can create the following links/routes:
      • Machine to Machine
      • Machine to Container
      • Container to Machine
      • Container to Container
    • Containers
      Defines a logical grouping of the machines by aliasing the computer groups defined in
      CA Client Automation
       along with the network properties associated with the group. These properties are common to all the machines defined in the group and will be considered, only if the link-level properties are not defined.
      Henceforth “Group Of Machines” will be referred to as Container or DT Containers in this document.
  3. In the Hop node links sections, create a link between two machines or container and set the following parameters:
    • Source
      Specifies the source machine/container of the link in question. For a single machine, machine label name is the only allowed value. Label name is a property of every computer or target in the
      CA Client Automation
      .
      For a set of machines, configure the DT Container under the container tab, that will be populated in the drop-down list for the user selection.
    • Destination
      Specifies the destination machine/container of the link in question. For a single machine, only label names are allowed as the values. Label name is a property of every computer or target in the
      CA Client Automation
      .
      For a set of machines, configure the DT Container which is auto populated in the drop-down list.
    • Link Metric
      Defines the priority of this link. Lesser the value, more is the priority. The addition of the link metric values for a particular route defines the best route, second best route and so on. For setting up the alternative routes, refer to Data Transfers, Alternative Routing section in DTS Administration Guide.
      If multiple links are defined from same source to destination, then the first link will be considered, irrespective of the link Metric value.
    • Link Throttle
      Defines the delay between the parcels sent out. For an increment by 1, the delay of 50 milli-seconds is added. If set to zero, there is no delay between each parcel transfer.
    • Maximum Parcel Size
      Specifies the maximum parcel size in bytes for this link.
    • Point-to-Point Protocol and Properties
      Specifies the protocol that is used in point-to-point transfer. Only TCP is supported in this case. User can pass additional protocol specific parameters for the point-to-point transfer.
      DTS manager decides which protocol to use based on the details of the transfer. For more details, refer to Optimized Data Transfer, Phase 4: Transfer Mechanism Selection section in DTS Administration guide.
    • Fan-out Protocol and Properties
      Specifies the protocol that is used in Fan-out transfer. Only TCP is supported in this case. User can set additional protocol specific properties in the adjacent field.
    • Point-to-Many Protocol, Address, and Properties
      Specifies the protocol used in case of point-to-many protocols. Currently, multi-cast and broadcast are supported.
    • Calendar
      Defines the calendar name that is associated with this link. CCS Calendars and the new DSM Calendars of
      CA Client Automation
       are supported. The new DTS implementation always searches for the calendars in the local host calendar server.
  4. Repeat the steps in point 3 for configuring all the links in your network.
  5. When all the links are configured, DTS automatically picks up the best route and transfers the package accordingly. It can also try the alternative routes depending on the configuration policy defined at Configuration Policy, DSM, Software Delivery, File Transfer, DTS: Alternative routes.
You can use the computer groups to define the links using DSM Explorer:
  1. CA Client Auto computer groups can be associated with the source and destination for a link.
  2. To add a particular computer group as part of the hop links, create the data transport container (DT Container) of the same.
Follow these steps:
  1. Navigate to Control Panel, Configuration, and Configuration Views.
  2. Select the DTS Hop Node configuration node and then the policy which is applied on the manager machine. Unseal the policy, if required.
  3. Go to the Container tab and set the following properties of the computer group:
    • Container Name
      Specifies the user-defined unique container name of the data transport container.
    • Computer Group Name
      Specifies the field associated with the computer group name defined in
      CA Client Automation
      . The name of the group should be same as it appears in GUI.
      If you change the name of the group, change this parameter accordingly.
    • Link Throttle
      Defines the delay between the parcels sent out. For an increment by 1, the delay of 50 milli-second is added. If set to zero, there is no delay between each parcel transfer.
    • Maximum Parcel Size
      Specifies the maximum parcel size in bytes for this Container.
    • Point-to-Point Protocol and Properties
      Specifies the protocol that is used in point-to-point transfer. Only TCP is supported in this case. User can pass additional protocol specific parameters for the point-to-point transfer.
      DTS manager decides which protocol to use based on the details of the transfer. For more details, refer to Optimized Data Transfer, Phase 4: Transfer Mechanism Selection section in DTS Administration guide.
    • Fan-out Protocol and properties
      Specifies the protocol that is used in Fan-out transfer. Only TCP is supported in this case. You can set additional properties in the adjacent field.
    • Point-to-Many Protocol, Address, and Properties
      Specifies the protocol used in case of point-to-many protocols. Currently, multi-cast and broadcast are supported.
    • Calendar
      Defines the calendar name that is associated with this link. CCS Calendars and the new DSM Calendars are supported. The new DTS implementation always searches for the calendars in the localhost calendar server.
The properties defined at container level are considered only if the link level properties are missing.
Configure Alternative Routes
If you want to use the alternative routes, then configure them in the configuration policy of the manager.
Follow these steps:
  1. Navigate to Control Panel, Configuration, and configuration policy which is applied on manager machine.
  2. Navigate to Software Delivery, file transfer and change the parameter “DTS: Alternative routes”. By default, this is set to zero. Zero means only the best route will be tried. If set to 1, first alternative route after the best route will be tried, if the best route is down. If set to 2, then up to two alternative routes based on the order of the priority will be considered after the best route is tried.
Facts and Limitations
If the computer groups mentioned in the Container is a dynamic query-based group, it will not be evaluated automatically before transfer. User must associate engine tasks for running the queries periodically.
Container names/ Computer groups are not supported for intermediate or hop nodes. If set, they are ignored.
Link-level properties have higher precedence over the container level properties.
Restart TOS when the “Use CCNF Hop links” parameter changes. The behavior is undefined or Software Delivery jobs may fail.
If two hop links are defined between same source and destinations, then the first link is considered even if it has higher link metric value.
2D-Map fails to connect to DTS repository when the “Use CCNF Hop links” is set to true. It gives the below error when we try to open the DTS details of an object.
Failed to retrieve properties from Common Object R.
If the Computer label name is duplicated in
CA Client Automation
 “All Computers” list and the same label is used as a hop node under the Hop link tab, then DTS Manager can pick any of the matching entry for hopping.