Move Event and Macro Configuration Between Environments
search cancel

Move Event and Macro Configuration Between Environments

book

Article ID: 430940

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

This article provides instructions for moving CA Service Desk Manager (CA SDM) Event and Macro data between two environments, such as during a system upgrade or when promoting changes from a test environment to production. 

Environment

  • Product: CA Service Desk Manager
  • Releases: 17.x
  • Database: All supported MDB database types

Cause

This is a guidance request for environment migration or system upgrades requiring the manual transfer of configuration data that is not captured by standard Schema Designer changes.

Resolution

The usage of pdm_extract and pdm_load commands is the recommended and supported mechanism to move data between CA SDM environments.

⚠️ IMPORTANT: Always test queries or command updates first in a non-production environment. Take a backup of the target database before implementing changes. This operation cannot be undone—verify every parameter before running.

1. Identify Required MDB Tables

The following tables must be considered when moving Events and Macros:

  • evt (Events)
  • splmac (Spell_Macro)
  • bpwshft (Bop_Workshift)
  • atomic_cond (Atomic_Condition)
  • atyp_asc (Act_Type_Assoc)

2. Extract Data from Source Environment

Run the following commands at an Administrator command prompt on the source server to create data files:

shell
pdm_extract Events > evt.dat
pdm_extract Spell_Macro > splmac.dat
pdm_extract Bop_Workshift > bpwshft.dat
pdm_extract Atomic_Condition > atomic_cond.dat
pdm_extract Act_Type_Assoc > atyp_asc.dat

3. Load Data into Target Environment

Copy the .dat files to the target server and run the following commands:

shell
pdm_load -f evt.dat
pdm_load -f splmac.dat
pdm_load -f bpwshft.dat
pdm_load -f atomic_cond.dat
pdm_load -f atyp_asc.dat

Additional Information

Please perform all necessary backups prior to attempting the above changes in production.  

Data dictionary changes exist between different releases of SDM.  As such, usage of this method to transfer data across versions is not recommended.

Certain fields, such as contact UUIDs and internal ID values are also present across the varied tables.  There is a chance of ID desynchronization, both between tables and with existing table data when moving such table content between environments. 

Additional care should also be taken if there are existing event/macro definitions, including any that were defined directly in the target SDM instance that is receiving the table data, as there is a chance of ID value overlap.

Powered by Wolken Software