SMMapper Use Cases

8/2/2019 SMMapper Use Cases

1/19

1 PMSoft Partners Company Confidential

SMMapper Use Cases

Author: Patrick WolfVersion: 2.00


2/19


Table of Contents

Context of the White Paper ............................................................................................................. 2Use Case 1: Sharing Service models between HPUCMDB and BMC Atrium CMDB ................. 3

Step 1: Automated meta-model acquisition from the trusted data source .................................. 4Step 2: Intelligent graphical mapping user interface .................................................................. 5Step3: Scheduled or event triggered transformation ................................................................... 8Step 4: Service mapping control and adjustment phase.............................................................. 9

Use Case 2: Sharing Service models between HP UCMDB and HP Asset Manager .................. 10Associated Business Value Proposition .................................................................................... 10

Use Case 3: Maintaining a Service model .................................................................................... 14Associated Business Value Proposition .................................................................................... 14Use Case flow description ........................................................................................................ 15

Use Case 4: More complex transformation rules based on regular expressions........................... 17Associated Business Value Proposition .................................................................................... 18Use Case flow description ........................................................................................................ 18

Context of the White Paper

The intent of this document is to provide a functional description of PMSoft PartnersSMMapper in the context of several use cases PMSoft Partners is currently working onin conjunctions with our clients.

At this stage, SMMapper is mainly focusing on 4 main use cases, namely:

Service model sharing across managed data repositories Service model sharing within the HP portfolio

The maintenance of the service model

More complex transformation rules based on regular expressions

We are considering other use cases in the future, namely:

Service model cost computation

Service catalogues population


3/19


Use Case 1: Sharing Service models betweenHPUCMDB and BMC Atrium CMDB

Associated Business Value Proposition

Industrialization of the service mapping process

Reduced implementation time and costs for CMDB and CMS initiatives Improved configuration information data quality

Repeatable process

Less technical skills required

The intent of SMMapper is to propose a repeatable process to model, collect, integrate,and map Configuration items thru an easy to use & cross technology Service ModelStandardization tool - SM Mapper with the unique goal to reduce the time and efforts

to implement CMDB or CMS projects.

On a high level, SMMapper leverages a 4 step repeatable process to map externalmanaged data sources to the central service model stored within HPs leading UCMDB,namely:

Step 1: Automated meta-model acquisition from the trusted data source

Step 2: Intelligent graphical mapping user interface

Step3: Scheduled or event triggered transformation

Step 4: Service mapping control and adjustment phase


4/19


Step 1: Automated meta-model acquisition from the trusted datasource

SMMapper implements a mechanism to automatically extract the Meta models of thetrusted data sources in an automated manner in leveraging techniques ranging fromSOAP, REST web services, to SQL, and API accesses to the managed data sources.

SMMapper implements a concept of predefined connectors along with mapping contentpacks. Mapping content packs understand Meta models from several CMDBs and ITservice management software on the market including (but not limited) to:

HP UCMDB 8.x & 9.x from / to HP Service Manager HP UCMDB 8.x & 9.x from / to HP Asset Manager HP UCMDB 8.x from / to HP UCMDB 9.x HP UCMDB 8.x & 9.x from / to BMC Atrium CMDB 7.5 & 7.6 HP UCMDB 8.x & 9.x from / to CA CMDB r11 & r12 HP UCMDB 8.x & 9.x from / to IBM CCMDB

HP UCMDB 8.x & 9.x from / to Service Now HP UCMDB 8.x & 9.x from / to ASG - metaCMDB HP UCMDB 8.x & 9.x from / to Altiris HP UCMDB 8.x & 9.x from / to Symantec Command Central HP UCMDB 8.x & 9.x from / to Tivoli inventory HP UCMDB 8.x & 9.x from / to Troux Technologies HP UCMDB 8.x & 9.x from / to Alphabet


5/19


In case managed data sources are not yet understood out of the box by SMMapper, anintuitive integration technology is in place for end users to build their own mappingcontent via integration SDK.

Step 2: Intelligent graphical mapping user interface

Once the Meta model has been extracted from the managed data sources, this one isprocessed by SMMapper and a very intuitive tree view is displayed.

This tree view is containing a very user friendly way of representing complex Metamodels, as illustrated bellow:


6/19


In the example on top, SMMapper is mapping information from HP UCMDB on the leftside to BMC Atrium CMDB on the right side of the screen.

This process allows a configuration manager or a service manager to create anintermediate scope by dragging classes from the source or destination to theintermediate scope (center tree view). The intermediate scope will be leveraged by the

software to transform the data.

Once classes have been mapped, the user gets access to another screen allowingmapping attributes for each of the selected classes (Ie. Computersystem and Memory inour example):


7/19


Note: The complete syntax for HPs TQL is supported including Constant, Direct, andCompound string transformations.

And finally, the user gets the ability to map relations from HP UCMDB to BMC AtriumCMDB. As SMMapper understands the complete meta model, these relations aregenerated automatically, it is up to the user to select the relevant one.


8/19


Step3: Scheduled or event triggered transformation

SMMapper is literally plugged on top of HP UCMDBs integration studio and a TQL fileis generated out of the mapping the user interface produces in step 2.

This TQL mapping file is consumed by the standard HP UCMDB to BMC Atrium CMDBpush adapter and avoids the process of writing mapping files between HP and BMCmodels.

As a result, the mapping process is highly simplified and the time to implement complexmapping reduced to the minimum.

Two modes of execution are available, a scheduled mode or an event triggered mode inwhich an external tool triggers a transformation job in calling the SMMapper web serviceREST API.

The illustration underneath highlights SMMapper working as service modelorchestration engine between HP UCMDB and BMC Atrium CMDB.


9/19


Step 4: Service mapping control and adjustment phase

Finally, once the transformation of the data is effective, the system allows the end user tocontrol the accuracy of the data and tweak the mapping and/or transformation rules whennecessary.

Other key features


10/19


Use Case 2: Sharing Service models betweenHP UCMDB and HP Asset Manager


Industrialization of the service mapping process Reduced implementation time and costs for CMDB and CMS initiatives Improved configuration information data quality Repeatable process

Less technical skills required


11/19


The goal for this use case is to generate configurations files that are compatible with theAsset Manager Adapter (Ie. AMAdapter). The AMAdapter is part of HP UCMDB contentpack 10 and leverages the generic DB adapter.

Note: A combination of SQL approach and the parsing of a database descriptionfiles are leveraged to extract the model and meta model structure out of HPAsset Manager.

The following structure is displayed to the user including the HP UCMDB modelon the left side discovered thru web services and the Asset Management modelon the right side:


12/19


At this stage, the user is allowed to map classes from HP UCMDB to HP Asset

Manager.

The next step in the workflow consists in the mapping of attributes related to theclasses that were mapped in the previous section.


13/19


Note: in this section, we are creating a direct mapping between the nt /

primary_dns_name in UCMDB and amAsset / Fullname in Asset Manager.

Once this step achieved, AMAdapter configuration files are generated basedupon the intermediate scope that was selected by the user.

Upon selection of an existing or new Asset Manager query within the HP UCMDBintegration studio, a job is executed to push information from HP UCMDB to HP

Asset manager.


14/19


Use Case 3: Maintaining a Service model


Provides automation in the maintenance of the service model less manualintervention


Reduced implementation time and costs for CMDB and CMS initiatives Improved configuration information data quality

Repeatable process Less technical skills required

This use case consists in automating the maintenance of a service model. Indeed,SMMapper is able to capture any modification to the HP Asset Manager meta model inan automated manner and reflects these changes to the master service model that ismaintained within HPs UCMDB.

In other words, SMMapper is able to understand meta model changes for any manageddata repositories connected to the master HP UCMDB and reflect these changes in anautomated manner to the core service model.

Maintaining service models is one of the most complex and time consuming tasks asthese ones are generally undertaken manually based in a configuration managementprocess.


15/19


Use Case flow description

Workflow sequence

The follow sequence is automated thru the use of SMMapper.

In this use case, SMMapper discovers the HP Asset Manager model and metamodel using a combination of SQL access and the parsing of some databasedescription files.


16/19


Initially, a modification is occurring within the HP Asset Manager Meta model. Asan example, a new type of asset is added to Asset Manager (Ex. a virtual

system).

SMMapper automatically captures the difference in the meta model and the useris allowed to compare the difference between two snapshots as highlightedbelow:

The following result is displayed to the user:


17/19


The user is finally allowed to drag and drop these artifacts from the comparisonwindow to the UCMDB tree view. The system via web services sets the newmeta model structure within the HP UCMDB and HP s UCMDB is getting updatedautomatically with the new VirtualSystem class.

As SMMapper is fully web services enabled, the automated service modelupdate could very well be tied to change management process. Changes withinthe managed data sources would be reflected to the core configurationmanagement system in a transparent manner as long as this change has beenapproved or pre-approved.

Use Case 4: More complex transformationrules based on regular expressions

In this use case SMMapper is leveraged to implement more complex transformation on flyfor configuration information that has previously been discovered b DDMa and is residingwithin HPs UCMDB.

A simplified workflow is described here:

MQ Series management configuration data previously discovered thru DDMa isextracted by SMMapper from HPs UCMDB via web services

The configuration data is transformed on the fly using SMMapper mapping

studio regular expression capabilities The transformed MQ Series data is reintegrated within HPs UCMDB via web

services


18/19




Reduced implementation time and costs for CMDB and CMS initiatives

Improved configuration information data quality Repeatable process Less technical skills required

Use Case flow description


19/19


Functional sequence:

A new Data Source is created within SMMapper pointing to the HPs UCMDBthat is hosting the MQ series data.

A tree view is displayed within SMMapper displaying the data structure related tothe MQ Series Data Source. Typically a queue manager linked to severalqueues.

The user selects the type of MQ series data he is intending to retrieve. Ex. MQManager and MQ queues.

For each Queue Managers and queues pulled from the UCMDB, a new attributeis created and instantiated by SMMapper in leveraging the regular expressioncapabilities. As an example, 3 first characters of the queue name. system name.

A new type of relation (ex. impact relation) is created based upon the newattribute created in the former section.

The existing web service adapter between SMMapper and HP UCMDB isleveraged to set the new structure and the associated data within HPs servicemodel.

Date post:	05-Apr-2018
Category:	Documents
Upload:	ivica-raguz
View:	219 times
Download:	0 times

SMMapper Use Cases

Documents