Configuring after installation

This section covers the tasks that a system administrator should complete after installing product components and before using the product.


If you manually configure values in some files after installing or upgrading the product, you must update the corresponding values in the PlatformInstalledConfiguration.xml file in the AO_HOME directory. 

During future upgrades, the installer reads the PlatformInstalledConfiguration.xml file to populate installation wizard screens with those values. To ensure that the values used to populate the install wizard screens are valid for your environment, keep the values updated in the PlatformInstalledConfiguration.xml file.

If you change values in the following files, ensure that you locate the original values in the AO_HOME/ PlatformInstalledConfiguration.xml file and replace them with the new values:

  • AO_HOME/tomcat/conf/server.xml – Includes values, such as port number, protocol type, and host name
  • AO_HOME/tomcat/conf/context.xml – Includes values, such as port number, protocol type, and host name
  • AO_HOM/config/authentication.xml – For Platform version 7.9 and later, this file contains Remedy Single Sign-On values for realm, URL, and Remedy SSO type (embedded or external)

Configuring Remedy Single Sign-On custom cookie name

If you change the default cookie name parameter in Remedy SSO, you must ensure that the custom cookie name is configured in the  Platform environment.

If the cookie name in RSSO and does not match, you cannot log on to any peers or the repository. The cookie name is automatically created at the installation and is based on the time stamp, which is the time the database is created during Remedy SSO installation. 

Perform the following steps for all  Platform components for which the cookie name is changed. 

  1. Go to AO_HOME/config/authentication.xml file.
  2. In the authentication.xml file, add a <token-name> parameter and specify the value for the cookie name that matches the cookie name specified in Remedy SSO. 
    For example, <token-name>%custom-cookie-name%</token-name>
  3. Save changes and restart the  Platform server. 
  4. Repeat steps 1 to 3 for all peers that contain a custom cookie name. 

Related topics

Using software configuration management systems when creating workflows


Was this page helpful? Yes No Submitting... Thank you