Deployment Package Library

The  package library contains a configurable set of installable software packages where you can control which products, versions, and platforms are available for deployment. You can control how these products are installed by creating standard package configurations that define the parameters that are required for an unattended installation of a configured software package.
casa
The 
Server Automation
package library contains a configurable set of installable software packages where you can control which products, versions, and platforms are available for deployment. You can control how these products are installed by creating standard package configurations that define the parameters that are required for an unattended installation of a configured software package.
Each package must have an associated package configuration file. The configuration file provides information describing both the package details and how the package installation can be configured.
See Deployment Package Configuration File for more information.
The package library is located in the following directory:
%AllUsersProfile%\CA\SM\domainserver\Deployment\Packages\SM
The requirements of the IDManager component define the directory tree layout. The package library consists of a top-level packages directory that contains two subdirectories: Public and Private. The Public directory contains all the deployable software packages.
..
└───SM
    ├───CA_LiteAgent
    ├───CA_ProcProbe_Utility
    ├───CA_SystemEDGE_AdvancedEncryption
    ├───CA_SystemEDGE_Core
    │   └───5.8.0
    │       └───ENU
    │           ├───AIX_aix
    │           ├───HPUX_hp
    │           ├───HPUX_ia64
    │           ├───Linux_ia64
    │           ├───Linux_ppc
    │           ├───Linux_x86
    │           ├───Solaris_sparc
    │           ├───Solaris_x86
    │           ├───Windows_ia64
    │           ├───Windows_x64
    │           └───Windows_x86
    ├───CA_SystemEDGE_ESAD
    ├───CA_SystemEDGE_HACMP
    ├───CA_SystemEDGE_SCVMM
    ├───CA_SystemEDGE_LPAR
    ├───CA_SystemEDGE_MSCS
    ├───CA_SystemEDGE_RM
    ├───CA_SystemEDGE_SRM
    ├───CA_SystemEDGE_UCS
    ├───CA_SystemEDGE_VCLOUD
    ├───CA_SystemEDGE_Zone
    └───CA_VMVCAIM
The top-level Public directory has five subdirectories:
  • Component Name
    The IDManager instance name, which for 
    Server Automation
    is
    SM
    .
  • Software Package
    All versions, localizations, and architectures of a single deployable package (for example, CA_SystemEDGE_Core, CA_SystemEDGE_SRM).
  • Version
    The version of the software packages that the directory contains.
  • Language
    The installation package language.
    Example:
    ENU
  • Architecture
    The architecture-specific installation materials (for example, Windows_ia64, Solaris_x86).
    The architecture directory name must be one of the platforms that IDManager supports.
When run on the distribution server, the IDManager component uses directories under the distribution server. The distribution server contains a temporary cache of encrypted packages for internal use. Remove these packages upon job completion.
A different directory contains the private IDPrimer installation materials. By default these materials are stored in the following directory under the installation directory of the IDManager component:
<CA Shared Components>/IDMgrApi/packages/private/idprimer
This directory contains the IDPrimer installation materials for all platforms that the infrastructure deployment component supports.