Install all server components‌‌

Remote schema requirements‌

Your environment may require a schema to be installed on a remote database. For example, users on a local node want to use a remotely administered database.

To use a remote Oracle database, a client must be set up on the local node to perform database operations between the local server and the remote database. The client can be any of the following:

  • SQL Server

    • An SQL Server Enterprise client

    • A full SQL Server Enterprise installation

  • Oracle RDBMS

    • An Oracle client.

    • An Oracle instant client.

    • A full Oracle Enterprise installation.

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 Single sign-on prerequisites‌‌.

  • See the SSO and smart card prerequisites in Single sign-on prerequisites‌‌.

Install a server with a PostgreSQL database‌

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

  2. For Database Type, select PostgreSQL.

  3. Select a database option:

    • Create new database installation. Use the version of PostgreSQL included with the installer.

    • Use existing local database installation. Use an existing PostgreSQL database located on the local machine.

    • Use existing remote database installation. Use an existing PostgreSQL database located on a remote machine.

  4. Select these installation components:

    • Single Sign On

      Installs or configures a connection to an SSO server. You can also configure 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.

    For details about separating the database upgrade or migration operations from the server installation, contact Support.

  5. Accept the default installation folder or choose a different one.

  6. 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).

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

  8. Select Dimensions server components and schema.

  9. Select a licensing option:

    • Specify License Server

      If the AutoPass License Server (APLS) is running on a remote machine, enter the URL of the remote machine.

      If APLS is running on the same machine as the Dimensions CM server, accept the following localhost URL:

      https://localhost:5814/autopass

      For details about configuring Dimensions CM to use APLS, see Licensing.

    • Install a 30-day evaluation license

  10. Enter the PostgreSQL installation or connection details:

    • New PostgreSQL installation:

      1. Accept the default installation folder or select a different one.

      2. Accept the default data directory or select a different one.

      3. Enter the name and password of the PostgreSQL SuperUser.

      4. Accept the default port number or enter a different one.

      5. Click Next and then enter the Dimensions CM database name and the DB Owner credentials.

    • Existing local PostgreSQL installation:

      Select a local installation from the list, or click Manual Entry and enter the PostgreSQL details:

      • Home and data directories.

      • Database name and port number.

      • SuperUser name and password.

    • Existing remote PostgreSQL installation:

      1. Enter the server host name and port number.

      2. Enter the Dimensions CM database name.

      3. Enter the name and password of the PostgreSQL SuperUser.

      4. (Optional) Check the connection to the database.

  11. Enter the password for the PCMS_SYS schema. This schema stores system data for the OpenText Dimensions CM installation. Default: pcms_sys

  12. Select a demo process model. For details, see Choose a process model .

  13. For process model options, specify the following:

    1. Enter the operating system ID of the tool manager for the demo process model. Default: dmsys

    2. Enter the credentials for the work and deployment areas:

      • Area Owner ID

        Accept the default (dmsys) or enter a login ID. This user is set by default as the system administrator login ID.

      • Password

        Enter the password for the area owner.

    3. Accept the default directory for the demo process model areas or select a different one.

    After the installation, you must assign operating system accounts to the users in the sample process model.

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

  15. If you are installing a Deployment Automation server:

    1. Accept the default installation directory or choose a different one.

    2. (Optional if DA is already installed) Select Use existing settings.

    3. (Optional) Select Skip database creation.

    4. Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default: 7918

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

    6. Specify a username and password for a new Deployment Automation database account to be created.

    For details about installing and using DA, contact Support.

  16. (Optional) Enter the host name of an email server so that CM can send emails to users, for example, when items are actioned. For details about configuring emails, see the Administration Guide.

  17. If you are not installing the PulseUno Git and Vault modules, choose whether to configure the Git and Vault server connection:

    • To configure the connection, specify the host name and port number for the Git/Vault server. Optionally select the HTTPS option to enable HTTPS.

    • To skip configuring the connection, select Do not configure PulseUno for a remote Git/Vault server.

  18. 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. For details, see Use TCP/IP ports.

  19. Review the settings and click Install. When the installation is complete, click Finish.

