IBM Tivoli Monitoring Version 5.1.1 Creating Resource Models and Providers Sg246900

7/31/2019 IBM Tivoli Monitoring Version 5.1.1 Creating Resource Models and Providers Sg246900

1/539


2/539


3/539


4/539


5/539


6/539


7/539


8/539


9/539


10/539


11/539


12/539


13/539


14/539


15/539


16/539


17/539


18/539


19/539


20/539


21/539


22/539


23/539


24/539


25/539


26/539


27/539


28/539


29/539


30/539


31/539


32/539


33/539


34/539


35/539


36/539


37/539


38/539


39/539


40/539


41/539


42/539


43/539


44/539


45/539


46/539


47/539


48/539


49/539


50/539


51/539


52/539


53/539


54/539


55/539


56/539


57/539


58/539


59/539


60/539


61/539


62/539


63/539


64/539


65/539


66/539


67/539


68/539


69/539


70/539


71/539


72/539


73/539


74/539


75/539


76/539


77/539


78/539


79/539


80/539


81/539


82/539


83/539


84/539


85/539


86/539


87/539


88/539


89/539


90/539


91/539


92/539


93/539


94/539


95/539


96/539


97/539


98/539


99/539


100/539


101/539


102/539


103/539


104/539


105/539


106/539


107/539


108/539


109/539


110/539


111/539


112/539


113/539


114/539


115/539


116/539


117/539


118/539


119/539


120/539


121/539


122/539


123/539


124/539


125/539


126/539


127/539


128/539


129/539


130/539


131/539


132/539


133/539


134/539


135/539


136/539


137/539


138/539


139/539


140/539


141/539


142/539


143/539


144/539


145/539


146/539


147/539


148/539


149/539


150/539


151/539


152/539


153/539


154/539


155/539


156/539


157/539


158/539


159/539


160/539


161/539


162/539


163/539


164/539


165/539


166/539


167/539


168/539


169/539


170/539


171/539


172/539


173/539


174/539


175/539


176/539


177/539


178/539


179/539


180/539


181/539


182/539


183/539


184/539


185/539


186/539


187/539


188/539


189/539


190/539


191/539


192/539


193/539


194/539


195/539


196/539


197/539


198/539


199/539


200/539


201/539


202/539


203/539


204/539


205/539


206/539


207/539


208/539


209/539


210/539


211/539


212/539


213/539


214/539


215/539


216/539


217/539


218/539


219/539


220/539


221/539


222/539


223/539


224/539


225/539


226/539


227/539


228/539


229/539


230/539


231/539


232/539


233/539


234/539


235/539


236/539


237/539


238/539


239/539


240/539


241/539


242/539


243/539


244/539


245/539


246/539


247/539


248/539


249/539


250/539


251/539


252/539


253/539


254/539


255/539


256/539


257/539


258/539


259/539


260/539


261/539


262/539


263/539


264/539


265/539


266/539


267/539


268/539


269/539


270/539


271/539


272/539


273/539


274/539


275/539


276/539


277/539


278/539


279/539


280/539


281/539


282/539


283/539


284/539


285/539


286/539


287/539


288/539


289/539


290/539


291/539


292/539


293/539


294/539


295/539


296/539


297/539


298/539


299/539


300/539


301/539


302/539


303/539


304/539


305/539


306/539


307/539


308/539


309/539


310/539


311/539


312/539


313/539


314/539


315/539


316/539


317/539


318/539


319/539


320/539


321/539


322/539


323/539


324/539


325/539


326/539


327/539


328/539


329/539


330/539


331/539


332/539


333/539


334/539


335/539


336/539


337/539


338/539


339/539


340/539


341/539


342/539


343/539


344/539


345/539


346/539


347/539


348/539


349/539


350/539


351/539


352/539


353/539


354/539


355/539


356/539


357/539


358/539


359/539


360/539


361/539


362/539


363/539


364/539


365/539


366/539


367/539


368/539


369/539


370/539


371/539


372/539


373/539


374/539


375/539


376/539


377/539


378/539


379/539


380/539


381/539


382/539


383/539


384/539


385/539


386/539


387/539


388/539


389/539


390/539


391/539


392/539


393/539


394/539


395/539


396/539


397/539


398/539


399/539


400/539


401/539


402/539


403/539


404/539


405/539


406/539


407/539


408/539


409/539


410/539


411/539


412/539


413/539


414/539


415/539


416/539


417/539


418/539


419/539


420/539


421/539


422/539


423/539


424/539


425/539


426/539


427/539


428/539


429/539


430/539


431/539


432/539


433/539


434/539


435/539


436/539


437/539


438/539


439/539


440/539


441/539


442/539


443/539


444/539


445/539


446/539


447/539


448/539


449/539


450/539


451/539


452/539


453/539


454/539


455/539


456/539


457/539


458/539


459/539


460/539


461/539


462/539


463/539


464/539


465/539


466/539


467/539


468/539


469/539


470/539


471/539


472/539


473/539


474/539


475/539


476/539


477/539


478/539


479/539


480/539


481/539


482/539


483/539

460 IBM Tivoli Monitoring: Creating Resource Models and Providers

Figure 11-16 Resource Model Wizard: Select a Class window

2. Select the bottom six items from the table and click on the right pointing arrowto place them in the selected table so that it looks like Figure 11-17 onpage 461 and then click Next .


484/539

Chapter 11. File monitoring Resource Model example 461

Figure 11-17 Resource Model wizard properties selection window

3. When you see the window in Figure 11-18 on page 462 , click Next , as you donot need to enter any information.


485/539


Figure 11-18 Resource Model wizard triggering conditions selection window

4. In the window shown in Figure 11-19 on page 463 , no additional informationis required, so click Next twice.


486/539


Figure 11-19 Resource Model wizard filtering selection window

5. You will now be presented with the Cycle Time window, as shown inFigure 11-20 . We chose 120 seconds as our cycle time. You may enteranything that is suitable for your environment to use a default value for yourResource Model.

Figure 11-20 Resource Model cycle time data entry panel

6. The IBM Tivoli Monitoring Workbench window will now be presented, asshown in Figure 11-21 .


487/539


Figure 11-21 IBM Tivoli Monitoring Workbench main window

11.3.1 Constructing the Resource Model: EventsIn this section, we will be opening the Events section of the monitoring tree to

create two events that we will use to send information about changes to the filesthat we are monitoring to TEC.

1. In the Events section of the monitor tree, right-click on Events and click onAdd . Enter FileChangeOnlyin InternalName field, click on the Add buttonunder attributes, and enter pathnameas a type string. Click on the Key buttonto make it a key, leave the Clearing Event box blank, and set the number ofoccurrences to one and holes to zero. In the notification panel, make sure thatSend to TEC is checked and the severity type is set to Warning. In the stringresources panel, set the descriptive name to File Change Only. The messagefield is what is displayed in the TEC console. Anything that is between two @symbols is a variable and will be substituted by the engine when the event is

dispatched to TEC. In the description field, describe when this event will betriggered. When it looks similar to Figure 11-22 , click OK .


488/539


Figure 11-22 Event construction window

2. We need to add another event. In the Events section of the monitor tree,right-click on Events and click on Add . Enter FileChangeRestored to theInternalName field, click on the Add button under Attributes, and enterpathnameas a type string. Click the Key button to make it a key, leave theClearing Event box blank, and set the number of occurrences to one andholes to zero. In the notification panel, make sure that Send to TEC ischecked and the severity type is set to Warning. In the string resources panel,set the descriptive name to File Change Restored. The message field is whatis displayed in the TEC console. Anything that is between two @ symbols is a

variable and will be substituted by the engine when the event is dispatched toTEC. In the description field, describe when this event will be triggered. Whenit looks similar to Figure 11-23 on page 466 , click OK .


489/539


Figure 11-23 Event construction window

3. Your Workbench should now have two events defined, as shown inFigure 11-24 on page 467.


490/539



11.3.2 Constructing the Resource Model: ParametersIn this section, we will define two parameters. One will contain the name andpath of the file to be monitored. The other will contain the action to take when themonitor detects that the file has changed.

1. In the Parameters section of the monitor tree, right-click on Parameters andclick on Add . Set the InternalName and DescriptiveName to ChangeAction.Set the drop-down type box to STRING LIST. Click on the Add Value buttonand enter AdviseOnly. Click on the Add Value button and enter Restore .Make sure that your Parameters dialog box looks similar to Figure 11-25 onpage 468 .


491/539


Figure 11-25 Parameter data entry window

2. In the Parameters section of the monitor tree, right-click on Parameters andclick on Add . Set the InternalName to FileList and the Descriptive Name toFiles to be checked . Set the drop-down type box to STRING LIST. Click onthe Add Value button and enter /etc/passwd .Click on the Add Value buttonand enter /etc/group . Click on the Add Value button and enter /etc/hosts .We chose these three files, but you can choose any files that are applicable toyour systems. Make sure that your Parameters dialog box looks similar toFigure 11-26 .

Figure 11-26 Parameter data entry window

3. You should now have two parameters defined under the Parameters sectionof the monitor tree, as per Figure 11-27 on page 469 .


492/539



11.3.3 Constructing the Resource Model: DependenciesIn this section we will set some dependencies that are required for eachoperating system type. You will note that the name of the dependency file for allthe Linux systems and Solaris is the same.

1. Expand all of the dependencies tree. Right-click on the All section under thedependencies tree and click on Add . A dialog box will open. Navigate towhere you saved DMXFile.mof, highlight it, and click on Open .

2. Right-click on the aix4-r1 section under the dependencies tree and click onAdd . Navigate to where you saved libDMXFile.a, highlight it, and click onOpen .

3. Right-click the hpux10 section under the dependencies tree and click on Add .Navigate to where you saved the libDMXFile.sl, highlight it, and click on

Open .

4. Right-click on the linux-ix86 section under the dependencies tree and click onAdd . Navigate to where you saved libDMXFile.so, highlight it, and click onOpen .

5. Right-click on the linux-s390 section under the dependencies tree and clickon Add . Navigate to where you saved libDMXFile.so, highlight it, and click onOpen .

6. Right-click on the solaris2 tree and click on Add . Navigate to where yousaved the libDMXFile.so, highlight it, and click on Open . You should now haved d i t f ll ti d th d d i t i


493/539


dependencies set for all sections under the dependencies tree, as inFigure 11-28 .


11.3.4 Constructing the Resource Model: Inserting codeWe have listed both the Init and the VisitTree subroutines. You may cut andpaste these sections into your Workbench Resource Models, if you choose, but

we expect that the easiest way will be to download the whole Resource Modelfrom the Redbook Web site:

http://www.ibm.com/redbooks

1. There was one special function added. It is called GetLastModDate. AsMicrosoft JavaScript does not provide any native way to access file attributes,we had to use the ActiveX object Scripting.FileSystemObject. This returns thedate last modified as a string. For details, see Example 11-1 .

Example 11-1 GetLastModDate function
http://www.ibm.com/redbookshttp://www.ibm.com/redbooks


494/539


Example 11 1 GetLastModDate function

function GetLastModDate(filespec){

var fso, f, s;fso = new ActiveXObject("Scripting.FileSystemObject");f = fso.GetFile(filespec);s = f.DateLastModified;return (s);

}

2. The Init subroutine is executed only once at the start of the Resource Model.Its basic function is to initialize variables. It needs to have some extra codeinstalled. Make sure that your subroutine looks similar to Example 11-2.

Example 11-2 Init subroutine

// This function is called by the DM For Windows Analyzer after that// the Resource Model default settings have been overridden// It is called only once, when the Resource Model is started.// You can write additional initializing code in this function if required// to use the thresholds and parameters valuesfunction Init(Svc){

Svc.Trace(2,"Start Init");var dimension = 0;var t=0;dimension= Svc.GetStrParameterCount("FileList");interpType = Svc.GetInterp();

if (dimension > 0 ) {if (interpType == "w32-ix86") {

Svc.Trace(2,"Interp is Windows");}else{

Svc.Trace(2,"Interp is Unix");Svc.AssociateParameterToClass ("FileList","File");

}} else {

Svc.Trace (0, "The Files to Be Checked parameter is empty");

return(1);}

for (k=0; k < dimension ; k++) {check [k]= -5 ;cTime [k]= -5 ;

mTime [k]= -5 ;}

S T (2 "E d I i ")


