**Service Modeling Toolkit version 2.0 Posted 6/10/2013**
The purpose of this Field Developed Integration is to automatically create CIs/CI Attributes and Dependencies that make up a Business Service Model. This toolkit can be used quickly “bulk” load/build large number of Service Models in Day 1 Operations. The toolkit can be used as a way to validate the functional components of a Service Model without needing to reconcile to BMC.ASSET. The source of the data is a multi-tabbed XLS spreadsheet.
The concept is to sit down with a customer or SME and fill in the “meta data” of the Service Model. The Service Modeling Toolkit is intended to accelerate the process for building Service Models.
The following diagram shows the data flow from XLS to an Import data set within the CMDB:
The Service Modeling Toolkit includes the following CIs and dependencies:
- Logical CIs such as Transaction and Business Service
- Virtual Server
- Server Clusters
- Load Balancer Resource Pools (e.g. Web Pool)
- SAN – Importing Disk Arrays and LUN Mappings (CI Relationships) to physical servers
- Edge Switch – Network Relationships
- And others ..
In this Release (version 2.0), Simple and Advanced Service Models are supported. Simple Service Models typically include the following CI classes: BMC_ComputerSystem, BMC_Application, BMC_Transaction (optional) and BMC_BusinessService CIs. The benefit is to quickly build out more Business Services (Day 1) which can be consumed by BPPM (for PCA/correlation) and ITSM Applications such as Change Management.
The following Table is a summary of the XLS tabs that are required (or optional) for Simple and Advanced Service Models:
Below is a screenshot of a Simple Service Model (in Atrium Explorer):
Note: Simple Models do supporting including SAN, Clusters and EdgeSwitch connections.
Below is a screenshot of Atrium Explorer after importing the “sample” data (XLS):
Other new features for Service Modeling Toolkit:
- CI Alias support for all CIs in a Service Model. This is primarily for event mapping from BPPM. For BMC_ComputerSystem CIs, an Alias is automatically created based on the following format:
- The CI Alias (BMC_ComputerSystem) can be over-ridden by typing in a value or CI_Alias column in the XLS worksheet.
- XLSX format – moved the spreadsheet from XLS to XLSX format. Spreadsheet now supports drop down menus and pivot tables which allows for easier entry.
- Color coding of columns for easier entry. Red columns are required. Yellow columns are optional.
- Marked As Deleted – you can now update the MarkedAsDeleted attribute for soft deleting the CI in the CMDB.
- Reconciliation ID – if you want to force “matching” CIs without using Reconciliation Rules, you can now use a tool that is shipped with the integration to pull out CIs from BMC.ASSET to an Excel Spreadsheet. You can then manually copy the ReconciliationID to force the matching. This could be beneficial to clean up existing CIs in the CMDB that, for example, are not in FQDN format.
- Transaction CI – the Transaction CI is not required to be part of the Service Model. Logic has been added to IGNORE transaction CI
- Name Attribute for BMC_ComputerSystem and BMC_Cluster using FQDN
- SoftwareServerType Attribute – added to the BMC_SoftwareServer transform
- Other CI Attributes have been added to various transforms …
The following are required for the Service Modeling Toolkit:
- Atrium Integrator 7.6.04 or Atrium Integrator 8.0
- BPPM Extensions installed (requirement even if BPPM is not deployed)
Reference for Pentaho Steps in Transforms:
- Pentaho Data Integration Steps (Use this as a Reference for steps in a Kettle Transform)