Upgrade CA SDM Using the SWING Box Method

 
casm1401
 
The SWING Box method is performed by using a separate server, typically, referred to as a SWING system.
In this method, the following are the main steps:
  • Replicate your current production system on the SWING system.
  • Migrate to CA Service Desk Manager (SDM) 14.1.
  • Move the migrated CA SDM 14.1 data and customizations to a clean (never migrated) server.
  • Install on new hardware.
This method has the following advantages:
  • The current production system retains its integrity even during a DR issue or failed migration.
  • At the end of the process, you install CA SDM 14.1 on a never migrated, system, with an updated version of the operating system and database.
  • If you are using a VMware environment as the SWING system, you can use the snapshot functionality to test the migration process multiple times, gather data on timings and steps, ensure an easy migration.
Ensure that you consider the following prerequisites before performing this method:
  • After initiating migration testing,
    do not
     perform any changes to the form, or schema (tables and columns) customizations on any system. For example,
    do not
    make any modification on 12.7/12.x production or 14.1 development, test, SWING, and so on. If you plan to add or modify additional tables or columns, it should be done either on 12.7/12.x and should put into production before testing migration. You can also modify during another outage that is planned after your production migration is complete and you are running CA SDM 14.1 on the new production system.
  • You have completed the following tasks:
    • A test migration of the replicated production system
    • Customized again the custom forms from 12.7/12.x that are incompatible with CA SDM 14.1.
    • Ensured that the you have the latest customized and complete
      site\mods
      directory from a 14.1 environment where all testing was completed.
  • Replicate the most recent migrated CA SDM 14.1 test environment installation to the latest production hardware, including your customized forms built for CA SDM 14.1.
Follow these steps:
Step 1: Gather Files or Data from Current Production System
Follow these steps:
  1. Create an SQL backup of the MDB as a .bak file (usually a normal SQL backup).
  2. Copy the
    C:\Program Files\CA\Service Desk\site\mods
     directory and create a zip file, if possible.
  3. Copy the
    C:\Program Files\CA\Service Desk\site\attachments
     (or the directory where your repositories are configured to store your attachments in) and create a zip file, if required.
  4. Copy the files in steps 1 - 3 to a stand-by directory on that system. Do not paste them yet on the SWING environment.
Step 2: Prepare the SWING Environment and Replicate Production to SWING
If your SWING environment has both Database and Application running on the same system, then you might start at step 3. In this section, the database server is referred to as SWING-DB and the application server as SWING-APP.
Follow these steps:
  1. On SWING DB (assuming SQL is already installed), run the MDB installer wizard from the CA SDM 12.7/12.x install media.
  2. On SWING-APP, install the SQL client and native client (workstation tools also).
  3. Install CA SDM 12.7/12.x on SWING-APP and run configuration so that you have a vanilla 12.7/12.x Service Desk Manager installation running.
  4. As the database administrator, execute the SQL Restore and restore the MDB from your current production that you backed up, to the SWING-DB server. Set option to
    OVERWRITE entire database
     when restoring.
    For more information, see How to Move the CA MDB Data from the Source to the Target Systems.
  5. Execute the stored procedure in SQL to fix the orphaned users which are created when restoring a database from one SQL instance to another. Example:  sp_change_users_login 'AUTO_FIX','mdbadmin'.
  6. Copy the
    site\mods
    directory that you backed up from current production and put in place on SWING-APP system.
  7. Copy the
    site\attachments
    directory (or whichever attachments directory) you backed up from current production and place it on SWING-APP system.
  8. Execute 
    pdm_configure
    :
    1. Skip selecting 
      TO LOAD DEFAULT DATA
      .
    2. In the configuration wizard, click
      next
       at the database section. A message displays, stating that database was previously configured.
      This message indicates that you restored the MDB from a different environment.
    3. Click
      Yes
      .
  9. After the configuration is complete, perform the following tasks:
    1. Start CA SDM services (if not started).
    2. Test the system functionality to ensure 12.7/12.x is running with your data, and customizations, as a full replica of your production environment.
Step 3: Upgrade and Migrate to CA SDM 14.1 on the SWING System
Test the migration and become familiar with the process and issues you might run into while migrating your production system. If your SWING system is on a VMware environment, then take a snapshot. You can roll back to that snapshot, then take your production system down, do another SQL backup on production, restore it to the SWING environment and then complete the steps mentioned in this section. In case migration fails, you can bring your 12.7/12.x production system back up and start the services. You can then retest migration on the SWING environment again, and schedule it for another time.
Follow these steps:
  1. Mount CA SDM 14.1 install media from a local folder, or run the setup.exe from the local folder where the install media is being stored.
    If you are extracting an ISO of the install media, it should be stored in a path and folder that has no spaces in the name, for example, SD127Setup. Also, run locally from the same drive volume where you plan to install CA SDM 14.1. Do not run the installer from a network drive or mounted share as this has been known to cause install and even post install problems to occur.
  2. Launch the CA Service Management 14.1 installer.
  3. Select a language and click
    Next
    .
    For example, select English and then click
    Next
    .
  4. Select CA Service Management.
  5. Follow the prompts to perform this upgrade.
  6. Copy the CA Service Management 14.1
    site\mods
    folder from previous test or development environment to this SWING system and run a
    pdm_configure
    to ensure that all customizations are properly implemented.
  7. Test the migrated, and customized 14.1 SWING system for integrity and functionality.
    If this is your test run on the SWING environment, the re-build your form customizations using the 14.1 forms that are delivered with the product as your previously customized 12.7/12.x versions are incompatible in 14.1. Once you have completed the rebuilding of your customizations, take a backup of your
    site\mods
    directory on the SWING box and store it somewhere outside of this environment for use later (as described in step 6).
  8. If all tests are successfully completed, you might now start the process of moving your migrated data, and customizations to the new production hardware.
Step 4: Move Migrated SWING Box Install to New Production Hardware
Follow these steps:
  1. Create an SQL backup on the SWING system, and let your database administrator perform an SQL Restore onto the SQL instance that your new production system is using.
    For more information, see Step 2 procedure and execute the steps 4-7.
  2. If you are using the Advance Availability configuration, complete the following steps or skip to step 4:
    1. Ensure that you have installed the following components:
      • (Oracle) client is installed and net service name is configured to connect with the new database server.
      • (MS SQL) MS SQL client is installed.
    2. From the DBCleanupUtility folder of the installer DVD, run the following script:
      • (Windows) ResetSDMuspServers.bat
      • (UNIX) ResetSDMuspServers.sh
    1. Follow the steps that are provided in the script (it might need database credentials).This utility deactivates all the servers present in usp_servers table.
  3. If you are using the conventional configuration, add NX_SWING_BOX_MIGRATE=Yes variable to NX.env file and run pdm_configure:
    1. Skip selecting 
      TO LOAD DEFAULT DATA
      .
    2. In the configuration wizard, click 
      next
       at the database section. A message displays, stating that database was previously configured.
      This message indicates that you restored the MDB from a different environment.
    3. Click 
      Yes
      .
  4. After the configuration is complete, perform the following tasks:
    1. Start CA SDM services (if not started).
    2. Test the system functionality to ensure 12.7/12.x is running with your data, and customizations, as a full replica of your production environment.
Reconfigure CA EEM
If you are using CA EEM for authentication on the source or originating CA SDM environment, and that original CA EEM server is not accessible by the Swing Box environment, perform the following steps to reconfigure CA EEM options as follows: 
1. Edit the 
NX.env
 file and set 
USE_EIAM_FOR_AUTH=No.
2. Recycle CA Service Desk Manager services.
3. Log into CA Service Desk Manager using the admin account .
4. Go to 
Options Manager
, and re-configure all CA EEM options to point to the appropriate CA EEM server, along with proper credentials and configurations for that server.
5. Edit the 
NX.env
 file again to 
USE_EIAM_FOR_AUTH=Yes.
 
6. Recycle CA Service Desk Manager Services again.