495/539


Svc.Trace(2, "End Init");return (0);

}

3. The VisitTree subroutine is executed each time the cycle time expires. It ishere that the intelligence of the Resource Model is invoked. It also needssome code inserted. Make sure that you subroutine looks is similar toExample 11-3 . This Resource Model will be available for downloading fromthe Redbooks Web site at:

http://www.ibm.com/redbooks

Example 11-3 VisitTree subroutine

// This function contains the monitoring algorithm// It is called cyclically after a cycle time has elapsed// Implement the monitoring code here

function VisitTree(Svc){Svc.Trace(2,"Start evaluate");var instancesF=0;var i=0;var j=0;var k=0;

var numsize =0;var nummodificationTime = 0;

var numchangeTime = 0;var numcrc32 = 0;

var strsize ="";var strnummodificationTime = "";var strnumchangeTime = "";var strnumcrc32 = "";

var strpathName ="";var FileAction="";var TempCmd;var curScriptResult;

var filelen= 0;var strtmp="";var flagNotFound= true;var masktemp=0;var strtmpfile="";var flagEvent = 0;

filelen = Svc.GetStrParameterCount("FileList");

var existing = new Array ( filelen );
http://www.ibm.com/redbookshttp://www.ibm.com/redbooks


496/539


var existing = new Array ( filelen );

for (k=0; k < filelen; k++) {existing[k] = 0;

}

if (interpType=="w32-ix86") {

Svc.Trace(2,"Interp is Windows in VisitTree");if (flagFirstTime){j=0;while ( j < filelen ){

Svc.Trace(3, "Its first time so just store file details and make backups" );strtmpfile = Svc.GetStrParameter("FileList", j);FileAction = Svc.GetStrParameter("ChangeAction", j);mTime[j]= GetLastModDate(strtmpfile);if (FileAction =="Restore") {

TempCmd = "cp "+strtmpfile+" "+strtmpfile+".ITMBackup";curScriptResult = Svc.Shell (TempCmd);

}j += 1;

}flagFirstTime=false;

} else {

j=0;while ( j < filelen ) {

strtmpfile = Svc.GetStrParameter("FileList", j);strpathName = strtmpfile + "";Svc.Trace(3, "File is " + strtmpfile);nummodificationTime = GetLastModDate(strtmpfile);strnummodificationTime = nummodificationTime + "";strnumchangeTime = strnummodificationTime;Svc.Trace(3, " ModTime is " + strnummodificationTime);Svc.Trace(3, "Old ModTime is " + mTime[ j] );stroldmodtime = mTime[ j] + "";FileAction = Svc.GetStrParameter("ChangeAction", j);

if ((strnummodificationTime != stroldmodtime) && (nummodificationTime != -1 )){Svc.Trace(3, "In modtime if file action= " + FileAction);

mTime[j] = nummodificationTime;if (FileAction =="Restore") {

flagEvent = 1;} else {

flagEvent = 2;}

switch ( flagEvent ) {case 1 :flagFirstTime=true;Svc SendEvent ("FileChangeRestored" strpathName );


497/539


Svc.SendEvent ( FileChangeRestored , strpathName );TempCmd = "cp "+strtmpfile+".ITMBackup"+" "+strtmpfile;curScriptResult = Svc.Shell (TempCmd);break;

case 2 :Svc.SendEvent ("FileChangeOnly", strpathName );break;

default :}}

flagEvent = 0;j += 1;

}}

}else {if (flagFirstTime){

i=0;instancesF=Svc.GetNumOfInst("File");while (i < instancesF){

numsize = Svc.GetNumProperty ("File",i,"size");nummodificationTime = Svc.GetNumProperty ("File",i,"modificationTime");numchangeTime = Svc.GetNumProperty ("File",i,"changeTime");numcrc32 = Svc.GetNumProperty ("File",i,"crc32");

strpathName = Svc.GetStrProperty ("File",i,"pathName");

strnumsize= numsize+"";strnummodificationTime = nummodificationTime+"";strnumchangeTime = numchangeTime+"";strnumcrc32 = numcrc32+"";Svc.Trace(3, "end Get attributes");

j=0;while ( j < filelen ){

strtmpfile = Svc.GetStrParameter("FileList", j);

FileAction = Svc.GetStrParameter("ChangeAction", j);if ( strpathName.equals (strtmpfile) ){existing [j] = 1;

check[ j] = numcrc32;cTime [ j]= numchangeTime;mTime[j]= nummodificationTime;j = filelen;if (FileAction =="Restore") {

TempCmd = "cp "+strtmpfile+" "+strtmpfile+".ITMBackup";curScriptResult = Svc.Shell (TempCmd);

}}j += 1;

}


498/539


}i=i+1;

}flagFirstTime=false;

} else {i=0;instancesF=Svc.GetNumOfInst("File");

while (i < instancesF) {numsize = Svc.GetNumProperty ("File",i,"size");nummodificationTime = Svc.GetNumProperty ("File",i,"modificationTime");numchangeTime = Svc.GetNumProperty ("File",i,"changeTime");numcrc32 = Svc.GetNumProperty ("File",i,"crc32");

strpathName = Svc.GetStrProperty ("File",i,"pathName");

strnumsize= numsize+"";strnummodificationTime = nummodificationTime+"";strnumchangeTime = numchangeTime+"";strnumcrc32 = numcrc32+"";

j=0;while ( j < filelen ) {

strtmpfile = Svc.GetStrParameter("FileList", j);FileAction = Svc.GetStrParameter("ChangeAction", j);if ( strpathName.equals (strtmpfile) ) {

existing [j] = 1;if (( numchangeTime != cTime[ j] ) && ( numchangeTime != -1 )) {

cTime[ j]= numchangeTime;if (FileAction =="Restore") {

flagEvent = 1;} else {

flagEvent = 2;}if ((nummodificationTime != mTime[ j] ) && (nummodificationTime !=

-1 )) {mTime[j]= nummodificationTime;

if (FileAction =="Restore") {flagEvent = 1;} else {

flagEvent = 2;}

}}if ((numcrc32 != check[j] ) && (numcrc32 != -1)) {

check[j]= numcrc32;if (FileAction =="Restore") {

flagEvent = 1;} else {flagEvent = 2;

}


499/539


}}

switch ( flagEvent ) {case 1 :

flagFirstTime=true;Svc.SendEvent ("FileChangeRestored", "", strtmpfile);

TempCmd = "cp "+strtmpfile+".ITMBackup"+" "+strtmpfile;curScriptResult = Svc.Shell (TempCmd);break;

case 2 :Svc.SendEvent ("FileChangeOnly", "", strtmpfile);break;

default :}

j = filelen;flagEvent = 0;

}j += 1;

}i=i+1;

}}

}Svc.Trace(2, "End evaluate");return (0)

}

