60 IBM Enterprise Workload Manager
3.3 Enabling DB2 Universal Database for ARM
Instrumenting DB2 Universal Database on each operating system platform is done in a very
similar way, but there are some differences. Therefore, we describe the steps for each
platforms separately.
AIX
Instrumenting DB2 Universal Database on AIX includes these steps:
1. Set AIX authorization attributes.
2. Set DB2 variable.
Set AIX authorization attributes
On AIX, the ARM platform support uses the native OS security model. In order for an
application to ARM register itself, you have to add two capabilities,
CAP_ARM_APPLICATION and CAP_PROPAGATE, to the user profile of the instance owner
who runs the application. The root user automatically has all of the capabilities but not the
DB2 instance owner, for example, db2inst1. To provide the capabilities to the DB2 instance
owner:
1. Log in as root user.
2. Start a terminal session.
3. Add the capabilities to the DB2 instance owner ID db2inst1 using chuser and verify it
using lsuser. Follow the sequence shown in Example 3-1.
Example 3-1 Add ARM related capabilities to user db2inst1
root@ewlm4:/> chuser “capabilities = CAP_ARM_APPLICATION,CAP_PROPAGATE” db2inst1
root@ewlm4:/> lsuser db2inst1
db2inst1 id=106 pgrp=db2grp1 groups=db2grp1,staff,dasadm1 home=/home/db2inst1 sh
ell=/usr/bin/ksh login=true su=true rlogin=true daemon=true admin=false sugroups
=ALL admgroups= tpath=nosak ttys=ALL expires=0 auth1=SYSTEM auth2=NONE umask=22
registry=files SYSTEM=compat logintimes= loginretries=0 pwdwarntime=0 account_lo
cked=false minage=0 maxage=0 maxexpired=-1 minalpha=0 minother=0 mindiff=0 maxre
peats=8 minlen=0 histexpire=0 histsize=0 pwdchecks= dictionlist= capabilities=CA
P_ARM_APPLICATION,CAP_PROPAGATE fsize=-1 cpu=-1 data=491519 stack
=32767 core=-1 rss=-1 nofiles=2000 time_last_login=1086381962 tty_last_login= ho
st_last_login=ewlm4 unsuccessful_login_count=0 roles=
4. Verify the user’s capabilities at the /etc/security/user file as shown in Example 3-2.
Verify operating system
instrumentation
X
2
X
2
X
2
Verify communication between
domain manager and managed server
X
2
X
2
X
2
X
2
1
Refer to 2.4, “EWLM configuration in our ITSO environment” on page 32, 2.5, “Installing the domain manager on other
operating systems” on page 50 and 4.1, “EWLM Control Center overview” on page 78 for details.
2
Refer to 2.4, “EWLM configuration in our ITSO environment” on page 32 and 2.6, “Configuring managed servers on
other operating systems” on page 54 for details.
Host name ewlmdm1 ewlm1 ewlm2, ewlm3 ewlm4
Role Domain manager Web server Application server Database server
Chapter 3. Enabling middleware for EWLM 61
Example 3-2 Verify user’s capabilities
root@ewlm4:/> grep -p db2inst1 /etc/security/user
db2inst1:
admin = false
umask = 22
capabilities = CAP_ARM_APPLICATION,CAP_PROPAGATE
Set DB2 variable
In order for a DB2 instance to call the ARM instrumented APIs, set DB2 variable:
1. Log in as the DB2 instance owner db2inst1:
root@ewlm4:/> su - db2inst1
2. Set the DB2LIBPATH variable and verify it using the db2set command as shown in
Example 3-3.
Example 3-3 Set the DB2LIBPATH and verify the DB2 variables on AIX
$ db2set DB2LIBPATH=/usr/lib
$ db2set
DB2_RR_TO_RS=YES
DB2LIBPATH=/usr/lib
DB2COMM=tcpip
DB2AUTOSTART=YES
3. Restart the DB2 instance as shown in Example 3-4.
Example 3-4 Restart DB2 instance on AIX
$ db2 force applications all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.
$ db2 terminate
DB20000I The TERMINATE command completed successfully.
$ db2stop
06-07-2004 14:14:03 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
$ db2start
06-07-2004 14:14:07 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
i5/OS
ARM is enabled on DB2 UDB by default. No other configuration of DB2 is required.
Windows
Instrumenting DB2 Universal Database on Windows includes these steps:
1. Verify the DB2 instance user group.
2. Set the DB2 variable.
Verify the DB2 instance user group
The user that is running the DB2 instance process should be a member of the eWLMArm4Users
or Administrators group. The DB2 instance user is added to the Administrators group by
DB2 installer automatically, but you have to check it using following sequence:
1. Click Start
→ Setting → Control Panel → Users and Password.
62 IBM Enterprise Workload Manager
2. Verify db2admin belongs to the Administrators group as shown in Figure 3-1.
Figure 3-1 db2admin group membership
Verify DB2 variables
ARM is enabled on DB2 UDB by default, so the DB2 instance should be able to register to
ARM. You might still want to verify that the following DB2 variables are set properly and if not,
then they need to be set to the correct values:
1. Log in as the DB2 instance owner db2admin.
2. Verify using the db2set command. Click Start
→ Run, type db2cmd, click OK, and follow
the sequence shown in Example 3-5.
Example 3-5 Set and verify DB2 variables on Windows Server 2003
C:Documents and Settingsdb2admin>db2set
DB2SATELLITEID=ITSOTOT54
DB2ACCOUNTNAME=TOT54db2admin
DB2INSTOWNER=TOT54
DB2PORTRANGE=60000:60003
DB2_GRP_LOOKUP=LOCAL
DB2INSTPROF=C:PROGRA~1IBMSQLLIB
DB2COMM=TCPIP
3. If you change any of the variables, you then need to restart the DB2 instance as illustrated
in Figure 3-2.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.