SMS2CMDB Project Summary v1.6

Transcription

1 SMS2CMDB Project Summary v1.6 Project Abstract SMS2CMDB provides the capability to integrate Microsoft Systems Management Server (MS- SMS) data with BMC Atrium CMDB (Atrium CMDB) and the BMC Remedy Asset Management Application (Asset Management). Microsoft Systems Management Server 2003 (MS-SMS) is a change and configuration management solution for the Microsoft platform. Several key components are included to streamline the management of Windows based systems including application deployment, asset inventory and security patch management. Organizations who have implemented MS-SMS have insight in to the assets deployed on their network and can efficiently deploy software and patch updates to these systems. Primary Benefits of SMS2CMDB Automated Accurate Inventory Without an automated update system, asset repositories notoriously have incorrect and outdated information. Because the MS-SMS integration updates asset and component configuration item records with any changes, the asset repository is as current as the last time the integration ran to update information. Improved Ability to Support IT Assets MS-SMS computer system and component inventory data integrated with BMC Atrium CMDB (Atrium CMDB) and BMC Remedy Asset Management Application (Asset Management) provides your help desk with the up-to-date, detailed configuration information it requires for effective troubleshooting. Even if an organization already had MS-SMS, it is sometimes cryptic to find the necessary information to resolve an issue, not to mention the need for the technician to move between multiple applications. With the integrated data, the technician can easily and effectively review the configuration of a given system without needing to leave the Remedy application. Easy Integration SMS2CMDB Integration is a separately distributed add-on to Atrium CMDB. Once the SMS2CMDB Integration is installed, the BMC Remedy Action Request System (AR System) Administrator can enable BMC Remedy Enterprise Integration Engine (EIE) to load MS-SMS inventory into Atrium CMDB with basic computer hardware information. An additional software component is utilized to collect and load software package information. When the data is submitted or modified, workflow normalized certain information to fit inventory norms for expression of memory and disk size. Then, loaded data can be merged in to the Asset Management dataset utilizing included reconciliation rules. These reconciliation rules server as examples and will probably require additional rules to merge with your legacy asset data. Software Inventory Management The SMSSync Integration is a separately installable and configurable component of the overall SMS2CMDB solution. It is a separate Java program which can be leveraged to support the integration of software package information into the Atrium CMDB. The SMSSync utilizes the Definitive Software Library (DSL) to both normalize and control the information that is loaded into the CMDB. Additionally, software packages can be individually identified for inclusion in the CMDB allowing users to control the number of software packages transferred. SMS2CMDB Project Summary Page 1

2 Integration Summary SMS2CMDB provides a method of creating and maintaining assets and their components from data stored in the Microsoft SQL Server (MS-SQL) database used by MS-SMS. The integration system utilizes BMC Remedy Link for SQL Server (Remedy Link for SQL) and the EIE to transfer data from the MS-SMS tables to AR System based applications. Out of the box, this integration system allows for the automatic creation of configuration items in the Atrium CMDB in an MS-SMS data set and reconciliation with the Asset Management data set. Any changes to the systems, components or software created using this integration system will be automatically reflected in the Atrium CMDB and Asset Management application if present. For Organizations that have purchased Atrium CMDB without Asset Management, a separate installer is included. This solution can easily be modified to work with custom asset applications, which have been built around the concept of an asset (parent form) and a component (child form) topology. System Requirements The following Microsoft software and BMC software products must be installed and operating correctly prior to the integration: BMC Remedy Action Request System 7.0 or later BMC Atrium CMDB 2.0 BMC Remedy Asset Management 7.0 (optional) Remedy Link for SQL Server (includes Enterprise Integration Engine) Microsoft Systems Management Server 2003 JRE or greater Detailed BMC Remedy product requirements and supported platforms can be found at Integration Details Installation Installation of SMS2CMDB is comprised of the following: 1. Import the EIE configuration, Atrium CMDB configuration, reconciliation rules and data cleansing filters, by running the included installation scripts. 2. Modify the EIE configuration to use the logon information for your site. 3. The reconciliation rules are by default set up for use with Asset Management. If Asset Management is not present, you will need to reconfigure or disable these rules. 4. Purge rules are shipped but disabled. These rules should be reviewed and enables as applicable. 5. If software integration is desired, SMSSync should be installed and configured. For additional details, see the SMS2CMDB Integration Guide, found in the integration zip file. SMS2CMDB Project Summary Page 2

3 Integration Components SMS2CMDB involves multiple products and operational steps. The interactions involved are illustrated in the table below. MS-SMS inventory data resides in an MS-SQL database. The Remedy Link for SQL product, including EIE, is used to copy the data in the Atrium CMDB. From the Atrium CMDB a set of cleansing filters and reconciliation engine rules are used to copy the date and expose it data via Asset Management. Details of each step follows. Enterprise Integration Engine (EIE) EIE has three primary components: the Service, the SQL Adapter and the Data Exchange Application (DEA) The Service The EIE service controls the activity between the AR System server and MS-SQL. The service reads the instructions from the DEA and executes them through the MS-SQL Adapter. This is how AR System servers installed on other databases can communicate with the MS-SQL database that stores the MS-SMS data. The SQL Adapter The SQL Adapter is used to communicate to the SQL database on behalf of the service. The Service will make requests of the adapter; the adapter carries out these requests and passes the results back to the service. The Service then updates the Remedy forms appropriately. The Data Exchange Application The DEA can be installed on any supported AR System. It is the EIE Application with forms and workflow that are used to configure the integration between MS-SMS and the AR System server. The Field Mappings, Relationship Mappings, schedule and description of qualifying data is included in this configuration. Mappings included in the integration are listed in Appendix A. SMSSync Software Loader The SMSSync component of the integration is a java executable process built on the BMC Remedy AR System JAVA API. It connects to the SMS backend SQL database just as EIE does and loads data through the BMC Remedy API. Additional filtration is performed by the utility to enable software of interest to be sorted from the high volume of software which is not licensable or merely components to other licensable applications. This utility is required to perform transformation during the data loading process for software CIs which cannot be performed by EIE. The SMSSync utility leverages the DSL in order to normalize software data and control the software items under management. SMS2CMDB Project Summary Page 3

4 The DSL The Definitive Software Library (DSL) is a central repository of approximately 10,000 approved product dictionary entries (PDEs). PDEs are the definitive, or master, names and descriptions of software applications. Any BMC application, and any third party product, can use the DSL to identify a single name for a software application and its versions, which in turn supports software license compliance. PDEs are made up of Software Library Items (SLIs), which are the physical locations of where the master copies of the software applications and their versions are stored. Atrium CMDB Atrium CMDB is the repository for all configuration data used by BMC Remedy applications, including Asset Management. Certain configuration items and workflow for use with Atrium CMDB have been included in the integration. SMS Dataset By default, entries created via the Asset Management user interface are in the data set BMC.ASSET. This integration creates a dataset MS.IMPORT.SMS. All records created via this integrations are created with the dataset ID = MS.IMPORT.SMS. This allows reconciliation between the MS-SMS data set and the Asset Master data set to be done with the reconciliation rules rather than which ever method was last written overwriting all like data from the other method. Data Cleansing MS-SMS stores Total Physical Memory as Kilobytes. This precision leads to values such as , , etc. As humans, we expect to see 128 MB. This not only is confusing, it makes defining a search to show all systems with 128 MG of memory nearly impossible. In a similar manner, Total Disk Size is listed in Kilobytes and leads to similar confusion. Filters have been written to normalize this data from MS-SMS before there is an attempt to reconcile with the Asset Management data set. Reconciliation The Reconciliation Engine allows Remedy data administrators to create rules for how to identify duplicate records and the action to take when duplicates are found. What normally constitutes a duplicate is when the information is entered in to the Atrium CMDB from multiple sources. Additionally, reconciliation must be done between the imported/updated data and the golden data set. Reconciliation between any two data sources is going to be a case by case exercise because there are no industry standards for how to express every attribute of a computer system. Because it is unknown what the source of the data is in the Asset Management golden data set is or how it was entered manually the rules included with this integration are to be considered samples. The sample job reconciles the data set MS.IMPORT.SMS with the dataset BMC.ASSET. Purge When systems are no longer reporting in MS-SMS, routines remove the data from the MS-SMS database. The configured exchanges will then mark the corresponding entries in the Atrium CMDB as no longer valid. Once reconciliation rules have run to pass this information to the golden data set, BMC.ASSET, it is no longer necessary to maintain the SMS data in the MS.IMPORT.SMS data set. Purge rules have been defined to clean up these entries which are no longer useful. In most situations, you will want to run the purge rules as it will speed the comparison operation between the SMS database and the MS.IMPORT.SMS data set in Atrium CMDB. Out of the box, these purge rules are disabled. These rules should be reviewed and implemented in accordance with your corporate procedures. SMS2CMDB Project Summary Page 4

5 Asset Management Asset Management stores information about assets in the Atrium CMDB. The Asset Management application then acts as the presentation layer and workflow engine to manage the asset data. This integration brings the MS-SMS information into the Atrium CMDB and via the reconciliation process in to the asset master data set.. SMS2CMDB Project Summary Page 5

6 Sample Scenario The following is only a sample of the scenarios where MS-SMS could be utilized in an IT Management environment where Atrium CMDB and Asset Management are implemented. It is assumed that each installation will have specific requirements that apply specifically to the needs of the organization. Asset Population The IT Department has just implemented Asset Management. They are required to gather detailed information about IT assets that are currently on the network and use that information to populate Asset Management. To accomplish the goal, they install and deploy MS-SMS, then install and run the integration. Asset inventory is automatically populated to the Atrium CMDB and visible from Asset Management forms. As changes are detected by MS-SMS, the MS-SMS database is updated. The delta data is used to update Asset Management the next time the integration runs. Data is now available for managing the assets in the organization including full lifecycle management and as an aid to support technicians who can view the asset information related to help desk issues and change management requests. Asset Reconciliation The IT Department has implemented Asset Management and populated the Atrium CMDB with asset data from various sources including other integrations and input by hand. None of these methods has been kept current or checked for accuracy. MS-SMS has been in operation but never integrated with the Asset Management application. The integration is installed and asset inventory is automatically populated to the Atrium CMDB. Reconciliation rules are then implemented to reconcile the existing data set with the MS-SMS data set. By analyzing the results of data reconciliations the asset management group can assure that all systems that should be on the network are reporting, that no leased equipment that was to have been returned is still on the network and data input errors are corrected. SMS2CMDB Project Summary Page 6

7 Appendix A: Data Dictionary Computer System SMS.V_R_System.Resource_ID SMS.v_R_System.Resource_Domain_OR_Wo rkgr0 BMC.CORE:BMC_ComputerSystem.SMSParentID BMC.CORE:BMC_ComputerSystem.DataSet BMC.CORE:BMC_ComputerSystem.Domain SMS.v_R_System. Name0 System SMS.v_GS_System_Enclosure.SerialNumber 0 SMS.v_GS_Computer_System.Model0 SMS.v_GS_Computer_System.Manufacturer 0 SMS.v_GS_X86_PC_Memory.TotalPhysicalM emory0 SMS.v_GS_PC_BIOS.Name0 BMC.CORE:BMC_ComputerSystem.Name BMC.CORE:BMC_ComputerSystem.Category BMC.CORE:BMC_ComputerSystem.Type BMC.CORE:BMC_ComputerSystem.Item BMC.CORE:BMC_ComputerSystem.Serial_Numbe r BMC.CORE:BMC_ComputerSystem.Model BMC.CORE:BMC_ComputerSystem.Manufacturer Name BMC.CORE:BMC_ComputerSystem.Total Physical Memory BMC.CORE:BMC_ComputerSystem.firmware_vers ion BMC.CORE:BMC_ComputerSystem.Submitter BMC.CORE:BMC_ComputerSystem.Short Description BMC.CORE:BMC_ComputerSystem.AssetLifecycle Status 0 BMC.CORE:BMC_ComputerSystem.Reconciliatio nidentity SMS2CMDB Project Summary Page 7

8 Disk Drive SMS.vGS_Logical_Disk.ResourceID BMC.CORE:BMC_DiskDrive.SMSParentID BMC.CORE:BMC_DiskDrive.DataSet SMS.vGS_Logical_Disk.GroupID BMC.CORE:BMC_DiskDrive.SMSChildID BMC.CORE:BMC_DiskDrive.Category BMC.CORE:BMC_DiskDrive.Type Logical Disk BMC.CORE:BMC_DiskDrive.Item BMC.CORE:BMC_DiskDrive.AssetLifecycleStatus SMS.vGS_Logical_Disk.DeviceID0 BMC.CORE:BMC_DiskDrive.Name SMS.vGS_Logical_Disk.DeviceID0 BMC.CORE:BMC_DiskDrive.PNPDeviceID SMS.vGS_Logical_Disk.Size0 BMC.CORE:BMC_DiskDrive.Size BMC.CORE:BMC_DiskDrive.Submitter BMC.CORE:BMC_DiskDrive.Short Description 0 BMC.CORE:BMC_DiskDrive.ReconciliationIdentity CD ROM Drive SMS.vGS_CDROM.ResourceID BMC.CORE:BMC_CDROMDrive.SMSParentID BMC.CORE:BMC_CDROMDrive.DataSet SMS.vGS_CDROM.GroupID Optical Drive SMS.vGS_CDROM.Manufacturer0 Removable Media SMS.vGS_CDROM.Manufacturer0 + SMS.vGS_CDROM.MediaType0 BMC.CORE:BMC_CDROMDrive.SMSChildID BMC.CORE:BMC_CDROMDrive.Category BMC.CORE:BMC_CDROMDrive.Type BMC.CORE:BMC_CDROMDrive.Item BMC.CORE:BMC_CDROMDrive.Status BMC.CORE:BMC_CDROMDrive.ManufacturerName BMC.CORE:BMC_CDROMDrive.MediaType BMC.CORE:BMC_CDROMDrive.Name BMC.CORE:BMC_CDROMDrive.Submitter BMC.CORE:BMC_CDROMDrive.Short Description 0 BMC.CORE:BMC_CDROMDrive.ReconciliationID SMS2CMDB Project Summary Page 8

9 Monitor SMS.vGS_DESKTOP_MONITOR.ResourceID BMC.CORE:BMC_Monitor.SMSParentID BMC.CORE:BMC_Monitor.DataSet SMS.vGS_ DESKTOP_MONITOR.GroupID Monitor SMS.vGS_ DESKTOP_MONITOR.MonitorManufacturer0 SMS.vGS_ DESKTOP_MONITOR.Name0 SMS.vGS_ DESKTOP_MONITOR.PixelsPerXLogicalInch0 SMS.vGS_ DESKTOP_MONITOR.PixlesPerYLogicalInch0 SMS.vGS_ DESKTOP_MONITOR.ScreenHeight0 SMS.vGS_ DESKTOP_MONITOR.ScreenWidth0 BMC.CORE:BMC_Monitor.SMSChildID BMC.CORE:BMC_Monitor.Category BMC.CORE:BMC_Monitor.Type BMC.CORE:BMC_Monitor.Item BMC.CORE:BMC_Monitor.Submitter BMC.CORE:BMC_Monitor.Short Description BMC.CORE:BMC_Monitor.ManufacturerName BMC.CORE:BMC_Monitor.Name BMC.CORE:BMC_Monitor.AssetLifecycleStatus BMC.CORE:BMC_Monitor.PixelsPerXLogicalInch BMC.CORE:BMC_Monitor.PixlesPerYLogicalInch BMC.CORE:BMC_Monitor.ScreenHeight BMC.CORE:BMC_Monitor.ScreenWidth 0 BMC.CORE:BMC_Monitor.ReconciliationIdentity SMS.vGS_ DESKTOP_MONITOR.TimeStamp IPEndpoint BMC.CORE:BMC_Monitor.LastScanDate SMS.v_GS_Network_Adapter_Configur.ResourceID SMS.v_GS_Network_Adapter_Configur.GroupID IPEndpoint SMS.v_GS_Network_Adapter_Configur.MACAddress0 SMS.v_GS_Network_Adapter_Configur.IPAddress0 SMS.v_GS_Network_Adapter_Configur.IPSubnet0 SMS.v_GS_Network_Adapter_Configur.DHCPEnabled0 BMC.CORE:BMC_IPEndpoint.SMSParentID BMC.CORE:BMC_IPEndpoint.DataSet BMC.CORE:BMC_IPEndpoint.SMSChildID BMC.CORE:BMC_IPEndpoint.Category BMC.CORE:BMC_IPEndpoint.Type BMC.CORE:BMC_IPEndpoint.Item BMC.CORE:BMC_IPEndpoint.AssetLifecycleStatus BMC.CORE:BMC_IPEndpoint.Name BMC.CORE:BMC_IPEndpoint.ShortDescription BMC.CORE:BMC_IPEndpoint.Submitter BMC.CORE:BMC_IPEndpoint.Address BMC.CORE:BMC_IPEndpoint.SubnetMask BMC.CORE:BMC_IPEndpoint.Notes 0 BMC.CORE:BMC_IPEndpoint.ReconciliationIdentity SMS2CMDB Project Summary Page 9

10 Network Port SMS.v_GS_Network_Adapter.ResourceID SMS.v_GS_Network_Adapter.GroupID Network Port SMS.v_GS_Network_Adapter.MACAddress0 *exclude NULL in EIE Query SMS.v_GS_Network_Adapter.Name0 SMS.v_GS_Network_Adapter.Manufacturer0 SMS.v_GS_Network_Adapter.ProductName0 BMC.CORE:BMC_NetworkPort.SMSParentID BMC.CORE:BMC_NetworkPort.DataSet BMC.CORE:BMC_NetworkPort.SMSChildID BMC.CORE:BMC_NetworkPort.Category BMC.CORE:BMC_NetworkPort.Type BMC.CORE:BMC_NetworkPort.Item BMC.CORE:BMC_NetworkPort.AssetLifecycleStatus BMC.CORE:BMC_NetworkPort.PermanentAddress *PermanentAddress will hold only one MAC Address. BMC.CORE:BMC_NetworkPort.Name BMC.CORE:BMC_NetworkPort.ManufacturerName BMC.CORE:BMC_NetworkPort.Model BMC.CORE:BMC_NetworkPort.Short Description BMC.CORE:BMC_NetworkPort.Submitter 0 BMC.CORE:BMC_NetworkPort..ReconciliationIdentity SMS.v_GS_Network_Adapter.TimeStamp BMC.CORE:BMC_NetworkPort.LastScanDate Processor SMS.v_GS_Processor.ResourceID SMS.v_GS_Processor.GroupID Processor SMS.v_GS_Processor.Name0 SMS.v_GS_Processor.Name0 SMS.v_GS_Processor.MaxClockSpeed SMS.v_GS_Processor.Manufacturer0 BMC.CORE:BMC_HardwareSystemComponent.SMSParentID BMC.CORE:BMC_HardwareSystemComponent.DataSet BMC.CORE:BMC_HardwareSystemComponent.SMSChildID BMC.CORE:BMC_HardwareSystemComponent.Category BMC.CORE:BMC_HardwareSystemComponent.Type BMC.CORE:BMC_HardwareSystemComponent.Item BMC.CORE:BMC_HardwareSystemComponent.AssetLifecycleStatus BMC.CORE:BMC_HardwareSystemComponent.Name BMC.CORE:BMC_HardwareSystemComponent.Model BMC.CORE:BMC_HardwareSystemComponent.MaxClockSpeed BMC.CORE:BMC_HardwareSystemComponent.ManufacturerName BMC.CORE:BMC_HardwareSystemComponent.Short Description BMC.CORE:BMC_HardwareSystemComponent.Submitter 0 BMC.CORE:BMC_ HardwareSystemComponent.ReconciliationIdentity SMS.v_GS_Processor.TimeStamp BMC.CORE:BMC_HardwareSystemComponent.LastScanDate SMS2CMDB Project Summary Page 10

11 Operating System SMS.v_GS_Operating_System.ResourceID SMS.v_GS_Operating_System.GroupID Software Operating System SMS.v_GS_Operating_System.Name0 SMS.v_GS_Operating_System.Caption0 SMS.v_GS_Operating_System.BuildNumber0 SMS.v_GS_Operating_System.Manufacturer0 SMS.v_GS_Operating_System.CountryCode0 SMS.v_GS_Operating_System.Version0 SMS.v_GS_Operating_System.CSDVersion0 BMC.CORE:BMC_OperatingSystem.SMSParentID BMC.CORE:BMC_OperatingSystem.DataSet BMC.CORE:BMC_OperatingSystem.SMSChildID BMC.CORE:BMC_OperatingSystem.Category BMC.CORE:BMC_OperatingSystem.Type BMC.CORE:BMC_OperatingSystem.AssetLifecycleStatus BMC.CORE:BMC_OperatingSystem.Item BMC.CORE:BMC_OperatingSystem.Name BMC.CORE:BMC_OperatingSystem.Model BMC.CORE:BMC_OperatingSystem.BuildNumber BMC.CORE:BMC_OperatingSystem.ManufacturerName BMC.CORE:BMC_OperatingSystem.CountryCode BMC.CORE:BMC_OperatingSystem.VersionNumber BMC.CORE:BMC_OperatingSystem.Patch Number BMC.CORE:BMC_OperatingSystem.Patch Short Description BMC.CORE:BMC_OperatingSystem.Patch Submitter 0 BMC.CORE:BMC_ OperatingSystem.ReconciliationIdentity SMS.v_GS_Operating_System.TimeStamp BMC.CORE:BMC_OperatingSystem.LastScanDate SMS2CMDB Project Summary Page 11

12 Software SMS.v_GS_SoftwareProduct.ResourceID SMS.v_GS_SoftwareProduct.ProductID As configured in DSL As configured in DSL As configured in DSL SMS.v_GS_SoftwareProduct.ProductName SMS.v_GS_SoftwareProduct.ProductVersion SMS.v_GS_SoftwareProduct.CompanyName BMC.CORE:BMC_Product.SMSParentID BMC.CORE:BMC_Product.DataSet BMC.CORE:BMC_Product.SMSChildID BMC.CORE:BMC_Product.Category BMC.CORE:BMC_Product.Type BMC.CORE:BMC_Product.Item BMC.CORE:BMC_Product.AssetLifecycleStatus BMC.CORE:BMC_Product.Name BMC.CORE:BMC_Product.VersionNumber BMC.CORE:BMC_Product.ManufacturerName BMC.CORE:BMC_Product.Short Description BMC.CORE:BMC_Product.Submitter 0 BMC.CORE:BMC_Product.ReconciliationIdentity Relationship Mappings Target Relationship BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_DiskDrive BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_CDROMDrive BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE: BMC_ Monitor BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_IPEndpoint BMC_HostedAccessPoint BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_NetworkPort BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_HardwareSystemComponent BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_OperatingSystem BMC_HostedSystemComponents BMC.CORE:BMC_ComputerSystem BMC.CORE:BMC_Product BMC_HostedSystemComponents SMS2CMDB Project Summary Page 12

13 Product Catalog Entries Company Tier 1 Tier 2 Tier 3 - Global - Hardware System From SMS - Global - Hardware Component Logical Disk - Global - Hardware Component Monitor - Global - Hardware Component Network Port - Global - Software Component Operating System - Global - Hardware Component Optical Drive - Global - Hardware Component Processor - Global - Hardware Component IPEndpoint - Global - Software Unknown Unknown CD ROM Product Catalog Mapping SMS.v_GS_CDROM.Manufacturer0 SMS.v_GS_CDROM.SystemName0 Optical Drive CDROM Drive BMC_CDROMDRIVE PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword Computer System Product Catalog Mapping SMS.v_GS_Computer_System.Manufacturer0 SMS.v_GS_Computer_System.Name0 System Computer System BMC_COMPUTERSYSTEM PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword SMS2CMDB Project Summary Page 13

14 Monitor Product Catalog Mapping SMS.vGS_DESKTOP_MONITOR.MonitorManufacturer0 SMS.vGS_DESKTOP_MONITOR.Name0 Monitor Monitor BMC_MONITOR PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword Network Adapter Product Catalog Mapping SMS.v_GS_NETWORK_ADAPTER.Manufacturer0 SMS.v_GS_NETWORK_ADAPTER.Name0 Network Port Network Port BMC_NETWORKPORT PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword Operating System Product Catalog Mapping SMS.v_GS_OPERATING_SYSTEM.Manufacturer0 SMS.v_GS_OPERATING_SYSTEM.Caption0 Software Operating System Operating System BMC_OPERATINGSYSTEM PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword SMS2CMDB Project Summary Page 14

15 Processor Product Catalog Mapping SMS.v_GS_PROCESSOR.Manufacturer0 SMS.v_GS_PROCESSOR.Name0 Processor Processor BMC_PROCESSOR PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword Software Product Catalog Mapping SMS.v_GS_SOFTWAREPRODUCT.CompanyName SMS.v_GS_SOFTWAREPRODUCT.Name0 Software Applicationt Third Party Product BMC_PRODUCT PCT:ProductCatalog.Manufacturer PCT:ProductCatalog.Product Name PCT:ProductCatalog.Tier1 PCT:ProductCatalog.Tier2 PCT:ProductCatalog.Tier3 PCT:ProductCatalog.CreateAssetType PCT:ProductCatalog.CategorizationSchemaKeyword CD ROM Manufacturer Mapping SMS.vGS_CDROM.Manufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status Computer System Manufacturer Mapping SMS.vGS_COMPUTER_SYSTEM.Manufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status Desktop Monitor Manufacturer Mapping SMS.vGS_DESKTOP_MONITOR.MonitorManufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status SMS2CMDB Project Summary Page 15

16 Network Adapter Manufacturer Mapping SMS.v_GS_NETWORK_ADAPTER.MonitorManufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status Operating System Manufacturer Mapping SMS.v_GS_OPERATING_SYSTEM.Manufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status Processor Manufacturer Mapping SMS.v_GS_PROCESSOR.Manufacturer0 Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status Software Manufacturer Mapping SMS.v_GS_SOFTWAREPRODUCT.CompanyName Manufacturer Enabled COM:Company.Company COM:Company.Company Type COM:Company.Status SMS2CMDB Project Summary Page 16

17 Endnotes BMC and BMC Software are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. BMC Remedy Asset Management Application, BMC Atrium CMBD, BMC Remedy Action Request System, BMC Remedy Link for SQL Server and BMC Remedy Enterprise Integration Engine are registered trademarks or trademarks of BMC Software, Inc. All other trademarks are the property of their respective owners. Copyright 2007 BMC Software, Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the BMC Software, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE BMC SOFTWARE, INC. OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SMS2CMDB Project Summary Page 17