Install a server with an Oracle database‌

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

  2. For Database Type, select Oracle.

  3. Select a database location:

    • Local: Use an Oracle located on the local machine.

    • Remote: Use an Oracle located on a remote machine.

  4. Select these installation components:

    • Single Sign On

      Installs or configures a connection to an SSO server. You can also configure 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.

      For details about separating the database upgrade or migration operations from the server installation, contact Support.

  5. Accept the default installation folder or choose a different one.

  6. 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).

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

  8. Select Dimensions server components and schema.

  9. Select a licensing option:

    • Specify License Server

      If the AutoPass License Server (APLS) is running on a remote machine, enter the URL of the remote machine.

      If APLS is running on the same machine as the Dimensions CM server, accept the following localhost URL:

      https://localhost:5814/autopass

      For details about configuring Dimensions CM to use APLS, see Licensing.

    • Install a 30-day evaluation license

  10. Select a local or remote Oracle installation from the list, or click Manual Entry and enter the Oracle SID and Oracle Home.

    • For a remote Oracle, specify:

      • Oracle Home: the location of your local Oracle client to manage communication with the remote database.

      • Oracle SID: the Net Service Name by which your client installation knows the remote database.

    • For a container database, click PDB Details and specify the Oracle Home and the PDB Name.

  11. Enter the user and password for the Oracle administration account.

    Defaults:

    • User ID: system

    • Password: manager

  12. Enter the password for the PCMS_SYS schema for the Oracle instance. Default: pcms_sys

  13. Select a demo process model. For details, see Choose a process model .

  14. For process model options, specify the following:

    1. Enter the operating system ID of the tool manager for the demo process model. Default: dmsys

    2. Enter the credentials for the work and deployment areas:

      • Area Owner ID

        Accept the default (dmsys) or enter a login ID. This user is set by default as the system administrator login ID.

      • Password

        Enter the password for the area owner.

    3. Accept the default directory for the demo process model areas or select a different one.

    After the installation, you must assign operating system accounts to the users in the sample process model.

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

  16. If you are installing a Deployment Automation server:

    1. Accept the default installation directory or choose a different one.

    2. (Optional if DA is already installed) Select Use existing settings.

    3. (Optional) Select Skip database creation.

    4. Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default: 7918

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

    6. Specify a username and password for a new Deployment Automation database account to be created.

    For details about installing and using DA, contact Support.

  17. (Optional) Enter the host name of an email server so that CM can send emails to users, for example, when items are actioned. For details about configuring emails, see the Administration Guide.

  18. If you are not installing the PulseUno Git and Vault modules, choose whether to configure the Git and Vault server connection:

    • To configure the connection, specify the host name and port number for the Git/Vault server. Optionally select the HTTPS option to enable HTTPS.

    • To skip configuring the connection, select Do not configure PulseUno for a remote Git/Vault server.

  19. 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. For details, see Use TCP/IP ports.

  20. Review the settings and click Install. When the installation is complete, click Finish.

Install a server with an SQL database

  1. Run the server installer. Read and accept the license agreement.
  2. For Database Type, select SQL Server.

  3. Choose an ODBC connection:

    • Existing: Use an existing ODBC connection to a database.

    • New: Create a new ODBC connection to a database.

  4. Select a database location:

    • Local: Use an SQL database located on the local machine.

    • Remote: Use an SQL database located on a remote machine.

    If you are installing a CM server into a remote SQL Server, you must use an existing and preconfigured ODBC. Creating a new ODBC as part of the installation does not work.

  5. Select these installation components:

    • Single Sign On

      Installs or configures a connection to an SSO server. You can also configure 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.

      For details about separating the database upgrade or migration operations from the server installation, contact Support.

  6. Accept the default installation folder or choose a different one.
  7. 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).

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

  9. Select Dimensions server components and schema.

  10. Select a licensing option:

    • Specify License Server

      If the AutoPass License Server (APLS) is running on a remote machine, enter the URL of the remote machine.

      If APLS is running on the same machine as the Dimensions CM server, accept the following localhost URL:

      https://localhost:5814/autopass

      For details about configuring Dimensions CM to use APLS, see Licensing.

    • Install a 30-day evaluation license

  11. Configure an ODBC connection:

    • Existing ODBC connection: Enter the database name and ODBC DSN for an existing connection.

    • New ODBC connection:

      1. Select the local or remote SQL Server instance you want to create an ODBC connection to.

        Default: local or MSSQLSERVER depending on whether you are running SQL Server Enterprise.

      2. Enter the database name and ODBC DSN for the new connection or accept the default values. These values are used by the Dimensions CM schema. The DSN is an ODBC data source that stores information about how to connect to the database.

      3. Specify the folder containing the SQL Server installation.

      4. Specify the folder where to create the SQL database.

      5. Specify the disk space to be allocated to CM data and log files.

  12. Enter the password for the PCMS_SYS schema for the Oracle instance. Default: pcms_sys

  13. Select a demo process model. For details, see Choose a process model .

  14. For process model options, specify the following:

    1. Enter the operating system ID of the tool manager for the demo process model. Default: dmsys

    2. Enter the credentials for the work and deployment areas:

      • Area Owner ID

        Accept the default (dmsys) or enter a login ID. This user is set by default as the system administrator login ID.

      • Password

        Enter the password for the area owner.

    3. Accept the default directory for the demo process model areas or select a different one.

    After the installation, you must assign operating system accounts to the users in the sample process model.

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

  16. If you are installing a Deployment Automation server:

    1. Accept the default installation directory or choose a different one.

    2. (Optional if DA is already installed) Select Use existing settings.

    3. (Optional) Select Skip database creation.

    4. Specify the port number that Deployment Automation agents will use to make Java Message Service (JMS) connections to the server. Default: 7918

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

    6. Specify a username and password for a new Deployment Automation database account to be created.

    For details about installing and using DA, contact Support.

  17. (Optional) Enter the host name of an email server so that CM can send emails to users, for example, when items are actioned. For details about configuring emails, see the Administration Guide.

  18. If you are not installing the PulseUno Git and Vault modules, choose whether to configure the Git and Vault server connection:

    • To configure the connection, specify the host name and port number for the Git/Vault server. Optionally select the HTTPS option to enable HTTPS.

    • To skip configuring the connection, select Do not configure PulseUno for a remote Git/Vault server.

  19. 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. For details, see Use TCP/IP ports.

  20. Review the settings and click Install. When the installation is complete, click Finish.