© 2009 IBM Corporation ITCAM for Transactions ISM Profiles Management ITCAM for Transactions – Internet Service Monitoring – Profile Management (v7.3) Andrea Douarinou, Pamela Vance, Stanford Madriaga Nov 2011

© 2009 IBM Corporation2 What is Internet Service Monitoring?  Works by emulating the actions of a real user.  i.e. HTTP monitor tries to access a web page, then measures how well the HTTP service performed. Admin decides on the acceptable return values.

© 2009 IBM Corporation3 Architecture (Version and Up)  Monitors –Monitors = Protocols = Elements. –Emulate users –Connects to Databridge.  Databridge –Communication bus for monitors and modules. –Receives data from Monitors and converts data into different formats for the modules.  Modules – ObjectServer - converts data and forward to Netcool/ObjectServer as events – Datalogs – converts data into XML – KIS agent – sends results to ITM Profiles - Holds elements 3 Without ITM module and ISM KIS agent = v6.0.0/v2.4

© 2009 IBM Corporation4 TEP Interface and MTEMS Window 4 Other interfaces : - Browser * Use regular Internet browser - WebStart Use Java plugin

© 2009 IBM Corporation ISM Profiles – Version 2.4 5

© 2009 IBM Corporation ISM Profiles – V2.4 Profiles elements 6

© 2009 IBM Corporation ISM 2.4 OID Groups – OID Groups 7

© 2009 IBM Corporation ISM 2.4 OID Groups – Members/Attributes 8

© 2009 IBM Corporation ISM 2.4 – Path of saved Profiles 9

© 2009 IBM Corporation ISM 2.4 OID groups – Path of saved groups 10

© 2009 IBM Corporation ISM 2.4 – Location of custom files (props, rules) 11

© 2009 IBM Corporation Migrating ISM v2.4 Profiles to ITCAM ISM 7.3 Steps  1. Convert existing profiles a. Create $ISMHOME/ismbackup/profiles and copy active profiles from ISM 2.4 b. Create $ISMHOME/ismbackup/profiles/defaults and copy oidgroups.xml and profiles.xsd from ISM 2.4 c. Convert the profiles to v7.3 format Unix/Linux: $ISMHOME/bin/profileUpgrade Windows: %ISMHOME%\platform\win32\bin\profileUpgrade.exe  2. Transfer custom properties  3. Copy custom rules files 12

© 2009 IBM Corporation Step 1a & 1b: Copy profiles, oidgroups.xml, profiles.xsd 13

© 2009 IBM Corporation Step 1c: Convert profiles to v7.3 14

© 2009 IBM Corporation Step 1c : Results 15

© 2009 IBM Corporation Step 2 – Copy *.props files ISM 2.4 path  NCHOME/etc/ism/props ISM 7.3 Path  ISMHOME/ism/etc/props 16 Step 3 – Copy *.rules files ISM 2.4 path  NCHOME/etc/ism/rules ISM 7.3 Path  ISMHOME/etc/rules

© 2009 IBM Corporation Extra steps 17 cli_xml2cli.html “Agent is offline” = ensure kisagent is running, or you can do a manual resync in the GUI after migration

© 2009 IBM Corporation Migration result 18

© 2009 IBM Corporation Known Issues  IV02709 – (version 7.2 to 7.3) ISM VERSION 7.3 DOES NOT CORRECTLY UPGRADE TRANSX PROFILES  IV The profileUpgrade tool fails during migration. The profileUpgrade.log may show "Error: Profile upgrade failed". The problem is memory allocation when migrating large volumes of data. It manifest at lower volumes in AIX compared to Linux or Windows. Workaround: Migrate the profiles in batches. 19

© 2009 IBM Corporation Command Line Tools  ismbatch – – dita/common/topic/app_ISMBatch_utility.html  ismconfig – – dita/ag/concept/kis_configcli_intro.html  Xml2cli (use to convert profile made by ismbatch to ismconfig) – mt.doc_7.3%2Fism%2Fdita%2Fag%2Fconcept%2Fkis_configcli_xml2cli.html 20

© 2009 IBM Corporation21 Creating and Deploying an ITCAMfT 7.3 ISM Profile Use the Tivoli Enterprise Portal ISM Configuration Tool to: 1.Add monitor types 2.Add, remove, configure and modify element’s 3.Set profile schedule 4.Define distribution - assign the profile to many hosts, or a host to many profiles 5.Create, modify and delete profiles

© 2009 IBM Corporation22 Profile Editor

© 2009 IBM Corporation23 Create Profile  In the Input Profile Name dialog, enter the name of your profile and click OK.  The profile will appear in the profiles pane of the Internet Service Monitoring Configuration Editor

© 2009 IBM Corporation24 Profile Scheduling  To associate a schedule that will deactivate monitoring between 11 p.m. and 1 a.m.with the profile, click the Scheduling tab after selecting your profile.  Click the box indicating Sunday 1:00 am and keep the mouse button depressed.  Drag your mouse to the right and slightly down until you reach the square that indicates Saturday at 11:00pm (23:00), then release it.  When you release the mouse button, the selected interval will be highlighted.  Click apply to save your changes.

© 2009 IBM Corporation25 Profile Element  To add an ICMP element, select ICMP from the menu in the Add monitor type to profile section and click Add.  In the element dialog, click the server field and type AppServer. The field stays grayed out until you start typing.  When you click the description field, the description is automatically filled in and the element is automatically activated.

© 2009 IBM Corporation26 Service Level Classification  Service level classifications are optional monitor parameters that can be applied to all monitors. They define the rules used by monitors to evaluate how well a monitored service is performing. The results form the basis for service level agreements (SLAs) evaluation.  The screen capture shows how service level classifications appear in the default ICMP configuration.

© 2009 IBM Corporation27 Deploy Profile  Select the system in the Available Systems group  Click the right arrow to move the selected system to the Deployed Systems group  Click Apply to save your changes and deploy the profile to the agent  Click OK to dismiss the ISM Configuration dialog  Confirm that the profile element has been distributed to ITM –Locate the icmp.xml file –Check the “last modified” date and time –Open file and review ICMP element settings

© 2009 IBM Corporation28 View Profile Data

© 2009 IBM Corporation Backup and Restore  29