11.3.5 The flow of the code

GetLastModDate subroutineThis subroutine uses an Microsoft ActiveX component to get the date lastmodified of any file listed in the input parameters of the Resource Model. It is

called from the VisitTree subroutine as required. ActiveX was used to avoid theJavaScript limitations with reading and opening files.

Init subroutineThe Init subroutine is always executed once per Resource Model at the start ofthe Tmw2k.exe engine. There is a little extra code for this Resource Model thatchecks that there are parameters defined. If none are defined, then the ResourceModel will return a False termination code and end. The interpreter type is alsodiscerned and stored in the variable interpType for later use in the VisitTreesubroutine.

Once this has completed, the array used for data storage is created, based uponhow many parameters are supplied.


500/539


VisitTree subroutineThis subroutine consists of a couple of loops divided by an if..else structure tosegregate the code for Microsoft Windows or Java.

The first loop is only visited on the first cycle period of the Resource Model. Hereall instances of files and their properties are checked as per the Dynamic Model.There is another internal loop that checks if it matches one of our parameter files.If it matches, our other parameter, ChangeAction, is checked. If ChangeAction isset to Restore, then a backup copy is created. The file properties are also storedin the data array.

Future iterations of the first loop are blocked by the variable FlagFirstTime beingset to false.

If FlagFirstTime is not set to False, then the second loop is executed. The firstsection of this loop is the same as the first loop. In the second section, you willnotice that various attributes of the files that match our parameters are checked.Different combinations of these attributes will produce either a Flagevent 1 or 2.Flagevent 1 will result in the an event being escalated and the file restored frombackup. Flagevent2 will only product an event, with no file restoration.

