Dimensions CM 14.5 Release Notes

These release notes contain important information about Dimensions CM 14.5. Last updated March 20, 2019.

About this Release What's New Installing and Upgrading Limitations Fixed Issues Known Issues Legal Notice

# Contents

- About this Release
- What's New
- Installing and Upgrading
- Limitations
- Fixed Issues
- Known Issues
- Legal Notice

# About this Release

Dimensions CM 14.5 is the version that immediately follows 14.4. All of the features, changes, and fixes that were made in 14.4 are included in 14.5.

Dimensions CM 14.5 supports new installations. You do not need to install a previous version of Dimesnions CM before installing this version.

## Helpful Links

Documentation: the most up to date CM 14.5 information including online help, all the documents in PDF format, and an archive going back to version 4.0.

Documentation Roadmap: a complete overview of the documentation to help you find the information you are looking for.

Dimensions CM Feature History: describes key feature enhancements in the major releases of Dimensions CM, starting with version 10.1.

Technical Support

## Contact Us

For specific Dimensions CM issues contact Support.

Additional technical information or advice is available from several sources:

- Product documentation, Knowledge Base articles, and videos.
- The Community web pages.

## Virtual Environment Support

Micro Focus recognizes that virtualization technology provides significant utility and value to our customers. As such, Micro Focus conducts functional testing and certifies our products using virtualization technology in addition to native environments. While Micro Focus expects that our products will function properly when running on supported platforms in a virtualized environment as well as a native environment, there may be functional and performance limitations. Micro Focus will not require customers to recreate and troubleshoot every issue in a non-virtualized environment, however there may be circumstances in which such action may be required. Micro Focus will only make this request when there is reason to believe that the virtualized environment is a contributing factor to the issue. If the issue cannot be reproduced in a supported non-virtualized environment, customers will need to refer their issues to their virtualization vendor.

# What's New

## Branching and Merging

New features have been added to streamline:

- Branching
- Making, reviewing, and approving code changes.
- Merging changes with work done by other developers.

For full details see the Dimensions CM User's Guide.

### Topic Streams

Topic streams are temporary streams that are fast and easy to create. You can use them to develop a set of defined changes, for example, to fix a defect or implement a small feature in isolation from other development work.

### Pull Requests

A pull request is a special type of review that you use to evaluate, review, and merge a set of defined changes, typically in a topic stream. Pull requests are a collaborative process that allows a team to:

- Review the proposed code changes.
- Add review comments and contribute to a discussion.
- Protect your mainline stream from unwanted changes, bad merges, and broken builds.
- Approve changes and merge them into a mainline.

A topic stream and its related pull request work together to help you manage and merge changes.

Micro Focus Pulse: using pull requests

### Rebase

If you have a topic and parent stream that both contain changes, and you want to update the topic stream with the changes from its parent, you can rebase the topic stream:

- Rebase updates the content of the topic stream with the tip of the parent stream (or an earlier version).
- Rebase merges the changes from the selected parent stream version, with all the changesets in the topic stream, into a single changeset on the topic stream.
- Rebase is simpler and quicker than merging the streams. The rebase is performed in the repository and not via the work area.

Rebase is particularly useful when development work on a topic stream is taking a long time and you want to test your code with the latest updates in the parent stream.

### Rehome

Rehome is a quick and easy way to switch a work area from one stream to another:

- Rehome fetches any required content into your existing work area so that it matches the stream you are rehoming to.
- Rehome avoids the need to fetch to a clean work area when switching to a different stream and is faster.

### Stream Merge

You can now merge streams without fetching the content into a work area. This automated server-side merge is used to merge the changes from a topic stream into its parent stream after changes have been reviewed.

## Micro Focus Pulse

- Pull requests enable you to review and merge sets of changes.
- New build expert plugins:
  - Ant
  - Gradle
  - MSBuild
  - Visual Studio Build
  - Makefile
- Other expert plugins have been updated.
- Dimensions CM product visibility rules are applied to Pulse where they can be scoped by a CM product.
- New distributed agent architecture for continuous integration and inspection.
- You can now set variables, used by experts, on agents and chains.
- Usability enhancements including a tabbed review page.
- Better visibility of chain runs in reviews and changeset pages.

For detail see the Pulse online help.

