You must define a data destination for every system to specify which technique to use to transport the deployment data to the remote system. The two choices are FTP and Shared DASD.
When FTP transport is specified as the transport mechanism, the deployment data is shipped to the target system through FTP. It is temporarily placed on the target system at the landing directory specified in the FTP Location information section of the System Registry.
When shared DASD is specified, CA CSM uses a virtual transport technique. That is, it does not actually copy the data from one system to the other. Because the two systems share DASD, there is no need to do this. All of the deployment data is kept in USS file systems managed by CA CSM.
The remote system, even though the DASD is shared, may not be able to find the deployment data in the USS file system. During the Deploy Product step, CA CSM temporarily unmounts the file system from the CA CSM driving system and mounts it in read-only mode on the remote system. For CA CSM to determine where to mount the file system on the remote system, you must specify a mount point location in the data destination. In addition, you can provide allocation information for the creation of the deployment file system, so that when the file system is created on the CA CSM driving system, it will be on the DASD that is shared.
If you have defined in the data destination that the transport is Shared DASD, the mount point that is defined in the data destination must exist on the contact system.
Example:
SYSA uri: usilsysa
SYSB uri: usilsysb
URI should be set to SYSA – usilsysa
Path should be set to a directory located on SYSA
Business Value:
CA CSM lets you use data destinations to specify how to transport the deployment and, if you choose, to specify the locations of the target libraries. Data destinations are done at the system level, allowing deployments to a given system to be performed in a consistent manner. This additional flexibility enables you to implement an automated, standardized, and less error-prone deployment process.
More Information:
For more information, see the online help.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|