Import

For the import process, CA SDM 14.1 or CA SDM 14.1.01 versions must have similar installation configuration on both the source and target systems.
casm173
For the import process, CA SDM 14.1 or CA SDM 14.1.01 versions must have similar installation configuration on both the source and target systems.
Before you initiate the import process, verify the following:
  • Manually copy the exported package from the source system to the target system and place this package under the
    NX_ROOT/Promotion/Import
    folder
    .
    However, if you have set
    export_import_path
    in the SDMP config properties file
    ,
    create
    the Promotion/Import
    folder under
    export_import_path
    and place the exported package
    .
    Warning!
    Do not rename the exported zip file.
  • Ensure that you have set the timeout value in the SDMP config properties file as per your environment. For more information, see SDMP Config Properties File
  • On a Non-windows system, set PATH and LD_LIBRARAY_PATH environment variables.
    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
  • (Optional) Set the
    export_import_path
    ,
    disk_space
    ,
    timeout
    property values in the SDMP Config properties file. For more information, see SDMP Config Properties File.
  • The user must have access to Web Screen Painter to successfully execute the import process.
How to Execute the Import Process
The CA SDM Environment Promotion performs
pdm_configure
as a part of the import process.
Warning:
Do not initiate multiple import processes to avoid the target system resulting in an inconsistent state.
We recommend that you execute the dryrun process before executing the import process.
Follow these steps:
  1. Execute the dryrun command:
    Windows: sdmp -a dryrun -p <exported package>
    Non-windows: sdmp.sh -a dryrun -p <exported package>
    The dryrun process reports failures, if any.
    For example:
    sdmp -a dryrun -p sdmp_import_151008_122725
    The process generates a dryrun summary report that is located in the <
    export_import_path>/Promotion/Dryrun
    folder. The summary report contains the number of files that needs to be imported, number of records to be loaded, and failure messages related to read and write access and validation failures (Text fixes, CA SDM version, locale, Java version, server type, and database Type.)
    When you encounter a patch level mismatch error, to fix or ignore the error, and proceed with the import.
  2. Create a backup of
    NX_ROOT
    folder before you proceed with the import.
    If the import fails, restore the application files from the location where you saved the backup.
  3. Execute the Import command and follow the on-screen instructions.
    Windows: sdmp -a import -p <exported package>
    Non-windows: sdmp.sh -a import -p <exported package>
    For example:
    sdmp -a import -p sdmp_import_151008_122725.zip
    The import process performs the following tasks on the target system:
    • Validates that the CA SDM version, text fixes, locale, Java version, Tomcat version, server type, and database type of the target and source systems are similar.
    • Generates a summary report, which contains the number of files and records imported, in the
      <export_import_path>/Promotion/Import
      folder.
  4. After completing the import process, verify that the changes are reflected on the target system.
    To verify errors or failures that are encountered during the import process, verify the
    sdmp.log
    file in the
    NX_Root/log
    folder.
  5. If any failures are encountered during import, rerun the import process using the same package.
    The import process restarts from the point of failure.