IBM Enterprise Workload Manager Release 1

46 IBM Enterprise Workload Manager

Linux domain manager at /opt/EWLMDM/WAS/logs/server1 and are called SystemOut.log

and SystemErr.log.

When we log in to the EWLM Control Center now and look at the managed servers in the

monitoring section on the left we do not see any servers. The domain manager does not

detect any managed servers because there are no managed servers that have joined this

domain yet.

2.4.2 Configuring managed servers on AIX and Windows

Once our domain manager is running we are ready to install and configure the managed

servers that belong to the EWLM management domain. In our ITSO environment, the EWLM

Management Domain consists of two systems running AIX 5L Version 5.2 ML03, and two

systems running Windows Server Version 2003. For information on the installation and

configuration of managed servers running other supported operating systems refer to 2.6.1,

“Managed server on i5/OS” and to 2.6.2, “Managed server on Solaris” . In this section we

describe the setup of the managed servers of our ITSO environment only. On Windows we do

not configure and run the managed server as Administrator but as user tested. On AIX we

show the configuration as root user even though it is not required. The managed server must

be able to call the EWLM APIs, which require either root authority or that you use a non-root

user like ibmewlm and grant authority by typing the following command:

chuser capabilities=CAP_EWLM_AGENT,CAP_PROPAGATE ibmewlm

When you install the EWLM code on the domain manager you are also given the option to

install the images for the managed servers. This means that the code for the managed

servers is copied to your domain manager but it does not get pushed out to the managed

servers automatically. You need to manually transfer the EWLM managed server code from

the domain manager to each managed server. This distribution of managed server images

can be done either by file transfer protocol (FTP) using binary mode on AIX and Solaris, or by

mapping a drive and copying the files to the file system, or by any other distribution

mechanism that works in your environment. Be aware that FTP does not maintain the

executable bit on the installation image file. You need to run chmod 700 on the installation

image to turn on the executable bit.

The managed server code location on the domain manager is a subdirectory of your

installation directory; on our domain manager it is at /opt/IBM/VE/ManagedNodes. For the

current release of EWLM, the IBM installation image includes AIX and i5/OS. The non-IBM

installation image includes images for Windows and Solaris. Which image will be in your

domain manager directory depends on what you have purchased. You can identify which

image goes with which platform by the names of the installable files, which are as follows:

򐂰 AIX - EWLMAixMS.bin

򐂰 Windows - EWLMWinMS.exe

򐂰 Solaris - EWLMSolarisMS.bin

򐂰 i5/OS - EWLMOS400MS.jar and Q5733VE1110.savf

We explain in 2.6.1, “Managed server on i5/OS” why you need two files for a managed server

installation on i5/OS.

Installing managed server code

In our ITSO environment, the managed servers are Windows and AIX machines which

means we need the files called EWLMWinMS.exe and EWLMAixMS.bin. We transfer these files to

our managed servers into the /software/EWLM directory, which can be a location of your

choice. Make sure the rights are set so the files can be executed. We start the installation