The document contains minutes from the January 18, 2012 Configuration Management - User Group (CM-UG) meeting. The agenda included a presentation and demo on customizing the Installation and Software Management (ISM) module, as well as a discussion on ISM customizations, ISM database cleanup, and software license data integration. Contact information was provided for upcoming CM-UG events and ways to get involved in the user group through mailing lists and LinkedIn. Information was also given on jobs and BMC consulting resources.
8. Agenda
Custom ISM presentation
Speaker : Neel Tiwari and Nitish Shrivastava
Custom ISM demo
Speaker : Surekha Dharmarajan
Q&A
9. Prelude…
Like Custom Inventory, ISM can be extended (from 8.2.01)
Includes custom statistics and SNMP
3 simple steps
Identification of custom data
Writing custom channel to capture data
Modifying database to Store/Display custom data
Add new tables
Update views [Specific to component]
If we want to use new attributes in health calculation then we need to create groups and
formulae to show them in ISM dashboard
Specification would be given in product documentation
10. Identification of custom data
Identify what the custom attributes are that you want to capture
For Eg: you want to capture number of running daemon processes. The value will
be an integer representing the number of processes.
“Associate” an Identifier with this attribute.
Eg: Let 6.6.1 be the custom attribute representing the above value.
11. Writing custom channel to capture data
Creating the custom channel to capture that data. Two important "interfaces"
for customers :
ICustomStatsProvider – This is implemented by customer in the channel to add
custom stats
IStatsService service = context.getFeature("ism") -This is the new ISM Feature
which the custom channel will register with.
Note: In above example , your code should be able to capture the number of
running daemon processes.
Eg:
t1 = new MyStatsAttribute();
t1.id = "6.6.1";
t1.val = [number of running daemon processes];
Properties to be added :
For a client, add the marimba.tuner.hm.customclient.url=<custom channel URL>.
For a transmitter add the marimba.tuner.hm.customtx.url=<custom channel URL>.
For a proxy, add the marimba.tuner.hm.customproxy.url=<custom channel URL>.
For a tuner, add the marimba.tuner.hm.customcms.url=<custom channel URL>.
12. Modifying database to Store/Display custom data
Adding new tables: Add database script to add custom tables.
Eg: create table hm_custom_tuner_stats(
machine_id varchar(128) not null,
tuner_id numeric(20, 0) not null ……
Update views [Component specific]
If we are adding new attributes in tuner, then we need to update hmv_client_tuner_summary
If we are adding new attributes in Tx then we need to update hmv_tx_summary
If we are adding new attributes in Proxy, then we need to update hmv_proxy_summary
If we are adding new attributes in CMS, then we need to update hmv_cms_summary
13. Modifying database to Store/Display custom data
If we want to use new attributes in health calculation then we need to create groups
and formulae to show them in ISM dashboard
Add/modify groups for components to capture custom stats in ISM Dashboard
To automate this step, you can "export" the group you create
14. Modifying database to Store/Display custom data
Modifying health formula to take into account custom stats
15. Custom SNMP traps
To view Custom SNMP Alerts in the ISM Dashboard, Traps will have to be sent in the
following format:
<Trap_id_for_time><Time> <Trap_id_for_ipAddress><IP Address>
<Trap_id_for_tunerID><Tuner ID> <Trap_id_for_Type><Trap Type> <Trap_id_for_Trap_details
><Trap Details> <Trap_id_for_stats_mapping><Stats_mapping>
<Trap_id_for_machine_id><Machine ID> <Trap_id_for_type_id><Type ID>
Database Script to add the Custom SNMP Alert in Email Notifications.
For Eg: Insert into hm_snmp_lookup values(‘id’,‘Trap_id’,’Trap Description’, ‘Is_Custom’)
Configure Email Notification for Custom SNMP Alert in ISM Dashboard.