Chapter 3. Enabling middleware for EWLM 69
13.Enable
anonymous access and enter the built-in account for anonymous access:
(IUSR_%COMPUTER_NAME%). Click OK.
14.Select the Home Directory tab on the Properties sheet. At the bottom, select the
Application pool that you just created, and click OK.
15.Select Start
Settings Control Panel Administrative Tools Computer
Management
Local Users and Groups Groups eWLMArm4Users Add
Advanced Find Now SERVICE OK.
16.Restart the IIS plug-in after the updates have been made.
3.6 Verifying application enablement
Each platform has its own verification command.
AIX
You can verify that instrumentation has been enabled using the lsarm command:
$ lsarm -a
The command may print the following ARM registered applications:
APPL: IBM DB2 Universal Database
APPL: WebSphere
APPL: IBM Webserving Plugin
APPL: Apache HTTP Server
i5/OS
You can verify that instrumentation has been enabled by looking at the job in question. If it
has ARM calls, it will have QPMWARM4 activation group active.
Windows
The ewlmWinAdTool command allows you to verify the applications registered to the ARM
interface. Click Start
Run..., type cmd, click OK, and follow the sequence shown in
Example 3-8.
Example 3-8 ewlmWinAdTool output
cd /d "%EWLMMS_HOME%classesms"
C:Program FilesIBMVEEWLMMSclassesms>ewlmWinAdTool ARM4PsInfo
Windows Platform Administrative and Diagnostic Tool for EWLM
Ver. 1.00.0130.4230 *
EWLM V1R1.0 (C) Copyright IBM Corporation, 2004.
>>> ARM4PsInfo: 3 process(es) is doing ARM instrumentation...
pid +|- gupid(hex) #ARs #TRs #AIs #TIs #TBs
-------- --- -------------------------- ---- ---- ---- ------- -------
1600 [+] 8C096030.01C44D9B.00000640 : 1/64 1/64 1/256 0/16384 0/16384
AR[00]: E39D49C700000000h (IBM Webserving Plugin)
TR[00]: E39D4A0F00000000h (WebRequest)
.APP: (IBM Webserving Plugin) E39D49C700000000h
AI[00]: D794770C00000000h (aiid=D794770Ch, aeid=BFE900C800000000h)
.GRP: (IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Win32))
.INS: (TOT54/PID= 1600)
.APP: (IBM Webserving Plugin) E39D49C700000000h
70 IBM Enterprise Workload Manager
pid +|- gupid(hex) #ARs #TRs #AIs #TIs #TBs
-------- --- -------------------------- ---- ---- ---- ------- -------
1316 [+] E22AC5A0.01C44DA1.00000524 : 2/64 2/64 2/256 0/16384 0/16384
AR[00]: E2D1578000000000h (IBM DB2 Universal Database)
AR[01]: 0000000000000000h (N/A)
TR[00]: E2D157C800000000h (SQL)
.APP: (IBM DB2 Universal Database) E2D1578000000000h
TR[01]: E2D1578100000001h (IBM DB2 Universal Database)
.APP: (N/A) 0000000000000000h
AI[00]: D794770E00000000h (aiid=D794770Eh, aeid=BFE900CA00000002h)
.GRP: (DB2)
.INS: (5)
.APP: (IBM DB2 Universal Database) E2D1578000000000h
AI[01]: D794770F00000001h (aiid=D794770Fh, aeid=BFE900CA00000002h)
.GRP: (DB2)
.INS: (6)
.APP: (IBM DB2 Universal Database) E2D1578100000001h
pid +|- gupid(hex) #ARs #TRs #AIs #TIs #TBs
-------- --- -------------------------- ---- ---- ---- ------- -------
3176 [+] 5D0958A0.01C44DA7.00000C68 : 1/64 2/64 1/256 0/16384 0/16384
AR[00]: E3644F5C00000000h (WebSphere)
TR[00]: E3644FA400000000h (EJB)
.APP: (WebSphere) E3644F5C00000000h
TR[01]: E3644F5C00000000h (WebSphere)
.APP: (IBM DB2 Universal Database) E2D1578100000001h
AI[00]: D794771000000000h (aiid=D7947710h, aeid=BFE900CB00000003h)
.GRP: (TOT54)
.INS: (TOT54.server1)
.APP: (WebSphere) E3644F5C00000000h
pid +|- gupid(hex) #ARs #TRs #AIs #TIs #TBs
-------- --- -------------------------- ---- ---- ---- ------- -------
1640 [+] 85E07D60.01C44E53.00000668 : 1/64 1/64 1/256 0/16384 0/16384
AR[00]: E3A292AE00000000h (Apache HTTP Server v2.0.42 test)
TR[00]: E3A292F600000000h (HTTP Request)
.APP: (Apache HTTP Server v2.0.42) E3A292AE00000000h
AI[00]: DC20EA9400000000h (aiid=DC20EA94h, aeid=BFE32AA200000003h)
.GRP: (IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Win32))
.INS: (TOT54/PID=1640)
.APP: (Apache HTTP Server v2.0.42) E3A292AE00000000h
Solaris
You can verify instrumentation using the lsarm command:
$ lsarm -a
The command may print the following ARM registered applications:
APPL: IBM DB2 Universal Database
APPL: WebSphere
APPL: IBM Webserving Plugin
APPL: Apache HTTP Server
For the DB2 environment, another way to verify the instrumentation (at a lower level) is to turn
on tracing with DB2 and make sure that the ARM libraries are loaded by entering the
following sequence of commands:
db2stop
db2trc on -f /tmp/DB2-trace.trc
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset