HPAC2CMDB. Integration Guide. Ver. 1.2

Transcription

1 HPAC2CMDB Integration Guide Ver. 1.2 HPAC2CMDB Integration Guide 1

2 Table of Contents Project Abstract... 2 HPAC2CMDB Overview... 2 Hewlett Packard AssetCenter (formerly Peregrine AssetCenter)... 3 Integration Summary... 3 System Requirements... 3 Integration Details... 4 Pre-installation steps... 4 Installation... 5 Tailoring to client environments:... 5 Integration Components... 6 Custom Database Views... 6 BMC Remedy Enterprise Integration Engine... 7 BMC Atrium CMDB... 7 Sample Scenario... 8 Asset Population... 8 Asset Reconciliation... 8 Appendix A: Custom Database Views... 9 Custom Database Views... 9 View computer_view... 9 View employee_location_view... 9 View location_view View phone_view View software_view Appendix B: Data Dictionary Atrium CMDB Data Mapping for Computer Devices Atrium CMDB Data Mapping for Network Devices Atrium CMDB Data Mapping for Printers Atrium CMDB Data Mapping for Phones Atrium CMDB Data Mapping for Monitors Atrium CMDB Data Mapping for Other Peripherals Atrium CMDB Data Mapping for Locations Atrium CMDB Data Mapping for Employees Atrium CMDB Data Mapping for Installed Software Project Abstract HPAC2CMDB Overview The HPAC2CMDB Project is intended to allow users of the BMC Atrium CMDB (Atrium CMDB) to pull information from the HP OpenView AssetCenter (HPAC) database directly into the Atrium CMDB. This is accomplished using several off-theshelf BMC products, including: BMC Atrium CMDB BMC Remedy Enterprise Integration Engine (EIE) HPAC2CMDB Integration Guide 2

3 BMC Remedy Link for SQL Server BMC Remedy Link for Oracle BMC Remedy Asset Management BMC Remedy Action Request System (AR System) This open-source project HPAC2CMDB utilizes the components above to construct a standard method of moving data into the Atrium CMDB from AssetCenter. This open-source project is intended to be compatible with HPAC version 4.4x. HP OpenView AssetCenter (formerly Peregrine AssetCenter) AssetCenter is an Asset Management application used at the enterprise level and is available on several platforms. Primary components include a database (SQL Server or Oracle) and a desktop client application. AssetCenter is compatible with a number of asset discovery tools and is used by large enterprises as a primary asset repository and asset management tool, similar to the Atrium CMDB and BMC Remedy Asset Management. Integration Summary The HPAC2CMDB Project is essentially a defined method for moving data out of AssetCenter into the Atrium CMDB. This is completed by using custom database views in HPAC which are accessed either the Remedy EIE via Remedy Link for SQL Server or Remedy Link for Oracle. The EIE then schedules mass inserts/updates on a timed schedule into the Atrium CMDB, utilizing some custom classes and attribute fields to hold the data. Once data is inside the Atrium CMDB it can be manipulated and used the same way any data within the Atrium CMDB normally could be. System Requirements The following BMC Software products and other non-bmc software products must be installed and operating correctly prior to the integration: BMC products include: BMC Remedy AR System 7.0 or later BMC Atrium CMDB 2.01 or later BMC Remedy Asset Management Application 7.0 (optional) BMC Remedy Link for SQL Server 7.0 (includes Enterprise Integration Engine), configured to connect to the HPAD database, OR HPAC2CMDB Integration Guide 3

4 BMC Remedy Link for Oracle 7.0 (includes Enterprise Integration Engine), configured to connect to the HPAC database. Other products include HP OpenView AssetCenter (formerly Peregrine AssetCenter) 4.4x HPAC database on a compatible Microsoft SQL Server or Oracle database Integration Details Pre-installation steps The HPAC product database is configured in such a way that pulling information directly from the basic application tables is not efficiently accomplished. In order to make this process more efficient the HPAC2CMDB open source kit includes script files to create custom database views for both Oracle and SQL Server. These views are then used by the HPAC2CMDB open-source kit to read data. These custom database views are intended to reside in the HPAC database instance. It is necessary for the DBA to perform the following tasks for either Oracle or SQL Server (depending on which the HPAC database resides in). 1. Obtain the HPAC1.01.zip media file (Windows) or HPAC.tar (Unix) media file. Decompress the file and use folder/directory names. 2. Identify your database platform (Oracle or SQL Server) 3. In the installation media locate the appropriate folder (<..installdir>\oracle or <..installdir>\sql Server) 4. Locate the following files: a. ORACLE oracle_views.sql b. SQL Server sql_server_views.sql 5. Using an appropriate tool (e.g., MS SQL Query Analyzer) run the script file for the appropriate database. Verify the custom views have been created correctly. Custom view descriptions can be located in Appendix A. 6. The permissions for these views should be set to Public/SELECT for both Oracle and SQL Server. As stated previously it is assumed that the EIE is installed and functional. Once the database views are created it is necessary to run the RULEHELPER.EXE utility to confirm connectivity and the ability to see the new database views. To do this perform the following steps: 1. Locate the RULEHELPER.EXE file located at <EIE Install Directory>\<server name> \rl_sql\bin (e.g., C:\Program Files\AR System\Apps\EIE\myserver\rl_sql\bin) x 2. Double click the RULEHELPER.EXE application to run it 3. Enter the appropriate connection information for your HPAC database server and instance on the Database Connection tab. HPAC2CMDB Integration Guide 4

5 4. On the Main tab select the Load Table/View Names button. 5. Confirm the database view names in Appendix A are included in the list If the custom database views appear in Step 5 the views were created and are visible to the EIE. No further action is necessary in the RULEHELPER utility application. Installation To install the HPAC2CMDB kit perform the following steps: 1. If you have not obtained the CMDB Extension loader binary contact BMC software and obtain the cmdbextloader.exe (Windows) or cmdbextloader (Unix). 2. Place the binary extension loader in the directory cmdextloader directory found in the directory structure created in the pre-installation steps. 3. Execute the cmdbextloader binary. You will be prompted for your server name and a valid Administrator login/password. The extension loader will then load the HPAC2CMDB extensions and data provided in the kit automatically, including a. Atrium CMDB Extensions b. Data mapping definitions c. EIE Rules d. Reconciliation Rules 4. The actual EIE integration is distributed disabled. In order to allow data transfer you will need to enable the HPAC Data Mapping exchange. Tailoring to client environments: Each data mapping makes basic assumptions on the defining Nature of items within your HPAC database. For example, the ComputerDeviceMapping item in the EIE retrieves all items with natures of: Computer Laptop Network Interface Network Hardware Any particular HPAC environment may have other unique entries that are not predictable by this open-source kit. Consequently the following data mapping qualifications need to be reviewed to determine if tailoring is needed. The construction of the custom database views allows all qualification for the data mapping tailoring to be completed using the Nature field. Data Mappings which may need tailoring include: ComputerDeviceMapping ComputerDeviceMapping2 PrinterDeviceMapping HPAC2CMDB Integration Guide 5

6 MonitorDeviceMapping LocationMapping EmployeeMapping InstalledSoftware To tailor the qualifications simply add the additional Nature you have in your HPAC environment. For example, to modify the ComputerDeviceMapping to include items with a nature of DB Server you would change: Nature = "Computer" OR Nature = "Laptop" OR Nature = "Network Interface" OR Nature = "Network Hardware" to Nature = "Computer" OR Nature = "Laptop" OR Nature = "Network Interface" OR Nature = "Network Hardware" OR Nature= DB Server Integration Components The integration utilizes a number of items in order to pull data out of the HPAC database and push it into the Atrium CMDB. There are 4 primary components of this system: Custom Database Views Data within the HPAC database was designed to be manipulated using the AssetCenter client application and not at the database level. In order to facilitate the efficient transfer of data out of the HPAC database custom database views were created. Notes on each follow: View computer_view This view utilizes the amcomputer table within AssetCenter as it s primary data table. Other data tables are included are amportfolio, amasset, amnature, and ammodel View employee_location_view This view pulls data primarily from the amempldept table. This is limited in the create view statement to only pull entries that are employees from this table. Departments are not pulled. Other tables include the amcountry table and the amlocation table. View location_view This view utilizes the amlocation table in conjunction with the amcountry table to pull location information. View phone_view This view utilizes the amphone, amportfolio, ammodel, amasset, and amnature tables to pull telephone information. HPAC2CMDB Integration Guide 6

7 View software_view This view utilizes the assoftinstall, amasset, amportfolio, ammodel, and amnature tables to pull information related to installed software. BMC Remedy Enterprise Integration Engine (EIE) The EIE has three major components: The Remedy Link Adapter Remedy Link for SQL Server and Remedy Link for Oracle are two separate products. Only one will be utilized for the HPAC open-source kit. Specifically this will be the one that corresponds to the database where HPAC is installed. The link adapter is primarily a communications tool that allows database-level requests from the EIE to be processed by the target HPAC database and the data returned as requested. The EIE Service The EIE is used to control data flow between AR System and the HPAC database, via either SQL Link for Remedy or Oracle Link for Remedy. The EIE Service reads the required fields and rules defined in the Date Exchange Application (DEA) and controls the data transfer from the HPAC database to the DEA. The Data Exchange Application The DEA can be installed on any supported AR System server. It is the EIE application with forms and workflow that are used to configure the integration between AssetCenter and Remedy 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. BMC Atrium CMDB The Atrium CMDB is the primary repository for all configuration items and data used by BMC applications. Atrium CMDB extensions are included with this open-source kit to facilitate the exact data structures as represented within the HPAC database. Entries created within the Atrium CMDB by this open-source kit are all created within the HPAC.IMPORT dataset (with HPAC.IMPORT specified as the dataset ID). Reconciliation Reconciliation rules are not included with this open-source kit. The basic implementation of this kit and a companion HPAC installation will require ground rules unique to every situation. The assumption is made that this kit will be on the receiving end of a one-way real time transfer from the HPAC application. Either end could be HPAC2CMDB Integration Guide 7

8 considered the master data depending on customer usage. It is also dependent on whether the customer is using the BMC Remedy Asset Management application to manipulate data on the receiving end or not. However, implementing simple data reconciliation is a straightforward task based on each customer site. Purge When an entry is reported by the EIE as deleted in the HPAC database the corresponding entry in the Atrium CMDB will be marked as deleted by marking the custom attribute HPAC.Deleted as Yes for the class. This can easily be changed to delete the object if desired simply by altering the Delete portion of the data mapping for that (or all) object type(s). Sample purge rules are included but disabled. Sample Scenario Asset Population Acme corporation has been a long-time user of the AssetCenter application to track their assets in many locations around the country. This database is populated by a variety of methods, including auto-discovery, vendor data loads from asset acquisition, and user data input. Due to a recent product expansion, the BMC Remedy ITSM suite has been implemented to provide support for the enterprise. HPAC is a useful tool that will not be phased out but the support organization needs to have access to the HPAC data in order to provide real, timely support with accurate information regarding the customer assets they are supporting. This business need would drive the implementation of this open source kit. Specifically the kit would update data in the Atrium CMDB on a daily batch basis, providing updates to the support organization which could view the customer data. This will allow users of the BMC Remedy ITSM suite to actually link problem and incident cases to actual assets within the BMC environment and not depend on expensive and inefficient custom data interfaces directly between HPAC and the Atrium CMDB. Asset Reconciliation Over time Acme corporation has decided the business need exists for users of the ITSM to modify assets using BMC Remedy Asset Management. Consequently, simple reconciliation rules are developed. These reconciliation rules state that the last user to touch an asset either in HPAC or in the Atrium CMDB count as the correct data. Equal weight can be given to each side since both allow for manual user entry. HPAC2CMDB Integration Guide 8

9 Appendix A: Custom Database Views Custom Database Views View computer_view Column Name lportfolioitemid AssetTag FullName lastid lmodelid BarCode Field1 Field2 Field3 ComputerDesc ComputerType CPUInternal CPUType lcpunumber lcpuspeedmhz ldisksizemb lmemorysizemb Name OperatingSystem PhysicalAddress TcpIpHostName TcpIpDomain TcpIpAddress VideoCard SoundCard Nature lparentid Workgroup SerialNo View employee_location_view Column Name lempldeptid bdepartment Fax FirstName FirstName2 Field3 Field2 Field1 HomePhone MailLogin MrMrs HPAC2CMDB Integration Guide 9

10 Name Phone Title UserDesc UserDomain UserLogin FullName llocaid lparentid Address1 Address2 City State ZIP LocationType LocationName Expr1 lcountryid CountryName MobilePhone View location_view Column Name Address1 Address2 City State ZIP LocationType LocationName Expr1 lcountryid CountryName FullName View phone_view Column Name lportfolioitemid AssetTag FullName lastid lmodelid BarCode Field1 Field2 Field3 Nature PhoneNum bspeaker HPAC2CMDB Integration Guide 10

11 lphoneid Extension litemid View software_view Column Name lportfolioitemid AssetTag Name lsoftinstid setype SoftOS Status lparentid luserid BarCode dtlastmodif Field1 Field2 Field3 VersionLevel RegisteredKey RegisteredUser Appendix B: Data Dictionary Atrium CMDB Data Mapping for Computer Devices HPAC BMC_ComputerSystem.Submitter HPAC.IMPORT BMC_ComputerSystem.DatasetId Computer BMC_ComputerSystem.Type HPAC.Computer BMC_BaseElement.HPAC_Nature X amcomputer.assettag BMC_BaseElement.HPAC_AssetTag X amcomputer.computerdesc BMC_BaseElement.Description amcomputer.computertype BMC_ComputerSystem.HPAC_SystemType X amcomputer.cpuinternal BMC_ComputerSystem.HPAC_CPUInternal X amcomputer.cputype BMC_HardwareSystemComponent.BMC_Processor amcomputer.lcpunumber BMC_HardwareSystemComponent.HPAC_CPUNumber X amcomputer.lcpuspeedmhz BMC_HardwareSystemComponen.HPAC_CPUSpeed X amcomputer.ldisksizemb BMC_ComputerSystem.HPAC_DiskSize X amcomputer.lmemorysizemb BMC_HardwareSystemComponent.BMC_Memory amcomputer.operatingsystem BMC_SystemSoftware.BMC_SOftware amcomputer.physicaladdress BMC_BaseRelationship.BMC_ElementLocation amcomputer.soundcard BMC_HardWareSystemComponent.HPAC_SoundCard X amcomputer.tcpipaddress BMC_ComputerSystem.HPAC_TCPIPAddress X amcomputer.tcpipdomain BMC_ComputerSystem.Domain amcomputer.tcpiphostname BMC_ComputerSystem.HostName amcomputer.videocard BMC_HardwareSystemComponent.VideoCard X amcomputer.workgroup BMC_ComputerSystem.HPAC_WorkGroup X amcomputer.fullname BMC_BaseElement.Name amcomputer.lparentid BMC_BaseElement.HPAC_ParenttID X HPAC2CMDB Integration Guide 11

12 amportfolio.manufacturer amportfolio.modelid amasset.serialno BMC_BaseElement.ManufacturerName BMC_BaseElement.Model BMC_BaseElement.SerialNumber Atrium CMDB Data Mapping for Network Devices HPAC BMC_ComputerSystem.Submitter HPAC.IMPORT BMC_ComputerSystem.DatasetId Network Device BMC_ComputerSystem.Type HPAC.Network BMC_BaseElement.HPAC_Nature X amcomputer.assettag BMC_BaseElement.HPAC_AssetTag X amcomputer.computerdesc BMC_BaseElement.Description amcomputer.computertype BMC_ComputerSystem.HPA_CSystemType X amcomputer.cpuinternal BMC_ComputerSystem.HPAC_CPUInternal X amcomputer.cputype BMC_HardwareSystemComponent.BMC_Processor amcomputer.lcpunumber BMC_HardwareSystemComponent.HPAC_CPUNumber X amcomputer.lcpuspeedmhz BMC_HardwareSystemComponen.HPAC_CPUSpeed X amcomputer.ldisksizemb BMC_ComputerSystem.HPAC_DiskSize X amcomputer.lmemorysizemb BMC_HardwareSystemComponent.BMC_Memory amcomputer.operatingsystem BMC_SystemSoftware.BMC_SOftware amcomputer.physicaladdress BMC_BaseRelationship.BMC_ElementLocation amcomputer.tcpipaddress BMC_ComputerSystem.HPAC_TCPIPAddress X amcomputer.tcpipdomain BMC_ComputerSystem.Domain amcomputer.tcpiphostname BMC_ComputerSystem.HostName amcomputer.workgroup BMC_ComputerSystem.HPAC_WorkGroup X amcomputer.fullname BMC_BaseElement.Name amcomputer.lparentid BMC_BaseElement.HPAC_ParenttID X amportfolio.manufacturer BMC_BaseElement.ManufacturerName amportfolio.modelid BMC_BaseElement.Model amasset.serialno BMC_BaseElement.SerialNumber Atrium CMDB Data Mapping for Printers HPAC BMC_ComputerSystem.Submitter HPAC.IMPORT BMC_ComputerSystem.DatasetId Printer BMC_Printer.Type HPAC.Network BMC_BaseElement.HPAC_Nature X amcomputer.assettag BMC_BaseElement.HPAC_AssetTag X amcomputer.computerdesc BMC_BaseElement.Description amcomputer.physicaladdress BMC_BaseRelationship.BMC_ElementLocation amcomputer.tcpipaddress BMC_Printer.HPAC_TCPIPAddress X amcomputer.tcpipdomain BMC_Printer.HPAC_Domain X amcomputer.tcpiphostname BMC_Printer.HPAC_HostName X amcomputer.workgroup BMC_Printer.HPAC_WorkGroup X amcomputer.fullname BMC_BaseElement.Name amcomputer.lparentid BMC_BaseElement.HPAC_ParenttID X amportfolio.manufacturer BMC_BaseElement.ManufacturerName amportfolio.modelid BMC_BaseElement.Model amasset.serialno BMC_BaseElement.SerialNumber HPAC2CMDB Integration Guide 12