The whole process is then repeated after the cycle timer expires.


501/539


Part 3


503/539


A


504/539

Copyright IBM Corp. 2003. All rights reserved. 481

Appendix A. Testing a Java ResourceModel

This appendix describes how to test a Resource Model from a developersperspective. Since the introduction of Distributed Monitoring 4.1 AdvancedEdition, it has been possible to develop Resource Models for several platforms(also named interps) even though the Workbench shipped with ITM Version5.1.1 is only available on the Windows platform. Unfortunately, there is not aconsolidated approach to developing a Java Resource Model and testing it.

The typical development life cycle of a Java Resource Model can be describedas an interactive process based on the following steps:

Workbench development and build.

Resource Model installation in the ITM environment using the wdmrm command.

Testing by pushing the profile on the application object.

Log file analysis to find possible bugs.

ITM Engine tracing and clean-up

Note: In order to replace an existing Resource Model with a newer version ofthe same Resource Model, the version number of the new Resource Modelmust be greater than the version number of the existing Resource Model. The

wdmrmcommand will then replace the existing Resource Model with the newResource Model. If you do not update the version number, then you will haveto change the name of the new Resource Model in order to install it into yourTivoli Enterprise environment.


505/539


Before performing a log file analysis, set the log level to 3 using the wdmtrcengcommand (see Example A-1 ).

Example: A-1 wdmtrceng

wdmtrceng -e "" 3 -1

To make the interactive development process of a Resource Model easier, it isuseful to have a clean ITM Engine prior to pushing a profile containing the newversion of the Resource Model. An engine without any Resource Modelsprocesses the latest MOF files, uses the newest JavaScript, and loads theupgraded ILTs and Providers. Before removing the Resource Models from theengine, stop it with the wdmcmdcommand (see Example A-2 ).

Example: A-2 wdmcmd

wdmcmd -stop -e

Now, you should remove any Resource Models from the target engine. Acleanrm.sh script prototype removes all the Resource Models from a Java ITMEngine, specifically on the UNIX platform, and is shown in Example A-3 .

Example: A-3 The cleanrm.sh script

# removes the serialized MOF files, dont remove __namespacerm $LCFNEW/Tmw2k/Unix/data/cimom/persistence/classes/root/# removes the ilts and providers classesrm $LCFNEW/Tmw2k/Unix/Classes/com/tivoli/dmunix/ep/ilts/*.classrm $LCFNEW/Tmw2k/Unix/Classes/com/tivoli/dmunix/ep/providers/*.class#removes the javascript filerm $LCFNEW/Tmw2k/Unix/Dec/*.js# removes Resource Modelsrm $LCFNEW/Tmw2k/Unix/data/rm/*.ziprm $LCFNEW/Tmw2k/Rm/*.zip# removes the logsrm $LCFNEW/AMW/logs/*.log

