Skip to content
CA Service Management - 17.1
Documentation powered by DocOps

Post-Installation Tasks for CA Service Management 17.1.0.1

Last update October 1, 2018

After installing CA Service Management 17.1.0.1 successfully, perform the following post-install steps: 

CA Service Desk Manager

Run the PDM_PERL Command Utility

Note: CA Service Management provides an option in the installer to automate the post-install tasks. If you have selected Yes to automate the post-installation steps, complete few of the post-install steps as documented below.

If you have selected No for automating the post-install steps while running the installer wizard, perform manually all of the post-install task in this section as per your deployment requirement.

CA SDM on Solaris:

CA Service Management installer does not provide an option to automate the post-installation tasks for Solaris. Hence, you must manually perform all the below post-install tasks for CA SDM on Solaris.

After installing CA Service Management 17.1.0.1, perform the following steps:

  1. Stop CA SDM services.
  2. Navigate to NX_ROOT\bin and run the below command:
    1. pdm_perl pdm_rm_files.pl T6EE401 (Windows)
    2. pdm_perl pdm_rm_files.pl T6EE412(Linux)
    3. pdm_perl pdm_rm_files.pl T6EE419 (Solaris)
  3. Start CA SDM services (if you have selected Yes in CA Service Management Installer to automate the post-installation tasks). 
  4. If you have selected No to automate the post-install steps while running the CA Service Management Installer, skip Step 3 and perform the following steps:
      1. Navigate to NX_ROOT/site/config.properties file and ensure that the value of resources.created parameter is set to 0. 
      2. Open a command prompt and run the following command:

        pdm_configure

      3. Start the CA SDM Services. 

CA Service Catalog

Execute the MDB Scripts

Perform the following post-install steps to execute the MDB Scripts:

  1. Navigate to %USM_HOME%\R17.1_RU1_Scripts.
    For example: \Program Files\CA\Service Catalog\R17.1_RU1_Scripts
    1.  Microsoft SQL Server: 
      1. Connect to the database using Microsoft SQL Server Management Studio.
      2. Now, copy and execute the contents of the file configureMSSQLMDB-SP2.sql.
    2. Oracle Server:
      1. Connect to the data base using Oracle SQL Developer.
      2. Now, copy and execute the contents of the file configureOracleMDB-SP2.sql.
  2. Restart the CA Service Catalog Services.

Import the Content pack

After successful installation of CA Service Catalog 17.1.0.1, perform the following post-install steps to import content pack. 

Note: This steps are applicable for CA Service Catalog Fixed Issues - DE37935, DE39846.

  1. Login to CA Service Catalog, select the Catalog tab.
  2. Navigate to ConfigurationContent Packs. Click Import, browse to %USM_HOME%\filestore\contentpacks.
  3. Select CA Service Management Content Pack 2.0.zip file
  4. Click start import to import the content pack. 
Was this helpful?

Please log in to post comments.

  1. J.W.
    2018-06-07 09:04

    Please confirm that the first post-installation step for CA Service Desk Manager is no longer to run Configuration (pdm_configure)? Also, completing the installation does not automatically start the services, so this must be done to complete the first PDM_PERL step.

    1. Rajashree Nair
      2018-06-11 08:11

      @J.W. Thanks for posting the query. Harikanth Palika and Ramesh Pasupuleti, please confirm the queries that J.W.is enquiring about. Please reply to this query through commenting option on this page. 

      Regards,

      DocOps Services Team

    1. Rajashree Nair
      2018-10-17 05:21

      Hi J.W.

      Please find the updated steps. Hope this helps. 

  2. Karen Matoke
    2018-09-12 10:05

    To successfully run the commands in the section titled "Run the PDM_PERL Command Utility", the CA Service Desk Manager service needs to be stopped (i.e. the files need to be not-in-use). If the files are being used, the output will include messages like "ERROR: Failed to move file path+filename to path+filename. Move file manually" (and doing so manually without stopping the service will return "The process cannot access the file because it is being used by another process") instead of "INFO: File path+filename removed successfully!"

    1. Raghuveer Agarwal
      2018-09-19 05:19

      Hello Karen Matoke,

      Thank you for your feedback on post installation for CA SDM.


      Regards,
      DocOps Services Team