## Audit Trail

You can record logs of all commands that are executed in an audit log in the database. This is in addition to the existing file cmdLogfile.log. A new published view PCMS_AUDIT_LOG has been added to allow reporting. To enable this functionality uncomment the following line in the server dm.cfg file:

DM_AUDIT_CMD_DATABASE true

The following new commands have been added:

- OBJATTR: enables you to create and manage attribute definitions and assign them to specific object types.
- OBJTMPL: manages templates for the Request and Item object types.
- OBJTYPE: creates and manages Requests, Items, Baselines, Parts, and Projects object type definitions.

Operations performed in the administration console on object types, request and item templates, and attributes now execute these commands. This ensures that all operations are recorded in the audit command logs with the user name and date/time.

## Dimensions Build Installation

Dimensions Build is now an optional installation.

## OpenJDK

Dimensions CM now uses OpenJDK.

## Desktop Client and IDE Usability

- Desktop client:

- The Global Inbox is now called the User Inbox.
- The Global Catalog is now called the Product Catalog.
- New Reports menu.
- Many menus have been simplified and the submenu items reorganized.
- The layout of My Current Stream and My Current Project panels has changed. They now have groups such as Catalogs, Inboxes, Areas, and Sub-projects.
- You can display project and stream tabs at the top or bottom.

- Visual Studio integration: menus and commands are more consistent with the desktop client.

## User Name Field Length

The maximum length of the user name field has been extended from 25 to 64 characters.

# Installing and Upgrading

## Update Operating Systems

Apply the latest updates for your operating system.

On AIX you must install the latest version of the OS package: bos.rte.libc

On Windows you must install the following updates:

- KB2919442
- KB2919355

## Hardware Requirements

For details about hardware scaling requirements see the Architecture and Optimization Guide.

## Installation and Upgrade Instructions

For information about installing and upgrading, see these documents:

- Dimensions CM Installation Guide for Windows
- Dimensions CM Installation Guide for UNIX

Note There are now separate UNIX installers for servers, agents, and clients.

## Upgrading from Dimensions CM 2009 R2 and 12.x

To upgrade from Dimensions CM 2009 R2 or 12.x:

1. Run the Dimensions CM 14.5 installer.
2. Run the Versioned Repository Schema (VRS) upgrade utility to upgrade the data in your RDBMS.

To prevent issues with data that was created with a pre-14.1.x release of Dimensions CM, do the following:

- Deliver changes (streams) or check in items (projects) to your repository before upgrading to 14.5.
- Run the Update command after the upgrade to 14.x, this will also upgrade the meta data in your work areas.

The VRS upgrade retains all the existing project structure, project history, and baseline data. This avoids the need to upgrade all projects and baselines at once and ensures that an error during upgrade does not result in a loss of data. However, database size may increase dramatically as it contains both the old and new data. Before performing the upgrade you should increase the space allocated for PCMS_DATA by at least 50% and the space allocated for PCMS_IDX by at least 100%.

To prevent poor performance you must recompute database statistics after an upgrade. If you choose to perform a series of partial upgrades you must recompute statistics after each partial upgrade.

After all projects and baselines have been upgraded you can drop the tables containing the pre-upgrade data. Backup and create an export of these tables (or the entire database) before dropping them:

XII_WS_FILES

XII_WS_DIRS

XII_PSH_REQ_RELS

XII_PSH_PSH_RELS

XII_PSH XII_PREV_CHANGES

XII_PART_PART_RELS

XII_PART_ITEM_RELS

XII_MIGRATED_CHANGES

XII_ITEM_SETS

XII_DP_ITEMS_SETS

XII_BASELINE_ITEM_FILES

XII_BASELINE_ITEM_DIRS

## Upgrading Dimensions CM with CM SSO

If you are upgrading a Dimensions CM installation that is already configured to use the CM Single Sign On Server (SSO), do the following.

Note These steps are not required if the installation is configured to use Solutions Business Manager as the SSO server.

1. Stop the Common Tomcat.
2. Navigate to the Tomcat installation location.
3. Rename the lib folder to lib.pre145.
4. Rename the alfssogatekeeper folder to alfssogatekeeper.pre145.
5. Perform the upgrade.
6. After the upgrade has completed, navigate to the CM installation location. Check that all occurrences of the variable SSO_STS_ENDPOINT in <DM_ROOT>/dm.cfg contain the string localhost and not the host name of your machine.

