New Integration Between HP Service Manager v9.30 and HP uCMDB v9.05

Posted by Rob Swingle  I  May 20, 12

On May 8th, 2012, I attended a very good webinar/demo covering the new integration between HP Service Manager v9.30 and HP uCMDB v9.05. There were over 400 people from around the world on the meeting and the speakers included the HP uCMDB Product Manager and a member of the HP Service Manager Research & Development Team.

It is always good to hear straight from the minds who are creating the applications you work with when it comes time for new releases and enhancements. I was thrilled to get a sneak peak at the latest and greatest, and to learn of the trends that are coming down the uCMDB pipeline to our customers.

hp specialist logo

The meeting opened with the reasons why the SM-UCMDB enhancements are being made:

  1. ITSM applications customers are unable to leverage HP UCMDB capabilities and new features due to an insufficient integration of the tools.
  2. There is a need in the market to build competitive strength. Major competitors have better integrations via a single-platform architecture.
  3. HP has heard the feedback from its customers and wants to deliver highly desired application integration enhancements.

With the reasons out of the way, we continued in to the guts of the presentation and the specifics of the enhancements to the integration.

First, the presenters covered the "enriched CI and CI relationship mapping for UCMDB and SM synchronization." They explained how the out-of-box integration content has been enriched to support more CI and CI Relationship types and subtypes for UCMDB to SM synchronization. This should reduce the effort needed to implement the integration for most customers. Example new types and subtypes include:

  • Running software
  • Switch
  • Storage
  • Mainframe
  • Network component
  • Mobile device

Another new enhancement is the improved error handling for the UCMDB-to-SM synchronization. Now, a single CI failure will not fail a complete push (UCMDB to SM). Instead, the push job completes with a "Passed with failure" status. Then, once the failed records are corrected, they can be re-pushed. This should speed up the data sync process and allow for simple error correction at the end.

Also, additional Device Event Manager (DEM) rule options have been made available for duplicate logical name values. Previously, CI's with a duplicate logical name would fail the whole job, however, now, DEM rules can be configured on the "Duplication Rule" tab to either rename the duplicate record or return an error for the failed CI. The whole job will then continue on to the next record. Errors can then be resolved at the end manually and data flow will not be interrupted.

Here is an enhancement that has been sorely needed... when data is pushed from UCMDB to SM, the "outage dependency relationship data" will also be synched. Previously, this data was lost during the push, but now, DEM rules can defined to maintain the outage dependency information.

Want to delete a CI from your database, but want to keep the record alive for future use, like reporting? In the new integration, you can now mark a CI as "decommissioned", and the record will be kept... no need for a full deletion then in order to keep your data accurate.

This next enhancement was the favorite of the audience by far. The new integration will be multi-thread capable. The SM adapter can connect to multiple Service Manager instances for parallel processing of data. The processing speed of the data push is therefore greatly improved.

The final enhancement allows for your previous data cleanup work to be remembered chronologically. When running a full data push from UCMDB to SM, if there are CI's that have been deleted since the last data push, the adapter will first send all pending deletions to SM. Once done with that step, the full push will then be started. Because of this new feature, you no longer have to worry about your prior work being overwritten between push cycles. Very nice.

So, this was the end of the part of the presentation that covered the major enhancements. Time to look at versioning now in order to take advantage of these new features.

Ideally, the client should be using:

  • HP Service Manager v9.30 or later + UCMDB Integration Content Pack v9.30.0 or later
  • UCMDB v9.05 or later

The UCMDB Integration Content Pack is compatible with 2 previously released application packages that can be used on top of v9.30 of HP Service Manager. They are the SM 9.30 Applications Patch 1 and the SM Process Designer Content Pack 9.30.0. If either of these 2 packages needs to be installed, they should be installed before the UCMDB Integration Content Pack is installed.

Want a copy of the presentation I attended for yourself? Get it here:


I would love to hear your thoughts on this integration! Please leave a comment below!

Tags:  HP, HP Service Manager