Post-Install Tasks for CA SDM Advanced Availability Configuration

This article describes the following post-installation tasks for CA SDM Advanced Availability Configuration:
casm1401
Perform manually the post-install tasks described in this article as per your environment requirement. The CA Service Management 14.1.03 installer currently does not provide an option to automate the post-install tasks for Advanced Availability.
This article describes the following post-installation tasks for CA SDM Advanced Availability Configuration:
If http://hostname:port/initialContext URL gives 500 as response code when xFlow Analyst Interface is configured with a load balancer, do not route users to the xFlow Analyst Interface server. 
Post-Install Steps after Installing CA Service Management 14.1.03 on CA SDM 14.1
For this procedure, the following host names are considered as examples:
  • Background server host name is
    sdmcahost1
  • Standby server host name is 
    sdmcahost2
  • Application server host name is 
    sdmcahost3
Perform the following steps if you have installed CA SDM 14.1.03 on CA SDM 14.1:
  1. Ensure that you have installed CA Service Management 14.1.03 on all servers in your environment.
  2. Ensure that the CA SDM services are in a stopped state on all servers.
  3. Log in to the standby server.
    Example, 
    sdmcahost2
  4. Open a Command Prompt window. Run the following command (as an administrator) on the standby server to start the CA SDM configuration wizard:
    pdm_configure
    On the last configuration screen, before clicking
    Finish
    ,
    uncheck
    the
    Start service when completed
    checkbox. Failure to uncheck the box may result in the loss of custom schema changes and configurations that were changed on the server.
  5. Promote the standby server as the new background server by performing the following steps:
    1. To suppress version control on the standby server (
      sdmcahost2)
      and later on the background (
      sdmcahost1) 
      server in step 6, run the following command on each server:
      pdm_server_control -v
    2. To start the services on the standby server, run the following command:
      pdm_server_control -b
    3. Run the
       
      pdm_server_control_b
       command again to promote the server as the background server. 
  6. On the original background server (
    sdmcahost1)
    , complete steps 4-5 to perform pdm_configure and promote the server.
  7. Start services on the standby server (sdmcahost2).
  8. On the background server (sdmcahost1), perform the following steps:
    1. Open the Command Prompt window and navigate to
      NX_ROOT\data.
    2. To load the updated data, run the following commands as an administrator:
      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
      pdm_load -f hampi_insert.dat
    3. To alert users to clear the browser cache, run the following command on both the background and standby servers (sdmcahost1 and sdmcahost2):
      pdm_webcache -H
      pdm_webcache -b
  9. Log in to the application server(s) (sdmcahost3).
  10. Run the following command on the application server (
    sdmcahost3)
    to start the CA SDM configuration wizard:
    pdm_configure
  11. To alert users to clear the browser cache, run the following command:
    pdm_webcache -H
    pdm_webcache -b
  12. Complete the Mandatory Steps on all servers in your environment.
  13. Now, enable the Heat Weather daemons. For more information, see Post-Install Steps for Enabling the Heat Weather Daemons.
Mandatory Steps
These mandatory steps are required if you are installing CA Service Management 14.1.03 on 14.1. Perform the mandatory steps on all servers in your CA SDM environment:
Open 
web.xml
 from 
NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\CAisd\WEB-INF.
  1. Search for the following statement:
    <!-- Add filter here -->
  2. 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>
  3. Search for the following statement:
    <!-- Add filter-mapping here -->
  4. 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>
  5.  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>
  6. Save the 
    web.xml
     file. 
  7. Restart tomcat.
  8. Repeat 
    Steps 1-7
     to update the 
    web.xml.tpl
     file in the 
    NX_ROOT\samples\pdmconf\web.xml.tpl folder.
  9. Run the 
    pdm_configure
     command.
  10. Start CA SDM services.
Post-Install Steps after Installing CA Service Management 14.1.03 on CA SDM 14.1.01
Perform the following post-installation steps if you have installed CA SDM 14.1.03 on CA SDM 14.1.01:
  1. Ensure that you run the CA Service Management 14.1.03 installer wizard on all servers in your environment. 
  2. Ensure that the CA SDM services are in a stopped state on all servers in the environment. 
  3. Log in to the standby server.
    For example,
    sdmcahost2
    server.
  4. Open a Command Prompt window. Run the following command as an administrator on the standby server (
    sdmcahost2)
     to start the CA SDM configuration wizard:
    pdm_configure
    On the last configuration screen, before clicking
    Finish
    ,
    uncheck
    the
    Start service when completed
    checkbox. Failure to uncheck the box may result in the loss of custom schema changes and configurations that were changed on the server.
  5. Promote the standby server (
    sdmcahost2)
    as the new background server by performing the following steps:
    1. To suppress version control on the standby (
      sdmcahost2)
      and later on the background server (
      sdmcahost1) in step 6
      , run the following command on each server:
      pdm_server_control -v
    2. Run the following command to start services on the standby server:
      pdm_server_control -b
    3. Run the
       
      pdm_server_control -b
      command
       
      again to promote the standby server (sdmcahost2) as the background server. 
  6. On the original background server (
    sdmcahost1)
    , complete step 4-5 to perform pdm_configure and promote the server. 
  7. Start services on the standby server (sdmcahost2).
  8. On the background server (sdmcahost1), perform the following steps:
    1. Open the Command Prompt Window and navigate to the 
      NX_ROOT\data
       folder.
    2. To load the updated data, run the following commands as an administrator:
      pdm_load -f tucson_insert.dat
      pdm_load -r -f tucson_delete.dat
      pdm_load -f hampi_insert.dat
    3. To alert users to clear the browser cache, run the following command on both the background and standby servers (sdmcahost1 and sdmcahost2):
      pdm_webcache -H
      pdm_webcache -b
  9. Log in to the application server(s) (sdmcahost3) and run the following command to start the CA SDM configuration wizard:
    pdm_configure
  10. To alert users to clear the browser cache, run the following command:
    pdm_webcache -H
    pdm_webcache -b
  11. Now, enable the Heat Weather daemons. For more information, see Post-Install Steps for Enabling the Heat Weather Daemons
Post-Install Steps after Installing CA Service Management 14.1.03 on CA SDM 14.1.02
Perform the following post-installation steps if you have installed CA SDM 14.1.03 on CA SDM 14.1.02:
  1. Ensure that you run the CA Service Management 14.1.03 installer wizard on all servers in the environment.
  2. Ensure that CA SDM services are in a stopped state on all servers in your environment. 
  3. Log in to the standby server.
    For example,
    sdmcahost2
  4. Open a Command Prompt window. Run the following command as an administrator on the standby server (
    sdmcahost2)
     to start the CA SDM configuration wizard:
    pdm_configure
    On the last configuration screen, before clicking
    Finish
    ,
    uncheck
    the
    Start service when completed
    checkbox. Failure to uncheck the box may result in the loss of custom schema changes and configurations that were changed on the server.
  5. Promote the standby server (
    sdmcahost2)
    as the new background server by performing the following steps:
    1. To suppress version control on the standby (
      sdmcahost2)
      and later on the background server (
      sdmcahost1)
      in step 6, run the following command on each server:
      pdm_server_control -v
    2. To start the services on standby server (
      sdmcahost2), run the following command:
      pdm_server_control -b
    3. Run the
      pdm_server_control -b
      command again to promote the standby server (
      sdmcahost2)
      as the new background server.
  6. On the original background server (
    sdmcahost1)
    , complete step 4-5 to perform pdm_configure and promote the server.
  7. Start the services on the standby server (sdmcahost2).
  8. On the background server, perform the following steps:
    1. Open the Command Prompt Window and navigate to the 
      NX_ROOT\data 
      folder.
    2. To load updated data, run the following command as an administrator:
      pdm_load -f hampi_insert.dat
    3. To alert users to clear the browser cache, run the following command on both the background and standby servers (sdmcahost1 and sdmcahost2):
      pdm_webcache -H
      pdm_webcache -b
  9. Log in to the application server(s) (
    sdmcahost3).
    Open a Command Prompt window and run the following command on the application servers (
    sdmcahost3) 
    to start the CA SDM configuration wizard:
    pdm_configure
  10. To alert users to clear the browser cache, run the following command:
    pdm_webcache -H
    pdm_webcache -b
  11. Now, enable the Heat Weather daemons. For more information, see Post-Install Steps for Enabling the Heat Weather Daemons
Enable the Heat Weather Daemons
After completing the appropriate post-installation task for your environment, ensure that you enable the heat weather daemons in your implementation. Perform the following steps:
  1. Execute the
    pdm_options_mgr
    command on the background server and then, the standby server.
    The
    pdm_options_mgr
    command updates the NX.env file with the newly installed options for heat and weather.
  2. On the background and standby server, open the
    NX.env
    file from the 
    $NX_ROOT
    directory and validate that the heat-related value is present:
    @NX_HEAT_WEATHER=HeatWeather
  3. Restart the CA SDM Service on the background server and then, the standby server.
  4. Restart the xFlow Analyst Service on all application servers.