CA SDM Environment Promotion

CA SDM Environment Promotion works in the following two-phased manner:
casm171
HID_SDM_EnvironmentPromotion
CA Service Desk Manager Environment Promotion lets you promote configuration, customization, and object data changes between the source and target systems with minimal manual intervention. As an administrator, you can promote any configuration, customization, or object data changes between the development, test, pre-production, and production systems. For example, you can promote modified forms, added tables, columns, spel, majic files, object data to the production system. Based on the type of change (Configuration/Customization or Object Data), the environment promotion is initiated either through command-line interface or CA SDM User Interface.
How CA SDM Environment Promotion Works
CA SDM Environment Promotion works in the following two-phased manner:
  1. Promotion of the configuration and customization of files 
    For more information, see CA SDM Configuration and Customization
  2. Promotion of the object data
    For more information, see Object Data Promotion
All modifications made to the files, .htmpl, .mods, .spl, .maj, and so on, are directly stored in the 
NX_ROOT/site/mods
 folder. These files are copied from the 
NX_ROOT/site/mods
 folder and creates an export package. Any modification made to add tables and columns using the Web Screen Painter are stored in the database. These modifications are captured in the form of .dat files as part of the export package.
Prerequisites
Verify the following prerequisites before performing any environment promotion processes:
  • To promote changes from the source to target system, ensure that the source and target system are on the same release version.
  • Close all the SDM-related files.
  • Ensure that the CA SDM services are running before you perform Export or Import.
  • When the environments are tenanted, both source and target systems must have the same tenants. The environment promotion does not create any tenants.
  • To execute the export or import process, the user must have the operating system administrator privileges to create files and folders.
  • The user must have access to Web Screen Painter to successfully execute the import process.
  • The user must have read and write access to the
    $NX_ROOT\site
    folder.
  • Do not change the name of the exported zip file. If the exported zip file name is changed, the import process fails.
  • For configuration and customization, the export or import process must be executed on the same type of servers, database, and operating systems.
    For example:
    • If an export is performed on a primary server, import of the package is allowed only on the primary server.
    • If an export is performed on a background server, import of the package is allowed only on the background server.
    • If an export is performed on a secondary server or application server, the import of the package is allowed only on the secondary server or application server.
      For more information about additional scenarios, see Approaches in Typical Environment Promotion Scenarios
  • Administrators are required to copy the .htmpl files to the secondary servers or application servers manually or modify the version control file to propagate the .htmpl files on the secondary servers or application servers.
  • Ensure that the Apache Tomcat service is running before you perform database export.
  • On Non-windows system, ensure that you enable X-Windows or an equivalent session to launch the browser for Web Screen Painter login.
  • On Non-windows system, set the CA SDM bin path and CA SDM LIB path environment variables before executing the export or import process.
    For example:
    For AIX: export PATH=/opt/CA/ServiceDeskManager/bin:$PATH export LIBPATH=/opt/CA/ServiceDeskManager/lib:$LIBPATH   For Solaris and Linux: export PATH=/opt/CA/ServiceDeskManager/bin:$PATH export LD_LIBRARY_PATH=/opt/CA/ServiceDeskManager/lib:$LD_LIBRARY_PATH
    Performing environment promotion affects the CA SDM application performance and also restarts the services. We recommend that you perform the CA SDM Environment Promotion operations during off peak hours.
Approaches in Typical Environment Promotion Scenarios
Scenario 1: To perform environment promotion when the number of servers vary in the test and production systems.
On the source system, there is one primary server and one secondary server. Whereas, on the target system, there is one primary server and multiple secondary servers.
The environment promotion is successful when the configuration on all the servers is the same.