Post-Installation Tasks for CA Service Management 17.2.0.8

casm172
If any SSL certificate(s) chain was imported to the Oracle Java's JAVA_HOME\lib\security\cacerts Keystore, those certificate(s) chain again need to be exported explicitly and imported properly into the new AdoptOpenJDK's JAVA_HOME\lib\security\cacerts Keystore.
After successful installation of
CA Service Management
17.2.0.8, perform the following post-install steps: 
2
CA Service Desk Manager
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 while running the CA Service Management Installer Wizard, you are not required to perform any manual post-install steps.
If you have selected
No
for automating the post-install steps while running the CA Service Management Installer wizard, perform the below manual post-install tasks as per your deployment requirements:
Manual Post-Install Tasks After Installing CA Service Desk Manager (SDM) 17.2.0.8 on CA SDM 17.2.0.7
Perform the following steps:
  1. Stop CA SDM services.
  2. Navigate to
    NX_ROOT/site/config.properties
    file and ensure that the value of
    resources.created parameter
    is set to 0.
  3. Open a command prompt and run the following command:
    pdm_configure
  4. Change the directory to
    NX_ROOT/data
    , and execute the following command:
    pdm_load -f 17_2_08_insert.dat
  5. Clear the browser cache by running the following command:
    pdm_webcache -H
Manual Post-Install Tasks After Installing CA SDM 17.2.0.8 on CA SDM 17.2.0.4 or CA SDM 17.2.0.3
Perform the follwing steps
:
  1. Stop CA SDM services.
  2. Navigate to
    NX_ROOT/site/config.properties
    file and ensure that the value of
    resources.created parameter
    is set to 0.
  3. Open a command prompt and run the following command:
    pdm_configure
  4. Change the directory to
    NX_ROOT/data
    , and execute the following command:
    pdm_load -f 17_2_05_insert.dat pdm_load -u -f 17_2_05_update.dat pdm_load -f 17_2_07_insert.dat pdm_load -f 17_2_08_insert.dat
  5. Clear the browser cache by running the following command:
    pdm_webcache -H
Manual Post-Install Tasks After Installing CA SDM 17.2.0.8 on CA SDM 17.2.0.2 or CA SDM 17.2.0.1 or CA SDM 17.2
Follow these steps
:
  1. Stop CA SDM services.
  2. Navigate to
    NX_ROOT/site/config.properties
    file and ensure that the value of
    resources.created parameter
    is set to 0.
  3. Open a command prompt and run the following command:
    pdm_options_mgr -c -s attach_force_save_dialog -v 1 -a pdm_option.inst -t
  4. Open a command prompt and run the following command:
    pdm_configure
  5. Change the directory to
    NX_ROOT/data
    , and execute the following command:
    pdm_load -f 17_2_03_insert.dat pdm_load -u -f 17_2_03_update.dat pdm_load -f 17_2_05_insert.dat pdm_load -u -f 17_2_05_update.dat pdm_load -f 17_2_07_insert.dat pdm_load -f 17_2_08_insert.dat
  6. Clear the browser cache by running the following command:
    pdm_webcache -H
AdoptOpenJDK (Mandatory)
CA SDM 17.2.0.7 is packaged with AdoptOpenJDK 11.0.3 and the older version JRE 11 is no more supported. You may manually remove the JRE 11 folder if it is not associated with any product other than CA Service Management in the following location:
C:\Program Files (x86)\CA\SC\JRE
.
Service Point
After successful installation of Service Point, refresh index and data on the Search Server. For more information, see Perform Initial Load and Refresh Index and Data on the Search Server.
CA Service Catalog
If any SSL certificate(s) chain was imported to the Oracle Java's JAVA_HOME\lib\security\cacerts Keystore, those certificate(s) chain again need to be exported explicitly and imported properly into the new AdoptOpenJDK's %USM_HOME%\embedded\jdk\lib\security\cacerts Keystore.
After upgrading to CA Service Catalog 17.2.0.8, perform the following post-install steps as per your deployment requirement.
Post-Install Tasks After Installing CA Service Catalog 17.2.0.8 on CA Service Catalog 17.2.0.4 .
Follow these steps
:
  • (Optional) If Service Catalog is accessed from applications like USS, ServicePoint, SharePoint and so on, then you must perform this step. Open the "
    web.xml
    " file located at
    USM_HOME%\view\webapps\usm\WEB-INF
    and update the respective parameter values for the parameter name "cors.allowed.origins" and "cors.support.credentials".
    For example, if you are using Catalog Widgets in Unified Self Service and ServicePoint
