Discovery

Modernized discovery framework

The Content Gathering service is one of many OCP services designed to scale horizontally. Simply run another client process for it to subscribe to its service, get dropped in the resource pool, and begin working.  Clients can be packaged in whatever type of boundary you use… VMs, lpars, containers, process virtualization, etc.  And they can be spun up/down on demand.

Revolutionary discovery methodology

The included “dynamic discovery” methodology is fundamentally different from the 1-to-1 method used by proprietary products.  The core framework enables you to continue creating the standard 1-to-1 packages of job-to-technology (e.g. a job to specifically discover Oracle databases).  However, this provides a new methodology to capture products and dependencies without requiring 1-to-1 configurations or scripts.  Dynamic discovery will discover and map out your company’s in house products, without telling it what to look for.  This is increasingly important with how fast products go from idea to release today, by using turn-key DevOps, readily available developer libraries, and the open-source consortium.

Enable content gathering to be ITSM vendor agnostic

The proprietary products in IT Service Management (ITSM) compete at reinventing the wheel.  They develop and support their own versions of each overlapping discovery/integration job (e.g. Apache web server, Oracle database, VMware infrastructure).  And often times, the people writing the jobs are more familiar with the ITSM vendor they are working with, than the endpoint they are discovering.  What if the scales were flipped, and jobs could be improved/refined by a community of developers familiar with the technologies – yet have no background in ITSM?  And what if those high quality content gathering jobs could be (re)used by all ITSM products?  You would tweak the datasets/mappings sent into the downstream ITSM product in integration flows managed by OCP, or let each ITSM product pull whatever they desired from the RESTful API, or have a third part integration service sit in the middle.  Any of those options are less work and provide higher job quality with broader support.

 

Screen captured demos

Note: these were created by CMS Construct; we were given permission to link them here: