{"id":156,"date":"2006-07-15T19:02:58","date_gmt":"2006-07-15T23:02:58","guid":{"rendered":"http:\/\/dougmcclure.net\/blog\/2006\/07\/itccmdb-installation-cdtscmdb-notes-cont\/"},"modified":"2006-07-15T19:02:58","modified_gmt":"2006-07-15T23:02:58","slug":"itccmdb-installation-cdtscmdb-notes-cont","status":"publish","type":"post","link":"https:\/\/dougmcclure.net\/blog\/2006\/07\/itccmdb-installation-cdtscmdb-notes-cont\/","title":{"rendered":"ITCCMDB Installation – CDTS\/CMDB Notes Cont."},"content":{"rendered":"

I was able to work through the last few issues I was having thanks to the tips and tricks section of the ITCCMDB redbook<\/a>.<\/p>\n

Discovery started after defining a simple scope range for the RHEL system I run in a VMware image on my laptop. There is lots of flexibility here to control what’s discovered and what’s excluded. The initial discovery consisted of basic port scans, ping, ICMP and ssh probes of my host to see what was happening. Various sensors are triggered based on what it finds and a very basic set of information is collected.<\/p>\n

Conducting a more detailed discovery was as simple as configuring proper credentials for my RHEL image and applications so the discovery process can log in and collect much richer information. Full information about my RHEL image, DB2 database, etc. was collected after adding this information and rediscovering.<\/p>\n

I’ve now got a lot of discovered information about what’s installed in my RHEL environment (Netcool\/OMNIbus, Netcool\/RAD 3.0, Netcool\/NGF, Netcool\/License Manager, Netcool\/Security Manager, ITCCMDB (CDTS\/CMDB)). Most of this makes sense to me as I’m familiar with all of those application characteristics. However, there’s not enough context to really know what 192.168.228.2 port 4100 is. Creating custom servers profiles allows you to add the right context to the discovered information for grouping everything into applications and services. There are quite a few out-of-the-box custom servers that you’d expect to find in a large IT environment so you’re likely to have a lot of information after your first discovery. Building custom servers is where you’ll spend a lot of time in custom service and application environments.<\/p>\n

There’s a lot of flexibility in how to build custom server profiles. The simplest way was to match a port that was discovered, such as port 4100. I know this port is for the Netcool\/ObjectServer. I can add more parameters that must match such as the program name “nco_objsvr” to be sure that I get an accurate match for future discoveries. Any future discovery information matching port 4100 and “nco_objsvr” will now show up as Netcool\/ObjectServer applications.<\/p>\n

It’s in the custom server profile that I also can define what configuration files, software modules or application descriptors that I want to discover and track. What I like about this is you can actually download and track the contents of configuration files, directories or if something changes with a module or binary.<\/p>\n

I’ve got a lot to play with now. Next steps are building business services and applications. Stay tuned.<\/p>\n","protected":false},"excerpt":{"rendered":"

I was able to work through the last few issues I was having thanks to the tips and tricks section of the ITCCMDB redbook. Discovery started after defining a simple scope range for the RHEL system I run in a VMware image on my laptop. There is lots of flexibility here to control what’s discovered […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58,45,38,37,65,40,41,39],"tags":[153,940,933,150,932,151,957,935,936,934],"class_list":{"0":"post-156","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-application-discovery","7":"category-cmdb","8":"category-ibm","9":"category-implementation","10":"category-itccmdb","11":"category-itil","12":"category-itsm","13":"category-tivoli","14":"tag-cdts","15":"tag-cmdb","16":"tag-ibm","17":"tag-ibm-tivoli","18":"tag-implementation","19":"tag-itaddm","20":"tag-itccmdb","21":"tag-itil","22":"tag-itsm","23":"tag-tivoli"},"_links":{"self":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/156","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/comments?post=156"}],"version-history":[{"count":0,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/156\/revisions"}],"wp:attachment":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/media?parent=156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/categories?post=156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/tags?post=156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}