Post Installation Steps for CA SDM Conventional Configuration

Complete the following post installation steps for CA SDM Conventional Configuration:
casm1401
Complete the following post installation steps for CA SDM Conventional Configuration:
Install CA Service Management 14.1.02 on CA SDM 14.1
Follow these steps:
  1. To reconfigure CA SDM on primary server, run the following command:
    pdm_configure
    Do not select Load Default Data.
  2. Navigate to
    NX_ROOT\data
    folder.
  3. To load data, run the following commands:
    pdm_load -f santafe_insert.dat
    pdm_load -f santafe_update.dat
    pdm_load -f tucson_insert.dat
    pdm_load -r -f tucson_delete.dat
  4. Alert users to clear browser cache. Run the following command:
    pdm_webcache -H
    pdm_webcache -b
  5. Repeat
    Step 1
    and
    Step 4
    on the secondary server.
Mandatory Steps
Perform the following steps: 
  1. Create a backup of 
    web.xml
     from 
    NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\CAisd\WEB-INF
     in your local directory to perform a backout, if required.
  2. Open the 
    web.xml
     file from 
    NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\CAisd\WEB-INF.
  3. Search for the following statement:
    <!-- Add filter here -->
  4. Copy and paste the following configuration under the 
    <!-- Add filter here -->
     statement:
    <!-- Cross-origin support for Attachments Servlet -->
    <filter>
    <filter-name>CORS</filter-name>
    <filter-class>com.thetransactioncompany.cors.CORSFilter</filter-class>
    <init-param>
    <param-name>cors.supportedMethods</param-name>
    <param-value>POST, GET, OPTIONS</param-value>
    </init-param>
    <init-param>
    <param-name>cors.allowOrigin</param-name>
    <param-value>*</param-value>
    </init-param>
    </filter>
  5. Search for the following statement:
    <!-- Add filter-mapping here -->
  6. Copy and paste the following configuration under the 
    <!-- Add filter-mapping here -->
     statement:
    <!-- Cross-origin support for Attachments Servlet -->
    <filter-mapping>
    <filter-name>CORS</filter-name>
    <servlet-name>UploadServlet</servlet-name>
    </filter-mapping>
  7.  Verify that the configurations under the filter and filter-mapping statements are as shown in the following sample:
    <!-- Add filter here -->
    <!-- Cross-origin support for Attachments Servlet -->
    <filter>
    <filter-name>CORS</filter-name>
    <filter-class>com.thetransactioncompany.cors.CORSFilter</filter-class>
    <init-param>
    <param-name>cors.supportedMethods</param-name>
    <param-value>POST, GET, OPTIONS</param-value>
    </init-param>
    <init-param>
    <param-name>cors.allowOrigin</param-name>
    <param-value>*</param-value>
    </init-param>
    </filter>
    <!-- Add filter-mapping here -->
    <!-- Cross-origin support for Attachments Servlet -->
    <filter-mapping>
    <filter-name>CORS</filter-name>
    <servlet-name>UploadServlet</servlet-name>
    </filter-mapping>
  8. Save and close the 
    web.xml
     file.
  9. For CORS setting preservation in a primary and secondary environment, the secondary server must also have the CORS entries in the following file:
    <NX_ROOT>\bopcfg\www\CATALINA_BASE\webapps\CAisd\WEB-INF\web.xml.last
  10. Repeat the 
    Steps
     
    1-8
     to update 
    web.xml.tpl
     file in the 
    NX_ROOT\samples\pdmconf\web.xml.tpl
     folder to avoid losing these changes when pdm_configure is run.
  11. Run the 
    pdm_configure
     command.
  12. Start CA SDM services.
Mandatory Steps for CA Business Intelligence
Complete the following steps if you have installed CA Business Intelligence:
Import Service Desk BIARs
Follow these steps:
  • Download the required patch from CA Support and follow the instructions provided in the Test Fix.
    • Windows: RO79125
    • Linux: RO79126
    • Solaris: RO79127
    • AIX: RO79128
      For example, download the Windows patch readme RO79125 and follow the instructions mentioned in the section 
      Procedure to create a backup .biar file
      .
Use Dashboard Reports
Before you use dashboard reports, ensure that both CA SDM and CA Service Catalog use the same CA Business Intelligence server. 
  • Run the following queries if you have configured MDB with Oracle database:
    create or replace function MDBADMIN.left(str1 varchar2 :=NULL,num1 NUMBER)
    RETURN VARCHAR2
    as
    ascii_chr varchar2(32767);
    begin
    ascii_chr:= substr(str1,1, num1);
    return ascii_chr;
    end;
    Update report_labels set language_code ='en' where language_code='en ';
    Update report_labels set language_code ='De' where language_code='De ';
Mandatory Steps for CA SDM Mobility
Perform the following steps:
  1. Navigate to
    NX_ROOT\bopcfg\www\CATALINA_BASE_REST\webapps
    .
  2. Create a backup and delete the workflow folder.
  3. Verify that the workflow folder is created after the CA SDM server services are recycled.
 
To resolve specific issues when installing CA SDM 14.1.02, see Optional Steps for Specific Issues when Installing CA Service Desk Manager 14.1.02.
Install CA Service Management 14.1.02 on CA SDM 14.1.01
If you are installing CA SDM 14.1.02 on CA SDM 14.1.01 installation, perform the following steps:
Before you proceed, ensure that you have performed the post-installation steps mentioned in the CA SDM 14.1.01 readme.
Follow these steps:
  1. To reconfigure CA SDM on primary server, run the following command:
    pdm_configure
    Do not select
    Load Default Data
    .
  2. Navigate to the
    NX_ROOT
    \data folder.
  3. To load data, run the following commands:
    pdm_load -f tucson_insert.dat
    pdm_load -r -f tucson_delete.dat
  4. To alert users to clear browser cache, run the following commands:
    pdm_webcache -H
    pdm_webcache -b
  5. Repeat
    Step 1
    and
    Step 4
     on the secondary server.
    To resolve specific issues when installing CA SDM 14.1.02, see Optional Steps for Specific Issues when Installing CA Service Desk Manager 14.1.02.