## Upgrading Dimensions Connect for Solutions Business Manager (SBM)

You must uninstall previous versions of Dimensions Connect for SBM and then install version 14.5 before you upgrade the Dimensions CM server. For example, if you upgrade the Dimensions CM server to 14.5 you must also install Dimensions Connect for SBM version 14.5. If not the integration may not work as expected. See the Dimensions CM Connect for Solutions Business Manager User's Guide.

## Unable to Connect to Database

If an error message is displayed during installation stating that Dimensions CM is unable to connect to the database, do the following:

- Check that you have entered the correct database password and Oracle DSN if applicable.
- Check that the database used by Dimensions CM is active ("up"). Confirm that it is running, or that you can connect to it, using standard RDBMS database utilities such as sqlplus.

## Installing on Windows Server 2012R2 with Oracle 12

If you cannot install on Windows Server 2012R2 with Oracle 12, check the following:

- The system PATH contains ORACLE_HOME (this should be true if the system is restarted after installing Oracle). If ORACLE_HOME is not in the path the CM server installation will fail to validate the Oracle connection details.
- The Oracle administrator password does not contain a full stop (.), comma (,), or semicolon (;). If it does the CM server installer may fail to validate the Oracle connection details. Temporarily remove these characters from the password before installing.

## New Version of ALF Events Configuration File

During installation and upgrade a new version of the ALF events configuration file ($DM_ROOT/dfs/alf_events_config.xml) is installed for Pulse and your customizations are overridden. Your original file is backed up and you can merge your customizations into the new version.

## dmappsrv Process

In Dimensions CM 14.5 the dmappsrv process writes directly to the local item libraries. This revised access mechanism provides performance enhancements, improved security, and server scalability. Check that the Dimensions CM Pool User has permissions to read and write to all local item library directories. To find out who is the Pool User check the value of the parameter -user in dfs/listener.dat.

To disable this behavior, in the Dimensions CM server dm.cfg file set the variable DM_DISALLOW_DIRECT_LOCAL_LIBRARY_CHECKIN to Y and restart the Dimensions listener.

## Web Applications Library

For the dmwebservices2 web application the connectioncache library has been replaced with the Apache Commons Pool2 library. To change the setting for the pool:

1. Edit this file: webapps\dmwebservices2\WEB-INF\classes\generickeyedobjectpoolconfig.properties
2. Restart Tomcat.

The following configuration file is no longer used: webapps\dmwebservices2\WEB-INF\classes\connectioncache.properties

## Installing into a Remote SQL Server

If you are installing a CM server into a remote SQL Server, you must use an existing and pre-configured ODBC.

## Installing the Visual Studio 2017 Integration

A bug in earlier versions of Visual Studio 2017 may cause the installation of the CM integration to fail. Install the latest update to Visual Studio 2017 before upgrading to, or installing, the CM 14.5 clients.

## UNIX CM Server Upgrade Messages

You can safely ignore the following messages after you upgrade Dimensions CM and Deployment Automation on UNIX to 14.5:

com.installshield.sra.event.InstallScript, msg2, InstallScript.onReplacingcCoreFiles

com.installshield.sra.event.InstallScript, msg2, Tomcat was not found.

com.installshield.sra.event.InstallScript, msg2, InstallScript.onReplacingcCoreFiles

## Pulse Data Directory

The location of the Pulse data directory on a Windows server installation may vary:

- If you upgrade from a previous release to Dimensions CM 14.5, the data directory for Pulse does not change: \ProgramData\Serena\Pulse
- If you perform a new installation of Dimensions CM 14.5, the data directory for Pulse is: \ProgramData\Micro Focus\Dimensions CM\Pulse

## Git Connector Upgrade

You cannot upgrade previous versions of the Git Connector. Uninstall the old version and install version 14.5.

## DA not Supported on Oracle 18c and PostgreSQL

Deployment Automation is not supported on Oracle 18c and PostgreSQL.

## Tomcat JVM Heap Size

The Tomcat default minimum and maximum JVM heap sizes are -Xms640M and -Xmx1280M respectively. For Micro Focus Pulse, set both values to 4096.

UNIX:

1. Stop the Tomcat process: <tomcat-home>/bin/shutdown.sh
2. Open this file: <tomcat-home>/bin/setenv/sh
3. Update this line: CATALINA_OPTS="-Xrs -Xms4096M -Xmx4096M -Djava.awt.headless=true -Dorg.eclipse.higgins.sts.conf=$CATALINA_HOME/webapps/idp/WEB-INF/conf"
4. Restart Tomcat: <tomcat-home>/bin/startup.sh

Windows:

1. Stop the Micro Focus Tomcat service. Wait for the Tomcat process to exit.
2. Open a Command Prompt and run these commands (enter the correct path for your environment):

> cd /D "<Tomcat directory path>\bin"

> tomcat8.exe //US//MicroFocusTomcat --JvmMs 4096 --JvmMx 4096

3. Restart the Tomcat service.

## Micro Focus Pulse Help

The help in Micro Focus Pulse opens the online version, which is the most current. If you do not have internet access you can configure Pulse to open the help that is installed locally with the product.

1. Open the Pulse data directory.
2. Open the file startup.properties and add this line: branding.link.help.url=../cm-help/pulse/

# Limitations

The following features and functionality are not supported in Dimensions CM 14.5:

- Java on Solaris is no longer shipped.
- The upload and download migration utilities. Use the UPLOAD and DOWNLOAD dmcli commands instead. The standalone utilities are supported for backward compatibility.
- CM Bridge for Subversion does not support 'git-svn'.
- File encryption using DM_FILE_ENCRYPTION. Use SSL Secured SDP (SSDP) instead.
- You can use the HTTP Connector to log into remote work areas and perform operations. However, the network connection from a Dimensions CM server to a remote work area uses the Standard Dimensions Protocol (SDP).
- HTTP connector when the server is configured for SSL using the SSDP protocol.
- New SBM 11.2 attributes: URL and File
- DM_CONCURRENT_DELIVER_LOCK_MODE server symbol.
- DM_USE_OLD_CRB server symbol.
- SCC plug-in with Microsoft Visual Studio 2013 and later. Older versions of Microsoft Visual Studio may work with the DM_SCC_ENABLE configuration variable.
- UPDATE command: /NOEXECUTE qualifier
- UPDATE and DELIVER commands: /SCRIPTFILE qualifier
- Developer dm command-line client: updating a work area from a specific stream version (the tip is always used).
- Text meta data format (.metadata): automatically converted to binary metadata format (.dm) after work area update.
- ActivClient 7 with 32-bit Eclipse for CAC authentication. Use ActivClient 6 or 64-bit Eclipse.
- Serena Runtime RDBMS 12.1.0.2:
  - Serena Runtime RDBMS 12.1.0.2 may only be used on servers that have a maximum capacity of 2 sockets. When used with Oracle Real Application Clusters, Serena Runtime RDBMS 12.1.0.2 may only be used on a maximum of 2 one socket servers. Each Serena Runtime RDBMS 12.1.0.2 may use a maximum of 16 CPU threads at any time. When used with Oracle Real Application Clusters, each Serena Runtime RDBMS 12.1.0.2 may use a maximum of 8 CPU threads per instance at any time. The new 16 CPU thread cap is a technical limitation in the database program, not merely a contractual license limitation. Serena Runtime RDBMS 12.1.0.2 cannot utilize more than 16 threads at any time. On a typical Intel processor, each core contains 2 threads. For example, a 2- socket Intel-based server may contain two processors each having 10 cores, so the server has 20 threads in total (if hyper threading is enabled). Serena Runtime RDBMS 12.1.0.2 can utilize a maximum of 16 threads at any time.
  - The Serena Runtime RDBMS 12.1.0.2 is not certified on Windows Server 2016.

# Fixed Issues

For a list of all the fixes in this version see the Supportline Knowledgebase.

For a complete list of fixes in previous releases of Dimensions CM, go to the knowledgebase and select a CM version. You must have a user account to view items in the Knowledge Base. Register for a free account if you do not have already have one.

# Known Issues

## Installing Pulse Agents on UNIX

On UNIX you cannot install Pulse agents into locations that contain spaces, for example: /var/opt/Micro Focus/Pulse Agent/bin