rm $LCFNEW/AMW/logs/*.old# removes the profilesrm $LCFNEW/Tmw2k/Unix/data/profiles/*.dmprf

Push the profile and analyze the log files for possible bugs.

Debugging the Init functionThe script component of a Resource Model has two main functions invoked bythe service object: the Init and the VisitTree methods The Init function is


506/539

Appendix A. Testing a Java Resource Model 483

the service object: the Init and the VisitTree methods. The Init function isintended to check the parameters used by the Resource Model and associatethe parameters to a CIM class or to a CIM class property. If the Resource Modelis dependant on a parameter lists and the list(s) are empty, there may be somecases when the Resource Model is unable to start. A simple approach to

providing user feedback that explains the lack of parameter list values is to returna value between 801 and 1000. This ensures that when a profile containing aResource Model with empty parameter lists is pushed to an endpoint, the userwill get a missed prerequisites error from the wdmlseng command. As shown inthe code snippet in the Example A-4 , the Resource Model will not start unlessthere is at least one parameter that contains at least one value. In this case, thereturn value is 801, which corresponds to a missing prerequisite having a valueof 1. In case the parameter filenameDifference contains no values, the missingprerequisite will be 2 (return code 802) while the value is 3 if the parameter

contains more than that one value. Note that a different return code should beassociated to each error so that the user is able to verify the missing parameter.Edit the profile and re-distribute the profile.

Example: A-4 Using missed prerequisites return values

dimension1= Svc.GetStrParameterCount("filenameDifference");dimension2= Svc.GetStrParameterCount("filenameCRC");dimension3= Svc.GetStrParameterCount("driveletter");dimension4= Svc.GetStrParameterCount("filenamePattern");

if ( (dimension==0) && (dimension1==0) && (dimension2==0) && (dimension3==0)&&(dimension4==0) ) {

Svc.Trace(0, "IBM DMOS2FileSystem All the parameters are empty.");return 801;

}

if (dimension == 0 ) {Svc.Trace(0, "IBM DMOS2FileSystem No values specified for the filename

permission.");

return 802;}

else if (dimension == 1) {Svc.AssociateParameterToClass ("filenameP","OS2FileSystem");

} else if (dimension > 1) {Svc.Trace(0, "IBM DMOS2FileSystem Too many values in the filename

permission.");return 803;

}

If the user does not have access to the documentation describing the ResourceModel, or the Resource Model has not been thoroughly documented, a way toverify the missing parameters is to inspect the trace_dmxengine.log file.

l A 4 483 i h l k f i l d h i


507/539


Example A-4 on page 483 requires that you look for entries related to the Initfunction for the specified Resource Model (for example, DMOS2Filesystem).

To perform this task, instead of accessing the monitored machine, use theserviceability task DMCollectEPLog. It will create a user-named tar file on the

endpoint. Next, transfer the tar file to a convenient location, such as yourdevelopment machine, un-tar it, and inspect the trace_dmxengine.log. In casethere is no ftp server available on the monitored machine, it is possible to use the

wadminep command shown in Example A-5 . This command will transfer the tarfile created with the DMCollectEPLog task from the monitored machine to thelocal machine, given the local machine has the Tivoli binaries loaded to supportthe wadminep command. 1

Example: A-5 wadminep

wadminep get_file /.tar .tar

After retrieving the tar file, untar it, open the trace_dmxengine.log file with aneditor, and inspect at the log entries. In case you are working on a windowsplatform where you have installed the Workbench, use either the tar utilityavailable in the bin subdirectory of the IBM Tivoli Monitoring Workbenchinstallation directory or Winzip to decompress the file.

The only drawback to this approach consists of having to collect the log files inorder to verify the missing parameter or consult the related Resource Modeldocumentation.

A more consistent approach makes use of the ITM event to notify the user thatsomething is going wrong on the endpoint. In this case, the event is related to theResource Model itself.

Therefore, when a parameter does not contain the required values, not only doesthe Init function return a missed prerequisites value, but it sends an event as1 The wadminep command has several unsupported options, such as view_directory and remove_file .

well. This could be implemented through an EmptyParameter event (withindications 1 and holes 0), as shown in Example A-6.

Example: A-6 sendEmptyParameter function

function sendEmptyParameterEvent(Svc, paramName) {var hPropTable = Svc.CreateMap();Svc.SetMapStrElement(hPropTable,"parameter",paramName);

Svc.SendEventEx ("EmptyParameter",hPropTable);Svc.DestroyMap(hPropTable);}


508/539

Appendix A. Testing a Java Resource Model 485

A sendEmptyParameter function can be invoked in the Init before returning themissed prerequisites value, as shown in Example A-7 .

Example: A-7 Sending the EmptyParameter event

if (dimension == 0 ) {Svc.Trace(0, "IBM DMOS2FileSystem No values specified for the filename

permission.");Svc.sendEmptyParameterEvent(Svc,filenameDifference);return 802;

}

After enabling both the profile and the events themselves to be sent to the TivoliEnterprise Console (TEC), it is possible to check the Resource Model behaviorwhen there is an error in the parameters configuration. There are two ways toverify the events received from a Resource Model: either through the commandline or with the TEC.

The most useful commands to inspects the events received by TEC are:

wtdumprl Verifies whether an event has arrived or not.

wtdumper d Verifies if an event has been parsed and stored. Thisreq

Documents

IBM Tivoli Monitoring Version 5.1.1 Creating Resource Models and Providers Sg246900