Updates in Service Pack 1
With BMC Atrium Core 8.1.01, the following enhancements are now available:
BMC Configuration Drift Management
Starting with Service Pack 1, you can now install BMC Configuration Drift Management version 8.1. The BMC Configuration Drift Management is built on the BMC Remedy AR System and is a consumer of the configuration data that is discovered by your discovery applications and stored in your BMC Atrium CMDB. Using the configuration management data in your BMC Atrium CMDB, Drift Management focuses on the auditing, verification, and management of infrastructure changes in your data center IT environment. The Drift Management also integrates with other BMC applications, such as BMC Remedy Change Management and BMC Remedy Incident Management, to provide the initial steps toward the automation of data center operations. To understand Drift Management, see BMC Configuration Drift Management. For more details on installing Drift Management, see Installing BMC Configuration Drift Management.
BMC Configuration Drift Management provides support for the following platforms:
|OS Name||OS Version||OS Architecture|
|Red Hat Enterprise Linux||4||64-bit|
|SUSE Linus Enterprise Server||10||64-bit|
|Mac OS X||10.5||64-bit|
Graphwalk query performance improvement
The Graphwalk API is now redesigned such that it gives you a better performance for an environment that has a complex service model. With this enhancement the Graphwalk API can now work efficiently for dense graphs as well as sparse graphs. Consider an environment where you have Business services depending on multiple computers, which depend on several applications. In such an environment the Graphwalk query results will now be more robust and faster. To understand how the Graphwalk API works, see Graph walk query function overview.
Attribute added in the Common Data Model
BMC_BaseElement class a new attribute called
SystemEnvironment is added. If you have the BMC Remedy IT Service Management product installed, the Asset Management form uses the
SystemEnvironment attribute to distinguish the environment in which the CI is deployed (for example, production, development, QA and so on). If you have BMC ProactiveNet Performance Management (BPPM) installed and are using Atrium CMDB with this product, the
SystemEvnironment attribute is published in BPPM to support the BPPM Group Blueprint feature, which maintains BPPM groups and memberships.If you have BPPM reporting installed the
SystemEnvironment attribute is used to sort and filer reports by environment. It also helps in defining reporting hierarchy.
Deleting Reconciliation job runs information from forms
The job run entries are removed from the RE:Job_Runs and RE:Job_Events forms. Using the Job runs retained in history option available in the Reconciliation Engine console, Edit Job window you can delete the unwanted job run logs. This helps improve the Reconciliation engine console UI performance. To understand how to use this option, see Configuring the deletion of Reconciliation Engine job log files.
Reconciliation engine added support for purging the strong relationships
Prior to 8.1 Service Pack 1, the reconciliation engine used to exclude all the relationships during purge activity. As a result, if the relationship between the strong and weak CI got deleted then the weak CI would become orphan. To avoid such data integrity issues, relationships were excluded during purge. However, from Service Pack 1 onwards the strong relationship (as defined in Common Data Model) can be purged safely, without causing any data integrity issues. For details about this update, see Purging soft-deleted data by using the Reconciliation Engine.
Reconciliation engine version details
The Reconciliation Engine now maintains its version details in the arrecond.log file. The Reconciliation Engine version details are displayed in the a format: Reconciliation Engine 8.1 Service Pack 01. The version details are also maintained for Reconciliation Engine hot fixes provided.
In a Cloud or BMC Remedy IT Service Management (ITSM) environment you have multiple products with different versions working together. If you encounter an issue with Reconciliation Engine, the version details right up to the hot fix applied are available to you in the arrecond.log file. Thus allowing you to quickly provide the basic version details information to the BMC technical support and reduce the time to resolution.
This enhancement also helps us to catch situations where a hot fix meant for a higher version is applied on a lower version of the product. For example, if you are on BMC Remedy AR Systems and BMC Atrium Core version 7.6.04 Service Pack 1 and a Reconciliation Engine hotfix meant for version 7.6.04 Service Pack 2 is applied on Service Pack 1. Such situations are easy to identify because the version details displayed in the arrecond.log file are right up to the hot fix applied.
Reconciliation engine handles timeout errors
The reconciliation engine is now enhanced to handle the timeout errors seen in the reconciliation engine while connecting to the BMC Remedy AR Systems server. When the AR Systems server is busy, not responding, or down the reconciliation Engine no longer stops working. The reconciliation engine is enhanced such that when it receives a timeout error from AR Systems server, it waits for some time and tries to contact the AR Systems server again after a certain time delay. After the AR Systems server starts responding, the arrecond process goes down and the armonitor process restarts the arrecond process for the jobs to resume.
For example, if the arrecond process gets a timeout error from AR Systems server at 1.00 AM, it waits for 30 seconds and tries to restart the jobs at 1.00.30AM. If it still finds AR System server non-responsive, it waits and tries again after a delay of 60 seconds at 1.01:30 AM
Map currency value and type in different fields
You can map currency field separately by mapping the currency value or denomination to Currency Value field and mapping the type of currency (INR, USD etc.) to Currency Type field.
For more information, see Mapping currency field.