• Review the Installation and upgrade considerations in this topic.

• Check the Support Matrix.

For instructions on installing and upgrading Dimensions CM, see the following guides:

• UNIX Installation Guide

• Windows Installation Guide

UNIX: Use separate installers for server, agents, and clients.

Update operating systems

Apply the latest updates for your operating system.

AIX: Install the latest version of the OS package: bos.rte.libc.

Windows Server 2012 R2: Install the following updates:

• KB2919442

• KB2919355

In addition to the packages listed in the installation guide, you need to add the following files:

• libnsl.x86_64

• libnsl.i686

• libxcrypt.i686

• motif.x86_64

Before installing Dimensions CM, verify that the following packages are installed:

• libxcrypt.x86_64

• libxcrypt.i686

• libstdc++.i686

• motif.x86_64

• motif.i686

• nss-softokn-freebl.x86_64

• nss-util.x86_64

• libXp.i686

• libXp.x86_64

• libXpm.x86_64

If you get an error message during installation, stating that Dimensions CM is unable to connect to the database:

• Check that you have entered the correct database password and Oracle DSN if applicable.

• Check that the database used by Dimensions CM is active (up). Confirm that it is running, or that you can connect to it, using standard RDBMS database utilities such as sqlplus.

If you cannot install Dimensions CM on Windows Server 2012R2 with Oracle 12, check the following:

• The system PATH contains ORACLE_HOME (this should be true if the system is restarted after installing Oracle).

  If ORACLE_HOME is not in the path, the CM server installation fails to validate the Oracle connection details.

• The Oracle administrator password doesn't contain a full stop (.), comma (,), or semicolon (;). If any of these characters are included, the CM server installer may fail to validate the Oracle connection details.

  Temporarily remove these characters from the password before installing.

A bug in earlier versions of Visual Studio 2017 may cause the installation of the CM integration to fail.

Before installing or upgrading Dimensions CM, install the latest update to Visual Studio 2017.

UNIX: After you upgrade Dimensions CM and Deployment Automation, you can safely ignore the following messages:

com.installshield.sra.event.InstallScript, msg2, InstallScript.onReplacingcCoreFiles

com.installshield.sra.event.InstallScript, msg2, Tomcat was not found.

com.installshield.sra.event.InstallScript, msg2, InstallScript.onReplacingcCoreFiles

Windows Server installation: The location of the PulseUno data directory may vary:

• If you perform a new installation, the PulseUno data directory is:

  \ProgramData\Micro Focus\Dimensions CM\Pulse

• If you upgrade from an earlier release, the PulseUno data directory is the same, for example:

  \ProgramData\Serena\Pulse

To upgrade a Dimensions CM installation configured to use the CM single sign-on Server (SSO):

1. Stop Common Tomcat.

2. Navigate to the Tomcat installation location.

3. Rename the lib directory to lib.pre145.

4. Rename the alfssogatekeeper directory to alfssogatekeeper.pre145.

5. Perform the upgrade.

6. After the upgrade has completed, navigate to the CM installation location. Verify that all occurrences of the SSO_STS_ENDPOINT variable in the %DM_ROOT%\dm.cfg configuration file contain the string localhost and not the host name of your machine.

Note: These steps are not required if the installation is configured to use Solutions Business Manager as the SSO server.

Make sure to uninstall earlier versions of Dimensions Connect for SBM and then install the corresponding version before you upgrade the Dimensions CM server.

For example, after you upgrade the Dimensions CM server to 14.6, you need to install Dimensions Connect for SBM version 14.6. Otherwise, the integration may not work as expected. See Connect to SBM.

During installation or upgrade, a new version of the ALF events configuration file is installed for PulseUno:

$DM_ROOT/dfs/alf_events_config.xml

Any customizations are overridden. But your original file is backed up, and you can merge your customizations into the new version.