## Rebasing Part of a Stream

If you are working with selected files or folders in a stream, and then rebase the stream, Micro Focus recommends that you do the following after the rebase:

- Delete the local work area.
- Get a fresh copy of the stream to the work area.

## Rehoming a Topic Stream from a Project

You cannot rehome a topic stream work area back to a project, only to another stream.

Workaround: delete your work area contents and refetch the project.

## Xcode and CM Bridge

Cloning from CM Bridge does not work using Xcode 9.x.

Workaround: clone using the svn checkout command and then import the project into Xcode.

## Dimensions Requirements Manager

If Dimensions CM is installed on the same machine as RM Manager you must use a Dimensions CM 14.4 or earlier client.

## dmpmcli on Solaris

dmpmcli on Solaris does not work as the installer does not provide a JRE.

Workaround: in the file $DM_ROOT/dmpmcli update the path in jre/bin/java to the correct value for your system.

## Dimensions CM/RM Integration

If you are using the Dimensions CM and RM integration, the length of the User login id field in RM is limited to 25 characters.

## Compiling PCMS_API Examples and Triggers

The client installers on all platforms do not have this file: pcms_api/dmdllsupport.h

To compile the PCMS_API examples or triggers, copy the file from a CM 14.5 server installation.

## GCC Compiler

(Solaris only) The PCMS_API example configuration files have not been updated to use the GCC compiler.

## Deployment Automation

- If you are using Deployment Automation (DA) instead of Dimensions CM deployment, and your Dimensions CM server is not running on Windows, please contact Support.
- If you installed DA as part of a CM agent installation on Windows, uninstalling CM may not delete the Deployment Automation folder.
- DA can prevent the shutdown of the Common Tomcat. If the Tomcat process persists after you attempt to shutdown, you can safely end the process manually.

## Reverting and Editing Deleted Files

If you revert a change to a work area and restore a file, before editing the file you must deliver it to CM. If you modify the file locally before committing the undo, the deliver operation reports a conflict.

## Upgrade dmpmcli

Previous versions of dmpmcli do not work with a Dimensions CM 14.5 server.

Solution: use dmpmcli version 14.5.

## Installing on AIX

If you run an AIX installation on a heavily loaded system, it may fail to exit cleanly, and hang while displaying this message: The Install Shield Wizard has successfully installed Dimensions CM 14.5 Choose Finish to exit the wizard. Press 3 to Finish or 5 to Redisplay [3]

Dimensions CM has been installed successfully and you can safely abort the installer.

## Microsoft Edge

To use Common Access Card (CAC) in Microsoft Edge, ActivClient version 7.1 (or later) must be installed.

## Wind River Workbench 3.3.x

Wind River Workbench version 3.3.x. does not work with this release of Dimensions CM.

Solution: Use the 14.1 version of the CM plug-in instead, however it does not support the new post 14.1 Dimensions CM features.

## Eclipse and Maven Integration Installers

The Eclipse and Maven integration installers on Windows Server 2012 R2 may fail with the following error: Installer User Interface Mode Not Supported

Solution: run the installers in compatibility mode.

1. Right-click the executable and select Troubleshoot compatibility.
2. Select Try recommended settings and accept the settings.

On Windows Server 2012 R2 and Windows 8.x the installers may still fail when run in compatibility mode and display this message: ZeroGu6: Windows DLL failed to load. This is caused by an incompatibility between the Java runtime embedded in the integration installers and recent versions of Windows. To resolve this problem install a 32-bit Java 7 or 8 runtime.

## Araxis Merge is not Registered

If you installed and uninstalled a trial version of Araxis Merge, the Dimensions CM instance of Araxis Merge may not be registered. Remove the expired license in the Windows registry by deleting the "SerialNumber" value under: HKEY_CURRENT_USER\Software\Araxis. The registration information provided by Dimensions CM will be used instead.

## Using Maven SCM with Java 9

In Java 9, JAXB classes have been removed. To avoid a runtime error, run the following command before running Maven:

set MAVEN_OPTS=--add-modules java.xml.bind

# Legal Notice

Copyright © 1988-2019 Micro Focus or one of its affiliates.

The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

##

Copyright © 1988-2019 Micro Focus or one of its affiliates.