ibm systems group © 2004 ibm corporationv 3.04 ibm confidential: this presentation is intended for...

IBM Systems Group

© 2004 IBM Corporationv 3.04

IBM Confidential: This presentation is intended for the education of IBM and Business Partner sales personnel. It should not be distributed to customers.

IBM Enterprise Workload ManagerVirtualization V2R1 Education: Configuration

Tom Schuler

September 2005

IBM Systems Group

© 2004 IBM CorporationIBM Confidential

page 2IBM Confidential: Template Version 3.05 IBM Systems Group Field Skills & Education

Agenda

Topics to be covered are:– Changes to configuration commands for EWLM V2R1

Assumption: Knowledge of EWLM V1R1 configuration concepts and commands

IBM Systems Group



Learning Objectives

At the conclusion of this material, you should be able to: – Understand changes to configuration commands

– Gather debug information in EWLM V2R1 environment

IBM Systems Group



Overview of Changes– Install – Config– ConfigWizard

IBM Systems Group



Install Changes

Panel ID on EWLM domain manager panels

Help button available on EWLM domain manager installs

Allow install of EWLM managed server via RPD or IBM Director within VE

EWLM managed server can be installed in console or silent mode

EWLM domain manager does not support console mode, but does support silent mode via VE suite installer silent mode install

EWLM installer / uninstaller logs are placed into the user’s home directory

IBM Systems Group



Config Changes

– Use of configID rather than working directory on all platforms– EWLM runs in background– Configuration code now done in Java (with script front-ends)– Security of EWLM user data and configuration logs– Support of z/OS domain manager– Interaction with VE– Location of EWLM configuration logs moved– Support for single system EWLM has been removed– No migration commands from EWLM V1R2 to V2R1– All messages now have message IDs. Also, where appropriate,

suggested action is provided.

IBM Systems Group



Configuration Wizard

Certain functions no longer available in the wizard. This is mainly the removal of setting trace options. Function still available via configuration commands.

Improved error handlingAdding users / groups to a role is now available as part of

creating an EWLM domain managerDuring creation of the EWLM domain manager, you can now

specify that the ELWM Control Center and the EWLM domain manager be started once configuration is complete.

IBM Systems Group



ConfigID

EWLM V1R1– OS/400 identified the user data for an EWLM instance via configID– All other platforms identified the user data by providing path to working

directory

EWLM V2R1– All platforms use configID to identify the user data for an EWLM

instance– The configID identifies a subdirectory within the

EWLM_DATA_ROOT/servers directory. – EWLM_DATA_ROOT is selected during install. Default value is

provided specific to OS platform which user can modify.

IBM Systems Group



EWLM runs in background

Windows – EWLM and WebSphere run as Windows service

Unix – EWLM and WebSphere run in the background as forked process. – stopXX commands implemented to stop background process

i5/OS – runs as a submitted job (same as EWLM V1R1)

IBM Systems Group



Windows Service for EWLM

EWLM and WebSphere / EWLM Control Center now always run as a Windows Service

Separate commands for Windows service usage have been eliminated. Function has been merged into startXX commands

stopXX commands stop the Windows Service

IBM Systems Group



Start EWLM DM as a Windows Service

startXX configID [-initHeap number] [-maxHeap number] [-autostart {YES or NO}]

startXX command options:

workingDir Working directory for the EWLM Domain Manager.

-initHeap number Initial size of heap allocated (in megabytes) to the EWLM Domain Manager. The default value is 128.

-maxHeap number Maximum size of heap allocated (in megabytes) to the EWLM Domain Manager. The default value is 512.

-autostart [YES | NO] YES starts this service automatically on server startup. If not specified, the current autostart value associated with this Windows service is used.

IBM Systems Group



Start WebSphere as a Windows ServicestartWAS configID [-autostart {YES or NO} -adminUser userID –adminPW password]

startWAS command options: configID Configuration ID for an EWLM domain manager instance.

-autostart [YES | NO] YES starts this service automatically when the server is started. NO indicates the the service is not started when the server is started. If this parameter is not specified, the current autostart value associated with this Windows service is used. The -adminUser and -adminPW parameters identifying the WebSphere administrator are required when -autostart is specified.

-adminUser userID UserID of the user that administers the WebSphere Application Server.

-adminPW password The password associated with the -adminUser parameter.

IBM Systems Group



Start EWLM MS & FB as a Windows Service

startXX configID [-autostart [YES | NO]]

startXX command options:

workingDir Working directory for the EWLM Domain Manager.

-autostart [YES | NO] YES starts this service automatically on server startup. If not specified, the current autostart value associated with this Windows service is used.

IBM Systems Group



Stop EWLM as a Windows Service

