Dimensions CM 14.5 Release NotesThese release notes contain important information about Dimensions CM 14.5. Last updated April 8, 2019.
Dimensions CM 14.5 Release NotesThese release notes contain important information about Dimensions CM 14.5. Last updated April 8, 2019.
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 Dimensions CM before installing this version.
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.
For specific Dimensions CM issues contact Support.
Additional technical information or advice is available from several sources:
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.
New features have been added to streamline:
For full details see the Dimensions CM User's Guide.
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.
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:
A topic stream and its related pull request work together to help you manage and merge changes.
Micro Focus Pulse: using pull requests
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 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 is a quick and easy way to switch a work area from one stream to another:
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.
For detail see the Pulse online help and the Micro Focus Pulse Agent Installation and Configuration Guide.
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:
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 is now an optional installation.
Dimensions CM now uses OpenJDK.
The maximum length of the user name field has been extended from 25 to 64 characters.
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:
For details about hardware scaling requirements see the Architecture and Optimization Guide.
For information about installing and upgrading, see these documents:
Note There are now separate UNIX installers for servers, agents, and clients.
To upgrade from Dimensions CM 2009 R2 or 12.x:
To prevent issues with data that was created with a pre-14.1.x release of Dimensions CM, do the following:
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
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.
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.
If an error message is displayed during installation stating that Dimensions CM is unable to connect to the database, do the following:
If you cannot install on Windows Server 2012R2 with Oracle 12, check the following:
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.
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.
For the dmwebservices2 web application the connectioncache library has been replaced with the Apache Commons Pool2 library. To change the setting for the pool:
The following configuration file is no longer used: webapps\dmwebservices2\WEB-INF\classes\connectioncache.properties
If you are installing a CM server into a remote SQL Server, you must use an existing and pre-configured ODBC.
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.
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
The location of the Pulse data directory on a Windows server installation may vary:
You cannot upgrade previous versions of the Git Connector. Uninstall the old version and install version 14.5.
Deployment Automation is not supported on Oracle 18c and PostgreSQL.
The Tomcat default minimum and maximum JVM heap sizes are -Xms640M and -Xmx1280M respectively. For Micro Focus Pulse, set both values to 4096.
UNIX:
Windows:
cd /D "<Tomcat directory path>\bin"
tomcat8.exe //US//MicroFocusTomcat --JvmMs 4096 --JvmMx 4096
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.
The following features and functionality are not supported in Dimensions CM 14.5:
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.
On UNIX you cannot install Pulse agents into locations that contain spaces, for example: /var/opt/Micro Focus/Pulse Agent/bin
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:
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.
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.
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 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.
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.
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.
(Solaris only) The PCMS_API example configuration files have not been updated to use the GCC compiler.
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.
Previous versions of dmpmcli do not work with a Dimensions CM 14.5 server.
Solution: use dmpmcli version 14.5.
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.
To use Common Access Card (CAC) in Microsoft Edge, ActivClient version 7.1 (or later) must be installed.
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.
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.
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.
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.
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
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.