19.02 enhancements

This section contains information about enhancements in the version 19.02 of BMC CMDB.

Additional Remedy ITSM 19.02 enhancements Open link

BMC CMDB enhancements

The following sections provide information about the enhancements in the 19.02 release.

Support for Java 11

Remedy platform and applications now support higher versions of Java and Remedy 19.02 release is certified to be compatible with Oracle Java 11. Due to changes in Oracle's Java release and support strategy, Remedy also supports OpenJDK 11. Remedy does not support Java version 9 and 10 because these Java versions are not supported by Oracle.

Similar to the earlier versions of Remedy, during installation of the Remedy AR System platform software, you can configure a compatible 64-bit Java software environment that is to be used by the Remedy environment.

Remedy 19.02 release also provides backward compatibility for applications that still use Java 8.

For information about the known issues when upgrading Remedy by using Java 11, see Application installation and upgrade known and corrected issues Open link .

Ability to archive CMDB data

You can now remove obsolete data from production datasets in your CMDB, and store them in an archive form for future reference. The CMDB archive feature is an extension of the core AR System Archiving functionality and is enabled for the out-of-the-box Common Data Model (CDM) and CDM Extensions that you define by using the Class Manager utility. The benefits of archiving include improving performance, reducing overall footprint, and storing data for historical purposes.

For more information, see Archiving CMDB data.

Create and edit CIs by using CMDB Explorer

Continuing with the CMDB Dashboard User Experience implementation, you can now create new CI instances and relationships, and edit existing information from the CMDB Explorer.

For more information, see Working with CIs and relationships.

What else changed in this release

In this release, note the following significant changes in the product behavior:

Update	Product behavior in versions earlier than 19.02	Product behavior in version 19.02
Remote execution of jobs and transformations in Spoon.	You cannot perform remote execution of jobs and transformations in Atrium Integrator Spoon.	You can now perform remote execution of jobs and transformations in Atrium Integrator Spoon. For more information, see Running a transformation job in Atrium Integrator Spoon.
Additional attributes to perform cost modeling.	You cannot use relationship data to identify the flow of cost and apportionment.	You can now use the following new attributes in the `BMC_BaseRelationship` class to allow for cost modeling: The `CostFlow` attribute enables you to identify directional flow of cost whether it flows upstream or downstream or is NULL. The `CostApportionment` attribute enables you to identify the percentage of source CI cost that is to be shared by the related item or service. For more information, see Summary of changes to the Common Data Model.
Additional attributes to add a detailed location to a location relationship.	You cannot add attributes to the location relationship to store detailed location information.	You can add very specific and detailed location information to the location relationship. For example, if the location CI is `Datacenter Denver`, it has attributes for elements such as floor, row, rack, and shelf that can be be stored as part of the relationship. For more information, see Summary of changes to the Common Data Model.
Handling large data in CMDB Explorer	If a graph containing more than 500 CIs was displayed in CMDB Explorer, the application expanded the graph and displayed all the CIs at once, resulting in slow performance.	If a graph containing more than 500 CIs was displayed in CMDB Explorer, you can choose to either display only the selected CI in the CMDB Explorer or display all the results, which includes two levels of CIs. But, this may result in slow performance.
Default archival of older UDM jobs execution or job log data forms for better performance of Atrium Integrator.	Sometimes, Atrium Integrator experienced slow performance when loading Atrium Integrator or UDM (Unified Data Model) jobs execution forms or job log data forms. This was due to an accumulation of job logs that are created on every job execution and eventually slowed the performance of the job log forms.	Default archival policies are defined in the AR System Archive Manager Console to archive accumulated UDM job logs and UDM transformation logs. For more information, see Improving the performance of Atrium Integrator
Normalization options when starting a normalization job.	When starting a job using the Start Job option in the Normalization Jobs page, there are no options to override the Normalize all instances check box in the Default Dataset Normalization section in the page.	When starting a job using the Start Job option in the Normalization Jobs page, the following options are available that can override the Normalize all instances check box setting in the core configuration settings for normalization: Default or Normalize Delta - Normalizes only those CIs that were added after the previous normalization job was run. Normalize all instances - Normalizes all CIs irrespective of the configurations.