Post Install Steps for CA Service Catalog

After installing CA Service Catalog 14.1.04, perform the following post-installation steps: 
casm1401
After installing CA Service Catalog 14.1.04, perform the following post-installation steps:
 
Post-Install Steps to Increase the Number of Active Database Connections (Mandatory)
To increase the number of active database connections, perform the following steps:
  1. Open the
    Applicationcontext.xml
    file from
    %USM_HOME%\view\webapps\usm\WEB-INF\
    bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
    <property name="driverClassName" value="${DBSource.driver}" />
    <property name="url" value="${DBSource.url}" />
    <property name="username" value="${DBSource.username}" />
    <property name="password" value="${DBSource.password}" />
    <property name="logAbandoned" value="true" />
    <property name="removeAbandoned" value="true" />
    <property name="maxWait" value="1800000" />
  2. Change the value of <property name="logAbandoned" value=
    "true"
    /> to "
    false
    "
    :
    <property name="logAbandoned" value="
    false
    " />
  3. Add the following line towards the end of
    Applicationcontext.xml
    file:
    <property name ="maxActive" value ="100" />
  4. After making the changes as shown in Step
    #2
    and step
    #3
    , the
    Applicationcontext.xml
    file will look like the following:
    bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
    <property name="driverClassName" value="${DBSource.driver}" />
    <property name="url" value="${DBSource.url}" />
    <property name="username" value="${DBSource.username}" />
    <property name="password" value="${DBSource.password}" />
    <property name="logAbandoned" value="false" />
    <property name="removeAbandoned" value="true" />
    <property name="maxWait" value="1800000" />
    <property name ="maxActive" value ="100" />
Post-Install Steps after Installing
CA Service Management
 14.1.04 on CA SM 14.1 or CA SM 14.1.01 or CA SM 14.1.02 (Mandatory)
Perform the following steps if you have installed CA SM 14.1.04 on CA SM 14.1 or CA SM 14.1.01 or CA SM 14.1.02
:
  1. Navigate to <USM_HOME>\view\scripts\EIAM\Safex and edit the following file: usm_create_additional_application_data.xml
  2. Update all the tags with EIAMAPPNAME in the name with the EEM application name.
    : To identify the EEM application name, open the <USM_HOME>\config.properties file and locate the eiam.application property.
  3. Open the command prompt from <USM_HOME>\usm.cmd and execute the following command:
    bin\safex\safex -h <EEM_HOST> -u EiamAdmin –p <EEM_ADMIN_PASSWORD> -f view\scripts\EIAM\safex \usm_create_additional_application_data.xml
    Replace the EM_HOST and EEM_ADMIN_PASSWORD parameters with the hostname and the administrator password of the EEM server.
  4. Log into EEM and navigate to
    Configure
    ,
    Session
    ,
    Synchronize Cache
    .
  5. Restart the CA Service Catalog services.
  6. Delete the browser cache.
Troubleshoot the SAFEX Command Error
When EEM is installed on a server different than CA Service Catalog, you may encounter errors while executing the SAFEX command. For example, you may encounter the 
ETPKI home is not set
error.
Follow these steps:
  1. Log into EEM and navigate to 
    Configure
    Session
    Synchronize Cache
    .
  2. Navigate to <USM_HOME>\view\scripts\EIAM\Safex\ and copy the usm_create_additional_application_data.xml file to the EEM server.
  3. Open command prompt and navigate to the location where you installed EEM.
    For example: Navigate to C:\Program Files\CA\SC\EmbeddedEntitlementsManager\bin
  4. Execute the following command:
    safex -h <EEM_HOST> -u EiamAdmin –p <EEM_ADMIN_PASSWORD> -f <path>\usm_create_additional_application_data.xml
    Replace the EM_HOST and EEM_ADMIN_PASSWORD parameters with the hostname and the administrator password of the EEM server.
  5. Log into EEM and navigate to 
    Configure
    Session
    Synchronize Cache
    .
  6. Restart the CA Service Catalog services.
  7. Delete the browser cache.
Merge Configuration Changes in the ehcache.xml File
When you install
CA Service Management
 14.1.04, the old
ehcache.xml
file is automatically replaced with the new
ehcache.xml
file in CA Service Catalog 14.1.04:
If you have made changes to an existing
ehcache.xml
file in your environment, ensure to merge your changes with the new
ehcache.xml
file provided with
CA Service Management
14.1.04. You can find the new and old
ehcache.xml
files in the following location.
  • New
    ehcache.xml
    for
    CA Service Management
    14.1.04:
     %USM_HOME%\view\conf
  • Old
    ehcache.xml
    from earlier release versions of
    CA Service Management
    14.1.04:
     %USM_HOME%\REPLACED\CA_SLCM_r14.1.04.OLD\view\conf
Post-Install Steps when Upgrading to Tomcat 7.0.52.x (Mandatory)
After you upgrade to Tomcat 7.0.52.x version, perform the following steps if there are issues with the plugin list. For example, the plugin list result is empty.
  1. Navigate to <USM_HOME>\view\conf folder and edit the server.xml file.
  2. Search for the following tag:
    <Context debug="0" docBase="C:\Program Files\CA\Service Catalog\view\webapps\usm" path="/usm" reloadable="false"/>
  3. Replace the tag with the following code:
    <Context path="/usm" docBase="__USMHOME__\view\webapps\usm" debug="0" reloadable="false"> <Loader delegate="true" /></Context>
  4. Save and close the file.
  5. Restart the CA Service Catalog services.
We do not support the following versions of Tomcat: Tomcat 7.0.73, Tomcat 7.0.74, and Tomcat 7.0.75 as they have known issues. For more information, see Supportability Matrix.
Post-Install Steps when Upgrading to Tomcat 7.0.76.x (Mandatory)
After you upgrade to Tomcat 7.0.76.x version, perform the following steps:
  1. Navigate to the following location: <USM_HOME>\view\conf and edit the viewService.conf file.
  2. In the Java Additional Parameters section, add the following parameters towards the end:
    wrapper.java.additional.xx=-Dtomcat.util.http.parser.HttpParser.requestTargetAllow=|
    Where, xx is the serial number of the list of parameters in the section. For example, wrapper.java.additional.23=-Dtomcat.util.http.parser.HttpParser.requestTargetAllow=|
  3. Save and close the file.
  4. Restart the CA Service Catalog services.
We do not support the Tomcat versions 7.0.73, 7.0.74 and 7.0.75 as they have known issues. For more information, see Supportability Matrix.
Post-Install Steps to Support TLS v1.2
Information:
This section is mandatory only when you want to enable TLS v1.2 support.
When you upgrade from EEM 12.51.0.4 to enable support for TLS v1.2, perform the following steps:
  1. Upgrade to JRE.
    From JRE 1.7.0_95.x to JRE 1.8.0_45 version. For example, to upgrade to JRE 1.8.0_45 version, see Step 3 - Perform CA Service Catalog Post-Installation Tasks.
    For more information on the supported JRE versions, see Supportability Matrix.
  2. Navigate to the following location: <USM_HOME>\view\conf and edit the viewService.conf file.
  3. In the Java Additional Parameters section, add the following parameters towards the end:
    1. wrapper.java.additional.xx=-Djdk.tls.client.protocols=TLSv1.2
    2. Add wrapper.java.additional.xx=-noverify
    Where, xx is the serial number of the list of parameters in the section. For example, wrapper.java.additional.16=-Djdk.tls.client.protocols=TLSv1.2
  4. Comment the following parameter: #wrapper.java.additional.18=-XX:-UseSplitVerifier
    The serial number of the uncommented properties must be in a sequence.
  5. Save and close the file.
  6. Restart the CA Service Catalog services.
Post-Install Steps to Improve the Performance of ActiveMQ Message Queue (Mandatory)
Follow these steps:
  1. Navigate to the <USM_HOME>\view\webapps\usm\WEB-INF folder and edit the applicationContext.xml file.
  2. Search for the <amq:broker id="amqBroker" tag and add the following attribute within the tag:
    offlineDurableSubscriberTimeout="3600000"
    For example, <amq:broker id="amqBroker" offlineDurableSubscriberTimeout="3600000">
  3. Search for  the <amq:connectionFactory id="amqConnFactory"> tag and add the following property within the tag:
    property name="optimizeAcknowledge" value="true"
    For example:
    <amq:connectionFactory id="amqConnFactory">
    <property name="optimizeAcknowledge" value="true" />
    </amq:connectionFactory>
  4. Save and close the file.
  5. Restart the CA Service Catalog services.
Enable CORS filter
Perform the following steps to enable CORS filter:
  1. Open the 
    USMHOME/view/webapps/usm/WEB-INF/web.xml
     file.
  2. Modify the Current Key with the New Key as shown next.
    Current Key
    :
    <param-name>cors.allowed.origins</param-name>
    <param-value>*</param-value>
     
    New Key
    :
    <param-name>cors.allowed.origins</param-name>
    <param-value><http/https>://<Catalog Host Name>:<Catalog Port No>,<http/https>://<USS Host Name>:<USS Port No></param-value>
    : Enter the host name in lower case only.
  3. Save the file.
  4. Restart the CA Service Catalog Windows Service.
(Optional) Disable Form Definition Cache
Form definitions are cached for better response time with use case like submitting a request and viewing a request. This configuration is ideal for production deployments as form definitions seldom change. However for deployments on development or test environments the form definitions change frequently, it becomes imperative to read the form definition every time instead of using the cache. 
Perform the following steps to disable form definition cache:
  1. Open the 
    USMHOME/view/conf/ehcache.xml
     file.
  2. Modify the Current Key with the New Key as shown next.
    Current Key:
     
     <cache name="system.form.cache" maxBytesLocalHeap="100M" eternal="false" overflowToDisk="false" timeToIdleSeconds="86400" timeToLiveSeconds="120000"/>
     
    New Key
    :
     <cache name="system.form.cache" maxBytesLocalHeap="100M" eternal="false" overflowToDisk="false" timeToIdleSeconds="2" timeToLiveSeconds="2"/>
  3. Save the file.
  4. Restart the CA Service Catalog Windows Service.