Chapter 2. Installing and configuring EWLM 51
and further issues if your domain manager is on other supported operating systems. This is
the focus of the following sections.
2.5.1 Domain manager on AIX
The configuration of the domain manager on AIX is very similar to the Linux configuration.
EWLM. On AIX you need to create a CDROM file system first using the smitty crcdrfs
command. Insert the first CD, labeled “VE Console & Runtime for AIX 5L (1 of 3)” and mount
the CDROM file system. The mount point in our example is /cdrom. Change to this directory
and look at the ls command output. The sequence of steps looks as follows:
# mount /cdrom
# cd /cdrom
# ls
Common/ VEInstall.ico installVECore.jar*
EWLM/ installVE.jar* log.txt
VEC/ installVEAgents.jar* uninstallVEAix.sh*
VECoreLog.txt installVEAix.sh*
The following command executes the installVEAix script and the Virtualization Engine
wizard appears on your screen:
# ./installVEAix.sh
Alternatively, you can mount the CDROM and launch autorun to start the installation. Use the
mount -v cdrfs -oro /dev/cd0 /mnt command to mount the CD. Launch the installation
program by typing the /mnt/autorun command. Autorun creates temporary directories, copies
the setup file from the CD to the temporary directory and launches the installVEAix.sh
script.
The space required for the installation directory /opt/IBM/VE is about 500 MB. The required
space for the installation directory for all operating systems is shown in Table 1-1 on page 17.
At the time of writing you must be root user to install EWLM code and to run WebSphere
Application Server and the domain manager. This is due to WebSphere requirements which
we explained in the first part of this chapter.
2.5.2 Domain manager on Windows
When you set up your domain manager on Windows you start by copying the installation
images to your server as we described in 2.3, “Virtualization Engine suite” . The CDs you
need for running domain manager on Windows are labeled “VE Console & Runtime for
Windows (N of 3).”
The configuration commands and associated log files are located at C:Program
FilesIBMVEEWLMin. To create the domain manager on Windows you can either issue the
command sequence described in “Configuring domain manager using command line” on
page 34 or you can call a configuration wizard as shown in “Configuring domain manager
using the wizard” on page 38.
If you want to run the WebSphere Application Server and the domain manager as user
Administrator you can immediately start the configuration. If you want to create another user
to run these commands, you need to make sure that this user has the right operating system
privileges. For example, create a user ibmewlm as a member of the administrative group with
the following privileges:
? Act as part of the operating system
? Log on as a service
52 IBM Enterprise Workload Manager
We log into our Windows machine as user Administrator and follow this procedure:
? Click Start
→ Settings → Control Panel → Administrative Tools → Local Security
Policy
→ Local Policies → User Rights Assignments
? Click Add and assign these two privileges to ibmewlm:
– Act as part of the operating system
– Log on as a service
These steps are necessary to ensure that this userid conforms with the requirements
WebSphere sets for a WebSphere Administrator. In addition you need to create users to map
to the EWLM Control Center roles. On Windows we create users ewlmadm, ewlmops, and
ewlmmon as Standard Users.
At this point you have two choices, just as we described for the configuration of domain
manager on Linux. Creating the domain manager using the configuration wizard is very
similar to what we discussed in 2.4.1, “Configuring domain manager on Linux” . We therefore
concentrate on the important command sequence only. In Example 2-12 we outline the
command line steps you need to follow when you want to configure your domain manager on
Windows without the wizard.
Example 2-12 Outline of configuration of domain manager on Windows
Logon as Administrator:
> cd "C:Program FilesIBMVEEWLMMSin"
> createDM C:IBMEWLMDM -ma 9.12.6.143 -mp 3333 -adminUser ibmewlm -adminPW 111111
-wasPorts 20000 -jp 9092 -dn itsoewlm -auth None
# changeCC -addUser C:IBMEWLMDM -adminUser ibmewlm -adminPW 111111 -roleUser ewlmadm
-role Administrator
> changeCC -addUser C:IBMEWLMDM -adminUser ibmewlm -adminPW 111111 -roleUser ewlmops
-role Operator
> changeCC -addUser C:IBMEWLMDM -adminUser ibmewlm -adminPW 111111 -roleUser ewlmmon
-role Monitor
Logon as ibmewlm:
> cd "C:Program FilesIBMVEEWLMMSin"
> startWAS C:IBMEWLMDM
> startDM C:IBMEWLMDM
Once you are comfortable with the startDM command, we recommend running this process
as a service by using the startDMService.bat command. This is also the recommended way
to run it into a production environment.
If you want to map several users to the -role Administrator flag, for example, the command
syntax is slightly different than what we showed for Linux. You can specify multiple users by
separating the users with the colon character and surrounding the list with double quotes as
follows:
>cd "C:Program FilesIBMVEEWLMMSin"
>changeCC -addUser C:IBMEWLMDM -adminUser ibmewlm -adminPW 111111 -roleUser
"ewlmadm1:ewlmadm2:ewlmadm3" -role Administrator
Log files associated with these creation commands are in the same directory. Log files
associated with the WebSphere Application Server are at C:IBMewlmDMWASlogsserver1
as well as at C:Program FilesIBMVEWebSphereAppServerlogsserver1.
If all commands completed successfully you are now ready to start your browser and log on to
the EWLM Control Center.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.