Chapter 2. Installing and configuring EWLM 53
2.5.3 Domain manager on i5/OS
Installing the EWLM code when your domain manager runs on i5/OS cannot be done directly.
For this you need to use the iSeries™ Access family of products to administer and access
your iSeries server. In our ITSO environment we use IBM eServer iSeries Access for
Windows. This means, the installation of the Virtualization Engine base support and EWLM
code works as on Windows. However, you need to insert the CD labelled “VE Console &
Runtime for OS/400® (1 of 3)” into your Windows PC; this automatically launches the
installation wizard on the Windows PC. For the first screen you need to provide the i5/OS
server name and login information. The installation of WebSphere Application Server takes a
lot longer than on the other operating systems we discussed in this chapter. You may find that
it takes up to two hours.
Once the EWLM code and WebSphere Application Server are installed on the i5/OS we need
to log on to the system. We run the STRWLM CL command with the following options:
# STRWLM CFGID(ewlmadm) MODE(*DMNMGR) DMNMGRNAME("9.56.204.66") DOMAIN(itsoewlm)
DMNMGRPORT(9092)
All configuration scripts require the EWLM configuration ID as a parameter. This allows all
information associated with a specific instance of an EWLM component to be easily found.
The ID is created by running the STRWLM CL command, which creates a directory under
/qibm/userdata/wlm/servers/<configID>. It contains all EWLM-related information. In addition,
it is used to name the WAS instance and causes the WebSphere data to be placed in a
directory called /qibm/userdata/webas51/base/<configID>.
The WebSphere Application Server instance is created using the createCC command. For
this to run we issue the qsh command to be able to run shell commands. We run the
command sequence as shown:
# cd /qibm/proddata/wlm/bin
# createCC ewlmadm -adminUser qsecofr -adminPW 111111 -wasPorts 20000 -jp 9092
For the configID parameter we take ewlmadm. It uniquely identifies the domain manager server
job and must be the value you passed on the STRWLM CL command. The adminUser is used as
WebSphere administrator and must conform with the requirements WebSphere sets.
However, for i5/OS there are no special requirements for WebSphere Application Server. To
install and configure EWLM the system administrator needs to have *ALLOBJ, *SECADM,
*JOBCTL, and *IOSYSCFG special authority. In our test setup we used the administration
user qsecofr.
The next step is to map users to the specific EWLM roles. These users must be created first
on the operating system. We can then issue the changeCC command with the arguments
shown in Example 2-13. Run the startWAS command and open a browser to the EWLM
Control Center as described for our ITSO environment. You should be able to log on as one of
the users specified here.
Example 2-13 Configure EWLM on i5/OS domain manager
# cd /qibm/proddata/wlm/bin
# changeCC -addUser ewlmadm -adminUser qsecofr -adminPW 111111 -roleUser ewlmadm -role
Administrator
# changeCC -addUser ewlmadm -adminUser qsecofr -adminPW 111111 -roleUser ewlmops -role
Operator
# changeCC -addUser ewlmadm -adminUser qsecofr -adminPW 111111 -roleUser ewlmmon -role
Monitor
# ./startWAS.sh ewlmadm

Get IBM Enterprise Workload Manager Release 1 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.