stopXX configID

stopXX command options:

configID Configuration ID for an EWLM instance.

IBM Systems Group



EWLM Unix background process

startXX commands save process ID and process start time in file named: EWLM_DATA_ROOT/servers/configID/ewlm_process.data

stopXX command examines ewlm_process.data and kills process if the process ID exists and that process has the same start time

IBM Systems Group



Configuration code in JavaEach configuration command has a small script that sets up the environment and starts the java program for that configuration command

Code written in Java for following reasons:

Use standard Java approach for translation of messages

More robust error checking

Better debug logging

IBM Systems Group



Security

createXX commands secure the working directory associated with the configID.

All configuration commands secure the EWLM configuration log files as they are created.

IBM Systems Group



z/OS domain manager

Separate scripts for creating WebSphere instance for use with EWLM

createDM syntax slightly different:– wasPorts parameter is removed. Ports are set up with z/OS scripts

for setting up WebSphere– -wasProfile parameter is new. Value is the path containing the

WebSphere instance created with the scripts.

IBM Systems Group



Interaction with VE

VE Console– Launchpad– GCR

VE Health Console Bridge for EWLM

IBM Systems Group



Debug logging changes – EWLM V1R1

Log file placed in bin directory containing configuration commands

Only last invocations of command has log. Previous invocations logs are overwritten.

Only one log file shared by each changeCC and displayCC command

IBM Systems Group



Debug logging changes – EWLM V1R2

Configuration commands:

Log file placed in separate directory labeled LOGFILE_ROOT

Logs for several invocations of each command are retained

Automatic pruning of LOGFILE_ROOT limits number of logs retained

Commands that involve WebSphere copy WebSphere logs if a failure is detected.

New file named config.log in LOGFILE_ROOT contains a history of all successful configuration commands.

Configuration wizard:– Log file of all invocations of confugration commands from last

invocation of wizard– Name of log file: ConfigurationWizard.log– Log file in LOGFILE_ROOT/ConfigurationWizardDiagnostics

IBM Systems Group



Debug Information (con’t)

EWLM components (Domain Manager, et al)– System console log named: System.log. Resides in EWLM working

directory– If log fills up, swaps with Previous.log. Otherwise Previous.log

contains messages from previous invocation of EWLM instance.– System diagnostic dumps are located in Diagnostics subdirectory in

the EWLM working directory

WebSphere– Logs are contained in the WebSphere logs subdirectory and the

logs/<server> subdirectory

IBM Systems Group



Debugging WebSphere problemsEWLM creates WebSphere profiless that support the WebSphere admin console.

Ports for running the console can be displayed using the displayCC –ports command

wsadmin command is available in WebSphere bin directory. The command has the following format:

wsadmin –conntype SOAP –port <SOAPport> -user <adminUser> -password <adminPW>

where:– <SOAPport> is the SOAP port for the WebSphere instance. This can be determined by using displayCC –

ports command– <adminUser> is the WebSphere administrator provided to the –adminUser property on the EWLM

configuration commands– <adminPW> is the WebSphere administrator’s password provided to the –adminPW property on the EWLM

configuration commands

Look at the xml files in the config subdirectory tree of associated WebSphere profile.

IBM Systems Group



Conclusion / Wrap-up

EWLM provides a complete set of configuration commands to setup EWLM domains, modify them as needed, and then delete EWLM components.

EWLM provides a configuration wizard GUI that supports most of the function available in the configuration commands.

EWLM configuration allows you to handle security of EWLM and to handle firewalls within your EWLM domain.

Various log files are available to help debug problems you may encounter.

IBM Systems Group



Additional Resources

EWLM V1R1 Configuration education presentation

EWLM Configuration Wizard online help

eServer Information Center

IBM Enterprise Workload Manager Redbook (SG24-6350-00)

IBM Systems Group



NoticesProduced in the United States of America, 08/04, All Rights ReservedIBM, IBM eServer logo, IBM logo, e-business on demand, DB2, DB2

Connect, DB2 Universal Database, HiperSockets, Enterprise Storage Server, Performance Toolkit for VM, Tivoli, TotalStorage, VM/ESA, WebSphere, z/OS, z/VM and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel is a trademark of Intel Corporation in the United States, other countries or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation

Other company, product and service names may be trademarks or service marks of others.

IBM Systems Group



Notices – cont’dInformation concerning non-IBM products was obtained from the suppliers of

their products or their published announcements. Questions on the capabilities of the non-IBM products should be addressed with the suppliers.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.

All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios

IBM Systems Group



End Of Presentation

ibm systems group © 2004 ibm corporationv 3.04 ibm confidential: this presentation is intended for...

Documents