DCML/ITIL/CMDB Use Cases
Ajay Gummadi
DCML
Problem
• Software Vendor VendorCo, requests for
an audit of Customer CustomerCo usage
of its server based application ServApp.
• VendorCo claims that CustomerCo
currently uses more licenses than
purchased and hence should purchase
more licenses.
• Use Case UC002 at
http://dcml.blogspot.com/
DCML
CustomerCo
• CIO of CustomerCo is IT/best-practices
savvy
• CIO has implemented DCML and ITIL in
the organization over a year ago
• CMDB reflects the current state of the
organization
DCML
DCML Architecture
User
DCML Processor
Report Server
DCML AGENT
CMIP
TMN
Hardware
SNMP
CIM
MIB
Operating
System
CMDB
HTTP
CIM
BIOS
DCML
Custom
Firmware
Applications
Step 1
• VendorCo requests an audit
• Requests a list of all instances of ServApp,
running on BSD
• Request made via DCML DIX format.
DCML
Sample Request
<dcml version=“1.0”>
<action>audit_request</action>
<message_id>1234</message_id>
<requestor>VendorCo</requestor>
<vendor_id>10032</vendor_id> <!– used for identification 
<request_date>March 23, 2005</request-date>
<respond_by_date>March 31, 2005</respond_by_date>
<application>
<application_name>ServApp<application_name>
<application_name/>
<version>6.2</version>
<application_platform>BSD</application_platform>
</application> <!– One or more instances of application 
</dcml>
DCML
Sample Response
• Message checksum checked
• Request acknowledged
<dcml version=“1.0”>
<action>request_acknowledgement</action>
<message_id>1234</message_id>
<sender>CustomerCo</sender>
<vendor_id>10032</vendor_id> <!– used for
identification 
</dcml>
DCML
Step 2: Audit Initiated
• DCML Processor generates query for
CMDB
<dcml version=“1.0”>
<message_id>312</message_id>
<type>cmdb_query</type>
<query>list</type>
</dcml>
DCML
Step 3: CMDB Response
<dcml version=“1.0”>
<message_id>435</message_id>
<request_id>312</request_id>
<type>cmdb_query_result</type>
<response>
<category>notebooks</category>
<category>desktops</category>
<category>servers</category>
<category>network_hardware</category>
<category>telco_hardware</category>
<category>PIM</category>
<category>Miscellaneous</category>
</response>
</dcml>
DCML
Step 4: DCML PROC. > CMDB
<dcml version=“1.0”>
<message_id>313</message_id>
<type>cmdb_query</type>
<query>
<search category=“servers”>BSD</search>
<search
category=applications”>ServApp</search>
</query>
</dcml>
DCML
Step 5: CMDB Response
<dcml version=“1.0”>
<message_id>436</message_id>
<request_id>313</request_id>
<type>cmdb_query_result</type>
<response>
<results>208</results>
<field>Vendor <type>string</type></field>
<field>Version</field>
<field>Language</field>
<field>Service Pack</field>
<field>Patch Version</field>
<field>Build Versions</field>
<field>Install Location</field>
<field>IP Address</field>
<field>License Key</field>
<field>Serial Number</field>
<field>Install Date</field>
<field>Number of Uses</field>
<field>User Name<field>
<field>Part Of Suite</field>
<field>Date of Last Use</field>
<field>Install Date</field>
<field>Number of Uses</field>
<field>User Name<field>
<field>Part Of Suite</field>
<field>Date of Last Use</field>
<field>License Key</field>
<field>Serial Number</field>
<field>Install Date</field>
<field>Number of Uses</field>
<field>User Name<field>
<field>Part Of Suite</field>
<field>Date of Last Use</field>
</response>
</dcml>
DCML
Step 6: DCML PROC. > CMDB
<dcml version=“1.0”>
<message_id>314</message_id>
<type>cmdb_query</type>
<query>
<search_handle>313</search_handle>
<fields>
<field>IP Address</field>
<field>User Name</field>
<field>Date of Last Use</field>
<field>Number of Uses</field>
<field>Serial Number</field>
<field>License Key</field>
</fields>
</query>
</dcml>
DCML
Step 7: CMDB Response
<dcml version=“1.0”>
<message_id>437</message_id>
<request_id>314</request_id>
<type>cmdb_query_result</type>
<response>
<results>208</results>
<row>
<value>192.168.1.1</value>
<value>jdoe</value>
<value>March 22, 2005</value>
…..
</row>
</response>
</dcml>
DCML
Step 8: Verification of keys
• DCML Processor verifies each license key
against CMDB and DSL
• License keys are also checked against
invoices and receipts (available via
CMDB)
• DCML Processor seeks clarification from
DCML agents and users via DCML DIX
and auto-generated XUL/XForms forms
• CMDB is updated, with findings.
DCML
Step 9: Completion of Audit
• DCML Processor generates audit reports
• Internal workflow engine routes report to
CIO for approval and digital signatures
• Approved report is dispatched to
VendorCo, in DIX format.
DCML
Step 10: Post Audit Assessment
• CIO has data regarding ServApp usage
• CIO can negotiate better pricing for
licenses, using data available from
DCML/CMDB
• CIO can reallocate unused/sparingly used
licenses.
• CIO can minimize/eliminate upgrade fees
for unused (but installed) instances.
DCML
Step 11: Post Audit Assessment
• CIO has data regarding ServApp usage
• CIO can negotiate better pricing for
licenses, using data available from
DCML/CMDB
• CIO can reallocate unused/sparingly used
licenses.
• CIO can minimize/eliminate upgrade fees
for unused (but installed) instances.
DCML
Advantages
•
•
•
•
•
Accuracy of information
Real-time updates
Quicker turnarounds
Cost savings
BSA/SIIA compliance
DCML
Advantages (contd…)
• Reports : Display by cost
center/department/site
• Resellers can bid, based on internal usage
data (DCML/CMDB PartnerNet)
• Powerful reporting (includes historical
data)
DCML
Questions?
DCML