Post-Install Tasks After Installing CA Service Catalog 17.2.0.8 on CA Service Catalog 17.2.0.3
Follow these steps
:
  1. Update the
    viewService.conf
    file.
    1. Open USM_HOME\view\conf\viewService.conf file in the Administrator edit mode.
    2. Search for "
      wrapper.java.additional.xx=-Xverify:none
      " and add the following entries after it.
      The
      xx
      is a sequence value in viewService.config file and varies as per your environment.
      #trust these packages for serialize for upgraded activemq wrapper.java.additional.xx=-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.ca,com.ca.usm.billing.ServiceManager,wv,sun
      For example, if the search string contains 23 i.e "
      wrapper.java.additional.23=-Xverify:none
      ", add the following entry after it.
      #trust these packages for serialize for upgraded activemq wrapper.java.additional.24=-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.ca,com.ca.usm.billing.ServiceManager,wv,sun
    3. Save the file.
  2. (Optional) If Service Catalog is accessed from applications like USS, ServicePoint, SharePoint and so on, then you must perform this step. Open the "
    web.xml
    " file located at
    USM_HOME%\view\webapps\usm\WEB-INF
    and update the respective parameter values for the parameter name "cors.allowed.origins" and "cors.support.credentials".
    For example, if you are using Catalog Widgets in Unified Self Service and ServicePoint:
    • Search the parameter name "
      cors.allowed.origins
      " and update the respective parameter value as shown here.
      <param-name>cors.allowed.origins</param-name> <param-value>http://usshostname:ussport,http://servicepointhostname:servicepointport</param-value>
    • Search the parameter name "
      cors.support.credentials
      " and update the respective parameter value to true as shown here.
      <param-name>cors.support.credentials</param-name> <param-value>true</param-value>
      Retain the
      default configuration in web XML, if no other application is accessing catalog:
      <param-name>cors.allowed.origins</param-name> <param-value>*</param-value>
      <param-name>cors.support.credentials</param-name> <param-value>false</param-value>
  3. Restart the CA Service Catalog services.
Post-Install Tasks After Installing CA Service Catalog 17.2.0.8 on CA Service Catalog 17.2.0.2 or CA Service Catalog 17.2.0.1 or  CA Service Catalog 17.2.
Follow these steps
:
  1. Update
    server.xml
    file located at
    USM_HOME\view\conf.
    Add the below attributes to HTTP and HTTPS connector tags to allow below characters which are mandatory for the application to work.
    relaxedPathChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
    For example:
    <!-- Define a HTTP/1.1 Connector on port XXXX --> <Connector port="XXXX" disableUploadTimeout="true" URIEncoding="UTF-8" .. .. relaxedPathChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" /> <!-- Define a SSL HTTP/1.1 Connector on port XXXX --> <Connector port="XXXX" disableUploadTimeout="true" URIEncoding="UTF-8" .. .. relaxedPathChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" />
    Tomcat server.xml allows special characters in Hex code format in
    relaxedPathChars
    and 
    relaxedQueryChars
    . For more information, see the following special characters and their respective Hex codes:
    Special Character Name
    Special Character
    Hex Code
    Backslash
    \
    &#x5c;
    Grave accent
    `
    &#x60;
    Double quotes
    "
    &quot;
    Less than
    <
    &lt;
    Greater than
    >
    &gt;
  2. Update the
    viewService.conf
    file.
    1. Open USM_HOME\view\conf\viewService.conf file in the Administrator edit mode.
    2. Search for "
      wrapper.java.additional.xx=-Xverify:none
      " and add the following entries after it.
      The
      xx
      is a sequence value in viewService.config file and varies as per your environment.
      #trust these packages for serialize for upgraded activemq wrapper.java.additional.xx=-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.ca,com.ca.usm.billing.ServiceManager,wv,sun
      For example, if the search string contains 23 i.e "
      wrapper.java.additional.23=-Xverify:none
      ", add the following entry after it.
      #trust these packages for serialize for upgraded activemq wrapper.java.additional.24=-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.ca,com.ca.usm.billing.ServiceManager,wv,sun
    3. Save the file.
  3. (Optional) If Service Catalog is accessed from applications like USS, ServicePoint, SharePoint and so on, then you must perform this step. Open the "
    web.xml
    " file located at
    USM_HOME%\view\webapps\usm\WEB-INF
    and update the respective parameter values for the parameter name "cors.allowed.origins" and "cors.support.credentials".
    For example, if you are using Catalog Widgets in Unified Self Service and ServicePoint:
    • Search the parameter name "
      cors.allowed.origins
      " and update the respective parameter value as shown here.
      <param-name>cors.allowed.origins</param-name> <param-value>http://usshostname:ussport,http://servicepointhostname:servicepointport</param-value>
    • Search the parameter name "
      cors.support.credentials
      " and update the respective parameter value to true as shown here.
      <param-name>cors.support.credentials</param-name> <param-value>true</param-value>
      Retain the
      default configuration in web XML, if no other application is accessing catalog:
      <param-name>cors.allowed.origins</param-name> <param-value>*</param-value>
      <param-name>cors.support.credentials</param-name> <param-value>false</param-value>
  4. Restart the CA Service Catalog services.
AdoptOpenJDK (Mandatory)
CA Service Catalog 17.2.0.8 is packaged with AdoptOpenJDK 11.0.3 and the older version JRE 11 is no more supported. You may manually remove the JRE 11 folder if it is not associated with any product other than CA Service Management in the following location:
C:\Program Files\CA\Service Catalog\Embedded\JRE
.
CA Asset Portfolio Manager
AdoptOpenJDK (Mandatory)
CA ITAM 17.2.0.4  is packaged with AdoptOpenJDK 11.0.3 and the older version JRE 11 is no more supported. You may manually remove the JRE 11 folder if it is not associated with any product other than CA Service Management in the following location:
C:\Program Files (x86)\CA\ITAM
.