Install Dimensions CM
This topic provides guidelines and considerations for installing and upgrading Dimensions CM on a Windows or UNIX system.
In this topic:
Installation overview
Use this information to prepare for installing or upgrading Dimensions CM.
Before you install |
|
Install and upgrade |
For instructions on installing and upgrading Dimensions CM, see the following guides: Note: For UNIX, there are separate installers for servers, agents, and clients. |
Manage licenses |
To use AutoPass License Server (APLS), see Dimensions CM licensing. To use License Manager (SLM), see Administering Licenses and the License Server in the Administration Guide. |
Optimize and scale | For details about hardware scaling requirements, see the Architecture and Optimization Guide. |
Get more support | See the Micro Focus Support portal for support, expertise, and resources. |
Installation and upgrade considerations
Review these considerations before you begin installing or upgrading Dimensions CM.
Update operating systems |
Apply the latest updates for your operating system. AIX: You must install the latest version of the OS package: bos.rte.libc. Windows 8.1 and Windows Server 2012 R2: You must install the following updates: |
Install on Winsdows | Before installing on Windows, ensure that you have at least 15 Gb of free space on the main disk (usually C:). |
Red Hat 8.x prerequisites |
In addition to the packages listed in the installation guide, you need to add the following files:
|
Red Hat 8.2 and CentOS 8.2 prerequisites |
Verify that the following packages are installed before you install Dimensions CM:
|
Unable to connect to database when installing |
If an error message is displayed during installation, stating that Dimensions CM is unable to connect to the database:
|
Install on Windows Server 2012R2 with Oracle 12 |
If you cannot install Dimensions CM on Windows Server 2012R2 with Oracle 12, check the following:
|
Install into a remote SQL server | If you are installing a CM server into a remote SQL server, you need to use an existing and preconfigured ODBC. |
Install the Visual Studio 2017 integration |
A bug in earlier versions of Visual Studio 2017 may cause the installation of the CM integration to fail. Before installing or upgrading to the CM clients 14.5.2 or later, install the latest update to Visual Studio 2017. |
UNIX CM server upgrade messages |
After you upgrade Dimensions CM and Deployment Automation on UNIX to 14.5.2 or later, you can safely ignore the following messages:
|
PulseUno data directory |
Windows Server installation: The location of the PulseUno data directory may vary:
|
Install on Solaris | The Solaris installer requires JRE 1.8 or later. |
Upgrade Dimensions CM with CM SSO |
To upgrade a Dimensions CM installation configured to use the CM Single Sign-On Server (SSO):
Note: These steps are not required if the installation is configured to use Solutions Business Manager as the SSO server. |
Upgrade Dimensions Connect for Solutions Business Manager (SBM) |
Make sure to uninstall earlier versions of Dimensions Connect for SBM and then install version 14.5.3 before you upgrade the Dimensions CM server. For example, if you upgrade the Dimensions CM server to 14.5.3, you must also install Dimensions Connect for SBM version 14.5.3. Otherwise, the integration may not work as expected. See the Dimensions CM Connect for SBM Guide. |
ALF events configuration file |
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. |
See also: