Upgrade all server components
Important: Your RDBMS must be running before you start the upgrade.
SSO and smart card limitations and requirements
-
The only smart card client reader supported is the Common Access Card (CAC), a United States Department of Defense (DoD) smart card issued as standard identification for logging in to DoD hosted software.
-
Installing or configuring an SSO server requires specific Light Directory Access Protocol (LDAP) parameters. For details, see SSO and smart card authentication.
-
Review the SSO and smart card prerequisites in SSO and smart card authentication.
-
After upgrading Dimensions CM configured for SSO with a smart card, your SSO+CAC setup may not work due to the new string encryption mechanism in the updated software version. For details on how to re-enable the CAC authentication. See SSO and smart card tasks.
Upgrade a server with a PostgreSQL database
-
Run the server installer. Read and accept the license agreement.
-
Select upgrade components:
-
Dimensions Server
Upgrades the server and CM schema.
-
Single Sign On
Installs or configures a connection to an SSO server.
-
Smart Card Setup
Configures smart card authentication.
-
Deployment Automation Server
Installs a Deployment Automation server.
-
PulseUno
Installs PulseUno (required) and its modules (optional):
-
Git server: The server that PulseUno uses for Git repositories.
-
Vault server: The server that PulseUno uses for the library of software packages.
-
-
-
Accept the default installation folder or choose a different one.
-
If you are installing an SSO server, select one of the following:
-
New: Install a new SSO server.
-
Existing: Configure a connection to an existing SSO server, for example, Solutions Business Manager (SBM).
-
-
If you are installing an SSO server and smart card, do one of the following:
-
Existing SSO server:Specify the SSO server’s host name and port. Optionally select a secure HTTPS connection.
-
New SSO server without smart card:
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Defaults:
-
Port:
389
-
Search Filter:
(&(objectClass=user)(sAMAccountName={0}))
For details about server SSO parameters, see Single sign-on prerequisites.
-
-
New SSO server with smart card:
-
To configure the LDAP connection for authenticating smart cards, enter parameters for Hostname, Port, Bind User DN, and Password.
Default port:
389 -
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Search Filter default:
(&(objectClass=user)(sAMAccountName={0})).
-
After the installation is complete, manually configure the smart card trusted certificate authorities. For details, see Configure trusted certificate authorities.
-
-
Select Dimensions server components and schema.
-
Select the PostgreSQL database type.
-
Enter the name and password of the PostgreSQL SuperUser.
-
Enter the password for the PCMS_SYS schema. Default:
pcms_sys -
If prompted, enter the OS account name and password for the Dimensions CM system administrator. Default:
dmsys -
If you are installing a Deployment Automation server:
-
Select Install DA.
-
Accept the default installation directory or choose a different one.
-
(Optional if DA is already installed) Select Use existing settings.
-
(Optional) Select Skip database creation.
-
Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default:
7918 -
Select Client Mutual Authentication if you want Deployment Automation to use agent authentication when connecting to the server.
-
Specify a username and password for a new Deployment Automation database account to be created.
For details about installing and using DA, contact Support.
-
-
(Optional) If you are installing the PulseUno modules:
-
Install local Git server: Installs the server that PulseUno uses for Git repositories.
-
Install local Vault server: Installs the server that PulseUno uses for the library of software packages.
The PulseUno server is installed automatically (required).
If you have the Git and Vault servers installed remotely, provide their connection details and optionally enable HTTPS.
-
-
Click Install to start the upgrade. When the upgrade is complete, click Finish.
Upgrade a server with an Oracle database
-
Run the server installer. Read and accept the license agreement.
-
Select upgrade components:
-
Dimensions Server
Upgrades the server and CM schema.
-
Single Sign On
Installs or configures a connection to an SSO server.
-
Smart Card Setup
Configures smart card authentication.
-
Deployment Automation Server
Installs a Deployment Automation server.
Important: You must not install DA into a Serena-Supplied Runtime.
-
PulseUno
Installs PulseUno (required) and its modules (optional):
-
Git server: The server that PulseUno uses for Git repositories.
-
Vault server: The server that PulseUno uses for the library of software packages.
-
-
-
Accept the folder where Dimensions CM is installed or choose a different one.
- If you are installing an SSO server, select one of the following:
-
New: Install a new SSO server.
-
Existing: Configure a connection to an existing SSO server, for example, Solutions Business Manager (SBM).
-
-
If you are installing an SSO server and smart card, do one of the following:
-
Existing SSO server:Specify the SSO server’s host name and port. Optionally select a secure HTTPS connection.
-
New SSO server without smart card:
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Defaults:
-
Port:
389
-
Search Filter:
(&(objectClass=user)(sAMAccountName={0}))
For details about server SSO parameters, see Single sign-on prerequisites.
-
-
New SSO server with smart card:
-
To configure the LDAP connection for authenticating smart cards, enter parameters for Hostname, Port, Bind User DN, and Password.
Default port:
389 -
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Search Filter default:
(&(objectClass=user)(sAMAccountName={0})).
-
After the installation is complete, manually configure the smart card trusted certificate authorities. For details, see Configure trusted certificate authorities.
-
-
Select Dimensions server components and schema.
-
Select the Oracle database type.
-
Select the Oracle installation.
-
Enter the user and password of the Oracle administration account.
-
Enter the password for the PCMS_SYS schema for the Oracle instance.
-
Enter the OS account name and password for the Dimensions CM system administrator. Default:
dmsys - If you are installing a Deployment Automation server:
-
Select Install DA.
-
Accept the default installation directory or choose a different one.
-
(Optional if DA is already installed) Select Use existing settings.
-
(Optional) Select Skip database creation.
-
Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default:
7918 -
Select Client Mutual Authentication if you want Deployment Automation to use agent authentication when connecting to the server.
-
Specify a username and password for a new Deployment Automation database account to be created.
For details about installing and using DA, contact Support.
-
-
(Optional) If you are installing the PulseUno modules:
-
Install local Git server: Installs the server that PulseUno uses for Git repositories.
-
Install local Vault server: Installs the server that PulseUno uses for the library of software packages.
The PulseUno server is installed automatically (required).
If you have the Git and Vault servers installed remotely, provide their connection details and optionally enable HTTPS.
-
-
Click Install to start the upgrade. The installer:
-
Upgrades the Oracle tablespaces and sample process model. This may take a long time.
-
Upgrades the Common Tools (the Tomcat server, web client, and Administration Console).
-
Recalculates database statistics.
When the upgrade is complete, click Finish.
-
Upgrade a server with an SQL database
-
Run the server installer. Read and accept the license agreement.
-
Select upgrade components:
-
Dimensions Server
Upgrades the server and CM schema.
-
Single Sign On
Installs or configures a connection to an SSO server.
-
Smart Card Setup
Configures smart card authentication.
-
Deployment Automation Server
Installs a Deployment Automation server.
-
PulseUno
Installs PulseUno (required) and its modules (optional):
-
Git server: The server that PulseUno uses for Git repositories.
-
Vault server: The server that PulseUno uses for the library of software packages.
-
-
-
Accept the folder where Dimensions CM is installed or choose a different one.
- If you are installing an SSO server, select one of the following:
-
New: Install a new SSO server.
-
Existing: Configure a connection to an existing SSO server, for example, Solutions Business Manager (SBM).
-
-
If you are installing an SSO server and smart card, do one of the following:
-
Existing SSO server:Specify the SSO server’s host name and port. Optionally select a secure HTTPS connection.
-
New SSO server without smart card:
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Defaults:
-
Port:
389
-
Search Filter:
(&(objectClass=user)(sAMAccountName={0}))
For details about server SSO parameters, see Single sign-on prerequisites.
-
-
New SSO server with smart card:
-
To configure the LDAP connection for authenticating smart cards, enter parameters for Hostname, Port, Bind User DN, and Password.
Default port:
389 -
To configure LDAP details for user credentials, enter parameters for Hostname, Port, Base DN, Search Filter, Bind User DN, and Password.
Search Filter default:
(&(objectClass=user)(sAMAccountName={0})).
-
After the installation is complete, manually configure the smart card trusted certificate authorities. For details, see Configure trusted certificate authorities.
-
-
Select Dimensions server components and schema.
-
Select the SQL Server database type.
-
Specify SQL Server Options:
-
Select an existing SQL Server database you want to create an ODBC connection to.
-
If the SQL Server is on a remote machine, select Remote Database.
-
Accept the ODBC DSN or enter a different one.
-
-
Enter the password for the PCMS_SYS schema for the SQL server instance. Default:
pcms_sys -
If prompted, enter the OS account name and password for the Dimensions CM system administrator. Default:
dmsys - If you are installing a Deployment Automation server:
-
Accept the default installation directory or choose a different one.
-
(Optional if DA is already installed) Select Use existing settings.
-
(Optional) Select Skip database creation.
-
Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default:
7918 -
Select Client Mutual Authentication if you want Deployment Automation to use agent authentication when connecting to the server.
-
Specify a username and password for a new Deployment Automation database account to be created.
For details about installing and using DA, contact Support.
-
-
(Optional) If you are installing the PulseUno modules:
-
Install local Git server: Installs the server that PulseUno uses for Git repositories.
-
Install local Vault server: Installs the server that PulseUno uses for the library of software packages.
The PulseUno server is installed automatically (required).
If you have the Git and Vault servers installed remotely, provide their connection details and optionally enable HTTPS.
-
-
Click Install to start the upgrade. When the upgrade is complete, click Finish.