13 Atrium CMDB Data Mapping for Phones HPAC.Network BMC_BaseElement.HPAC_Nature X amcomputer.assettag BMC_BaseElement.HPAC_AssetTag X lphoneid BMC_HPACPhone.PhoneID X bspeaker BMC_HPACPhone.Speaker X bvoic BMC_HPACPhone.VM X Extension BMC_HPACPhone.PhoneExt X PhoneNum BMC_BaseElement.Name Atrium CMDB Data Mapping for Monitors HPAC BMC_SystemComponent.Submitter HPAC.IMPORT BMC_SystemComponent.DatasetId amnature.nature BMC_Monitor.HPAC_Nature X amcomputer.assettag BMC_Monitor.AssetID X amcomputer.computerdesc BMC_Monitor.Type amcomputer.fullname BMC_Monitor.Name amcomputer.lparentid BMC_Monitor.HPAC_ParenttID X amportfolio.manufacturer BMC_Monitor.SupplierName amportfolio.modelid BMC_Montior..Model amasset.serialno BMC_Monitor.SerialNumber Atrium CMDB Data Mapping for Other Peripherals HPAC BMC_SystemComponent.Submitter HPAC.IMPORT BMC_SystemComponent.DatasetId amnature.nature BMC_SystemCompontent.HPAC_Nature X amcomputer.assettag BMC_HPAC_Peripheral.HPAC_AssetTag X amcomputer.computerdesc BMC_ HPAC_Peripheral.Description X amcomputer.computertype BMC_ HPAC_Peripheral HPAC_SystemType X amcomputer.fullname BMC_ HPAC_Peripheral Name X amcomputer.lparentid BMC_ HPAC_Peripheral HPAC_ParenttID X amportfolio.manufacturer BMC_HPAC_Peripheral ManufacturerName X amportfolio.modelid BMC_HPAC_Peripheral Model X amasset.serialno BMC_HPAC_Peripheral SeriallNumber X Atrium CMDB Data Mapping for Locations llocaid BMC_PhysicalLocation.HPAC_ID X Address1 BMC_PhysicalLocation.Address Address2 BMC_PhysicalLocation.HPAC_Address2 X BarCode BMC_PhysicalLocation.HPAC_BarCode City BMC_PhysicalLocation.City LocationType BMC_PhysicalLocation.Type HPAC2CMDB Integration Guide 13

14 Name State ZIP FullName lcountryid BMC_BaseElement.Name BMC_PhysicalLocation.StateOrProvince BMC_PhysicalLocation.PostalCode BMC_BaseElement.Description BMC_PhysicalLocation.Country Atrium CMDB Data Mapping for Employees lempldeptid BMC_Person.HPACId X BarCode BMC_Person.HPACBarCode X bdepartment BMC_Person.Department BMC_Person. Fax BMC_Person.Fax Field1 BMC_Person.HPAC.Field1 X Field2 BMC_Person.HPAC.Field2 X Field3 BMC_Person.HPAC.Field3 X FirstName BMC_Person.FirstName FirstName2 BMC_Person.HPACFirstName2 X HomePhone BMC_Person.HPACHomePhone X IDNo BMC_Person.HPACIDNo X MobilePhone BMC_Person.MobilePhone MrMrs BMC_Person.PersonAdditionalDetails Name BMC_Person.LastName Phone BMC_Person.OfficePhone Title BMC_Person.Title UserName BMC_BaseElement.Name FullName BMC_BaseElement.Name Atrium CMDB Data Mapping for Installed Software (in BMC Software) lsoftinstid BMC_SystemSoftware Field1 BMC.HPAC.SoftInstallField1 X Field2 BMC.HPAC.SoftInstallField2 X LicenseNo BMC.HPAC.SoftInstallLicenseNo X RegisteredKey BMC.HPAC.SoftInstallRegisteredKey X SoftOS BMC.HPAC.SoftInstallOS X VersionLevel BMC.HPAC.SoftInstallVersion X 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. HPAC2CMDB Integration Guide 14

15 HP OpenView AssetCenter is a registered trademark or trademarks of Hewlett Packard. All other trademarks are the property of their respective owners. Copyright (c) 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. HPAC2CMDB Integration Guide 15