Server post-upgrade tasks

Update database views ‌

Perform the following steps on each additional base database:

1. Log in to dmdba as the Dimensions CM RDBMS administrator.

   • Oracle Enterprise: system

   • Microsoft SQL Server: pcms_sys

2. Enter the following in a command prompt. <connect_string> is the appropriate Database Source Name for the connection:

   • Oracle Enterprise:

     dmdba system/<system_password>@<connect_string>

     For example:

     dmdba system/manager@dim14

   • For SQL Server

     dmdba -ea dbo@<connect_string>

     For example:

     dmdba -ea dbo@dim14

3. At the SYSTEM> or PCMS_SYS> prompt, enter the following Dimensions dmdba command-pairs for each base database:
   

   drop_base_views <BaseDatabase1> /Force 
   create_base_views <BaseDatabase1> /Force 
   drop_base_views <BaseDatabase2> /Force 
   create_base_views <BaseDatabase2> /Force
   ...
   ...
   drop_base_views <BaseDatabaseN> /Force 
   create_base_views <BaseDatabaseN> /Force 
   exit

   For example, for a server that uses Oracle and has additional base databases test1 and test2 with the default <connect_string> of dim14, enter:

   $ dmdba system/<system_password>@dim14 
   SYSTEM> drop_base_views test1 /Force 
   SYSTEM> create_base_views test1 /Force 
   SYSTEM> drop_base_views test2 /Force 
   SYSTEM> create_base_views test2 /Force 
   SYSTEM> exit

Reinstall Dimensions published views‌

After upgrading, reinstall all published views.

For details, see Install Dimensions published views‌‌ and the Reports Guide.

Rebuild developer toolkit applications‌

Rebuild existing API, web services, or custom integrations. For details, see the Developer's API Reference.

SSO SBM Server tasks

• Replace the sts.pem file and update the file $Tomcat\alfssogatekeeper\conf\truststore.jks.

• If the SBM SSO Server is using SSL (https), the non-Java clients need to have the $installdir\dfs\cacerts.pem file updated so that it includes the JBOSS certificate and certificate chain in PEM format.

• Stop and restart the OpenText Common Tomcat and Dimensions CM listener.

SSO and smart card tasks

If you are installing an SSO server with smart card, see the following additional post-installation activities:

• Configure trusted certificate authorities

• Establish a certificate revocation list‌‌

Restore SSO/CAC customizations

If your environment already uses SSO with Common Access Card (CAC) enabled, during an upgrade, the following folders are backed up:

•                     tomcat/<version>/alfssogatekeeper
                  

  to

  tomcat/<version>/alfssogatekeeper.pre.1.8.0.0

•                     tomcat/<version>/lib
                  

  to

  tomcat/<version>/lib.pre.1.8.0.0

•                     tomcat/<version>/webapps/idp
                  

  to

  tomcat/<version>/webapps.pre.14.5.1/idp

If you customized your SSO configuration with new certificates, and made changes to the truststore and keystore, do the following:

• Manually restore your custom keystore files from the backup to the idp and alfssogatekeeper folders.

• Merge your custom changes into:

  • <TOMCAT_HOME>\webapps\idp\WEB-INF\conf\
    Configuration.xml
    

  • <TOMCAT_HOME>\alfssogatekeeper\conf\
    gatekeeper-core-config.xml

  Do not replace these new .xml files with the backed-up versions.
  

After you upgrade Dimensions CM that uses SSO with a smart card, your SSO+CAC configuration may not work due to the new string encryption mechanism in the updated software version.

To enable the CAC authentication, re-encode all encoded values of type htf:encstring contained in this file:

<TOMCAT_HOME>/webapps/idp/WEB-INF/conf/ 
  Configuration.xml

To re-encode each value, run the sso_encstring.sh command:

<TOMCAT_HOME>/bin/sso_encstring.sh" -e <value to encode>

For example:

C:\Program Files\OpenText\common\tomcat\9.0\
bin\sso_encstring.bat" -e changeit