Upgrade all server components

  1. Run the server installer. See Run the installer. Read and accept the license agreement.

  2. Select Upgrade.

  3. Accept the directory where Dimensions CM is installed or choose a different one.

  4. Select Upgrade all Dimensions Server Components.

  5. Select an SSO upgrade option:

    • Dimensions SSO

    • Dimensions SSO and Smart Cards

    • Do not setup Dimensions SSO or Smart Cards

  6. Enter the OS account name and password for the Dimensions CM system administrator. Default: dmsys

  7. Select a database type, Oracle or PostgreSQL.

  8. If you selected an Oracle database:

    1. Select an Oracle installation.

    2. Enter the owner of the Oracle files:

      • For a local database, enter the user on the local machine.

      • For a remote database, enter the user on the remote machine.

      Default: oracle

    3. Select the directory where Oracle is installed.

    4. Enter the following Oracle system information:

      • Host name of the machine where Oracle is installed.

      • System ID (SID), for example, dim14.

      • NET8 Service Name, for example, dim14.

      • TCP /IP Port number: a local or remote Oracle instance. Default: 1521

        Note: SID and NET8 Service Name are normally the same. You must enter these correctly. Otherwise, the upgrade does not function properly.

    5. Enter the following Oracle values:

      • Oracle administration user. Default: system

      • Password for the administration user. Default: manager

      • Password for the PCMS_SYS schema that was created for the Oracle instance. Default: pcms_sys

      Note:  

      • Values are case-sensitive.

      • If you are installing on a Linux server that has a 32-bit RDBMS, a message may appear. This server is native 64-bit and cannot be used with a 32-bit RDBMS. The installer automatically installs a 64-bit Oracle Instant Client. Accept the default directory or select a different one.

    6. Enter the name of the Dimensions CM base database that the listener connects to after the upgrade is complete, for example, cm_typical.

  9. If you selected a PostgreSQL database:

    1. Select a local or remote database.

    2. Enter the following PostgreSQL parameters:

      • The database host name and port number.

      • The database name, for example, dim14.

      • The name and password of the PostgreSQL SuperUser.

  10. (Optional) Install a Deployment Automation server:

    Important:You must not install DA into a Serena-supplied Oracle runtime.

    • 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.

    • Select Client Mutual Authentication if you want Deployment Automation to use agent authentication when connecting to the server.

    • Specify the username and password for the new Deployment Automation database account to be created.

    For details about installing and using DA, see the Support website.

  11. (Optional) Install the PulseUno modules:

    • Install local Git server: Install the server that PulseUno uses for Git repositories.

    • Install local Vault server: Install 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 an HTTPS connection.

  12. Select an SSO server installation option:

    • New: Install a new SSO server.

    • Existing: Configure a connection to an existing SSO server, for example, Solutions Business Manager (SBM).

  13. 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})).

        For information about server SSO and smart card parameters, see Single sign-on prerequisites‌‌.

    After the upgrade is complete, manually configure the smart card trusted certificate authorities. For details, see Configure trusted certificate authorities.

  14. Specify the operating system user to own and run Tomcat and Java. This user is typically given restricted permissions and must exist before you start the installation.

    Default: dmsys

  15. Accept the default port number for the Tomcat server (8080) or enter a different one if it is in use. Some software is hard-coded to port 8080 and cannot be reassigned. See Use TCP/IP ports.

  16. Review the settings and click Install to start the upgrade. The installer:

    • Creates uninstaller files in the directory _uninst_maint located one level up from the root directory. A record of the installed products is created in: 138

      To uninstall, you must use the uninstaller files in the _uninst_maint directory to ensure that the inventory is correctly updated. For details, see Uninstall OpenText Dimensions CM.

    • Upgrades the Oracle tablespaces and sample process model. This may take a long time.

    • Upgrades the Common Tools (Tomcat server, web client, and Administration Console).

    • Recalculates database statistics, status is logged at:

      /tmp/dimensions_install/dbstats.log

    When the upgrade is complete, click Finish.