OneCMDB_Core_Concepts

–
September 2006

Job Trigger
●
A Job Process can have one or more Job Triggers OneCMDB starts a job when its trigger(s) have met their conditions Triggers can be configured to be

OneCMDB Core Concepts and API overview
Check the documentation available at for more details
Concepts Used
●
Configuration Item (CI) Attribute Template and Instance Reference Change Control Board (CCB) Policy Accounting Job Process Job Trigger
●
●
●
●
●
●
●
●
Configuration Item
●
A CI in OneCMDB is defined by:
– – – –
ID Label (alias/display name) Description (text/icon) User-defined attributes...
●
Everything is a CI!
–
●
●
The types are model dependent
●
Example of reference types
– – – –
physical dependency logical dependency business relation organizational relation, etc.
Root Policy
Root Container
Root Ci All other User-defined CIs
User-defined references
User-defined Policies
User-defined Containers
September 2006

●
type of the link (e.g. physical relation)
–
Min/Max Occurrences
●
number of values the Attributes must/can have

September 2006
Template and Instance
– – – –
a Java Class (Java Class can startup an external program) Input parameters (all attributes existing on Job Process) Progress (up to Java Class) State (idle/running) automatically set by OneCMDB
– –
●
Create a new CI
– – – – – – – –
ICcb ccb = (ICcb) session.getService(ICcb.class); ICmdbTransaction tx = ccb.getTx(session); ICiModifiable template = tx.getTemplate(ci); ICiModifiable newCi = template.createOffspring(); newCi.setAlias("My new CI"); ITicket ticket = ccb.submitTx(tx); IRfcResult result = ccb.waitForTx(ticket); if (result.isRejected()) return errorMsg(result.getRejectCause());

September 2006
CCB
●
'Automated' Change Control Board
– –
Reviews all RFCs Grants or rejects the changes based on the existing Policies
●
RFCs are created for all changes: creation, modifications and removal of CIs.
Instances
September 2006

Reference
●
A reference is a CI pointing to another CI A reference is created when the Attribute of a CI has another CI for value References are typed
Code Example
●
Query a CI with ID '101'
–
IModelService onecmdbModel = (IModelService) session.getService(IModelService.class); ItemId id = new ItemId(“101”); ICi ci = onecmdbModel.find(id);
–
Everything can be changed except the ID of a CI
●
CCB is asynchrone, as some changes may take time to realize (use a ticket)
September 2006

Policies
– – – –
●
Session
–
Contains credentials of user acting toward OneCMDB

September 2006
Internal CIs
Root
Root Reference
Root Job User-defined Job Processes Job Triggers
– – –
●
●
Manual trigger (a user or another entity) Schedule trigger (date/time based trigger) Event trigger (based on changes to specific CIs) - later
September 2006
●
CIs are organized using object-oriented techniques
– – – –
All CIs are derived from a 'parent' CI: a Template A CI has only one parent Template A CI inherits all Attributes defined by its parent Template. Changes to a Template affect all the Template's children (adding, modifying or removing Attributes) A CI that is not a Template is said to be an Instance A Template may have a parent Template There is always a Root Template

API Overview
●
IService
– – –
IModelService (find any CI) ICcb (create, submit and find RFCs) IReferenceService (access Root of references, navigate references forward/backward) ICiService (access Root of user-defined CIs) IJobService (access Root of Jobs, start/stop/cancel jobs) IPolicyService (access Root of Policies) IContainerService (access Root of containers)
September 2006

Job Process
●
OneCMDB can use external programs
–
Mainly used to create or modify CIs (auto-population).
●
Job Processes are CIs with attributes
–
OneCMDB keeps an history of all changes to a CI since its creation
●
Can query all RFCs on a specific CI
– – – –
Type of RFC (default: all) From date – to date Ordering ascending/descending How many (paging)
●
Policies are created in Java Modify the behavior of the CCB Example: