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

Post Installation Steps for CA Unified Self-Service

Last update July 19, 2016

Perform the following optional post-installation steps for USS 14.1.02:

Prerequisites

Create a backup of the US4SM\OSOP\portal-ext.properties file.

Note: US4SM is the default Unified Self-Service installation directory.

Customize CA SDM Data Source Property

Perform the following steps to customize the CA SDM Data Source Property:

  1. Open the US4SM\OSOP\portal-ext.properties file and copy the following content at the end of the file:

    # SDM Datasource Config Fields

    # Maximum number of the SDM Fields that can be shown in SDM Datasource config Fields sections

    # If no value/invalid value/ value less than 4 is specified, it will default to 10

    sdm.configFields.maxFieldsToShowInConfigOptionsPage = 10

    # If you want this property to be tenant specific, prefix the Web ID of the tenant to the property. It is case-sensitive

    # (Web Id can be obtained from the http(s)://server-name:<port-no>/group/control panel > Portal Instances)

    # Example Format:

    someCompany.com.sdm.configFields.maxFieldsToShowInConfigOptionsPage = 10

  2. Save the file and restart the services.

Enable or Disable the Community

Perform the following steps to enable or disable the community: 

  1. Open US4SM\OSOP\portal-ext.properties and copy the following content at the end of the file:

    # Community On/Off
    # Community/Message board feature can be disabled by the setting property disable.uss.community to true (case sensitive)

    # Example - with Multi tenancy 
    # For a specific tenant, prefix the property with the tenant webID 
    # For tenants, if the value is not defined or the property is missing,Community is enabled, by default.

    someCompany.com.disable.uss.community = true 

    # Example - All other tenant Community will be disabled if the value for the property is true (case sensitive).
    # If the value is not defined or the property is missing, Community is enabled, by default.

    # disable.uss.community = true

  2. Save the file and restart the services.

Enable Clickjacking Filter

Follow these steps:

  1. Open the US4SM\OSOP\tomcat-7.0.40\conf\web.xml file.

  2. Search for the text: Built In Filter Definitions
    The Built In Filter section appears as follows:
    <!-- ================== Built In Filter Definitions ===================== -->

    <filter>
    .
    .
    .
    </filter>

  3. Add the following filter at the end of the Built In Filter Definitions section:

    <!-- Filter :Restricts framing of USS application in all domains expect the current domain in which USS is hosted -->

    <filter>
    <filter-name>ClickjackFilterSameOrigin</filter-name>
    <filter-class>org.owasp.esapi.filters.ClickjackFilter</filter-class>
    <init-param>
    <param-name>mode</param-name>
    <param-value>SAMEORIGIN</param-value>
    </init-param>
    </filter>

    <filter-mapping> 
    <filter-name> ClickjackFilterSameOrigin </filter-name>
    <url-pattern>/*</url-pattern>
    </filter-mapping>

  4. Save and close the file and restart the services.

USS Announcements are Formatted Incorrectly for Windows

  1. Navigate to the US4SM\OSOP\tomcat-7.0.40\bin folder and edit the file wrapper.conf:
    1. Modify the variable wrapper.java.additional.20 value from -Duser.timezone=GMT to -Duser.timezone=sdm-time-zone
      For Example: ‘-Duser.timezone=America/Denver’. (Mountain Time)
    2. Save and close the file.
  2. Navigate to US4SM\OSOP\ folder and append the following content at the end of the portal-ext.properties file.

    #set this to show the announcement date format in 24/12 hr

    #format:

    # dd-MMM-yy hh.mm.ss aa for 12 hr format

    # dd-MMM-yy HH.mm.ss for 24 hr format

    announcement.date.format=dd-MMM-yy hh.mm.ss aa

  3. Save the file and restart the services.

USS Announcements are Formatted Incorrectly for Linux

  1. Navigate to the US4SM\OSOP\tomcat-7.0.40\bin folder and edit the file setupenv.sh
    1. Modify the variable Duser.timezone value from -Duser.timezone=GMT to -Duser.timezone=sdm-time-zone
      For Example: ‘-Duser.timezone=America/Denver’. (Mountain Time)
    2. Save and close the file.
  2. Navigate to US4SM\OSOP\ folder and append the following content at the end of the portal-ext.properties file.

    #set this to show the announcement date format in 24/12 hr

    #format:

    # dd-MMM-yy hh.mm.ss aa for 12 hr format

    # dd-MMM-yy HH.mm.ss for 24 hr format

    announcement.date.format=dd-MMM-yy hh.mm.ss aa

  3. Save the file and restart the services.

For more information about USS enhancements, see CA Service Management Release 14.1.02 Enhancements.

Was this helpful?

Please log in to post comments.

  1. Kyle R
    2016-01-19 09:18

    NOTE The value for "sdm-time-zone" in the sections "USS Announcements are Formatted Incorrectly for Windows/Linux" are the "Symbol" values from the Timezones.

    See Service Desk Manager, Administration, Service Desk, Application Data, Codes, Timezone.

    For example, if you were in Singapore and wished to use a timezone offset of "GMT+0800" then there is a default Symbol value of "Beijing" which matches to this: "Beijing. GMT+0800. Beijing, Chongqing, Urumqi, Hong Kong, Perth, Singapore, Taipei." which would be recorded in the file as: "wrapper.java.additional.20=-Duser.timezone=Beijing"

    Or of course, you may add your own Timezone and use that Symbol.

    1. Kyle R
      2016-01-19 09:19

      Including an incorrect Symbol will result in USS displaying "NaN" against any Announcements.

      1. Madhuri Mishra
        2016-03-31 11:12

        Thanks, Kyle R.

        I'll update the topics.

        Thanks,

        DocOps Services Team

  2. J.W.
    2016-11-06 10:04

    This topic is a duplicate if this:

    https://docops.ca.com/ca-service-management/14-1/en/implementing/implementing-ca-service-management-14-1-02/post-installation-tasks/post-installation-steps-for-unified-self-service

  3. Rajashree Nair
    2016-11-11 03:06

    Thanks J.W. We will remove the duplicate topic. 

     

    Thanks again.

    Regards,
    DocOps Services Team