It's been awhile since I posted here. I also got to meet Doug (BMC CMDB Architect) in person recently. Here is my recent ah-ha moment with CMDB, and Discovery. I will start with BMC discovery (ADDM) then move to the CMDB topic of service concept. There is lots confusion out there on the difference of technical and business service should be within the CMDB. Some of you might say, I knew that years ago! But, It took me awhile to grabs the concepts even though I used and implemented the various BMC products. I am a visual and tactical learner. I am writing this blog for those type of students. Diagram 1 explains The Pattern Language (TPL) and how things are discovery
Picture 1 explains the discovery concepts and how things are the development by looking for a pattern within a process(s) running on a device. Once you find that process you write a pattern or use discovery to find that process via TPL. By using the discovered process, you can now create a software instance(s) by the group the process into the software(s).
Diagram 2 shows the structure of the TPL base on Diagram 1. Notice the trigger is on a node of node kind base on the condition. You now see the relationship between the pattern and the TPL. Once you define the software instances into business application instance(s). Once BAI is moved into the CMDB CI called BMC.CORE:BMC_ApplicationSystem, BMC.CORE:BMC_ApplicationInfrastructure. Base on your application model you create using the pattern that is consumed by CMDB common data model in different ways. You also need to know that TPL is base on Python. Those of you are interested in pattern and AI. That's another discussion/blog.
Let's look at BAI and SI from the discovery with SAAM and predefine SI that becomes part of a larger model like BSM.
SAAM's Business Application Instances are consumed by these forms:
Let's look at the CDM for CMDB forms BMC.CORE:BMC_ApplicaitionSystem and BMC.CORE:BMC_Applicaiton. You have to understand that parent class is BMC.CORE_ApplicationSystem. The subclasses are BMC.CORE:BMC_Application, BMC.CORE:BMC_ApplicationInfrastructure, BMC.CORE:BMC_SoftwareServer. (Basics)
|CI Name||CI Class||Description|
|BMC Atrium Discovery and Dependency Mapping Active Directory Proxy 10.1 identified as Active Directory on %hostname%|
|manager module on Apache Tomcat Application Server 7.0 listening on 8005, 8080, 8009 on %hostname%|
|Class that stores information about services that represent low-level modules of an application, for example the components deployed within an application server. This class has no corresponding DMTF CIM class.|
|BSM (Business Service Managment is define pattern via TKU of software instance)|
If you drill down after modeling each of these, you notice that subclass is related to the mapping you've created to BMC.CORE:BMC_ApplicaitonSystem.
Software Instance is consumed by these forms:
It is not comsume by the follwing forms:
(Non-organized brain dump)
If you look at CMDB forums, there is lots of confusion around what technical and business service(s) is defined with CMDB in relationship to BMC discovery. I've consulted with large companies like Duke, Starbucks, and eBay. I am finding that this question is asked over and over again. The way understood @Doug Muller: There is no direct relationship between business and technical services that relate(s) into BMC.CORE:BMC_ApplicationSystem. These definitions can be defined by how your business generate revenue with a business service. (If your company makes cars. Any system that supports selling cars is tied to business services.) . Technical services are defined supporting of business service(s). You can define the technical services without a business service(s). The confusion comes from the type of business your company does and way BMC represents examples of technical vs business service(s). BMC is a company that sells software so a lot of the business services sounds like technical services but, it is not a technical service(s). Becuase those services help generate revenue for BMC software. More to come later...
Service Modeling brain Dump