UNIX 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, normally system.

2. Enter the following in a terminal window:
   

   $ dmdba system/<system_password>@<connect_string>

   where <connect_string> is the appropriate RDBMS Database Source Name for the connection. For example:
   

   $ dmdba system/manager@dim14

3. At the SYSTEM> 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‌

Reinstall all published views by running the following DMDBA commands as your system user.

delv basedatabasename 

insv basedatabasename

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

Rebuild existing API applications ‌

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

Configure UNIX command files‌

The upgrade creates the dmstartup and dmshutdown scripts in the $installdir/prog directory. You may need to merge any customized changes that you performed on your previous scripts with these new versions.

After you have made these changes, verify that Dimensions CM shuts down and starts up successfully using these scripts.

Remove duplicate configuration entries‌

The upgrade may generate multiple rows of the same entry in the configuration file $installdir/dm.cfg.

We recommend to check this file and remove any duplicate entries. Future changes made to particular rows fail to become effective if subsequent unchanged formerly duplicate rows exist in the file.

SSO and smart card tasks

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

• Configure trusted certificate authorities

• Disable username and password authentication‌‌

• Establish a certificate revocation list‌‌

Fix demo certificate mismatches

Upgrading a CM 12 server (without SSO) to the latest 14.x version and then enabling SSO with the demo certificates causes a mismatch of the jks and pem files. You need to manually restore the certificates on the latest server version, and restart Tomcat:

1. Before running the installer, make a copy of the 14.x.x backup file:
   

   <tomcat-install-dir>/alfssogatekeeper/conf/ truststore.jks.14.x.x

   where 14.x.x is the upgraded Dimensions CM version.

2. Stop the Tomcat service.

3. Run the installer to install SSO.

4. Rename this file:
   

   <tomcat-install-dir>/alfssogatekeeper/conf/
     truststore.jks

   Replace it with your backup of truststore.jks.14.x.x.

5. Rename this file:

   /opt/opentext/dimensions/<version>/cm/dfs/sts.pem

   Replace it with a file called sts.pem.14.x.x in the same folder, where 14.x.x is the upgraded Dimensions CM version.

6. Restart the Tomcat service.

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:

  • idp/WEB-INF/conf/Configuration.xml

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

/opt/opentext/dimensions/14.7/common/tomcat/9.0/ bin/sso_encstring.sh" -e changeit

Deployment automation tasks‌

If you previously installed CM and Deployment Automation (DA) together and then upgraded them using the CM server installers, edit the CM configuration file (dm.cfg) and change the following line:

DM_SDA_URL %DM_WEB_URL%/serena_ra

to

DM_SDA_URL %DM_WEB_URL%/da