Wa8551 Va8551stud

V8.
cover
Front cover
WebSphere Application
Server V8.5.5 Administration
(Course code WA855 / VA855)
Student Notebook
ERC 1.0
WebSphere Education
Student Notebook
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in
many jurisdictions worldwide:
AFS® AIX® CICS®
CloudBurst® DataPower® DB™
DB2® developerWorks® Express®
HACMP™ IMS™ Lotus®
MVS™ Notes® OS/400®
Passport Advantage® Power® RACF®
Rational® RDN® Redbooks®
Tivoli® U® WebSphere®
z/OS® zSeries®
Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in
the United States, and/or other countries.
Intel and Intel Core are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows and Windows Vista are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle and/or its affiliates.
VMware and the VMware “boxes” logo and design, Virtual SMP and VMotion are registered
trademarks or trademarks (the “Marks”) of VMware, Inc. in the United States and/or other
jurisdictions.
Other product and service names might be trademarks of IBM or other companies.
July 2013 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without
any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer
responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While
each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will
result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
© Copyright International Business Machines Corporation 2013.

This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
V8.1
Student Notebook
TOC Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Unit 1. WebSphere product family overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.1. Platform and packaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Platform and packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
WebSphere software platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
WebSphere application infrastructure: The big picture . . . . . . . . . . . . . . . . . . . . . . 1-8
WebSphere Application Server family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
WebSphere Application Server V8.5.5 packaging . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Product packaging comparison (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Product packaging comparison (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Specifications that are supported in V8.5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.2. WebSphere family products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
WebSphere family products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
WebSphere Application Server for Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
WebSphere Application Server Hypervisor Edition . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Mobile application development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
WebSphere eXtreme Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
WebSphere eXtreme Scale entitled capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
WebSphere DataPower XC10 Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
WebSphere eXtreme Scale and DataPower XC10 Appliance . . . . . . . . . . . . . . . 1-27
IBM Workload Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
IBM Tivoli Composite Application Manager for WebSphere Application Server . . 1-30
Rational Application Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
IBM Assembly and Deploy Tools for WebSphere Administration . . . . . . . . . . . . . 1-32
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Checkpoint questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Checkpoint answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Unit 2. WebSphere Application Server architecture – stand-alone . . . . . . . . . . . . . 2-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1. Architecture runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Architecture runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Version 8.5 packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
WebSphere Application Server basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
WebSphere architecture runtime (1 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
WebSphere architecture runtime (2 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
© Copyright IBM Corp. 2013 Contents iii

Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook
WebSphere architecture runtime (3 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12

WebSphere architecture runtime (10 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19
JDBC providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
Data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-21
2.2. Architecture administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-23
Architecture administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
WebSphere architecture administration (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25
2.3. Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30
WebSphere profile overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31
WebSphere profile benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32
Managing profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-33
Profile types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36
Checkpoint questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-37
Checkpoint answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-38
Unit 3. WebSphere Application Server architecture – federated. . . . . . . . . . . . . . . .3-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
3.1. Network deployment concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Network deployment concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Version 8.5 packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Network deployment concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
Network deployment runtime flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
Administration flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
File synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
WebSphere Network Deployment profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12
3.2. Managing web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13
Managing web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
Web servers within a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15
Managed versus unmanaged nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
Web server definitions (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17
Web server definitions (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18
Web server custom plugin-cfg.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
Managing plugin-cfg.xml files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
Managing web server plug-in properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21
Virtual hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
Defining virtual hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24
iv WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

V8.1
Student Notebook
TOC Managing web servers with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Unmanaged web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Managed web server on a managed node (local) . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
IBM HTTP Server as unmanaged node (remote) . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
IBM HTTP Server administration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
IBM HTTP Server administration server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
3.3. Additional concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Additional concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Flexible management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Centralized Installation Manager (CIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Intelligent runtime provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Edge Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Unit 4. IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1. IBM Installation Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
IBM Installation Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
IBM Installation Manager (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
IBM Installation Manager history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
IBM Installation Manager basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Installation Manager command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
IBM Installation Manager repository (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Remote installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.2. IBM Installation Manager installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
IBM Installation Manager installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Installing the IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Install IBM Installation Manager (1 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Install IBM Installation Manager silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.3. IBM Installation Manager: Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
IBM Installation Manager: Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Modify (add or remove) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Modify (add or remove) features (1 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
© Copyright IBM Corp. 2013 Contents v

Student Notebook
Modify (add or remove) features (4 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33

Modify (add or remove) features (5 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-34
4.4. IBM Installation Manager: Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
IBM Installation Manager: Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36
Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37
Updating the software silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38
4.5. IBM Packaging Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
IBM Packaging Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
IBM Packaging Utility (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
IBM Packaging Utility (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
Technical preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
4.6. Uninstall IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-45
Uninstall IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46
Uninstalling the IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-48
Unit 5. WebSphere Application Server installation . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
5.1. Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6
Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Installing WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
IBM WebSphere Application Server product packages . . . . . . . . . . . . . . . . . . . . .5-11
5.2. Hardware and software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15
Software requirements: Operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16
Software requirements: Web servers and database servers . . . . . . . . . . . . . . . . .5-17
5.3. Installing WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Installing WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-20
IBM Installation Manager terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21
Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
Installation GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
Shared resources directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26
Package group and installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
Features: Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
Features: Install packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31
Install WebSphere Application Server silently . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
5.4. Working with profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Working with profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36
Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-37
vi WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

V8.1
Student Notebook
TOC Starting the Profile Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

Profile Management Tool: Environment and options . . . . . . . . . . . . . . . . . . . . . . 5-39
Profile creation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Profile Management Tool: Name, location, and tuning . . . . . . . . . . . . . . . . . . . . . 5-41
Profile Management Tool: Node and host names . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Profile Management Tool: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Profile Management Tool: Security certificate (1 of 2) . . . . . . . . . . . . . . . . . . . . . 5-44
Profile Management Tool: Security certificate (2 of 2) . . . . . . . . . . . . . . . . . . . . . 5-45
Profile Management Tool: Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Profile Management Tool: Service Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Profile Management Tool: Web server definition . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Profile Management Tool: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Profile Management Tool: Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Profile creation with command-line tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
5.5. Verifying an installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Verifying an installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
Installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
5.6. Post installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Post installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
Applications installed following installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
Directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
Common command-line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
Server commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Configuration backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Accessing the information center: Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
Accessing the information center: Offline options . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Unit 6. Web server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.1. Topic: Installing IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Topic: Installing IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Web servers for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Web server plug-in installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
IBM HTTP Server: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
IBM HTTP Server: Select package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
IBM HTTP Server: License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
IBM HTTP Server: Installation directory and package group . . . . . . . . . . . . . . . . 6-12
IBM HTTP Server: Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
IBM HTTP Server: Port values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
IBM HTTP Server: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
IBM HTTP Server: Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
© Copyright IBM Corp. 2013 Contents vii

Student Notebook
6.2. Topic: WebSphere Customization Toolbox overview . . . . . . . . . . . . . . . . . . . . . . .6-17

Topic: WebSphere Customization Toolbox overview . . . . . . . . . . . . . . . . . . . . . . .6-18
WebSphere Customization Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19
WebSphere Customization Toolbox: Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20
WebSphere Customization Toolbox: Installation . . . . . . . . . . . . . . . . . . . . . . . . . .6-21
WebSphere Customization Toolbox: Selective tool installation . . . . . . . . . . . . . . .6-22
WebSphere Customization Toolbox: Features . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-23
Starting WebSphere Customization Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-24
Embedded WebSphere Customization Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . .6-25
Stand-alone WebSphere Customization Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . .6-26
WebSphere Customization Toolbox: Command line . . . . . . . . . . . . . . . . . . . . . . .6-27
WebSphere Customization Toolbox: Restrictions . . . . . . . . . . . . . . . . . . . . . . . . .6-28
6.3. Topic: Installing web server plug-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29
Topic: Installing web server plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30
Web server plug-ins: Package installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31
Web server plug-ins: License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32
Web server plug-ins: Package group and installation directory . . . . . . . . . . . . . . .6-33
Web server plug-ins: Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-34
Web server plug-ins: Summary and results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35
Plug-ins Configuration Tool: Add location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36
Plug-ins Configuration Tool: Web server selection . . . . . . . . . . . . . . . . . . . . . . . . .6-37
Plug-ins Configuration Tool: Administration server . . . . . . . . . . . . . . . . . . . . . . . . .6-38
Plug-ins Configuration Tool: Web server definition name . . . . . . . . . . . . . . . . . . . .6-39
Plug-ins Configuration Tool: Configuration scenario . . . . . . . . . . . . . . . . . . . . . . .6-40
Plug-ins Configuration Tool: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-41
Plug-ins Configuration Tool: Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43
Exercise 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46
Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47
Exercise 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-48
Exercise 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-50
Unit 7. WebSphere Application Server administrative console . . . . . . . . . . . . . . . .7-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Starting the administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Administrative console in a cell topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
Console login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
Recovering prior changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
Administrative console session timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
Administrative console panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Administrative console areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Administrative console banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
Administrative console navigation tree (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
viii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC Administrative console navigation tree (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Administrative console help (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Administrative console help (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Administrative console preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Administrative console preferences, filters, and scope . . . . . . . . . . . . . . . . . . . . . 7-18
Guided Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
My tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Troubleshooting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Tivoli Performance Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Exercise 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Unit 8. Introduction to the PlantsByWebSphere application . . . . . . . . . . . . . . . . . . 8-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
PlantsByWebSphere application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
PlantsByWebSphere sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Home page: http://<hostname>/PlantsByWebSphere . . . . . . . . . . . . . . . . . . . . . . . 8-6
Login & Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
My Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Shopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Select an item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Shopping cart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Checking out: Billing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Checking out: Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Help page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
View Server Info page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Admin home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
HTML documentation for PlantsByWebSphere (1 of 2) . . . . . . . . . . . . . . . . . . . . 8-17
HTML documentation for PlantsByWebSphere (2 of 2) . . . . . . . . . . . . . . . . . . . . 8-18
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Unit 9. Application assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
9.1. Overview of Java EE application packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Overview of Java EE application packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Overview of application assembly and installation . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Java EE 6 packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
WebSphere: Application packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
WebSphere application contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
9.2. Application assembly and deployment tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Application assembly and deployment tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Assembly and deployment tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
IBM Assembly and Deploy Tools for WebSphere Administration . . . . . . . . . . . . . 9-14
© Copyright IBM Corp. 2013 Contents ix

Student Notebook
IBM Assembly and Deploy Tools tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15

Features in IBM Assembly and Deploy Tools for WebSphere Administration (1 of 2)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16
Features in IBM Assembly and Deploy Tools for WebSphere Administration (2 of 2)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17
Assembling an enterprise application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18
Import modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-19
Java EE perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-20
Application deployment descriptor (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-21
Application deployment descriptor (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22
Enterprise applications without application.xml . . . . . . . . . . . . . . . . . . . . . . . . . . .9-23
Packaging enterprise applications for deployment . . . . . . . . . . . . . . . . . . . . . . . . .9-24
Application scope resources (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-25
Application scope resources (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-26
9.3. Enhanced EAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-27
Enhanced EAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-28
Enhanced EAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-29
Unenhancing an EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-30
Dealing with enhanced EAR files at deployment time . . . . . . . . . . . . . . . . . . . . . .9-31
9.4. Java EE modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-33
Java EE modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34
EJB module assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-35
EJBs included in the web module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-36
Web module assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-37
Web module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-38
Adding metadata through the menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-39
Web deployment descriptor editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-40
Application client assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-41
Generating an EAR file for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-42
9.5. Java EE annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-43
Java EE annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-44
Annotations in Java code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-45
How annotations help the developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-46
Example of declaring a session bean with annotations . . . . . . . . . . . . . . . . . . . . .9-47
Stateless session bean as shown in the Explorer view . . . . . . . . . . . . . . . . . . . . .9-48
Using annotations to inject EJB references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-49
Example of injecting an EJB reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-50
Application bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-51
WebSphere default bindings for bean interfaces . . . . . . . . . . . . . . . . . . . . . . . . . .9-52
Specifying Java EE 6 metadata for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . .9-53
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-54
Exercise 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-57
Unit 10. Application installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2
x WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

V8.1
Student Notebook
TOC Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10.1. Application installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Application installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Installing enterprise applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Creating a J2C authentication alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Creating a data source (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Installing a new application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Example of fast path installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Example of detailed installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Enhanced EAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Removing enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
10.2. Application settings and interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Application settings and interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Starting an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Application update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Other application configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Application startup behavior and auto start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
View the application deployment descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
The application deployment descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Manage modules (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Metadata for modules (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Metadata for modules (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
10.3. Monitored directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Monitored directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Overview of monitored directory deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Supported tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
Enabling the monitored directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
Notes about the monitored directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
Drag-and-drop properties files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Properties file based configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Steps to use properties file to deploy applications (1 of 2) . . . . . . . . . . . . . . . . . 10-43
Steps to use properties file to deploy applications (2 of 2) . . . . . . . . . . . . . . . . . 10-45
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
Checkpoint questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Checkpoint answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Exercise 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
Unit 11. Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11.1. Server logs and diagnostic tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
© Copyright IBM Corp. 2013 Contents xi

Student Notebook
Server logs and diagnostic tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6

Examining server log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
WebSphere Application Server logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Server log files: Types and locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10
Configuring JVM logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12
Viewing runtime messages in the console (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . .11-13
Viewing runtime messages in the console (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . .11-14
HTTP plug-in logs and tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-15
Diagnostic tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16
Using diagnostic tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-17
Enable and configure tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18
Setting the log detail level (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19
Setting the log detail level (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21
Trace output content and format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-22
Reading a log or trace file (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-23
Reading a log or trace file (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25
High Performance Extensible Logging (HPEL) . . . . . . . . . . . . . . . . . . . . . . . . . . .11-26
HPEL logging and tracing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-27
Configure HPEL logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-28
The HPEL Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-29
LogViewer command-line tool (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-31
LogViewer command-line tool (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-33
What is Cross Component Trace (XCT)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-34
Administering XCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-35
XCT request IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-36
Use XCT request ID information to track requests . . . . . . . . . . . . . . . . . . . . . . . .11-37
11.2. Gathering diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-39
Gathering diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-40
Gathering JVM diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-41
Enable verbose garbage collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-42
Java memory dumps and cores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-43
Generating a JVM thread dump (javacore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-45
Generating a JVM heap dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-46
Hung thread detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-47
Connection leak diagnostic messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-48
Checking version levels and applying APARs . . . . . . . . . . . . . . . . . . . . . . . . . . .11-50
11.3. Problem determination tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-51
Problem determination tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-52
Problem determination tool availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-53
Problem determination tools: Administrative console . . . . . . . . . . . . . . . . . . . . . .11-54
Dumping the JNDI namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-55
11.4. IBM Support Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-57
IBM Support Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-58
What is the IBM Support Assistant? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-59
IBM Support Assistant workbench home page . . . . . . . . . . . . . . . . . . . . . . . . . . .11-61
IBM Support Assistant: Search component . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-63
IBM Support Assistant: Tools component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-65
IBM Support Assistant: Collect Data component . . . . . . . . . . . . . . . . . . . . . . . . .11-66
xii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC IBM Support Assistant: Collect and send data . . . . . . . . . . . . . . . . . . . . . . . . . . 11-67

IBM Support Assistant 5.0 Beta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-69
IBM Support Assistant 5.0 Beta: New features . . . . . . . . . . . . . . . . . . . . . . . . . . 11-71
Using the IBM Support Assistant Data Collector (1 of 2) . . . . . . . . . . . . . . . . . . 11-72
Using the IBM Support Assistant Data Collector (2 of 2) . . . . . . . . . . . . . . . . . . 11-73
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-74
Exercise 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-78
Unit 12. Introduction to wsadmin and scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
wsadmin versus administration console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Scripting benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
wsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
wsadmin invocation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Jython versus Jacl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Administrative functions that use wsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Administrative objects in wsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Starting wsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Starting wsadmin with security enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
wsadmin properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Profile scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
AdminConfig: Managing configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
AdminApp: Managing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
AdminControl: Managing running objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
AdminTask: Accessing administrative functions . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Help within wsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
Administrative command help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
Important points to remember when using wsadmin . . . . . . . . . . . . . . . . . . . . . . 12-34
Scripting: Simple script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35
Scripting: Looping script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
Jython script library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
How to use the Jython script library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
Configuration repository: The issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41
Properties file based configuration: A solution . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
Properties file configuration content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
Properties file configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
Create, test, and debug Jython scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
Start the Jython debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50
Jython debugger perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-52
Command assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
Using command assistance within IBM Assembly and Deploy Tools . . . . . . . . . 12-56
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-58
Exercise 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
© Copyright IBM Corp. 2013 Contents xiii

Student Notebook
Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-62
Unit 13. Federating a cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-2
WebSphere cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-3
WebSphere Application Server process types . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-5
Network deployment concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-7
Profiles in network deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-9
Application server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Deployment manager profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-13
Custom profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-15
Creating profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-17
Profile Management Tool: Launch and create . . . . . . . . . . . . . . . . . . . . . . . . . . .13-19
Profile Management Tool: Environment and server type . . . . . . . . . . . . . . . . . . .13-20
Profile Management Tool: Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-22
Profile Management Tool: Names and location . . . . . . . . . . . . . . . . . . . . . . . . . .13-24
Profile Management Tool: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-26
Profile Management Tool: Security certificate (1 of 2) . . . . . . . . . . . . . . . . . . . . .13-27
Profile Management Tool: Security certificate (2 of 2) . . . . . . . . . . . . . . . . . . . . .13-29
Profile Management Tool: Ports and Windows service . . . . . . . . . . . . . . . . . . . .13-31
Profile Management Tool: Results and exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-33
Profile creation: Command-line tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-34
Directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-36
Server commands review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-38
Profile precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-39
Deployment manager console versus stand-alone console . . . . . . . . . . . . . . . . .13-41
Common command-line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-42
Adding a node to a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-44
Adding a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-46
Managed versus unmanaged nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-48
Cell topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-49
Configuring synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-50
Remove a node from a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-52
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-54
Managing a web server: Adding a node to a cell . . . . . . . . . . . . . . . . . . . . . . . . .13-56
Managing a web server: Add the web server . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-58
Managing a web server: Plug-in configuration file . . . . . . . . . . . . . . . . . . . . . . . .13-60
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-62
Checkpoint questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-63
Checkpoint answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-64
Exercise 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-65
Unit 14. Workload management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-3
14.1. Workload management concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-5
Workload management concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-6
xiv WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC What is workload management (WLM)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7

What can be workload managed? (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
What can be workload managed? (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
14.2. Clusters and cluster members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Clusters and cluster members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Clusters and cluster members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Configurations: Vertical scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Configurations: Horizontal scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Configurations: Vertical and horizontal scaling . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Creating a cluster (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
Installing enterprise applications to a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Controlling a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Cluster members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-24
Modification of clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25
14.3. Routing concepts and session affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27
Routing concepts and session affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28
Basic routing algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-29
HTTP session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-31
Session affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-32
JSESSIONID cookie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-33
WebSphere session affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-34
Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-35
Plugin-cfg.xml (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-36
Plugin-cfg.xml (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-37
Interpreting the plugin-cfg.xml file (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-38
Weighted round robin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-42
Weighted routing example with no affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-43
Weighted routing example with affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-44
Weighted routing example with counting affinity . . . . . . . . . . . . . . . . . . . . . . . . . 14-45
Routing alternative: Random . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-46
Using Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-47
14.4. Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-49
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-50
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-51
Edge Components failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52
HTTP server failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-53
Web container failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-54
EJB container failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-55
14.5. Session persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-57
Session persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-58
Session persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-59
© Copyright IBM Corp. 2013 Contents xv

Student Notebook
Session configuration: Memory-to-memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-60

Session configuration: Replication domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-61
Database persistence configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-62
Tuning session persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-63
eXtreme Scale persistence configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-64
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-65
Exercise 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-68
Unit 15. Introduction to WebSphere Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-3
15.1. Overview of messaging concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-5
Overview of messaging concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-6
What is JMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-7
JMS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-8
What is a JMS provider? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-9
Basic messaging flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
WebSphere default messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-12
Service integration bus (SIBus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-13
SIBus members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-15
Messaging engine (ME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-16
Bus member and messaging engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-17
Message stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-18
Messaging engine data stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-20
Messaging engine data stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-21
What is a bus destination? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-22
SIBus destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-23
Linking destinations to bus members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-25
Message points (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-27
Message points (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-28
SIBus destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-29
SIBus queue destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-30
SIBus topic space destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-31
Java EE access to bus members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-32
JMS destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-34
JMS connection factory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-35
JMS ActivationSpec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-36
Applications can run outside bus members . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-37
Message engine clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-38
Messaging engine policy assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-39
Example: High availability policy (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-40
Example: High availability policy (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-41
Example: Scalability policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-42
Example: Scalability with high availability policy . . . . . . . . . . . . . . . . . . . . . . . . . .15-43
SIBus and messaging engine topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-44
xvi WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC Messaging engine topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-45

SIBus and MEs in a stand-alone server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-46
Bus topology: Stand-alone servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-47
SIBus and MEs in a Network Deployment cell . . . . . . . . . . . . . . . . . . . . . . . . . . 15-48
Network Deployment cell topologies (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-49
Network Deployment cell topologies (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-50
Additional messaging considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-51
Additional messaging considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-52
SIBus destination quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-53
Destination quality of service for reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-54
What is a mediation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-56
SIBus security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-57
Interoperating with a WebSphere MQ network . . . . . . . . . . . . . . . . . . . . . . . . . . 15-58
Connect SIBus to WebSphere MQ Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-59
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-60
Exercise 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-63
Exercise: Messaging tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-65
Unit 16. Job manager and Centralized Installation Manager . . . . . . . . . . . . . . . . . 16-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
16.1. Flexible management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Flexible management topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Flexible management characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Administrative agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Administrative agent topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Administrative agent features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
Job manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
Job manager topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Flexible management jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
Asynchronous nature of jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
16.2. The job manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17
The job manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
Job manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
The deployment manager job manager process . . . . . . . . . . . . . . . . . . . . . . . . . 16-21
Job manager Jobs section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22
Registering targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-23
Job manager: Submit jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
Job manager jobs for host targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
Job manager jobs for WebSphere targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-26
Liberty profile jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-27
16.3. Centralized Installation Manager (CIM) in the job manager . . . . . . . . . . . . . . . 16-29
Centralized Installation Manager (CIM) in the job manager . . . . . . . . . . . . . . . . 16-30
© Copyright IBM Corp. 2013 Contents xvii

Student Notebook
Centralized Installation Manager (CIM) in the job manager . . . . . . . . . . . . . . . . .16-31

Add IBM Installation Manager installation "kits" . . . . . . . . . . . . . . . . . . . . . . . . . .16-32
Job example: Install IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . .16-33
Install IBM Installation Manager on a target . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-34
Job scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-36
Job status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-37
Submitting a "Manage offerings" job (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-38
Differences between CIM for V 8 and CIM for V 6.1 and 7 . . . . . . . . . . . . . . . . . .16-43
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-44
Demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-47
Demonstration objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-48
Unit 17. Overview of Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3
17.1. Overview of Intelligent Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-5
Overview of Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-6
Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-7
Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-9
History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-11
17.2. Intelligent Management components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-13
Intelligent Management components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-14
Intelligent Management components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-15
Dynamic clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-16
Dynamic cluster settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-17
Service policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-18
Autonomic managers and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-19
Intelligent routers: the on demand router (ODR) . . . . . . . . . . . . . . . . . . . . . . . . .17-21
Intelligent routers: the WebSphere plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-23
What is intelligent routing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-24
17.3. Health management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-25
Health management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-26
What is health management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-27
Health policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-28
Viewing health conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-30
Predefined health conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-31
Heath conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-32
Creating health conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-33
Predefined actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-34
Administering actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-35
Maintenance modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-36
Custom health conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-38
17.4. Application edition management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-39
Application edition management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-40
xviii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC What is Application edition management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-42
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-44
Rollout activation (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-46
Rollout activation (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-47
Concurrent activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-49
Validation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-50
Edition control center (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-51
Edition control center (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-52
17.5. Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
What is Performance Management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
17.6. Deployment manager high availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
Deployment manager high availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-58
Highly available deployment manager (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . 17-59
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-62
Unit 18. WebSphere security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
18.1. WebSphere security basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
WebSphere security basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Basic security end-to-end model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
WebSphere Application Server security overview . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
WebSphere security service: Big picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Types of security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Administrative security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Authentication and authorization: What is the difference? . . . . . . . . . . . . . . . . . 18-14
Challenge mechanism: Authentication basic steps . . . . . . . . . . . . . . . . . . . . . . . 18-15
Challenge mechanism: Basic authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Challenge mechanism: Form-based authentication . . . . . . . . . . . . . . . . . . . . . . 18-17
Defining the challenge type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
18.2. WebSphere user registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
WebSphere user registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
Registries and authentication mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Defining user registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Manual security configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
Security wizard: Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
User registry support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Federated repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
© Copyright IBM Corp. 2013 Contents xix

Student Notebook
Custom registry: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-31

Authentication mechanism: LTPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-32
LTPA provides delegation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-33
LTPA provides single sign-on (SSO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-34
18.3. Administrative security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-35
Administrative security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-36
Administrative security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-37
Console security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-38
Additional console security roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-39
Administrative roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-40
Console security: Creating users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-41
Console security: Mapping users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-42
18.4. Application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-43
Application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-44
Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-45
Security roles: Application authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-46
Securing Java EE application artifacts: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .18-47
Securing Java EE application artifacts: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .18-48
Applying application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-49
Creating security constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-50
Using the console to map security roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-51
18.5. Security domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-53
Security domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-54
Security configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-56
Creating a security domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-58
Configuring a security domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-59
18.6. Java 2 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-61
Java 2 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-62
Java security model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-63
Java security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-64
Enabling Java 2 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-66
18.7. SSL basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-67
SSL basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-68
What is SSL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-69
Symmetric key encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-70
Asymmetric key encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-71
How does SSL work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-72
18.8. Certificates and certificate authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-73
Certificates and certificate authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-74
What is a certificate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-75
Types of certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-76
What is a certificate authority (CA)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-78
SSL: Putting it all together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-79
18.9. SSL within a WebSphere cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-81
SSL within a WebSphere cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-82
SSL within WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-83
xx WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

V8.1
Student Notebook
TOC WebSphere SSL management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84

What are key rings, keystores, and truststores? . . . . . . . . . . . . . . . . . . . . . . . . . 18-85
Node certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-86
Cell default truststore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-87
Managing WebSphere keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-88
Creating keystores and certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-89
What is a chained certificate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-90
Expiration manager scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-91
Keys for web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-92
Web server plug-in keystores propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-93
IBM HTTP Server key ring propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-94
18.10. Security auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-95
Security auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-96
Security auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-97
Enabling security auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-98
Viewing audit data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-99
Securing audit records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-100
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-101
Checkpoint questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-102
Checkpoint answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-103
Exercise 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-104
Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-105
Exercise 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-106
Exercise 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-108
Unit 19. Overview of the Liberty profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
19.1. Introduction to the Liberty profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Introduction to the Liberty profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
What is the Liberty profile? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
What does the Liberty profile provide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Liberty profile architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Clarification: Profile versus profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11
WebSphere Application Server family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Features available in the Liberty editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
19.2. Tools, runtime, and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Tools, runtime, and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
Liberty profile developer tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Where to get WebSphere Application Server Developer Tools for Eclipse . . . . . 19-18
Where to get the Liberty profile runtime environment . . . . . . . . . . . . . . . . . . . . . 19-19
Installing the Liberty profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Creating a Liberty profile server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
Creating a server with developer tools (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22
© Copyright IBM Corp. 2013 Contents xxi

Student Notebook
19.3. Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-25

Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-26
Simplified server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-27
Simplified configuration: server.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-28
Flexible configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-29
Shared configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-30
Application deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-31
Highly composable runtime that is based on features . . . . . . . . . . . . . . . . . . . . .19-32
Dynamic enablement of feature sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-33
Class visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-35
Shared libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-36
Packaging an application for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-37
Liberty profile server command-line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-38
Deploying an application by using the drop-ins directory . . . . . . . . . . . . . . . . . . .19-39
Creating the production image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-40
Deploying Liberty topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-41
Example: A shared topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-42
19.4. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-43
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-44
Liberty profile security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-45
Enable SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-46
Advanced SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-47
User registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-49
Basic user registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-50
LDAP user registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-51
SAF user registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-52
Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-54
Liberty administrative security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-55
19.5. Using the job manager to manage Liberty profile servers . . . . . . . . . . . . . . . . .19-57
Using the job manager to manage Liberty profile servers . . . . . . . . . . . . . . . . . .19-58
Administering Liberty profiles by using the job manager . . . . . . . . . . . . . . . . . . .19-59
Job manager Liberty profile jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-60
Deploying a self-contained topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-61
HTTP request routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-62
Job type: Generate merged plug-in configuration . . . . . . . . . . . . . . . . . . . . . . . . .19-63
Merged plugin-cfg.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-65
19.6. Liberty collectives and clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-67
Liberty collectives and clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-68
Liberty collectives and clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-69
Example of server clusters and a Liberty collective . . . . . . . . . . . . . . . . . . . . . . .19-70
Administering Liberty profiles in collectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-71
Liberty profile collective controller and collective members . . . . . . . . . . . . . . . . .19-73
Liberty clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-74
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-75
Exercise 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-78
xxii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC Unit 20. Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
20.1. Performance tuning and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Performance tuning and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
The need for performance monitoring and tuning . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
Tuning performance suggested practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Performance terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Tuning parameter hot list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Solving performance problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
Measuring performance and collecting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-14
WebSphere performance tools (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
PMI architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-20
Types of performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
PMI data collection settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Using the administrative console to enable PMI . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Start monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Tivoli Performance Viewer (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Summary reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31
Example: Servlet Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
Performance servlet overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-34
Performance servlet output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-35
20.2. Request metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-37
Request metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38
Request metrics (RM) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Enabling request metrics collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-40
Isolating performance for specific types of requests . . . . . . . . . . . . . . . . . . . . . . 20-42
Example request metrics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
20.3. Performance advisors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-45
Performance advisors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-46
Performance advisors overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-47
Performance and Diagnostic Advisor (1 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-49
Tivoli Performance Viewer advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-55
Examples of performance advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-56
Viewing performance advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58
Performance advice detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-59
Performance advisor suggested practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-60
20.4. IBM Tivoli Composite Application Manager for WebSphere Application Server 20-63
IBM Tivoli Composite Application Manager for WebSphere Application Server . 20-64
© Copyright IBM Corp. 2013 Contents xxiii

Student Notebook
IBM Tivoli Composite Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-65

IBM Tivoli Composite Application Manager for WebSphere Application Server . .20-67
IBM Tivoli Composite Application Manager for WebSphere Application Server . .20-69
IBM Tivoli Composite Application Manager metrics in Tivoli Performance Viewer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-70
IBM Tivoli Composite Application Manager application metrics in Tivoli Performance
Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-71
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-72
Exercise 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-75
Unit 21. WebSphere Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-2
Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-3
21.1. Overview of WebSphere Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-5
Overview of WebSphere Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-6
The challenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-7
Introduction to WebSphere Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-8
Key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-9
21.2. Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-12
WebSphere Batch components (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-13
WebSphere Batch components (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-14
Batch container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-15
Batch programming model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-16
WebSphere Batch environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-18
Main concepts of batch processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-19
The WebSphere Batch workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-20
21.3. Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-21
Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-22
Parallel batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-23
Enterprise integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-24
CommandRunner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-25
COBOL support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-26
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-28
Unit 22. Course summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-2
Course learning objectives (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-3
Course learning objectives (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-4
Class evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-5
To learn more about this subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-6
References (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-7
References (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-8
xxiv WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TOC References (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-9

Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Glossary of abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
© Copyright IBM Corp. 2013 Contents xxv

Student Notebook
xxvi WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
TMK Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in
many jurisdictions worldwide:
AFS® AIX® CICS®
CloudBurst® DataPower® DB™
DB2® developerWorks® Express®
HACMP™ IMS™ Lotus®
MVS™ Notes® OS/400®
Passport Advantage® Power® RACF®
Rational® RDN® Redbooks®
Tivoli® U® WebSphere®
z/OS® zSeries®
Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in
the United States, and/or other countries.
Intel and Intel Core are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows and Windows Vista are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle and/or its affiliates.
VMware and the VMware “boxes” logo and design, Virtual SMP and VMotion are registered
trademarks or trademarks (the “Marks”) of VMware, Inc. in the United States and/or other
jurisdictions.
Other product and service names might be trademarks of IBM or other companies.
© Copyright IBM Corp. 2013 Trademarks xxvii

Student Notebook
xxviii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
pref Course description

WebSphere Application Server V8.5.5 Administration
Duration: 5 days
Purpose
This 5-day instructor-led course teaches you the skills that are needed
to install and administer IBM WebSphere Application Server V8.5.5.
This release offers users enhanced support for standards, emerging
technology, and a choice of development frameworks.
In this course, you learn how to install, configure, and maintain IBM
WebSphere Application Server V8.5.5 Base, Network Deployment
(ND), and the Liberty profile. You learn how to deploy enterprise Java
applications in a single computer or clustered configuration. In
addition, you learn how to work with features of WebSphere
Application Server V8.5.5, such as IBM Installation Manager,
WebSphere Customization Toolbox, security enhancements,
Intelligent Management, and centralized installation.
Throughout the course, hands-on exercises and demonstrations
reinforce lecture content and give you practical experience with
WebSphere Application Server V8.5.5. You complete tasks such as
installing and assembling applications, applying problem
determination techniques, configuring a clustered environment, and
working with fine-grained administrative security.
Audience
This course is designed for administrators who install, configure, and
manage web-based applications on WebSphere Application Server.
Web administrators, lead application developers, and application
architects can also benefit from this course.
Prerequisites
Before taking this course, you should have:
• An understanding of basic Internet concepts
• Experience in using a web browser
• Administrative skills for a web server, such as IBM HTTP Server or
Apache
© Copyright IBM Corp. 2013 Course description xxix

Student Notebook
• Basic operational skills for the Linux operating system
Objectives
After completing this course, you should be able to:
• Relate WebSphere Application Server to the WebSphere family of
products
• Describe the features and standards in WebSphere Application
Server V8.5.5
• Describe the architectural concepts that are related to WebSphere
Application Server
• Install and configure WebSphere Application Server V8.5.5
• Install and configure IBM HTTP Server
• Assemble and install server-side Java enterprise applications
• Use WebSphere administrative tools to configure and manage
enterprise applications
• Use wsadmin scripting
• Configure WebSphere Application Server security
• Deploy applications in clustered environments
• View performance information about server and application
components
• Use problem determination tools and log files to troubleshoot
problems
• Configure messaging with the service integration bus
• Describe Intelligent Management features
• Describe WebSphere Batch features
• Describe the Liberty profile
• Install and configure the Liberty profile
Curriculum relationship
• WA380 (Windows), WA580 (Linux), WA180 (AIX)
• WA585
xxx WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
pref Agenda
Day 1
Course introduction
Unit 1: WebSphere product family overview
Unit 2: WebSphere Application Server architecture – stand-alone
Unit 3: WebSphere Application Server architecture – federated
Unit 4: IBM Installation Manager
Unit 5: WebSphere Application Server installation
Unit 6: Web server installation
Exercise 1: Installing IBM Installation Manager
Exercise 2: Installing WebSphere Application Server
Exercise 3: Installing IBM HTTP Server
Day 2
Unit 7: WebSphere Application Server administrative console
Exercise 4: Exploring the administrative console
Unit 8: Introduction to the PlantsByWebSphere application
Unit 9: Application assembly
Exercise 5: Assembling an application
Unit 10: Application installation
Exercise 6: Installing an application
Unit 11: Problem determination
Exercise 7: Problem determination
Day 3
Unit 12: Introduction to wsadmin and scripting
Exercise 8: Using wsadmin
Unit 13: Federating a cell
Exercise 9: Creating a federated cell
Unit 14: Workload management
Exercise 10: Clustering and workload management
© Copyright IBM Corp. 2013 Agenda xxxi

Student Notebook
Day 4
Unit 15: Introduction to WebSphere Messaging
Exercise 11: Configuring the service integration bus
Unit 16: Job manager and centralized installation manager
Demonstration: Using the job manager
Unit 17: Overview of Intelligent Management
Unit 18: WebSphere security
Exercise 12: Configuring WebSphere security
Exercise 13: Configuring application security
Day 5
Exercise 14: Configuring SSL for WebSphere
Unit 19: Overview of the Liberty profile
Exercise 15: Working with the Liberty profile
Unit 20: Performance monitoring
Exercise 16: Using the performance monitoring tools
Unit 21: WebSphere Batch
Unit 22: Course summary
xxxii WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
Uempty Unit 1. WebSphere product family overview
What this unit is about

This unit describes the products in the WebSphere product family and
their relationship to WebSphere Application Server V8.5.5.
What you should be able to do

After completing this unit, you should be able to:
• Describe the WebSphere family of products
• Describe the relationships between various products in the
WebSphere family
• Describe the WebSphere Application Server V8.5.5 offerings
• Describe the standards that are supported in this release
How you will check your progress

• Checkpoint
References
WebSphere Application Server V8.5 Information Center
http://publib.boulder.ibm.com/infocenter/wasinfo/v8r5/
index.jsp
© Copyright IBM Corp. 2013 Unit 1. WebSphere product family overview 1-1
Student Notebook
Unit objectives
• Describe the relationships between various products in the WebSphere
family
© Copyright IBM Corporation 2013
Figure 1-1. Unit objectives WA855 / VA8551.0
Notes:
1-2 WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
Student Notebook
Uempty
Topics
• Platform and packaging
• Related WebSphere products
Figure 1-2. Topics WA855 / VA8551.0
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 1.1. Platform and packaging
Student Notebook
Platform and packaging

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Figure 1-3. Platform and packaging WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere software platform
• WebSphere • IBM
Process Server WebSphere
• IBM Integration Portal
Designer • IBM Web
• WebSphere Experience
Business
DataPower SOA Factory
portals
Appliances • IBM Mashup
• WebSphere MQ Center
Business
• WebSphere
integration
Message Broker
• WebSphere
Foundation and tools
Enterprise
Service Bus
• WebSphere Application Server

• WebSphere eXtreme Scale
• Rational Application Developer
Figure 1-4. WebSphere software platform WA855 / VA8551.0
Notes:
The WebSphere software platform consists of multiple products. These products can be
grouped into three categories:
• Foundation and tools
• Business integration
• Business portals
As shown in the graphic, the three categories build upon each other in the order listed.
WebSphere Application Server is the base product for all others that are listed in this slide.
Rational Application Developer is the primary Java development tool for all these products.
Student Notebook
WebSphere application infrastructure: The big picture
Cloud and IBM Workload Deployer (images, topologies, patterns)

operational
management
and efficiency WebSphere Application Server Pattern for web
Hypervisor applications
Mobile
applications IBM Worklight Server
(web, hybrid,
native)
WebSphere eXtreme
Fit for purpose
Scale WebSphere Application Server
foundation and V8.5.5 foundation
distributed
caching Liberty profile
DataPower XC10 Intelligent Management
WebSphere Batch
IBM JVM
Figure 1-5. WebSphere application infrastructure: The big picture WA855 / VA8551.0
Notes:
WebSphere Application Server Version 8.5.5 delivers the core foundational requirements
for the rest of the WebSphere Application Server portfolio of products. Built upon the IBM
Java Virtual Machine (JVM), the Application Server provides the foundation for the
WebSphere portfolio, including IBM Workload Deployer, WebSphere eXtreme Scale, and
the DataPower XC10 Appliance.
V8.1
Student Notebook
Uempty
WebSphere Application Server family

WebSphere WebSphere WebSphere WebSphere
Application Application Server Application Server Application Server
Server for Hypervisor Edition Network Deployment for z/OS
Developers
Optimized to instantly Delivers near-continuous Takes full advantage of
run in VMware and availability, with the z/OS Sysplex to
Provides the
other server advanced performance deliver a highly secure,
environment for
virtualization and management reliable, and resource
efficient
environments capabilities efficient experience
development of
innovative +WXS +LP +WXS +LP +WXS +LP
applications
that eventually
run on WebSphere Provides a secure, high performance, transaction
WebSphere in Application Server engine for moderately sized configurations with web
production tier clustering and failover across up to five application
+WXS +LP server profiles
Available as a
no-charge A lightweight and low- A lower-cost,
edition for the WebSphere WebSphere
cost Liberty-profile-based Application ready-to-go
developer Application
offering, providing solution to build
desktop Server Server
capabilities to rapidly dynamic
Liberty Core build and deliver web Express websites and
+WXS +LP apps that do not require applications
+LP
the full Java EE stack
+WXS – entitlement to WebSphere eXtreme Scale +LP – includes Liberty Profile

Figure 1-6. WebSphere Application Server family WA855 / VA8551.0
Notes:
The WebSphere Application Server family for Version 8.5.5 continues to provide offerings
to fit your needs, which might range from lightweight developer desktop environments to
highly complex and highly available enterprise environments. As more qualities of service
are required in your environment, the WebSphere Application Server family of offerings
continues to meet those requirements on a common code base.
This chart shows each of the different versions of WebSphere Application Server and how
they relate to one another regarding customer needs and capabilities.
WebSphere Application Server Express features reduced acquisition cost and enables fast
deployment of a single application server. The difference between this package and the
WebSphere Application Server “Base” edition is the license. Both editions are virtually the
same, but “Base” includes a license for unlimited processors. Express is limited to two
processors. Both Express and Base editions can support a stand-alone deployment.
WebSphere Application Network Deployment includes all the capabilities of the Base
edition, but also supports high transaction volume, scalability, clustering, high availability,
and failover.
Student Notebook
WebSphere Application Server for z/OS includes all the features of Network Deployment
for the z/OS platform.
WebSphere Application Server for Developers is a no-charge WebSphere Application
Server development runtime for projects that do not warrant the expense of a priced and
supported runtime on the developer desktop. The development runtime environment allows
developers to test their applications on their desktop before moving the application into a
production runtime environment.
New in version 8.5.5 is WebSphere Application Server Liberty Core. Liberty Core is a highly
composable, fast to start, and ultra lightweight profile of the application server that is
optimized for developer productivity and web application deployment.
Each of these editions is described in more detail on the following slides.
V8.1
Student Notebook
Uempty
WebSphere Application Server V8.5.5 packaging
Scalability, clustering,
high availability,
central administration
License
WebSphere common WebSphere common WebSphere common

base code base code base code
WebSphere WebSphere WebSphere

Application Application Application
Server Express Server Server Network
Deployment
Figure 1-7. WebSphere Application Server V8.5.5 packaging WA855 / VA8551.0
Notes:
The image compares the basic differences in packaging between the WebSphere
Application Server Express, Base, and Network Deployment editions. All three packages
include the WebSphere common base code. The major difference between Express and
Base is the license. Express has a limited license for two processors; Base has a license
for unlimited processors. The Network Deployment product adds support for scalability,
clustering, high availability, and central administration.
Student Notebook
Product packaging comparison (1 of 2)

Server Express Server (base) Server Network
Deployment
Core Application Stand-alone node; Stand-alone Multiple
Server two processors node; unlimited distributed nodes,
processors with centralized
administration
IBM HTTP Server ¥ ¥ ¥
web server plug-ins
Application client, ¥ ¥ ¥
update installer,
installation factory,
migration tools, IBM
Support Assistant
Data Direct JDBC ¥ ¥ ¥
drivers
Liberty profile ¥ ¥ ¥
Intelligent
Management Pack ¥
Figure 1-8. Product packaging comparison (1 of 2) WA855 / VA8551.0
Notes:
This chart summarizes the WebSphere Application Server V8.5.5 Express, Base, and
Network Deployment packages for production use, and provides a side-by-side
comparison of some of the important features. Detailed comparison information for the
versions can be found at:
http://www.ibm.com/software/webservers/appserv/wasfamily/compare.html
All three versions include the core application server, IBM HTTP Server, web server
plug-ins, application client, and Data Direct JDBC drivers.
The Express and Base packages provide for deployment of a stand-alone node. In addition
to a stand-alone node, the Network Deployment edition supports a managed or clustered
multi-node environment with a central point of administration.
The Express edition includes Rational Web Developer. The Base and Network Deployment
packages include a trial version of Rational Application Developer. Rational Application
Developer is available in the WebSphere Application Server disk package with two
licenses. The license for assembly and deployment capabilities does not expire. The
V8.1
Student Notebook
Uempty license for development and other capabilities is available on a trial basis and is available
only for a limited time.
In addition, the Network Deployment edition also includes the Edge Components, IBM
Tivoli Directory Server, and Tivoli Access Manager Server.
Student Notebook
Product packaging comparison (2 of 2)

Server Express Server (base) Server Network
Deployment
Batch processing ¥ ¥ ¥
Development and Rational Rational Rational

deployment tools Application Application Application
Developer Developer Developer
Trial Trial Trial

Database included in DB2 Express DB2 Express DB2
the package (developmental (developmental
use only) use only)
Edge components ¥
IBM Tivoli Directory ¥
Server (LDAP server)
Tivoli Access Manager ¥
Server
Figure 1-9. Product packaging comparison (2 of 2) WA855 / VA8551.0
Notes:
This chart summarizes the WebSphere Application Server V8.5.5 Express, Base, and
Network Deployment packages for production use, and provides a side-by-side
comparison of some of the important features.
All three versions include the core application server, IBM HTTP Server, web server
plug-ins, application client, and Data Direct JDBC drivers.
The Express and Base packages provide for deployment of a stand-alone node. In addition
to a stand-alone node, the Network Deployment edition supports a managed or clustered
multi-node environment with a central point of administration.
The Express edition includes Rational Web Developer. The Base and Network Deployment
packages include a trial version of Rational Application Developer. Rational Application
Developer is available in the WebSphere Application Server disk package with two
licenses. The license for assembly and deployment capabilities does not expire. The
license for development and other capabilities is available on a trial basis and is available
only for a limited time.
V8.1
Student Notebook
Uempty In addition, the Network Deployment edition also includes the Edge Components, IBM
Tivoli Directory Server, and Tivoli Access Manager Server.
Student Notebook
Specifications that are supported in V8.5.5

Specification or API
Java EE 6, 5, and J2EE Java SE 7 Servlet 3.0, 2.5, 2.4, 2.3
1.4, 1.3
JSP 2.2, 2.1, 2.0 Portlet 2.0 SIP 1.1, 1.0
EJB 3.1, 3.0, 2.1, 2.0, 1.1 JDBC 4.1 JPA 2.0, 1.0
JAXB 2.2 JAX-RS 1.1 JAX-RPC 1.1

JAXP 1.2 JAXR 1.0 JAX-WS 2.2di
SAAJ 1.2, 1.3 JSF 2.0, 1.2 SOAP 1.1, 1.2
StAX 1.0 UDDI 3.0 XML schema 1.0
JCA 1.6 WS-AT 1.0, 1.1 WS-BA 1.0, 1.1
WS-COOR 1.0, 1.1 WSDL 1.1 JSR 109 1.2
SDO 1.0 JMS 1.1 JavaMail 1.4
Java 2 Security JAAS 2.0 JACC 1.1
JCE 1.0 CertPath 1.1 WS-Security 1.0, 1.1
JAF 1.1 WS-I Attachments 1.0 WSIF
JNDI on Java SE 7 JTA 1.1 And more
Figure 1-10. Specifications that are supported in V8.5.5 WA855 / VA8551.0
Notes:
This chart lists some of the specifications and APIs supported in WebSphere Application
Server V8.5.5. For a more exhaustive list of supported specifications and APIs, refer to the
WebSphere information center.
V8.1
Student Notebook
Uempty 1.2. WebSphere family products
Student Notebook
WebSphere family
products

Figure 1-11. WebSphere family products WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere Application Server for Developers

• Efficient development and innovative features of WebSphere
Application Server V8.5.5 available at no charge
• Reduce testing effort and develop with confidence by using a runtime

environment that is identical to the production runtime environment
your applications eventually run on
• Available at:
http://www.ibm.com/developerworks/downloads/ws/
wasdevelopers/index.html
Figure 1-12. WebSphere Application Server for Developers WA855 / VA8551.0
Notes:
WebSphere Application Server Version 8.5.5 delivers a no-charge offering to enable quick
and easy developer access to the application server that is built on the same code base as
the other WebSphere Application Server offerings.
Student Notebook
WebSphere Application Server Hypervisor Edition

• WebSphere Applications Server shipped ready to run on a hypervisor
that is based on OVF standard (such as VMware ESX, PowerVM,
z/VM)
– No installation is required (run and choose a profile)
– Single virtual image capable of supporting single servers or clusters
– New images are released on quarterly update intervals
• Maintenance, support, and fixes through IBM for both WebSphere

Application Server and operating system.
WebSphere
Hypervisor Edition
• Products support various combinations of:
– VMware ESX, z/VM, and PowerVM hypervisors WebSphere
Application Server
– Red Hat Enterprise Linux, SUSE Linux, AIX
Operating system
Figure 1-13. WebSphere Application Server Hypervisor Edition WA855 / VA8551.0
Notes:
Open Virtualization Format (OVF) specifies an open, secure, portable, and flexible format
for the packaging and distribution of virtual machines.
Previously, when customers wanted to use WebSphere Application Server in a
virtualization context, they were forced to build and own these images, which involved
managing two parallel code paths (operating system and middleware). Now, IBM is building
and supporting the entire virtual image.
A virtual machine or virtual image is a complete system platform that contains an operating
system on which you can install any number of customized applications to create a
complete virtual system. A virtual image requires less time and labor to set up because the
operating system and applications are already installed and configured or partially
configured. Virtual images are run on a hypervisor, which is the virtualization technology
that manages the state of virtual images. A hypervisor product can run on top of a host
operating system, or the hypervisor can run as the operating system itself, such as VMware
ESX. Some hypervisors also handle load balancing and failover.
V8.1
Student Notebook
Uempty By deploying virtual images on VMware and other virtualization technologies, you can
consolidate servers and streamline your environments.
WebSphere Application Server Hypervisor Edition Version 8.5.5 can function either as a
stand-alone server or with IBM Workload Deployer. Workload Deployer as a hardware
appliance that provides access to software virtual images and patterns.
The virtual image can be used as a demonstration, a development system, or a simple
quality assurance system. A single virtual image can also be a single production system for
a small department.
Student Notebook
Mobile application development

WebSphere WebSphere + Web 2.0
Application Server and Mobile Toolkit Worklight
Enterprise web Mobile web app development Application delivery in

applications that is based on standard web various forms:
technologies: • Hybrid application
• Java EE
programming • Run applications in mobile • Native
browser
• Build, deploy, and • Install through app store
manage Enterprise • Based on HTML5, CSS3, and
applications and JavaScript • Access to native services
services
• Native look and feel
• Server-side and
• Advanced mobile user
client-side
interface components
development
•Feature Pack for V6.1, V7, and
V8
Desktop web Mobile web applications Mobile applications

applications
Figure 1-14. Mobile application development WA855 / VA8551.0
Notes:
Worklight takes WebSphere Application Server mobile web applications to the next level.
With WebSphere Application Server V8.5.5, the Web 2.0 and Mobile Feature Pack is part
of WebSphere Application Server. WebSphere developers can build and deploy reliable
mobile web applications by using standards web technologies, such as HTML 5, CSS3,
and JavaScript. Resulting applications are available on various mobile platforms by using
the web browser of the device. Supported platforms are iPhone OS, Android, and
BlackBerry. User experience is close to each mobile operating system, and supports usual
touch interactions.
Worklight extends those applications to make them deployable as hybrid or native
applications. Other functions include access to local resources and native functions (such
as camera or GPS). Installation is done through app stores.
V8.1
Student Notebook
Uempty
WebSphere eXtreme Scale

A flexible framework for realizing high
NYC Tokyo
performance, scalable and data-intensive
applications
LA London
• Can be used as a • Can be used as a form of • Can be used as

powerful cache in-memory database a platform for
– Scales from simple, – Manages application states building powerful
in-process topologies – Scales to thousands of servers data grid
to powerful, applications
– Sometimes referred to as
distributed topologies
Distributed Application State
Management
Figure 1-15. WebSphere eXtreme Scale WA855 / VA8551.0
Notes:
Applications and organizations can evolve as business needs and requirements change,
which can require more scalability or the use of some of the other advanced features that
eXtreme Scale provides.
What is IBM WebSphere eXtreme Scale? IBM WebSphere eXtreme Scale is a flexible
framework for realizing high-performance, scalable, and data-intensive applications. It is a
single map addressable space of virtualized JVM heap spaces. The first use of WebSphere
eXtreme Scale is a power cache for your applications. WebSphere eXtreme Scale can
move that collection of application caches into a grid that is highly available, elastic, and
self-healing. The second use of WebSphere eXtreme Scale is a form of in-memory
database. The third use of WebSphere eXtreme Scale is a form of redundancy across data
centers.
WebSphere eXtreme Scale dynamically caches, partitions, replicates, and manages
application data and business logic across multiple servers. WebSphere eXtreme Scale
does massive volumes of transaction processing with high efficiency and linear scalability,
and provides qualities of service such as transactional integrity, high availability, and
Student Notebook
predictable response times. WebSphere eXtreme Scale can be used in different ways. It
can be used as a powerful cache, as a form of an in-memory database processing space to
manage application state, or as a platform for building powerful extreme transaction
processing (XTP) applications.
Some editions of WebSphere Application Server come with an entitlement to use
WebSphere eXtreme Scale.
V8.1
Student Notebook
Uempty
WebSphere eXtreme Scale entitled capabilities

– Entitlement to session caching
– Entitlement to DynaCache
– Only in support of WebSphere Application Server.
• WebSphere Application Server Network Deployment
– Full entitlement to WebSphere eXtreme Scale.
• WebSphere Application Server for Developers includes
– Full entitlement to WebSphere eXtreme Scale on the developer workstation.
• WebSphere Application Server for z/OS includes
– Full entitlement to WebSphere eXtreme Scale for z/OS
• Client APIs for connecting to distributed WebSphere eXtreme Scale servers
Figure 1-16. WebSphere eXtreme Scale entitled capabilities WA855 / VA8551.0
Notes:
Several WebSphere Application Server V8.5.5 editions include entitlement to WebSphere
eXtreme Scale capabilities for both Liberty profile and full profile WebSphere Application
Server.
Student Notebook
WebSphere DataPower XC10 Appliance

• A purpose-built, easy-to-use appliance that is designed for simplified
deployment at the caching tier of the enterprise application
infrastructure
– Designed for rapid, drop-in use with WebSphere Application Server, and other
WebSphere family products
– Physical hardware device capable of running
one or more grids
– Set of XC10 appliances can be grouped
together for scalability
• Used for simple data-oriented

scenarios
– HTTP session replication
– Elastic dynamic cache
– Web side cache XC10
Figure 1-17. WebSphere DataPower XC10 Appliance WA855 / VA8551.0
Notes:
The IBM WebSphere DataPower XC10 is a purpose-built, easy-to-use appliance that is
designed for simplified deployment at the caching tier of your enterprise application
infrastructure. The DataPower XC10 is designed for rapid, “drop-in” use along with
WebSphere Application Server and other WebSphere family products. It is based on the
DataPower 9004 platform and contains 160 gigabytes of storage per unit. Because your
needed data can be stored on the appliance in an in-memory grid, application caching
functions can be done fast and can scale with consistent performance.
V8.1
Student Notebook
Uempty
WebSphere eXtreme Scale and DataPower XC10 Appliance

“Data-oriented”
Session management
Elastic DynaCache
DataPower XC10 Appliance Web side cache
• Drop-in cache solution Petabyte analytics WebSphere
that is optimized and eXtreme Scale
Data buffer
hardened for data-
oriented scenarios Event Processing
• Ultimate flexibility
• High density, low footprint
Worldwide cache across a broad range of
improves data center
In-memory OLTP
caching scenarios
efficiency
• In-memory capabilities
• Stores cached data on the In-memory SOA for application-oriented
appliance
scenarios
“Application-oriented” • Builds grids by using
JVMs
Elastic caching for linear scalability
High availability data replication
Simplified management, monitoring, and administration
Figure 1-18. WebSphere eXtreme Scale and DataPower XC10 Appliance WA855 / VA8551.0
Notes:
In simple, data-oriented scenarios, few code changes are necessary to adopt elastic
caching. Customers are looking for performance and scalability improvements that are
balanced with cost savings.
Application-oriented scenarios require investment in new architectures.
XC10 focuses on simple, data-oriented caching scenarios where customers want to quickly
and cost effectively scale their applications while improving performance. Data-oriented
caching scenarios require few application code changes; with XC10, no application code
changes are required at all for WebSphere Session Management and extending
DynaCache. XC10 provides a large (160 GB) cache in a high density, low footprint that
allows you to save time, money, and storage space. Fault tolerance is built in, lowering your
risk of data loss and providing continuous availability.
WebSphere eXtreme Scale provides the ultimate flexibility that supports a broad range of
caching scenarios, which include caches where the data and application are collocated.
These customers are investing in growing their business, differentiating their applications
from the competition.
Student Notebook
Value of data-oriented scenario:

• Accelerated application performance by removing data bottlenecks
• Consistent response times
• High availability of data
Key features:
• Time to value by using “plug-in” caching
• Single configuration (no collocation of data and applications)
• “Drop-in” strategy: HTTP session management, web side cache, and DynaCache
• Focus on ease of use, time to value, and manageability
Value of application-oriented scenario:
• State-of-the-art developer and architect accessibility to emerging transaction
processing patterns
• Scalable runtime for 24x7 operations
• Consistent response times for high-volume applications
Key features:
• High-performance, scalable transaction processing, event processing
• Caching and data management as foundational element
• Applications and data together (collocation)
• Focus on application pattern adoption, developer productivity, and runtime
management
V8.1
Student Notebook
Uempty
IBM Workload Deployer

• Secure, self-service cloud management hardware appliance
– Fully programmable and can integrate into an existing management
infrastructure
• Enables consistent and repeatable deployment of application
environments that are based on patterns
– Dispenses hardened WebSphere patterns into a pool or cloud of virtualized
hardware that is running a supported hypervisor
• Includes all functions from WebSphere CloudBurst Appliance, plus new
capabilities
– Integrates with existing infrastructure through programmable REST APIs
– More robust platform (more storage and compute power)
IBM Workload
WebSphere CloudBurst Deployer V3.1
Appliance V2.0
Figure 1-19. IBM Workload Deployer WA855 / VA8551.0
Notes:
IBM Workload Deployer, previously known as IBM WebSphere CloudBurst Appliance,
dispenses and manages IBM middleware to virtualized servers and private
cloud-computing environments. Workload Deployer manages two styles of patterns:
• The first style is “topology patterns,” which are customizable patterns of IBM
middleware that are packaged as “Hypervisor Edition” images. This familiar pattern was
available since WebSphere CloudBurst V1.0, but is more dynamic in Workload
Deployer V3.0. When IBM WebSphere Application Server Hypervisor Edition Intelligent
Management Pack is enabled in a deployed environment, users can enable automated
elasticity to allow patterns to grow and shrink without manual input.
• The second style of pattern is “workload patterns,” which contain all IT components that
are needed to run a certain type of workload. This type of pattern is less customizable,
but is designed to meet the needs of common use cases with little modification. As
such, workload patterns offer a much more cost-effective way of deploying and
managing suitable applications.
Student Notebook
IBM Tivoli Composite Application Manager for WebSphere

Application Server
• Data Collector available in WebSphere Application Server V8.5.5 as an
extension offering (optional download and installation)
• IBM Tivoli Composite Application Manager for WebSphere Application
Server provides more
request-based response
time and processor metrics
• Customer application code IBM Tivoli Composite
is not instrumented Application Manager
• Simple upgrade from IBM
Tivoli Composite
Application Manager for
Server to IBM Tivoli
Composite Application Manager for Application Diagnostics
• After upgrade IBM Tivoli Composite Application Manager data still
visible in Tivoli Performance Viewer
Figure 1-20. IBM Tivoli Composite Application Manager for WebSphere Application Server WA855 / VA8551.0
Notes:
With IBM Tivoli Composite Application Manager, administrators can view the health of
applications and servers. They can then drill down to diagnostic information for specific
application requests to identify the root cause of problems.
V8.1
Student Notebook
Uempty
Rational Application Developer

Team productivity Problem determination Enterprise connectivity

• Integration with Rational • Code visualization - class, • J2C (EIS) tools
Team Connect sequence, and topic diagrams • CICS and IMS adapters
• Collaborative debug • Static analysis (code review) • WebSphere Adapters for SAP,
• Collaborative code • Code coverage: optimize unit Siebel, JDE, Oracle, and
analysis testing PeopleSoft
Programming model support WebSphere integration

• Create, edit, validate applications • WebSphere test servers: V7.0, V8.0,
• SCA, Java Batch, XML feature pack V8.5 and Liberty profile
• Create and debug Jython and
• Standards: Java EE (Web, EJB, Web wsadmin scripts
Services, JAX-RS…), SCA, OSGi, SIP, XML, • Portal tools and server support
Web (JSF, Dojo, JavaScript, Web 2.0)
• Profile applications on WebSphere
• Debug applications on WebSphere Application • Find and deploy to WebSphere or
Server Portal instances in the IBM SBDT
• Database tools cloud
• Integration with ClearCase SCM Adapter, • IBM Workload Deployer 3.1, 3.0
Rational RequisitePro, RUP
Figure 1-21. Rational Application Developer WA855 / VA8551.0
Notes:
Rational Application Developer is the only IDE you need when you want to design, develop,
and deploy your applications. It provides a development environment for building
applications that run on WebSphere Application Server V8.5.5.
Student Notebook
IBM Assembly and Deploy Tools for WebSphere Administration
• Rapidly assemble and deploy applications to WebSphere Application

Server environments
• The tool replaces the previously available IBM Rational Application

Developer Assembly and Deploy function in V7
– Restricted to assembly and deployment usage only
• Key capabilities include:

– Import and validate applications
– Edit deployment descriptors and binding files
– Edit EAR-level configuration (enhanced EAR)
– Create and debug Jython and wsadmin scripts
– Deploy EJB and web services
– Deploy applications to local or remote WebSphere servers
– Debug applications on WebSphere
Figure 1-22. IBM Assembly and Deploy Tools for WebSphere Administration WA855 / VA8551.0
Notes:
The application assembly and deployment tools that are delivered together with the
WebSphere Application Server Version 8.5 offering are the IBM Assembly and Deploy
Tools for WebSphere Administration. With IBM Assembly and Deploy Tools for WebSphere
Administration, developers can accomplish key assembly and deployment needs including
editing of deployment artifacts, script development and testing, and application deployment
and debugging. This tool is not intended for general application development.
V8.1
Student Notebook
Uempty
Unit summary
Having completed this unit, you should be able to:
• Describe the relationships between various products in the WebSphere
family
Figure 1-23. Unit summary WA855 / VA8551.0
Notes:
Student Notebook
Checkpoint questions
1. What is the main difference between the Express and base
WebSphere Application Server editions?
2. Which WebSphere Application Server edition do you need if you

want to deploy a single application with low transaction volume?
3. True or False: WebSphere Application Server Hypervisor Edition is

shipped in OVF format, which includes WebSphere Application
Server and the operating system.
4. True or False: Support is included for mixed WebSphere Application

Server releases in a cell.
Figure 1-24. Checkpoint questions WA855 / VA8551.0
Notes:
Write your answers here:
1. 
2. 
3. 
4. 
V8.1
Student Notebook
Uempty
Checkpoint answers
1. What is the main difference between the Express and base
WebSphere Application Server editions?
– The Express edition license covers only two processors. The license for the
base edition covers unlimited processors.
2. Which WebSphere Application Server edition do you need if you
want to deploy a single application with low transaction volume?
– Any edition allows you to deploy a single application with low transaction
volume.
3. True or False: WebSphere Application Server Hypervisor Edition is
shipped in OVF format, which includes WebSphere Application
Server and the operating system.
– True
4. True or False: Support is included for mixed WebSphere Application
Server releases in a cell.
– True
Figure 1-25. Checkpoint answers WA855 / VA8551.0
Notes:
Student Notebook
V8.1
Student Notebook
Uempty Unit 2. WebSphere Application Server

architecture – stand-alone

This unit provides an architectural overview of WebSphere Application
Server V8.5.5 at run time.

• Describe a typical e-business application architecture
• Describe the architectural differences between WebSphere
Application Server packages
• Describe what is running in a WebSphere Application Server node
• Describe the architectural implications of the web server plug-in
• Describe the use of Java Database Connectivity (JDBC) providers
and data sources

• Checkpoint questions
References
index.jsp
© Copyright IBM Corp. 2013 Unit 2. WebSphere Application Server architecture – stand-alone 2-1
Student Notebook
Unit objectives
• Describe the architectural differences between WebSphere Application
Server packages
• Describe the use of Java Database Connectivity (JDBC) providers and
data sources
Notes:
V8.1
Student Notebook
Uempty
Topics
• Architecture runtime
• Architecture administration
• Profiles
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 2.1. Architecture runtime

This topic provides information about architecture runtime.
Student Notebook
Architecture runtime

Figure 2-3. Architecture runtime WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Version 8.5 packaging
WebSphere Application Server Network Deployment
Clustering Node agent Deployment manager
Intelligent Management Web Services Gateway
WebSphere Application Server

and
WebSphere Application Server Express (up to two processors)
Web-based admin Web services
EJB container Messaging
Web container JDK
PMEs
Figure 2-4. Version 8.5 packaging WA855 / VA8551.0
Notes:
In this unit, the focus is on the Express and Base versions of WebSphere Application
Server. All of the concepts that this unit presents are applicable to all three versions:
Express, Base, and Network Deployment.
Student Notebook
WebSphere Application Server basics

– Is a platform on which Java based business applications run
– Is an implementation of the Java Platform, Enterprise Edition (Java EE)
specification
– Provides services (database connectivity, threading, workload management) that
the business applications can use
Application
Application Server
Hardware, operating system, database,

network, storage
Figure 2-5. WebSphere Application Server basics WA855 / VA8551.0
Notes:
This diagram illustrates the differences between the application, the application server, and
the hardware and operating system layers. WebSphere Application Server is a platform on
which Java based business applications run and is an implementation of the Java Platform,
Enterprise Edition specification. It provides services (database connectivity, threading,
workload management) that the business applications can use.
V8.1
Student Notebook
Uempty
WebSphere architecture runtime (1 of 10)
Browser
Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013
Figure 2-6. WebSphere architecture runtime (1 of 10) WA855 / VA8551.0
Notes:
This diagram illustrates the basic architecture of WebSphere Application Server, including
several of the larger components.
The main element is the application server, a Java process that encapsulates many
services, including the containers, where business logic runs. If you are familiar with Java
EE, you recognize the web container and the EJB container. The web container runs
servlets and JavaServer Pages (JSPs), both of which are Java classes that generate
markup that a web browser can view. Traffic into and out of the web container travels
through the embedded IBM HTTP Server. While servlets and JSPs can act independently,
they most commonly make calls to EJBs to run business logic or access data. EJBs, which
run in the EJB container, are easily reusable Java classes. They most commonly
communicate with a relational database or other external source of application data, either
returning that data to the web container or changing the data on behalf of the servlet or
JSP.
The JMS messaging engine is built into the application server. This messaging engine is
pure Java. JMS destinations, which are known as queues and topics, provide
Student Notebook
asynchronous messaging services to the code that runs inside the containers. JMS is
covered in more depth later in this course.
As you see in more detail later on, the web services engine provides the ability for
application components to be exposed as web services, which can be accessed by using
SOAP.
Several other services are run within the application server, including the dynamic cache,
data replication, security, and others. You look at these topics later in the course.
In addition, there are some important components outside of the application server
process.
WebSphere Application Server also provides a plug-in for HTTP servers that determines
the HTTP traffic that WebSphere intends to handle, and routes the requests to the
appropriate server. The plug-in is also a critical player in workload management of HTTP
requests, as it can distribute the load to multiple application servers, and steer traffic away
from unavailable servers. It also reads its configuration from a special XML file.
1 of 10: The browser is the main interaction mechanism for users.
V8.1
Student Notebook
Uempty
Browser
HTTP(S)
HTTP
server
Notes:
2 of 10: A browser communicates with a web server (HTTP server).
Student Notebook

Application Server
Browser
Web container
Embedded HTTP
Servlets
Server
HTTP
server JSPs
Plug-in
Plug-in
configuration
file
Notes:
3 of 10: The way the request gets into the WebSphere Application Server is from the HTTP
server plug-in that is loaded with the HTTP server. This request is forwarded to the
embedded HTTP server within the application server. The embedded server forwards the
request into the web container to either a servlet or a JSP.
V8.1
Student Notebook
Uempty

Application Server
Browser
Web container EJB container
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
Plug-in
configuration
file
Notes:
4 of 10: If these servlets or JSPs access distributed business logic or a database, the Java
EE way to accomplish it is through EJBs within the EJB container.
Student Notebook

Application Server
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
Plug-in Application
configuration data
file
Notes:
5 of 10: EJBs (entity in this case) can communicate with the database to store, retrieve,
query, and delete data. JDBC is one way that this communication can occur.
V8.1
Student Notebook
Uempty

Application Server
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX
Data replication Security
Name server Other services
Notes:
6 of 10: Many other services are provided within WebSphere Application Server. Some of
those services are listed here.
Student Notebook

Application Server
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
configuration data
file
Dynamic cache JMX
Notes:
7 of 10: The browser can communicate directly with the embedded HTTP server
(bypassing the external web server); use this direct communication only for testing and
development purposes. In this way, you access your application servers in many of the lab
exercises.
V8.1
Student Notebook
Uempty

Java
Application Server client
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
configuration data
file
Dynamic cache JMX
Notes:
8 of 10: Browsers are not the only clients; a pure Java client can access EJBs directly
through RMI/IIOP.
Student Notebook

Java
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
configuration data
file
Dynamic cache JMX
Web
services
client
Notes:
9 of 10: Web services clients can also access your application server. This communication
occurs in two ways:
• Through SOAP over HTTP and passing through the embedded HTTP server
• Through SOAP over JMS communicating directly to the messaging engine within the
application server
V8.1
Student Notebook
Uempty

Java
Browser
Embedded HTTP
Servlets
Server
HTTP EJBs
server JSPs
Plug-in
configuration data
file
Dynamic cache JMX

Web JMS
services client
client
Legend HTTP/S RMI/IIOP SOAP JDBC JMS

Notes:
10 of 10: Finally, you can use a JMS client to communicate directly with the messaging
engine.
Student Notebook
JDBC providers
• Provide the JDBC driver implementation for database access
– Type 2 JDBC drivers (thick): require the database client software on the client
node to connect to the database server
– Type 3 JDBC drivers (net protocol): require server-side code to map net
protocol to native database
– Type 4 JDBC drivers (native protocol): connect directly to the database by
using its native protocol
• XA drivers support transaction recovery
Client node
JNDI Connection
pool JDBC Database
Database
client
JDBC driver server
Data source
Figure 2-16. JDBC providers WA855 / VA8551.0
Notes:
To access a database from an application server, a JDBC provider is necessary. The JDBC
provider allows access to the database through a JDBC driver implementation for database
access. There are three different JDBC driver implementations available with the
application server.
• Type 2 JDBC drivers, sometimes known as “thick”, require the database client software
on the client node to connect to the database server.
• Type 3 JDBC drivers (net protocol) require server-side code to map net protocol to the
native database.
• Type 4 JDBC drivers (native protocol) connect directly to the database by using its
native protocol.
XA drivers support transaction recovery.
V8.1
Student Notebook
Uempty
Data sources
• Data sources can improve performance and portability for database
access
– Standard and XA data sources
• Two parts provide connection pooling:

– J2C connection manager
– Relational resource adapter
• Connection factories are similar to data sources

– Typically connect to external resources that are not databases
Relational resource
adapter
Application
Data source
or Connection Database
Connection pool
factory
J2C
connection
manager © Copyright IBM Corporation 2013
Figure 2-17. Data sources WA855 / VA8551.0
Notes:
Rather than having the JDBC drivers communicate directly with the database, the
communication is abstracted into a data source.
Student Notebook
V8.1
Student Notebook
Uempty 2.2. Architecture administration

This topic provides information about architecture administration.
Student Notebook
Architecture administration

Figure 2-18. Architecture administration WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere architecture administration (1 of 4)

Application Server
Embedded HTTP
Servlets
EJBs
Server
JSPs

engine engine
Dynamic cache JMX
Figure 2-19. WebSphere architecture administration (1 of 4) WA855 / VA8551.0
Notes:
Earlier, you saw the runtime depiction of a WebSphere Application Server. This diagram
illustrates the basic architecture of administering WebSphere Application Server.
Two main tools are used to administer WebSphere Application Server: the administrative
console and the wsadmin command-line tool.
The configuration of the server is stored in a set of XML files, often referred to as the
configuration repository. These files define the server itself, and the resources and services
that it provides.
1 of 4: This diagram is a standard application server, as previously mentioned.
Student Notebook

Application Server

Admin
Embedded HTTP
Servlets service
JSPs EJBs
Server
Admin
Admin
MBeans
application

engine engine
Dynamic cache JMX
XML
configuration
files
Notes:
2 of 4: One of the services available within the application server is the administrative
service. This service allows for configuration of the application server. The files necessary
for configuration are stored outside of the actual application server in a set of XML
configuration files. An application that runs within the web container provides users the
ability to administer the application server through a web application: the administrative
console.
V8.1
Student Notebook
Uempty

Application Server
Web-based
administrative
console Web container EJB container
Admin
Embedded HTTP
Servlets service
JSPs EJBs
Server
Admin
Admin
MBeans
application

engine engine
Dynamic cache JMX
XML
Legend HTTP/S RMI/IIOP SOAP/HTTP File I/O configuration
files
Notes:
3 of 4: This diagram illustrates communication from the browser to the XML configuration
files.
Student Notebook

Application Server
Web-based
administrative
console Web container EJB container
Admin
Embedded HTTP
Servlets service
JSPs EJBs
Server
Admin
Admin
MBeans
application
Web services
engine Messaging
engine
wsadmin
command-line Dynamic cache JMX
client
C:\> wsadmin
XML
Legend HTTP/S RMI/IIOP SOAP/HTTP File I/O configuration
files
Notes:
4 of 4: The wsadmin command-line client is used to administer the application server
through SOAP, by communicating with the embedded HTTP server, or by using RMI (the
default) to communicate directly with the administrative service.
V8.1
Student Notebook
Uempty 2.3. Profiles

This topic provides information about profiles.
Student Notebook
Profiles

Figure 2-23. Profiles WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere profile overview

Profiles are sets of files that represent a
WebSphere Application Server configuration
WebSphere Application Server files are split

into two categories: WebSphere
product files
• Product files (binary files)
– Set of shared read-only static files or product
binary files
– Shared among any instances of the WebSphere Profile files
Application Server product DmgrProfile
profile1
profile2
• Profiles (configuration files)
– Set of user-customizable data files
– Files include WebSphere configuration, installed
applications, resource adapters, properties, and
log files
Figure 2-24. WebSphere profile overview WA855 / VA8551.0
Notes:
Profiles are the configuration mechanism that allows you to run more than one application
server on a single installation of WebSphere product files.
For a stand-alone server, the dmgr profile would not exist yet. The dmgr profile is explained
in the next unit.
Student Notebook
WebSphere profile benefits

• Benefits of profiles:
– Each profile uses the same product files
– Simpler than multiple WebSphere installations
– Less disk space
– Simplifies application of product updates
profile1 profile2
Figure 2-25. WebSphere profile benefits WA855 / VA8551.0
Notes:
Notice that under the WebSphere installation directory (<was_root>) there are
subdirectories for each profile. In the example that is shown, two application servers are
each configured according to the files that exist within their own profile directory.
V8.1
Student Notebook
Uempty
Managing profiles
2
Profiles are managed through one of the tools provided:

1. Profile Management Tool
• Accessed through the WebSphere Customization Toolbox
• Gathers user input and starts the manageprofiles
command-line tool to create the profiles
2. manageprofiles script
• Command-line interface for profile management functions
Figure 2-26. Managing profiles WA855 / VA8551.0
Notes:
These two tools are available for creating and managing profiles. Profiles are managed
through one of the tools provided:
1. The Profile Management Tool (PMT) wizard is an Eclipse-based GUI tool for creating
profiles. The wizard gathers user input and starts the manageprofiles command-line
tool to create the profiles.
2. The manageprofiles script is run from a command-line interface for profile
management functions.
Student Notebook
Profile types
• Cell
– Deployment manager with a federated application server
• Management
– Administrative agent
– Deployment manager
– Job manager
• Application server
– Stand-alone
• Custom profile
– Federated node
(no application server)
• Secure proxy
Figure 2-27. Profile types WA855 / VA8551.0
Notes:
There are numerous profile types:
• Cell
- Deployment manager with a federated application server
• Management
- Administrative agent
- Deployment manager
- Job manager
- Stand-alone
• Custom profile
- Federated node
- (No application server)
- Secure proxy
V8.1
Student Notebook
Uempty
Unit summary
• Describe the architectural differences between WebSphere Application
Server packages
• Describe the use of Java Database Connectivity (JDBC) providers and
data sources
Notes:
Student Notebook
1. Which of the following provides an environment for running servlets?
A. Client module
B. Web container
C. EJB module
2. Which type of JDBC driver is considered a “thick” driver?

A. Type 2
B. Type 3
C. Type 4
3. Which of the following are components contained within the JVM of

the application server?
A. HTTP Server plug-in
B. Embedded HTTP Server
C. DB2 database
Notes:
1. 
2. 
3. 
V8.1
Student Notebook
Uempty
Checkpoint answers
1. Which of the following provides an environment for running servlets?
B. Web container
2. Which type of JDBC driver is considered a “thick” driver?

A. Type 2
3. Which of the following are components contained within the JVM of

the application?
B. Embedded HTTP Server
Notes:
Student Notebook
V8.1
Student Notebook

architecture – federated

This unit describes the concepts and terminology of a Network
Deployment installation.

• Describe the Network Deployment runtime flow
• Describe Network Deployment concepts and terminology, such as
cell, node, node agent, and deployment manager
• Describe the Network Deployment administration flow
• Explain how to manage web servers from WebSphere Application
Server

References
http://publib.boulder.ibm.com/infocenter/wasinfo/v8r5/
index.jsp
© Copyright IBM Corp. 2013 Unit 3. WebSphere Application Server architecture – federated 3-1
Student Notebook
Unit objectives
• Describe Network Deployment concepts and terminology, such as cell,
node, node agent, and deployment manager
Server
Notes:
V8.1
Student Notebook
Uempty
Topics
• Network deployment concepts
• Managing web servers
• Additional concepts
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 3.1. Network deployment concepts
Student Notebook
Network deployment
concepts

Figure 3-3. Network deployment concepts WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Version 8.5 packaging
WebSphere Application Server Network Deployment
Clustering Node agent Deployment manager
Intelligent Management Web Services Gateway

and
WebSphere Application Server Express (up to two processors)
Web-based admin Web services
EJB container Messaging
Web container JDK
PMEs
Figure 3-4. Version 8.5 packaging WA855 / VA8551.0
Notes:
This unit focuses on the Network Deployment version of WebSphere Application Server.
Student Notebook
Network deployment concepts

• A deployment manager (DMgr) process manages the node agents
– Holds the configuration repository for the entire management domain, called a
cell
– Within a cell, the administrative console runs inside the DMgr
• A node is a logical grouping of application servers
– A single node agent process manages each node
– Multiple nodes can exist on a single machine by using profiles
Cell Deployment
manager
Node 01 Node 02
Node Node
agent agent
AppSrv01 AppSrv02 AppSrv03 AppSrv04
Notes:
The deployment manager is an application server that manages the administrative
environment within a cell. As you see later in this unit, a node is represented as a profile.
The node agent is an important process that allows for communication of administrative
information, such as commands and configuration files, to reach the application servers.
V8.1
Student Notebook
Uempty
Network deployment runtime flow
HTTP server Node A

Browser
AppSrv01
AppSrv02
Plug-in
Load Java
balancer Plug-in config client
HTTP server Node B
AppSrv03
Application
data
Legend AppSrv04
HTTP or Plug-in
HTTPS
Plug-in config
JDBC
RMI/IIOP
Figure 3-6. Network deployment runtime flow WA855 / VA8551.0
Notes:
The main theme with Network Deployment is distributed applications. While the “flow” of an
application remains the same, there are significant additions to the runtime of an
application. Note the “load balancer”: it allows for multiple HTTP servers. Users point their
browsers to the load balancer, and their requests are workload managed to an HTTP
server. When a request arrives at one of these HTTP servers, the HTTP server plug-in load
balances the request between the application servers that it is configured to serve. When
the request enters the application server, the flow is identical to how it was in Express and
Base.
The Java client requests to EJBs can also be workload managed so that the requests do
not all arrive at one application server.
Student Notebook
Administration flow Node A

Node agent
Administrative Deployment manager Admin service

console
Web container Cell config AppSrv01
Admin application Node A cfg
AppSrv01 cfg Admin service
C:\> wsadmin Admin service EAR

wsadmin
command line Node B
Legend Master repository Node agent

HTTP/S Cell config
SOAP/HTTP Node A cfg Admin service

or AppSrv01 cfg Cell config AppSrv03
RMI/IIOP Node B cfg Node B cfg
RMI/IIOP AppSrv03 cfg AppSrv03 cfg Admin service
File sync
File I/O EAR EAR
Figure 3-7. Administration flow WA855 / VA8551.0
Notes:
The administrative console and wsadmin are the two ways that the environment is
administered. However, these tools communicate with the deployment manager and not
with the application servers directly. The communication flow of these commands is from
the tools to the deployment manager, to the node agents, to the application servers. This
flow allows for the administration of multiple nodes from a single focal point (the
deployment manager). Each node can possibly contain multiple application servers.
There is one main (master) repository for the configuration files within a cell, and those files
are associated with the deployment manager. All updates to the configuration files go
through the deployment manager. Be careful about directly connecting to an application
server with wsadmin or the administrative console. Any changes to the configuration files
are only temporary and are overwritten with the configuration files from the master files
(repository).
V8.1
Student Notebook
Uempty
File synchronization
Deployment manager Node A
Web container
Admin application
Node agent
Admin service File sync service File sync service
1 Admin service
Master repository AppSrv01
Cell config Cell config

Admin service
Node A cfg Node A cfg
AppSrv01 cfg AppSrv01 cfg AppSrv02
AppSrv02 cfg AppSrv02 cfg
Node B cfg Admin service
AppSrv03 cfg EAR
AppSrv04 cfg
2
EAR
Figure 3-8. File synchronization WA855 / VA8551.0
Notes:
Each managed process, node agent, and deployment manager starts with its own set of
configuration files. The deployment manager contains the master configuration. Any
changes at the node agent or server level are local, and the master configuration overrides
them at the next synchronization (update).
1. Node agents synchronize their files with the master copy either automatically or
manually. Automatic synchronization can be done at startup or scheduled periodically.
Manual synchronization is done with the administrative console or from the command
line.
2. During synchronization, the node agent asks for changes to the master configuration.
Any new or updated files are copied to the node.
Student Notebook
WebSphere Network Deployment profiles

Benefits of profiles in network deployment
• Think of profiles as representing a node
• Can install multiple profiles on a single machine
All profiles use the same product files

• Application server profile (stand-alone)
– Equivalent to Base or Express application server
– Has a node name and a cell name property, and corresponding directories
– Cell directory is overwritten upon federation
• Deployment manager profile
– Creates a deployment manager
• Custom profile (managed)
– Creates a managed node which, by default, is federated into a cell
– Creates a node agent, but no application servers
• Cell profile
– Creates both a deployment manager and a federated node
• Others
Figure 3-9. WebSphere Network Deployment profiles WA855 / VA8551.0
Notes:
The addition of Network Deployment to this discussion does not change the definition of a
profile. The WebSphere configuration is still built by creating profiles, which consist of
product binary files and configuration files. The profile that is listed as a “stand-alone node”
is listed here as an “application server”. The deployment manager profile is added, which is
a special type of node that manages the administrative domain of a cell.
V8.1
Student Notebook
Uempty 3.2. Managing web servers
Student Notebook
Managing web servers

Figure 3-10. Managing web servers WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Web servers within a cell

Web servers are customized
• Each web server plug-in is customizable
• Requires a web server definition
– Defining a web server does not mean that it is managed
• Plug-in properties are defined on a per web server basis
• Each plug-in has a unique plugin-cfg.xml generated for it
• A cell level plugin-cfg.xml can also be generated
Web servers can optionally be managed

• Web servers can be unmanaged
– No management is available
• You can manage web servers by:
– A node agent
– The IBM HTTP Server administrative process
Figure 3-11. Web servers within a cell WA855 / VA8551.0
Notes:
Web servers within a cell are customized. Each web server plug-in is customizable and
requires a web server definition. Defining a web server does not mean that it is managed;
plug-in properties are defined on a web-server-by-web-server basis. Each plug-in has a
unique plugin-cfg.xml file that is generated for it; a cell level plugin-cfg.xml can also
be generated.
Web servers can be managed or they can be unmanaged. For a managed web server, a
node agent or the IBM HTTP Server administrative process can manage it.
Student Notebook
Managed versus unmanaged nodes

• A managed node is a node that contains a node agent
• An unmanaged node is a node in the cell without a node agent

– The rest of the environment can be aware of the node
– Useful for defining HTTP servers as part of the topology
– Allows creation of different plug-in configurations for different HTTP servers
Cell Deployment
manager
Node 02
Node
Unmanaged node agent
AppSrv03 AppSrv04
Figure 3-12. Managed versus unmanaged nodes WA855 / VA8551.0
Notes:
A node agent is a process that handles communications with the resources within the
node.
An unmanaged node has no node agent. It is a reference to a machine somewhere in the
topology. Typically an unmanaged node is used to define the location of web servers.
V8.1
Student Notebook
Uempty
Web server definitions (1 of 2)

• Web server definitions are created to allow the mapping of Java EE
enterprise applications to specific web servers
– Can be done through the administrative console
– By default, all currently installed applications are mapped to a web server created
using the admin console
Figure 3-13. Web server definitions (1 of 2) WA855 / VA8551.0
Notes:
Just as modules for an enterprise application must to be mapped to one or more
application servers, they also must be mapped to one or more web servers. When you
define a web server, the default is that all currently installed applications are mapped to the
web server.
Student Notebook
Web server definitions (2 of 2)

• Alternately use the script that is generated during the configuration of
the plug-in, which can automate the mapping of all the applications to
the web server
configure<Web_server_name>.bat in <plugin_root>\bin
HTTP server
C:\...\configurewebserver1.bat
Plug-in
Application
All currently installed applications
server
Mapped to this web server
plugin-cfg.xml
Figure 3-14. Web server definitions (2 of 2) WA855 / VA8551.0
Notes:
When the web server plug-in is configured, a script is generated that you can use to define
the web server. The script uses the same defaults as defining the web server in the
administrative console.
V8.1
Student Notebook
Uempty
Web server custom plugin-cfg.xml

• Mapping the applications to specific web servers causes the plugin-
cfg.xml files for only those web servers to include the information for
those applications
– Target-specific web server applications that run in a cell
– Deployment manager automatically generates them
Application module explicitly mapped to a web server
Figure 3-15. Web server custom plugin-cfg.xml WA855 / VA8551.0
Notes:
After the web servers are defined, any applications that are installed after the web servers
are defined must be explicitly mapped to a web server.
Student Notebook
Managing plugin-cfg.xml files

• plugin-cfg.xml files are plugin-cfg.xml files can be generic to a
automatically generated and cell or custom to web server
propagated • Generating a cell generic
plugin-cfg.xml file
• This behavior is the default, but
can be changed – Use the command-line script
<was_root>\bin\GenPluginCfg.bat
• This behavior is configurable – Not available through the console
through the console • Generating a web server custom
plugin-cfg.xml file
– Use the administrative console
– Must map applications to web servers
– Can customize the plug-in settings of each
web server
Figure 3-16. Managing plugin-cfg.xml files WA855 / VA8551.0
Notes:
The plugin-cfg.xml files are automatically generated and propagated. This behavior is
the default, but it can be changed; it is configurable through the console.
The plugin-cfg.xml files can be generic to a cell or custom to a web server. To generate
a cell generic plugin-cfg.xml file, use the command-line script:
<was_root>\bin\GenPluginCfg.bat
This action is not available through the console.
To generate a web server custom plugin-cfg.xml file, you use the administrative
console. You map applications to web servers, and you can customize the plug-in settings
for each web server.
V8.1
Student Notebook
Uempty
Managing web server plug-in properties
• Each web server can

have customized
plug-in configuration
settings
– Not just application
mappings
Figure 3-17. Managing web server plug-in properties WA855 / VA8551.0
Notes:
The links on the right side of the page under Additional Properties provide access to pages
for changing the plug-in properties.
Student Notebook
Virtual hosts
• Configuration that allows a host machine to resemble multiple host
machines
• Each virtual host has a logical name and one or more host aliases
• There are several default virtual hosts, including:
– default_host: used for accessing the default applications
Example: http://localhost:9080/snoop
– admin_host: used for accessing the administrative console
Example: http://localhost:9060/ibm/console
Application server
HTTP server
Browser
Plug-in
Virtual host important here

Figure 3-18. Virtual hosts WA855 / VA8551.0
Notes:
The virtual hosts definition for the application server determines not which ports are
listened to, but what ports are acceptable for the incoming URL. Since most requests come
in from the external HTTPd, the ports that are specified either explicitly or implicitly
(because of the protocol used) are 80 and 443. If an administrator wants to allow other
ports to be used, the ports must be specified on the virtual host to which the application is
mapped. If direct access is required to an application (without going through an external
web server), adding the port that the application server accepts for incoming requests to
the virtual host definition makes that possible. More specifically, if an application server
listens to port 9084 and direct access was required (http://<hostname>:9084/<uri>),
then adding 9084 to the virtual host definition makes that possible.
A virtual host is a configuration that allows a host machine to resemble multiple host
machines.
• Allows one machine to support multiple applications
• Associated with the cell, not a single node
V8.1
Student Notebook
Uempty • Allows plug-in to route requests to the correct servers

Each virtual host has a logical name and one or more host aliases.
• Each alias is a host name and port combination (allows wildcards)
• Example: *:80, *:443, *:9080, *:9060
Student Notebook
Defining virtual hosts
Figure 3-19. Defining virtual hosts WA855 / VA8551.0
Notes:
This slide shows the definition for “default_host.” Notice that the host aliases are specified
with the “*” symbol. Using the “*” symbol means that a request for any host name on ports
9080, 80, and 9443 is forwarded to this host. When applications are installed, web modules
within those applications must be mapped to a virtual host.
V8.1
Student Notebook
Uempty
Managing web servers with WebSphere

Deployment manager can manage external web servers
• IBM HTTP Server (special case; no node agent needed)
– Deployment manager can distribute plugin-cfg.xml files to web server
machines
– Can be started and stopped
– Can edit the httpd.conf
• Other web servers (node agent needed)
– Can have plugin-cfg.xml files that are automatically distributed to them
– Can be started and stopped
Web servers are defined within WebSphere cell topologies

• Managed node (local) or unmanaged node (remote)
– Managed nodes use a node agent to control the web server
– Unmanaged nodes use the IBM HTTP Server Admin Service instead of a node
agent to control the web server
Figure 3-20. Managing web servers with WebSphere WA855 / VA8551.0
Notes:
There are three types of WebSphere Application Server nodes upon which you can create
and manage a web server. Over the next several pages, three common web server
management scenarios are presented:
• Using a web server as an unmanaged node
• Using IBM HTTP Server as an unmanaged node
• Using a web server as a managed node
Student Notebook
Unmanaged web server Cell Deployment

Unmanaged Manual manager
copy or
shared file
HTTP server plugin-cfg.xml
Node
Node
Unmanaged
agent
web server
definition
Plug-in
AppSrv01 AppSrvN
plugin-cfg.xml
• WebSphere node agent does not manage web server (other than IBM HTTP
Server)
– Allows WebSphere system administrator to create custom plug-in files for a
specific web server
– Application mappings
– SSL certificates
• Manually copy or use FTP to transfer the plug-in configuration file from the
deployment manager machine to the web server machine
Figure 3-21. Unmanaged web server WA855 / VA8551.0
Notes:
The web server is registered as an unmanaged node in this WebSphere configuration. This
scenario is common for web servers that are installed outside the firewall or in a DMZ
where no WebSphere Application Server exists. The implication with this scenario is that all
management of the web server occurs manually, which is outside the control of WebSphere
Application Server.
V8.1
Student Notebook
Uempty
Managed web server on a managed node (local)
Managed node Managed Deployment

web server manager
HTTP server Node definition
Manages
agent
Node
Node
agent
Plug-in Local
plug-in
installation
plugin-cfg.xml AppSrv01 AppSrvN
Cell
• Install a web server on a managed node

• Create a web server definition within the DMgr
• Node agent receives commands from DMgr to administer the web server
•plugin-cfg.xml file is propagated through the file synchronization
service and is in the config directory
• Warning: security issues if this configuration spans a DMZ
Figure 3-22. Managed web server on a managed node (local) WA855 / VA8551.0
Notes:
The deployment manager manages the web server through the node agent. In this way,
you can start or stop the web server and automatically push the plug-in configuration file to
the web server from the deployment manager. This configuration can be used when the
web server is installed on the same machine as the WebSphere Application Server is
installed. It is a common scenario for behind a firewall where a WebSphere node can be
installed.
A node agent communicates with the web server from the administrative tools of
WebSphere.
It might be undesirable to use this configuration, since access to the node agent in a DMZ
can compromise security.
Student Notebook
IBM HTTP Server as unmanaged node (remote)

Unmanaged node
Deployment
HTTP server manager
IBM HTTP Server administrative process
Node
httpd.conf file Node

Plug-in agent
Remote plug-in
plugin-cfg.xml
installation AppSrv01 AppSrvN
Cell
• The IBM HTTP Server administrative process provides administrative

functions for IBM HTTP Server within WebSphere
– Able to start, stop IBM HTTP Server, make configuration changes to
httpd.conf, and automatically push the plug-in configuration file to IBM HTTP
Server machine
– Node agent is not needed on the web server machine
Figure 3-23. IBM HTTP Server as unmanaged node (remote) WA855 / VA8551.0
Notes:
IBM HTTP Server can be managed completely from the deployment manager (dmgr). The
dmgr communicates with the IBM HTTP Server administrative process that runs on the
node with IBM HTTP Server. There are actually two Apache instances (processes) on the
IBM HTTP Server machine: one running the administrative services and one containing the
plug-in.
UNIX note: On UNIX operating systems, the user ID under which the IBM HTTP Server
administrative process runs must have write permissions to the plugin-cfg.xml file. By
default, when IBM HTTP Server is installed, root owns the plugin-config.xml file, and
only root has write access to it. The result is a failure with propagation of the
plugin-cfg.xml file when it is run from the administration tools.
V8.1
Student Notebook
Uempty
IBM HTTP Server administration overview

• Direct administration of IBM HTTP Server V7 by manually editing
httpd.conf
• There is no web-based console for IBM HTTP Server as there was in
previous versions
IBM HTTP Server
httpd.conf file
Plug-in
plugin-cfg.xml
Figure 3-24. IBM HTTP Server administration overview WA855 / VA8551.0
Notes:
The user interface that was used to administer IBM HTTP Server in earlier versions no
longer exists. You must either manually make updates to the httpd.conf file, or use the
administrative console.
Student Notebook
IBM HTTP Server administration server

• IBM HTTP Server administration server runs as a separate instance of
IBM HTTP Server
• Administrative component for IBM HTTP Server V7 includes:
– IBM HTTP Server administration configuration file (admin.conf)
– Default port for the IBM HTTP Server administration server is 8008
• IBM HTTP Server administration authentication password file

(admin.passwd)
– Initially blank, which prohibits access to IBM HTTP Server administration
– Administrator updates IBM HTTP Server admin password file by using:
> htpasswd -cm ..\conf\admin.passwd <user_name>
• To start and stop the administration server:

– <ihs_root>/bin/adminctl start
– <ihs_root>/bin/adminctl stop
– Or Windows service
Figure 3-25. IBM HTTP Server administration server WA855 / VA8551.0
Notes:
There are no changes from previous versions of IBM HTTP Server on UNIX operating
systems. The functionality in version 6 is now extended to Windows operating systems.
V8.1
Student Notebook
Uempty 3.3. Additional concepts
Student Notebook
Additional concepts

Figure 3-26. Additional concepts WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Flexible management
• Loose management coupling
• Coordinates management across a group of endpoints
– One job to install application across a number of nodes
• Can manage through administrative agent or deployment manager
Node A
Node C
AppSrv01
Node
Admin agent
AppSrv02 agent
Deployment
manager
AppSrvN AppSrv01 AppSrvN
Node D
Node B
AppSrv01 Job manager Node
•Control agent
Admin multiple
AppSrv02 agent endpoints
•Remote
management AppSrv01 AppSrvN
AppSrvN Cell
•Loose coupling
Figure 3-27. Flexible management WA855 / VA8551.0
Notes:
Flexible management is an approach that allows an administrator to manage multiple
application servers or cells through a loose asynchronous interface. Flexible management
is covered later in this course.
Student Notebook
Centralized Installation Manager (CIM)

• Simplifies the installation and maintenance of application servers within
a Network Deployment cell
• Install, update, uninstall version 8.x and all Installation Manager
installable products
• For V7 nodes in a v8.x cell

– Pushes remote binary files or maintenance to remote targets
– Starts the standard or update installer to complete the installation of the update
Figure 3-28. Centralized installation manager (CIM) WA855 / VA8551.0
Notes:
The CIM pushes the product binary files or maintenance to the remote targets and starts
the standard installer or update installer tool to complete the installation or update on the
targets, allowing you to:
• Download interim fixes and fix packs from IBM support directly to the CIM repository
• Install interim fixes and fix packs on target nodes with the Network Deployment cell
• Monitor download and installation status of packages through the administrative
console
V8.1
Student Notebook
Uempty
Intelligent runtime provisioning

• Dynamic start of server components that are
based on application needs
• Reduces runtime footprint; less memory
required
• Can significantly reduce startup times
• Disabled by default
V6.1 server V8.5 server
Web container Web container

EJB container EJB container
Web services Web services
SIP container SIP container
Security Security
HA manager HA manager Dynamically
All
activated
Infrastructure… activated Infrastructure…
Figure 3-29. Intelligent runtime provisioning WA855 / VA8551.0
Notes:
Intelligent runtime provisioning allows the application server to start faster and with less
memory because it loads only those components that are required. As other services are
needed, they are loaded on demand.
Student Notebook
Edge Components
• WebSphere Application Server Network
Deployment package
contains the
following Edge
Components
functions: Caching Load
Client
– Load balancer proxy balancer
– Caching proxy Cluster of

load-balanced
• Edge Components install separately servers
from WebSphere Application Server
• Load balancer is responsible for balancing the load across
multiple servers that can be within either local area networks or wide
area networks
• Purpose of caching proxy is to reduce network congestion within an
enterprise by offloading security and content delivery from web servers
and application servers
Figure 3-30. Edge Components WA855 / VA8551.0
Notes:
Edge Components are included the Network Deployment package. The Edge Components
include a load balancer and a caching proxy. The load balancer distributes incoming client
requests across servers, balancing workload and providing high availability by routing
around unavailable servers. The caching proxy can satisfy subsequent requests for the
same content by delivering it directly from the local cache, which is much quicker than
retrieving it again from the content host. Cacheable content includes static web pages and
JSP files with dynamically generated but infrequently changed fragments.
V8.1
Student Notebook
Uempty
Intelligent Management
Health Application Performance

management edition management
management
Self protecting Self optimizing
Self healing Self managing
App App
version version
1.0 2.0
Intelligent routing
Figure 3-31. Intelligent Management WA855 / VA8551.0
Notes:
Intelligent Management provides a virtualized infrastructure that redefines the traditional
concepts of Java Platform, Enterprise Edition (Java EE) resources and applications and
their relationships with one another. This application infrastructure virtualization facilitates
the ability of the product to automate operations in an optimal manner, increasing the
quality of service. By introducing an automated operating environment with workload
management, you can reduce total cost of ownership by using less hardware to do more
work.
Student Notebook
Unit summary
• Describe Network Deployment concepts and terminology, such as cell,
node, node agent, and deployment manager
Server
Notes:
V8.1
Student Notebook
Uempty
1. A process that handles communications with the resources within the
node is __________.
2. What is the process when the node agent checks for changes to the
master configuration?
3. What is a configuration that allows a host machine to resemble

multiple host machines?
4. What defines the runtime environment for either the deployment

manager or the application server?
Notes:
1. 
2. 
3. 
4.
Student Notebook
Checkpoint answers
1. A process that handles communications with the resources within the
node is the __________.
Node agent
2. What is the process when the node agent checks for changes to the
master configuration?
3. What is a configuration that allows a host machine to resemble

multiple host machines?
Virtual host
4. What defines the runtime environment for either the deployment

manager or the application server?
Profiles
Notes:
V8.1
Student Notebook
Uempty Unit 4. IBM Installation Manager

This unit describes the IBM Installation Manager.

• Define the IBM Installation Manager
• Describe the IBM Installation Manager wizards
• Describe the IBM Packaging Utility
• Uninstall the IBM Installation Manager

• Checkpoint
• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 4. IBM Installation Manager 4-1

Student Notebook
Unit objectives
Notes:
V8.1
Student Notebook
Uempty
Topics
• IBM Installation Manager overview
• IBM Installation Manager installation
• IBM Installation Manager – modify
• IBM Installation Manager – update
• IBM Packaging Utility
• Uninstall IBM Installation Manager
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 4.1. IBM Installation Manager overview

Student Notebook
IBM Installation Manager

overview

Figure 4-3. IBM Installation Manager overview WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM Installation Manager (1 of 3)

• IBM Installation Manager is the Eclipse-based tool to manage the
installation, update, modification, rollback, and uninstallation of product
packages
• Includes a number of wizards that make it easy to maintain packages

throughout their lifecycles:
– Installation wizard: walks you through the installation
– Update wizard: searches for updates to packages installed
– Modify wizard: modifies certain elements of a package
– Roll back wizard: allows you to revert to a previous version of a package
– Uninstall wizard: removes a package
– Manage licenses wizard: allows you to manage and configure various licenses
• Can be installed interactively or silently
Figure 4-4. IBM Installation Manager (1 of 3) WA855 / VA8551.0
Notes:
WebSphere Application Server Version 8.5 uses the IBM Installation Manager for the
installation process. The installation experience is now unified across all of the WebSphere
platforms. Also, various IBM products use the same IBM Installation Manager installer.
The IBM Installation Manager full product installation lifecycle management includes
product installation, adding or removing features, uninstallation, and full service
management, which includes installing and uninstalling fixes and applying and rolling back
service fix packs.

Student Notebook

• Install binary files relevant to user selections and system environment
• GUI and response file modes of operation

– GUI to complete individual operations
– Response files can be recorded from the GUI or created by specifying the
appropriate xml
– Silent mode support for starting multiple operations
• Single user experience across WebSphere, WebSphere components,

and various IBM products
– A single instance of IBM Installation Manager can manage the product lifecycle
for any Installation Manager-based products, from WebSphere, Rational, and
others
– Support for WebSphere, IBM HTTP Server, WebSphere Customization Toolbox,
and others
Notes:
IBM Installation Manager provides full graphical user interface for distributed platforms,
excluding z/OS and IBM i operation systems, but it provides a command-line interface for
all platforms. Using the Installation Manager command-line utility (IMCL) and the response
files, you can install products silently.
V8.1
Student Notebook
Uempty
Notes:
Installation Manager can be configured to automatically search for updates to itself. To
verify or modify this setting, click File > Preferences > Updates in the Installation Manager
GUI. If this option is selected, network connectivity is required so Installation Manager can
look for any updates. If it finds an update, you are provided details on a possible action. If
the updating option is cleared, Installation Manager does not look for updates to itself.

Student Notebook
IBM Installation Manager history

• IBM Installation Manager product was originally introduced to support
the installation of IBM Rational desktop products
• Currently multiple products across IBM use Installation Manager

– A single instance of IBM Installation Manager can manage the product
lifecycle for any IBM Installation Manager based product from WebSphere,
Rational, Lotus, or any other brand within IBM
• IBM Installation Manager supports

– Full graphical user interface (GUI)
– Command-line (IMCL) mode and response file
• IBM Installation Manager can install the product directly from:

– Product (DVD) media
– IBM Passport Advantage website
– Customer internal enterprise intranet
Figure 4-7. IBM Installation Manager history WA855 / VA8551.0
Notes:
IBM Installation Manager was originally introduced to support the installation of IBM
Rational desktop products, and many products across IBM use this tool. A single instance
of IBM Installation Manager can manage the product lifecycle for any IBM Installation
Manager based product from WebSphere, Rational, Lotus, and any other brand within IBM.
The IBM Installation Manager full product installation lifecycle management includes
product installation, adding or removing features, uninstallation, and full service
management, which includes installing and uninstalling fixes and applying and rolling back
the service fix pack.
Every product is packaged and delivered differently. You can download installation files for
a product, or you can obtain product discs that contain installation files. When you insert a
disc into a local computer, the IBM Installation Manager starts automatically. If you are not
using a disc on a local computer, you must start the installation process yourself. Extract
the downloaded files or copy the disc files to a common location, and then you can
determine the files to use to start the installation.
V8.1
Student Notebook
Uempty
IBM Installation Manager basics

• The IBM Installation Manager can be used to interactively install or
update packages
– Set repository preferences to indicate where to get the data for installing or
updating packages
– Default repository preferences is a service repository which requires Internet
connectivity
– Can modify repository preference to use local repository
• Starting the IBM Installation Manager:
– Can be started by using the Start/Computer menu
– Can be started by using the IBMIM command
– In <install_root>/IBM/InstallationManager/eclipse
• More information about the IBM Installation Manager can be found by
using the information center
– http://publib.boulder.ibm.com/infocenter/install/v1r5/
index.jsp
Figure 4-8. IBM Installation Manager basics WA855 / VA8551.0
Notes:
IBM Installation Manager is a tool that you can use to install and maintain your software
packages. Wizards guide you through the steps that you must take to install, modify,
update, roll back, or uninstall your IBM products. Use Installation Manager to install
individual software packages on your local machine, or with the IBM Packaging Utility to
install software for an enterprise.

Student Notebook
Installation Manager command line

• When you cannot use the IBM Installation Manager user interface, you
can use IBM Installation Manager command line to manage
installations
– In <IM_install_root>/tools/imcl
• Use imcl commands with either the installed version of Installation

Manager or the Installation Manager installer
• From the command line, you can:

– Manage installations
– View repository contents, available packages, fixes, and others
– Run installation scripts that include commands and options for specifying the
details of your installation
• Run the help command to view the available commands for Installation
Manager
– For example, <IM_install_root>/tools/imcl -help
Figure 4-9. Installation Manager command line WA855 / VA8551.0
Notes:
You must run imcl commands from the tools directory. You cannot use imcl from the
Installation Manager installer if an earlier version of Installation Manager is installed.
Include quotation marks around file paths that have spaces.
V8.1
Student Notebook
Uempty
IBM Installation Manager repository (1 of 3)

• Contains one or multiple product offerings that have both metadata
and actual payload for the offerings
• Metadata describes such aspects of the offering as:

– Name, version, supported platforms, and other items
– Components of the offering (optional and required feature)
– Relationships between offerings and features of the offerings
• Repository normally contains full content that is required to install

certain offering of various platforms, operating systems, and others
• Different IBM Installation Managers, on different workstations, can

reference the same repository
Figure 4-10. IBM Installation Manager repository (1 of 3) WA855 / VA8551.0
Notes:
A repository is a location that stores data for installing, modifying, rolling back, updating, or
uninstalling packages. You can add, edit, or remove repositories and modify the repository
order in the repository table. The IBM Installation Manager repository contains one or
multiple product offerings that have both metadata and actual payload for the offerings. The
offering metadata describes such aspects of the offering as: name, version, supported
operating systems, required and optional features, and relationships and dependencies
between offerings and features of offerings.
Normally, an IBM Installation Manager repository contains the full content that is required to
install on various platforms or operating systems. Remote repositories are available for
installation through the web, or product images and fixes can be stored in local repositories
and customized.

Student Notebook

• Repository topologies can be generalized in the following three
categories
– Public IBM hosted repository (accessible to general public using URL)
– Enterprise hosted repository (located behind the firewall that multiple
computers within the enterprise access)
– Local Installation Manager repository (single user accesses repository, not
shared with others)
• Tools are provided to copy offerings from one repository to another

– IBM Package Utility or file transfer tools
Notes:
Different IBM Installation Managers can reference repositories on different machines, and
the repository topologies can be generalized in three categories:
• Public repository, which can be publicly accessible by using a URL with an internal
connect or local share file system
• Enterprise repository, which is usually behind the firewall and accessed by multiple
machines only within the enterprise intranet
• Local repository, which a single user uses and does not share with others
There are tools available to copy offerings from one repository to another, such as the IBM
Package Utility. If you are using a third-party tool to transfer the repository between
machines, you must use binary transfer mode.
V8.1
Student Notebook
Uempty
Notes:
In the Repositories window, you can add, edit, or remove repositories and modify the
repository order in the repository table. You can clear credentials for a repository or test a
connection to a repository. You might find both a diskTag.inf and a repository.config
in the IBM product installation files. Use the diskTag.inf file when selecting a repository
location.

Student Notebook
Remote installations
• IBM Installation Manager – manages installation on local system and
can:
– Access remote installation repositories
– Update the current installation
• Job manager – sends batch style tasks to remote systems to run

– Can communicate with deployment managers or admin agents
• Centralized installation manager (CIM) - can remotely run installations
Figure 4-13. Remote installations WA855 / VA8551.0
Notes:
In a flexible management environment, you can submit the Install IBM Installation
Manager job to install the Installation Manager on registered hosts of the job manager. You
can use the administrative console of the job manager or the deployment manager to
submit the job.
Use the centralized installation manager (CIM) to shorten the number of steps that are
required to create and manage environments that contain previous versions of WebSphere
Application Server. As an administrator, you can remotely install or uninstall product
components and apply maintenance from the administrative console.
V8.1
Student Notebook
Uempty 4.2. IBM Installation Manager installation

Student Notebook
IBM Installation Manager

installation

Figure 4-14. IBM Installation Manager installation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Installing the IBM Installation Manager

• For computers that do not have internet access, you must download
the installer package on a computer that has internet access
– Download the installer package, agent.installer.platform.zip, for a specific
platform
– Copy the compressed file to the computer where you are installing the
Installation Manager
• Multiple installation options

– IBM Installation Manager user interface (GUI installation)
– Silently
• Starting the IBM Installation Manager user interface

– Windows: install.exe
– UNIX: ./install
Figure 4-15. Installing the IBM Installation Manager WA855 / VA8551.0
Notes:
Installation Manager comes in the form of an installation kit, which is an archive file that
contains a set of Installation Manager binary files and a flat-file repository for the
Installation Manager product. The installation kit is used only for setup and maintenance of
Installation Manager. You run Installation Manager only on systems on which you install or
update product code. Typically, you need only one Installation Manager instance on a
computer because one instance can track any number of product installations.

Student Notebook
Install IBM Installation Manager (1 of 6)
Figure 4-16. Install IBM Installation Manager (1 of 6) WA855 / VA8551.0
Notes:
The product DVD media includes a launchpad program, which can be used to install IBM
Installation Manager Version 1.5.2, IBM WebSphere Application Server Version 8.5, and
other software products. After IBM Installation Manager is installed, it can be used to install
IBM WebSphere.
With Application Server Network Deployment, you can add or remove more optional
features of the IBM WebSphere Application Server Network Deployment installation, or
uninstall the product.
Start the launchpad from the product DVD media, and you see that the launchpad GUI
comes up. Click the link to start Installation Manager installation for administrators.
V8.1
Student Notebook
Uempty
Notes:
The IBM Installation Manager installation wizard pops up. Follow the wizard instructions
and click Next to continue.
You cannot install multiple versions of Installation Manager on the same physical machine
in the same mode. If you try to install more instances of Installation Manager on the same
physical machine, it returns an error that indicates that it is already installed.

Student Notebook
Notes:
Read and accept the license agreement to proceed with the installation.
V8.1
Student Notebook
Uempty
Notes:
Choose the default installation location or keep the default directory.

Student Notebook
Notes:
After reviewing the installation summary panel, click Install to continue with the installation.
V8.1
Student Notebook
Uempty
Notes:
After the installation is completed, click Restart Installation Manager to exit the
installation wizard and restart the IBM installed Installation Manager.

Student Notebook
Install IBM Installation Manager silently

• Silently installing IBM Installation Manager methods
– Open a command prompt to the directory where you extracted the compressed
file
– Windows: installc.exe -acceptLicense
– UNIX: ./installc -acceptLicense
Figure 4-22. Install IBM Installation Manager silently WA855 / VA8551.0
Notes:
Silent mode allows you to install packages in a non-interactive and non-GUI mode. It uses
a response file to provide the input for each installation. The key to silent mode
installations, then, is the creation of the response files that guide each effort. Response
files can be used to install, update, modify, roll back, and uninstall software packages.
V8.1
Student Notebook
Uempty 4.3. IBM Installation Manager: Modify

Student Notebook
IBM Installation Manager:

Modify

Figure 4-23. IBM Installation Manager: Modify WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Modify (add or remove)
Figure 4-24. Modify (add or remove) WA855 / VA8551.0
Notes:
Start IBM Installation Manager on your system and click the Modify icon from the IBM
Installation Manager welcome panel to modify the installation.

Student Notebook
Modify (add or remove) features (1 of 5)
Figure 4-25. Modify (add or remove) features (1 of 5) WA855 / VA8551.0
Notes:
Select the package group that you would like to modify, and click Next to proceed.
You have more than one choice if you have multiple installations of WebSphere Application
Server. Each package group corresponds to an installation location.
V8.1
Student Notebook
Uempty
Notes:
Select a new optional language that you want to install, or clear the already installed
optional language to uninstall. Click Next to proceed.

Student Notebook
Notes:
Select or clear the optional features that you want to install or uninstall. Click Next to
proceed.
V8.1
Student Notebook
Uempty
Notes:
Review the Modify summary panel. Click Modify to start the add or remove feature
operation.

Student Notebook
Notes:
When the modification completes, there are final installation status details on the final
panel. You can also click the View Log File link to review the log.
V8.1
Student Notebook
Uempty 4.4. IBM Installation Manager: Update

Student Notebook
IBM Installation Manager:

Update

Figure 4-30. IBM Installation Manager: Update WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Update
Figure 4-31. Update WA855 / VA8551.0
Notes:
Start IBM Installation Manager on your system and click the Update icon from the IBM
Installation Manager welcome panel to update the installation.

Student Notebook
Updating the software silently

• Can silently update packages that are installed by using the IBM
– On Windows, enter the command:
<IM_install_root>\tools\ibmcl –launcher.ini silent-
install.ini –updateAll –log <log_path_and_name>
– On UNIX, enter the command:
<IM_install_root>/tools/ibmcl –launcher.ini silent-
install.ini –updateAll –log <log_path_and_name>
• Requires Internet connectivity
– Modify repository preferences point to a local repository
• Cannot use the IBM Installation Manager to install updates on the
underlying WebSphere Application Server Network Deployment
installation
– Must install updates by using the IBM Update Assistant and then reimport the
installation into the IBM Installation Manager
– Only required for fix pack updates, not interim fixes
Figure 4-32. Updating the software silently WA855 / VA8551.0
Notes:
Before you can update a package, Installation Manager must have access to the repository
that contains the package updates. Internet access might be required.
Each installed package has an embedded location for its default update repository. For
Installation Manager to search the default repository locations for the installed packages,
the preference Search service repositories during installation and updates must be
selected.
If you use another installer besides Installation Manager to update a package, Installation
Manager might not be able to recognize the change. You might be required to uninstall the
update from the other installer to be able to use Installation Manager to update later.
V8.1
Student Notebook
Uempty 4.5. IBM Packaging Utility

Student Notebook
IBM Packaging Utility

Figure 4-33. IBM Packaging Utility WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM Packaging Utility (1 of 2)

• A packaging tool that creates and manages software repository content
in the correct format for IBM Installation Manager
– WebSphere Application Server V8.5.5 depends on the IBM Packaging Utility
1.6.2
• Allow you to manage repository content by using CD images, PPA

compressed files, IBM hosted repositories, and custom repositories
• The packaging utility can:

– Create a repository
– Copy multiples packages into a single repository
– Copy multiple versions of a product to a repository
– Copy packages from Passport Advantage to a local repository
– Delete packages
– Add fixes to a repository
Figure 4-34. IBM Packaging Utility (1 of 2) WA855 / VA8551.0
Notes:
You can use the IBM Packaging Utility to create custom or “enterprise” IBM Installation
Manager repositories that contain multiple products and maintenance levels that fit the
needs of your business. As an administrator, you can control the content of your enterprise
repository, which then can serve as the central repository to which your organization
connects for product installations and updates. IBM Packaging Utility essentially copies
from a set of source IBM Installation Manager repositories to a target repository and
eliminates duplicate artifacts, helping to keep the repository size as small as possible.

Student Notebook
IBM Packaging Utility (2 of 2)

• After installation of the IBM Packaging Utility, it includes
– A GUI interface
– The PUCL command-line interface
• Includes the –platform option that can copy repository files for
specific platform.
– Saves disk space and network bandwidth by copying only the files you need
– Example: -platform os=os,arch=arch
• Example: create a repository for installation on Linux

– PUCL.exe copy com.ibm.Websphere.ND.v80_8.5.0.20120222_0247
–repositories http://ibm.com/repository/package -target
"/IBM/IBMPackages/" -platform os=linux,arch=ppc -
acceptLicense
Figure 4-35. IBM Packaging Utility (2 of 2) WA855 / VA8551.0
Notes:
If Installation Manager is installed, you can use the Packaging Utility repository on
www.ibm.com to install or update Packaging Utility without downloading files. If Installation
Manager is not installed, you must download the Packaging Utility files. Installation
Manager is included in the Packaging Utility download packages.
V8.1
Student Notebook
Uempty
Technical preview
• IBM Packaging Utility V1.6.2 includes the –updateFromVersion
technical preview
– Creates a repository that contains the files for updating from the specified
version to another version
– Copies only the files that are required to update to a later version
– Only available for the PUCL command-line interface
– Works only with packages and does not work with fixes
• Example for a repository update on Linux

– PUCL.exe copy com.ibm.package.1.2 –updateFromVersion 1.1 –
repositories http://ibm.com/repository/package -target
"/IBM/IBMPackages/"
• For complete details, visit: http://www.ibm.com/support/

docview.wss?uid=swg27023960
Figure 4-36. Technical preview WA855 / VA8551.0
Notes:
Use the -updateFromVersion option to copy only the files that are required to update to a
later version. The version value is the version of the package that you are updating from.
The package that you are copying is the version that you are updating to. An update might
require files from a base offering. Use the -repositories option to list the repository for
the base offering.

Student Notebook
V8.1
Student Notebook
Uempty 4.6. Uninstall IBM Installation Manager

Student Notebook
Uninstall IBM Installation

Manager

Figure 4-37. Uninstall IBM Installation Manager WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Uninstalling the IBM Installation Manager

• Before you uninstall IBM Installation Manager, you must uninstall all
the packages that the IBM Installation Manager installed
– Close Installation Manager before starting the uninstall process
• To uninstall IBM Installation Manager:

– On Windows, use Control Panel > Add or Remove Programs
– On UNIX, use the uninstall IBM Installation Manager icon
– By using the /var/ibm/InstallationManager/uninstall/uninstall
command
Figure 4-38. Uninstalling the IBM Installation Manager WA855 / VA8551.0
Notes:
To uninstall the Installation Manager, you must log on to your workstation with a user
account that has the same privileges as the user account used to install Installation
Manager.

Student Notebook
Unit summary
Notes:
V8.1
Student Notebook
Uempty
1. (True or False) You can have multiple versions of the IBM Installation
Manager installed on a workstation.
2. (True or False) To uninstall the IBM Installation Manager, you must

uninstall all packages that the Installation Manager installed.
3. (True or False) The IBM Packaging Utility allows you to create a

repository and copy multiple packages into a single repository.
However, you cannot copy multiple versions of a product into a
repository.
Notes:
1. 
2. 
3. 

Student Notebook
Checkpoint answers
1. False: You can have only one version of the IBM Installation
Manager installed on a workstation.
2. True. To uninstall the IBM Installation Manager, you must uninstall all
packages that the Installation Manager installed.
3. False. The IBM Packaging Utility allows you to create a repository,

copy multiple packages into a single repository, and copy multiple
versions of a product into a repository.
Notes:
V8.1
Student Notebook
Uempty Unit 5. WebSphere Application Server installation

This unit describes the tasks that are involved with the planning,
installation, and post-installation of WebSphere Application Server.

• Describe the installation process for WebSphere Application Server
• Verify the installation of WebSphere Application Server
• Describe WebSphere profiles
• Describe the directories and configuration files for WebSphere
Application Server
• Describe how to use configuration commands
• Describe how to use backup and restore configuration utilities

• Checkpoint
• Lab exercises
References
http://publib.boulder.ibm.com/infocenter/wasinfo/v8r5/ 
index.jsp
© Copyright IBM Corp. 2013 Unit 5. WebSphere Application Server installation 5-1
Student Notebook
Unit objectives
Application Server
Notes:
V8.1
Student Notebook
Uempty
Topics
• Installation overview
• Hardware and software requirements
• Installing WebSphere Application Server
• Working with profiles
• Verifying an installation
• Post installation tasks
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 5.1. Installation overview
Student Notebook
Installation overview

Figure 5-3. Installation overview WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Preinstallation tasks
Read the documentation Installation media

WebSphere Information Center DVD media
platform-specific tips for Downloaded repository
installing and migrating Passport Advantage
Install readme file
Confirm hardware and software TCP/IP networking

Obtain necessary products Host name of node is not to
and maintenance be in DNS or local hosts file
Check WebSphere website Host name of node is not to
for any maintenance remain fixed
DHCP not supported
User ID File system and memory

Create and verify user ID for Enough space is available
starting services Enough memory is available
Verify user ID for disk
read and write access
Figure 5-4. Preinstallation tasks WA855 / VA8551.0
Notes:
Before beginning the installation of WebSphere Application Server, read the documentation
that is included with the product. Also, review the WebSphere Information Center for tips on
planning the installation process.
Confirm that you meet the hardware and software requirements. Application requirements
dictate more hardware and software needs.
Create and verify that the user ID that is used to install the product has the appropriate
rights for starting services. Ensure that the user ID has read and write access to the file
system where the product is installed. A non-administrator ID can be used to install
WebSphere. Review the information center topic that is titled “Describing installation by
using non-administrator ID”.
Locate the installation media. The installation files are delivered as a DVD or can be
downloaded by using a Passport Advantage ID.
Student Notebook
WebSphere opens up several ports by default. Ensure that the host name assigned to your
system is in DNS or in the local host’s files. The host name must remain fixed after you
create a profile. Changing the host name can cause WebSphere not to function properly.
Finally, ensure that you have enough disk space and physical memory on the system to
support your application server environment. The applications that you plan to install
contribute to the amount of disk space and physical memory needed.
V8.1
Student Notebook
Uempty
Installation overview
Deployment manager
+ WebSphere
IBM profile 1 Application server
Installation
1 Manager
Custom profile
+ WebSphere Admin agent

profile 2
Job manager
WebSphere
installation
product
binary files Cell
+ WebSphere
profile 3
Secure proxy
2 3
Figure 5-5. Installation overview WA855 / VA8551.0
Notes:
Student Notebook
Installing WebSphere Application Server

• Installation options:
– Use the launchpad
– Use the Installation Manager GUI (without the launchpad)
– Use a response file install_response_file.xml to install silently
• IBM Installation Manager GUI flow:

– Install IBM Installation Manager
– Install IBM WebSphere Application Server Network Deployment
– Modify (add or remove) optional features
– Uninstall IBM WebSphere Application Server Network Deployment
Figure 5-6. Installing WebSphere Application Server WA855 / VA8551.0
Notes:
The product DVD media includes a launchpad utility, which can be used to install IBM
Installation Manager Version 1.6.2 and IBM WebSphere Application Server Version 8.5.5.
After IBM Installation Manager is installed, it can be used to:
• Install IBM WebSphere Application Server Network Deployment
• Add or remove optional features to the IBM WebSphere Application Server Network
Deployment installation
• Uninstall the installation
V8.1
Student Notebook
Uempty
IBM WebSphere Application Server product packages

• IBM WebSphere Application Server V8.5.5 has multiple product
offering packages
– Including Network Deployment, Base, Express, and HTTP Server
• These product packages are packaged in the product DVD media and
also available in IBM Passport Advantage site
• IBM Installation Manager V1.6.2 or later is required to install IBM

WebSphere Application Server V8.5.5
• Same product offering package can be used to install on any

supported distributed platforms
Figure 5-7. IBM WebSphere Application Server product packages WA855 / VA8551.0
Notes:
The IBM WebSphere Application Server Version 8.5.5 product contains multiple offering
packages. For example, Application Server Network Deployment, Base, Express, or the
IBM HTTP Server is a separate offering.
These offering packages are also available for download and to be installed directly from
the IBM Passport Advantage site. Users must have a valid Passport Advantage user ID
and password with entitlement to IBM WebSphere Application Server Version 8.5.5.
All IBM WebSphere Application Server offerings must be installed by using IBM Installation
Manager Version 1.6.2 or later.
Unlike previous versions of WebSphere Application Server, each offering contains
complete program binary files and can be installed on any supported distributed platforms.
There are not separate 32-bit and 64-bit Application Server installable packages.
Student Notebook
V8.1
Student Notebook
Uempty 5.2. Hardware and software requirements
Student Notebook
Hardware and software

requirements

Figure 5-8. Hardware and software requirements WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Hardware requirements
• Requirements vary by platform and your intended workload
• For the latest requirements, check:

– http://www-01.ibm.com/support/docview.wss?uid=swg27038218
Figure 5-9. Hardware requirements WA855 / VA8551.0
Notes:
Hardware requirements vary by platform and application requirements. Use this link to
check for the latest hardware requirements. Also, consult your application documentation
to help determine your hardware requirements.
Student Notebook
Software requirements: Operating systems

• Supported operating systems include:
– Windows
– AIX
– Sun Solaris
– HP-UX
– Linux/Intel, Linux/PowerPC, Linux for zSeries
– RHEL, RHEL Server, SUSE Linux Enterprise Server
– IBM i
– IBM z/OS
Figure 5-10. Software requirements: Operating systems WA855 / VA8551.0
Notes:
This list contains the supported operating systems. Software requirements vary by platform
and application requirements. To check for the latest supported operating system versions
and patch levels, see: http://www.ibm.com/support/docview.wss?uid=swg27038218
Also, consult your application documentation to help determine your software
requirements.
V8.1
Student Notebook
Uempty
Software requirements: Web servers and database servers

• Supported web servers include:
– Apache
– IBM HTTP Server
– Internet information services
– Sun Java System web server
– Lotus Domino
• Supported database servers include:

– IBM DB2
– Apache Derby
– Oracle
– Sybase
– Microsoft SQL
– Informix
– IMS
Figure 5-11. Software requirements: Web servers and database servers WA855 / VA8551.0
Notes:
The first list contains the supported web servers. To check for the latest supported web
server versions and patch levels, see:
http://www.ibm.com/support/docview.wss?uid=swg27038218
Also, consult your application documentation to help determine your web server
requirements.
The second list contains the supported database servers. Use the same link to check for
the latest supported database server versions and patch levels. Also, consult your
application documentation to help determine your database server requirements.
Student Notebook
V8.1
Student Notebook
Uempty 5.3. Installing WebSphere Application Server
Student Notebook
Installing WebSphere
Application Server

Figure 5-12. Installing WebSphere Application Server WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM Installation Manager terminology

• Package
– Software product that Installation Manager can install
– com.ibm.websphere.ND.v85_8.5.5.20130514_1044
package name package version
• Package group
• Repository
– Local directory or remote server location for package files
• Shared resources
– Files and plug-ins that packages share
Figure 5-13. IBM Installation Manager terminology WA855 / VA8551.0
Notes:
A package is a software product that Installation Manager can install. It is a separately
installable unit that can operate independently from other packages of that software. It can
be a product, a group of components, or a single component that can be installed by using
Installation Manager. Each package has a name, version, and identifier, as shown in this
example:
• Package name: com.ibm.websphere.ND.v85
• Package version: 8.5.5.20130514_1044
• Package identifier: com.ibm.websphere.ND.v85_8.5.5.20130514_1044
The packages are installed to a defined directory location in the file system. Installation
Manager allows you to control where products are installed and at which level.
A package group is used when more than one product is installed at the same location.
Installation Manager automatically sets package group names. Some packages support
installing to the same package group, and other packages must be installed to a new
package group.
Student Notebook
A repository is a place where the installable packages can be found. The repository
includes metadata that describes the software version and how to install it. It has a list of
files that are organized in a tree structure and can be stored on a local directory or on a
remotely reachable server.
Shared resources provide a place where software files and plug-ins are stored and where
packages share them. You can specify the shared resources directory only the first time
you install a package, and you cannot change the location while packages are installed.
V8.1
Student Notebook
Uempty
Repositories
• Add the
repository that
1 contains the
installation
packages
Figure 5-14. Repositories WA855 / VA8551.0
Notes:
You must configure the repository that contains the WebSphere Application Server
installation packages.
Student Notebook
Installation GUI
Figure 5-15. Installation GUI WA855 / VA8551.0
Notes:
Click Install to start the installation process.
V8.1
Student Notebook
Uempty
Packages
Figure 5-16. Packages WA855 / VA8551.0
Notes:
Select the installation package for WebSphere Application Server Network Deployment.
Student Notebook
Shared resources directory
Figure 5-17. Shared resources directory WA855 / VA8551.0
Notes:
Select the location for the shared resources directory. As soon as it is set, the directory
location cannot be modified.
V8.1
Student Notebook
Uempty
Package group and installation directory
Figure 5-18. Package group and installation directory WA855 / VA8551.0
Notes:
Determine the package group and installation directory. The package group is a location
that contains one or more packages. The installation directory is the location for the
installation binary files.
Student Notebook
Features: Translations
Figure 5-19. Features: Translations WA855 / VA8551.0
Notes:
In version 8.5.5, you can select individual language packs for the WebSphere Application
Server runtime environment and administrative console. You can confirm the features to
install.
V8.1
Student Notebook
Uempty
Features: Install packages
Figure 5-20. Features: Install packages WA855 / VA8551.0
Notes:
In version 8.5.5, you can select individual features to install. Other features that you can
install include sample applications.
Student Notebook
Summary
Figure 5-21. Summary WA855 / VA8551.0
Notes:
An installation summary panel is displayed. Review the installation location, installation
features, and the language pack option before clicking Install to start the installation.
During the installation, a progress status bar is displayed. You can pause or cancel the
installation.
V8.1
Student Notebook
Uempty
Results
Figure 5-22. Results WA855 / VA8551.0
Notes:
This image is the final panel of the installation flow. An installation status is displayed on the
top of the panel. You can also click the View Log File link to review the detailed installation
logs.
In version 8.5.5, product installation is separated from product configuration. The
installation of WebSphere Application Server does not automatically create a server profile
instance. However, a tool integration option is available at the final panel of the installation
wizard to start the Profile Management Tool application upon closing of this final installation
wizard panel.
Student Notebook
Install WebSphere Application Server silently

• IBM Installation Manager also provides a command-line interface
– Can be used for basic installation, modify, update, and uninstall operations
• IBM Installation Manager is able to record an installation response

file
– Example: <IM_install>\IBMIM.exe C:\temp\imRegistry
–record C:\temp\install_response_file.xml
• The installation operations can be rerun with the command-line

interface and the installation response file
– Example: <IM_install>\IBMIM.exe –launcher.ini
silent-install.ini –input
C:\temp\install_response_file.xml –log
C:\temp\install_log.xml
Figure 5-23. Install WebSphere Application Server silently WA855 / VA8551.0
Notes:
IBM Installation Manager also provides a command-line interface, which can be used for
installation automation, and it is useful when installing WebSphere Application Server in
many machines within the customer’s (your) enterprise. You can use the command-line
interface alone to do basic installation, modify, update, and uninstall operations, or you can
use it with an installation response file to rerun the same installation operations. IBM
Installation Manager also can record the operation to an installation response file in its GUI
mode, or you can use the sample response file that is provided in the WebSphere
Application Server Information Center. There are instructions in the sample response file to
guide you in changing it for your environment.
In the IBM WebSphere Application Server Version 8.5 Information Center, you can find
sample response files that contain complete documentation on how to modify the sample
response file to suit your particular installation environment. An example is a different
installation location or a choice of optional features.
When you record a new response file, you can specify the -skipInstall parameter.
Using this parameter has the following benefits:
V8.1
Student Notebook
Uempty • No files are installed, which speeds up the recording.

• If you use a temporary data location with the -skipInstall parameter, Installation
Manager writes the installation registry to the specified data location while recording.
When you start Installation Manager again without the -skipInstall parameter, you
then can use your response file to install against the real installation registry. The
-skipInstall operation is not expected to be used on the actual agent data location
that Installation Manager uses. It is unsupported. Use a clean, writable location, and
reuse that location for future recording sessions.
Student Notebook
V8.1
Student Notebook
Uempty 5.4. Working with profiles
Student Notebook
Working with profiles

Figure 5-24. Working with profiles WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Profiles
• Profiles define application server configuration
Profile types packages Functions
Application server Runs your enterprise applications; functions

All
(default) independently from other application servers
Provides management capabilities for multiple

Deployment manager Network Deployment
federated nodes
Job manager Network Deployment stand-alone application servers, administrative
agents, and deployment managers
Administrative agent All
stand-alone application servers
Creates and federates a node that contains no

Custom (managed) Network Deployment
predefined application server definitions
Provides two profiles: a deployment manager and a

Cell Network Deployment
federated application server profile
Provides a secure proxy configuration-only profile

Secure proxy Network Deployment
only for use with a DMZ secure proxy server
Figure 5-25. Profiles WA855 / VA8551.0
Notes:
Profiles define application server configurations. WebSphere Application Server V8
Network Deployment has seven profile types, which are listed and described in the table.
Profiles contain the configuration files that WebSphere uses at run time and are
customizable. The Profile Management Tool, which is a graphical interface to the
manageprofiles script, is used to create profiles.
Student Notebook
Starting the Profile Management Tool

• Start the Profile Management Tool from the WebSphere
Customization Toolbox
– At <was_root>/bin/ProfileManagement/wct.sh
• Click Create
Figure 5-26. Starting the Profile Management Tool WA855 / VA8551.0
Notes:
To begin the process of creating and configuring a profile, start the Profile Management
Tool from the WebSphere Customization Toolbox. Click Create to start the process.
The Profile Management Tool is installed to WebSphere Customization Toolbox during
installation of WebSphere Application Server.
V8.1
Student Notebook
Uempty
Profile Management Tool: Environment and options

Environment selection
• A profile is associated with
an environment type
Application
deployment options
• Administration
console
• Default
application
Figure 5-27. Profile Management Tool: Environment and options WA855 / VA8551.0
Notes:
A number of different profiles can be created from this tool. In this example, the
environment for the profile is an application server. As part of the profile creation, both the
administrative console and the default application are deployed. It is best to deploy the
administrative console so there is an initial point to administer the application server. In a
development or test environment, you can install the default application. The default
application contains several servlets that provide information about the application server.
In a production environment, it is best to uninstall (or not install at all) the default
application. Installation of the default application is considered a security risk.
Student Notebook
Profile creation options
Figure 5-28. Profile creation options WA855 / VA8551.0
Notes:
To begin the process of creating and configuring a profile, start the Profile Management
Tool from the WebSphere Customization Toolbox. Click Create to start the process.
The Profile Management Tool is installed to WebSphere Customization Toolbox during
installation of WebSphere Application Server.
V8.1
Student Notebook
Uempty
Profile Management Tool: Name, location, and tuning
Figure 5-29. Profile Management Tool: Name, location, and tuning WA855 / VA8551.0
Notes:
The profile creation process provides a default name and location. You must change the
profile name and location according to the naming standards of your enterprise. The
example that is shown here is the profile name that is used in the lab exercises for this
course. The profile is created beneath the profiles directory of the application server
installation.
The runtime performance tuning standards are used to tune the environment appropriately.
There are settings for general-purpose usage (standard), optimal production usage (peak),
and development environments.
Student Notebook
Profile Management Tool: Node and host names
Figure 5-30. Profile Management Tool: Node and host names WA855 / VA8551.0
Notes:
The parameters on this panel identify the profile. Node name identifies the application
server profile in the administrative console. If the node is federated, the node name must
be unique within the cell. Server name is the logical name of the application server. The
host name is the DNS name.
V8.1
Student Notebook
Uempty
Profile Management Tool: Security
Figure 5-31. Profile Management Tool: Security WA855 / VA8551.0
Notes:
Creating a user name and password provides access to the administrative tools
(administrative console and wsadmin). This administrative user is created in a repository
within the application server. When the profile is created, you can add users, groups, or
external repositories.
Student Notebook
Profile Management Tool: Security certificate (1 of 2)
Figure 5-32. Profile Management Tool: Security certificate (1 of 2) WA855 / VA8551.0
Notes:
When you import a personal certificate as the default personal certificate, import the root
certificate that signed the personal certificate. Otherwise, the Profile Management Tool
adds the signer of the personal certificate to the trust.p12 file.
V8.1
Student Notebook
Uempty
Notes:
If you create the certificates, you can use the default values or modify them to create new
certificates. The default personal certificate is valid for one year by default, and the root
signing certificate signs it. The root signing certificate is a self-signed certificate that is valid
for 15 years by default. The default keystore password for the root signing certificate is
WebAS. You must change the password.
Student Notebook
Profile Management Tool: Ports
• Review port
value
assignments
Figure 5-34. Profile Management Tool: Ports WA855 / VA8551.0
Notes:
Verify that the port value assignments are correct and that there are no port conflicts.
V8.1
Student Notebook
Uempty
Profile Management Tool: Service Definition
Figure 5-35. Profile Management Tool: Service Definition WA855 / VA8551.0
Notes:
You can determine to run WebSphere Application Server as a Linux service.
Student Notebook
Profile Management Tool: Web server definition
Figure 5-36. Profile Management Tool: Web server definition WA855 / VA8551.0
Notes:
From this panel, you can create a web server definition that is used when a web server
routes requests to the application server. You can create that web server definition here or
when you generate the web server plug-in.
V8.1
Student Notebook
Uempty
Profile Management Tool: Summary
Profile creation
summary
y Summary
information is
based on the
selections
you made in
previous
panels
y Review the
summary for
accuracy
Figure 5-37. Profile Management Tool: Summary WA855 / VA8551.0
Notes:
This screen provides a summary of the options you chose for the profile creation. Review
the summary and click Next.
Student Notebook
Profile Management Tool: Results
Profile creation results

• Optionally start the First
steps console when
finished
• Each profile that you create
is displayed in the profile
list
Figure 5-38. Profile Management Tool: Results WA855 / VA8551.0
Notes:
You can optionally start the First steps console. The newly created profile is displayed in
the list of profiles.
V8.1
Student Notebook
Uempty
Profile creation with command-line tool

• The manageprofiles command-line tool allows you to create, list,
alter, or delete profiles
manageprofiles -<mode> -<argument> <argument parameter>
Figure 5-39. Profile creation with command-line tool WA855 / VA8551.0
Notes:
Use the manageprofiles command to create, delete, augment, back up, and restore
profiles, which define runtime environments. The manageprofiles command and its
graphical user interface, the Profile Management Tool, are the only ways to create runtime
environments. There are multiple parameters for this command. Consult the information
center for an explanation of each parameter.
Student Notebook
V8.1
Student Notebook
Uempty 5.5. Verifying an installation
Student Notebook
Verifying an installation

Figure 5-40. Verifying an installation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
First steps
First steps starts automatically

after profile creation
Figure 5-41. First steps WA855 / VA8551.0
Notes:
You can automatically start the First steps console after profile creation. Click the
Installation verification link to start the verification process.
Student Notebook
Installation verification
• When successful, the Installation Verification Tool starts the application

server and displays a successful completion message
Figure 5-42. Installation verification WA855 / VA8551.0
Notes:
The IVT tool starts the server process of a profile automatically if the server is not running.
After the server initializes, the IVT runs a series of verification tests. The tool displays pass
or fail status in a console window. The tool also logs results to the ivtClient.log file in
the logs directory for the profile. As the tool verifies your system, it reports any detectable
errors in the SystemOut.log file.
V8.1
Student Notebook
Uempty 5.6. Post installation tasks
Student Notebook
Post installation tasks

Figure 5-43. Post installation tasks WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Applications installed following installation

• System applications:
– isclite (administrative console)
– filetransfer
• Enterprise (Java EE) applications:

– Default application
– Installation verification test
– Query
– Samples (if selected)
• Samples gallery includes:

– PlantsByWebSphere
Figure 5-44. Applications installed following installation WA855 / VA8551.0
Notes:
Depending on the options you chose during installation and profile creation, several
applications can be installed.
System applications consist of isclite (administrative console) and the filetransfer
application. These applications are not listed in the administrative console, and you cannot
administer them.
Enterprise applications consist of the Default application and the Query application.
Sample applications consist of PlantsByWebSphere.
Student Notebook
Uninstall
Always use IBM Installation Manager to uninstall
• Do not use Add/Remove program to uninstall
WebSphere
Cannot custom
uninstall parts of
WebSphere
installation
• All the components are
removed
• Logs and properties
files are not removed
Silent uninstallation is
supported by
running IBM
as a background
process
Figure 5-45. Uninstall WA855 / VA8551.0
Notes:
In WebSphere Application Server V8, use the IBM Installation Manager to uninstall the
product. You cannot uninstall parts of the installation. All components are removed. Logs
and properties files are not removed.
The silent option can also be used to uninstall the product.
V8.1
Student Notebook
Uempty
Directory structure
Installable
applications
Plug-ins
Profile root
System
applications
Figure 5-46. Directory structure WA855 / VA8551.0
Notes:
This picture displays the directory structure after a profile is created. Take note of the
profiles directory. Beneath the profiles directory are the files and directories that
represent the runtime environment for the application server. This picture shows a single
profile, but there can be a deployment manager and other profiles in the profiles
directory.
Student Notebook
Configuration files
Figure 5-47. Configuration files WA855 / VA8551.0
Notes:
Beneath the config directory of the profile, you find configuration files that are specific to
the application server for the profile. Configuration files are typically well-formed XML files.
V8.1
Student Notebook
Uempty
Common command-line tools

• startServer starts a server
• stopServer stops a server
• serverStatus displays server status
• versionInfo displays installed product versions
Figure 5-48. Common command-line tools WA855 / VA8551.0
Notes:
The startServer command is used to start an instance of an application server. The
startServer command reads the configuration file for the specified server process and
starts that server process.
The stopServer command reads the configuration file for the specified server process.
This command sends a Java management extensions (JMX) command to the server that
tells it to shut down. The server process can be an application server, a DMZ secure proxy
server for IBM WebSphere Application Server, an administrative agent server, or a job
manager server. By default, the stopServer command does not return control to the
command line until the server completes the shutdown process. There is a -nowait option
to return immediately, and other options to control the behavior of the stopServer
command. For more information about where to run this command, see the “Using
command-line tools” topic.
The serverStatus command displays the status of one or all of the servers that are
configured on a node.
Student Notebook
The versionInfo tool displays important data about the product and its installed fix packs
and interim fixes, such as the build version and build date. This tool is useful when working
with support personnel to determine the cause of any problem.
V8.1
Student Notebook
Uempty
Server commands
• WebSphere commands are profile aware
– There is a -profileName option on many WebSphere V8 commands
<was_root>\bin\startServer server1 –profileName profile1
– Or issue the commands from the appropriate profile directory
<profile_root>\profile1\bin\startServer server1
• If no profile is specified, the default profile is assumed

– There can be only one default profile
• Examples:
– startServer server1 -profileName profile1
– startManager -profileName DmgrProfile
– stopServer server1 (assumes the default profile)
Figure 5-49. Server commands WA855 / VA8551.0
Notes:
WebSphere commands are profile aware. These commands can be issued from the bin
directory of the WebSphere Application Server root, or they can be issued from the bin
directory of the profile. If the command is issued from the WebSphere Application Server
root, then you must supply the profile name by using the -profileName option.
Student Notebook
Configuration backup and restore

• Backup configuration files: backupConfig <backup_file>.zip
• Restore configuration files: restoreConfig <backup_file>.zip
Figure 5-50. Configuration backup and restore WA855 / VA8551.0
Notes:
Commands for backing up and restoring a configuration are shown here. When you use the
backupConfig command, all servers on the node stop before the backup is made so that
partially synchronized information is not saved by default. For more information about
where to run this command, see command-line tools. If you do not have root authority, you
must specify a path for the backup file in a location where you have write permission. The
backup file is saved in compressed file format.
V8.1
Student Notebook
Uempty
Accessing the information center: Online

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r5/index.jsp
Figure 5-51. Accessing the information center: Online WA855 / VA8551.0
Notes:
Student Notebook
Accessing the information center: Offline options

• For offline solutions, the information center is available through
documentation plug-ins
• There are two solutions to configure and view information center

content offline:
– Install documentation plug-ins into an existing IBM User Interface Help System
– Provided as part of another IBM product (example: IBM Rational Application
Developer or IBM Assembly and Deploy Tool)
– Customize and export documentation plug-ins from the Toolkit for Custom and
Reusable Solution Information
Figure 5-52. Accessing the information center: Offline options WA855 / VA8551.0
Notes:
There are two solutions to configure and view the information center content offline.
Install the documentation plug-in into an existing IBM User Interface Help System that is
provided as part of another IBM product. The IBM Rational Application Developer and IBM
Assembly and Deploy Tool are two products where the plug-ins can be installed.
The other option is to customize and export documentation plug-ins from the Toolkit for
Custom and Reusable Solution Information.
V8.1
Student Notebook
Uempty
Unit summary
Application Server
Notes:
Student Notebook
1. What are the types of profiles that can be configured?
2. Which log file is used to verify that the installation was successful?
3. What is the Installation Verification Tool, and how can it be

accessed?
Notes:
1. 
2. 
3.
V8.1
Student Notebook
Uempty
Checkpoint answers
1. What are the types of profiles that can be configured?
– For the application server, an application server profile. For
Network Deployment, you can also configure deployment manager, custom,
and cell profiles.
2. Which log file is used to verify that the installation was successful?
– Examine the log file <was_root>\logs\install\log.txt
3. What is the Installation Verification Tool, and how can it be

accessed?
– The Installation Verification Tool scans log files to look for errors that might
occur during installation. It can be started from the command line or from the
First steps console of each profile.
Notes:
Student Notebook
V8.1
Student Notebook
Uempty Unit 6. Web server installation

In this unit, you learn the tasks that are involved in planning and
installing IBM HTTP Server and the plug-ins for WebSphere
Application Server.

• Explain the installation process for IBM HTTP Server
• Verify the installation of IBM HTTP Server
• Explain the installation process for WebSphere Customization
Toolbox
• Install web server plug-ins for WebSphere Application Server
• Use the Plug-in Configuration Tool to configure the web server
plug-in

• Checkpoint
• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 6. Web server installation 6-1

Student Notebook
Unit objectives
• Explain the installation process for WebSphere Customization Toolbox
• Use the Plug-in Configuration Tool to configure the web server plug-in
Notes:
V8.1
Student Notebook
Uempty
Topics
• Installing IBM HTTP Server
• WebSphere Customization Toolbox overview
• Installing web server plug-ins
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 6.1. Topic: Installing IBM HTTP Server

Student Notebook
Topic: Installing IBM HTTP

Server

Figure 6-3. Topic: Installing IBM HTTP Server WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Web servers for WebSphere Application Server

• Supported web servers include:
– Apache HTTP Server
– Lotus Domino Web Server
– IBM HTTP Server
– Microsoft Internet Information Services
– Sun Java System Web Server
• For the latest specifics on versions and patch levels, check:

– http://www-01.ibm.com/support/docview.wss?uid=swg27038218
Browser
traffic
Web server WebSphere

Application
Server
Figure 6-4. Web servers for WebSphere Application Server WA855 / VA8551.0
Notes:

Student Notebook
Web server plug-in installation

• Plug-in is a separate installation package
• Typical plug-in installation action
– Installs the plug-in binary files for the web server
– Updates the web server configuration file
Plug-in module
Web server
Web Server
configuration
file
Plug-in configuration
XML file
Figure 6-5. Web server plug-in installation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM HTTP Server: Installation

• IBM Installation Manager used for product installation
• Silent installation
– Uses a response file as an input
install –options "responsefile.txt" –silent
• Option to change the installation location

– Support for local and remote web server installations
• User ID and password with appropriate authority is required for

Windows platform
Figure 6-6. IBM HTTP Server: Installation WA855 / VA8551.0
Notes:

Student Notebook
IBM HTTP Server: Select package
Figure 6-7. IBM HTTP Server: Select package WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM HTTP Server: License agreement

y Read or print the license agreement
y Accept the license agreement
Figure 6-8. IBM HTTP Server: License agreement WA855 / VA8551.0
Notes:

Student Notebook
IBM HTTP Server: Installation directory and package group
y Create a package group

y Specify the directory location for the product installation
Figure 6-9. IBM HTTP Server: Installation directory and package group WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM HTTP Server: Features
Figure 6-10. IBM HTTP Server: Features WA855 / VA8551.0
Notes:

Student Notebook
IBM HTTP Server: Port values
y Verify the assigned port values
Figure 6-11. IBM HTTP Server: Port values WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
IBM HTTP Server: Summary
Figure 6-12. IBM HTTP Server: Summary WA855 / VA8551.0
Notes:

Student Notebook
IBM HTTP Server: Results
y Review the results

Figure 6-13. IBM HTTP Server: Results WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 6.2. Topic: WebSphere Customization Toolbox overview

Student Notebook
Topic: WebSphere
Customization Toolbox
overview

Figure 6-14. Topic: WebSphere Customization Toolbox overview WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere Customization Toolbox

• WebSphere Customization Toolbox includes tools for managing,
configuring, and migrating various parts of the WebSphere environment
– Plug-ins Configuration Tool (PCT) is available
– Other tools that existed earlier in previous versions are incorporated into the
WebSphere Customization Toolbox group of tools
• WebSphere Customization Toolbox comes in two offerings with varying

tool combinations based on the platform
– Embedded WebSphere Customization Toolbox is included as part of a
WebSphere Application Server installation
– Stand-alone WebSphere Customization Toolbox
Figure 6-15. WebSphere Customization Toolbox WA855 / VA8551.0
Notes:
WebSphere Customization Toolbox in essence is a container framework that holds various
tools that are used for configuring an WebSphere Application Server environment.
WebSphere Customization Toolbox comes as an independent stand-alone offering; it is
also embedded into WebSphere Application Server. Tools that get wrapped into the
WebSphere Customization Toolbox framework are different in the stand-alone and
embedded offerings.

Student Notebook
WebSphere Customization Toolbox: Offerings

• Embedded WebSphere Customization Toolbox
– Included with WebSphere Application Server installation
– Available on all architectures wherever WebSphere Application Server is
supported
– Contains Profile Management Tool (PMT) and Configuration Migration Tool
(CMT)
• Stand-alone WebSphere Customization Toolbox

– Distributed as a product offering
– A command-line version comes with it
– Operates as a 32-bit component on a 32-bit JDK in either a 32 or 64 operating
system
– Contains Web Server Plug-ins Configuration Tool (PCT), Remote Installation
for IBM i Tool, z/OS Profile Management Tool (zPMT), and z/OS Migration
Management Tool (zMMT)
Figure 6-16. WebSphere Customization Toolbox: Offerings WA855 / VA8551.0
Notes:
Embedded WebSphere Customization Toolbox comes as a part of WebSphere Application
Server. Therefore, it gets installed on all architectures wherever WebSphere Application
Server is supported. Added GUI support on AIX 64-bit is introduced in version 8. Platforms
include: HPUX 64 bit, Windows (32 and 64), Linux on x86 (32 and 64), Linux on Power PC
(32 and 64), Linux on IBM System z (32 and 64), Solaris, and AIX (32 and 64).
Stand-alone WebSphere Customization Toolbox is available on the following platforms:
HPUX 64-bit, Win2K (32 and 64), Linux on x86 (32 and 64), Linux on Power (32 and 64),
Linux on IBM System z (32 and 64), Solaris, and AIX (32 and 64). Note: even on 64-bit
systems, stand-alone WebSphere Customization Toolbox operates as a 32-bit component
with a 32-bit JDK. Platforms include: HPUX, Windows, Linux on x86, Linux on Power, Linux
on IBM System z, Solaris, and AIX.
V8.1
Student Notebook
Uempty
WebSphere Customization Toolbox: Installation

• Installation Manager is used to install WebSphere Customization
Toolbox
• Each underlying tool can be selected individually during installation
• WebSphere Customization Toolbox maintains a repository to store its

metadata
– Its location is tied to the user who started WebSphere Customization Toolbox
– C:\Documents and Settings\Administrator\AppData\Local\IBM\
WebSphere (Windows)
– /root/.ibm/WebSphere/AppServer/ (UNIX)
• Multiple launches of WebSphere Customization Toolbox allowed if

there are no workspace collisions
Figure 6-17. WebSphere Customization Toolbox: Installation WA855 / VA8551.0
Notes:
AIX 64-bit (embedded) requires GTK as a prerequisite. GTK stands for GNU GUI toolkit
from the GNU project. The installer can directly install GTK, or by installing Firefox the GTK
is automatically installed.

Student Notebook
WebSphere Customization Toolbox: Selective tool installation
Figure 6-18. WebSphere Customization Toolbox: Selective tool installation WA855 / VA8551.0
Notes:
This picture illustrates the choices for possible WebSphere Customization Toolbox tool
selections during installation.
V8.1
Student Notebook
Uempty
WebSphere Customization Toolbox: Features
Figure 6-19. WebSphere Customization Toolbox: Features WA855 / VA8551.0
Notes:
This picture illustrates the choices for possible WebSphere Customization Toolbox tool
features selections during modification, which is the same panel for features installation.

Student Notebook
Starting WebSphere Customization Toolbox

• For Windows and Linux systems, a Start menu shortcut is created
during installation
• On all supported platforms, a shell script can be used to start

– Stand-alone: <WCT-INSTALL-HOME>\WCT\wct.sh(bat)
– Embedded: <WAS_INSTALL-HOME>\bin\ProfileManagement\WCT\
wct.sh(bat)
• A pmt.sh(bat) shell script is provided for compatibility with earlier

versions but is deprecated in version 8
Figure 6-20. Starting WebSphere Customization Toolbox WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Embedded WebSphere Customization Toolbox
Figure 6-21. Embedded WebSphere Customization Toolbox WA855 / VA8551.0
Notes:

Student Notebook
Stand-alone WebSphere Customization Toolbox
Figure 6-22. Stand-alone WebSphere Customization Toolbox WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere Customization Toolbox: Command line

• WebSphere Customization Toolbox stand-alone includes a
command-line version
• Can be used to configure a web server to use an application server

as a hosting server
– For example: wctcmd.sh -tool pct -createDefinitionLocation
-defLocName WCTCmdTest2 -defLocPathname/WAS85/
Plugins -response/Temp/response.wct.txt
• Command-line arguments are documented in the information center
Figure 6-23. WebSphere Customization Toolbox: Command line WA855 / VA8551.0
Notes:
Command-line arguments are documented in the information center.

Student Notebook
WebSphere Customization Toolbox: Restrictions

• You cannot have the following tools or two instances of either tool
open at the same time:
– Profile Management Tool for distributed operating systems
– Migration Management Tool for distributed operating systems
• You cannot have the following tools within the WebSphere

Customization Toolbox or two instances of any one tool open at the
same time:
– Web Server Plug-ins Configuration Tool
– Profile Management Tool (z/OS only), which runs on Windows or Linux
operating systems that are based on Intel
– z/OS Migration Management Tool, which runs on Windows or Linux operating
systems that are based on Intel
Figure 6-24. WebSphere Customization Toolbox: Restrictions WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 6.3. Topic: Installing web server plug-ins

Student Notebook
Topic: Installing web

server plug-ins

Figure 6-25. Topic: Installing web server plug-ins WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Web server plug-ins: Package installation
Figure 6-26. Web server plug-ins: Package installation WA855 / VA8551.0
Notes:

Student Notebook
Web server plug-ins: License agreement

y Read or print the license agreement
y Accept the license agreement
Figure 6-27. Web server plug-ins: License agreement WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Web server plug-ins: Package group and installation directory
Figure 6-28. Web server plug-ins: Package group and installation directory WA855 / VA8551.0
Notes:

Student Notebook
Web server plug-ins: Features
Figure 6-29. Web server plug-ins: Features WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Web server plug-ins: Summary and results
y Verify the
package
y Review the
results
Figure 6-30. Web server plug-ins: Summary and results WA855 / VA8551.0
Notes:

Student Notebook
Plug-ins Configuration Tool: Add location
y After the plug-in is installed, it must be configured
y Start the Web Server Plug-ins Configuration Tool from the

y Select the installation location
Figure 6-31. Plug-ins Configuration Tool: Add location WA855 / VA8551.0
Notes:
After you install the plug-in, it must be configured. Configuration is done through the Web
Server Plug-ins Configuration Tool. The first step is to provide the location of the plug-in,
which is selected during installation of the plug-in.
V8.1
Student Notebook
Uempty
Plug-ins Configuration Tool: Web server selection
y Select the
web server
y Select the
location of
the
httpd.conf
file
Figure 6-32. Plug-ins Configuration Tool: Web server selection WA855 / VA8551.0
Notes:
Select the web server to configure. Be sure that it is installed. You also must select the web
server configuration file and web server port. After configuration, the configuration file
contains the location of the plug-ins and other information about the plug-ins.

Student Notebook
Plug-ins Configuration Tool: Administration server
y Configure IBM
HTTP Server
Administrative
Server when
administering
IBM HTTP
Server from the
administrative
console
Figure 6-33. Plug-ins Configuration Tool: Administration server WA855 / VA8551.0
Notes:
IBM HTTP Server Administration Server is used to control communication between the
administrative console and IBM HTTP Server.
V8.1
Student Notebook
Uempty
Plug-ins Configuration Tool: Web server definition name
y Web server name is used to identify the web server in the

administrative console
Figure 6-34. Plug-ins Configuration Tool: Web server definition name WA855 / VA8551.0
Notes:
The web server definition name is displayed in the administrative console and is used to
identify the web server.

Student Notebook
Plug-ins Configuration Tool: Configuration scenario
Figure 6-35. Plug-ins Configuration Tool: Configuration scenario WA855 / VA8551.0
Notes:
Determine whether the web server is hosted locally or remotely.
V8.1
Student Notebook
Uempty
Plug-ins Configuration Tool: Summary
Figure 6-36. Plug-ins Configuration Tool: Summary WA855 / VA8551.0
Notes:

Student Notebook
Plug-ins Configuration Tool: Results
Figure 6-37. Plug-ins Configuration Tool: Results WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Unit summary
• Explain the installation process for WebSphere Customization Toolbox
• Use the Plug-in Configuration Tool to configure the web server plug-in
Notes:

Student Notebook
1. What are the two platforms for the WebSphere Configuration Tool?
2. What is the reason for configuring HTTP Server Administrative

Server?
3. When running IBM HTTP Server as a Windows Service, what user

rights are required for the user account?
Notes:
1. 
2. 
3.
V8.1
Student Notebook
Uempty
Checkpoint answers
1. What are the two platforms for the WebSphere Configuration Tool?
• Embedded and stand-alone
2. What is the reason for configuring HTTP Server Administrative

Server?
• The Administrative Server controls communication between the
administrative console and IBM HTTP Server
3. When running IBM HTTP Server as a Windows Service, what user

rights are required for the user account?
• Act as part of the operating system
• Log on as a service
Notes:

Student Notebook
Exercise 1
Installing IBM Installation Manager

Figure 6-41. Exercise 1 WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
After completing this exercise, you should be able to:
• Install IBM Installation Manager
• View the installation log file
• Confirm the installation of Installation Manager
Figure 6-42. Exercise objectives WA855 / VA8551.0
Notes:

Student Notebook
Exercise 2
Installing WebSphere Application

Server

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Use IBM Installation Manager to install WebSphere Application Server
Network Deployment
• Use IBM Installation Manager to modify a product feature
• Use the Profile Management Tool to create a profile
• Verify that the installation was successful by examining log files
• Start and stop the application server
Notes:

Student Notebook
Exercise 3
Installing IBM HTTP Server

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Install IBM HTTP Server with IBM Installation Manager
• Confirm and test the installation of IBM HTTP Server
• Install Web Server Plug-ins for WebSphere Application Server
• Install WebSphere Customization Toolbox
• Configure the Web Server Plug-ins for WebSphere Application Server
• Examine the installed directories and files for IBM HTTP Server and the
plug-ins
Notes:

Student Notebook
V8.1
Student Notebook


This unit describes the features in the administrative console for
WebSphere Application Server.

• Describe how to access the administrative console
• Describe the administrative console in a cell topology
• Describe the administrative console interface
• Describe the use of the following administrative tools:
- Help
- Preferences
- Filters
- Guided activities
- Troubleshooting
• Describe user and group administrative roles
• Describe the Tivoli Performance Viewer

• Lab exercises
References
WebSphere Application Server Network Deployment V8.5 Information
Center:
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp
© Copyright IBM Corp. 2013 Unit 7. WebSphere Application Server administrative console 7-1
Student Notebook
Unit objectives
– Help
– Preferences
– Filters
– Guided activities
– Troubleshooting
Notes:
V8.1
Student Notebook
Uempty
Administrative console
• Web browser-based tool that manages

• Supports a full range of product
administrative activities
Figure 7-2. Administrative console WA855 / VA8551.0
Notes:
The administrative console is also known as the Integrated Solutions Console.
The console is accessed by using any supported web browser and entering the web
address: http://<host_name>:9060/ibm/console
Using the browser back button with the console can produce unexpected results and is not
supported. Use the controls and links that are provided in the console to navigate between
pages and applications.
Student Notebook
Starting the administrative console
Node
Application Server
Admin
console Load, edit, Admin
save application EAR file
Admin
service
• AdminApplication
– Installed as a system application Configuration
(XML files)
– Runs within an application server profile
– Cannot be managed through the console
– Not listed as an installed application Stand-alone single server
– WebSphere Security protects it
• Accessed through http://localhost:9060/ibm/console

– 9060 is the default port
Figure 7-3. Starting the administrative console WA855 / VA8551.0
Notes:
The administrative console is implemented as an application (AdminApplication). It is
deployed as a system application during product installation and within an application
server. The AdminApplication cannot be managed through the console, and is not listed as
an installed application. WebSphere administrative security is used to control which users
can log in to the console.
V8.1
Student Notebook
Uempty
Administrative console in a cell topology

Deployment Node agent
Web-based manager Admin server1
service
admin console
HTTP or
Admin Cell config
HTTPS
application server2
Node01 config
Web server1 config
container
Command-line server2 config EAR file
C:\> wsadmin
SOAP Node01
Admin
services Node agent
Master
Admin server3
service
Cell config
Node01 config Cell config
server1 config EAR file server4
Node02 config
server2 config
Node02 config server3 config
server3 config Commands server4 config EAR file
server4 config Configuration
Node02
Figure 7-4. Administrative console in a cell topology WA855 / VA8551.0
Notes:
This diagram depicts two separate views of WebSphere administration.
The flow of administration commands is shown as solid lines, and the flow of administration
configuration files is shown as dotted lines.
For both of these flows, the diagram proceeds from left to right.
Student Notebook
Console login 1
Log on to the console
• User ID
– A string that identifies the user
– Is used to track changes that
the user makes
– User ID must be unique
• Password
– If security is set, specify a
password
User ID conflict
y Shown when another
user is logged in with
the same user ID
Figure 7-5. Console login WA855 / VA8551.0
Notes:
To access the console, enter your user ID and password and then click Log in. The
password is required only if security is enabled.
If the user ID that you provide is already logged in at a different location, you are prompted
to choose between logging out from the other location or returning to the login page. If you
log out the user from the other location, you might be prompted to recover unsaved
changes that the user made.
V8.1
Student Notebook
Uempty
Recovering prior changes
• You can recover prior changes if your prior session times out
• Two options are available:
– Work with the default administrative configuration
– Work with the administrative configuration from the prior session
Figure 7-6. Recovering prior changes WA855 / VA8551.0
Notes:
After you are logged in, be sure to use the Logout link in the console toolbar when you are
finished working with the console to prevent unauthorized access. If there is no activity
during this login session for an extended period, the session expires, and you must log in
again to access the console. The administrator can change the session timeout. The
default is set to 30 minutes.
Student Notebook
Administrative console session timeout
Timeout value
in minutes
• Issue wsadmin –f <path to timeout script>/timeout.jacl

Figure 7-7. Administrative console session timeout WA855 / VA8551.0
Notes:
This slide shows a Jacl script that modifies the administrative console timeout duration. You
are going to work with a similar script in one of the upcoming lab exercises.
V8.1
Student Notebook
Uempty
Administrative console panels
1 Collection pages
2 Detail pages
3
Wizard pages
y JDBC
wizard is an
example © Copyright IBM Corporation 2013
Figure 7-8. Administrative console panels WA855 / VA8551.0
Notes:
This slide shows the three basic types of pages in the administrative console. These
common patterns provide a consistency of format within the administrative console.
Student Notebook
Administrative console areas
1 Banner
4 Message area
5 Help
3 Work area
2 Navigation tree
Figure 7-9. Administrative console areas WA855 / VA8551.0
Notes:
The purpose of this slide is to show the layout of the administrative console. The details are
not the important message here. It is not critical that you can read the text on this slide.
The next several slides show each of the sections in detail.
V8.1
Student Notebook
Uempty
Administrative console banner
Item Description
Welcome • The administrative console home page
• Contains links to information sources
Logout • Logs you out of the administrative console session
• Shows the Login page after successfully logging out
• If changes were made and not saved, the Save page is shown
Help • Opens a new web browser with detailed online help for the administrative console
• Note: This Help is not the information center
Figure 7-10. Administrative console banner WA855 / VA8551.0
Notes:
After you are logged in, be sure to use the Logout link in the console toolbar when you are
finished working with the console to prevent unauthorized access.
Student Notebook
Administrative console navigation tree (1 of 2)

Tasks Description
Guided activities Step-by-step guidance for certain configuration

tasks such a connecting to a database
Servers Configuration of application servers and web

servers
Applications Installation and management of applications
Services Configuration of service providers, clients,

policy sets, trust service, security, cache, and
reliable message state
Resources Configuration of application resources and

management of those resources
Security Configuration and management of WebSphere

security, SSL, and web services security
Environment Configuration of hosts, replication domains,

environment variables, naming, and others
Figure 7-11. Administrative console navigation tree (1 of 2) WA855 / VA8551.0
Notes:
This slide briefly describes some of the tasks that are listed in the navigation tree.
Expanding any of these tasks reveals more subtasks.
V8.1
Student Notebook
Uempty
Administrative console navigation tree (2 of 2)

Tasks Description
System Configuration and management of

administration components, users, and preferences
Users and Groups Configuration of users and groups
Monitoring and Configuration of the Performance Monitoring

Tuning Infrastructure and Tivoli Performance Viewer
Troubleshooting Tracking and verification of configuration

errors and problems
Service Configuration for service integration buses,

integration messaging engines, and messages
destinations
UDDI Configuration of UDDI nodes
Figure 7-12. Administrative console navigation tree (2 of 2) WA855 / VA8551.0
Notes:
This slide briefly describes the remaining tasks that are listed in the navigation tree. Some
of these tasks are explored in more detail later in this unit.
Student Notebook
Administrative console help (1 of 2)

1 Console help
y Click Help from console banner
y Select from list of references
Figure 7-13. Administrative console help (1 of 2) WA855 / VA8551.0
Notes:
All of the help panels that you can access from the administrative console are also
accessible from the WebSphere Application Server Information Center.
V8.1
Student Notebook
Uempty
Administrative console help (2 of 2)

2 Page help
y Click More information about this page
from help workspace
Figure 7-14. Administrative console help (2 of 2) WA855 / VA8551.0
Notes:
You can access help in the following ways:
• Click either of the following tabs of an online help page:
- Click the Help index tab and select from the list of help panels to view administrative
console help information.
- Click the Search tab, provide search terms, and then click Search. Under Results,
select a help panel that contains the search information.
• In the help portal that is on the right side of the administrative console panel, do one or
all of the following tasks:
- Click a field label or a list marker in the administrative console panel for the help to
display under field help. Alternatively, place the cursor over the field label or the list
marker for the corresponding help to display at the cursor. Attention: When you
place the cursor over the field label or list marker, the help might be truncated in a
Firefox browser. Click the field label or list marker so that the full help displays under
field help.
Student Notebook
- Click the link under Page help to access the help panel for the administrative
console panel. The help panel is the same help panel that displays when you click
the “?” icon.
- If Command assistance is listed, click the link under Command assistance to view
wsadmin scripting commands for the last action that completed within the console
panel.
V8.1
Student Notebook
Uempty
Administrative console preferences
• Specify how features of the administrative console workspace behave

Figure 7-15. Administrative console preferences WA855 / VA8551.0
Notes:
Use the preference settings to specify how you want information to display on an
administrative console panel. The preference settings vary from one administrative console
panel to another.
Turn on workspace automatic refresh: Specifies whether you want the administrative
console workspace to refresh automatically after the administrative configuration changes.
The default is for the workspace to refresh automatically. If you delete a WebSphere
variable, for example, the WebSphere variables page refreshes automatically and shows
the updated list of WebSphere variables in the WebSphere variables collection.
Enable command assistance notifications: Specifies whether to send Java
Management Extensions (JMX) notifications that contain command assistance data from
the administrative console. Enablement of the notifications allows integration with product
tools such as the Toolkit Jython editor for WebSphere Application Server. Enablement of
this option is suggested for non-production environments only.
Student Notebook
Administrative console preferences, filters, and scope

• Some
administrative
console
pages include 1 Set preferences
fields to
customize
how much
data is shown
• Select options
in the 2 Select resources
following
fields:
– Preferences 3 Set filters
– Filter
– Scope
Figure 7-16. Administrative console preferences, filters, and scope WA855 / VA8551.0
Notes:
Maximum rows: Indicates the maximum number of rows to display per page when the
collection is large.
Show resources at one authorizing group level: Specifies the authorization group level
that is used to filter the resources in the table. Only those roles that apply to your ID can
display in the table. Valid values are All Roles, Administrator, Deployer (for application
collection panels only), Operator, Configurator, and Monitor. If All Roles is selected, then all
the resources that you are authorized to view are displayed in the table and grouped by
role. Otherwise, the resources for the role that is selected are displayed in the table.
V8.1
Student Notebook
Uempty
Guided Activities
• Structured steps through • Otherwise, must know exactly what pages to

common administrative tasks use and where to find them within the console
Figure 7-17. Guided Activities WA855 / VA8551.0
Notes:
The Guided Activities feature displays each administrative console page on which you
must do a task. The following information surrounds the task to help you do the task
successfully.
The Guided Activities feature displays an introduction to the task, introducing essential
concepts and describing when and why to perform the task:
• Other tasks to perform before and after performing the task
• The main steps to complete during this task
• Hints and tips to help you avoid and recover from problems
• Links to field descriptions and extended task information, which can be found in the
online documentation
Student Notebook
My tasks
2 Select tasks to add to My tasks list
1 Select My tasks from the navigation view
selection list
2 Select tasks to add to My tasks list

3 The tasks are shown in My tasks list
Figure 7-18. My tasks WA855 / VA8551.0
Notes:
Use “My tasks” to create and edit a list of tasks to view in the console navigation. A task
includes a page that contains one or more web applications, or console modules, that are
used to complete that task. When you first access the console, all tasks to which you have
access are displayed in the navigation. “My tasks” is especially useful to customize the
navigation to show only the tasks you use most often. After you customize your tasks, “My
tasks” is initially displayed each time you log in to the console.
V8.1
Student Notebook
Uempty
Users and groups
Administrative
2
roles
y Monitor
y Configurator
y Operator
1 y Administrator
User and group y ISC Admins
management y Deployer
y Administer user y Admin Security
and group roles Manager
y Manage users y Auditor
and groups
Figure 7-19. Users and groups WA855 / VA8551.0
Notes:
Administrative user roles: Use this page to add, update, or remove administrative roles
for users. Assigning administrative roles to users enables them to administer application
servers through the administrative console or through wsadmin scripting.
Administrative group roles: Use this page to add, update or to remove administrative
roles for groups. Assigning administrative roles to groups enables them to administer
application servers through the administrative console or through wsadmin scripting.
Manage Users and Manage Groups: Allows you to create or delete users and groups
within your user registry.
Student Notebook
Troubleshooting information
• Troubleshooting
– Configure log and trace settings
– Identify and view configuration problems
– View class loaders for modules within the
topology of enterprise applications
– Generate thread, heap, and system memory
dumps
• Configuration Validation
– View problems that exist in the present
configuration
• Diagnostic Provider
– Review the startup configuration, current
configuration, and current state of a
diagnostic domain
• Runtime Messages
– Review runtime error, warnings, and
information messages
Figure 7-20. Troubleshooting information WA855 / VA8551.0
Notes:
The Class Loader Viewer helps you diagnose problems with class loaders.
Diagnostic Providers are a quick method for viewing configuration and the current state of
individual components within an application server environment.
V8.1
Student Notebook
Uempty
Tivoli Performance Viewer

• Integrated browser-based performance viewer and advisor
Figure 7-21. Tivoli Performance Viewer WA855 / VA8551.0
Notes:
Administrators and programmers can use Tivoli Performance Viewer to monitor the overall
health of WebSphere Application Server from within the administrative console.
From Tivoli Performance Viewer, you can view current activity or log Performance
Monitoring Infrastructure (PMI) performance data for the following resources:
• System resources such as processor utilization
• WebSphere pools and queues such as a database connection pool
• Customer application data such as average servlet response time
Student Notebook
Unit summary
– Help
– Preferences
– Filters
– Guided activities
– Troubleshooting
Notes:
V8.1
Student Notebook
Uempty
1. The AdminApp application can be configured with the administrative
console.
A. True
B. False
2. Configurable console settings, including session timeout, can be set

through the Console Preferences page of the system administration
task.
A. True
B. False
Notes:
1. 
2.



Student Notebook
Checkpoint answers
1. The AdminApp application can be configured with the administrative
console.
B. False
2. Configurable console settings, including session timeout, can be set

through the Console Preferences page of the system administration
task.
B. False. The session timeout is set from a script.
Notes:
V8.1
Student Notebook
Uempty
Exercise 4
Exploring the administrative console

Notes:
Student Notebook
Exercise objectives
• Verify that WebSphere Application Server is started
• Start the administrative console
• Explore the navigation and functions of the administrative console
• Use the administrative console to examine configuration information,
resources, and properties
Notes:
V8.1
Student Notebook
Uempty Unit 8. Introduction to the PlantsByWebSphere

application

This unit introduces the PlantsByWebSphere application architecture,
and explains how it is used to demonstrate WebSphere Application
Server concepts and functions.

• Describe the architecture and components of the
PlantsByWebSphere application
• Explain how the application is used as a case study for WebSphere
Application Server

• Lab exercises
References
Center:
© Copyright IBM Corp. 2013 Unit 8. Introduction to the PlantsByWebSphere application 8-1
Student Notebook
Unit objectives
• Describe the architecture and components of the PlantsByWebSphere
application
Application Server
Notes:
V8.1
Student Notebook
Uempty
PlantsByWebSphere application
• Simple shopping cart application

– Added server information
– Uses Derby, but can use DB2
– Built as an enhanced EAR
Figure 8-2. PlantsByWebSphere application WA855 / VA8551.0
Notes:
PlantsByWebSphere is a simple shopping cart application that is available with the
WebSphere Application Server distribution. It uses Derby as its back-end database, but
can also be configured to work with other databases such as DB2.
Student Notebook
PlantsByWebSphere sample
• PlantsByWebSphere is available through the Features > Samples
Applications that come with the WebSphere Application Server
– Can be found in <was_root>\samples\PlantsByWebSphere
– Additional samples are available through the information center
• The version of PlantsByWebSphere used in this course is altered
slightly
– To make the
PlantsByWebSphere
application more
useful for
educational
purposes, two links
are added to the
bottom of the
Help page
(View Server Info
and Admin Home)
Figure 8-3. PlantsByWebSphere sample WA855 / VA8551.0
Notes:
PlantsByWebSphere is a sample application. There are numerous other sample
applications, which are now available through the information center. In previous versions
of WebSphere, these other samples were available directly through the WebSphere
Application Server distribution.
For educational purposes, the PlantsByWebSphere application is modified slightly. This
modification is made to more easily demonstrate several functional issues that are useful to
point out in a class such as this.
To demonstrate session failover in a clustered environment, another link is added to the
Help page. This link shows server information so that it is easy to understand where the
server affinity is mapped.
• To more easily demonstrate application security, another link that is called Admin Home
is also added to the Help page. This link makes it easier to access the Admin servlet,
which is protected through Java EE security. Otherwise, the user must type in the URL
(or use a bookmark).
V8.1
Student Notebook
Uempty This course also uses DB2 instead of Derby, giving students a chance to configure data
sources and JDBC drivers (instead of relying on the embedded definitions as part of the
enhanced EAR). To rebuild the DB2 database, run the CreateDB script in the software
directory.
Student Notebook
Home page: http://<hostname>/PlantsByWebSphere
Figure 8-4. Home page: http://<hostname>/PlantsByWebSphere WA855 / VA8551.0
Notes:
This screen shows the home screen for the PlantsByWebSphere application.
V8.1
Student Notebook
Uempty
Login and Registration
• Log in with
– User: [email protected]
– Password: plants
• Or, register as new user
– Enter your own data
Figure 8-5. Login and Registration WA855 / VA8551.0
Notes:
This screen shows the Login and Registration screens for the PlantsByWebSphere
application.
It is not necessary to log in to the application unless the user wants to go through the
purchasing screens.
Student Notebook
My Account
• Click My Account on the

bottom to see your account
information
– If you are not logged in, you are
prompted to log in or register
Figure 8-6. My Account WA855 / VA8551.0
Notes:
This screen shows the My Account page for the PlantsByWebSphere application. If this
screen shows user information, it means that the user is already logged in. If not, a login
screen is displayed.
V8.1
Student Notebook
Uempty
Shopping
• Select a tab, and
then click items to
view or add to cart
Figure 8-7. Shopping WA855 / VA8551.0
Notes:
This screen shows three of the shopping tabs for the PlantsByWebSphere application.
These include Trees, Flowers, and Fruits & Vegetables. From these screens, users can
click the individual items and add them to their cart.
Student Notebook
Select an item
• When you have an item page open, you
see the details and are able to change
the quantity and Add to cart.
Figure 8-8. Select an item WA855 / VA8551.0
Notes:
This screen shows the details for an individual item within the PlantsByWebSphere
application. Users can click Add to cart and continue to shop. Or, if they want, they can
choose to check out.
V8.1
Student Notebook
Uempty
Shopping cart
• The shopping cart can be filled with
numerous items
• Click Checkout Now when ready
Figure 8-9. Shopping cart WA855 / VA8551.0
Notes:
This screen shows the shopping cart screen for the PlantsByWebSphere application. From
this screen, users can modify the quantities of their items, click Checkout Now, or continue
to shop.
Student Notebook
Checking out: Billing information
• Checkout requires more information,

including credit card data
• Click Continue
Figure 8-10. Checking out: Billing information WA855 / VA8551.0
Notes:
This screen shows the first of the checkout screens for the PlantsByWebSphere
application. This screen is where users confirm the billing and shipping information. They
also must enter credit card data. Be careful here, as the format of the credit card
information is required to be XXXX XXXX XXXX XXXX (with spaces).
V8.1
Student Notebook
Uempty
Checking out: Submit
• Click Submit
Order to complete
the transaction
Figure 8-11. Checking out: Submit WA855 / VA8551.0
Notes:
When the billing information is entered, the user is able to click Submit Order.
Student Notebook
Help page
• The Help page provides an

entry point to the following
links:
– View Server Info
– Admin Home
Figure 8-12. Help page WA855 / VA8551.0
Notes:
The Help page provides an entry point to the following links: View Server Info and Admin
Home. These links are added to the PlantsByWebSphere application especially for this
course. They are not part of the PlantsByWebSphere EAR file that is distributed with the
product.
V8.1
Student Notebook
Uempty
View Server Info page • The View Server Info page shows which
server is hosting the connection
– Used for demonstrating server failover
• It also displays the Session Data (and
time created)
– Used for demonstrating session failover
Figure 8-13. View Server Info page WA855 / VA8551.0
Notes:
The View Server Info page shows which server is hosting the current connection. This
information is useful for demonstrating server failover, since it is important to know which
cluster member to stop.
The session data is used to demonstrate failover of session information through
memory-to-memory replication.
The PlantsByWebSphere application does not store the shopping cart in an HTTP session
object, so it does not fail over correctly upon a server failure. Instead, this session
information field was created to demonstrate HTTP session object failover.
Student Notebook
Admin home page
• The Admin Home page is

used to demonstrate
application security
• When configured, these
pages require authentication
Figure 8-14. Admin home page WA855 / VA8551.0
Notes:
The administrative pages are mapped to the SampAdmin security role. When application
security is enabled, authentication is required to access these pages.
V8.1
Student Notebook
Uempty
HTML documentation for PlantsByWebSphere (1 of 2)

• For more information about PlantsByWebSphere, there are several
HTML files in the sample directory that can be useful
• Overview:
<was_root>/samples/PlantsByWebSphere/docs/index.html
Figure 8-15. HTML documentation for PlantsByWebSphere (1 of 2) WA855 / VA8551.0
Notes:
The following files contain potentially useful information about PlantsByWebSphere:
<was_root>/samples/PlantsByWebSphere/docs/index.html
<was_root>/samples/PlantsByWebSphere/docs/techNotes.html
Student Notebook
HTML documentation for PlantsByWebSphere (2 of 2)

• TechNotes:
<was_root>/samples/PlantsByWebSphere/docs/techNotes.html
Figure 8-16. HTML documentation for PlantsByWebSphere (2 of 2) WA855 / VA8551.0
Notes:
The Technotes page provides information about the default email address and password.
Also, the database tables and SQL statement for creating them are shown. A description of
the Java objects that are used in the application is shown.
The Plants by WebSphere Sample incorporates the following technologies:
• Java Persistence API (JPA) entity beans
• Stateless session beans
• Stateful session beans
• Servlets
• JavaServer Faces (JSF) files and Facelets
• Java Platform, Enterprise Edition security
The Plants by WebSphere application is supported through a series of JSF pages and
HTML pages. These pages communicate with the following servlets: AccountServlet,
V8.1
Student Notebook
Uempty ShoppingServlet, ImageServlet, and AdminServlet. The servlets use the various enterprise
bean business methods which, in turn, access data from the database as needed.
Student Notebook
Unit summary
• Describe the architecture and components of the PlantsByWebSphere
application
Application Server
Notes:
V8.1
Student Notebook
Uempty Unit 9. Application assembly

In this unit, you learn to use the IBM Assembly and Deploy Tools for
WebSphere Administration to prepare and export an enterprise
application for deployment to WebSphere Application Server.

• Describe the functions of the IBM Assembly and Deploy Tools for
WebSphere Administration
• Describe the application assembly process
• Describe the use of the IBM Assembly and Deploy Tools for
WebSphere Administration, including:
- Importing and examining application components
- Preparing and exporting an enterprise application for
deployment on WebSphere Application Server
- Explaining how annotations work and describing their benefits
for programmers
- Showing the metadata that annotations generate
- Explaining the relationship between annotations and
deployment descriptors

• Lab exercises
References
Center:
© Copyright IBM Corp. 2013 Unit 9. Application assembly 9-1

Student Notebook
Unit objectives
– Importing and examining application components
– Preparing and exporting an enterprise application for deployment on
– Explaining how annotations work and describing their benefits for programmers
– Showing the metadata that annotations generate
– Explaining the relationship between annotations and deployment descriptors
Notes:
V8.1
Student Notebook
Uempty
Topics
• Overview of Java EE application packaging
• Application assembly and deployment tools
• Enhanced EAR
• Java EE modules
• Java EE annotations
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 9.1. Overview of Java EE application packaging

Student Notebook
Overview of Java EE
application packaging

Figure 9-3. Overview of Java EE application packaging WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Overview of application assembly and installation
Enterprise
bean Deployment
descriptors
EAR file
Servlet
Web modules
Assemble EJB modules Install
Client modules Application
JSF
Deployment server
descriptor
HTML, GIF Application Enterprise

assembly application
Client
class
Figure 9-4. Overview of application assembly and installation WA855 / VA8551.0
Notes:
Two main activities are shown in this figure: assembly and installation. This unit describes
the assembly process, and a following unit defines the installation activity.

Student Notebook
Java EE 6 packaging
Resource J2EE
adapter application Application
RAR file DD
EAR file
EJB Web Web Client

module module DD module
JAR file WAR file JAR file
Enterprise HTML, Client

bean JSP DD
GIF
Client
Servlet class
EJB
Legend: DD
= Container file
= object that is contained
DD = deployment descriptor © Copyright IBM Corporation 2013
Figure 9-5. Java EE 6 packaging WA855 / VA8551.0
Notes:
This diagram shows the pieces that can be put together to create a Java EE 6 application.
V8.1
Student Notebook
Uempty
WebSphere: Application packaging

IBM
Resource Java EE bindings
adapter application Application
RAR file DD
EAR file IBM
extensions
Persistence EJB Web Web Client

unit DD module module DD module
JAR file WAR file JAR file
IBM
bindings Enterprise HTML, Client
bean JSP DD
GIF
IBM Client
extensions class
Servlet
EJB
Legend: DD
IBM IBM IBM
= Files bindings extensions bindings
= object that is in a file
DD = deployment descriptor © Copyright IBM Corporation 2013
Figure 9-6. WebSphere: Application packaging WA855 / VA8551.0
Notes:
See how this diagram adds more items to the enterprise application. (Hint: compare it to
the previous diagram).These additional items are required for the WebSphere Application
Server to “understand” how this application is going to run.

Student Notebook
WebSphere application contents

Deployment descriptors
• XML-based text files that describe the application environment
IBM bindings
• Bind application names to deployment platform-specific resources
– User-to-role mappings
IBM extensions
• Support other options, beyond the Java EE specification, such as:
– Access intent attributes
– Web application reloading
– File serving and servlet invoker (by class name)
Figure 9-7. WebSphere application contents WA855 / VA8551.0
Notes:
A deployment descriptor is an Extensible Markup Language (XML) file that describes how
to deploy a module or application by specifying configuration and container options.
Before an application can start, all enterprise bean (EJB) references and resource
references that are defined in the application must be bound to the actual artifacts
(enterprise beans or resources) defined in the application server.
When defining bindings, you specify Java Naming and Directory Interface (JNDI) names for
the referenceable and referenced artifacts in an application. The jndiName values that are
specified for artifacts must be qualified lookup names. An example of a referenceable
artifact is an EJB defined in an application. An example of a referenced artifact is an EJB or
a resource reference that the application uses.
V8.1
Student Notebook
Uempty 9.2. Application assembly and deployment tools

Student Notebook
Application assembly and

deployment tools

Figure 9-8. Application assembly and deployment tools WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Assembly and deployment tools

• IBM Assembly and Deploy Tools for WebSphere Administration is
included with WebSphere Application Server V8.5
– A subset of Rational Application Developer for the rapid assembly and
deployment of modules for WebSphere
– License for IBM Assembly and DeployTools does not expire
– Runs on Windows, Linux, AIX, and Oracle (Solaris) platforms
– Replaces the V7 Assembly and Deploy toolkit
– WebSphere Application Server license fully licenses and supports assembly and
deployment functions
• Rational Application Developer for WebSphere Software is available on

a trial basis for a limited time
– Available at:
http://www.ibm.com/developerworks/downloads/r/rad/
Figure 9-9. Assembly and deployment tools WA855 / VA8551.0
Notes:
IBM Assembly and Deploy Tools for WebSphere Administration enables rapid assembly
and deployment of applications to WebSphere Application Server environments. These
tools replace the previously available IBM Rational Application Developer Assembly and
Deploy function and are restricted to assembly and deployment usage only.

Student Notebook
IBM Assembly and Deploy Tools for WebSphere Administration
• Tool to assemble and configure enterprise applications

– Based on the Eclipse tools platform
– Subset of IBM Rational Application Developer for WebSphere
• Opening IBM Assembly and DeployTools requires pointing to a

workspace folder
– Files and metadata are kept in the workspace
– Create a workspace by pointing to an empty folder
– Thereafter open the workspace folder
– Guideline: one workspace per enterprise application
Figure 9-10. IBM Assembly and Deploy Tools for WebSphere Administration WA855 / VA8551.0
Notes:
With IBM Assembly and Deploy Tools for WebSphere Administration, you get access to the
complete set of Rational Application Developer documentation. Some documented
features are available only with the full Rational Application Developer for WebSphere
Software product.
V8.1
Student Notebook
Uempty
IBM Assembly and Deploy Tools tasks

• Create and configure Java EE enterprise applications (EAR files):
– Build from scratch
– Java EE modules
• Generate and modify deployment descriptor information

• Generate and modify binding information attributes
• Generate and modify the IBM extension attributes
• Deploy applications to a remote server
• Create, debug, and run Jython scripts
• Import command assistance logs from the console in to Jython scripts
• View, analyze, and correlate log files
Figure 9-11. IBM Assembly and Deploy Tools tasks WA855 / VA8551.0
Notes:
IBM Assembly and Deploy Tools provides all of the core functions for assembling and
deploying a Java EE application.

Student Notebook
Features in IBM Assembly and Deploy Tools for WebSphere

Administration (1 of 2)
• Tools for publishing server-side code on WebSphere V8.5
• Automated deployment descriptor generation and visual editors
• Jython scripting editor and debugger
• J2EE and Java EE XML form-based deployment descriptor and binding
editors
• Tools for assembling and deploying OSGi applications, bundles,
fragments, and composites and a source editor for blueprint file editing
• Tools for JAX-RPC web service import, discovery, and deployment
• Tools for JAX-WS web service deployment; policy set association and
binding
Figure 9-12. Features in IBM Assembly and Deploy Tools for WebSphere Administration (1 of 2) WA855 / VA8551.0
Notes:
• Java EE=Java Platform Enterprise Edition
V8.1
Student Notebook
Uempty
Features in IBM Assembly and Deploy Tools for WebSphere

Administration (2 of 2)
• XML deployment descriptor, binding editors, and code validators
• Tools for importing, exporting, assembling, and deploying Session
Initiation Protocol (SIP) applications
• Tools for assembling and deploying portlet applications
• Tools for adding database access to your applications, including built-in
support and JDBC providers for many supported databases
• EJB deployment
• Enhanced EAR editor
Figure 9-13. Features in IBM Assembly and Deploy Tools for WebSphere Administration (2 of 2) WA855 / VA8551.0
Notes:
IBM Assembly and Deploy Tools supports the following WebSphere Application Server
Version 8 applications for assembly and deployment purposes:
• Java EE
• Basic OSGi
• Web services
• XML
• Basic SIP
• Basic Portlet

Student Notebook
Assembling an enterprise application

• When working with a workspace that an application developer
provides, no assembly is required (the tool already automatically does
the assembly)
• The application assembler must:
– Configure modules
– Export an EAR file
• When assembling individual modules:
– Create a workspace (first time)
– Import modules into the workspace
– Assign modules to an enterprise application
– Configure the deployment descriptors of the module
– Configure the Java EE module dependencies
– Export the EAR file
• After assembly:
– Optionally test within the tool by using a V8.5.5 test server
Figure 9-14. Assembling an enterprise application WA855 / VA8551.0
Notes:
The final product of the application assembly process is an EAR file.
V8.1
Student Notebook
Uempty
Import modules
Wizard driven:
• Import modules
– EAR files
– EJB JAR files
– Application client
JAR files
– Web module
WAR files
• Import Java
Utility JAR files
• Imported into a
new or existing
enterprise
application
Figure 9-15. Import modules WA855 / VA8551.0
Notes:
Select File > Import.
Wizards are provided for importing application modules into the enterprise application.

Student Notebook
Java EE perspective
Editor
Project view
(Enterprise
Explorer)
Stacked views
Figure 9-16. Java EE perspective WA855 / VA8551.0
Notes:
This screen capture shows the primary perspective of IBM Assembly and Deploy Tools for
packaging Java EE applications.
V8.1
Student Notebook
Uempty
Application deployment descriptor (1 of 2)
Figure 9-17. Application deployment descriptor (1 of 2) WA855 / VA8551.0
Notes:
The detail on this picture shows the editor for the EAR file deployment descriptor. Some of
the actions that can be done are described on the next page.

Student Notebook
Application deployment descriptor (2 of 2)

Simplest of deployment
descriptors
(application.xml)
The editor can be used to:

• Edit the display name
and description of the
application
• Add and remove
modules
– Web
– EJB
– Application client
– Resource adapter
(connector)
• Work with security roles
of the application
Figure 9-18. Application deployment descriptor (2 of 2) WA855 / VA8551.0
Notes:
The application.xml file identifies each module of an application. A Java EE 6
application is not required to provide an application.xml file in the EAR file. When an
application.xml file does not exist, the product examines the Java archive (JAR) file
contents to determine whether the JAR file is an enterprise bean (EJB) module or an
application client module.
V8.1
Student Notebook
Uempty
Enterprise applications without application.xml

• Java EE 6 enterprise applications can be built without specifying an
application deployment descriptor (application.xml)
• The runtime product supplies a default deployment descriptor

– The application name is assumed to be the name of the EAR file with the .ear
extension removed
– Files ending in .war are assumed to be web modules
– The context root of the web module is assumed to be the name of the web
module with the .war extension removed
– Files not in the /lib directory that end in .jar, and contain an
ejb-jar.xml file or at least one EJB, are assumed to be EJB modules
Note the limitation of the default

context root name
Figure 9-19. Enterprise applications without application.xml WA855 / VA8551.0
Notes:
It is important to understand the limitation of the default context root name. For example, if
the web module is named PlantsByWebSphereWeb.war, then the default context root is
PlantsByWebSphereWeb.

Student Notebook
Packaging enterprise applications for deployment

• You can deploy Java compliant EAR and WAR files
• An enhanced EAR includes Java EE artifacts plus resource information
that is needed to install in the application server:
– JDBC resources (data sources) Enhanced EAR
– Class loader
– JAAS authentication aliases
– Shared libraries Resources
– Virtual host Enhanced Java EE
information EAR application
EAR
• Benefits in improved productivity:
– Application resources and Properties
properties come with the application
– The application installation process
creates the necessary resources within the server or cluster
– Moving an application from one server to another also moves the resources
• Assembly and deployment tools support WebSphere extensions
Figure 9-20. Packaging enterprise applications for deployment WA855 / VA8551.0
Notes:
An enhanced EAR file is created if you use the administrative console to export an
application.
To export applications, click Export on the Enterprise applications page. Using Export
produces an enhanced enterprise archive (EAR) file that contains the application and the
deployment configuration. The deployment configuration consists of the deployment.xml
and other configuration files that control the application behavior on a deployment target.
Exporting applications enables you to back up your applications and preserve binding
information for the applications. You might export your applications before updating
installed applications or migrating to a later version of the product.
V8.1
Student Notebook
Uempty
Application scope resources (1 of 2)

• Define
resources
to include
in the
enhanced
EAR file
Figure 9-21. Application scope resources (1 of 2) WA855 / VA8551.0
Notes:
This picture shows how to open the editor for resources that are going to be scoped at the
application level. These types of resources are part of an enhanced EAR. Later, there is
more information about enhanced EAR files.

Student Notebook
Application scope resources (2 of 2)
Figure 9-22. Application scope resources (2 of 2) WA855 / VA8551.0
Notes:
This picture shows part of the editing of an enhanced EAR.
V8.1
Student Notebook
Uempty 9.3. Enhanced EAR

Student Notebook
Enhanced EAR

Figure 9-23. Enhanced EAR WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Enhanced EAR
Not part of the Java EE specification
• Used mainly during development and test stages
• Not intended to be used in
Enhanced EAR
production
• Resources at application scope
Resources
Enhanced Java EE
EAR application
EAR
Properties
• Resources are visible in the administrative console

– Under the resources of the application, not with other scoped resources
– Can be tested in the console (for example, test connection for data sources)
• Takes precedence over all other scopes
Notes:
Resources are defined at application scope, which takes precedence over higher level
scopes.

Student Notebook
Unenhancing an EAR file

• Before deployment to production, remove resources that are defined in
an enhanced EAR file
• Reconfigure resources to be at the correct scope

– Preferably through scripting
• Resources can be removed:

– By using the IBM Assembly and DeployTools (preferable)
– Another .zip file-manipulating tool to remove the META-INF/ibmconfig
folder
– In UNIX systems, use the EARExpander script:
1. Expand the EAR file
2. Remove only the META-INF/ibmconfig folder and all of its contents
3. Compress the EAR file
4. Deploy
Figure 9-25. Unenhancing an EAR file WA855 / VA8551.0
Notes:
When an enhanced EAR is uninstalled, the resources that are defined at the application
scope are removed.
V8.1
Student Notebook
Uempty
Dealing with enhanced EAR files at deployment time
To ignore
application
scoped
resources at
installation time
Figure 9-26. Dealing with enhanced EAR files at deployment time WA855 / VA8551.0
Notes:
The check box named “Process embedded configuration” determines whether the
application scoped resources are deployed to the server. If this box is checked, then the
resources from the enhanced EAR get used. If it is not checked, these resources are
ignored and not installed in the WebSphere Application Server.

Student Notebook
V8.1
Student Notebook
Uempty 9.4. Java EE modules

Student Notebook
Java EE modules

Figure 9-27. Java EE modules WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
EJB module assembly

• Import wizard
– Imports into a new or existing enterprise project
• Adds Enterprise JavaBeans in the module

– Session bean
– Entity bean
– Message-driven bean
• Optionally use the deployment descriptor editor to configure

– EJB references
– Security roles
– Method permissions
– Application exceptions
– Container transactions
Figure 9-28. EJB module assembly WA855 / VA8551.0
Notes:
An enterprise bean is a managed Java component that can be combined with other
resources to create Java Enterprise Edition (Java EE) applications.
Assemble an EJB 3.0 or 3.1 module to contain enterprise beans and related code artifacts.
Group web components, client code, and resource adapter code in separate modules.
After the EJB module is assembled, install it as a stand-alone application or combine it with
other modules into an enterprise application.

Student Notebook
EJBs included in the web module

• In EJB 3.1, you can put
enterprise bean
classes in the WAR file
along with web
components
• No longer necessary to
put EJB classes in the
ejb-jar file
Figure 9-29. EJBs included in the web module WA855 / VA8551.0
Notes:
This picture from the IBM Assembly and Deploy Tools shows an EJB JAR file that is
packaged into a WAR module. According to the Java EE 6 specification, EJBs can now be
packaged into the WAR file.
V8.1
Student Notebook
Uempty
Web module assembly

• Import wizard
– Imports into an existing enterprise application project, or creates a new one
– Adds web components from a WAR module: Servlets, JSPs, static HTML,
supporting Java code
• Use the deployment descriptor editor to configure

– Named servlets and JSPs (URL mappings)
– Initialization parameters
– Resource references
– Security roles and constraints
– Authentication mechanism
– Welcome and error pages
– Filters and listeners
• Context root is defined under web_module > Properties > Web

Project Settings, not the deployment descriptor of the module
Figure 9-30. Web module assembly WA855 / VA8551.0
Notes:
The Import wizard imports into an existing enterprise application project, or creates a new
one. You can use the wizard to add web components from a WAR module, such as
servlets, JSPs, static HTML, and other supporting Java code.

Student Notebook
Web module
Figure 9-31. Web module WA855 / VA8551.0
Notes:
This screen gives a look at some of the files that are contained in the web module. This
module is going to be exported as a WAR file.
V8.1
Student Notebook
Uempty
Adding metadata through the menus
Figure 9-32. Adding metadata through the menus WA855 / VA8551.0
Notes:
By clicking an item in the IBM Assembly and Deploy Tools (typically a right-click), more
information can be created or modified. In the example that is shown here, security data is
going to be added to the web module.

Student Notebook
Web deployment descriptor editor
Figure 9-33. Web deployment descriptor editor WA855 / VA8551.0
Notes:
This screen shows the use of the IBM Assembly and Deploy Tools to edit the DD
(deployment descriptor) of the web module.
Open the Web Application 3.0 Deployment Descriptor Editor by double-clicking the web
module name in the Enterprise Explorer.
V8.1
Student Notebook
Uempty
Application client assembly

• Import wizard
– Imports into existing enterprise application project, or creates a new one
– Adds application client components from the JAR module
– Specify the class path and the class that contains the main() method that the
application client uses
• Add any icons

• Add EJB references
• Add resource references
Figure 9-34. Application client assembly WA855 / VA8551.0
Notes:
Application client projects contain the resources that are needed for application client
modules. An application client module is used to contain a full-function client Java
application (non-web-based) that connects to and uses the Java EE resources that are
defined in your server. When you place the client code in an application client module
instead of a simple JAR file, the application client benefits from the resources of the
application server. For example, it is not necessary to respecify the class path to Java EE
and server JAR files. Also, JNDI lookup is easier since the client container provides the
initial context and other parameters. The application client project allows you to work as if
you are creating a stand-alone Java application in a Java project.
An application client project enables you to do the following things:
• Develop the Java classes that implement the client module
• Set the application client deployment descriptor
• Test the application client

Student Notebook
Generating an EAR file for deployment

1
• Assemble application
modules
• Resolve Java EE
dependencies
• Save all changes
• Export the EAR file
• If source is available,
it can optionally be
2 included in the EAR
file
• The exported file is
ready to be deployed
Figure 9-35. Generating an EAR file for deployment WA855 / VA8551.0
Notes:
Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to
export an enterprise application project into an EAR file for deployment.
Optional: To export source files, select the Export source files check box.
Optional: If you are exporting to an existing EAR file and you do not want to be warned
about overwriting it, select the Overwrite existing file check box.
The wizard exports the contents of the EAR project to the specified EAR file. Additionally,
for each project that corresponds to a module or utility JAR in the application, the project
contents are exported into a nested module or JAR file in the EAR file. If any unsaved
changes exist on any of the files in any of the referenced projects, you are prompted to
save these files before export.
V8.1
Student Notebook
Uempty 9.5. Java EE annotations

Student Notebook
Java EE annotations

Figure 9-36. Java EE annotations WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Annotations in Java code

• The most prominent feature in Java EE 5 and EJB 3.0 is the use of
annotations
– Simplifies EJB development
– Removes the need for the deployment descriptor for most purposes
• Annotations are metadata that can be embedded directly into the Java
classes they describe
– Allow application settings to be visible in the component they affect
– Allow you to attach more information to a Java class or method
– The server generates EJB infrastructure code that is based on annotations
• A combination of annotations and deployment descriptor can be used
– The deployment descriptor augments or overrides the annotations
– Allows for customization when application is assembled or deployed
@Stateless
Annotation syntax starts with @ ...
@RolesAllowed ("SampAdmin")
public class BackOrderMgr {
...
Figure 9-37. Annotations in Java code WA855 / VA8551.0
Notes:
Annotations enable you to write metadata for Enterprise JavaBeans (EJB) inside your
source code. You can use them instead of Extensible Markup Language (XML) deployment
descriptor files. Annotations can also be used with descriptor files.

Student Notebook
How annotations help the developer
• Using annotations reduces complexity:

– Reduces the number of artifacts the developer must deal with
– Metadata is in the code instead of the deployment descriptors
– Default values can be used for most common scenarios
– Developers must specify information only if they want the application to behave
differently from the default
– Plain old Java objects (POJO) plus annotation-based programming model
Figure 9-38. How annotations help the developer WA855 / VA8551.0
Notes:
EJB 3.0 represents a vast improvement in the EJB programming model and is one of the
biggest potential sources of increased productivity for Java EE developers. An EJB can
now be an annotated “plain old Java object” (POJO), which is not required to extend a
certain class. It must implement a remote interface only, which you define or allow your IDE
to create automatically. Deployment descriptors are no longer required because the EJB
container can extract all that is necessary to know from the annotations on an EJB.
V8.1
Student Notebook
Uempty
Example of declaring a session bean with annotations
package com.ibm.websphere.samples.pbw.ejb;
import javax.ejb.Stateless;
...
/**
* The BackOrderMgr provides a transactional and secured
* facade to access back order information. This bean no longer
* requires an interface as there is one and only one implementation.
*/
@Stateless
public class BackOrderMgr
{
@PersistenceContext(unitName="PBW")
private EntityManager em;
...
Figure 9-39. Example of declaring a session bean with annotations WA855 / VA8551.0
Notes:
In Java Platform, Enterprise Edition 1.4, this EJB had to implement the SessionBean
interface, requiring six method implementations. In many cases, these method
implementations wind up empty and exist only to satisfy the interface and allow the code to
compile, leading to cluttered code. EJB 3.0 eliminates that problem by providing the
lifecycle annotations @PostConstruct, @PreDestroy, @PostActivate, and
@PrePassivate. You add these annotations as needed to any public, parameterless
method that returns void to implement reactions to lifecycle events.

Student Notebook
Stateless session bean as shown in the Explorer view
...
@Stateless
public class BackOrderMgr
{
@PersistenceContext(unitName=
"PBW")
private EntityManager em;
...
Figure 9-40. Stateless session bean as shown in the Explorer view WA855 / VA8551.0
Notes:
The Explorer view within the IBM Assembly and Deploy Tools allows you to see the
hierarchy of the application, its modules, and the components of the modules.
V8.1
Student Notebook
Uempty
Using annotations to inject EJB references

• Dependency injection:
– Hides creation and lookup of resources from application code
– Resources are “injected” into the source code by the container that is based on
the annotations specified
– Programmers are no longer required to do JNDI lookups in their code
– Clients that are managed classes can access EJBs by declaring a dependency:
@EJB
private CatalogMgr catalog;
private ProductBean product;

private LinkedList<ProductBean> products;
private float shippingCost;
Figure 9-41. Using annotations to inject EJB references WA855 / VA8551.0
Notes:
Here you see how an annotation becomes application metadata as seen in the console.

Student Notebook
Example of injecting an EJB reference
• Source
package com.ibm.websphere.samples.pbw.war;
import javax.ejb.EJB;
import javax.inject.Named;
...
@Named("help")
public class HelpBean {
@EJB ResetDBBean rdb;
• Generated EJB references
Figure 9-42. Example of injecting an EJB reference WA855 / VA8551.0
Notes:
The screen capture is from the administrative console. It shows a portion of the EJB
references for the PlantsByWebSphere application. You can access this view by clicking
Applications > Application Types > WebSphere enterprise applications >
PlantsByWebSphere > EJB > EJB references.
V8.1
Student Notebook
Uempty
Application bindings
• All EJB references and resource references that are defined in the
application must be bound to the artifacts defined in the application
server
– These artifacts include enterprise beans or resources
• You specify Java Naming and Directory Interface (JNDI) names for the
referenced artifacts in an application
• For EJB 3.0 modules, binding definitions are stored in

ibm-ejb-jar-bnd.xml
• For EJB 3.0 modules, you do not need to specify JNDI binding names
for each of the business interfaces on your enterprise beans
– If you do not explicitly assign bindings, the EJB container assigns default
bindings
Figure 9-43. Application bindings WA855 / VA8551.0
Notes:
An application assembler can define bindings when modifying deployment descriptors of
an application. Bindings are specified in the WebSphere Bindings section of a deployment
descriptor editor. Modifying the deployment descriptors might change the binding
definitions in the ibm-xxx-bnd.xmi files that are created when developing an application.
After defining the bindings, the assembler gives the application to a deployer. When
installing the application onto a supported application server, the deployer does not modify,
override, or generate default bindings unless changes are necessary for successful
deployment.

Student Notebook
WebSphere default bindings for bean interfaces

• WebSphere assigns default names that are based on patterns:
Description Binding pattern
Short form local ejblocal:<package.qualified.interface>

interfaces
Short form <package.qualified.interface>

remote interfaces
Long form local ejblocal:<component-id>#<package.qualified.interface>

interfaces
Long form ejb/component-id># <package.qualified.interface>

remote interfaces
Figure 9-44. WebSphere default bindings for bean interfaces WA855 / VA8551.0
Notes:
An application deployer or server administrator can use the administrative console to
modify the bindings when installing the application onto a supported application server.
New binding definitions can be specified on the installation wizard pages.
Also, a deployer or administrator can select to generate default bindings during application
installation. Selecting Generate default bindings during application installation instructs
the product to define incomplete bindings in the application with default values. Existing
bindings are not changed.
V8.1
Student Notebook
Uempty
Specifying Java EE 6 metadata for deployment
• Java EE 6 modules can specify metadata:

– In annotations
– In deployment descriptors
– Both: deployment descriptors override or augment annotations
• EJB 3.0 deployment descriptors (ejb-jar.xml) or web deployment

descriptors (web.xml) are optional in Java EE 6 EAR files
• You can view deployment descriptors in the WebSphere Application

Server administrative console, even if you did not specify them
– They are generated for you when you deploy the EAR in the application server
Figure 9-45. Specifying Java EE 6 metadata for deployment WA855 / VA8551.0
Notes:
Bindings support in the EJB container is expanded in Java EE 6. The EJB container
assigns default JNDI bindings for EJB 3.0 and 3.1 business interfaces. The bindings are
based on application name, module name, and component name. You do not have to
explicitly define JNDI binding names for each of the interfaces or EJB homes within an EJB
3.0 module or no-interface views within an EJB 3.1 module.

Student Notebook
Unit summary
– Importing and examining application components
– Preparing and exporting an enterprise application for deployment on
– Explaining how annotations work and describing their benefits for programmers
– Showing the metadata that annotations generate
– Explaining the relationship between annotations and deployment descriptors
Notes:
V8.1
Student Notebook
Uempty
1. The result of packaging an enterprise application is _________ .
2. True or false: Java EE 6 reduces or eliminates the need to deal with

Java EE deployment descriptors in many cases.
3. True or false: Enhanced enterprise applications are the preferred way

to deploy applications in a production environment.
Notes:
1. 
2. 
3.

Student Notebook
Checkpoint answers
1. The result of packaging an enterprise application is _________.
– An EAR file
2. True or false: Java EE 6 reduces or eliminates the need to deal with

Java EE deployment descriptors in many cases.
– True
“Annotations reduce or eliminate the need to deal with Java EE deployment
descriptors in many cases.” From the Java EE 6 specification
– Caveat: If you do not specify the deployment descriptors, the product
assumes certain default names.
3. True or false: Enhanced enterprise applications are the preferred way

to deploy applications in a production environment.
– False. Enhanced EAR files help the developer to test the application.
Notes:
V8.1
Student Notebook
Uempty
Exercise 5
Assembling an application

Notes:

Student Notebook
Exercise objectives
• Explore the Assembly and Deploy tool
• Import and examine enterprise application components
• Define application-scoped resources: data source and authentication
alias
• Export an enhanced EAR file that is ready for deployment
Notes:
V8.1
Student Notebook
Uempty Unit 10. Application installation

In this unit, you learn methods for installing and updating enterprise
applications on WebSphere Application Server.

• Describe methods of installing enterprise applications in
• Explain how fine-grained application updates work
• Describe enterprise application properties
• Enable monitored directories
• Deploy an application by using the monitored directory
• Use a profile-file-based configuration with monitored directories to
deploy an application

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 10. Application installation 10-1

Student Notebook
Unit objectives
• Describe methods of installing enterprise applications in WebSphere
Application Server
Notes:
V8.1
Student Notebook
Uempty
Topics
• Application installation
• Application settings and interaction
• Monitored directory
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 10.1.Application installation

Student Notebook
Application installation

Figure 10-3. Application installation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Installing enterprise applications
Administrative
EAR file
console
WebSphere
Application
Server
EAR file
wsadmin>
Jython
script
Configuration
Figure 10-4. Installing enterprise applications WA855 / VA8551.0
Notes:
This simple diagram shows the two paths for installing an EAR file (enterprise application)
into the application server:
• From the administrative console
• Using a script or commands with wsadmin

Student Notebook
Installation tasks
• Configure the application environment as required
– Variables, virtual hosts, class path, security
• Configure application resources

– JDBC provider, data sources, JMS resources, or SIBus, if applicable
• Install the application

– The default directory that is assigned to hold the EAR file before it is installed is
<profile_root>\<profile>\installableApps
– Most often, the application file you receive is an enterprise archive (.ear) file
• Manage static content

– Web server serves files, not in EAR file
– Leave static content in EAR file
Figure 10-5. Installation tasks WA855 / VA8551.0
Notes:
Installing an application involves configuring the runtime environment as required. You can
define variables, virtual hosts, and any other resources that the application needs before
you actually install the application. In general, it is a good practice to leave the static
content that the application uses in the EAR file, and allow the infrastructure to take care of
serving and caching the static content. In the end, leaving the static content in the EAR file
can be as effective as moving it to the web server.
V8.1
Student Notebook
Uempty
Creating a J2C authentication alias

• Wizard can be reached from many pages in the administrative
console
– Security > Global Security > Authentication > Java Authentication and
Authorization Service > J2C authentication data
• Provide
– Alias name: console
prefixes name with
node name
– User ID and
corresponding
password
– Optional description
– EJBs, data sources,
JMS resources,
and SIBus
resources use them
Figure 10-6. Creating a J2C authentication alias WA855 / VA8551.0
Notes:
Here is the input screen for creating a security resource that is used to access a back-end
resource.

Student Notebook
Creating a data source (1 of 3)
• Create JDBC provider before or while defining data

sources
• One JDBC provider is needed for each database
driver type
• JDBC providers can be defined at cell, node, server,
or application scope (in an enhanced EAR file)
Figure 10-7. Creating a data source (1 of 3) WA855 / VA8551.0
Notes:
These screens show the process for creating the required resources that an application
uses to access a database. Here you see the setup for the database drivers (JDBC).
V8.1
Student Notebook
Uempty

• JDBC driver paths can be defined in the wizard
Notes:
uses to access a database. These two screens show the definition of variables that hold
the path to the database drivers.

Student Notebook

• Provide the database-specific parameters:
– Driver type
– Database name
– Database server name and communication port number
• Choose whether data source is going to be used with CMP beans
Notes:
uses to access a database. This simple screen shows the data that is required to access a
database.
V8.1
Student Notebook
Uempty
Installing a new application

• Select Applications >
New Application >
New Enterprise Application
Figure 10-10. Installing a new application WA855 / VA8551.0
Notes:
Here are the screens for the simple method of installing an application. This method is
called the “fast path.”

Student Notebook
Example of fast path installation
Step 1:
Select
installation
options
Figure 10-11. Example of fast path installation WA855 / VA8551.0
Notes:
There are various options available for the fast path installation.
V8.1
Student Notebook
Uempty
Example of detailed installation
Summary
step
Figure 10-12. Example of detailed installation WA855 / VA8551.0
Notes:
This picture shows the summary of information just before the application is installed.

Student Notebook
Enhanced EAR
• Enterprise archive that contains Java EE artifacts plus resource information
necessary to install on WebSphere Application Server
– JDBC resources (data sources)
– Class loader Enhanced EAR
– JAAS authentication aliases
Resources
– Shared libraries
– Virtual host information Enterprise
application
• Benefits: improved productivity EAR
Properties
– Application resources and properties come
with the application
– Application installation process creates the
necessary resources within the server or cluster
– Moving application from one server to another also moves the resources
• Support integrated with the IBM Rational Development and Assembly and
Deployment tools
– Found on Deployment page of application deployment descriptor
• Warning: Can possibly cause problems if unintended application scoped
resources are used in production
– Enhancements can be removed or ignored during application installation
Notes:
A JDBC resource can be defined in an enhanced EAR file. Enhanced EAR files are specific
to IBM WebSphere and are not part of Java EE. However, artifacts that are defined within
an enhanced EAR are ignored if this EAR file is installed on an application server other
than WebSphere.
Developers or administrators can use tools to define resources and properties within an
enterprise application, and import or export the enhanced EAR file.
Some resources still must be defined in the application server, for example, JMS and
JavaMail. Settings are defined in IBM tools, which are stored in deployment.xml, and
packaged with the EAR file. These resources are applied at the new application scope.
EAR files and enhanced EAR files are presented in more detail later in the course.
V8.1
Student Notebook
Uempty
Removing enhancements
• Resources can be
ignored
– Remove
enhancements from
EAR before
deploying (preferred)
– Clear Process
embedded
configurations
– Is prechecked only if
there are
enhancements
• Resources can be viewed, but not

through the normal screens
– Click Application scoped resources
under the enterprise application
Figure 10-14. Removing enhancements WA855 / VA8551.0
Notes:
There are several methods to ignore resources in an enhanced EAR file. The preferred
method is to remove enhancements from the EAR before deploying. If there are
enhancements, clear the check box for Process embedded configuration. This check
box is filled only if there are enhancements.
You can view resources, but not through the normal screens. You must click Application
scoped resources under the enterprise application.

Student Notebook
V8.1
Student Notebook
Uempty 10.2.Application settings and interaction

Student Notebook
Application settings and

interaction

Figure 10-15. Application settings and interaction WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Starting an application
• After the application is installed, you can select from a number of options
to manage the application
– Click Applications > Application types > WebSphere enterprise
applications
Figure 10-16. Starting an application WA855 / VA8551.0
Notes:
After the application is installed, you can see it listed on the Enterprise Applications page
by going to Applications > Applications types > WebSphere enterprise applications.
To start the application you installed, click the check box beside it to select it, and then click
Start. The application status symbol changes from a red X to a green arrow.

Student Notebook
Application update
You can update the full

application, a single
module, a single file, or
part of the application
Figure 10-17. Application update WA855 / VA8551.0
Notes:
It is possible to update an application without uninstalling that application first. This screen
is the screen that is used to update an existing application. It is not important that you read
all of the options on this slide, just that you understand the purpose of this activity.
V8.1
Student Notebook
Uempty
Other application configuration settings
• Click Applications > Application Types > WebSphere

enterprise applications > application_name
Enable or
disable New options:
automatic • Metadata
start for modules
• Manage
modules
Configure
startup
behavior
View
deployment
descriptor
Figure 10-18. Other application configuration settings WA855 / VA8551.0
Notes:
This slide shows a broad overview of the metadata for an enterprise application that can be
modified or configured through the application console.

Student Notebook
Application startup behavior and auto start

• Start up behavior of an application
– The values set affect how quickly an application starts and what occurs when
an application starts
– Click Applications > Application Types > WebSphere enterprise
applications > application_name > Startup behavior in the console
navigation tree to configure startup behavior settings
• Automatic starting of an application

– By default, an installed application starts automatically when the server starts
on which the application is deployed
– Click Applications > Application Types > WebSphere enterprise
applications > application_name > Target specific application status to
configure auto startup
Figure 10-19. Application startup behavior and auto start WA855 / VA8551.0
Notes:
For the startup behavior of an application, the values that are set affect how quickly an
application starts and what occurs when an application starts. By default, an application
starts when its parent server starts.
V8.1
Student Notebook
Uempty
View the application deployment descriptor
Figure 10-20. View the application deployment descriptor WA855 / VA8551.0
Notes:
This slide shows the link for viewing the application deployment descriptor. Note: IBM
Assembly and Deploy Tools allows for editing this data before the application is installed.

Student Notebook
The application deployment descriptor
Figure 10-21. The application deployment descriptor WA855 / VA8551.0
Notes:
You can view the application.xml deployment descriptor for the installed application
from the administrative console. Select Enterprise applications > application_name and
then click View Deployment Descriptor under Detail Properties.
V8.1
Student Notebook
Uempty
Manage modules (1 of 4)
• To view the web or EJB deployment descriptors for an enterprise
application
– Click Manage Modules
Figure 10-22. Manage modules (1 of 4) WA855 / VA8551.0
Notes:
These four slides show the steps for viewing the deployment descriptor of an EJB JAR file
(EJB module). First, on the application details view, click the link for Manage Modules.

Student Notebook
Notes:
(EJB module). Second, click the module that contains the EJBs (shown here as
“PlantsbyWebSphere”).
V8.1
Student Notebook
Uempty
Notes:
(EJB module). Third, on the right side, click the link titled View Deployment Descriptor.

Student Notebook
Notes:
(EJB module). Fourth, the details of the EJB deployment descriptor are shown.
V8.1
Student Notebook
Uempty
Metadata for modules (1 of 2)

• This option enables you to either allow or ignore metadata that is
coming from annotations in source code
Figure 10-26. Metadata for modules (1 of 2) WA855 / VA8551.0
Notes:
It is not necessarily a suggested practice to set metadata-complete to true if your
programmers intend to use annotation-based programming techniques. The technique that
you adopt can be based on personal preference.
Values in deployment descriptors can augment or override the equivalent annotation-based
metadata:
• After viewing the deployment descriptor information in the administrative console, the
deployer can change the appropriate deployment descriptor to reflect the required
changes.
• Expand the EAR file in the directory you installed from, for example:
<profile_root>/<profile>/installableApps
• Modify the deployment descriptor with your required changes and reinstall or update the
application.

Student Notebook
Metadata for modules (2 of 2)
Figure 10-27. Metadata for modules (2 of 2) WA855 / VA8551.0
Notes:
The next slide gives some guidelines on how and when to set the metadata-complete
options for the modules of an application.
V8.1
Student Notebook
Uempty 10.3.Monitored directory

Student Notebook
Monitored directory

Figure 10-28. Monitored directory WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Overview of monitored directory deployment

• A simple and fast way to install, update, and uninstall applications
without:
– The administrative console
– Rational Application Developer
– wsadmin
– A specially configured environment
• Tasks can be accomplished by copying archive files in or out of a

monitored directory
– The application must be an EAR, JAR, WAR, or SAR
EAR
Monitored directory
Figure 10-29. Overview of monitored directory deployment WA855 / VA8551.0
Notes:
A monitored directory application deployment is a new, simple, and fast way for
administrators and developers to install, update, and uninstall applications by moving
archive files in or out of a monitored directory.
A user who prepackages an application file with all bindings specified can quickly deploy
that application without any tools other than a running application server or, in a network
deployment environment, a deployment manager.
Monitored directory application deployment can be done with applications packaged as
enterprise archive (EAR) files, web archive (WAR) files, Java archive (JAR) files, or SIP
application resources (SARs).
In addition to the mentioned archive files, a properties file can be used to deploy an
application.
Properties files are different from the other file types. They are not archives. Instead, they
contain properties that describe an application, including the source archive location and its
installation parameters. Monitored directory deployment with properties files relies on the

Student Notebook
properties file based configuration (PFBC) feature introduced in WebSphere Application

Server Version 7. Using a properties file can allow a higher degree of control over the
deployment than with a plain archive.
V8.1
Student Notebook
Uempty
Supported tasks
• Install: place an archive file into the monitored directory
• Uninstall: remove an archive file from the monitored directory
• Update: move or copy a new archive file with the same name as an
existing archive file in the monitored directory
remove
EAR Install
EAR
Update
EAR
Monitored directory
Figure 10-30. Supported tasks WA855 / VA8551.0
Notes:
To install an application, use an operating system file management tool such as a graphical
file manager or the command line to copy or move its archive file into a monitored directory.
Deleting a file from a monitored directory causes uninstallation of the corresponding
application.
To do a full replacement update of a deployed application, move or copy an updated
archive file with the same application name into a monitored directory. The archive file
name determines the application name. Or, or in case of an EAR archive, the display name
determines the application name if a display name is specified in the archive.

Student Notebook
Enabling the monitored directory

• Disabled by default in both stand-alone federated environments
– Click Applications > Global deployment settings
Figure 10-31. Enabling the monitored directory WA855 / VA8551.0
Notes:
Before using monitored directory deployment, it must be enabled. Go to the administrative
console under Applications > Global deployment settings. In addition to enabling the
service, the Global deployment settings panel allows configuration of the root path to the
monitored directories and the polling interval at which the monitored directories are
checked for changes.
Enabling the service is required only once.
The deployment manager or base server where the service is running must be restarted to
register any changes on the Applications > Global deployment settings panel.
V8.1
Student Notebook
Uempty
Notes about the monitored directory

• Within the existing directory structure, it is possible to create specific
server, cluster, and even node directories
– These additional structures allow tasks to be directed to specific elements of
your environment
• Directory location:
– Stand-alone:
<profile_root>/monitoredDeployableApps/servers/<servername>
– Federated:
<dmgr_profile>/monitoredDeployableApps/servers/<servername>
• For clusters:
– Create a clusters directory:
.../monitoredDeployableApps/clusters/<clustername>
• For servers with the same name on federated nodes:

– Applications are deployed to all servers with the same name
– Create: .../monitoredDeployableApps/nodes/nodename/servers/
<servername>
Figure 10-32. Notes about the monitored directory WA855 / VA8551.0
Notes:
The path to a monitored directory depends on the type of application server, and what the
target of the deployment is going to be. To control where the monitored directory
applications are deployed, administrators create more directories to represent their clusters
or servers. These names must exactly match what is actually in the cell.
If you are using a stand-alone application server, then the only possible target is the server
itself, and the monitored directory is automatically created if the service is enabled. For
example, if the profile is called AppSrv01, and the server is named server1, the path is:
app_server_root/profiles/AppSrv01/monitoredDeployableApps/server1
If you are using a network deployment system, it is necessary to create the monitored
directories manually.
For application servers on a node that is federated with a deployment manager, you must
create the monitored directories for servers under the deployment manager profile:
app_server_root/profiles/dmgrprofilename/monitoredDeployableApps/servers/
server_name

Student Notebook
If multiple servers on different nodes have the same name and you want to target only one
of the servers, you can specify the node and server in the path to the monitored directory.
Create a directory for the node by using the node name, then servers, and finally the
server_name directory.
app_server_root/profiles/dmgrprofilename/monitoredDeployableApps/nodes/node
_name/servers/server_name
For clusters, create a monitored directory under the deployment manager profile with the
name of the targeted cluster:
app_server_root/profiles/dmrprofilename/monitoredDeployableApps/clusters/
cluster_name
V8.1
Student Notebook
Uempty
Drag-and-drop properties files

• The standard drag-and-drop approach lacks the ability to do anything
but the default
– There is no ability to customize a deployment in any way
• Drag-and-drop technique also supports properties file based

configuration
– A property file can define which EAR file to install, and also configure any of the
necessary attributes
Properties Monitored directory

file
EAR
Figure 10-33. Drag-and-drop properties files WA855 / VA8551.0
Notes:
Monitored directory supports the ability to drag a properties file. This support allows
administrators to customize any installation settings that might be required for monitored
directory installations.

Student Notebook
Properties file based configuration

• Provides a group of administrative commands
• Manage system configuration
• Troubleshoot configuration issues
• Replicate configuration properties across profiles, nodes, servers, or
applications
• Use properties file on monitored directory deployment to deploy
applications
• Introduced in WebSphere Application Server V7.0
Figure 10-34. Properties file based configuration WA855 / VA8551.0
Notes:
Version 7 introduced the properties file based configuration feature, which provides a group
of administrative commands to manage system configuration by using properties files.
Users can use the properties file based configuration commands to copy configuration
properties from one environment to another. They can also use the properties file to
troubleshoot configuration issues and apply one set of configuration properties across
multiple profiles, nodes, cells, servers, or applications. The details of the properties file
based configuration commands are documented in the version 7 information center. The
monitored directory deployment is extended to use the properties file to install, uninstall, or
update an application in version 8.
V8.1
Student Notebook
Uempty
Steps to use properties file to deploy applications (1 of 2)

• Step 1: create a properties file that defines deployment options
– Use properties file based configuration command to create an application
properties file
– Extract application properties to a file with version 7 output format

AdminTask.extractConfigProperties('[-propertiesFileName
myApp.props
myApp.props -configData
-configData Deployment=MyApplication]')
Deployment=MyApplication]')
– Extract application properties to a file with simple output format

myApp.props
myApp.props -configData
-configData Deployment=MyApplication
Deployment=MyApplication --
options
options [[SimpleOutputFormat
[[SimpleOutputFormat true]]]')
true]]]')
– Note: the monitored directory installation process uses only the properties that
relate to an application
– Create the file manually
Figure 10-35. Steps to use properties file to deploy applications (1 of 2) WA855 / VA8551.0
Notes:
A user can use the properties file based configuration command to extract application
properties to an application properties file. After a properties file is extracted, edit
application properties and copy the properties file to the MonitoredDeployableApps
directory under the deploymentProperties directory. The Monitored directory
deployment service runs the applyConfigProperties command to apply the application
properties change to install, uninstall, or update an application for you.
Step 1 shows how to use the properties file based configuration
extractConfigProperties command to extract application properties to a file.
By default, the extractConfigProperties command produces output that displays all
columns, including all hidden and non-hidden columns of installation tasks and task data
values, in separate rows. You can also extract application properties in simple output
format to display non-hidden columns of installation task data in columnName=value pairs.
You can also use the properties file examples that are documented in the information
center to create an application properties file to deploy, uninstall, or update an application.

Student Notebook
Steps to use properties file to deploy applications (2 of 2)

• Step 2: verify that the targeted server or cluster member is running
• Step 3: verify that monitored directory deployment is enabled
• Step 4: copy the properties file to the deploymentProperties
directory
copy
Properties file deploymentProperties
EAR
Figure 10-36. Steps to use properties file to deploy applications (2 of 2) WA855 / VA8551.0
Notes:
The monitored directory deployment service starts the application after it is deployed or
updated. Therefore, you must verify that the application server or cluster member on which
you want to install the enterprise application files is running.
Step 3 is to verify that the monitored directory deployment is enabled. You can look at the
information center “Setting monitored directory deployment values” section.
The last step is to copy the application properties file to the monitoredDeployableApps
directory. You can use a file browser to drag the properties file to the monitored directory or
use the operating system command to copy the properties file to the directory.
V8.1
Student Notebook
Uempty
Unit summary
• Describe methods of installing enterprise applications in WebSphere
Application Server
Notes:

Student Notebook
1. True or false: You can update a single module or part of an
application in the console.
2. True or false: The default startup behavior for an application is to

automatically start when the server starts.
3. True or false: Monitored directory is supported in a federated

environment.
Notes:
1. 
2. 
3. 
V8.1
Student Notebook
Uempty
Checkpoint answers
1. True. You can update a single module or part of an application.
2. True. The default startup behavior for an application is to

automatically start when the server starts.
3. True. Monitored directory is supported in a federated environment.
Notes:

Student Notebook
Exercise 6
Installing an application

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Use the administrative console to install an application
• Use a web browser to test the application
• Use the drag-and-drop function to deploy an application
Notes:

Student Notebook
V8.1
Student Notebook
Uempty Unit 11. Problem determination

This unit introduces you to resources and basic methods for problem
determination.

• Describe a basic approach for problem determination
• List resources for completing a problem investigation
• Locate relevant log files
• Examine log activity
• Enable tracing on specific components
• Enable high performance extensible logging (HPEL) and use the
Log Viewer
• Locate other troubleshooting tools
• Use the IBM Support Assistant

• Checkpoint
• Lab exercises
References
WebSphere Application Server V8.5 Information Center,
troubleshooting and support topics:
© Copyright IBM Corp. 2013 Unit 11. Problem determination 11-1

Student Notebook
Unit objectives
• Enable high performance extensible logging (HPEL) and use the Log
Viewer
Notes:
V8.1
Student Notebook
Uempty
Topics
• Server logs and diagnostic tracing
• Gathering diagnostic data
• Problem determination tools
• IBM Support Assistant
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 11.1.Server logs and diagnostic tracing

Student Notebook
Server logs and diagnostic

tracing

Figure 11-3. Server logs and diagnostic tracing WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Examining server log files

• Log files are an initial source of diagnostic data
• WebSphere provides several useful logs, including:

– JVM logs
– Process logs
– HTTP plug-in logs
– Console runtime messages
Figure 11-4. Examining server log files WA855 / VA8551.0
Notes:
WebSphere provides several useful logs and messaging facilities, including JVM logs,
HTTP plug-in logs, and console runtime messages.

Student Notebook
WebSphere Application Server logs

• JVM logs: created by redirecting the System.out and
System.err streams of the JVM to independent log files
– One set of JVM logs for each application server and all of its applications that
are located by default in the following directory:
<profile_root>/<profile_name>/logs/<server_name>
– SystemOut.log and SystemErr.log
• Process logs: contain two output streams (stdout and stderror) which
are accessible to native code that runs in the process
– One set for each application server
– native_stderr.log and native_stdout.log
• IBM service log: contains both the WebSphere Application Server

messages that are written to the System.out stream and some
special messages that contain extended service information
– One per profile (node)
– activity.log
Figure 11-5. WebSphere Application Server logs WA855 / VA8551.0
Notes:
Java virtual machine (JVM) logs
The JVM logs are created by redirecting the System.out and System.err streams of the
JVM to independent log files. WebSphere Application Server writes formatted messages to
the System.out stream. In addition, applications and other code can write to these
streams by using the print() and println() methods of the streams.
In a WebSphere Application Server Network Deployment configuration, JVM logs are also
created for the deployment manager and each node agent because they also represent
JVMs.
Process logs
WebSphere Application Server processes contain two output streams, which are
accessible to native code that is running in the process. These streams are the stdout and
stderr streams. Native code, including Java virtual machines (JVM), might write data to
these process streams. JVM-provided System.out and System.err streams can be
configured to write their data to these streams.
V8.1
Student Notebook
Uempty As with JVM logs, there is a set of process logs for each application server, since each JVM
is an operating system process. For a WebSphere Application Server Network Deployment
configuration, there is a set of process logs for the deployment manager and each node
agent.
IBM service logs
The IBM service log contains the WebSphere Application Server messages that are written
to the System.out stream. It also contains some special messages that provide extended
service information, which is normally not of interest, but can be important when analyzing
problems. There is one service log for all WebSphere Application Server JVMs on a node,
including all application servers. The IBM service log is maintained in a binary format and
requires a special tool to view. This viewer, the Log Analyzer, provides more diagnostic
capabilities. In addition, the binary format provides capabilities that IBM support
organizations use.
The HTTP server plug-in log is covered later in this presentation.

Student Notebook
Server log files: Types and locations

• Application server log file destinations and names are configurable
– The default location is:
<was_root>\profiles\<profile_name>\logs\<server_name>
• Application server log files are all text files
– JVM logs: SystemOut.log and SystemErr.log
– Start and stop logs: startServer.log and stopServer.log
– Diagnostic trace log: trace.log
– Process logs: native_stdout.log and native_stderr.log
• Web server plug-in log file:
– http_plugin.log
– Location: <plugin_root>\logs\<webserver_name>
• IBM service log is in binary format

– In <profile_root>\<profile_name>\logs\activity.log directory
– Use Log Analyzer in IBM Support Assistant to view
Figure 11-6. Server log files: Types and locations WA855 / VA8551.0
Notes:
All WebSphere Application Server log files are under the
<was_root>\profiles\<profile_name>\logs directory.
The default names for the JVM logs are SystemOut.log and SystemErr.log. They
contain server information and user program information (sent by System.out.xxx code
in the program).
The startServer.log and stopServer.log files can also be found under the
<was_root>\logs\<servername> directory; they contain information that the server logs
as it starts and shuts down.
The activity.log file size can be set by using the administrative console as IBM service
logs. You can also disable activity.log.
The standard JVM output and error logs are SystemOut.log and SystemErr.log.
The startServer.log and stopServer.log files are written to during startup and
shutdown of the application servers.
V8.1
Student Notebook
Uempty The trace.log file contains output from a diagnostic trace if tracing is enabled. The
location and name of this log file are configurable.
The operating system uses the native_stdout.log and native_stderr.log files to log
out-of-memory exceptions and verbose garbage collection data, if verbose GC is enabled.
The http_plugin.log file is the web server plug-in log file. It is not in <was_root>, but in
<plugin_root>\logs\<webserver_name>.

Student Notebook
Configuring JVM logs
• From the administrative console,

select Troubleshooting >
Logs and Trace >
server_name > JVM Logs
• SystemOut and SystemErr logs
can be configured from this
page
• Logs are self-managing
– Can roll over based on time or
file size
– Number of historical log files is
configurable
• To view logs through the

console, use the runtime tab
Figure 11-7. Configuring JVM logs WA855 / VA8551.0
Notes:
The JVM logs can be configured from the administrative console. For both log files,
systemOut and systemErr, you can specify the path to their location, file formatting (basic
or advanced), and log file rotation (by file size or time interval). You can also configure the
maximum number of historical files to store on the file system.
V8.1
Student Notebook
Uempty
Viewing runtime messages in the console (1 of 2)

• Runtime events are grouped
according to severity: error,
warning, information
• To view, select:
Troubleshooting >
Runtime Messages >
– Runtime Error
– Runtime Warning
– Runtime Information
• Runtime events are disabled

by default
– None
• Select Info to enable all

runtime events
Figure 11-8. Viewing runtime messages in the console (1 of 2) WA855 / VA8551.0
Notes:
When viewing runtime messages, first select the Error, Warning, or Info category link (a
count of zero means that nothing is available). Then, the details for the selected category
are shown. Selecting one of these links gives you detail information (see next slide).
You can have multiple pages of messages; the button on the bottom of the page allows you
to view and read all of them.

Student Notebook
Viewing runtime messages in the console (2 of 2)

• Runtime events details
include:
– Message code and text
– Brief explanation of the
event
– Action for the user to take
– What server component
issued the message
• Other details include:

– Timestamp
– Thread ID
– Node name
– Server name
Figure 11-9. Viewing runtime messages in the console (2 of 2) WA855 / VA8551.0
Notes:
Most runtime messages are designed with improved message text. A message code, for
example SRVE0255E, can be used to look up the message in the information center.
Information is shown on the detail screen for the event, and sometimes a user action is
provided to resolve the problem.
V8.1
Student Notebook
Uempty
HTTP plug-in logs and tracing

• To configure plug-in logs and tracing from the administrative console, click
Servers > Web Servers > web_server_name > Plug-in Properties >
Configuration tab > Plug-in logging
• Default location:
<plugin_root>/logs/<web_server_name>/http_plugin.log
• Set the Log level to Trace to trace all the steps in the HTTP request
process (caution: this trace produces much log data)
Figure 11-10. HTTP plug-in logs and tracing WA855 / VA8551.0
Notes:
The HTTP plug-in logs messages to a log file that is stored under the plugin_root
directory on the web server. The log level can be set to different values, depending on the
amount of detail that you want written to the log. Setting the log level to Trace causes it to
log all steps in the request process.
The embedded HTTP server logs
There are administrative console panels for configuring embedded HTTP server (HTTP
transport channel) logs. There are also an access log and an error log.
From main application server configuration panel, click Troubleshooting > server_name
> HTTP Error and NCSA Access Logging.
This service is disabled by default. To enable, check the Enable logging service box, and
restart the server.
Error logs can be controlled separately with log levels: Critical, Error, Warning, Information,
Debug

Student Notebook
Diagnostic tracing
• Diagnostic tracing can be used to collect detailed processing data for
all WebSphere Application Server components
• To take advantage of tracing, you must:

– Enable tracing of one or more WebSphere components
– Configure and view trace logs
– Interpret trace logs and trace messages
• Trace files show the time and sequence of methods that WebSphere
Application Server base classes call
– You can use these files to pinpoint the failure
Figure 11-11. Diagnostic tracing WA855 / VA8551.0
Notes:
To take advantage of tracing, you do these steps:
1. Enable tracing of one or more WebSphere components.
2. Configure and view trace logs.
3. Interpret trace logs and trace messages.
V8.1
Student Notebook
Uempty
Using diagnostic tracing

• Tracing can be started:
– While the server is running, by using Runtime Diagnostic Trace
– When the server is starting and running, by using Configuration Diagnostic
Trace
• Trace output can be directed to:
– File (default)
– Memory ring buffer, and dumped after trace stops
• Tracing has a significant affect on performance
– Enable temporarily for problem determination
– Tracing to a file is slower than tracing to a memory ring buffer
Trace Memory Dump

Java component Dump
ring buffer file
Figure 11-12. Using diagnostic tracing WA855 / VA8551.0
Notes:
Trace output allows administrators to examine processes in the application server and
diagnose various issues. On an application server, trace output can be directed either to a
file or to an in-memory circular buffer. If trace output is directed to the in-memory circular
buffer, it must be dumped to a file before it can be viewed. On an application client or
stand-alone process, trace output can be directed either to a file or to the process console
window. In all cases, trace output is generated as plain text in either basic, advanced, or log
analyzer format as the user chooses. The basic and advanced formats for trace output are
similar to the basic and advanced formats that are available for the JVM message logs.

Student Notebook
Enable and configure tracing
• Troubleshooting >
Logs and Trace >
server_name >
Diagnostic Trace
• Configure Trace Output

– None
– Memory buffer
– File (default)
• Configure Trace Output Format

– Basic (IBM Support preference)
– Advanced
• Note: Configure Log Detail Level

to get trace output
Figure 11-13. Enable and configure tracing WA855 / VA8551.0
Notes:
The Diagnostic Trace Service box looks almost the same as it did in previous versions. The
Configuration and Runtime tabs behave as they always have, with Configuration affecting
the configuration repository and taking effect at the next startup. The Runtime settings take
effect immediately but are only optionally persisted to the server configuration.
Trace strings must be configured on a separate panel (Log Detail Level).
View and dump are available in the Runtime tab of diagnostic trace. The Log Analyzer can
be used to analyze trace output, but you can use your favorite editor. Before you can view
or dump a trace, you must specify the log detail level.
V8.1
Student Notebook
Uempty
Setting the log detail level (1 of 2)

• Logs and trace >
server_name >
Change Log Detail Level
• Log detail level affects tracing and
regular logging
– Setting levels below info reduces
the amount of data in logs
– *=off disables logging altogether
• Trace levels (fine, finer, finest) are
not displayed in the trace file
unless logging is enabled
• Use the graphical menu to type in
or set the log string
– Default is *=info
• User-created applications can be
instrumented too, and be included
in the trace output
Figure 11-14. Setting the log detail level (1 of 2) WA855 / VA8551.0
Notes:
Log levels control which events Java logging processes.
WebSphere Application Server controls the levels of all loggers in the system. The level
value is set from configuration data when the logger is created and can be changed at run
time from the administrative console.
Note: Trace information, which covers events at levels fine, finer, and finest, can be written
to the trace log. Therefore, if you do not enable diagnostic trace, setting the log detail level
to fine, finer, or finest does not affect the data that is logged.
Log string syntax: <component / group> = <log level>
Examples include:
• com.ibm.ws.classloader.ClassGraph=finest enables the finest trace level for
com.ibm.ws.classloader.ClassGraph
• EJBContainer=fine enables the least verbose trace level for all components in the
EJBContainer group

Student Notebook
• com.ibm.ws.classloader.*=finer enables detailed trace for all classes in the

com.ibm.ws.classloader package
• *=info sets the log level for all components to info (default is no trace output)
V8.1
Student Notebook
Uempty
Setting the log detail level (2 of 2)

• Select
component
• Select one of
– No Logging
– Messages Only
– All Messages
and Traces
• Or select
Message and
Trace Levels
and select
Message
Levels
Figure 11-15. Setting the log detail level (2 of 2) WA855 / VA8551.0
Notes:
Examples include:
• No Logging results in the following trace string: com.ibm.websphere.security.*=off
• Messages Only results in the following trace string: *=info (the default)
• All Messages and Traces results in the following trace string:
com.ibm.websphere.security.*=all

Student Notebook
Trace output content and format

• Trace output allows administrators to examine processes in the
application server and diagnose various issues
• Two formats can be configured

– Basic (IBM Support preference)
– Advanced
• Trace events that are displayed in basic use the following format:
– <timestamp><threadId><shortName><eventType>[className]
[methodName]<textmessage> [parameter 1] [parameter 2]
• Possible values of eventType include:

– > a trace entry of type method entry
– < a trace entry of type method exit
– 3 a trace entry of type finest, debug, or dump
Figure 11-16. Trace output content and format WA855 / VA8551.0
Notes:
Other values of eventType include:
• 1: a trace entry of type fine or event
• 2: a trace entry of type finer
• Z: a placeholder to indicate that the trace type was not recognized
V8.1
Student Notebook
Uempty
Reading a log or trace file (1 of 2)

• Example log record format
• [5/9/11 12:27:56:237 EDT] 00000000 PMIImpl A CWPMI1001I:
PMI is enabled
– Timestamp = [5/9/11 Message type Description
12:27:56:237 EDT] 1,2,3 Trace information: fine, finer, finest
– Thread ID = 00000000 A Audit
– Logger = PMIImpl W Warning
– Message type = A
Z Type was not recognized
– Message code =
CWPMI1001I E Error
– Message = D Detail
PMI is enabled C Configuration
F Fatal (exits process)
I Information
O Program output (system.out)
R Program output (system.err)

Figure 11-17. Reading a log or trace file (1 of 2) WA855 / VA8551.0
Notes:
The following list defines the sections of a trace entry:
• TimeStamp: The timestamp is formatted by using the locale of the process where it is
formatted. It includes a fully qualified date (YYMMDD), 24-hour time with millisecond
precision, and the time zone. ThreadId is an eight-character hexadecimal value that is
generated from the hash code of the thread that issued the trace event.
• ThreadName: The name of the Java thread that issued the message or trace event.
• ShortName: The abbreviated name of the logging component that issued the trace
event. This value is typically the class name for WebSphere Application Server internal
components, but can be some other identifier for user applications.
• LongName: The full name of the logging component that issued the trace event. This
value is typically the fully qualified class name for WebSphere Application Server
internal components, but can be some other identifier for user applications.
• EventType: A one-character field that indicates the type of the trace event. Trace types
are in lowercase.

Student Notebook
• ClassName: The class that issued the message or trace event.

• MethodName: The method that issued the message or trace event.
V8.1
Student Notebook
Uempty
Reading a log or trace file (2 of 2)

• Timestamps give good clues:
– Timestamps are real host time values
– Good when comparing traces from different processes and correlating events of
different servers
• Look for exceptions (search for exception from top of stack trace)
– Events before the exception are probable causes
– Events after the exception are recovery attempts
• Often useful to follow a single thread

– Use the Thread ID to gather related messages
Figure 11-18. Reading a log or trace file (2 of 2) WA855 / VA8551.0
Notes:
While it is possible to use a text editor to read logs and trace files, it is suggested that you
use a tool such as Log Analyzer, which is available in the IBM Support Assistant.

Student Notebook
High Performance Extensible Logging (HPEL)

• HPEL can be enabled on
any server in the cell
– Deployment manager
– Node agent
– Application server
• Click
Troubleshooting >
Logs and trace >
server_name
– Click Switch to
HPEL mode
Figure 11-19. High Performance Extensible Logging (HPEL) WA855 / VA8551.0
Notes:
After the log level is switched to HPEL mode for a server, there is a new list of links in the
General Properties section. One new link is Change log and trace mode, which allows
you to switch back to basic logging.
V8.1
Student Notebook
Uempty
HPEL logging and tracing configuration

• Use this page to configure HPEL logging and tracing
Figure 11-20. HPEL logging and tracing configuration WA855 / VA8551.0
Notes:
This screen capture shows the default configuration for HPEL logging and tracing. To
modify the configuration, click any of the links on this page.
After HPEL is enabled for a server, it is suggested that you disable the HPEL text log.
Disabling the text log improves server performance.

Student Notebook
Configure HPEL logging

• Clicking the Configure
HPEL logging link
starts the configuration
page
• Changes that are made

on the Configuration
tab require you to restart
the server
• Changes that are made

on the runtime tab take
effect immediately
Figure 11-21. Configure HPEL logging WA855 / VA8551.0
Notes:
Clicking the Configure HPEL logging link starts the configuration page. Changes that are
made on the Configuration tab require a server restart. Changes that are made on the
runtime tab take effect immediately.
V8.1
Student Notebook
Uempty
The HPEL Log Viewer

• Click Troubleshooting > Logs and trace > server_name > View
HPEL logs and trace
– There are numerous filtering options to modify which records are displayed
Figure 11-22. The HPEL Log Viewer WA855 / VA8551.0
Notes:
The log view section lists the records. Use the First Page, Previous Page, Next Page,
and Last Page buttons to move through the list of records. You can also specify filter
criteria in the Content and Filtering Details section to limit the rows that are shown. Records
are always listed in the order that the server recorded them. By default, the log view has
five columns:
• Time Stamp: The time when the event was recorded.
• Thread ID: The identity of the thread that recorded the event in hexadecimal notation.
• Logger: The logger that recorded the event.
• Level: The type of event that was recorded.
• Message: The message from the recorded event. If the message has a message ID,
the message ID is underlined. Click the message ID to get an explanation and
suggested user action for the message.
To manipulate the log view, you can use available buttons to complete the following
actions:

Student Notebook
• Refresh View: Uses records from the server to clear the contents of the viewer and
reinitialize the view. Use this button to retrieve information about any additional rows
that are created since the log viewer was started.
• Show Only Selected Threads: Show only records with the same thread as the one
that is selected in the selection area. Clicking this button enables the Show All
Threads button.
• Show All Threads: Lists any records that were filtered when you clicked Show Only
Selected Threads. This button is enabled only when you use the Show Only Selected
Threads button to restrict the view.
• Select Columns: Enables you to select the columns in the viewer that you want to
view.
• Export: Exports logs to the local workstation in any of basic, advanced, or binary
(HPEL) formats.
• Copy to Clipboard: Copies the records that are highlighted in the selection area into
the operating system clipboard.
• Server Instance Information: Lists attributes for the selected server instance process.
Use this table to find attributes and corresponding values for the server instance
process environment. These properties are similar to the ones that are found in the
header of basic mode logs.
V8.1
Student Notebook
Uempty
LogViewer command-line tool (1 of 2)

• Use the LogViewer command to query the contents of the High
Performance Extensible Logging (HPEL) log and trace repositories
– logViewer.sh/bat
• You can also use the LogViewer command to view new log and
trace repository entries as the server writes content to them
– logViewer.sh/bat –monitor [interval]
Figure 11-23. LogViewer command-line tool (1 of 2) WA855 / VA8551.0
Notes:
The first tool for analyzing HPEL logs is the command-line log viewer. The command-line
log viewer is a simple, intuitive, and fast tool for doing analysis on the logs in problem
determination efforts.
You are no longer required to be aware of whether data is written to the SystemOut.log,
SystemErr.log, or trace.log file. With HPEL, the logs are consolidated, and the log
viewer can be used to view all the data or filtered according to what subset of messages
you need:
• -tail [interval]: Specifies that you want the logViewer to continuously monitor the
repository and output new log record entries as they are created. You can provide an
optional integer argument after this parameter to specify how often you want the
LogViewer tool to query the repository for new records. By default, the LogViewer
queries the repository for new records every 5 seconds. When used with other filtering
options, only those new records that match the filter criteria are listed.
• -monitor [interval]: A synonym for -tail.

Student Notebook
LogViewer command-line tool (2 of 2)

• To get a listing of available logViewer options:
– logViewer.sh/bat -help
• The logViewer command started from the profile bin directory

without any options results in a display of all the log and trace
messages of a server
• To view the log and trace entries of the most recent server, run:
– logViewer.sh/bat –latestInstance
– With this option, it is no longer necessary to clear log files before restarting a
server
Figure 11-24. LogViewer command-line tool (2 of 2) WA855 / VA8551.0
Notes:
To get a listing of available LogViewer options, use the -help option.
LogViewer can be started from the bin directory of a profile without any options, and a
listing of all the entries of a server is shown. If there are multiple servers in a profile, the
user is first prompted to select the server for viewing.
V8.1
Student Notebook
Uempty
What is Cross Component Trace (XCT)?

• A feature that annotates the logs so that entries that are related to a
request are identified as belonging to the same unit of work
• The request might traverse more than one

– Thread
– Process
– Server
• XCT helps identify the root cause of problems across components,

which provides the following benefits:
– Enables administrators and support teams to follow the flow of a request from
end-to-end.
– The request is traced as it traverses thread or process boundaries, or travels
between stack products and WebSphere Application Server
– Helps to resolve questions about which component is responsible for a request
that fails
Figure 11-25. What is Cross Component Trace (XCT)? WA855 / VA8551.0
Notes:
Depending on the nature of your applications, multiple threads within an application server
might be used to handle requests, such as HTTP requests or JMS requests. More than one
application server can handle some requests, such as when one application server makes
a request to another application server for a web services request.
Applications that are built by using distributed architectures, such as service-oriented
architecture, can benefit from XCT, since XCT helps facilitate problem determination across
multiple services on different systems.

Student Notebook
Administering XCT
• A server must have HPEL enabled before XCT can be enabled
• Click Troubleshooting > Logs and trace > server_name > Change
log detail levels
• Check Enable log and trace correlation
• Select option for including request IDs, creating correlation logs,

capturing data snapshots
Figure 11-26. Administering XCT WA855 / VA8551.0
Notes:
Enable XCT to include request IDs in log and trace files when you want to see which log
and trace entries, in all threads and application server processes, are related to the same
request. Request IDs are recorded only when using HPEL log and trace mode and can be
seen or used for filtering when using the logViewer command.
Enable XCT to create correlation log records when you want to log how requests branch
between threads and processes, and see extra information about each request. Enabling
XCT to create correlation log records might have a significant performance impact on your
system, so it is best suited to test and development environments.
V8.1
Student Notebook
Uempty
XCT request IDs

• XCT request IDs are identifiers added to log and trace records that the
server produces
• XCT adds the same request ID to every log or trace record that is a
part of the same request, regardless of which thread or JVM produces
the record
• When XCT is used with the HPEL log and trace infrastructure, you can
view request IDs when logs are output in advanced format
– logViewer.sh -minLevel WARNING -format advanced
[Time_stamp] 00000094 W UOW= source=com.ibm.ws.webcontainer.srt

class=com.ibm.ws.webcontainer.srt.SRTServletResponse method=setIntHeader
org= prod= component= thread=[WebContainer : 4]
requestID=[AAAsirk1Njr-AAAAAAAAAA+] appName=[PlantsByWebSphere]
Figure 11-27. XCT request IDs WA855 / VA8551.0
Notes:
You can use XCT to augment your log and trace files with correlation information. This
correlation information clarifies which threads and which application server processes
participated in the handling of each request.

Student Notebook
Use XCT request ID information to track requests

• Filter your logs by request ID by using the HPEL LogViewer command-
line tool
– logViewer.sh -includeExtensions requestID=AAAsirk1Njr-
AAAAAAAAAA+
[Time_stamp] 00000094 XCT I BEGIN AAAsirk1Njr-AAAAAAAAAA+

00000000000-cccccccccc2 HTTPCF(InboundRequest
/PlantsByWebSphere/javax.faces.resource/jsf.js.jsf
RemoteAddress(127.0.0.1) RequestContext(-957274864))
[Time_stamp] 00000094 srt W

com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W:
WARNING: Cannot set header. Response already committed.
[Time_stamp] 00000094 XCT I END AAAsirk1Njr-AAAAAAAAAA+

00000000000-cccccccccc2 HTTPCF(Request AsyncWrite RequestContext(-
957274864))
Figure 11-28. Use XCT request ID information to track requests WA855 / VA8551.0
Notes:
XCT log records:
• XCT log records are typically added to the logs to:
- Demarcate the beginning and ending of work for a particular request on a particular
thread
- Demarcate when work is transferred to another thread or process, or to indicate
when work returned from another thread or process
- Demarcate when work moves from major component to major component, even if
work continues on the same thread; for example, to show transfer of control from
application server code to application code
• XCT log records are composed of:
- XCT type (BEGIN / END)
- XCT parent correlator ID (for example, 00000000000-cccccccccc2)
- XCT current correlator ID (for example, AAAsirk1Njr-AAAAAAAAAA+)
V8.1
Student Notebook
Uempty - XCT annotations, for example:

HTTPCF(InboundRequest)
/PlantsByWebSphere/javax.faces.resource/jsf.js.jsf
RemoteAddress(127.0.0.1) RequestContext(-957274864)
• XCT tools
The HPEL logViewer tool is able to filter log and trace records by request ID.
Tools such as the XCT Log Viewer can also take advantage of XCT log records or XCT
request IDs, or both, when rendering log and trace content. The XCT Log Viewer is
available as a tool add-on for the IBM Support Assistant.

Student Notebook
V8.1
Student Notebook
Uempty 11.2.Gathering diagnostic data

Student Notebook
Gathering diagnostic data

Figure 11-29. Gathering diagnostic data WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Gathering JVM diagnostic data

• A wealth of valuable JVM diagnostic data can be gathered by doing the
following tasks:
– Enable logging of verbose garbage collection data for servers
– Generate a Java thread dump
– Generate a Java heap dump
– Generate a system core dump
– Configure hung thread detection
– Enable tracing of connection leaks
Figure 11-30. Gathering JVM diagnostic data WA855 / VA8551.0
Notes:
The tasks that are listed on this slide are described in detail in the WebSphere Application
Server V8.5 Information Center. See the articles on troubleshooting.

Student Notebook
Enable verbose garbage collection

• Verbose GC is an option that the JVM run time provides
• Provides a garbage collection log
– Interval between collections
– Duration of collection
– Compaction required
– Memory size, memory that was freed, memory available
• Turns on verbose GC for each server through the administrative
console
– Servers > server_name > Process Definition > Java Virtual Machine
– Select “Verbose Garbage Collection” check box
– Save and distribute
– Restart the server or servers
• Usually writes to native_stderr.log file
– Varies depending on platform and WebSphere version
– Some load on system resources because of disk I/O, but minimal unless
thrashing
Figure 11-31. Enable verbose garbage collection WA855 / VA8551.0
Notes:
It is often suggested that you have verbose GC enabled permanently in production. The
cost on a reasonably well-tuned JVM is small. The benefits of having it on the first time
something happens are considerable (no necessity to reproduce the problem a second
time after enabling). It is also good to keep an eye on the verbose GC regularly as a way to
monitor the health of the system, even when nothing bad is noticed.
Enabling verbose GC is a decision that each system administrator must make
conscientiously. However, it is no longer “not recommended as a normal production
setting.”
V8.1
Student Notebook
Uempty
Java memory dumps and cores

• New feature in the Troubleshooting section is Java dumps and cores
• Select servers and click

– Heap dump
– Java core
– System dump
Figure 11-32. Java memory dumps and cores WA855 / VA8551.0
Notes:
Clicking the Java dumps and cores link opens the panel that is shown in the screen
capture. Use this panel to generate heap dumps, Java cores, or system dumps for a
running process. Select the server and click the appropriate button for Heap dump, Java
core (thread dump), or System dump (JVM core). The files that result from these
operations are placed on the local file system; by default they are written to the profile root
directory, was_root/profiles/profile-name.
• Heap dump: A heap dump is a snapshot of JVM memory. It shows live objects in the
memory and references between them.
• Java core: Use this button to investigate why a server is hanging or to investigate
messages in the logs that indicate a thread did not complete its work in the expected
amount of time.
• System dump: Use this button to generate system native dumps of the server process.
These dumps can be large.

Student Notebook
A note on verbose garbage collection data: As in previous versions, verbose GC is not

enabled by default. When you enable verbose GC for a server in version 8, the default
garbage collection policy is generational-concurrent (gencon). The data is written to the
native_stderr.log or native_stdout.log file, depending on the operating system of
the server.
V8.1
Student Notebook
Uempty
Generating a JVM thread dump (javacore)

• What is a javacore?
– Small diagnostic text file that the JVM produces
– Contains much vital information about the running JVM process
– Provides a snapshot of all the running threads, their stack traces, and the
monitors (locks) held by the threads
– Useful for detecting hang or deadlock conditions
• How to manually trigger a thread dump

– Warning: triggering a thread dump can terminate the server process
– Use operating system facilities:
kill -3 <JVM PID> (UNIX or Linux)
– Explicitly tell WebSphere to generate a thread dump
– Issue wsadmin Jacl or Jython commands
Figure 11-33. Generating a JVM thread dump (javacore) WA855 / VA8551.0
Notes:
Run the following wsadmin Jacl commands:
set jvm [$AdminControl completeObjectNametype=JVM, process=<SERVER_NAME>,*]
$AdminControl invoke $jvm dumpThreads
Thread dumps also can be helpful in detecting performance problems. Take a few (at least
three) snapshots of the JVM (about 2–3 minutes apart). Analyze the javacore file to see
what different threads are doing in each snapshot.
For example, a series of snapshots where container threads are in the same method or
waiting on the same monitor or resource is an indication of a bottleneck, hang, or deadlock.

Student Notebook
Generating a JVM heap dump

• JVM heap dump is created in the <profile_root> directory when
an OutOfMemoryError exception is thrown
– Heap dump is in phd (portable heap dump) format by default
– Different locations and formats can be configured by using command-line
arguments
• Use the –Xdump generic JVM arguments to configure heap dumps
• For example:
– Xdump:heap:file=/dumps/heapdump.%Y%m%d.%H%M%S.%pid.%seq.phd
specifies the location and format of the heap dump file name
– Xdump:heap, opts=PHD+CLASSIC enables heap dump creation and creates
the file in both binary and text format
– Xdump:heap:none disables heap dump creation
• Can also trigger heap dumps by using wsadmin Jython commands
– AdminControl.invoke(AdminControl.completeObjectName("type=J
VM, process=<server_name>,*"), "generateHeapDump")
Figure 11-34. Generating a JVM heap dump WA855 / VA8551.0
Notes:
IBM Support Assistant includes a tool for inspecting Java memory dumps, called the
Memory Analyzer. You can start it from the IBM Support Assistant workbench “tools” tab.
This tool can analyze several Java heap dump formats, including the standard dump
formats from both the IBM and Sun Java runtime environments, and also z/OS SVC
dumps. It lists and analyzes the data structures in the heap and their relationships, helping
you identify the structures that are most likely responsible for memory leakage.
V8.1
Student Notebook
Uempty
Hung thread detection

• Hung threads can be hard to diagnose
– They are often not noticed until many threads are hung, resulting in a
performance problem
• Application threads can hang for a number of reasons, which include:
– Endless loops
– Deadlocks
– Inaccessible resources
• The ThreadMonitor component monitors the web container, ORB, and
Async bean thread pools for hung threads
• Example thread monitor message
[8/1/11 10:51:01:955 EDT] 00000021 ThreadMonitor W

WSVR0605W: Thread "WebContainer : 0" (00000020) has been
active for 65103 milliseconds and may be hung. There is/are
1 thread(s) in total in the server that may be hung.
Figure 11-35. Hung thread detection WA855 / VA8551.0
Notes:
Application threads can hang for a number of reasons, including infinite loops or deadlocks.
A component that is known as the ThreadMonitor monitors the web container, ORB, and
Async bean thread pools for hung threads. The thread monitor does not try to deal with the
hung threads; it just issues notifications so that the administrator or developer can deal with
the issues.
When a hung thread is detected, three notifications are sent: a JMX notification is sent for
JMX listeners, PMI Thread Pool data is updated for tools like the Tivoli Performance
Viewer, and a message is written to the SystemOut log.
When the thread pool gives work to a thread, it notifies the thread monitor. The thread
monitor notes the thread ID and timestamp. The thread monitor compares active threads to
timestamps.
Threads that are active longer than the time limit are marked “potentially hung.”
Performance impact is minimal (less than 1%).

Student Notebook
Connection leak diagnostic messages

• Poorly written applications often do not properly release database
connections
– Forget to call connection.close()
– Most often in the exception case
– Connections must be closed in a finally{} block
• Orphaned connections return to the pool only after timeout

– Can cause a backup of new connections that are waiting for old connections to
timeout
– New connections that wait too long throw a
connectionWaitTimeoutException
• Connection manager is instrumented to print stack traces when a

connectionWaitTimeoutException occurs
– Enable by using trace string WAS.j2c=finest
Figure 11-36. Connection leak diagnostic messages WA855 / VA8551.0
Notes:
Applications can suffer from performance problems and even “hang” if they do not close
their connections properly. Not properly using the connection.close() method often
causes a leak. To ensure that connections are closed properly, they must be closed in a
finally{} block.
WebSphere eventually times out orphaned connections and returns them to the pool, but
for an application that makes frequent use of database connections, this timeout might not
be enough. New connections can get queued up waiting for the database while old
connections are waiting to be timed out. This behavior can halt the application, and you can
see connectionWaitExceptions.
The connection manager has lower performance impact than connection manager tracing.
When activated, it enables a connection manager wrapper that holds the stack trace of all
getConnection() calls in a throwable object. When an exception is thrown because of
waiting on a full connection pool, it is best to print stack traces of all open connections. This
action enables you to significantly narrow your search area when you look at the
application source code in an attempt to find the responsible code.
V8.1
Student Notebook
Uempty Connection leaks are difficult to diagnose because the error messages do not usually
provide enough specific information about the source of the problem. Usually a source
code review is needed to find points in the code where connections are not properly closed.
The connection manager makes this task much easier.

Student Notebook
Checking version levels and applying APARs

• The versionInfo command generates a report from data that is
extracted from XML files in the properties/version folder
– The report includes a list of changed components and installed or uninstalled
maintenance packages
• APAR: Authorized Program Analysis Report

– Tracks software defects that customers report
• Download suggested fixes, and fixes by version from the WebSphere

Support page
• IBM Installation Manager: new standard tool for installing fixes
Figure 11-37. Checking version levels and applying APARs WA855 / VA8551.0
Notes:
The versionInfo command generates a report from data that is extracted from XML files
in the properties/version folder. The report includes a list of changed components and
installed or uninstalled maintenance packages.
APAR is an Authorized Program Analysis Report; it tracks software defects that customers
report.
Download suggested fix packs for your version of the product from the WebSphere Support
website.
IBM Installation Manager is a new standard tool for installing fixes.
V8.1
Student Notebook
Uempty 11.3.Problem determination tools

Student Notebook
Problem determination
tools

Figure 11-38. Problem determination tools WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Problem determination tool availability

• Some tools are integrated into the administrative console
– Tivoli Performance Viewer
– Configuration validation
– Class loader viewer
– Others
• Some tools are separate programs that are shipped with WebSphere
Application Server itself, or shipped as separate products in their own
right
– dumpNameSpace
– versionInfo
• IBM Support Assistant:

– Serves as a central point from which many tools can be found and even run
directly inside IBM Support Assistant
Figure 11-39. Problem determination tool availability WA855 / VA8551.0
Notes:
In the overall process of problem determination, diagnostic data must be collected or
generated, and the data must be analyzed. Various tools are available to help you collect
and analyze diagnostic data for solving problems that are related to JVM, server and
application configuration, performance, and namespace issues.

Student Notebook
Problem determination tools: Administrative console

• Tivoli Performance Viewer and Performance Advisor
– Captures and analyzes statistical performance data from a running WebSphere
Application Server system
• Configuration validation
– Checks for errors in a WebSphere Application Server configuration
• Class Loader Viewer

– Provides a hierarchical view of class loaders that applications use
– Helps diagnose problems that are related to loading of classes in applications
• Diagnostic Provider
– Tool for viewing configuration and the current state of individual application
server components
Figure 11-40. Problem determination tools: Administrative console WA855 / VA8551.0
Notes:
The administrative console provides several tools that can be used for troubleshooting and
problem determination. See the WebSphere Application Server V8.5 Information Center for
more details about how to use these tools.
V8.1
Student Notebook
Uempty
Dumping the JNDI namespace

• The dumpNameSpace utility shows JNDI directory content
• Useful to ensure correct association of named objects:

– JDBC resources
– EJBs
– JMS resources
– Other resources
• Syntax and some of the options:

<was_root>\bin\dumpNameSpace
[-host bootstrap_host_name (defaults to localhost)]
[-port bootstrap_port_number (defaults to 2809)]
[-startAt subcontext/in/the/tree]
• Output can be redirected to a file and inspected
Figure 11-41. Dumping the JNDI namespace WA855 / VA8551.0
Notes:
Usage: dumpNameSpace [-keyword value]
If a keyword occurs more than one time with different values, the value that is associated
with the last occurrence is used.
The keywords and associated values are:
• -host myhost.austin.ibm.com: Bootstrap host; it is the WebSphere host whose
namespace you want to dump. It defaults to “localhost.”
• -port nnn: Bootstrap port, defaults to 2809.
• -factory com.ibm.websphere.naming.WsnInitialContextFactory: The initial
context factory that is going to be used to get the JNDI initial context. It defaults as
shown, and normally is not required to be changed.
-root [cell | server | node | host | legacy | tree | default]

Student Notebook
V8.1
Student Notebook
Uempty 11.4.IBM Support Assistant

Student Notebook
IBM Support Assistant

Figure 11-42. IBM Support Assistant WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is the IBM Support Assistant?

• The IBM Support Assistant workbench is a free, stand-alone
application that is installed on any workstation
• It can also be enhanced by installing plug-in modules for the IBM

products you use
– The IBM Support Assistant workbench is supported on Windows and Linux
– The IBM Support Assistant Agent manager and Assistant agent must be
configured to support other platforms such as AIX and Solaris
• Benefits of IBM Support Assistant include:

– Saves time in searching product, support, and educational resources
– Helps with opening a problem management report (PMR)
– Allows for easy location and installation of useful product support tools by
using a support tool framework
– Easily downloaded from
http://www.ibm.com/software/support/isa/
Figure 11-43. What is the IBM Support Assistant? WA855 / VA8551.0
Notes:
The IBM Support Assistant is a free, stand-alone application that is installed on any
workstation. It can also be enhanced by installing plug-in modules for the IBM products you
use.
Benefits of IBM Support Assistant include:
• Improves your ability to locate IBM support, development, and educational information
through a federated search interface (one search: multiple resources).
• Provides quick access to the IBM Education Assistant and key product education
roadmaps.
• Simplifies access to IBM product home pages, product support pages, and product
forums or newsgroups, through convenient links.
• Saves time in submitting problems to IBM Support by collecting key information, then
electronically creating a problem management record (PMR) from within IBM Support
Assistant. If a PMR must be opened, IBM Support Assistant helps with:
- Gathering support information that is based on problem type

Student Notebook
- Creating and updating the problem report

- Tracking your electronic problem report
• Includes a support tool framework, allowing for the easy installation of support tools that
are associated with different IBM products.
• Provides a framework for IBM software products to deliver customized self-help
information into the different tools within it. Customize your IBM Support Assistant client
by using the built-in update capability to find and install new product features or support
tools.
V8.1
Student Notebook
Uempty
IBM Support Assistant workbench home page
Figure 11-44. IBM Support Assistant workbench home page WA855 / VA8551.0
Notes:
Follow these steps to download and install IBM Support Assistant:
1. Go to http://www.ibm.com/software/support/isa/ and choose IBM Support
Assistant V4. Download the installation package for any platform where you want to
install IBM Support Assistant.
2. Log in with your IBM web identity (the same ID as used for MySupport and
developerWorks).
3. If you do not already have an IBM web identity, complete the free registration process to
obtain one.
4. Download the compressed archive files with the web service proxy.
5. Use a tool such as WinZip to extract the archive file in a temporary directory.
6. The archive contains an installer program and the Installation and troubleshooting
guide. Follow the directions in the Installation and troubleshooting guide to install IBM
Support Assistant.

Student Notebook
IBM Support Assistant: Search component

• Find Information > Search Information
• Allows searching multiple information locations concurrently,

including:
– Technical notes from the IBM software support website
– Topics from IBM developerWorks
– Postings from IBM newsgroups and forums
– Google web search
– Online information centers
• You can also narrow your search by selecting specific IBM software
products and versions
Figure 11-45. IBM Support Assistant: Search component WA855 / VA8551.0
Notes:
Search options are provided to help you narrow the scope of your search. The search
location that you choose determines what search options are available. For example, if you
select Google web search, search options do not apply. The IBM developerWorks and IBM
Newsgroups and Forums search locations allow you to narrow your search to specific
product areas.
• The IBM Software Support Documents search location offers the most options. You
can select specific products and versions, and you can select specific types of
documents.
• The online information centers are available only for products that enable this feature.
Not all products have an information center to search.
• The product information component helps you quickly find helpful IBM websites.
• With product information links, you can access support, troubleshooting, and
educational options, including traditional classes, web-based training, CD-ROM
training, and certification.
V8.1
Student Notebook
Uempty • Select a link, depending on what type of product information you are looking for.
• Select the Product home page to find introductory information, with descriptions of
features, benefits, and requirements. You can also find links to product literature,
events, news, and success stories.
• Select the Product Support page to search IBM software support documents that
pertain to your product. This page also provides links to support resources such as My
Support, Passport Advantage, and support news flashes.
• Select Product Forums to see and contribute to product discussions.
• Select the Skills Enhancement links to see education-related documents for your
product.
• Select the troubleshooting links to see product-specific troubleshooting information.

Student Notebook
IBM Support Assistant: Tools component

• Select Analyze Problem > Tools
– Provides support tools to identify and troubleshoot problems
• Configuration tools
– Port Scanning Tool: scan system for active and configured ports
– Visual Configuration Explorer: visualize, explore, and analyze configuration
information from diverse sources
– Others
• JVM-based tools
– Thread and Monitor Dump Analyzer: analyze javacore files
– Garbage Collector and Memory Visualizer: analyze verbose GC logs
– Memory Analyzer: analyze heap dumps for leak suspects
– Java Health Center: monitor active JVMs with minimal effect on performance
– Others
Figure 11-46. IBM Support Assistant: Tools component WA855 / VA8551.0
Notes:
The tools component is a way to provide support tools to you. These tools can be used
diagnostically to identify problems you are having. Some tools can also be used as a
preventive measure to stop a problem before it occurs.
This component provides a way to use support-related tools to identify problems or
health-checking tools to prevent problems. The Updater component of IBM Support
Assistant is used to install tools. A tool is started in a new window by clicking its name.
V8.1
Student Notebook
Uempty
IBM Support Assistant: Collect Data component

• Select Analyze Problem > Collect Data
– Provides data collectors for many different problems
– Interactive collection process
• System collectors
– Collect system data information
– Collect network information
– Collect software inventory
– Others
• WebSphere Application Server collectors

– Security
– Connectors
– Containers
– JDK
– Runtime
– Others
Figure 11-47. IBM Support Assistant: Collect Data component WA855 / VA8551.0
Notes:
Collecting data is optional, but proactive collection of diagnostic data can help you
troubleshoot problems with IBM software and help IBM resolve your service requests
faster. If you are troubleshooting a problem on your own or intend to submit a service
request, collect data first. You can store the collected data in a case (a placeholder for all
the items that are related to a particular issue) in the Case Manager. Using a case helps to
organize your problem determination (PD) efforts and allows you to send it to IBM when
you create a service request.

Student Notebook
IBM Support Assistant: Collect and send data

• Select collect data
– Local collection with IBM Support Assistant Workbench
– Remote collection with IBM Support Assistant Lite
– Remote collection with agents
• Select service request

– Open a new service request
– Review or update service requests
Figure 11-48. IBM Support Assistant: Collect and send data WA855 / VA8551.0
Notes:
Collect data:
Collecting data is an important part of submitting a problem report because IBM can use it
to resolve your problem report more quickly.
When you click Collect Data, you are asked to select the product for which you would like
to collect data. You are prompted to select a problem type as well.
Depending on the product you select, you might be asked for other information. When you
select a product and provide the required information, click Collect.
For most problem types, IBM Support Assistant collects data for the product you select and
stores it in a JAR file. For some problem types, the information that is collected results in a
report file or a simple message to the user. You can collect data for more than one product
at a time if you want.
Manage problem reports:
To manage problem reports, you must log in. After you are logged in, you can:
V8.1
Student Notebook
Uempty • Open a new problem report

• View existing problem reports
• Attach a file to a new or existing problem report
To log in, you must provide your IBM ID, password, IBM customer number, and country.
The login process also verifies that you have an IBM service contract and that your ID is on
the Authorized Callers list.
After you log in, the service component shows you any problem reports that you submitted.
You can see these problem reports at any time by clicking List Problem Reports.

Student Notebook
IBM Support Assistant 5.0 Beta

• The new IBM Support Assistant 5.0 Beta provides a web browser-
based version of the problem determination platform
Figure 11-49. IBM Support Assistant 5.0 Beta WA855 / VA8551.0
Notes:
Download IBM Support Assistant 5.0 Beta from:
http://www.ibm.com/software/support/isa
In this Beta release, new problem determination tools are included, and the number of tools
will continue to grow in future releases. Report-generating tools from the technology
preview, along with the new addition of Desktop tools (by using Java Webstart) and
web-based tools, include the following tools:
• Garbage Collection and Memory Visualizer (GCMV) [desktop]
• Garbage Collection and Memory Visualizer (GCMV) [report]
• Health Center
• Memory Analyzer [desktop]
• Memory Analyzer [report]
• Memory Analyzer Web Edition [web]
• Pattern Modeling and Analysis tool for Java Garbage Collector (PMAT)
V8.1
Student Notebook
Uempty • Portal Log Analyzer

• Profile Port Checker
• Thread and Monitor Dump Analyzer (TMDA) [desktop]
• Thread and Monitor Dump Analyzer (TMDA) [report]
• WebSphere Application Server Configuration Visualizer
To learn more about the tools in this release, select the Help link in the IBM Support
Assistant UI to access the new information center documentation.

Student Notebook
IBM Support Assistant 5.0 Beta: New features

• New and improved features:
– Reports view: Provide a quick, concise view into all reports that are generated
from the execution of a report generator analysis tool
– Information center: Expanded documentation for IBM Support Assistant and
Tools and now built into the application
– Desktop tools: Desktop tools can be started by using the IBM Support
Assistant browser UI (Note: requires a Java plug-in in your browser)
– Web-based tools: Rich UI tools run in your browser while the heavier processing
of diagnostic files is offloaded to the IBM Support Assistant server
• Multiple installation and deployment options:
– EAR deployment: New easy deployment of an EAR file to your existing
– Extract and go: Simple installation by extracting a download package and
starting IBM Support Assistant. This new embedded server (Liberty profile) has a
fast startup time, fast page load, and small footprint
Figure 11-50. IBM Support Assistant 5.0 Beta: New features WA855 / VA8551.0
Notes:
IBM Support Assistant is provided with two deployment options to meet your needs:
• If you have an existing WebSphere Application Server, you can install IBM Support
Assistant as an enterprise application (EAR) module. Tools are provided as Java
Platform, Enterprise Edition web modules.
• IBM Support Assistant 5.0 Beta is also provided with an embedded server if you are
looking for an all-in-one package that allows you to extract and go.
V8.1
Student Notebook
Uempty
Using the IBM Support Assistant Data Collector (1 of 2)

• The IBM Support Assistant Data Collector for WebSphere Application
Server is a tool for gathering diagnostic data from an application server
– It replaces the collector tool, which is deprecated
• Also provides symptom analysis support for the various categories of
problems
• The tool runs in console mode by starting the launch script from the
command line
• In a Windows environment, run the
<profile_root>/bin/isadc.bat command
• In a Linux, AIX, HP-UX, Solaris, IBM i, or zOS environment, run the
<profile_root>/bin/isadc.sh command
Figure 11-51. Using the IBM Support Assistant Data Collector (1 of 2) WA855 / VA8551.0
Notes:
The IBM Support Assistant Data Collector for WebSphere Application Server tool focuses
on automatic collection of problem data. It also provides symptom analysis support for the
various categories of problems that IBM software products encounter. Information pertinent
to a type of problem is collected to help identify the origin of the problem under
investigation. The tool assists customers by reducing the amount of time it takes to
reproduce a problem with the correct RAS tracing levels set. Also, the tool helps customers
by reducing the effort that is required to send the appropriate log information to IBM
Support.

Student Notebook
Using the IBM Support Assistant Data Collector (2 of 2)
Figure 11-52. Using the IBM Support Assistant Data Collector (2 of 2) WA855 / VA8551.0
Notes:
Run the IBM Support Assistant Data Collector tool with the user ID for which you
configured your WebSphere Server instance. Depending on what collection you are
running, you are asked for more information to complete the data collection activities. A
script might ask for more configuration information, information about the sequence of
events that leads up to the problem you are dealing with, or your preferences about how it
completes the collection. At each step, the choices are presented as numbered lists, and
you input the number of your selection and press the Enter key. When input is required,
prompts are displayed at which you enter your response and press the Enter key. You can
find collection details for each WebSphere Application Server problem type in its
corresponding MustGather documents.
V8.1
Student Notebook
Uempty
Unit summary
• Enable high performance extensible logging (HPEL) and use the Log
Viewer
Notes:

Student Notebook
1. What are the two approaches for problem determination?
2. In basic mode logging, what are the two types of JVM log files, and
what data do they contain?
3. What are the three levels of diagnostic trace detail?
4. What are the three major features of the IBM Support Assistant that
are accessible from the Welcome screen?
5. What are some JVM-related problems that a server can experience?
Notes:
1. 
2. 
3. 
4. 
5.



V8.1
Student Notebook
Uempty
Checkpoint answers
1. What are the two approaches for problem determination?
– Analysis and isolation
2. In basic mode logging, what are the two types of JVM log files, and
what data do they contain?
– The SystemOut.log file contains messages from different server
components. Mostly informational, these messages log events that occur
during the lifetime of the JVM. The SystemErr.log file contains any
exceptions and stack traces that server components throw.
3. What are the three levels of diagnostic trace detail?

– Fine, finer, and finest
4. What are the three major features of the IBM Support Assistant that
are accessible from the Welcome screen?
– Find Information, Analyze Problem, Collect, and Send Data
5. What are some JVM-related problems that a server can experience?

– Hung threads, OutOfMemory conditions, connect leaks
Notes:

Student Notebook
Exercise 7
Problem determination

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Use the administrative console to configure and view log data
• Enable a server to use HPEL
• Enable tracing on application server components
• Use the HPEL Log Viewer to examine log and trace data
• Enable verbose garbage collection for an application server
• Enable memory leak detection for an application server
• Describe how IBM Support Assistant tools can be used to analyze JVM
memory dumps
Notes:

Student Notebook
V8.1
Student Notebook
Uempty Unit 12. Introduction to wsadmin and scripting

This unit introduces you to the capabilities of wsadmin as an
administrative tool for WebSphere Application Server.

• Use wsadmin to enter administrative commands
• Create Jython scripts to run wsadmin commands
• Customize the wsadmin environment with profiles and property
files
• Use property file based configurations to modify an environment
• Use IBM Assembly and Deploy Tools for WebSphere
Administration to edit and debug Jython scripts
• Configure and use command assist to develop wsadmin scripts

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 12. Introduction to wsadmin and scripting 12-1
Student Notebook
Unit objectives
• Customize the wsadmin environment with profiles and property files
• Use IBM Assembly and Deploy Tools for WebSphere Administration
to edit and debug Jython scripts
Notes:
V8.1
Student Notebook
Uempty
wsadmin versus administration console
Command-line Web-based
C:\> wsadmin administrative
console
Admin
Admin application
Jython or Jacl services
script Read
Write
Configuration
Application server (XML files)
Figure 12-2. wsadmin versus administration console WA855 / VA8551.0
Notes:
You can use the administrative console or wsadmin tool to manage an application server
and the configuration, application deployment, and server runtime operations.
The administrative console is a graphical interface that allows you to manage your
applications and do system administration tasks for your WebSphere Application Server
environment. The administrative console runs in your web browser.
The wsadmin tool is a command-line client that runs Jython or Jacl scripts that allow you to
manage your applications and do system administration tasks for your WebSphere
Application Server environment.
Your actions that use the administrative console or wsadmin can access (read) and modify
(write) a set of XML configuration files that are used to describe the application server
environment.
Student Notebook
Scripting benefits
• Automation of routine administration tasks
• Schedule administration tasks
• Support changes in production environments, especially with

multiple nodes
• Apply configuration changes or updates to targeted resources in an

efficient and consistent manner
• Safer than the administrative console in production environments
Figure 12-3. Scripting benefits WA855 / VA8551.0
Notes:
There are several benefits for using scripting to manage an application server and the
configuration, application deployment, and server runtime operations:
• Automation of routine administration tasks without relying on an operator to run the
• Schedule administration tasks to run at times when it might be inconvenient to have an
operator to run the administrative console
• Support changes in production environments, especially with multiple nodes
• Apply configuration changes and updates to all targeted resources in an efficient and
consistent manner
Using wsadmin is safer than using the administrative console in production environments.
V8.1
Student Notebook
Uempty
wsadmin
• Provides:
– Scripting capabilities
– Command-line administration
• Support for:
– Python commands through Jython
– Tcl commands through Java Command Language (Jacl)
• Modes:
– Interactive
– Command-line
– Script file
• Examples:
– Start and stop deployment manager, nodes, application servers, enterprise
applications, and clusters
– Configure virtual hosts, JDBC providers, JMS resources
– Create application servers
– Create clusters and add members to a cluster
Figure 12-4. wsadmin WA855 / VA8551.0
Notes:
The WebSphere administrative (wsadmin) scripting program is a powerful, non-graphical
command interpreter environment, enabling you to run administrative operations in a
scripting language. The wsadmin tool is intended for production environments and
unattended operations. The wsadmin tool provides:
• Scripting capabilities
• Command-line administration
The wsadmin tool uses the Bean Scripting Framework (BSF), which supports various
scripting languages to configure and control your WebSphere Application Server
installation. The wsadmin tool provides support for:
• Python commands through Jython
• Tcl commands through Java Command Language (Jacl)
The wsadmin launcher makes administrative objects available through language-specific
interfaces. Scripts use these objects for application management, configuration,
Student Notebook
operational control, and communication with MBeans running in WebSphere server

processes. Three modes are used to start wsadmin:
• Interactive
• Command line
• Script file
You can use the wsadmin tool to do the same tasks that you can use the administrative
console for. You can use the wsadmin tool to manage a WebSphere Application Server V8
installation. Examples of tasks include:
• Start and stop deployment manager, nodes, application servers, enterprise
applications, and clusters
• Configure virtual hosts, JDBC providers, JMS resources
• Create application servers
• Create clusters and add members to a cluster
V8.1
Student Notebook
Uempty
wsadmin invocation options

• wsadmin invocation options include:
wsadmin
-h (help) or -?
-c <command>
-f <script_file_name>
-p <properties_file_name>
-profile <profile_script_name>
-profileName <profile_name>
-lang
-conntype [SOAP | RMI | JSR160RMI | IPC | NONE ]
-host
-user or username
-password
-port
Figure 12-5. wsadmin invocation options WA855 / VA8551.0
Notes:
There are several wsadmin invocation options available. Use the following command-line
invocation syntax for the wsadmin scripting client:
• -h, -help, -? 
Provides syntax help.
• -c <command> 
Specifies to run a single command. Multiple -c options can exist on the command line.
They run in the order that you designate. If you start the wsadmin tool with the -c
option, any changes that you make to the configuration are saved automatically.
• -f <script_file_name> 
Specifies a script to run. Only one -f option can exist on the command line. You can
use the -f option to run scripts that contain nested Jython scripts. The second level is
the user default, wsadmin.properties, which is in your home directory.
• -p <properties_file_name> 
Specifies a properties file. The file that is listed after -p represents a Java properties
Student Notebook
file that the scripting process reads. Three levels of default properties files load before
the properties file that you specify on the command line.
- The first level is the installation default, wsadmin.properties, which is in the
product properties directory.
- The second level is the user default, wsadmin.properties, which is in your home
directory.
- The third level is the properties file that the environment variable
WSADMIN_PROPERTIES references.
Multiple -p options can exist on the command line. Those options start in the order that
you supply them.
• -profile <profile_script_name> 
Specifies a profile script. The profile script runs before other commands, or scripts. If
you specify -c, then the profile script runs before it starts this command. If you specify
-f, then the profile script runs before it runs the script. In interactive mode, you can use
the profile script to do any standard initialization that you want.
You can specify multiple-profile options on the command line, and they start in the order
that you supply them.
• -profileName <profile_name> 
Specifies the profile from which the wsadmin tool runs. Specify this option if one of the
following reasons applies:
- You run the wsadmin tool from the <was_root>/bin directory, and you do not have
a default profile, or you want to run in a profile other than the default profile.
- You are currently in a profile bin directory but want to run the wsadmin tool from a
different profile.
• -lang 
Specifies the language of the script file, the command, or an interactive shell. The
possible languages include Jacl and Jython. The options for the -lang argument
include jacl and jython.
This option overrides language determinations that are based on a script file name, a
profile script file name, or the com.ibm.ws.scripting.defaultLang property. The
-lang argument has no default value.
If you do not specify the -lang argument but you have the -f <script_file_name>
argument, then the wsadmin tool determines the language, which is based on a target
script file name. If you do not specify the -lang argument and the -f argument, the
wsadmin tool determines the language, which is based on a profile script file name if the
-profile <profile_script_name> argument is specified. If the command line or the
property does not supply the script language, and the wsadmin tool cannot determine it,
then an error message is generated.
V8.1
Student Notebook
Uempty • -conntype 
Specifies the type of connection to use. This argument consists of a string that
determines the type – for example, SOAP – and the options that are specific to that
connection type. Possible types include:
SOAP
RMI
JSR160RMI
IPC
NONE
For each connection type, you can specify more attributes about the connection.
An example of when NONE can be used is when the application server configuration
files are so corrupted that the application server cannot be started to access the
administrative tasks of the running server.
• -host 
Specifies a host name to which wsadmin attempts to connect. The default
wsadmin.properties file that is in the properties directory of each profile provides
localhost as the value of the host property, if this option is not specified.
• -user or -username 
Specifies a user name that the connector uses to connect to the server if security is
enabled in the server.
• -password 
Specifies a password that the connector uses to connect to the server, if security is
enabled in the server.
• -port 
Specifies a port that the connector uses. The default wsadmin.properties file that is
in the properties directory of each application server profile provides a value in the port
property to connect to the local server.
Student Notebook
Jython versus Jacl

• Jython syntax is more natural to Java or C programmers
• Jython provides much better support in tools

–Rational Application Developer (Jython editor, command completion, debugger)
–WebSphere Administrative console (console command assistance)
• Jacl syntax is more familiar to administrators familiar with Tcl
• Jacl is supported in version 8

–No future development or enhancements for Jacl
–Jacl-to-Jython (Jacl2Jython) conversion assist tool is available
Figure 12-6. Jython versus Jacl WA855 / VA8551.0
Notes:
The wsadmin tool supports Jython and Jacl scripting languages.
• Jython scripting language: Jython is an alternative implementation of Python, and is
written entirely in Java.
- The wsadmin tool uses Jython V2.1.
- Jython syntax might seem more natural to Java or C programmers.
- Future investment and strategic direction focus on the Jython language. Jython has
much better support for tools:
• IBM Assembly and Deploy Tool (Jython editor, command completion, debugger)
• Administrative console (console command assistance)
- The product uses a Jython version that does not support Microsoft Windows 2003 or
Windows Vista operating systems.
• Jacl scripting language: Jacl is an alternative implementation of Tcl, and is written
entirely in Java code.
V8.1
Student Notebook
Uempty - The wsadmin tool uses Jacl V1.3.2.

- Jacl might seem more familiar to administrators familiar with Tcl.
- The Jacl language is stabilized in WebSphere Application Server V7.
Jacl-to-Jython (Jacl2Jython) is a conversion utility that converts Jacl syntax wsadmin
scripts into equivalent Jython syntax wsadmin scripts.
Student Notebook
Administrative functions that use wsadmin

• WebSphere Application Server system management separates
administrative functions into three categories:
1 Running objects in WebSphere Application Server installations
–
Node01
server1
Deployment
Node agent
manager
server2
2 Configuration of
Cell config
Server installations Node01 config
(repository) Configuration repository
server1 config
server2 config
3 Installed Applications
EAR files installedApps directory
Figure 12-7. Administrative functions that use wsadmin WA855 / VA8551.0
Notes:
WebSphere Application Server system management separates administration functions
into two categories:
• Running objects in WebSphere Application Server installations: The wsadmin tool
can be used to install, uninstall, and manage applications. There are two methods you
can use to install, uninstall, and manage applications.
- You can use the commands for the AdminApp and AdminControl objects to start
operations on your application configuration.
- Alternatively, you can use the AdminApplication and BLAManagement Jython
script libraries to do specific operations to configure your enterprise and
business-level applications.
• Configuration of WebSphere Application Server installations (repository): The
wsadmin tool can be used to configure application servers in your environment.
V8.1
Student Notebook
Uempty - You can use the commands for the AdminConfig and AdminTask objects to
retrieve configuration IDs and start operations on the objects to configure the
application server.
- Alternatively, you can use the script library for specific operations to configure your
application servers.
An application server configuration provides settings that control how an application
server provides services for running applications and their components.
Configuration data is stored in several different XML files, which the server runtime
reads when it starts and responds to the component settings stored there. The
configuration data includes the settings for the runtime, such as Java virtual machine
(JVM) options, thread pool sizes, container settings, and port numbers the server uses.
Other configuration files define Java Platform, Enterprise Edition resources to which the
server connects to obtain data that the application logic needs.
Security settings are stored in a separate document from the server and resource
configuration. Application-specific configurations, such as deployment target lists,
session configuration, and cache settings, are stored in files under the root directory of
each application. When viewing the XML data in the configuration files, you can discern
the relationship between the configuration objects.
For information about the WebSphere Application Server configuration objects, view the
HTML tables in the <was_root>/web/configDocs directory. There are several
subdirectories, one for each configuration package in the model. The index.html file
ties all of the individual configuration packages together in a top-level navigation tree.
Each configuration package lists the supported configuration classes, and each
configuration class lists all of the supported properties. The properties with names that
end with the @ character imply that property is a reference to a different configuration
object within the configuration data. The properties with names that end with the *
character imply that the property is a list of other configuration objects.
Student Notebook
Administrative objects in wsadmin

AdminApp
AdminConfig
Scripts wsadmin AdminControl
AdminTask
Resources
Help
• Five administrative objects perform different operations:

– AdminControl: work with “live” running objects
– AdminConfig: create or modify WebSphere Application Server “static”
configuration
– AdminApp: install, modify, or administer applications
– AdminTask: administrative commands that are more usable and task-oriented
– Help: obtain general help
Figure 12-8. Administrative objects in wsadmin WA855 / VA8551.0
Notes:
The wsadmin tool acts as an interface to Java objects by way of scripts to access
resources. The tool uses the same interface (through JMX) as the administrative console to
make configuration changes and control servers.
Five objects are available when you use scripts:
• AdminControl: Use AdminControl to run operational commands, work with “live”
running objects, and do traces or data type conversions.
• AdminConfig: Use AdminConfig to run configuration commands to create or modify
WebSphere Application Server “static” configurational elements.
• AdminApp: Use AdminApp to install, modify, or administer applications.
• AdminTask: Use AdminTask to run administrative commands that are easier to use
and more task-oriented.
• Help: Use Help to obtain general help.
V8.1
Student Notebook
Uempty
Starting wsadmin
• Interactively wsadmin
• Command option wsadmin –c <command>
• Script file wsadmin –f <script_file>
Figure 12-9. Starting wsadmin WA855 / VA8551.0
Notes:
The wsadmin tool can be started in three ways:
• Interactively: wsadmin 
Run wsadmin with an option other than -f or -c or without an option. The wsadmin
tool starts and provides an interactive shell with a wsadmin prompt. From the wsadmin
prompt, enter any Jacl or Jython command. You can also use the AdminControl,
AdminApp, AdminConfig, AdminTask, or Help wsadmin objects to start commands. To
leave an interactive scripting session, use the quit or exit command. The graphic
demonstrates wsadmin in an interactive mode:
<was_root>\profiles\profile1\bin\wsadmin
• Command option: wsadmin -c <command> 
Run the wsadmin tool with the noninteractive -c option. The graphic demonstrates
Student Notebook
wsadmin by using the command option to run the list command for the AdminApp object
that uses Jython.
<was_root>\profiles\profile1\bin\wsadmin -c print(AdminApp.list()) -lang
jython
• Script file: wsadmin -f <script_file> 
Run the wsadmin tool with the noninteractive -f option, and place the commands that
you want to run into a script file. The graphic demonstrates wsadmin by using the script
file option to run a Jython script.
<was_root>\profiles\profile1\bin\wsadmin -f c:\Program Files\IBM\
WebSphere\AppServer\profiles\profile1\bin\initialSIBSetup.jy
When running wsadmin with the -f option, you are not required to specify the script
language with the -lang command-line option. The wsadmin command recognizes
the script language by looking at the extension of the file name (.py for Jython and
.jacl for Jacl).
V8.1
Student Notebook
Uempty
Starting wsadmin with security enabled

• If security is enabled, authentication information must be supplied
• There are several ways to provide authentication information:
– Prompted
– Command-line parameters
– RMI connections: sas.client.props file

– SOAP connections: soap.client.props file
Figure 12-10. Starting wsadmin with security enabled WA855 / VA8551.0
Notes:
WebSphere Application Server console security is enabled by default.
• If security is enabled, authentication information must be supplied.
• There are several ways to provide authentication information:
- Prompted:
If security is enabled and you do not provide credentials when you start wsadmin,
you are prompted to provide them. The Login at the Target Server window opens.
Two fields, User Identity and User Password, must be entered with valid
credentials before proceeding.
- Command-line parameters:
You can use command-line parameters to pass authentication credentials.
• -user or -username can be used interchangeably to provide a user ID.
• -password is used to provide a password.
Student Notebook
The graphic demonstrates the use of command-line parameters to pass

authentication credentials:
<was_root>\profiles\profile1\bin\wsadmin -user USERID -password
PASSWORD
- RMI connections: sas.client.props file
For RMI connections, authentication credentials can be provided in the
sas.client.props file. The file is in the profile properties directory: 
<was_root>\profiles\<profile_name>\properties\
The authentication parameters are:
• com.ibm.CORBA.loginUserid
• com.ibm.CORBA.loginPassword 
- SOAP connections: soap.client.props file

For SOAP connections, authentication credentials can be provided in the
soap.client.props file. The file is in the profile properties directory: 
<was_root>\profiles\<profile_name>\properties\
The authentication parameters are:
• com.ibm.SOAP.loginUserid
• com.ibm.SOAP.loginPassword 
V8.1
Student Notebook
Uempty
wsadmin properties
• Certain default behaviors for wsadmin can be changed by editing:
<profile_root>\<profile_name>\properties\wsadmin.properties
• Examples of properties include:

–– com.ibm.ws.scripting.connectionType=SOAP
com.ibm.ws.scripting.connectionType=SOAP
–– com.ibm.ws.scripting.port=8880
com.ibm.ws.scripting.port=8880
–– com.ibm.ws.scripting.host=localhost
com.ibm.ws.scripting.host=localhost
–– com.ibm.ws.scripting.defaultLang=jython
com.ibm.ws.scripting.defaultLang=jython
–– com.ibm.ws.scripting.traceFile=
com.ibm.ws.scripting.traceFile=
–– com.ibm.ws.scripting.validationOutput=
com.ibm.ws.scripting.validationOutput=
–– com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
–– com.ibm.ws.scripting.profiles=
com.ibm.ws.scripting.profiles=
–– com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy=true
com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy=true
–– com.ibm.ws.scripting.tempdir=
com.ibm.ws.scripting.tempdir=
–– com.ibm.ws.scripting.validationLevel=
com.ibm.ws.scripting.validationLevel=
–– com.ibm.ws.scripting.crossDocumentValidationEnabled=
com.ibm.ws.scripting.crossDocumentValidationEnabled=
–– com.ibm.ws.scripting.classpath=
com.ibm.ws.scripting.classpath=
Figure 12-11. wsadmin properties WA855 / VA8551.0
Notes:
Scripting administration uses several Java properties files. Properties files can be used to
control your system configurations. Before any properties file is specified on the command
line, three levels of default properties files are loaded. These properties files include:
• Installation default file: The first level represents an installation default, which is in the
profile_root/properties directory for each application server profile called
wsadmin.properties.
• User default file: The second level represents a user default, and is in the Java
user.home property. This properties file is also called wsadmin.properties.
• Properties file: The third level is a properties file that is pointed to by the
WSADMIN_PROPERTIES environment variable. This environment variable is defined in the
environment where the wsadmin tool starts.
If one or more of these properties files are present, they are interpreted before any
properties file that is present on the command line. The three levels of properties files load
Student Notebook
in the order that they are specified. The properties file that is loaded last overrides the ones
that are loaded earlier.
Certain default behaviors for wsadmin can be changed by editing:
<profile_root>\<profile_name>\properties\wsadmin.properties
Examples of properties include:
• com.ibm.com.ws.scripting.connectionType=SOAP 
Determines the connector to use. This value can either be SOAP, JSR160RMI, RMI, IPC,
or NONE. The wsadmin.properties file specifies SOAP as the connector.
• com.ibm.com.ws.scripting.port=8880 
Specifies the port to use when attempting a connection. The wsadmin.properties file
specifies 8879 as the SOAP port for a single server installation.
• com.ibm.com.ws.scripting.host=localhost 
Determines the host to use when attempting a connection. If not specified, the default is
the local host.
• com.ibm.com.ws.scripting.defaultLang=jython 
Indicates the language to use when running scripts. The wsadmin.properties file
specifies Jacl as the scripting language. The supported scripting languages are Jacl
and Jython.
If you change this value to Jython, some WebSphere Application Server scripts that
depend on the default language of Jacl fail unless rewritten to call wsadmin with the
-lang jacl command-line option.
• com.ibm.com.ws.scripting.traceFile= 
Determines where trace and log output is directed. The wsadmin.properties file
specifies the wsadmin.traceout file that is in the <profile_root>/logs directory of
each application server profile as the value of this property.
• com.ibm.com.ws.scripting.validationOutput= 
Determines where the validation reports are directed. The default file is
wsadmin.valout, which is in the <profile_root>/logs directory of each application
server profile.
• com.ibm.com.ws.scripting.traceString=com.ibm.*=all=enabled 
Turns on tracing for the scripting process. The default has tracing turned off.
• com.ibm.com.ws.scripting.profiles= 
Specifies a list of profile scripts to run automatically before running user commands,
scripts, or an interactive shell.
• com.ibm.com.ws.scripting.emitWarningForCustomSecurityPolicy=true 
Controls whether the WASX7207W message is emitted when custom permissions are
found. The possible values are true and false. The default value is true.
V8.1
Student Notebook
Uempty • com.ibm.com.ws.scripting.tempdir= 
Determines the directory to use for temporary files when installing applications. The
Java virtual machine (JVM) API uses java.io.temp as the default value.
• com.ibm.com.ws.scripting.validationLevel= 
Determines the level of validation to use when configuration changes are made from
the scripting interface. Possible values are: NONE, LOW, MEDIUM, HIGH, and HIGHEST.
The default is HIGHEST.
• com.ibm.com.ws.scripting.crossDocumentValidationEnabled= 
Determines whether the validation mechanism examines other documents when
changes are made to one document. Possible values are true and false. The default
value is true.
• com.ibm.com.ws.scripting.classpath= 
Searches for classes and resources, and is appended to the list of paths.
Student Notebook
Profile scripts
• Profile scripts can be used to preload wsadmin with predefined settings
and functions
• Run during wsadmin startup
• Either of the following can call a profile script:
– Using the –profile option on the command line
– Defined in wsadmin.properties com.ibm.ws.scripting.profiles=
Figure 12-12. Profile scripts WA855 / VA8551.0
Notes:
Profile scripts can be used to preload wsadmin with predefined settings and functions.
Profile scripts are run during wsadmin startup. They can be called in one of two ways:
• Use the -profile option on the command line.
• Use the com.ibm.ws.scripting.profiles= property to define the profile script in
wsadmin.properties.
The profile script runs before other commands, or scripts. If you specify -c, then the profile
script runs before it starts this command. If you specify -f, then the profile script runs
before it runs the script. In interactive mode, you can use the profile script to do any
standard initialization that you want.
You can specify multiple -profile options on the command line, and they start in the
order that you supply them.
V8.1
Student Notebook
Uempty The graphic example identifies a Jython script named global_profile.py with the
following syntax:
#-----------------------------------------------
# Print whereAMI
#-----------------------------------------------
def whereAMI():
#Print cell and node names
print "Cell: " + AdminConfig.showAttribute(AdminConfig.list("Cell"), "name")
print "Node: " + AdminConfig.showAttribute(AdminConfig.list("Node"), "name")
return
#-----------------------------------------------
# Start of main
#-----------------------------------------------
print ""
print "Hello, and welcome to wsadmin using jython"
print ""
print "Running global_profile.py Global definitions and settings could be
added"
print "here. It would also be possible to extend wsadmin by defining new"
print "customized commands and procedures."
print ""
whereAMI()
print ""
The following example output demonstrates that wsadmin started by using the -profile
option to run the global_profile.py script:
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile1\bin\wsadmin
-profile c:\software\wsadmin\global_profile.py
WASX7209I: Connected to process "server1" on node was7host01Node01 using
SOAP connector; The type of process is: UnManagedProcess
Hello, and welcome to wsadmin using jython
Running global_profile.py Global definitions and settings could be added
here. It would also be possible to extend wsadmin by defining new
customized commands and procedures.
Cell: was7host01Node01Cell
Node: was7host01Node01
WASX7031I: For help, enter: "print Help.help()"
Student Notebook
AdminConfig: Managing configurations

• Management configuration scripts use the AdminConfig object to
access the repository where configuration information is stored
• Example:
wsadmin> AdminConfig.list
wsadmin> AdminConfig.list ('Server')
('Server')
'server(cells/was8host01Node01Cell/nodes/was8host01Node01/servers/server1
'server(cells/was8host01Node01Cell/nodes/was8host01Node01/servers/server1
|server.xml#Server_1183122130078
|server.xml#Server_1183122130078
wsadmin>
wsadmin>
• Use the AdminConfig object to:

– List configuration objects and their attributes
– Create configuration objects
– Modify configuration objects
– Remove configuration objects
– Obtain help
Figure 12-13. AdminConfig: Managing configurations WA855 / VA8551.0
Notes:
Management configuration scripts use the AdminConfig object to access the repository
where configuration information is stored.
Here is an example of AdminConfig:
wsadmin>AdminConfig.list ('Server')
You can use the AdminConfig object to:
• List configuration objects and their attributes
• Create configuration objects
• Modify configuration objects
• Remove configuration objects
• Obtain help
V8.1
Student Notebook
Uempty
AdminApp: Managing applications

• Application management scripts use the AdminApp object to manage
applications in the application server configuration
• Example:
• Use the AdminApp object to:

– Install and uninstall applications
– List installed applications
– Edit application configurations
– Obtain help
Figure 12-14. AdminApp: Managing applications WA855 / VA8551.0
Notes:
Application management scripts use the AdminApp object to manage applications in the
application server configuration.
Here is an example of AdminApp:
wsadmin>AdminApp.view ('ivtApp')
Running the command produces output specific to the application. In the Jython command,
output is easier to read when using the print option:
wsadmin>print AdminApp.view ('ivtApp')
You can use the AdminApp object to:
• Install and uninstall applications
• List installed applications
• Edit application configurations
• Obtain help
Student Notebook
AdminControl: Managing running objects

• Operation management scripts use the AdminControl object to
communicate with the MBeans that represent running objects
• Example:
• Use the AdminControl object to:

– List running objects and their attributes
– Start actions on running objects
– Obtain dynamic information about MBeans that represent running objects
– Obtain help
Figure 12-15. AdminControl: Managing running objects WA855 / VA8551.0
Notes:
Operation management scripts use the AdminControl object to communicate with the
MBeans that represent running objects.
Here is an example of AdminControl:
wsadmin>AdminControl.getPort()
You can use the AdminControl object to:
• List running objects and their attributes
• Start actions on running objects
• Obtain dynamic information about MBeans that represent running objects
• Obtain help
The number and type of MBeans available to the scripting client depend on the server to
which the client is connected. If the client is connected to a deployment manager, then all
the MBeans running in the deployment manager are visible. All the MBeans running in the
V8.1
Student Notebook
Uempty node agents that are connected to this deployment manager, and all the MBeans running in
the application servers on those nodes, are visible.
Student Notebook
AdminTask: Accessing administrative functions

• AdminTask object is used to access a set of administrative commands
to provide an alternative way to access configuration commands
• Example:
• Benefits of using AdminTask:

– Provides more usable and task-oriented commands
– Runs simple and complex commands
– Commands grouped based on function
– Can be run in batch or interactive mode
– Can be run in connected or local mode
Figure 12-16. AdminTask: Accessing administrative functions WA855 / VA8551.0
Notes:
The AdminTask object is used to access a set of administrative commands that provide an
alternative and easier way to access configuration commands. AdminTask commands
enable you to run a single command for administrative actions that might otherwise require
multiple commands.
Here are examples of AdminControl:
wsadmin>AdminTask.binaryAuditReader('-interactive')
wsadmin>AdminTask.listServers()
The benefits of using AdminTask include:
• Provides commands that are more task-oriented and easier to use
• Runs simple and complex commands
• Commands are grouped, based on function
• Can be run in batch or interactive mode
• Can be run in connected or local mode
V8.1
Student Notebook
Uempty The administrative commands are discovered dynamically when you start a scripting client.
The set of available administrative commands depends on the edition of WebSphere
Application Server you install. You can use the AdminTask object commands to access
these commands.
Administrative commands are grouped based on their function. You can use administrative
command groups to find related commands. For example, the administrative commands
that are related to server management are grouped into a server management command
group. The administrative commands that are related to the security management are
grouped into a security management command group. An administrative command can be
associated with multiple command groups because it can be useful for multiple areas of
system management. Both administrative commands and administrative command groups
have names that uniquely identify them.
Two run modes are always available for each administrative command, namely the batch
and interactive modes. When you use an administrative command in interactive mode, you
go through a series of steps to collect your input interactively. This process provides users
a text-based wizard and a similar user experience to the wizard in the administrative
console. You can also use the help command to obtain help for any administrative
command and the AdminTask object.
The administrative commands do not replace any existing configuration commands or
running object management commands, but provide a way to access these commands and
organize the inputs. The administrative commands can be available in connected or local
mode. The set of available administrative commands is determined when you start a
scripting client in connected or local mode. If a server is running, do not run the scripting
client in local mode because any configuration changes made in local mode are not
reflected in the running server configuration, and the reverse is also true. If you save a
conflicting configuration, you can corrupt the configuration.
Student Notebook
Help within wsadmin

Jython
• print Help.help() • print Help.AdminControl()
• print Help.AdminConfig() • print Help.AdminApp()
• print Help.AdminTask()
Figure 12-17. Help within wsadmin WA855 / VA8551.0
Notes:
You can find general help and dynamic online information about the currently running
MBeans with the wsadmin tool. Use the Help object as an aid in writing and running scripts
with the AdminControl object.
Here are examples of commands available for the Help object:
• AdminConfig 
Use the AdminConfig command to view a summary of each available method for the
AdminConfig object.
• AdminTask 
Use the AdminTask command to view a summary of help commands and ways to start
an administrative command with the AdminTask object.
• AdminControl 
Use the AdminControl command to view a summary of the help commands and
ways to start an administrative command.
V8.1
Student Notebook
Uempty • AdminApp 
Use the AdminApp command to view a summary of each available method for the
AdminApp object.
• help 
Use the help command to view a summary of all the available methods for the Help
object.
Here are some Jython examples:
print Help.help()
print Help.AdminConfig()
print Help.AdminTask()
print Help.AdminControl()
print Help.AdminApp()
For complete documentation, see the information center. The information center also
includes a number of examples that demonstrate some useful wsadmin features.
Student Notebook
Administrative command help
• You can select from three levels of online help for administrative
commands
• Example of command-level help:
Figure 12-18. Administrative command help WA855 / VA8551.0
Notes:
You can select from three levels of online help for administrative commands.
• Top-level help:
Top-level help provides general information for the AdminTask object and associated
commands.
print AdminTask.help()
• Second-level help:
Second-level help provides information about all of the available administrative
commands and command groups.
print AdminTask.help('-commands')
• Third-level help: 
Third-level help provides specific help on a command group, a command, or a step.
Command group-specific help provides descriptions for the command group that you
specify and the commands that belong to the associated group. Command-specific help
V8.1
Student Notebook
Uempty provides a description of the specified command, and associated parameters and
steps.
Step-specific help provides a description of the specified step and the associated
parameters. For command and step-specific help, required parameters are marked with
an asterisk in the help output.
print AdminTask.help('listServers')
Student Notebook
Important points to remember when using wsadmin

• Commands are case-sensitive
• Running multiple commands in a script file is faster than running
individual commands
• Saving configuration changes is a two-step process:
– The first step validates the changes
– The second step completes the save
• Save periodically:
wsadmin>
wsadmin> AdminConfig.save()
AdminConfig.save()
''
''
wsadmin>
wsadmin>
Figure 12-19. Important points to remember when using wsadmin WA855 / VA8551.0
Notes:
When using wsadmin, remember the following important points:
• Commands are case-sensitive.
• Running multiple commands in a script file is faster than running individual commands.
For example, wsadmin -f "script_file_name" is faster than individual commands
with wsadmin -c
• Saving configuration changes is a two-step process:
- The first step validates the changes.
- The second step saves the changes.
• Save periodically in the script file or interactive mode to persist configuration updates to
existing objects.
AdminConfig.save()
V8.1
Student Notebook
Uempty
Scripting: Simple script
C:\Program
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile1\bin>wsadmin
Files\IBM\WebSphere\AppServer\profiles\profile1\bin>wsadmin –f–f
"C:\software\wsadmin\simple_script.py"
"C:\software\wsadmin\simple_script.py" –username
–username wasadmin
wasadmin –password
–password
********
********
WASX7209I:
WASX7209I: Connected
Connected to
to process
process "server1"
"server1" on
on node
node was8host01Node01
was8host01Node01 using
using
SOAP connector: The type of process is: UnManagedProcess
SOAP connector: The type of process is: UnManagedProcess
Simple
Simple wsadmin
wsadmin scripting
scripting example
example
Cell
Cell name
name is:
is: was8host01Node01Cell
was8host01Node01Cell
Node
Node name
name is:
is: was8host01Node01
was8host01Node01
Figure 12-20. Scripting: Simple script WA855 / VA8551.0
Notes:
The following is an example of a simple script:
print "Simple wsadmin scripting example."
cell = AdminConfig.list("Cell")
node = AdminConfig.list("Node")
cellName = AdminConfig.showAttribute(cell, "name")
nodeName = AdminConfig.showAttribute(node, "name")
print ""
print "Cell name is: " + cellName
print "Node name is: " + nodeName
An example of the output from this script is:
Simple wsadmin scripting example.
Cell name is: was7host01Node01Cell
Node name is: was7host01Node01
Student Notebook
Scripting: Looping script
C:\Program
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile1\bin>wsadmin
Files\IBM\WebSphere\AppServer\profiles\profile1\bin>wsadmin –f
–f
"C:\software\wsadmin\simple_script.py"
"C:\software\wsadmin\simple_script.py" –username
–username wasadmin
wasadmin –password
–password
********
********
WASX7209I:
WASX7209I: Connected
Connected to
to process
process "server1"
"server1" on
on node
node was8host01Node01
was8host01Node01 using
using
SOAP
SOAP connector:
connector: The
The type
type of
of process
process is:
is: UnManagedProcess
UnManagedProcess
Simple
Simple loop
loop scripting
scripting example
example
app
app Name:
Name: DefaultApplication
DefaultApplication
app
app Name:
Name: PlantsByWebSphere
PlantsByWebSphere
app
app Name:
Name: ivtApp
ivtApp
app
app Name:
Name: query
query
Figure 12-21. Scripting: Looping script WA855 / VA8551.0
Notes:
The following is an example of a looping script:
print "Simple loop script"
print ""
appNames = AdminApp.list()
AppNamesArray = appNames.split('\r\n')
for appName in appNamesArray:
print "App Name: " + appName
Here is an example of the output from these scripts:
Simple loop script
App Name: DefaultApplication
App Name: PlantsByWebSphere
App Name: ivtApp
App Name: query
V8.1
Student Notebook
Uempty
Jython script library

• Provides a library of
wsadmin Jython scripts for
commonly used
administrative functions
• Grouped according to
administrative function
• One location for learning
script syntax
• Supports rapid development
of new scripts by combining
library scripts with custom
code
• In:
– Information center, under
Reference
– <was_root>/
scriptLibraries
Figure 12-22. Jython script library WA855 / VA8551.0
Notes:
The Jython script library provides a set of procedures to automate the most common
application server administration functions. For example, you can use the script library to
easily configure servers, applications, mail settings, resources, nodes, business-level
applications, clusters, authorization groups, and more. You can run each script procedure
individually, or combine several procedures to quickly develop new scripts.
The Jython script library helps to eliminate the complexities that are associated with
scripting:
• Syntax is complex.
• Incompatible or incorrect parameters are easy to specify.
• Complexity presents a barrier to learning WebSphere.
• Complexity can result in inconsistent and unstable systems that make problem
determination difficult.
• wsadmin provides a low level of abstraction that results in complex mappings between
operations and problems that users are trying to solve.
Student Notebook
Jython script library features include:

• It provides a library of wsadmin Jython scripts for commonly used administrative
functions:
- Application management
- Configuration
- Runtime operations
• Scripts are grouped according to administrative function. Examples of grouped
functions include:
- Utility scripts
- JDBC query scripts
- Cluster administration scripts
- Cluster configuration scripts
- Server administration scripts
- Server configuration scripts
• Users can learn script syntax from the script library, rather than referencing external
documentation.
• It supports rapid development of new scripts by combining library scripts with custom
code that the user develops.
The Jython script library is in the <was_root>/scriptLibraries directory. Information
regarding the script library is available in the information center under Reference.
V8.1
Student Notebook
Uempty
How to use the Jython script library

• There are three ways to use the Jython script library:
– Run scripts in interactive mode with the wsadmin tool
wsadmin>AdminServerManagement.createApplicationServer("profile1",
wsadmin>AdminServerManagement.createApplicationServer("profile1",
"server1",
"server1", "default")
"default")
– Use a text editor to combine several scripts

## My
My Custom
Custom Jython
Jython Script
Script –– file.py
file.py
AdminServerManagementcreateApplicationServer("profile1",
"server1","default")
## Use
Use one
one of
of them
them as
as the
the first
first member
member of
of aa cluster
cluster
AdminClusterManagement.createClusterWithFirstMember("cluster1",
"APPLICATION_SERVER",
"APPLICATION_SERVER", "profile1",
"profile1", "server1")
"server1")
## Install
Install an
an application
application
AdminApplication.installAppWithClusterOption("DefaultApplication",
"..\installableApps\DefaultApplication.ear",
"..\installableApps\DefaultApplication.ear", "cluster1")
"cluster1")
## Start
Start all
all servers
servers and
and applications
applications on
on the
the node
node
AdminServerManagement.startAllServers("profile1")
– Use the Jython scripting library code as sample syntax to write custom scripts
Figure 12-23. How to use the Jython script library WA855 / VA8551.0
Notes:
The scripting library provides a set of procedures to automate the most common
application server administration functions. Each script in the script library demonstrates
suggested practices for writing wsadmin scripts.
The script library code is in the <was_root>/scriptLibraries directory. Within this
directory, the scripts are organized into subdirectories according to function, and further
organized according to version. For example, the
<was_root>/scriptLibraries/application/V80 subdirectory contains procedures that
complete application management tasks that are applicable to version 8.0 and later of the
product.
There are three ways to use the Jython script library.
• Interactively:
Run scripts from the Jython script library in interactive mode with the wsadmin tool. You
Student Notebook
can start the wsadmin tool, and run individual scripts that are included in the script
library:
wsadmin>AdminServerManagement.createApplicationServer("myNode",
"myServer", "default")
• Use a text editor to combine scripts.
Use a text editor to combine several scripts from the Jython script library, as the
following example demonstrates:
#
# My Custom Jython Script - file.py
#
AdminServerManagement.createApplicationServer("profile1", "server1",
"default")
AdminServerManagement.createApplicationServer("profile2", "server2",
"default")
# Use one of them as the first member of a cluster
"APPLICATION_SERVER", "profile1", "server1")
# Install an application
"..\installableApps\DefaultApplication.ear", "cluster1")
# Start all servers and applications on the node
• As sample scripts:
Use the Jython scripting library code as sample syntax to write custom scripts.
V8.1
Student Notebook
Uempty
Configuration repository: The issues

• The repository consists of multiple files in XML and other formats
• The configuration files are spread across many directories
• Configuration objects are complex
• Some configuration objects repeatedly stored in multiple files
• Example: properties for a JDBC provider
Figure 12-24. Configuration repository: The issues WA855 / VA8551.0
Notes:
In previous releases of WebSphere Application Server, users used wsadmin, the
administrative console, and Java APIs to query and modify configurator objects. Now users
who work with the WebSphere Application Server configuration repository are confronted
with several issues:
• The repository consists of multiple files in XML and other formats.
• The configuration files are spread across many directories.
• Some files contain complex objects that are associated with the WebSphere Common
Configuration Model.
• Some configuration objects are repeatedly stored in multiple files.
Properties-based file configuration is a tool to help users deal more easily with these
issues. A new set of wsadmin commands is available that can extract and apply properties
files to configuration objects.
The graphic shows JDBCProvider object content from the configuration XML file named
resources.xml.
Student Notebook
Properties file based configuration: A solution

• Properties files are more human readable
• Properties files consist of name and value pairs
• Decouples configuration data from changes in the underlying
configuration model between releases
• Can be used with configuration archives
• Differences between configuration environments are easier to identify
wsadmin>AdminTask.extractConfigProperties('-propertiesFileName
jdbcprovider.props
jdbcprovider.props –configData
–configData Server=server1
Server=server1 filterMechanism
filterMechanism
•• SELECTED_SUBTYPES
SELECTED_SUBTYPES –selectedSubTypes
–selectedSubTypes [JDBCProvider]')
[JDBCProvider]')
Figure 12-25. Properties file based configuration: A solution WA855 / VA8551.0
Notes:
Using the PropertiesBasedConfiguration command group for the AdminTask object,
you can extract the configuration attributes and values from your environment to properties
files. You can use this feature for various purposes, including:
• To modify your existing configuration in one location, instead of configuring multiple
administrative console panels or running many commands
• To improve the application development lifecycle
Properties file-based configuration offers the following benefits:
• Properties files are more human readable than configuration files, which are in XML or
other formats.
• Properties files consist of a standard name-value pair format.
• The properties file-based configuration decouples configuration data from changes in
the underlying configuration model between releases.
- Automating the configuration process is made easier.
V8.1
Student Notebook
Uempty - The necessity to write complex wsadmin scripts is eliminated.

Many users of WebSphere Application Server try to create their own automated
methods for modifying an application server configuration, often by directly
manipulating files in the configuration repository. However, custom solutions are tightly
coupled to the underlying file structure, which can change from release to release.
• Properties file-based configuration can be used with, but is not a replacement for,
configuration archives.
Properties files can be used with configuration archives to replicate a configuration by:
- Importing a configuration archive
- Using properties file configuration to customize the environment
At most, the properties files-based configuration commands extract commonly used
configuration attributes from the configuration repository only. However, a backup that is
made by using configuration archives can contain an exact copy of the configuration
that can be applied to another system to exactly replicate the configuration information.
If you want to replicate the configuration of one system onto another, with some
customizations, you can use configuration archives to gain an exact replica of the
configuration. Then, follow with properties file-based configuration to make the required
customizations.
• Differences between configuration environments are easier to identify since properties
files are simple text files. It is easy to use standard text editors to compare properties
files from different configuration environments to help identify potential configuration
problems.
WebSphere Application Server derives configuration information from the configuration
repository, not from configuration properties files. To update the configuration repository to
reflect the information in a configuration properties file, you must use wsadmin commands
to apply the properties files to the configuration.
The graphic depicts the use of the wsadmin extractConfigProperties command to
create a properties file with content based on information that is contained in the
configuration XML file.
Student Notebook
Properties file configuration content

• Each object is defined in a separate section:
– Resource type and identifier
– Configuration information
• Example: properties for a JDBC provider
## SubSection
SubSection 1.0
1.0 ## JDBCProvider
JDBCProvider attributes
attributes
##
ResourceType=JDBCProvider
ResourceType=JDBCProvider 1 Resource type and identifier
ImplementingResourceType=JDBCProvider
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!
{serverName}:JDBCProvider=ID#JDBCProvider_1183122153343
{serverName}:JDBCProvider=ID#JDBCProvider_1183122153343
##
## Properties
Properties
##
classpath={$DERBY_JDBC_DRIVER_PATH}/derby.jar}
classpath={$DERBY_JDBC_DRIVER_PATH}/derby.jar} 2 Configuration information
name=Derby
name=Derby JDBC
JDBC Provider
Provider
implementationClassName=
implementationClassName=
org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
nativepath={}
nativepath={}
description=Derby
description=Derby embedded
embedded non-XA
non-XA JDBC
JDBC Provider
Provider
providerType=Derby JDBC Provider #readonly
xa=false
xa=false #boolean
#boolean
Figure 12-26. Properties file configuration content WA855 / VA8551.0
Notes:
Configuration properties files contain a series of name-value pairs. Each configuration
object is defined in two separate sections:
1. Resource type and identifier
The first section of the example defines a resource type and a resource identifier. The
identifier is often in a format that includes the cell, node, and server names, ending with
a string that contains the resource type and a large number.
In the example, the resource type is JDBC provider.
2. Configuration information
Name-value pairs are used to describe the configuration information.
V8.1
Student Notebook
Uempty The following is an example of a JDBC provider configuration object:

#
# SubSection 1.0 # JDBCProvider attributes
#
ResourceType=JDBCProvider
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}:JDBCProvi
der=
ID#JDBCProvider_1183122153343
#
#
# Properties
#
classpath={$DERBY_JDBC_DRIVER_PATH}/derby.jar}
name=Derby JDBC Provider
implementationClassName=org.apache.derby.jdbc.EmbeddedConnectionPoolDataSou
rce
nativepath={}
description=Derby embedded non-XA JDBC Provider
xa=false #boolean
Student Notebook
Properties file configuration commands

• extractConfigProperties: extracts configuration data into a properties file
server1.props
server1.props –configData
–configData Server=server1')
Server=server1')
• validateConfigProperties: verifies that the properties in the properties file

are valid
wsadmin>AdminTask.validateConfigProperties('-propertiesFileName
wsadmin>AdminTask.validateConfigProperties('-propertiesFileName
server1.props')
server1.props')
• applyConfigProperties: applies properties in a specific properties file

wsadmin>AdminTask.applyConfigProperties('-propertiesFileName
wsadmin>AdminTask.applyConfigProperties('-propertiesFileName
app.props')
app.props')
• deleteConfigProperties: deletes objects in your configuration

wsadmin>AdminTask.deleteConfigProperties('-propertiesFileName
wsadmin>AdminTask.deleteConfigProperties('-propertiesFileName
thread.props')
thread.props')
• createPropertiesFileTemplates: creates template properties files

wsadmin>AdminTask.createPropertiesFileTemplates('-propertiesFileName
wsadmin>AdminTask.createPropertiesFileTemplates('-propertiesFileName
app.props
app.props –configType
–configType Application')
Application')
Figure 12-27. Properties file configuration commands WA855 / VA8551.0
Notes:
Properties file-based configuration uses the following five commands:
• extractConfigProperties 
The extractConfigProperties command extracts configuration data in the form of a
properties file. The system exports the most commonly used configuration data and
attributes, converts the attributes to properties, and saves the data to a file. You can
specify the resource of interest with the target object or the configData parameter.
Use the configData parameter to specify a server, node, cluster, or application
instance. If no configuration object is specified, the command extracts the profile
configuration data. Here is an example:
AdminTask.extractConfigProperties('-propertiesFileNameserver1.
props -configData Server=server1')
One common scenario for using properties files to work with your configuration is to
extract a properties file, which is based on your current environment. Modify the
extracted file, and then apply the updated properties to your configuration. You can use
any text editor to modify the properties file.
V8.1
Student Notebook
Uempty • validateConfigProperties 
The validateConfigProperties command verifies that the properties in the
properties file are valid and can be successfully applied to the new configuration. Here
is an example:
AdminTask.validateConfigProperties('-propertiesFileNameserver1.props')
It is a good practice to validate the properties file before applying it to your
configuration. There are two steps to validate a properties file before applying it to the
configuration:
- Use the validateConfigProperties command to validate the properties file.
- Use the applyConfigProperties command and the -validate option to apply
the properties and validate the file simultaneously.
• applyConfigProperties 
The applyConfigProperties command applies properties in a specific properties file
to the configuration. The system adds attributes or configuration data to the
configuration if specific properties do not exist. If the properties exist in the
configuration, the system sets the new values for the attributes. Here is an example:
wsadmin>AdminTask.applyConfigProperties('-propertiesFileNameapp.props')
• deleteConfigProperties 
The deleteConfigProperties command deletes properties in your configuration as
designated in a properties file. The system removes the attributes or configuration data
that corresponds to each property in the properties file. In the properties file, you must
add the flag DELETE=true to the section that contains the resource identifier for the
object that you want to delete. Then, run the deleteConfigProperties command on
your properties file. Here is an example:
- In the properties file:
#
# SubSection 1.0.1.4 # Thread pools
#
ResourceType=ThreadPool
ImplementingResourceType=Server
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!
{serverName}:ThreadPoolManager=
ID#ThreadPoolManager_1:ThreadPool-myThreadPool
DELETE=true
#
- The command to delete the thread pool would be:
wsadmin>AdminTask.deleteConfigProperties
('-propertiesFileNamethread.props')
If you run the deleteConfigProperties command before you add the DELETE=true
attribute and value to the properties file, the command resets each property to the
Student Notebook
default value. The system completely removes properties that do not have default
values.
• createPropertiesFileTemplates
Use the createPropertiesFileTemplates command to create template properties
files to use for creating or deleting specific object types. The command stores the
template properties file in the properties file that the propertiesFileName parameter
identifies. Here is an example:
wsadmin>AdminTask.createPropertiesFileTemplates(
'-propertiesFileNameapp.props -configType Application')
There are four different types of properties file templates that you can create with the
createPropertiesFileTemplates command:
- Server
- ServerCluster
- Application
- AuthorizationGroup
The templates are properties files that contain the required parameters to create a
configuration object of a specific type. When you create a template for the application
configuration type, you must provide a resource ID and information about the application
that you are deploying. The properties file template contains comments and instructions for
how to modify and use the template.
V8.1
Student Notebook
Uempty
Create, test, and debug Jython scripts
Rational
Application
Developer
Assembly and
Deploy
provides:
• Full support for Jython projects and source files

• Ability to create, test, and debug Jython projects and files
• Syntax colored editor and command completion tools
• A source outline view
• Source level debugging
Figure 12-28. Create, test, and debug Jython scripts WA855 / VA8551.0
Notes:
With the IBM Assembly and Deploy Tool, you can create, test, and debug Jython scripts.
Jython projects and scripts are treated as first-class objects. The Jython editor provides the
same facilities as all other specialized editors, including:
• Full support for Jython projects and sources files
• Ability to create, test, and debug Jython projects and files
• Syntax colored editor, automated formatting, and command completion tools
• A source outline view
• Source-level debugging
Student Notebook
Start the Jython debugger
2
Set up debugging
parameters and run
• Enter parameters and
1 click Debug
Select the script and debug option
• Select the menu of the script
• Click Debug As > Administrative Script © Copyright IBM Corporation 2013
Figure 12-29. Start the Jython debugger WA855 / VA8551.0
Notes:
To start the Jython debugger:
1. Select the script and debug option.
- Highlight the script and right-click to open the menu.
- Click Debug As > Administrative script to open the debugger runtime and security
parameters window.
2. Set up debugging parameters and start the debugger.
- Enter debugging parameters as appropriate. Runtime parameters are categorized
under the following tabs:
• Script
• Arguments
• Classpath
• Source
V8.1
Student Notebook
Uempty • Environment
• Common
Debugging a script for the first time requires setup of runtime and security
parameters that are defined under the Script tab:
• Administrative script name
• Scripting runtime environment
• WebSphere profile name
• wsadmin arguments
• Security options include:
- No security on the target server
- As defined in soap.client props or the sas.client.props file
- Specify as user ID and password
Click Debug when parameter input is complete to start the Debug perspective.
Student Notebook
Jython debugger perspective
Debug, Servers Variables, breakpoints
Source code Outline
Console, Tasks
Figure 12-30. Jython debugger perspective WA855 / VA8551.0
Notes:
The Jython debugger perspective is a tool that can help you track the behavior and state of
your Jython scripts and easily pinpoint logic errors. Using the debugger, you can pause the
running script, examine the working code, locate the source of the bug, and locate bugs
that were missed.
The Jython debugger helps to pinpoint logic errors by offering script developers the ability
to do the following functions:
• Trace or highlight code as it is being run
• Inspect and set variables
• Step through Jython script logic
• Set conditional breakpoints
• Show the stack
The debugger perspective is divided into views:
• The Debug view (upper left pane)
V8.1
Student Notebook
Uempty • The upper right pane has multiple tabs, including:

- The Breakpoints view lists all the breakpoints that are set in the workbench projects.
To show this view, click Window > Show View > Breakpoints.
You can double-click a breakpoint to show its location in the editor. In this view, you
can also enable or disable breakpoints, delete them, or add new ones. This view
also lists exception breakpoints, which suspend execution at the point where the
exception is thrown. You can add or remove exceptions.
- From the Expressions view, you can inspect data from a scrapbook page, a stack
frame of a suspended thread, and other places. To show this view, click Window >
Show View > Expressions.
- The Variables view shows information about the variables in the currently selected
stack frame. To show this view, click Window > Show View > Variables.
• The Source view (middle left pane) shows the result of evaluating an expression in the
context of the current stack frame. You can evaluate and show a selection either from
the editor or directly from the Display view.
• The Outline view (middle right pane) shows an outline of the structure of the currently
active Jython script in the editor area.
• The Console view (lower pane) shows messages that result from the execution of the
Jython script.
Student Notebook
Command assistance
• Works in concert with the
– Last run commands are made
available to Rational Application
Developer
– Commands can be pasted
directly to Jython scripts
• Administrative console access

– Under Help, click View administrative
scripting command for last action
– The last command run is displayed
– Place the cursor over the command to get
command information
– Command can be copied into a Jython script
Figure 12-31. Command assistance WA855 / VA8551.0
Notes:
Using command assistance, you can see wsadmin scripting commands that correspond to
actions in the administrative console. Seeing these commands might help you develop the
commands necessary to administer WebSphere Application Server from the wsadmin
utility. You can view wsadmin scripting commands in the Jython language for the last action
that runs in the administrative console. Working in concert with the administrative console,
administrative command assistance provides the following capabilities:
• The last commands are made available to Rational Application Developer.
When you do server operations in the administrative console, the administrative
command assistance tool captures and shows the wsadmin commands issued.
• Commands can be pasted directly to Jython scripts.
You can transfer the output from the administrative command view directly to a text
editor, such as the Jython editor, enabling you to develop Jython scripts that are based
on actual console actions.
V8.1
Student Notebook
Uempty To access command assistance from the administrative console:

1. Under Help, click View administrative scripting command for last action. The last
command is shown.
2. Place the cursor over the command to get command information.
3. The command can be copied into a Jython script.
Student Notebook
Using command assistance within IBM Assembly and Deploy Tools
• Command assistance setup includes the following steps:

– Add the WebSphere Administration Command view:
Click Window > Show View > Other > Server > WebSphere Administration
Command
– Open the WebSphere Administration Command view
– Use Select Server to Monitor to connect to the server
– Select the command that you want

– Use Insert into Editor to copy the command to a Jython script file
Figure 12-32. Using command assistance within IBM Assembly and Deploy Tools WA855 / VA8551.0
Notes:
You can use command assistance from IBM Assembly and Deploy Tools, and the
administrative console. To enable command assistance from IBM Assembly and Deploy
Tools, administrative console setup is required.
1. Under Help, click View administrative scripting command for last action.
2. Expand Preferences and enable both preference options.
- Log command assistance commands:
This option logs the command assistance data to a file. A timestamp and the
breadcrumb trail of the panel that produced the command assistance data are
provided with the wsadmin data.
- Enable command assistance notifications:
This option allows command assistance to emit Java Management Extensions
(JMX) notifications. Enablement of the notifications allows integration with product
tools such as the Rational Application Developer Jython editor to assist you in
writing scripts.
V8.1
Student Notebook
Uempty 3. Click Apply.

Using command assistance from Rational Application Developer:
1. Add the WebSphere Administration Command view to the perspective.
Click Window > Show View > Other > Server > WebSphere Administration
Command.
2. Open the WebSphere Administrative Command view.
3. Connect to the server by clicking Select Server to Monitor.
4. Select the command from the list. The command list provides a description for each
command listed.
5. Copy the command to a Jython script file by clicking Insert into Editor.
Student Notebook
Unit summary
• Customize the wsadmin environment with profiles and property files
• Use IBM Assembly and Deploy Tools for WebSphere Administration
to edit and debug Jython scripts
Notes:
V8.1
Student Notebook
Uempty
1. Which of the following is not one of the five Java objects that perform
different operations?
A. AdminConfig
B. AdminControl
C. AdminTask
D. Help
E. AdminStart
2. What is the default protocol type for wsadmin?

A. SOAP
B. RMI
C. None
3. The default behaviors for wsadmin can be changed by editing which

file?
Notes:
1. 
2. 
3.
Student Notebook
Checkpoint answers
1. Which of the following is not one of the five Java objects that perform
different operations?
E. AdminStart
2. What is the default protocol type for wsadmin?

A. SOAP
3. The default behaviors for wsadmin can be changed by editing which

file?
wsadmin.properties
Notes:
V8.1
Student Notebook
Uempty
Exercise 8
Using wsadmin

Notes:
Student Notebook
Exercise objectives
• Use wsadmin to run administrative commands interactively and with
scripts
• Create a simple administrative script
• Use console command assistance
• Use property file based configuration to modify your settings
Notes:
V8.1
Student Notebook
Uempty Unit 13. Federating a cell

In this unit, you learn the process of federating a base profile into a cell
and the administration of a multinode distributed environment. You
learn the process of creating a deployment manager and federating
base profiles into a cell. You also learn how to add a node by using
commands or the administrative console, and how to manage a web
server with the administrative console.

• Describe WebSphere Application Server cell concepts
• Describe and create the deployment manager profile
• Describe and create other profile types
• Describe custom profiles and automatic federation
• Describe the directories and configuration files for profiles
• Add a node by using commands or the administrative console
• Compare the deployment manager administrative console with the
base administrative console
• Compare managed and unmanaged nodes
• Use the administrative console to manage a web server

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 13. Federating a cell 13-1

Student Notebook
Unit objectives
Notes:
V8.1
Student Notebook
Uempty
WebSphere cells
• A WebSphere cell defines an administrative domain
– Available in WebSphere Application Server Network Deployment
– A deployment manager provides centralized administration for entire cell
– A cell is created as a profile
– Nodes run application components in application servers
Cell
Deployment manager
Node01 Node02
Node agent Node agent
server1 server2 server3 server4
Figure 13-2. WebSphere cells WA855 / VA8551.0
Notes:
A WebSphere cell defines an administrative domain. A cell is a grouping of nodes into a
single administrative domain. A cell can consist of multiple nodes, all administered from a
deployment manager server. When a node becomes part of a cell (a federated node), a
node agent server is created on the node to work with the deployment manager server to
manage the WebSphere Application Server environment on that node. A cell includes the
following characteristics:
• It is available in WebSphere Application Server Network Deployment.
• A deployment manager provides centralized administration for the entire cell.
• A cell is created as a profile.
• Nodes run application components in application servers.
The graphic includes the following cell environment topology:
• A cell encapsulating:
- Deployment manager with connections to the node agents of two nodes

Student Notebook
- Node01:
• Node agent with connections to the application servers of the node
• server1
• server2
- Node02:
• Node agent
• server3
• server4
V8.1
Student Notebook
Uempty
WebSphere Application Server process types

– Provides the functions that are required to support and host user applications
– Runs on only one node, but one node can support many application servers
• Node agent
– Created and installed when a node is federated into a cell
– Works with the deployment manager to perform administrative activities on the
node
• Deployment manager
– Administers multiple application servers from one centralized manager
– Works with the node agents on each node to manage all the servers in a
distributed topology
– Application server nodes are federated with the deployment manager before the
deployment manager can manage them
Figure 13-3. WebSphere Application Server process types WA855 / VA8551.0
Notes:
There are three main types of WebSphere managed processes that make up a cell. These
server types interact to do system administration.
- A WebSphere Application Server provides the functions that are required to support
and host user applications.
- An application server runs on only one node, but one node can support many
application servers.
• Node agent
- When a node is federated, a node agent is created and installed on that node.
- The node agent works with the deployment manager to do administrative activities
on the node.

Student Notebook
- With the deployment manager, you can administer multiple nodes from one
centralized manager.
- The deployment manager works with the node agent on each node to manage all
the servers in a distributed topology.
- Application server nodes are federated with the deployment manager before the
deployment manager manages them.
V8.1
Student Notebook
Uempty
Network deployment concepts

• Deployment manager (dmgr) • Node
– Manages the node agents – Logical grouping of servers
– Holds the configuration repository – A single node agent process
for the entire management manages it
domain, called a cell – Each node is defined within a profile
– Administrative service runs inside the dmgr
– The deployment manager is defined within
a profile Web-based
administrative
console Command-line
Cell C:\> wsadmin
Commands Deployment
Configuration manager
Node01 Admin service Node02
server1 server3
Node Node
server2 agent agent server4
Master
configuration
config repository config
Notes:
Deployment manager (dmgr):
• The deployment manager works with the node agent on each node to manage all the
servers in a distributed topology.
• The deployment manager holds the configuration repository for the entire management
domain, called a cell.
• An administrative service runs inside the deployment manager.
• The deployment manager is defined within a profile.
Node:
• A node is a logical group of WebSphere Application Server-managed server processes
that share a common configuration repository.
• A single node agent process manages a node.
• A node is associated with a single WebSphere Application Server profile.

Student Notebook
• A WebSphere Application Server node does not necessarily have a one-to-one

association with a system. One computer can host arbitrarily many nodes, but a node
cannot span multiple computer systems.
• A node can contain zero or more application servers.
Configuration repository:
• When a node is part of a cell, the configuration and application files for all nodes in the
cell are centralized into a cell master configuration repository.
• The deployment manager server manages the centralized repository and synchronizes
the repository to local copies that are held on each node.
• The local copy of the repository that is given to each node contains just the
configuration information that the node needs, not the full configuration that the
deployment manager maintains.
• When a deployment manager is registered with a job manager, the deployment
manager continues to manage the centralized configuration repository.
- Deployment manager with connections to the node agents of two nodes
• Administrative service is shown within the deployment manager.
- Master configuration repository with a link to the deployment manager
- Web-based administrative console that uses the deployment manager
administrative console to demonstrate administration of the cell
- Node01:
• Local configuration repository with configuration links to the node agent and the
application servers within the node
• server1
• server2
- Node02:
• Local configuration repository with configuration links to the node agent and the
application servers within the node
• server3
• server4
V8.1
Student Notebook
Uempty
Profiles in network deployment

Profiles represent the nodes
• Multiple nodes can be installed on a single computer
• Nodes can contain a single stand-alone application server
• Nodes can be federated into a cell
Each profile uses the same product files regardless of type:
• Cell (deployment manager and
a federated application server) Application server
• Management + WebSphere
profile 1 Custom profile
– Administrative
agent Deployment manager
– Deployment WebSphere
manager install + WebSphere Job manager
product profile 2
– Job manager binaries Administrative agent
• Custom profile Cell
+ WebSphere
• Secure proxy profile 3 Secure proxy
Figure 13-5. Profiles in network deployment WA855 / VA8551.0
Notes:
A profile defines the runtime environment for a node. The profile includes all of the files that
the server processes in the runtime environment and that you can change.
A profile defines the application server configuration and runtime environment. The profile
includes all of the files that the server processes in the runtime environment and that you
can change. After installing the core product files for the Network Deployment product, you
must create a profile.
• Profiles represent the nodes:
- Multiple nodes can be installed on a single computer.
- Nodes can contain a single stand-alone application server.
- Nodes can be federated into a cell.
• Each profile uses the same product files regardless of type:
- Cell (deployment manager and a federated application server)
- Management

Student Notebook
• Administrative agent
• Job manager
- Application server
- Custom profile
- Secure proxy
The graphic includes a diagram that includes:
• WebSphere installation product files (used by all profiles)
• Three sets of profiles (which can be any of seven profile environment types):
- WebSphere profile 1
• Here is a list of seven profile environment types:
- Cell
- Administrative agent
- Deployment agent
- Job manager
- Application server
- Custom profile
- Secure proxy
V8.1
Student Notebook
Uempty
Application server profile

• Application server profiles provide a base installation
• Application servers in the network deployment product can run as:
– Part of managed nodes in a cell
– Stand-alone application servers Cell
• Multiple application server profiles
can be created on a single computer Deployment
manager
• Each application server
profile can be
federated into a cell Node01
Node01
• Multiple base profiles
Node agent
on a single computer server1
can be federated:
server1
– Into the same cell
– Into different cells Stand-alone After Federation
– Remain stand-alone
Figure 13-6. Application server profile WA855 / VA8551.0
Notes:
Use the application server to make enterprise applications available to the Internet or to an
intranet. Application server profiles provide a base installation.
• Application servers in the Network Deployment product can run as:
- Managed nodes in a deployment manager cell
- Stand-alone application servers
• Multiple application server profiles can be created on a single computer.
• Each application server profile can be federated into a cell.
• Multiple base profiles on a single computer can:
- Be federated into the same cell
- Be federated into different cells
- Remain a stand-alone profile

Student Notebook
An important product feature is the ability to scale up a stand-alone application server

profile by adding the application server node into a deployment manager cell. Multiple
application server processes in a cell can deploy an application that is in demand. You can
also remove an application server node from a cell to return the node to the status of a
stand-alone application server.
Each stand-alone application server can optionally have its own administrative console
application, which you use to manage the application server. You can also use the
wsadmin scripting facility to complete every function that is available in the administrative
console application.
No node agent process is available for a stand-alone application server node unless you
decide to add the application server node to a deployment manager cell. Adding the
application server node to a cell is known as federation. Federation changes the
stand-alone application server node into a managed node. You use the administrative
console of the deployment manager to manage the node. If you remove the node from the
deployment manager cell, then use the administrative console and the scripting interface of
the stand-alone application server node to manage the process.
• Unfederated Node01 containing a stand-alone application server, server1
- Deployment manager
- Federated Node02
• Node agent with connections to application servers within the node
• server2
• server3
V8.1
Student Notebook
Uempty
Deployment manager profile

• Is used to create a deployment manager process (dmgr)
• Can exist on an
independent
Cell
computer
Deployment
• Can exist on a manager
computer with
other profiles
Node01 Node02
• Provides centralized
administration of Node agent Node agent
managed application
server nodes and server1 server2 server2 server3
custom nodes as a
single cell
Figure 13-7. Deployment manager profile WA855 / VA8551.0
Notes:
The deployment manager profile provides the necessary configuration files for starting and
managing the deployment manager server that it contains. The profile also provides
everything necessary to configure and manage WebSphere Application Server profiles, or
nodes, that are in the deployment manager cell.
The deployment manager profile contains an application server with a server name of
dmgr. The dmgr application server is a special application server that contains the
deployment manager. The dmgr server contains the Network Deployment administrative
console application and the Network Deployment file transfer application. These
applications enable the distributed management of one or more WebSphere Application
Server profiles, or nodes.
The deployment manager profile:
• Is used to create a deployment manager process (dmgr)
• Can exist on an independent computer
• Can exist on a computer with other profiles

Student Notebook
• Provides centralized administration of managed application server nodes and custom

nodes as a single cell
- Deployment manager with connections to two nodes
- Federated Node01:
• server1
• server2
- Federated Node02:
• server2
• server3
V8.1
Student Notebook
Uempty
Custom profile
• A custom profile creates a node without an application
• Automatically federated into a cell during profile creation by default
• No application
servers are created Cell
during profile creation
• Use the deployment Deployment
manager
manager administrative
console to create
servers and clusters
on the federated node Node01 Node02
• Consider a custom
profile as a Node agent Node agent
production-ready
shell, ready for server1 server2
customization to
contain your servers Custom
and applications
Figure 13-8. Custom profile WA855 / VA8551.0
Notes:
Use the custom profile, which belongs to a deployment manager cell, to make enterprise
applications available to the Internet or to an intranet under the management of the
deployment manager. A custom profile does not have its own administrative console or
scripting interface. You cannot manage the node directly with the wsadmin scripting facility.
A custom profile does not include default applications or a default server as the application
server profile does. A custom profile is an empty node. Add the node to the deployment
manager cell. Then, you can use the administrative interface of the deployment manager to
customize the managed node by creating clusters and application servers.
In summary:
• A custom profile creates a node without an application.
• A custom profile automatically is federated into a cell during profile creation by default.
In the process, the node agent process is then instantiated on the newly managed
node.
• No application servers are created during profile creation.

Student Notebook
• Use the deployment manager administrative console to create servers and clusters on
the federated node.
• Consider a custom profile as a production-ready shell, ready for customization to
contain your servers and applications.
- Deployment manager with connections to two nodes
- Federated Node01:
• server1
• server2
- Federated Node02 (custom profile):
• Node agent
• No application servers
V8.1
Student Notebook
Uempty
Creating profiles
Profile Management Tool
• Start menu (Windows only)
• Started from installation wizard
• Launch command-line tool pmt.bat
– <was_root>\bin\ProfileManagement\
– Similar command
exists for UNIX
– Wizard in First steps
console
manageprofiles
• Command-line tool
• Use manageprofiles
-silent option to create
profiles in silent mode
• Other manageprofiles
options include:
-listProfiles -delete © Copyright IBM Corporation 2013
Figure 13-9. Creating profiles WA855 / VA8551.0
Notes:
You can use the Profile Management Tool or the manageprofiles command to create
profiles.
• Profile Management Tool:
- The tool is started in several ways:
• Start menu (Windows only)
• Started from the installation wizard
• Started with the command-line tool: pmt.bat
- In <was_root>/bin/ProfileManagement/
- A similar command exists for UNIX
• The wizard is available from the First steps console
- The graphic displays the Profile Management Tool Environment Selection window.
Five environments can be selected from the listing:

Student Notebook
• Cell (deployment manager and a federated application server)

• Management
• Custom profile
• Secure proxy (configuration-only)
The Profile Management Tool refers to profiles as environments because selecting
cell results in creating two profiles: a deployment manager profile and a federated
application server profile. There is really no such thing as a cell profile. It is just a fast
way to build a cell. Additionally, there is no such thing as a management profile. There
are three types of management profiles: administrative agent, deployment manager,
and job manager.
• manageprofiles
- manageprofiles is a command-line tool.
- You can use the manageprofiles -silent option to create profiles in silent mode.
- Other manageprofiles options include: -create, -listProfiles, and -delete
- The graphic displays the following example:
manageprofiles -create -profileName profile3 -profilePath "C:\Program
Files\IBM\WebSphere\Appserver\profiles\profile3" -templatePath
"C:\Program Files\IBM\WebSphere\Appserver\ profileTemplates\default"
-nodeName was8host01Node03 -cellName washost01Cell03 -hostname
was8host01
The resulting output produces the following message:
"INSTCONFSUCCESS: Success: Profile profile3 now exists."
Profiles can be silently created:
• As part of a silent WebSphere installation process
• Manually by using the -silent option with the pctWindow utility
Silent creation of profiles requires a response file, which should be customized:
• Dmgr: responsefile.pct.NDdmgrProfile.txt
• Application Server: responsefile.pct.NDStand-aloneProfile.txt
• Custom: responsefile.pct.NDmanagedProfile.txt
V8.1
Student Notebook
Uempty
Profile Management Tool: Launch and create

1 Start the Profile
Management Tool
y Started from:
- First steps or
Windows Start
menu >
WebSphere
Customization
Toolbox
- Command-line
y Click Launch Profile
Management Tool
to manage profiles
2
Create a profile
y Existing
profiles are
shown
y Click Create
Figure 13-10. Profile Management Tool: Launch and create WA855 / VA8551.0
Notes:
1. To create a profile, launch the Profile Management Tool.
- The tool can be started:
• Following installation, if selected on the installation results window; the Profile
Management Tool welcome window displays
• From Windows Start menu by clicking Start > Programs > IBM WebSphere >
Application Server Network Deployment V8.5 > Profile Management Tool
• From the command line with pmt.bat
- As soon as it is started, click Launch Profile Management Tool to manage profiles.
2. The Profile Management Tool provides a listing of existing profiles and an option to
create a profile.
- The profile list displays existing profiles. In the example, profile1 is shown.
- To begin the process of creating a profile, click Create.

Student Notebook
Profile Management Tool: Environment and server type

Environment Selection
3 y A profile is associated with an environment type
y Following panels vary by environment
y Example follows creation of a deployment
manager
4
Server Type Selection
y Administrative agent
y Deployment manager
y Job manager
Figure 13-11. Profile Management Tool: Environment and server type WA855 / VA8551.0
Notes:
3. The Environment Selection window allows you to choose the type of environment that is
associated with your new profile. A profile is associated with one of seven environment
types.
- Cell (deployment manager and a federated application server)
A cell environment creates two profiles: a management profile with a deployment
manager and an application server profile. The application server is federated to the
cell of the deployment manager.
- Management
A management profile provides the server and services for managing multiple
application server environments. The administrative agent manages application
servers on the same computer. The Network Deployment edition also includes a
deployment manager for tightly coupled management and a job manager for loosely
coupled management of topologies that are distributed over multiple computers.
- Application server
An application server environment runs your enterprise applications. WebSphere
V8.1
Student Notebook
Uempty Application Server is managed from its own administrative console and functions
independently from all other application servers.
- Custom profile
A custom profile contains an empty node, which does not contain an administrative
console or servers. The typical use for a custom profile is to federate its node to a
deployment manager. After federating the node, use the deployment manager to
create a server or a cluster of servers within the node.
- Secure proxy (configuration-only)
A secure proxy configuration-only profile is for use with a DMZ secure proxy server.
You cannot start the secure proxy server on the Network Deployment installation.
This configuration-only profile is intended to be used only to configure the profile by
using the administrative console.
4. When you select the management environment, the Server Type Selection window is
displayed. You can select one of three types of management servers to create.
- Administrative agent
An administrative agent provides management capabilities for multiple stand-alone
application servers. An administrative agent can manage only the application
servers that exist within the same installation on one computer.
- Deployment manager
A deployment manager provides management capabilities for multiple federated
nodes. A deployment manager can manage nodes that span multiple systems and
platforms. A single deployment manager can manage a node, and the node must be
federated to the cell of that deployment manager.
- Job manager
A job manager provides management capabilities for multiple stand-alone
application servers, administrative agents, and deployment managers. The job
manager can manage nodes that span multiple systems and platforms. If a job
manager manages a node or nodes, other job managers can also manage those
nodes.

Student Notebook
Profile Management Tool: Options
Profile Creation Options 5

y Typical profile creation uses
default configuration settings
y Advanced profile creation allows
you to accept default settings or
specify your own
6
Optional Application Deployment
y Deploy the administrative
console
Figure 13-12. Profile Management Tool: Options WA855 / VA8551.0
Notes:
5. Configuration values can be assigned based on default configuration values, or you can
specify your own configuration values. The Profile Creation Options window allows you
to choose which option best fits your needs.
- Typical profile creation
This option creates an application server profile that uses default configuration
settings. The Profile Management Tool assigns unique names to the profile, node,
and host. The tool also assigns unique port values.
The administrative console and the default application are installed. You can
optionally select whether to enable administrative security.
The tool might create a system service to run the application server, which depends
on the operating system of your computer and the privileges that are assigned to
your user account.
Typical profile creation is the default.
V8.1
Student Notebook
Uempty - Advanced profile creation

This option uses default configuration settings to create an application server or
specifies your own values for settings, such as the location of the profile and names
of the profile, node, and host.
You can assign your own port values. You can optionally choose whether to deploy
the administrative console and sample applications, and create a web server
definition.
There is an option to run the application server as a system service, which depends
on the operating system of your machine and the privileges that are assigned to
your user account.
6. From the Optional Application Deployment window, you can select the applications to
deploy to the WebSphere Application Server environment that is being created. The
options available from this window depend on the type of profile you are creating. In the
example, a deployment manager profile is being created. There is only one option to
choose for this type of profile.
- Deploy the administrative console (recommended)
This option installs a web-based administrative console that manages the
application server. Deploying the administrative console is suggested, but if you
clear this option, the information center provides detailed steps for deploying it after
the profile exists. This option is selected by default.

Student Notebook
Profile Management Tool: Names and location
7
Profile Name
and Location
8
Node, Host, and
Cell Names
Figure 13-13. Profile Management Tool: Names and location WA855 / VA8551.0
Notes:
7. From the Profile Name and Location window, the profile name and profile directory
path are specified. The directory that is named contains the files for the runtime
environment, such as commands, configuration files, and log files.
- Profile name
The default name can be changed as you choose.
- Profile directory
The default directory can be changed as you choose.
- Depending on the profile that being created, more options can be specified by
selecting the appropriate check box. In this example, a deployment manager profile
has one option.
• Make this profile the default
Each installation of WebSphere Application Server always has one default
profile. Commands that run without referring to a specific profile use the default
profile.
V8.1
Student Notebook
Uempty 8. The Node, Host, and Cell Names window allows you to specify:
- Node name
A node name is used for administration. If the node is federated, the name must be
unique within the cell.
- Host name
A host name is the Domain Name System (DNS) name (short or long) or the IP
address of the computer.
- Cell name
A cell name is a logical name for the group of nodes that the deployment manager
manages.

Student Notebook
Profile Management Tool: Security
9
Specify Administrative Security
y User name and password
Figure 13-14. Profile Management Tool: Security WA855 / VA8551.0
Notes:
9. From the Administrative Security window, choose whether to enable administrative
security. If enabled, the administrative user that is specified is created in a repository
within the application server. After profile creation finishes, you can add more users,
groups, or external repositories.
- Enable administrative security
Check this box to enable administrative security.
- User name
If enabling administrative security, provide a user name for administrative security.
- Password
If enabling administrative security, provide a password. The password that you enter
must be confirmed before proceeding.
V8.1
Student Notebook
Uempty
10 Security Certificate
(Part 1)
y Create or import a
default personal
certificate
y Create or import a
root signing
certificate
Notes:
10. From the Security Certificate (Part 1) window, choose whether to create a default
personal certificate and root signing certificate, or import them from keystores. To create
new certificates, proceed to security certificate (part 2) and provide more certificate
information. To import existing certificates from keystores, locate the certificates; then
proceed to security certificate (part 2) and verify the certificate information.
- There are two options for a default personal certificate:
• Click Create a new default personal certificate:
If this option is chosen, you provide certificate information about the Security
Certificate (part 2).
• Click Import an existing default personal certificate and provide the following
details:
- Path
Specify the directory location of the default personal certificate.

Student Notebook
- Password
Specify the password for the default personal certificate.
- Keystore type
There are four keystore types to choose from the list:
JKS
JCEKS
PKCS12
CMSKS
- Keystore alias
- There are two options for a root signing certificate:
• Click Create a new root signing certificate:
If this option is chosen, you provide certificate information about the Security
Certificate (part 2) window.
• Click Import an existing root signing certificate and provide the following
details:
- Path
Specify the directory location of the root signing certificate.
- Password
Specify the password for the root signing certificate.
- Keystore type
There are four keystore types to choose from the list:
JKS
JCEKS
PKCS12
CMSKS
V8.1
Student Notebook
Uempty
11
Security Certificate
(Part 2)
Notes:
11. On the Security Certificate (Part 2) window, you can modify the certificate information to
create new certificates during profile creation. If you are importing certificates from
keystores, use the information to verify whether the selected certificates contain the
appropriate information.
- The following information must be provided for a default personal certificate (a
personal certificate for this profile, public and private key):
• Issued to distinguished name
The default distinguished name is: cn="computer IP address",
ou="host_name"Node01Cell,ou="host_name"Node01,o=ibm,c=US
• Issued by distinguished name
The default distinguished name is: cn="computer IP address",ou=Root
Certificate,ou="host_name"Node01Cell,ou="host_name"Node01,o=ibm,
c=US

Student Notebook
• Expiration period in years

The default is one year. You can choose 1–15 years.
- The following information must be provided for a root signing certificate (a personal
certificate for signing other certificates, public and private key):
• Expiration period in years
The default is 15 years. You can choose between 15, 20, and 25 years.
- The default keystore password must be specified. The default password, WebAS, is
supplied in the password field and in the confirmation field.
The default value for the keystore is documented in the information center and
should be changed to protect the security of the keystore files and SSL
configuration.
- If you make a mistake after making any configuration changes, you can always
restore the default values by clicking Restore Defaults.
V8.1
Student Notebook
Uempty
Profile Management Tool: Ports and Windows service

12
Review port value
assignments
13
Specify Windows
service option
Figure 13-17. Profile Management Tool: Ports and Windows service WA855 / VA8551.0
Notes:
12. The port values assignment window lists the values of the ports that the application
server uses. The values that define the ports do not conflict with other profiles in the
current installation.
- Three options are available for you to choose ports:
• Manually enter the port value for each port.
• Click Default Port Values to populate the port values with the default port
values.
• Click Recommended Port Values to populate the port values based on
suggested values that the Profile Management Tool calculates.
Another installation of WebSphere Application Server or other programs might use the
same ports. To avoid runtime port conflicts, verify that each port value is unique. If the
Profile Management Tool detects conflicts, a window displays at the top of the window
and list the ports for which activity is detected.

Student Notebook
13. From the Windows Service Definition window, choose whether to use a Windows
service to run WebSphere Application Server. Windows services can start and stop
WebSphere Application Server, and configure startup and recovery actions.
- The check box Run the application server process as a Windows service is
selected by default. If you do not want to run the application server as a Windows
service, clear the check box.
- If you are running the application server process as a Windows service, two logon
options are available. The user account that is specified must be able to log on as a
service.
• Log on as a Local system account
• Log on as a specified user account
You must provide a user name and password for this option.
- Select the Startup type:
• Automatic
• Manual
• Disabled
V8.1
Student Notebook
Uempty
Profile Management Tool: Results and exit

14
Profile Creation Summary
15
Profile Creation
Complete
y Option to start the
First steps
console
Figure 13-18. Profile Management Tool: Results and exit WA855 / VA8551.0
Notes:
14. When all Profile Management Tool windows are completed, the Profile Creation
Summary window displays.
- The summary information is based on the selections you made previously.
- Review the summary for correctness before proceeding with the profile creation.
15. Review the results that are shown on the Profile Creation Complete window. If you want
to launch the First steps console, click the Launch the First steps console check box.
The First steps console is then started when you click Finish.
The window also displays information that is based on the type of profile that was
created. In the figure above, the window provides information about an application
server.
When you click Finish from the profile creation complete window, you are returned to
the Profile Management tool welcome window. The profile that you created is now
shown in the profile listing. You can continue to create more profiles or exit the tool. To
exit the Profile Management Tool, click File > Exit.

Student Notebook
Profile creation: Command-line tool

The manageprofiles script supports a number of functions:
• Create new stand-alone application server profiles
manageprofiles –create
• List all profiles

manageprofiles –listProfiles
• Delete profiles
manageprofiles –delete –profileName
Figure 13-19. Profile creation: Command-line tool WA855 / VA8551.0
Notes:
Use the manageprofiles command to create, delete, augment, back up, and restore
profiles, which define runtime environments. The manageprofiles script supports a number
of functions:
Create new stand-alone application server profiles:
• manageprofiles -create
An example is:
manageprofiles -create -profileName profile3 -profilePath "C:\
Program Files\IBM\WebSphere\Appserver\profiles\profile3" -templatePath
"C:\Program Files\IBM\WebSphere\Appserver\profileTemplates\default"
-nodeName was8host01Node03 -cellName washost01Cell03 -hostname was8host01
If successful, the output displays the message: "INSTCONFSUCCESS: Success:
Profile3 now exists."
V8.1
Student Notebook
Uempty List all profiles:

• manageprofiles -listProfiles
An example is:
• manageprofiles -listProfiles
The output displays a list of profiles, such as: [profile1, DmgrProfile, profile2,
profile3]
Delete profiles:
• manageprofiles -delete -profileName
Here is an example:
• manageprofiles -delete -profileName profile3
The output displays the following message if successful: INSTCONFSUCCESS: Success:
The profile no longer exists.
Deleting a profile leaves a number of files behind, including the logs directory. To
delete all of these files, the profile must be deleted manually.

Student Notebook
Directory structure bin directory holds the

profile specific tools and
scripts
config directory holds

all the configuration files
for the profile
Installable applications
Installed applications
Logs
Profile
root Properties
System applications
Uninstaller for product

Figure 13-20. Directory structure WA855 / VA8551.0
Notes:
The following file paths are default locations. You can install the product and other
components or create profiles in any directory where you have write access. Multiple
installations of WebSphere Application Server products or components require multiple
locations.
• WebSphere Application Server: /usr/IBM/WebSphere/AppServer
• Profile root: <was_root>/profiles/
• Profiles: <was_root>/profiles/profile_name
• System applications: <was_root>/systemApps
• Uninstaller for the product: <was_root>/uninstall
The directory of each profile contains the same standard directories, which include:
• bin 
The bin directory holds the profile-specific tools and scripts.
V8.1
Student Notebook
Uempty • config 
The config directory holds all the configuration files for the profile.
• installableApps 
The installableApps directory holds applications that can be associated with the
profile, but are not currently installed.
• installedApps 
The installedApps directory holds all installed applications for the profile.
• logs 
The logs directory holds all log files that are associated with the profile.
• properties 
The properties directory holds properties files that are associated with the profile.

Student Notebook
Server commands review

• WebSphere commands are profile aware
– There is a -profileName option on many WebSphere commands
– Or issue the commands from the appropriate directory:
<profile_root>\<profile_name>\bin
• If no profile is used, the default profile is assumed

– There can be only one default profile
– Unless otherwise manually set, the first profile that is created is the default
profile
• Examples (from <was_root>\bin):

– startServer server1 -profileName profile1
– startManager -profileName DmgrProfile
– stopServer server1 (assumes default profile)
Figure 13-21. Server commands review WA855 / VA8551.0
Notes:
WebSphere commands are profile aware. There is a -profileName option on many
WebSphere V8 commands to specify that the profile or the command can be issued from
the appropriate directory without specifying a profile name. For example:
<profile_root>/<profile>/bin
If no profile is specified, the default profile is assumed. Keep in mind that there can be only
one default profile. Unless otherwise manually set, the first profile that is created is the
default profile. It is suggested that you always specify the name of the profile.
Examples of server commands include:
startServer server1 -profileName profile1
startManager -profileName DmgrProfile
stopServer server1
V8.1
Student Notebook
Uempty
Profile precautions
When multiple profiles are created
on a single computer, be careful:
• Use the correct profile bin
directory to perform:
– startServer
– stopServer
– serverStatus
• Be aware of possible port conflicts

for node agents and application
servers
• There can be multiple server1
instances on a single computer
• Ensure that consistent host names
within a computer are used
Figure 13-22. Profile precautions WA855 / VA8551.0
Notes:
When multiple profiles are created on a single computer, be careful:
• Use the correct profile bin directory for the following commands:
startServer
stopServer
serverStatus
• Be aware of possible port conflicts for node agents and application servers. The graphic
displays a list of ports that are shown in the administrative console for a resource.
• There can be multiple server1 instances on a single computer.
• Ensure that consistent host names within a computer are used.
Be careful when using the Profile Management Tool. It is possible that it preinstalls a
default host name by adding the default DNS suffix to the short machine name, which
can cause problems if other profiles used only the short host name.

Student Notebook
It does not matter which form is used (short name or fully qualified name), on the
condition that the name is used consistently. For example, was85host and
was85host.ibm.com are different.
V8.1
Student Notebook
Uempty
Deployment manager console versus stand-alone console
Stand-alone
Deployment manager
• Deployment manager administrative console
has more functions for administration of the
cell
Figure 13-23. Deployment manager console versus stand-alone console WA855 / VA8551.0
Notes:
The deployment manager administrative console provides more tasks for administration of
a cell that the stand-alone administrative console does not provide. The example
demonstrates a few differences between the deployment manager and stand-alone
administrative consoles.
• Under Servers
The deployment manager provides more server task options for managing clusters,
DataPower, and core groups.
• Under System administration
The deployment manager provides management tasks that are associated with
administering a cell, nodes, node agents, and node groups.

Student Notebook
Common command-line tools

• In several directories:
– <was_root>\bin
– <profile_root>\<profile_name>\bin
• Tools include:
Command Function
addNode Add a node to a cell
syncNode Synchronize a node with the cell configuration
removeNode Remove a node from a cell
cleanupNode Cleans up a node configuration from the cell repository
startNode Start the node agent
stopNode Stop the node agent
startManager Start the deployment manager
stopManager Stop the deployment manager

Figure 13-24. Common command-line tools WA855 / VA8551.0
Notes:
Several tools are commonly used in a cell environment. The command-line tools are in
more than one directory:
<was_root>\bin
<profile_root>\<profile_name>\bin
The tools include:
• addNode 
The addNode command incorporates an application server installation into a cell.
Depending on the size and location of the new node you incorporate into the cell, this
command can take a few minutes to complete.
• syncNode 
The syncNode command forces a configuration synchronization to occur between the
node and the deployment manager for the cell in which the node is configured.
• removeNode 
The removeNode command returns a node from a Network Deployment distributed
V8.1
Student Notebook
Uempty administration cell to a stand-alone application server installation. The removeNode

command removes the node-specific configuration from the cell. This command does
not uninstall any applications that are installed as the result of running an addNode
command.
• cleanupNode 
The cleanupNode command cleans up a node configuration from the cell repository.
Use this command to clean up a node if you have a node that is defined in the cell
configuration, but the node no longer exists.
• startNode 
The startNode command reads the configuration file for the node agent process and
constructs a launch command. You do not have to use a user name and password with
the startNode command because this command starts a server process but does not
invoke an MBean method.
• stopNode 
The stopNode command reads the configuration file for the Network Deployment node
agent process and sends a Java Management Extensions (JMX) command that tells
the node agent to shut down. By default, the stopNode command waits for the node
agent to complete shutdown before it returns control to the command line.
• startManager 
The startManager command starts the deployment manager. You do not have to use
a user name and password with the startManager command because this command
starts a server process but does not invoke an MBean method.
• stopManager 
The stopManager command stops the deployment manager. It sends a Java
Management Extensions (JMX) command to the manager to shut down. By default, the
stopManager command waits for the manager to complete the shutdown process
before it returns control to the command line.

Student Notebook
Adding a node to a cell

• Add a node to a cell by using: Cell
– Administrative console, or
– addNode command-line tool
Deployment
• Adding a node to a cell includes: manager
– Creation of a backup of
current configuration
– Connection to the Node01 Node01
deployment manager
– Configuration of the Node agent
server1
node agent
– Addition of
server1
applications of node
to cell configuration
Before federation After federation
• After the node has
been added:
– Use startNode to start the node agent
– Use syncNode to synchronize a node
Figure 13-25. Adding a node to a cell WA855 / VA8551.0
Notes:
The process of adding a node to a cell is known as federation. The process of federation
creates a managed node with an application server and a node agent that belongs to a
deployment manager cell.
A node is added to a cell by using:
• The deployment manager administrative console, or
• The addNode command-line tool
The process of adding a node to a cell includes:
• Creation of a backup of the current configuration
• Connection to the deployment manager
• Configuration of the node agent
• Addition of applications of the node to the cell configuration
After the node is added to the cell, the following commands can be used:
V8.1
Student Notebook
Uempty • startNode to start the node agent

• syncNode to synchronize a node
The graphic describes the process of adding a node to a cell with the following topology:
• An unfederated node that includes a stand-alone application server
• Following federation:
- A cell encapsulating:
• Deployment manager with connection to the node agent for the newly managed
node
• Node agent with connection to the application server of the node

Student Notebook
Adding a node
• Deployment manager administrative
console
• Command line
addNode dmgr_host [dmgr_port] [-profileName profilename]
[-conntype type] [-excludesecuritydomains true | false] [-includeapps]
[-startingport portnumber] [-portprops qualified_filename]
[-nodeagentshortname name] [-nodegroupname name]
[-includebuses] [-registerservice] [-serviceusername name]
[-servicepassword password] [-coregroupname name] [-noagent]
[-statusport 1231] [-quiet] [-nowait] [-logfile filename] [-replacelog]
[-trace] [-username uid] [-password pwd] [-localusername localuid]
[-localpassword localpwd] [-help]
Figure 13-26. Adding a node WA855 / VA8551.0
Notes:
A node can be added to a cell by one of two methods:
• Deployment manager administrative console:
- From the navigation tree, expand System administration. Click Nodes > Add
Node.
• Command line:
V8.1
Student Notebook
Uempty - The addNode command is used to add a node to a cell. The command syntax is:
addNode dmgr_host [dmgr_port] [-profileName profilename]
[-conntype type] [-excludesecuritydomains true | false] [-includeapps]
[-startingport portnumber]
[-portprops qualified_filename] [-nodeagentshortname name]
[-nodegroupname name] [-includebuses] [-registerservice]
[-serviceusername name] [-servicepassword password]
[-coregroupname name] [-noagent] [-statusport 1231] [-quiet] [-nowait]
[-logfile filename] [-replacelog] [-trace] [-username uid] 
[-password pwd] [-localusername localuid]
[-localpassword localpwd] [-help]
- Here is an example:
• Add profile profile4 to the cell managed by profile dmgr01:
addNode dmgr01 8879 -profileName profile4

Student Notebook
Managed versus unmanaged nodes

• Managed nodes
– Use node agent or administrative agent to manage their servers
– Application server process runs within the deployment manager cell
• Unmanaged nodes
– Node agent or administrative agent does not manage its servers
– A stand-alone application server is an unmanaged node
– Commonly used for web servers
Figure 13-27. Managed versus unmanaged nodes WA855 / VA8551.0
Notes:
Nodes can be managed or unmanaged. Both application servers and supported web
servers can be on unmanaged or managed nodes.
• Managed nodes
- Node agent or administrative agent is used to manage its servers
- Application server process runs within the deployment manager cell
• Unmanaged nodes
- Node agent and administrative agent do not manage their servers
- A stand-alone application server is an unmanaged node
- Commonly used for web servers
V8.1
Student Notebook
Uempty
Cell topology
• Cell topology can be
viewed through the
– From
System Administration >
Cell >
Local Topology
Figure 13-28. Cell topology WA855 / VA8551.0
Notes:
The deployment manager administrative console can be used to view the topology of a cell.
The topology page is used to set the discovery protocol for an existing cell. A cell is a
configuration concept, a way for an administrator to logically associate nodes according to
whatever criteria make sense in the administrator’s organizational environment.
To view the cell topology, expand System Administration from the navigation tree. Click
Cell > Local Topology.

Student Notebook
Configuring synchronization
From the node agent

detail page, click
service
Figure 13-29. Configuring synchronization WA855 / VA8551.0
Notes:
The file synchronization service runs in the deployment manager and node agent. The
service ensures that configuration changes made to the cell repository are propagated to
the appropriate node repositories.
The deployment manager administrative console is used to configure the file
synchronization service. Configuration is set for each node agent.
To configure file synchronization, expand System administration from the navigation tree.
Click Node agents and click the appropriate node agent to set the configuration. Under
Additional Properties, click File synchronization service.
The file synchronization page includes the following properties:
• Enable service at server startup
Specifies whether the server attempts to start the file synchronization service. This
setting does not cause a file synchronization operation to start. This setting is enabled
by default.
V8.1
Student Notebook
Uempty • Synchronization interval

Specifies the number of minutes that elapse between synchronizations. Increase the
time interval to synchronize files less often. Decrease the time interval to synchronize
files more often.
• Automatic synchronization 
Specifies whether to synchronize files automatically after a designated interval. When
this setting is enabled, the node agent automatically contacts the deployment manager
every synchronization interval to attempt to synchronize the configuration repository of
the node with the master repository owned by the deployment manager.
If the automatic synchronization setting is enabled, the node agent attempts file
synchronization when it establishes contact with the deployment manager. The node
agent waits the synchronization interval before it attempts the next synchronization.
• Startup synchronization
Specifies whether the node agent attempts to synchronize the node configuration with
the latest configurations in the master repository before starting an application server.
The default is to not synchronize files before starting an application server. Enabling the
setting ensures that the node agent has the latest configuration but increases the
amount of time it takes to start the application server.
• Exclusions
Specifies files or patterns that should not be part of the synchronization of configuration
data. Files in this list are not copied from the master configuration repository to the
node, and are not deleted from the repository at the node.

Student Notebook
Remove a node from a cell

• Use the removeNode command to remove a node from a cell
– Restores stand-alone configuration of the node from a backup
– The removeNode command is equivalent to using the Remove Node
action
• Use the cleanupNode (Force Delete) command to force the
removal of a node from a cell
– Used to clean up a node that is defined in the cell configuration, but no longer
exists
– The cleanupNode command is equivalent to using the Force Delete
action
Figure 13-30. Remove a node from a cell WA855 / VA8551.0
Notes:
The removeNode command returns a node from a cell to a stand-alone application server
installation. The removeNode command removes the node-specific configuration from the
cell. When a node is removed from a cell, the profile reverts to the configuration it had
before it was federated into a cell. Any applications or configuration changes that were
made while it was part of a cell are lost.
• Restores stand-alone configuration of the node from a backup.
• The node can be removed through the deployment manager administrative console.
Expand System administration. Click Nodes. Select the node to remove and click
Remove Node.
The cleanupNode command cleans up a node configuration from the cell repository.
• The command is used to clean up a node that is defined in the cell configuration, but no
longer exists.
V8.1
Student Notebook
Uempty • A node can be cleaned up through the deployment manager administrative console.
Expand System administration. Click Nodes. Select the node to clean up and click
Force Delete.

Student Notebook
Synchronization
• Synchronize
– Uses the normal synchronization optimization algorithm
– Node and cell configuration might still be out of synchronization after operation
• Full Resynchronize
– Clears all synchronization optimization settings
– No mismatch between node and cell configuration
Figure 13-31. Synchronization WA855 / VA8551.0
Notes:
If you add a managed node or change a managed node configuration, synchronize the
node configuration. Synchronization can be done by selecting the nodes and clicking
Synchronize or Full Resynchronize.
Clicking either option sends a request to the node agent for that node to complete a
configuration synchronization immediately, instead of waiting for the periodic
synchronization to occur. This action is important if automatic configuration synchronization
is disabled. It is also important if the synchronization interval is set to a long time, and a
configuration change is made to the cell repository that must replicate to that node.
Settings for automatic synchronization are on the File Synchronization Service page.
• Synchronize
Synchronize requests that a node synchronization operation processes by using the
normal synchronization optimization algorithm. This operation is fast, but might not fix
problems from manual file edits that occur on the node. It is still possible for the node
and cell configuration to be out of synchronization after this operation is done.
V8.1
Student Notebook
Uempty • Full Resynchronize

Full Resynchronize clears all synchronization optimization settings and completes
configuration synchronization anew, so there is no mismatch between node and cell
configuration after this operation is done. This operation can take longer than the
Synchronize operation.
• syncNode command
The syncNode command forces a configuration synchronization to occur between the
node and the deployment manager for the cell in which the node is configured.
The node agent server runs a configuration synchronization service that maintains
synchronization between the configuration the node and that of the master cell. If the
node agent is unable to run because of a problem in the node configuration, you can
use the syncNode command to complete a synchronization. When the node agent is
not running, it can be used to force the node configuration back in sync with the cell
configuration. If the node agent is running and you want to run the syncNode
command, you must first stop the node agent.

Student Notebook
Managing a web server: Adding a node to a cell

• Create an unmanaged node for defining remote web servers
– From System administration > Nodes > Add node
Figure 13-32. Managing a web server: Adding a node to a cell WA855 / VA8551.0
Notes:
An application server works with a web server to handle requests for dynamic content,
such as servlets, from web applications. A web server uses a web server plug-in to
establish and maintain persistent HTTP and HTTPS connections with an application server.
Before beginning work to manage the web server, make sure that the appropriate plug-in
file is installed on your web server.
The first step to establish communication with a web server is to create a node to manage
the web server. Within a cell topology, unmanaged nodes are typically used to manage web
servers.
To create an unmanaged node:
1. From the navigation tree, expand System administration. Click Nodes > Add node.
2. Click Unmanaged node and click Next.
3. From the new node page, provide the general properties for the unmanaged node:
V8.1
Student Notebook
Uempty - Name:
Specifies a logical name for the node. The name must be unique within the cell.
- Host name:
Specifies the host name of the unmanaged node that is added to the configuration.
- Platform type:
Specifies the operating system on which the unmanaged node runs. Valid options
are:
• Windows
• AIX
• HP-UX
• Solaris
• Linux
• OS/400
• z/OS
4. Click OK.

Student Notebook
Managing a web server: Add the web server

3
• Add the web server to the created node
– From Servers > Server Types >
Web servers > New
Figure 13-33. Managing a web server: Add the web server WA855 / VA8551.0
Notes:
When a node is created that is used to manage the web server, a web server definition can
be created. The deployment manager administrative console can be used to create the
web server definition. The web server definition adds the web server to the newly created
node.
To create a web server definition: from the navigation tree, expand Servers > Server
Types. Click Web servers > New.
1. The first step is to identify the node and web server.
- Select node:
Identifies the node that manages the web server.
- Server name:
Server name is the logical name of the server. The name must be unique within the
node.
- Type:
Type identifies the web server vendor type.
V8.1
Student Notebook
Uempty 2. Select the web server template that you want to correspond to the web server you want
to create. The template is based on the type of web server you chose previously.
3. Enter the properties for the new web server.
- Port:
The port that the web server uses.
- Web server installation location:
The location of the web server installation. It is required for IBM HTTP Server only.
- Service name:
Specifies the Microsoft Windows operating system service name of the web server.
- Plug-in installation location:
The fully qualified path for the location of the plug-in configuration file.
- Application mapping to the web server:
Web server application mapping. The options are:
• All: All applications are automatically mapped to the web server.
• None: No applications are automatically mapped to the web server.
Enter the properties for the IBM Administration Server:
- Administration Server Port
- Username
- Password

Student Notebook
Managing a web server: Plug-in configuration file

• The plug-in configuration file contains routing for all applications that are
mapped to the web server
• After changes that affect routing, regenerate and propagate the plug-in
file to the web server
– From Servers > Server Types > Web servers
1. Generate
plug-in
2. Propagate
plug-in
Figure 13-34. Managing a web server: Plug-in configuration file WA855 / VA8551.0
Notes:
The plug-in configuration file contains routing for all applications that are mapped to the
web server, passing HTTP requests from a web server to WebSphere Application Servers.
The plug-in is regenerated and propagated to the web server after changes that affect
routing are made. The plug-in configuration file is automatically generated by default,
whenever the web server environment changes, with a few exceptions. For example, the
plug-in configuration file is regenerated whenever one of the following activities occurs:
• A new application is deployed on an associated application server.
• The web server definition is saved.
• An application is removed from an associated application server.
• A new virtual host is defined.
V8.1
Student Notebook
Uempty You can manually generate and propagate a plug-in configuration file for a web server from
the deployment manager administrative console. From the navigation tree, expand
Servers > Server Types. Click Web servers.
1. To generate the plug-in configuration file, select the web server whose plug-in
configuration file must be generated. Click Generate Plug-in.
When the generation is complete, a message displays to indicate that the generation
was successful. A message also indicates the directory location and name of the
plug-in configuration file. Here are some example messages:
"PLGC0005I: Plug-in configuration file = C:\Program
Files\IBM\WebSphere\AppServer\profiles\DmgrProfile\config\cells\was8host
01Cell01\nodes\ihsnode\servers\webserver01\plugin-cfg.xml
PLGC0052I: Plug-in configuration file generation is complete for the Web
server was8host01Cell01.ihsnode.webserver01"
2. To propagate the plug-in configuration file, select the web server whose plug-in
configuration file must be propagated. Click Propagate Plug-in.
When the propagation is complete, a message indicates the directory location and the
name of the plug-in configuration file that is used for propagation. The message also
indicates the directory location and name of the plug-in configuration file where the
configuration is propagated to on the web server computer. Here are some example
messages:
"PLGC0062I: The plug-in configuration file is propagated from C:\Program
Files\IBM\WebSphere\AppServer\profiles\DmgrProfile\config\
cells\was8host01Cell01\nodes\ihsnode\servers\webserver01\plugin-cfg.xml
to C:\Program Files\IBM\HTTPServer\Plugins\config\
webserver01\plug-in-cfg.xml on the Web server computer
PLGC0048I: The propagation of the plug-in configuration file is complete
for the Web server was8host01Cell01.ihsnode.webserver01"

Student Notebook
Unit summary
Notes:
V8.1
Student Notebook
Uempty
1. Which managed processes can be part of a cell?
A. Deployment manager
B. Node agent
C. Load balancer
D. Application server
2. Which profiles can be created by using the Profile Management

Tool?
A. Load balancer profile
B. Custom profile
C. Plug-in profile
D. IBM HTTP Server profile
3. All application servers have a corresponding node agent.

A. True
B. False
Notes:
1. 
2. 
3.


Student Notebook
Checkpoint answers
1. Which managed processes can be part of a cell?
Answer: A, B, and D
A. Deployment manager
B. Node agent
D. Application server
2. Which profiles can be created by using the Profile Management

Tool? Answer: B
B. Custom profile
3. All application servers have a corresponding node agent.

Answer: B
B. False
Notes:
V8.1
Student Notebook
Uempty
Exercise 9
Creating a federated cell

Notes:

Student Notebook
Exercise objectives
• Create a deployment manager profile
• Back up the deployment manager configuration
• Use the deployment manager administrative console
• Federate a node into the deployment manager cell
• Create a custom profile
• Create an unmanaged web server node
• Use the administrative console to start and stop a web server
• Map an application to a web server
Notes:
V8.1
Student Notebook
Uempty Unit 14. Workload management

In this unit, you learn workload management principles and how
WebSphere Application Server can be configured to participate in
workload management.

• Define workload management
• Create clusters and cluster members
• Compare clustered configurations
• Explain how weights are used in workload management
• Describe failover scenarios
• Describe the role of the HTTP plug-in in workload management
• Explain session management
• Configure distributed session management

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 14. Workload management 14-1

Student Notebook
Unit objectives
Notes:
V8.1
Student Notebook
Uempty
Topics
• Workload management concepts
• Clusters and cluster members
• Routing concepts and session affinity
• Failover
• Session persistence
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 14.1.Workload management concepts

Student Notebook
Workload management
concepts

Figure 14-3. Workload management concepts WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is workload management (WLM)?

• Sharing requests across multiple application servers
• Configuration options that improve:

– Performance: improve response time for requests
– Scalability: grow capacity as the number of users increases
– Load balancing: allocate workload proportionately among available resources
– Availability: applications are still available if a server fails
Figure 14-4. What is workload management (WLM)? WA855 / VA8551.0
Notes:
There are numerous potential definitions for the term workload management. Within the
context of the WebSphere Application Server, what is meant generically is to spread the
work between different hosts. This feature can provide for better performance, scalability,
load balancing, and availability.

Student Notebook
What can be workload managed? (1 of 2)

HTTP server
HTTP
requests
Plug-in
HTTP server
Load balancer
Plug-in

Servlet
requests Web
HTTP server container

Plug-in
Web
container
Figure 14-5. What can be workload managed? (1 of 2) WA855 / VA8551.0
Notes:
Within a standard application server topology, there are frequently three points where WLM
occurs. The first point is where a load balancer spreads the work among numerous web
servers. The second point is where the web server plug-in spreads work among numerous
application servers, or more specifically, web containers.
V8.1
Student Notebook
Uempty
What can be workload managed? (2 of 2)
WebSphere
Web IIOP EJB Application
container container
Server
EJB
requests WebSphere
Web IIOP EJB Application
container container
Server
Java client
Figure 14-6. What can be workload managed? (2 of 2) WA855 / VA8551.0
Notes:
The third point where work can be spread is between the EJB clients and the EJB
containers. This third point does not usually occur because the EJB client (in most cases,
the web container) is typically in the same JVM as the EJB container. This topology forces
all traffic to stay within the same JVM. The other cases are when a web container is placed
in a different JVM and then the EJB container (not common), and when a stand-alone Java
client is being used (again, not common).

Student Notebook
V8.1
Student Notebook
Uempty 14.2.Clusters and cluster members

Student Notebook
Clusters and cluster

members

Figure 14-7. Clusters and cluster members WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Clusters
1 Create a cluster by
using an existing
server (or create a
blank cluster)
WebSphere
Application 2 Install applications
Server or make other
changes
Template
3 Create cluster
members
Cluster member Cluster member Cluster member

1 2 3
Figure 14-8. Clusters WA855 / VA8551.0
Notes:
Creating more throughput within a cell cannot be done by installing one application on
multiple application servers. This situation can possibly create conflicts with the
namespace and the plug-in. Clusters allow for the same application server to have multiple
copies within a single cell. They provide a single point of management, automatic workload
management, and failover.

Student Notebook
Clusters and cluster members

• Clusters are a set of application servers that have the same
applications installed, and are grouped logically for workload
management
– Applications that are installed to the cluster are automatically propagated to
the cluster members
• Creation of a cluster
– Can use an existing server to become the first cluster member
– Additional cluster members are created from templates
• Cluster members are similar to “clones” in previous WebSphere

Application Server versions in that they:
– Run the same applications
– Share workload
– Can be centrally administered
Figure 14-9. Clusters and cluster members WA855 / VA8551.0
Notes:
You can create a blank cluster and then install applications in it. It is also possible to have a
cluster that is based on an existing application server. At any point, cluster members can
be created within a cell. These cluster members are actually application servers, but they
are associated with the cluster. At any point, then, more applications or configuration
changes can be made to the cluster, and those changes are pushed out to all of the cluster
members.
V8.1
Student Notebook
Uempty
Configurations: Vertical scaling

• Might provide better performance with multiple processors
• Provides process level failover
Computer A Node agent
Cluster member
HTTP server 1
Cluster
Plug-in
Cluster member
2
Plug-in
configuration
Figure 14-10. Configurations: Vertical scaling WA855 / VA8551.0
Notes:
Cluster members can be scaled vertically. You can put multiple cluster members on the
same node (or computer). Although this practice might not increase throughput (assuming
that one cluster member uses the computer fully), it does provide process level failover.

Student Notebook
Configurations: Horizontal scaling

• Supports server failover
HTTP server
Plug-in
Computer A Node agent

Computer B Node agent
Cluster member Cluster member

1 2
Cluster
Figure 14-11. Configurations: Horizontal scaling WA855 / VA8551.0
Notes:
Cluster members can be scaled horizontally. You can put cluster members on different
computers. This method not only increases throughput but also provides system level
failover.
V8.1
Student Notebook
Uempty
Configurations: Vertical and horizontal scaling

Computer A
• Performance and
failover Node agent
Cluster member
1
Cluster member
2
HTTP server
Cluster
Computer B
Plug-in
Cluster member
3
Cluster member
4
Node agent
Figure 14-12. Configurations: Vertical and horizontal scaling WA855 / VA8551.0
Notes:
Scaling both vertically and horizontally combines both system and process level failover.

Student Notebook
Creating a cluster (1 of 4)
• In console, select Servers > Clusters > WebSphere application
server clusters and click New
• Enter cluster
name
• Check options
– Prefer local
– Configure
HTTP session
memory-to-
memory
replication
• Click Next
Figure 14-13. Creating a cluster (1 of 4) WA855 / VA8551.0
Notes:
This diagram shows the first step of the cluster creation wizard.
V8.1
Student Notebook
Uempty
• Create the first cluster member that is based on:
– A server template
– An existing server
– Converting an existing server
– An empty cluster
• Enter member name
• Select node
• Enter weight
• Click Next
Notes:
When creating a cluster, several options must be specified. These options include what to
base the new cluster on (a template, an existing application server, converting an existing
application server) and things like the cluster member name, the weight, the node, and
other items.

Student Notebook
Notes:
In this example, the option to create the first cluster member that is based on an existing
server is selected.
V8.1
Student Notebook
Uempty
1. Enter Member name
2. Select node
1
3. Set weight
2
4. Check options:
3
• Generate unique
HTTP ports 4
(default) 5
5. Click Add Member
6. Repeat to create
other cluster members
7. Click Next
8. Click Finish on Summary
screen
Notes:
After the first cluster member is created, you can create more members. This screen shows
the options for creating more cluster members.

Student Notebook
Installing enterprise applications to a cluster

1. Select a cluster as the target
3. Click Apply
2. Map to web servers,

if applicable
Figure 14-17. Installing enterprise applications to a cluster WA855 / VA8551.0
Notes:
This procedure follows the same steps as installing to a base server except:
1. You select a cluster as the target, rather than a server.
2. And possibly map to web servers.
V8.1
Student Notebook
Uempty
Controlling a cluster
• Start the cluster • Status

– Start starts all – Started: all servers are started
servers together – Partial Start: some servers are started
– Ripplestart starts – Stopped: all the servers are stopped
servers one at a time – Partial Stop: some servers are stopped
Figure 14-18. Controlling a cluster WA855 / VA8551.0
Notes:
If ripplestart is used on a running cluster, each application server in the cluster is stopped
one at a time, and restarted.
The screen capture shows a partially stopped cluster.

Student Notebook
Cluster members
• Clusters can also be started (or stopped) by merely starting all
application servers that are members
• Cluster members are just application servers
Figure 14-19. Cluster members WA855 / VA8551.0
Notes:
Cluster members can be started individually by starting the application servers.
V8.1
Student Notebook
Uempty
Modification of clusters
• Use the administrative console or wsadmin
• What can be changed in a cluster?

– Cluster member settings: weights, prefer local
– Install or update applications
– Application server settings: cluster members are application servers and the
normal application server settings can be modified
• After modifying the cluster:

– Save the configuration and resynchronize
– Regenerate the HTTP server plug-in and redistribute it if necessary
Figure 14-20. Modification of clusters WA855 / VA8551.0
Notes:
Individual cluster member settings include Weight and Prefer local. Applications can be
installed or updated on a cluster. Changes to application server settings must be made to
each cluster member individually.

Student Notebook
V8.1
Student Notebook
Uempty 14.3.Routing concepts and session affinity

T

Student Notebook
Routing concepts and

session affinity

Figure 14-21. Routing concepts and session affinity WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Basic routing algorithms

• Routing decision points
1. Load balancer
2. HTTP Server plug-in
3. WLM-aware EJB client
– Includes web
Name Java
container, Java client
service
client, EJB
Routing
Load table 3
balancer 1 HTTP server 2
HTTP(S) HTTP(S) Web IIOP EJB

container container
Plug-in WebSphere WebSphere

Application Server Application Server
Routing
Plug-in
table
configuration
Figure 14-22. Basic routing algorithms WA855 / VA8551.0
Notes:
1. Load balancer:
- The routing decision table is stored internally
- Configured by using the Load Balancer tool
- Multiple intelligent routing options
2. HTTP server plug-in:
- The plugin-cfg.xml file defines routing
- Configured by using administrative console, or wsadmin
- Default is weighted round robin
3. WLM-aware EJB client:
- Includes web container, Java client, EJB
- Name service then supplies routing table
- Configured by using administrative console, or wsadmin

Student Notebook
- Options:
• Prefer local: yes or no
V8.1
Student Notebook
Uempty
HTTP session management

• HTTP is a stateless protocol
• Sessions allow you to maintain state information across a series of
HTTP requests from the same client
– For example, maintain shopping cart until checkout
JSESSIONID
cookie HTTP server
Session object
Servlet 123:A
123:A SessionID: 123
requests
Web CustName: Bob
HTTP container ProductID: xyz
Plug-in Cluster member 1
ID - A
Web client
Figure 14-23. HTTP session management WA855 / VA8551.0
Notes:
HTTP is a stateless protocol.
Sessions allow you to maintain state information across a series of HTTP requests from the
same client (for example, maintaining your shopping cart until checkout).
The Java servlet specification defines the session management process for web
applications.
The session manager stores session information, and sends the client a unique clone ID
and session ID through:
• A cookie in the HTTP header, or
• URL rewriting in a parameter on links or forms

Student Notebook
Session affinity
JSESSIONID
cookie
Session object
123:A 123:A
SessionID: 123
Servlet Web CustName: Bob
container ProductID: xyz
requests
Cluster member 1
Web client ID - A
HTTP server
JSESSIONID
HTTP
cookie
Plug-in Session object
345:B 345:B
SessionID: 345
Web CustName: Fred
container ProductID: abc
Cluster member 2
Web client ID - B
Figure 14-24. Session affinity WA855 / VA8551.0
Notes:
An application can retain state information for a user’s session in memory. Other servers in
the cluster might not have this information.
The HTTP server plug-in routes subsequent servlet requests consistently to the same
application server after the session is created, by using a clone ID passed with the session
ID in a cookie or URL.
V8.1
Student Notebook
Uempty
JSESSIONID cookie
• The JSESSIONID cookie is used to help manage sessions
– The plug-in
uses the data
to find which
clone has
affinity
– The web
container uses
it to find the
right http
session object
HTTP session ID
Epoch number Clone ID
Figure 14-25. JSESSIONID cookie WA855 / VA8551.0
Notes:
The JSESSIONID cookie includes three main parts:
• The HTTP session ID
• The clone ID and
• The epoch number
The clone ID allows the plug-ins to identify which cluster member (or clone) holds the
session object. The HTTP session object allows the application server to find the object
that is specific to that particular request. And finally, the epoch number allows the web
container to make sure that the cached HTTP session object is not stale.
The format of the cookie can change in certain cases. For example, if memory-to-memory
session replication is used, the format is entirely different. Also, if the session is failed over
to another web container, there can be a list of clone IDs instead of just one.

Student Notebook
WebSphere session affinity

Clone ID
JSESSIONID=00018320953:123
Web
client HTTP
servlet
requests Cluster member
1
321
321
123 Cluster member
345 2
476 123 Clone ID
HTTP server
Load
plug-in
balancer Cluster member
3
345
321
123
345 Cluster member
476 4
476
HTTP server
plug-in © Copyright IBM Corporation 2013
Figure 14-26. WebSphere session affinity WA855 / VA8551.0
Notes:
WebSphere session affinity has the following features:
• Session cookie is generated
• Uses clone ID to allow affinity on first hit
• Plug-ins know how to route to correct clone ID
• Can be turned off by removing clone IDs from plug-in file
• Format for the JSESSIONID cookie changes when using memory-to-memory
replication
V8.1
Student Notebook
Uempty
Plug-in
• Based on the data in the plugin-cfg.xml file, the plug-in is able
to route sticky requests to the correct application server
– If the application server is unavailable, the request is rerouted to the next
application server
– This new application server now has affinity
– The session information that is held within the web container does not fail over
unless session failover is configured
– An unavailable application
server is marked as down HTTP server WebSphere
Application
for a certain amount of time
Server
(default is 2 minutes)
– After that time, the server is
tried again
Plug-in WebSphere
– The plugin-cfg.xml file Application
is checked for updates every Server
60 seconds so new application
servers are automatically
Plug-in configuration
brought into the active list
Figure 14-27. Plug-in WA855 / VA8551.0
Notes:
Based on the data in the plugin-cfg.xml file, the plug-in is able to route sticky requests
to the correct application server. If the application server is unavailable, the request is
rerouted to the next application server; this new application server now has affinity. The
session information that is held within the web container does not fail over unless session
failover is configured. An unavailable application server is marked as down for a certain
amount of time (default is 2 minutes); after that time, the server is tried again. The
plugin-cfg.xml file is checked for updates every 60 seconds; so new application servers
are automatically brought into the active list.

Student Notebook
Plugin-cfg.xml (1 of 2)
Figure 14-28. Plugin-cfg.xml (1 of 2) WA855 / VA8551.0
Notes:
This slide shows the contents of a plugin-cfg.xml file where the CloneID is highlighted.
V8.1
Student Notebook
Uempty
Plugin-cfg.xml (2 of 2)
Figure 14-29. Plugin-cfg.xml (2 of 2) WA855 / VA8551.0
Notes:
The slide shows the portion of the contents of a plugin-cfg.xml file that contains
JSESSIONID cookie information.

Student Notebook
Interpreting the plugin-cfg.xml file (1 of 4)

Find a UriGroup that has a regular expression matching the request
<Config
<Config ...>
...>
...
...
<<UriGroup
UriGroup Name="default_host_PlantsCluster_URIs">
Name="default_host_PlantsCluster_URIs">
...
...
<Uri Name="/PlantsByWebSphere/*
<Uri Name=" /PlantsByWebSphere/*"" .../>
.../>
...
...
<Route
<Route UriGroup="default_host_PlantsCluster_URIs“
UriGroup="default_host_PlantsCluster_URIs“
ServerCluster="PlantsCluster"/>
...
...
<ServerCluster
<ServerCluster Name="PlantsCluster"
Name="PlantsCluster" LoadBalance="Round
LoadBalance="Round Robin"
Robin" ...
... >>
<Server
<Server CloneID="17shqbbrq"
CloneID="17shqbbrq" LoadBalanceWeight="2"
LoadBalanceWeight="2" ...>
...>
<Transport
<Transport Hostname="was85host"
Hostname="was85host" Port="9080"
Port="9080" Protocol="http"/>
Protocol="http"/>
<Transport
Port="9443" Protocol="https">
Protocol="https">
...
...
<Server
<Server CloneID="17shqbcf9"
CloneID="17shqbcf9" LoadBalanceWeight="2"
...>
<Transport
Protocol="http"/>
<Transport
Protocol="https">
Figure 14-30. Interpreting the plugin-cfg.xml file (1 of 4) WA855 / VA8551.0
Notes:
Application requests are mapped to a UriGroup by matching one of the UriGroup’s regular
expressions.
V8.1
Student Notebook
Uempty

Find the Route element that maps to the UriGroup name
<Config
<Config ...>
...>
...
...
<UriGroup Name="default_host_PlantsCluster_URIs
<UriGroup Name=" default_host_PlantsCluster_URIs">
">
...
...
<Uri
<Uri Name="/PlantsByWebSphere/*"
Name="/PlantsByWebSphere/*" .../>
.../>
...
...
<<Route UriGroup="default_host_PlantsCluster_URIs
Route UriGroup=" default_host_PlantsCluster_URIs““
...
...
<ServerCluster
<ServerCluster Name="PlantsCluster"
Name="PlantsCluster" LoadBalance="Round
Robin" ...
... >>
<Server
...>
<Transport
Protocol="http"/>
<Transport
Protocol="https">
...
...
<Server
...>
<Transport
Protocol="http"/>
<Transport
Protocol="https">
Notes:
All of the application requests that are mapped to a UriGroup are routed based on the
information in a Route XML element that corresponds to the UriGroup.

Student Notebook

Find the ServerCluster element that maps to the Route’s ServerCluster
<Config
<Config ...>
...>
...
...
<UriGroup
<UriGroup Name="default_host_PlantsCluster_URIs">
...
...
<Uri
.../>
...
...
<Route
ServerCluster="PlantsCluster
ServerCluster=" PlantsCluster"/>
"/>
...
...
<<ServerCluster Name="PlantsCluster
ServerCluster Name=" PlantsCluster"" LoadBalance="Round
LoadBalance="Round Robin“
Robin“ >>
<Server
...>
<Transport
Protocol="http"/>
<Transport
Protocol="https">
...
...
<Server
...>
<Transport
Protocol="http"/>
<Transport
Protocol="https">
Notes:
The Route XML element determines which ServerCluster element to use for selecting
cluster members to forward the request to.
V8.1
Student Notebook
Uempty

Server selected based on algorithm, affinity, and protocol
...
...
<UriGroup
<UriGroup Name="default_host_PlantsCluster_URIs">
...
...
<Uri
.../>
</UriGroup>
</UriGroup>
...
...
<Route
...
...
<ServerCluster
<ServerCluster Name="PlantsCluster" LoadBalance="Round
Name="PlantsCluster" LoadBalance=" Round Robin
Robin““ ……
<<Server CloneID="17shqbbrq
Server CloneID=" LoadBalanceWeight="2
17shqbbrq"" LoadBalanceWeight=" 2"" ...>
...>
<Transport Hostname="was85host
<Transport Hostname=" Port="9080
was85host"" Port=" Protocol="http
9080"" Protocol=" http"/>
"/>
was85host"" Port=" Protocol="https
9443"" Protocol=" https">
">
...
...
<<Server CloneID="17shqbcf9
Server CloneID=" LoadBalanceWeight="2
17shqbcf9"" LoadBalanceWeight=" 2"" ...>
...>
was85host"" Port=" Protocol="http
9081"" Protocol=" http"/>
"/>
was85host"" Port=" Protocol="https
9444"" Protocol=" https">
">
Notes:
After a ServerCluster XML element is determined, a Server in the ServerCluster is chosen
based on algorithm, affinity, and protocol.

Student Notebook
Weighted round robin

• Both the plug-in and EJB routing use weighted round robin by default
– The plug-in can be configured to use random instead
• Initial weights are given to each cluster member
– The weights default to a value of 2
– The maximum weight that is allowed in the console is 20
• An internal routing table is set up for each plug-in
– Using a greatest common divisor (GCD), the plug-in attempts to reduce the
weight values for each cluster member
HTTP server
Server 1
Weight = 8 x/GCD
Plug-in Routing table initial values*
Server 1 Server 2
Server 2 EJB ORB
Weight = 2 client 4 1
WLM
plug-in
Figure 14-34. Weighted round robin WA855 / VA8551.0
Notes:
The default routing option for both the plug-in and the ORB is called weighted round robin.
Each server is assigned a weight that is then reduced by dividing all values by the GCD
(greatest common divisor). These new values are then inserted into a table (for both the
plug-in and the ORB) that is used to track the distribution between the available servers.
V8.1
Student Notebook
Uempty
Weighted routing example with no affinity

Server 1 Server 2 • Example 1: only new hits (no
Start: 4 1 session affinity)
Request 1 3 1 • As requests come into the plug-
in, round robin is used to
Request 2 3 0
distribute the hits
Request 3 2 0
• Each request decrements the
Request 4 1 0 value in the internal table
Request 5 0 0 • As soon as a server has a count
Reset: 4 1 of zero, no new hits are sent to
that server
• As soon as all servers have a
value of zero, the values are all
As soon as all reset
values <=0, a
reset is done Reset adds • Results:
initial values
of 4, 1 – server1: 80%
– server2: 20%
Figure 14-35. Weighted routing example with no affinity WA855 / VA8551.0
Notes:
This algorithm is used for both the plug-in and ORB WLM.

Student Notebook
Weighted routing example with affinity

• Example 2: combination of hits Server 1 Server 2
• Sticky hits are those hits that have affinity
• Property IgnoreAffinityRequests Start: 4 1
(default = true) causes the internal table Request 1 3 1
to not decrement the count for sticky
hits Request 2* 3 1
• As requests come into the plug-in, Request 3 3 0

weighted round robin is used Request 4** 3 0
• Each non-sticky request decrements the
Request 5 2 0
value in the table
• Sticky hits are routed to the server for Request 6 1 0
which they have affinity Request 7** 1 0
• As soon as a server has a count of zero,
Request 8 0 0
no new hits are sent to that server
• As soon as all servers have a value Reset: 4 1
of zero, the values are all reset
• Results: Forced hits due to sticky sessions:
Server 1: *
– server1: around 80% Server 2: **
– server2: around 20%
Figure 14-36. Weighted routing example with affinity WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Weighted routing example with counting affinity

• Example 3: combination of hits Server 1 Server 2
• Setting IgnoreAffinityRequests
to false Start: 4 1
• As requests come into the plug-in, Request 1 3 1
weighted round robin is used
Request 2* 2 1
• All requests decrement the weight
values in the table Request 3 2 0
– Sticky hits are routed to the server Request 4** 2 -1
for which they have affinity
Request 5 1 -1
– Weighted round robin is used to
route non-sticky hits Request 6** 1 -2
• As soon as a server has a count of Request 7 0 -2
zero, no new hits are sent to that server
• As soon as all servers have a value of Reset: 4 -1
zero or less, the values are all reset
– A reset adds the modified server weights (4 and 1) to the Forced hits due to
servers repeatedly until all servers are greater than zero sticky sessions:
• Results (can vary): Server 1: *
Server 2: **
Figure 14-37. Weighted routing example with counting affinity WA855 / VA8551.0
Notes:

Student Notebook
Routing alternative: Random

• An alternative algorithm to weighted round robin is random
– Sticky hits still go to the appropriate application server
– New hits are randomly distributed
Figure 14-38. Routing alternative: Random WA855 / VA8551.0
Notes:
An alternative to the weighted round robin is random. This attribute can be set in the plug-in
properties (as show in the diagram). Hits that have affinity are still routed to the appropriate
server.
V8.1
Student Notebook
Uempty
Using Intelligent Management

• The plug-in can be configured to retrieve dynamic weights rather than
using static weights
• Information is added to the plugin-cfg.xml file about how to retrieve the
dynamic weights
• Enabled using:
– Servers > Server Types > Web servers > [web server name] > Additional
Properties > Intelligent Management
• More information in Intelligent Management Unit
Figure 14-39. Using Intelligent Management WA855 / VA8551.0
Notes:
The plug-in can be configured to use Intelligent Management features of WebSphere
Application Server. When Intelligent Management is enabled, the plug-in communicates
with management servers in the cell to obtain the current state of the application servers.
The current state includes server weights that are calculated based on the current
performance characteristics of the application servers. More detail on this topic is included
in the unit on Intelligent Management.

Student Notebook
V8.1
Student Notebook
Uempty 14.4.Failover

Student Notebook
Failover

Figure 14-40. Failover WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Failover
What happens if there is a failure?
Name Java
service client
Routing
Load HTTP table 3
balancer 1 server 2
HTTP HTTP Web IIOP EJB

container container
HTTPS HTTPS
Plug-in WebSphere WebSphere
Application Server Application Server
Routing Plug-in
table configuration
Figure 14-41. Failover WA855 / VA8551.0
Notes:
The next few slides cover what happens during failures at:
1. The load balancer
2. The web server
3. The web container

Student Notebook
Edge Components failover

• Load balancer can be
HTTP server
paired with a backup Load
server balancer
• Topology is active or Plug-in
standby HTTP server
– One computer does all

the work
– The other waits for a Plug-in
failure to begin handling HTTP server
routing
Load
balancer
Plug-in
Figure 14-42. Edge Components failover WA855 / VA8551.0
Notes:
If a load balancer fails, a standby load balancer can take over. No session information is
lost.
V8.1
Student Notebook
Uempty
HTTP server failover

• Multiple HTTP servers provide coverage
• Load Balancer can route around a failed HTTP server
• All HTTP servers handle load before failover
• HTTP plug-in
– Every plug-in knows about
all web containers
HTTP server
– Session key
contains address WebSphere
Application
of server Server
– Sessions get Plug-in
properly routed
HTTP server
Load WebSphere
balancer Application
Server
Plug-in
Figure 14-43. HTTP server failover WA855 / VA8551.0
Notes:
If a web server fails, any other web server can deal with the request since each plug-in is
aware of all of the downstream application servers. If there is affinity to a specific
application server, the request still ends up going to the correct application server (based
on the JSESSIONID cookie) even if a web server is unavailable.

Student Notebook
Web container failover

• HTTP server plug-in • What about in-flight sessions?
– Detects failure of web – Sessions can be persisted to
containers database
– Marks container as unavailable – Sessions can be replicated in
– Tries next cluster member in memory
the cluster
Web EJB
HTTP server container container
HTTP(S)
Memory-memory
Plug-in replication, or
Web IIOP EJB session database
container container
Figure 14-44. Web container failover WA855 / VA8551.0
Notes:
If a plug-in detects that a web container is unavailable, it marks that container as down and
does not make more attempts to communicate with it for 2 minutes. After 2 minutes, it
attempts to communicate with that server. If it is still unavailable, it is marked down for 2
minutes again, and the process continues.
This algorithm allows each plug-in to dynamically deal with web containers that either
become unexpectedly unavailable or are taken offline. At the same time, when new cluster
members are added and the plugin-cfg.xml file is generated and propagated, the
plug-in automatically knows about the new containers and dynamically adds them to the
pool.
V8.1
Student Notebook
Uempty
EJB container failover

• Client code and ORB plug-in can route to next available cluster
member
• Failure occurs before any work is initiated on the cluster member:
– ORB automatically reroutes EJB request
– If no other cluster member available, throws NO_IMPLEMENT exception
• Failure occurs after EJB method call initiated work:
– System exceptions
are thrown
IIOP
– Client must Web EJB
determine appropriate container container
recovery action
Java
– Reissue request or IIOP client
rollback transaction
– If NO_IMPLEMENT
exception is thrown, no Web EJB
container container
recovery is possible
Figure 14-45. EJB container failover WA855 / VA8551.0
Notes:
When an EJB container fails, the failover depends on the initial type of failure. If the error
was in reaching the EJB container, then WebSphere fails over to another possible EJB
container. However, if the initial call was successful, but the response timed out, then the
programmer must try again.

Student Notebook
V8.1
Student Notebook
Uempty 14.5.Session persistence

Student Notebook
Session persistence

Figure 14-46. Session persistence WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Session persistence
Session objects are cached in server memory by default, and therefore
are lost if server fails
Three methods to enable session persistence:
• Database
– JDBC data source is used to persist session objects
– DB2 included in package for session persistence
• Memory-to-memory replication
– Data Replication Service (DRS) is used to copy sessions to another server
• eXtreme Scale servlet filter
– Entitlement included with WebSphere Application Server
Memory-memory
Session database eXtreme Scale servlet filter
replication
WebSphere eXtreme
WebSphere WebSphere Scale grid
Application
Application Application
Server
Server Server Container
server
WebSphere
WebSphere WebSphere Container
Application
Application Session Application server
Server
Server database Server
Figure 14-47. Session persistence WA855 / VA8551.0
Notes:
If your application cannot tolerate loss of session information, session persistence can be
enabled. The three choices are database, memory-to-memory, and eXtreme Scale. The
database approach has greater cost, but provides persistence to a database.
Memory-to-memory can still fail if all copies of the session are lost. The eXtreme Scale
solution can be more robust.
A number of settings can be used to affect the balance between failover and performance.
This topic is described in upcoming slides.

Student Notebook
Session configuration: Memory-to-memory

• Configuring
memory-to-memory
session replication
– Found under
WebSphere application
servers >
<servername> >
Session management >
Distributed environment
settings
– Select Memory-to-memory
replication
– Configure the replication
domain
Figure 14-48. Session configuration: Memory-to-memory WA855 / VA8551.0
Notes:
Replication modes:
• Server mode: Stores copies of other WebSphere Application Server sessions and not
to send out copies of any session that are created in that particular server
• Client mode: Broadcasts or sends out copies of the sessions it owns and not to receive
backup copies of sessions from other servers
• Both mode: Simultaneously broadcasts or sends out copies of the sessions it owns
and acts as a backup table for sessions that other WebSphere Application Server
instances own
V8.1
Student Notebook
Uempty
Session configuration: Replication domains

Creating replication domains:
• Created during cluster
creation
• Or Environment >
Replication Domains >
New
To configure replication
domains after creation:
• Through the administrative
console, select the
Replication domain under
Environment >
Replication domains
• Select the replication domain
• Select the number of replicas
– Single replica
– Entire domain
– Specified
Figure 14-49. Session configuration: Replication domains WA855 / VA8551.0
Notes:
Single replica means that for every session object, one backup copy is stored on a different
server for failover. It is also possible to back up the sessions on every member of the
domain. This practice does not scale as well because every member must store every
other member’s session objects. However, it means that the chance for a successful
failover is higher.
Depending on the needs of the application and the tolerance for failure, it is possible to
tune the number of members that back up every session object.

Student Notebook
Database persistence configuration
1. Create database in DBMS

2. Create data source: Resources > JDBC >
Data sources
3. Select Database in Distributed
environment settings page
– Found under
WebSphere Application Servers >
<servername> >
Session management
4. Configure database settings
Figure 14-50. Database persistence configuration WA855 / VA8551.0
Notes:
Database persistence configuration requires specifying a data source. This picture shows
the console database replication and data source configuration settings.
V8.1
Student Notebook
Uempty
Tuning session persistence

• Session persistence can be
tuned to favor performance or
failover
• Accesses through
Servers >
<servername> >
Session management >
Distributed environment
settings >
Tuning parameter
Figure 14-51. Tuning session persistence WA855 / VA8551.0
Notes:
Session persistence can be tuned so that it is more appropriate for failover or for
performance. These settings allow administrators to choose if they want to have greater
failover ability (at the price of performance) or have better performance (at the price of
having failover).

Student Notebook
eXtreme Scale persistence configuration

• Create splicer.properties file
– Provides eXtreme Scale configuration details
• “Splice” HTTP servlet filter into a Web application

– Run script
“addObjectGridFilter.[bat|sh]
<location of ear/war file>
<location of splicer.properties file>”
• Deploy application
Figure 14-52. eXtreme Scale persistence configuration WA855 / VA8551.0
Notes:
To activate the HTTP servlet filter for WebSphere eXtreme Scale, you must “splice” the
filter into your application. eXtreme Scale includes a script, addObjectGridFilter, to add the
filter to your application. The script takes two parameters: the absolute path to the
application to be spliced, and the location of a file that contains various configuration
properties. The splicer utility modifies the application’s deployment descriptor, web.xml,
with parameters that control how the filter interacts with the WebSphere eXtreme Scale
grid.
Follow the normal procedure to deploy the new application to your application server. The
servlet filter is started as part of the application initialization.
V8.1
Student Notebook
Uempty
Unit summary
Notes:

Student Notebook
1. A WebSphere cluster member is what type of process?
A. An application server
B. A web server
C. An edge server
D. A proxy server
2. The creation of a cluster can be based on which of the following?

A. An application
B. An application server
C. An enterprise application
D. An application manager
3. Having session affinity means that session information is not lost

during failover.
A. True
B. False
Notes:
1. 
2. 
3.
V8.1
Student Notebook
Uempty
Checkpoint answers
1. A WebSphere cluster member is what type of process?
A. An application server
2. The creation of a cluster can be based on which of the following?

B. An application server
3. Having session affinity means that session information is not lost

during failover.
B. False
Notes:

Student Notebook
Exercise 10
Clustering and workload

management

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Create a cluster and add cluster members
• Map modules to clusters and web servers
• Test load balancing and failover between two cluster members
• Configure a data replication domain for session management
Notes:

Student Notebook
V8.1
Student Notebook
Uempty Unit 15. Introduction to WebSphere Messaging

This unit provides an overview of WebSphere Messaging through the
presentation of several sample topologies.

• Describe what WebSphere Messaging is and how it is used
• Describe messaging components such as JMS providers, the
service integration bus (SIBus), and messaging engines
• Configure resources to support messaging applications such as
queues, topics, and connection factories
• Implement various clustered messaging engine policies for high
availability and scalability
• Create links to foreign buses and WebSphere MQ
• Describe how JMS and WebSphere MQ use the SIBus to support
application messaging services

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 15. Introduction to WebSphere Messaging 15-1
Student Notebook
Unit objectives
• Describe messaging components such as JMS providers, the service
integration bus (SIBus), and messaging engines
Notes:
V8.1
Student Notebook
Uempty
Topics
• Overview of messaging concepts
• Messaging engine clustering
• SIBus and messaging engine topologies
• Additional messaging considerations
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 15.1.Overview of messaging concepts
Student Notebook
Overview of messaging
concepts

Figure 15-3. Overview of messaging concepts WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is JMS?
• The Java Message Service (JMS) is an API for accessing enterprise
messaging systems
• WebSphere Application Server V8.5.5 supports JMS 1.1 as part of the

Java Platform, Enterprise Edition (Java EE) 6 specification
• The Java Message Service allows Java EE applications to

asynchronously send and receive business data and events
• JMS supports two styles of asynchronous messaging:

– Point-to-point (queues)
– Publish and subscribe (topics)
Figure 15-4. What is JMS? WA855 / VA8551.0
Notes:
JMS defines an API; it is not an implementation.
JMS defines some interfaces for applications to use. It is up to someone else to provide the
implementation under those interfaces.
The implementation is delivered as a JMS provider.
Student Notebook
JMS applications
• The JMS specification defines the interfaces that JMS applications use
• JMS applications do not need to know how the interfaces are
implemented
– Java objects that implement the interface are returned through JNDI lookups
– The implementation objects are vendor-specific
– The implementation objects use vendor-specific properties to access the
messaging resources
Messaging
JMS client provider
resources
JMS
applications Resource
Implementation
object
JNDI
namespace
Figure 15-5. JMS applications WA855 / VA8551.0
Notes:
The application that uses the JMS API is called a JMS client.
The JMS client must get actual Java objects that implement the JMS interfaces. The
objects are stored in JNDI, and have vendor-specific properties and behaviors.
When the object is retrieved from JNDI, the standard JMS APIs can be used to work with
the vendor-specific resources. If the client is deployed to a different JMS provider, the JNDI
lookup remains the same, but the object that is returned is different. The client uses the
same JMS API calls, but the object has different behaviors for working with the different
vendor resources.
V8.1
Student Notebook
Uempty
What is a JMS provider?

• A JMS provider is the implementation of the JMS API
• The following JMS providers are supported:
– WebSphere Application Server default messaging provider
– V5 default messaging provider
– WebSphere MQ messaging provider
– Generic JMS provider: Click New and define a third-party provider
Figure 15-6. What is a JMS provider? WA855 / VA8551.0
Notes:
• WebSphere Application Server default messaging provider: This fully featured
messaging provider comes free with WebSphere Application Server. It is a robust and
stable messaging platform that can handle point-to-point queues, topics in a
publish/subscribe environment, and web service endpoints.
• WebSphere MQ messaging provider: WebSphere MQ is the premier messaging
middleware that IBM provides. Use WebSphere MQ when you require advanced
messaging facilities and options. WebSphere MQ existed much earlier than the
WebSphere Application Server default messaging provider and is available on many
platforms, supporting many programming languages. It is fully JMS-compliant and has
a large client base.
• Generic JMS provider: This provider is the catch-all for any external messaging
providers other than WebSphere MQ. Although WebSphere Application Server works
with any JMS-compliant messaging provider (after it is defined to WebSphere), there
can be only limited administrative support in WebSphere. This approach is suggested
only if you have an existing investment in a third-party messaging provider because
Student Notebook
much greater support is available in the WebSphere Application Server default

messaging provider and WebSphere MQ messaging provider.
• WebSphere Application Server V5 default messaging provider: The WebSphere
Application Server V5 default messaging provider is supported for migration purposes
only.
V8.1
Student Notebook
Uempty
Basic messaging flow

Destination
Producer message message Consumer
Administration
• Producers send or put messages to destinations

• Consumers receive or get messages from destinations
• Destinations are managed points of communication:
– JMS queues
– JMS topics (publish and subscribe)
– Web service endpoints
• While the messaging flow is inherently asynchronous, it can be used
to provide synchronous communication
– Uses temporary REPLY-TO destinations
Figure 15-7. Basic messaging flow WA855 / VA8551.0
Notes:
Producers send messages to destinations. Consumers get messages from destinations.
Destinations are managed points of communication. Destinations can be JMS queues,
JMS topics (publish/subscribe), or web service endpoints.
Student Notebook
WebSphere default messaging

• Default messaging is the JMS provider that is delivered with
• Messaging capabilities are fully integrated into the WebSphere

Application Server
• Based on service integration bus (SIBus) technology
• Complements and extends WebSphere MQ and WebSphere

Application Server
• Other WebSphere products use default messaging
Figure 15-8. WebSphere default messaging WA855 / VA8551.0
Notes:
Messaging capabilities are fully integrated in the WebSphere Application Server platform.
Messaging is integrated with application server management, including security and high
availability. Default messaging is fully compliant with JMS V1.1.
Default messaging complements and extends WebSphere MQ and WebSphere Application
Server. You can share and extend messaging family capabilities and interoperate with
WebSphere MQ.
Other WebSphere products use default messaging such as WebSphere Enterprise Service
Bus and WebSphere Process Server. Default messaging is supported in tools by
WebSphere Integration Developer.
V8.1
Student Notebook
Uempty
Service integration bus (SIBus)

• A service integration bus is an administrative concept for configuring
and hosting messaging resources
– Buses are scoped to a network deployment (ND) cell
• An SIBus contains bus members and destinations
• Producers and consumers connect to SIBus bus members
• The SIBus manages communication with destinations

– The SIBus can hold messages for a destination until a consumer becomes
available
Figure 15-9. Service integration bus (SIBus) WA855 / VA8551.0
Notes:
The SIBus provides the following capabilities:
• Any application can exchange messages with any other application by using a
destination to which one application sends, and from which the other application
receives.
• A message-producing application, that is, a producer, can produce messages for a
destination regardless of which messaging engine the producer uses to connect to the
SIBus.
• A message-consuming application, that is, a consumer, can consume messages from a
destination (whenever that destination is available) regardless of which messaging
engine the consumer uses to connect to the SIBus.
The SIBus supports the following types of messaging:
• Sending messages synchronously (requires the consuming application to be running
and reachable).
Student Notebook
• Sending messages asynchronously (possible whether the consuming application is

running or not and whether the destination is reachable). Both point-to-point and
publish/subscribe messaging are supported.
• Publishing events or other notifications. The SIBus itself can also generate notification
messages.
V8.1
Student Notebook
Uempty
SIBus members
• SIBus members can be:
– Application servers or clusters
• When a new bus member is defined, one or more messaging engines

are automatically created
– When adding a cluster as a bus member, more than one messaging engine
might be created
• Bus members can be added or removed from the bus

– This action effectively adds or removes messaging engines from the servers
Figure 15-10. SIBus members WA855 / VA8551.0
Notes:
SIBus members can be application servers or clusters. When a new bus member is
defined, a messaging engine (ME) is automatically created on the corresponding
application server or cluster. Bus members can be added or removed from the bus, which
effectively adds or removes messaging engines from the servers.
Student Notebook
Messaging engine (ME)

• MEs run inside the application server or cluster member, and manage
messaging resources
– A common pattern is one ME per bus member
• Each ME has a unique identity that is made up of the SIBus name and
the name of the bus member
– For example,
PlantsCluster.000-msgBus, PlantsCluster.001-msgBus
– was85hostNode01.MyServer01-MyBus
• MEs provide a connection point for clients to put or get messages
• All MEs are visible and accessible from anywhere on the bus, no
matter which ME the client has an actual network connection with
Figure 15-11. Messaging engine (ME) WA855 / VA8551.0
Notes:
One ME is automatically created for the application server or the cluster when defining a
new SIBus member (application server or cluster). Multiple MEs can be running within the
same cluster.
Within an SIBus, each ME has a unique identity, which is made up of the SIBus name and
the bus member name.
V8.1
Student Notebook
Uempty
Bus member and messaging engine

• An SIBus bus member can be a server or a cluster
• Each bus member contains at least one messaging engine (ME)
• The ME provides the runtime functions for the SIBus
Bus member
Messaging
engine
(ME)
SIBus
Figure 15-12. Bus member and messaging engine WA855 / VA8551.0
Notes:
One ME is automatically created for the application server or the cluster when defining a
new SIBus member (application server or cluster). It is possible to have multiple MEs
running within the same cluster.
Within an SIBus, each ME has a unique identity, which is made up of the SIBus name and
the server name.
Student Notebook
Message stores
• An ME requires a persistent backing store for storing recoverable
data such as messages
• Two types of message stores

– File stores (flat files in the file system)
– Data stores (relational database tables)
• Multiple MEs can share a database, but each ME has its own schema
within the database (which results in different tables)
• Derby database is used as the default data store in a stand-alone

server
• For cluster bus members, a distributed database, such as DB2, or a

shared file system is required
Figure 15-13. Message stores WA855 / VA8551.0
Notes:
The message store is a subcomponent of the messaging engine. It is used to buffer in-flight
messages and hold a number of other pieces of information (for example, records of
message delivery when delivering multiple copies of a single message).
A message store can be either persistent or nonpersistent. A persistent message store can
hold both persistent objects and volatile objects. A persistent object is state data that
survives after an engine stops for any reason. A volatile object is state data that does not
survive an ME failure, and might not survive an orderly shutdown of the messaging.
In contrast, a nonpersistent message store can hold only volatile objects; it cannot hold
persistent objects.
ME requires a persistent back-end data store, even for nonpersistent messages (for
example, spilling).
Included is support for persistence by using Derby. DB2, Oracle, and Sybase are also
supported so that customers can use an RDBMS of choice. These databases must also
V8.1
Student Notebook
Uempty offer higher performance than Derby. Starting with version 6.1, a file system data store is
also available.
The data store preserves messages and subscriptions so that they survive if the server or
messaging engine is stopped and restarted. It is also used for the overflow of the
nonpersistent messages in some quality of service (QoS) options.
Student Notebook
Messaging engine data stores

• An ME can be configured to use data source to connect to its message
store
Bus member
JDBC provider
Data
Messaging source
engine
SIBus
Figure 15-14. Messaging engine data stores WA855 / VA8551.0
Notes:
A file store or a data store can provide persistent storage.
A file store provides an environment that is easier to manage and has better performance.
In a clustered environment a shared file system must be used so all instances of
messaging engines can have access for failover purposes.
The message store preserves messages and subscriptions so that they survive if the
server or messaging engine is stopped and restarted. It is also used for the overflow of the
V8.1
Student Notebook
Uempty
Messaging engine data stores

• An ME can also use the file system for its message store
Bus member
File
Messaging system
engine
SIBus
Figure 15-15. Messaging engine data stores WA855 / VA8551.0
Notes:
A file store or a data store can provide persistent storage.
A file store provides an environment that is easier to manage and has better performance.
In a clustered environment, a shared file system must be used so all instances of
messaging engines can have access for failover purposes.
The data store preserves messages and subscriptions so that they survive if the server or
messaging engine is stopped and restarted. It is also used for the overflow of the
Student Notebook
What is a bus destination?

Ɣ A bus destination is a virtual place within an SIBus, which applications
(producers and consumers) use to exchange messages
Ɣ An SIBus destination is associated with bus members, therefore

associating it with the corresponding MEs
– MEs associated with a destination have a message point for that destination
– Allows administrator to control which message store is used for persistence
Ɣ Any destination on a bus is visible and accessible to applications

connected anywhere on the bus
Figure 15-16. What is a bus destination? WA855 / VA8551.0
Notes:
A bus destination is a virtual location within an SIBus, which applications (producers,
consumers, or both) use to exchange messages.
SIBus destinations are associated with bus members, therefore associating them with the
corresponding MEs. MEs associated with a destination have a message point for that
destination. This behavior allows the administrator to control which message store is used
for persistence.
V8.1
Student Notebook
Uempty
SIBus destinations
• A logical name which applications
use to exchange messages
• Queue
– For point-to-point messaging
• Topic space
– For publish and subscribe messaging
– Represents hierarchies of topics
• Alias
– Provide a level of abstraction
between applications and the target bus destinations that hold messages
• Foreign
– Identifies a destination on another bus
– Applications on one bus can directly access the destination on another bus
• Exception
– Automatically created for each messaging engine
Figure 15-17. SIBus destinations WA855 / VA8551.0
Notes:
SIBus defines several types of destinations. Alias and foreign destinations represent some
other destination. A chain of alias destinations ultimately must end in a real destination. A
foreign destination must refer directly to a destination on a “foreign” bus and must have the
same name as the destination on that foreign bus.
A topic space is a hierarchy of topics that are used for publish/subscribe messaging. Topics
with the same name can exist in multiple topic spaces.
Alias destinations provide a level of abstraction between applications and the underlying
target bus destinations that hold messages. Applications interact with the alias destination,
so the target bus destination can be changed without changing the application. Each alias
destination identifies a target bus destination and target service integration bus.
Applications can use an alias destination to route messages to a target destination in the
same bus or to another (foreign) bus (including across an MQLink to a queue that
WebSphere MQ provides).
The foreign destination identifies a destination on another bus so that applications on one
bus can directly access the destination on another bus.
Student Notebook
Each messaging engine has a default exception destination,

SYSTEM.DEFAULT.EXCEPTION.DESTINATION.me_name, which can be used to handle
undeliverable messages for all bus destinations that are localized to the messaging engine.
V8.1
Student Notebook
Uempty
Linking destinations to bus members

• A bus destination is associated with one or more bus members,
therefore associating it with the corresponding MEs
– Allows the administrator to control which database is used for persistence
– In most cases, a destination is associated with one ME
– Multiple MEs provide scalability
• Use a queue for point-to-point messaging

– The administrator defines a queue destination on one assigned bus member
– Each ME in that assigned bus member has a queue point where messages are
held
• Use a topic space for publish and subscribe messaging

– Every ME in the SIBus is a publication point where messages are held
Figure 15-18. Linking destinations to bus members WA855 / VA8551.0
Notes:
Messages are transported through a bus (for example, an SIBus). A bus is a virtual
messaging environment that spans servers. If you want to send or receive messages
through a bus, you must connect to it. Servers (for example, server1) can be added to a
bus, and in doing so, a messaging engine (ME) starts in that server.
SIBus destinations are defined on the bus (rather than on an ME). Queues are localized to
a particular ME (for example, messages sent to that queue are stored in a database on one
particular ME within the bus). Topic spaces (groups of topics) are localized on every ME.
A message point is the general term for the location on a messaging engine where
messages are held for a bus destination. For point-to-point messaging, the administrator
selects one bus member, an application server or cluster, as the assigned bus member that
is to implement the runtime state of a queue destination. This action automatically defines a
queue point for each messaging engine in the assigned bus member. For a queue
destination that is assigned to an application server, the messaging engine of that server
handles all messages sent to that destination, and message order is preserved.
Student Notebook
For publish/subscribe messaging, the administrator configures the destination as a topic

space (a hierarchy of topics), but is not required to select any assigned bus member for the
topic space. A topic space has a publication point that is defined automatically for each
messaging engine on the bus.
V8.1
Student Notebook
Uempty
Message points (1 of 2)
• A message point is the physical location on a messaging engine where
messages are held for a bus destination
• A message point can be a

– Queue point
– Publication point
Messaging engine
Message
point
Bus
destination Service integration bus
Figure 15-19. Message points (1 of 2) WA855 / VA8551.0
Notes:
If the bus member is an application server, a single queue point is created and associated
with the messaging engine on that application server. This messaging engine handles all of
the messages that are sent to the queue destination. In this configuration, message order
is maintained on the queue destination.
If the bus member is a cluster of application servers, a queue point is created and
associated with each messaging engine defined within the bus member. The queue
destination is partitioned across the available messaging engines within the cluster. In this
configuration, message order is not maintained on the queue destination.
Student Notebook
Message points (2 of 2)
• A queue point is the message point for a queue destination
• When creating a queue destination on a bus:

– Specify the bus member that holds the messages for the queue
– A queue point is automatically defined for each messaging engine that is
associated with the specified bus member
• A publication point is the message point for a topic space
• When creating a topic space destination:

– Creating a topic space destination automatically defines a publication point on
each messaging engine within the bus
Figure 15-20. Message points (2 of 2) WA855 / VA8551.0
Notes:
A publication point is the message point for a topic space. Creating a topic space
destination automatically defines a publication point on each messaging engine within the
bus.
It is not required to specify a bus member to hold messages for a topic space.
V8.1
Student Notebook
Uempty
SIBus destinations
• SIBus destinations are associated with one or more MEs
– Queues are explicitly assigned to a bus member
– Topic spaces are associated with all bus members
Bus member
Messaging
engine
JDBC provider
Message Data
point source
SIBus Messages
destination
SIBus
Figure 15-21. SIBus destinations WA855 / VA8551.0
Notes:
A message point is the location on a messaging engine where messages are held for a bus
destination. A message point can be a queue point, a publication point, or a mediation
point.
A queue point is the message point for a queue destination. When creating a queue
destination on a bus, an administrator specifies the bus member that holds the messages
for the queue. This action automatically defines a queue point for each messaging engine
that is associated with the specified bus member.
A publication point is the message point for a topic space. When creating a topic space
destination, an administrator is not required to specify a bus member to hold messages for
the topic space. Creating a topic space destination automatically defines a publication point
on each messaging engine within the bus.
Student Notebook
SIBus queue destinations

• Queues are visible across the entire bus
– Physically on one bus member
– Applications can connect to any ME on the bus and produce or consume
messages from a queue
– Even if the queue is associated with a different bus member
JMS JMS
producer consumer
application application
Bus member Bus member Bus member

Messaging
engine
Messaging Queue Messaging
engine point engine
SIBus
Figure 15-22. SIBus queue destinations WA855 / VA8551.0
Notes:
A particular queue destination is associated with one SIBus, and is assigned to one of the
bus members.
If the bus member is an application server, a single ME is responsible for the queue.
If the bus member is a cluster, then each of the MEs in the cluster supports operations on
the queue.
To access the queue, clients do not have to connect to the messaging engine responsible
for the queue.
In this picture, although both the producer and the consumer a connected to different MEs
from the one with the queue destination, both of the applications can access the queue.
V8.1
Student Notebook
Uempty
SIBus topic space destinations

• Each topic space is a namespace for dynamically created topics
– Topics are hierarchical: for example, A/B/C
• They are located across the whole bus as publication points
• Subscriber subscriptions are localized to a single ME
• Messages that are published anywhere on the bus are propagated only
to MEs with subscribers for the topics that are published to
JMS publisher JMS subscriber

application application
Bus member Bus member Bus member

ME ME ME
Publication Publication Publication

point point point
SIBus
Figure 15-23. SIBus topic space destinations WA855 / VA8551.0
Notes:
Topic space destinations provide support for publish/subscribe messaging.
Every ME on the bus can handle operations for the topic spaces that are defined on the
bus.
Producer applications publish messages to particular topics through a topic space
destination. To publish to a topic, publishers can use any ME that it is connected to.
Subscriber applications create subscriptions on particular topics in a topic space.
A subscription is associated with the ME to which the subscriber application is connected.
Published messages are propagated only to MEs with subscribers.
In this picture, you see that there are two subscriber applications. When a publisher creates
a message to which it is subscribed, the message is sent to the two MEs where there are
subscribers. It is not sent to the ME with no connected subscribers.
Student Notebook
Java EE access to bus members

• Java EE applications (producers, consumers) access the SIBus and
the bus members through the JMS API
• JMS defines queues and topics

– Applications access JMS destinations
– JMS destinations have JNDI names
– For example, jms/tradeQueue, jms/storeTopic
• JMS defines interfaces for accessing destinations

– ConnectionFactory: Java EE components use it to connect to the SIBus
through a messaging engine (Typically used by producer applications)
– ActivationSpec: message-driven beans use it to connect to the SIBus through a
messaging engine (Used by consumer applications)
Figure 15-24. Java EE access to bus members WA855 / VA8551.0
Notes:
JMS connection factory
Session EJBs use the connection factory to connect to a JMS provider, in this case, to
connect to the SIBus through a messaging engine. The connection factory generates
connection objects. The generated connection object holds details of how to create a
connection: for example, an IP address, port, and SSL configuration.
When it is connected to a messaging engine, the session EJB can access destinations on
the bus. The destination is not required to be associated with the messaging engine to
which it was connected. As soon as it is connected, the session EJB can connect to any
destination on the bus.
JMS ActivationSpec
Message-driven beans use the ActivationSpec to connect to the SIBus. The ActivationSpec
is a resource adapter. It requires the JNDI name of the JMS destination where messages
are consumed. The ActivationSpec invokes the MDB onMessage() method when a
V8.1
Student Notebook
Uempty message becomes available on the destination. An ActivationSpec can be created for a
queue or a topic space destination.
Student Notebook
JMS destinations
• JMS destinations are associated with SIBus destinations
• The SIBus destination implements the JMS destination function
Bus member
Messaging
engine JDBC provider
JMS queue Data

destination Queue source
point
SIBus queue
destination Messages
SIBus
Figure 15-25. JMS destinations WA855 / VA8551.0
Notes:
An administrator must create both the JMS destination and the SIBus destination. As
mentioned earlier, the message point is created automatically when the SIBus is created.
V8.1
Student Notebook
Uempty
JMS connection factory

• Producers and consumers use the JMS API to access destinations
• Java EE components (Session EJBs for example) use a JMS
connection factory to connect to the JMS provider (ME)
Bus member
EJB
JMS standard API
JMS connection
factory JDBC provider
JMS Data
destination source
Messaging
engine
SIBus
destination
(ME)
SIBus
Figure 15-26. JMS connection factory WA855 / VA8551.0
Notes:
Session EJBs can be producers or consumers. The flow is as follows. A session EJB
references a JMS connection factory. With the messaging engine and SIBus destination,
the EJB can access the JMS destination.
Other Java EE components besides session beans can use JMS connection factories
(servlets, for example).
Student Notebook
JMS ActivationSpec
• Message-driven beans (MDBs) use a JMS ActivationSpec to connect
to the JMS provider (ME)
Bus member
MDB
JMS standard API
JMS
JDBC provider
ActivationSpec
JMS Data
destination source
Messaging
engine
SIBus
destination
(ME)
SIBus
Figure 15-27. JMS ActivationSpec WA855 / VA8551.0
Notes:
An MDB is only a consumer of messages, hence the one-way arrows back to the MDB in
the diagram.
V8.1
Student Notebook
Uempty
Applications can run outside bus members

• Producers and consumers can also run outside of the server that is
hosting the ME
Producer application Consumer application
EJB MDB
JMS API JMS API
JMS JMS
ConnectionFactory ActivationSpec
JDBC provider
Bus member
JMS Data
destination source
Messaging
engine
SIBus
destination (ME)
SIBus
Figure 15-28. Applications can run outside bus members WA855 / VA8551.0
Notes:
Producers and consumers can also run outside of the server that is hosting the ME.
Student Notebook
Messaging engine
clustering

Figure 15-29. Message engine clustering WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Messaging engine policy assistance

• Administrative console feature in WebSphere Application Server
• When you add a cluster to an SIBus, you can choose one of three
predefined messaging engine policies:
– High availability
– Scalability
– Scalability with high availability
• A custom policy option is also available
Figure 15-30. Messaging engine policy assistance WA855 / VA8551.0
Notes:
The administrative console provides messaging engine policy assistance whenever you
add a cluster as a member of an SIBus. Three predefined policies can be configured: high
availability, scalability, and scalability with high availability. There is also an option to select
a custom policy, but there is no console assistance for this option.
Student Notebook
Example: High availability policy (1 of 2)

• High availability: Ensures that a single ME is always available
Existing node Existing node
Cluster
Existing
messaging
engine
(arrow
indicates
failover)
Figure 15-31. Example: High availability policy (1 of 2) WA855 / VA8551.0
Notes:
By default, only one application server in a cluster has an active messaging engine on a
bus. If the server fails, the messaging engine on another server in the cluster is activated.
This behavior provides failover, but no workload management.
The server with the active messaging engine has local access to the bus, but the rest of the
servers in the cluster access the bus remotely by connecting to the active messaging
engine. Servers accessing the bus remotely can consume asynchronous messages from a
remote messaging engine. However, by default, an instance of a message-driven bean
(MDB) deployed to the cluster can consume only from a local messaging engine.
Because everything is funneled through one messaging engine, performance might still be
an issue.
V8.1
Student Notebook
Uempty
Example: High availability policy (2 of 2)

• The ME runs on only one cluster member
– The HA manager decides which cluster member
• If the host cluster member fails, ME fails over to another cluster

member
• No failback
• By default, if the consumer app runs on the same cluster as the bus
member, only MDBs with an active ME get messages from the
destination
– You can configure all MDBs on all cluster members to receive messages
– Configure the activation specification by using the option: always activate MDBs
in all servers
Figure 15-32. Example: High availability policy (2 of 2) WA855 / VA8551.0
Notes:
The ME runs on only one cluster member; the HA Manager decides which cluster member.
If the host cluster member fails, the ME fails over to another cluster member, which
continues to host the ME even when the original cluster member is running again. There is
no failback.
By default, only MDBs on the host cluster member can get messages from the destination,
but you can configure all consumers on all cluster members to receive messages. You
must enable the option. Always activate MDBs in all servers, on the activation specification.
Student Notebook
Example: Scalability policy

• Scalability: Creates an ME for every server in the cluster
– Each ME is always hosted by its assigned server
– No failover
Existing
messaging
engines:
000 and 001
Figure 15-33. Example: Scalability policy WA855 / VA8551.0
Notes:
Each cluster member has its own ME. If one cluster member fails, its ME does not fail over
to another cluster member.
V8.1
Student Notebook
Uempty
Example: Scalability with high availability policy

• Scalability with high availability:
– Creates an ME for every server in the cluster
– One other server can host each ME (in addition to the one to which it is
assigned)
Existing messaging
engines
(arrows indicate
failover Æ and
failback Å)
Figure 15-34. Example: Scalability with high availability policy WA855 / VA8551.0
Notes:
Each server in the cluster is able to host two MEs, its own and one for the other cluster
member.
Student Notebook
SIBus and messaging

engine topologies

Figure 15-35. SIBus and messaging engine topologies WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Messaging engine topology

• You can have multiple interconnected buses in a cell or stand-alone
node (single server)
– A common pattern is to have one SIBus in a stand-alone single server
• A topology that consists of just one cluster bus member by using a high
availability policy is adequate for many applications
– This results in a single ME
• Advantages in creating more than one ME are:

– Spreading messaging workload across multiple servers
– Placing message processing close to the applications that are using it
– Improving availability in the face of system or link failure
– Accommodating firewalls or other network restrictions that limit the ability of
network hosts all to connect to a single ME
Figure 15-36. Messaging engine topology WA855 / VA8551.0
Notes:
Messaging engine topologies can have many interconnected buses in a cell or stand-alone
node (single server). A common pattern is to have one SIBus in a stand-alone single
server.
The default topology, which consists of just one ME on a bus, is adequate for many
applications.
Advantages in deploying more than one ME, and linking them together, are:
• Spreading messaging workload across multiple servers
• Placing message processing close to the applications that are using it
• Improving availability in the face of system or link failure
• Accommodating firewalls or other network restrictions that limit the ability of network
hosts all to connect to a single ME
Student Notebook
SIBus and MEs in a stand-alone server
ME-1 SIBus 1
Server1
ME-2
SIBus 2
• A stand-alone server can be a member of multiple buses

• When the server is made a bus member, a messaging engine is
created
Figure 15-37. SIBus and MEs in a stand-alone server WA855 / VA8551.0
Notes:
With a stand-alone server that is not part of a federated environment, there are not many
options for configuring SIBus topology. You can use different buses for different
applications. There is obviously no support for clustered bus members when using a
stand-alone server that is not part of a cell.
V8.1
Student Notebook
Uempty
Bus topology: Stand-alone servers
• An enterprise might deploy multiple interconnected messaging

buses for organizational reasons
– For example, separately
administered buses for each
department SIBus 1
Server1
ME-1
• A bus can connect to other
buses, which are known as
foreign buses SIBus link
• The administrator can create SIBus 2

Server2
– An SIBus link
ME-2
– A WebSphere MQ link
Figure 15-38. Bus topology: Stand-alone servers WA855 / VA8551.0
Notes:
You can also connect the buses between different stand-alone servers.
A bus can connect to other buses, which are referred to as foreign buses. If messaging
engines are on different buses, applications can use those different buses, each with its
own topology and set of resources. The inter-bus links might reflect the distribution of
buses across organizations, across departments within organizations, or perhaps the
separation of test and production facilities. Depending on the type of the foreign bus, you
create either a Service Integration Bus link or a WebSphere MQ link.
Student Notebook
SIBus and MEs in a Network Deployment cell
ServerD
ServerB SIBus 1
ME
ME
ME
ServerE
ServerA
ME ME
ServerC
SIBus 2 ServerF
ND cell
• A WebSphere Application Server ND cell can have multiple buses

• Each bus can have servers and clusters as bus members
• When a server, or cluster, is made a bus member, a messaging engine
is created
• The cell can have servers that are not bus members
Figure 15-39. SIBus and MEs in a Network Deployment cell WA855 / VA8551.0
Notes:
A typical WebSphere Application Server configuration is to define a single bus for each
WebSphere cell and to run a default ME in each application server that is a member of this
bus. This configuration serves as the embedded JMS provider, and provides SIBus
capabilities for web service applications.
MEs run inside an application server and alongside Java EE applications and their
containers. You can have multiple MEs running in the same application server. This
behavior is to allow the processing that is related to different sets of messaging
applications, which run within the process that is going to be separated. It also allows for
the different applications to use different buses, each with its own topology and set of
resources. There is no architectural requirement for MEs within the same process to be
members of different buses. It is possible to have two MEs that are part of the same bus
both running in the same process, which can occur under different policy settings for
clustered bus members.
V8.1
Student Notebook
Uempty
Network Deployment cell topologies (1 of 2)

• In WebSphere Messaging, the administrative unit is the cell
– Assumes uniform access to all MEs within the cell
– All MEs on a bus are fully interconnected
– A cell can host multiple buses
– A bus in one cell can have a link to a bus in another cell
Figure 15-40. Network Deployment cell topologies (1 of 2) WA855 / VA8551.0
Notes:
When you have a bus, every destination on that bus must have a unique name; so to a
certain extent, the bus is a namespace. If you have a second bus, you can have another
destination with the same name as one in the first bus. When you go to the level of the JMS
proxies in the JNDI namespace, a JMS destination specifies only the destination name, not
the bus name. The connection factory specifies the name of the bus to connect to. Thus, to
connect to two different destinations, it would be possible to use the same JMS destination
with two different connection factories that specify different bus names.
Student Notebook
Network Deployment cell topologies (2 of 2)
SIBus 1 • Links are used to

ME ME ME provide connectivity
ServerD ServerE ServerF beyond a single bus
– SIBus link: used to connect
SIBus link Cell 1 two different buses
– WebSphere MQ link: used
SIBus 2 to connect a WebSphere
ME ME ME Messaging bus and a
ServerD ServerE ServerF
WebSphere MQ network
SIBus link
Cell 2
SIBus 1 WebSphere MQ
Queue
MQlink Manager
ME ME
ServerA ServerB
Figure 15-41. Network Deployment cell topologies (2 of 2) WA855 / VA8551.0
Notes:
Protocol attachment is the only way WebSphere MQ applications can interact with
WebSphere Messaging applications. WebSphere Messaging does not directly support any
WebSphere MQ programming interface, such as the MQI or the AMI. Connectivity between
a messaging engine and a WebSphere MQ queue manager is established by defining a
WebSphere MQ link. One of the primary functions of the WebSphere MQ link is to convert
between the formats and protocols that WebSphere MQ and WebSphere default
messaging use. A component that is called the JS/MQ protocol adapter handles this
conversion.
V8.1
Student Notebook
Uempty
Additional messaging
considerations

Figure 15-42. Additional messaging considerations WA855 / VA8551.0
Notes:
Student Notebook
Additional messaging considerations

• For a complete configuration of WebSphere Messaging, consider:
– Quality of service
– Mediation
– SIBus security
– Interoperability with WebSphere MQ
Figure 15-43. Additional messaging considerations WA855 / VA8551.0
Notes:
For a complete configuration of WebSphere Messaging, you might consider quality of
service, mediation, SIBus security, and interoperability with WebSphere MQ.
V8.1
Student Notebook
Uempty
SIBus destination quality of service

• Quality of service can be configured for SIBus destinations
• Producers can override default reliability: Select this option so that
producers can override the default reliability that is set on the
destination
• Default reliability:
The reliability that is
assigned to a
message that is
produced to this
destination when the
producer does not set
an explicit reliability
• Maximum reliability:
The maximum
reliability of messages
that this destination
accepts
Figure 15-44. SIBus destination quality of service WA855 / VA8551.0
Notes:
Select Service integration > Buses > bus_name > Destinations > destination_name.
Student Notebook
Destination quality of service for reliability

Low • BEST_EFFORT_NONPERSISTENT High
– Messages are never written to disk
• EXPRESS_NONPERSISTENT
– Messages are written asynchronously to persistent storage if
memory cache overruns
Performance
Reliability
• RELIABLE_NONPERSISTENT
– Same as EXPRESS_NONPERSISTENT, except you have a
low-level acknowledgement message
• RELIABLE_PERSISTENT
– Messages are written asynchronously to persistent storage
during normal processing
• ASSURED_PERSISTENT
High – Highest degree of reliability where assured delivery is Low
supported
Figure 15-45. Destination quality of service for reliability WA855 / VA8551.0
Notes:
You can define quality of service on a destination basis to determine how messages are (or
are not) persisted.
Quality of service is configured through the administrative console in the Service
Integration > Buses > Destinations page.
You can also specify quality of service within the application.
• BEST_EFFORT_NONPERSISTENT
- Messages are never written to disk.
- Throw away messages if the memory cache overruns.
• EXPRESS_NONPERSISTENT
- Messages are written asynchronously to persistent storage if the memory cache
overruns, but are not kept over server restarts.
- No acknowledgment that the ME received the message.
V8.1
Student Notebook
Uempty • RELIABLE_NONPERSISTENT
- Same as EXPRESS_NONPERSISTENT, except that you have a low-level
acknowledgment message for which the client code waits before returning to the
application with an OK or not OK response.
• RELIABLE_PERSISTENT
- Messages are written asynchronously to persistent storage during normal
processing, and stay persisted over server restarts.
- If the server fails, messages are lost if they are held in the cache at the time of
failure.
• ASSURED_PERSISTENT
- Highest degree of reliability where assured delivery is supported.
Express nonpersistent and reliable persistent are defaults for nonpersistent and persistent.
In express nonpersistent, messages are sent from a producer to the ME, but there is never
an acknowledgment flow (at the low-level communications layer) to indicate that the ME
has the message. You return to the application immediately and assume that all is well. In
the reliable nonpersistent, you have a low-level acknowledgment message that the client
code waits for before returning to the application with an OK or not OK response. Thus,
express runs faster, but with a slightly lower level of reliability.
Quality of service is configured through the administrative console in the Service
Integration > Buses > Destinations page.
Student Notebook
What is a mediation?
• Mediation: The ability to manipulate a message as it traverses the
messaging bus (destination)
– Transform the message
– Copy or reroute the message to a different destination, or sequence of
destinations
– Allow interaction with nonmessaging resource managers (for example,
databases)
• Mediations are attached administratively to a destination
Destination
Producer message message Consumer
Mediation Destination
Figure 15-46. What is a mediation? WA855 / VA8551.0
Notes:
A mediation is a programmable extension to the messaging capabilities of WebSphere
Application Server that can simplify connecting systems, services, applications, or
components that use messaging. A mediation is used to process in-flight messages.
A mediation can do the following types of processing:
• Modifying or transforming a message
• Routing messages (or cloned messages) to other or more destinations
• Allowing or disallowing a message to be delivered based on some conditional logic in
the mediation
V8.1
Student Notebook
Uempty
SIBus security
• SIBus security can be enabled when the bus is created
• Authentication:
– Inherit cell level security domain (default)
– Use a selected security domain
• Authorization: available roles for users and groups

– Bus connector: can connect to the bus
– Sender: can send (produce) messages to the destination
– Receiver: can read (consume) messages from the destination
– Browser: can read (non-destructive) messages from the destination
• Secure message transportation

– Encrypt transport channel with SSL
Figure 15-47. SIBus security WA855 / VA8551.0
Notes:
Several new security panels are provided in the administrative console to help configure
role-based access to bus resources. Previously, the only way to administer the role-based
authorization mechanism was through several commands that were used in wsadmin.
Student Notebook
Interoperating with a WebSphere MQ network

• WebSphere Application Server can interoperate with WebSphere MQ
in the following ways:
– By using the WebSphere MQ messaging provider to configure WebSphere MQ
as an external JMS provider
– By using the default messaging provider and a WebSphere MQ link to connect a
service integration bus to a WebSphere MQ network
– By using the default messaging provider and a WebSphere MQ server to
integrate WebSphere MQ queues into a bus
Figure 15-48. Interoperating with a WebSphere MQ network WA855 / VA8551.0
Notes:
The default messaging provider (service integration) can use a WebSphere MQ link or a
WebSphere MQ server to interoperate with a WebSphere MQ network. Alternatively, you
can use WebSphere MQ as your messaging provider. Each type of connectivity is designed
for different situations and provides different advantages. Choose the most appropriate
interoperation method for each of your messaging applications.
V8.1
Student Notebook
Uempty
Connect SIBus to WebSphere MQ Network
SIBus WebSphere WebSphere WebSphere

JMS MQ app MQ app MQ app
application
MQ channel WebSphere WebSphere WebSphere
ME MQ Queue MQ Queue MQ Queue
MQ link Manager Manager Manager
Web Protocol WebSphere
services
Application
Server
• You use a WebSphere MQ link to connect an SIBus to a WebSphere MQ

network
• WebSphere MQ treats the SIBus ME as a virtual queue manager
• SIBus treats WebSphere MQ network as a foreign bus
• WebSphere MQ applications can send messages to queues hosted on
WebSphere Application Server SIBuses
• WebSphere Application Server messaging applications can send messages
to WebSphere MQ queues
Figure 15-49. Connect SIBus to WebSphere MQ Network WA855 / VA8551.0
Notes:
A WebSphere MQ link provides a server-to-server channel connection between a service
integration bus and a WebSphere MQ queue manager or queue-sharing group, which acts
as the gateway to the WebSphere MQ network. When you use a WebSphere MQ link, the
WebSphere MQ network sees the messaging bus as a virtual queue manager, and service
integration sees the WebSphere MQ network as a foreign bus.
A WebSphere MQ link allows WebSphere Application Server applications to send
point-to-point messages to WebSphere MQ queues (defined as destinations in the service
integration bus). Also, a WebSphere MQ link allows WebSphere MQ applications to send
point-to-point messages to destinations in the service integration bus (defined as remote
queues in WebSphere MQ). The link also allows WebSphere Application Server
applications to subscribe to messages that WebSphere MQ applications publish, and
WebSphere MQ applications to subscribe to messages that WebSphere Application Server
applications publish. The link ensures that messages are converted between the formats
that WebSphere Application Server uses and the formats that WebSphere MQ uses.
Student Notebook
Unit summary
• Describe messaging components such as JMS providers, the service
integration bus (SIBus), and messaging engines
Notes:
V8.1
Student Notebook
Uempty
1. Name two types of JMS destinations.
2. What can be added as a member of an SIBus?
3. True or False: An application server always has at least one message

engine that is running.
4. True or False: Producer and consumer applications connect to the

SIBus through a Messaging Engine.
Notes:
1. 
2. 
3. 
4.
Student Notebook
Checkpoint answers
1. Name two types of JMS destinations.
Queues and topics
2. What can be added as a member of an SIBus?

Application servers and clusters
3. True or False: An application server always has at least one message

engine that is running.
False
4. True or False: Producer and consumer applications connect to the

SIBus through a Messaging Engine.
True
Notes:
V8.1
Student Notebook
Uempty
Exercise 11
Configuring the service integration

bus

Notes:
Student Notebook
Exercise objectives
• Explain some of the design decisions that are required to set up a
messaging environment
• Explain how to configure the service integration bus, messaging
engines, and bus destinations in WebSphere Application Server
• Explain how to set up basic SIBus security
• Explain how to configure JMS queues, connection factories, and
activation specifications for message-driven beans
• Explain how to install and test the messaging features of the two
example programs
Notes:
V8.1
Student Notebook
Uempty
Exercise: Messaging tasks

Bus: msgBus
1 3
Bus destination:
TradeQueueDestination
ME:
PlantsCluster.
000-msgBus
Server1 Server2
Trade
Message
5 processor
sender app
app (MDB)
4 JMS JMS
connection activation
factory JMS spec
destination
queue
2 Bus member: PlantsCluster

Figure 15-55. Exercise: Messaging tasks WA855 / VA8551.0
Notes:
1. Create and secure an SIBus named msgBus.
2. Add PlantsCluster as a bus member.
3. Create the SIBus destination named TradeQueueDestination.
4. Create the JMS objects that the messaging applications require.
5. Install the messaging applications to the PlantsCluster.
Student Notebook
V8.1
Student Notebook
Uempty Unit 16. Job manager and centralized installation

manager

This unit describes flexible management by using the job manager and
the administrative agent. It also covers the new job manager functions
that incorporate the centralized installation manager (CIM).

• Describe the flexible management topology
• Describe the function of the job manager and the administrative
agent
• Configure target hosts for the job manager
• Configure CIM jobs for the job manager
• Submit a job to install the Installation Manager on a remote host
• Monitor the status of a job manager job

References
WebSphere Application Server ND V8.5 Information Center:
© Copyright IBM Corp. 2013 Unit 16. Job manager and centralized installation manager 16-1
Student Notebook
Unit objectives
• Describe the function of the job manager and the administrative agent
Notes:
V8.1
Student Notebook
Uempty
Topics
• Flexible management
• Job manager
• Centralized Installation Manager (CIM) in the job manager
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 16.1.Flexible management
Student Notebook
Flexible management

Notes:
V8.1
Student Notebook
Uempty
Flexible management
• The flexible management model addresses scalability requirements
with the introduction of the job manager
– A single job manager can manage many WebSphere Application Server base
edition and Network Deployment topologies that are registered with it as
managed nodes
• In this model, rather than starting administrative operations directly

against stand-alone servers and deployment managers, they are
instead submitted as administrative jobs to the job manager
• The managed nodes then fetch these administrative jobs at predefined

intervals
• A job manager supports

– Configuration and control (start and stop) operations for servers, clusters, and
applications
– Execution of wsadmin scripts as administrative jobs
Notes:
The flexible management model addresses scalability requirements with the introduction of
the job manager. A single job manager can manage several WebSphere Application Server
Base edition and Network Deployment cell topologies that are registered with it as
managed nodes. In this model, rather than using administrative operations directly against
stand-alone servers and deployment managers, they are instead submitted as
administrative jobs to the job manager. The managed nodes then fetch these
administrative jobs at predefined intervals. A job manager supports configuration and
control (start and stop) operations for servers, clusters, and applications. It also supports
execution of wsadmin scripts as administrative jobs.
Student Notebook
Flexible management topology

Job
manager
Job manager console
Job
endpoint
manager
Data
cache
Any latency network
Application
server Application Deployment
endpoint Admin Admin server manager
agent agent Dmgr
console console
Master
Master
Application
config
configuration
Local server
repository
repository
configuration
repository
Figure 16-5. Flexible management topology WA855 / VA8551.0
Notes:
This slide shows the topology that is used in a flexible management environment. In this
environment, there can be one or more job manager endpoints, each containing a job
manager process, and running code for a job manager console. There is also a cache of
endpoint information to minimize the time that is needed to fetch some information. If there
are multiple job managers, they are not clones of each other but are independent entities.
The job managers connect through a network to one or more WebSphere Application
Server endpoints. Each of these endpoints contains a WebSphere node. The node
contains a process that is called the administrative agent, which runs code for an
administrative console that is known as the administrative agent console. The node also
contains a local configuration repository and some number of application servers. It is also
possible to have a job manager control one or more deployment managers, as shown in
the lower right section of the slide.
V8.1
Student Notebook
Uempty
Flexible management characteristics

• Offers asynchronous job-queuing mechanism for administration
purposes
• Offers administrators more management options not available before
WebSphere Application Server V7
• Management of multiple base servers
– Can manage a server farm that contains hundreds of base servers
• Coordinate management actions across multiple deployment managers
– Can manage multiple cells
– Geographically distributed cells
• An alternative to the network deployment cell model, not a replacement
Figure 16-6. Flexible management characteristics WA855 / VA8551.0
Notes:
Flexible management environments rely on asynchronous processing of work units (known
as jobs) from the job manager. This approach supports large scaling and can support many
application servers without degrading performance. It also reduces latency and bandwidth
requirements on the network; even dial-up lines to remote sites can work well without
slowing down the overall system. Additionally, configuration information does not exist
beyond the node level, so no bottleneck is associated with accessing a master
configuration repository.
Flexible management is not a replacement for the network deployment model but can be
used as an alternative to it. The two models can be combined by having a job manager
coordinate management actions across multiple deployment managers.
Student Notebook
Administrative agent
• New profile type to support flexible management
• Register base application server profiles with the administrative agent
– Reduces application server footprint
– Offloads administrative functions to administrative agent
– Most administrative function is removed from base application servers
– Maintains isolation between base nodes; no master repository or synchronization
• Register base application server profiles with the job manager through
the administrative agent
• Administrative agent polls job manager for jobs on behalf of application
servers
Figure 16-7. Administrative agent WA855 / VA8551.0
Notes:
An administrative agent provides a single interface to administer multiple unfederated
application server nodes in environments such as development, unit test, or that portion of
a server farm that is on a single machine.
The administrative agent and application servers must be on the same machine, but you
can connect to the machine from a browser or the wsadmin tool on another machine.
You can register an application server node with the administrative agent or federate the
node with a deployment manager, but not both.
V8.1
Student Notebook
Uempty
Administrative agent topology
Administrative agent node
Administrative
agent
Base node A Base node B Base node C
Config Config Config

files files files

server server server
Figure 16-8. Administrative agent topology WA855 / VA8551.0
Notes:
The administrative agent is designed as an option to complement the WebSphere
Application Server base topology, in which the stand-alone application server continues to
serve the application requests. Only administrative services from the server are
consolidated into the administrative agent. For every WebSphere Application Server base
profile registered with the administrative agent, an administrative subsystem is created
within the administrative agent to represent the new administrative entry point for that
profile.
Student Notebook
Administrative agent features

• Multiple stand-alone application servers can be registered with a single
administrative agent
– When registered, that one administrative agent monitors and controls the
application servers
• The administrative agent becomes the central point of entry for
administering multiple stand-alone application servers on the same
host
– Especially significant for users who manage topologies that contain many stand-
alone application servers on a single host
• The administrative services of the registered servers are consolidated
into the administrative agent
– Thus reducing the memory footprint from previously duplicated services
• Management functions that the administrative agent does remain
isolated between registered application servers
– The user can direct operations to a specific server within the set of servers that
are being managed
Figure 16-9. Administrative agent features WA855 / VA8551.0
Notes:
Multiple customers administer application servers in their development, test, and
production environments by federating the application server nodes into a cell and
administering the application servers from the deployment manager. However, if you have
development and unit test environments, then you might prefer to run application servers
whose nodes are not federated. These application servers have some administrative
disadvantages. The application servers lack a common administrative interface. Remote
administration is limited to installing applications and changing application server
configurations. As an alternative, you can register these application servers with an
administrative agent to administer application servers from a single interface and to more
fully administer application servers remotely.
V8.1
Student Notebook
Uempty
Job manager
• New profile type to support flexible management
• Use administrative agent to register base server profiles with a job
manager
• To manage multiple cells, register deployment managers with job
manager directly
• Use job manager to queue jobs for registered profiles
• Registered profiles retain autonomy and can be managed without the
job manager
• Scales to support large number of registered profiles
Figure 16-10. Job manager WA855 / VA8551.0
Notes:
The job manager is a new server type that is added to support flexible management. It is a
new profile type, and the various tools that can create profiles are modified to support
creation and maintenance of this profile. The job manager is central to flexible
management.
To participate in flexible management, a base server first registers itself with the
administrative agent. The base server must then register with the job manager. If a
deployment manager wants to participate in an environment that a job manager controls,
the deployment manager registers directly with the job manager; no administrative agent is
involved in this case.
The main use of the job manager is to queue jobs to application servers in a flexible
management environment. These queued jobs are pulled from the job manager by the
administrative agent and distributed to the appropriate application server or servers.
Student Notebook
Job manager topology

Job manager
Cell A Cell B
Admin node A Admin node B Manager node Manager node
Admin Admin
DMgr DMgr
agent agent
Base nodes Base nodes Federated Federated

nodes nodes
Application Application Node Node

server server agent agent
Application Application
servers servers
Figure 16-11. Job manager topology WA855 / VA8551.0
Notes:
The job manager is designed to complement the Network Deployment and Base edition
topologies. Existing nodes are not required to be reconfigured. A single job manager can
manage hundreds of nodes, and multiple job managers can manage a single node. This
model is different from having ownership of a managed node by the deployment manager
in a network deployment topology.
• The topologies that a job manager controls maintain their autonomy, including their
security configuration, and thus they can be directly managed with existing
administrative processes, such as scripts or the administrative console.
• This model allows coordinated management actions across multiple managed nodes
that are defined as a group.
• The asynchronous job submission model facilitates the management of nodes that are
geographically dispersed and reachable only through low-bandwidth, high-latency
networks.
V8.1
Student Notebook
Uempty
Flexible management jobs

• Manage servers • File distribution
– Create or delete application – Collect file
server – Distribute file
– Start or stop server – Remove file
• Manage applications
• Run wsadmin script
– Download application EAR
files • Configure properties
– Install or uninstall application
• Inventory
– Start or stop application
– Update application • Status
• Manage offerings
Figure 16-12. Flexible management jobs WA855 / VA8551.0
Notes:
Examples of jobs in flexible management are installing an application, creating an
application server, running a wsadmin script on a remote node, and many others.
Student Notebook
Asynchronous nature of jobs

• When jobs are submitted, they are not necessarily run right away
• The administrative agents and deployment managers pull jobs from the
job manager when they are online, based on configured polling
intervals
• Because jobs can also be created with intervals of allowable execution,
if the job is not retrieved during a validity period, it is not run
• The job status summary page presents four types of job completion
status
– Succeeded
– Partially succeeded
– Failed
– Incomplete
Figure 16-13. Asynchronous nature of jobs WA855 / VA8551.0
Notes:
Status is displayed in a chart with which you can drill down to look at which nodes are
completed under each state. The chart indicates status by color and position in the
summary bar.
When you submit a job, it starts out with incomplete status. When the job is retrieved, the
detailed status shows it as distributed, then in progress. The normal progression of jobs at
that point is for their status to go to successful, partially successful, or failed. It takes at
least two polling cycles to retrieve a job and then return results, and it can take more
cycles, according to how long the job actually takes to process on the node. The polling
cycle time is configurable at the administrative agent or the deployment manager. You
might find that the status summary shows incomplete nodes, but when you drill down, no
nodes show in the list. When you refresh the status summary, you find that the node either
completed or failed in that window of time and is no longer incomplete.
V8.1
Student Notebook
Uempty 16.2.The job manager
Student Notebook
The job manager

Figure 16-14. The job manager WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Job manager
• Two types of job manager
– Stand-alone job manager profile: has a separate administrative console
– Job manager server: Runs within the deployment manager
• The deployment manager administrative console has a Jobs navigation tree
with choices similar to the options in the job manager administrative console
• With each job manager, you can submit administrative jobs
asynchronously for:
– Application servers that are registered to administrative agents
– Deployment managers
– Remote host computers
• Centralized Installation Manager (CIM) tasks can be submitted as jobs
in the job manager
Figure 16-15. Job manager WA855 / VA8551.0
Notes:
The job manager “embedded” within the deployment manager profile is identical to the
stand-alone job manager profile in terms of function.
Here are some additional facts about the “embedded” job manager.
• It runs within the deployment manager process.
• It has no jobs that are defined until you register a target host.
• The jobs available depend on what target hosts are registered. If you register a remote
host with no WebSphere products installed, then you see only the CIM-related job
types. If you register a stand-alone WebSphere node, then you see all the job manager
job types.
• You can register the host machine of the deployment manager as a target.
• You can use an administrative agent to register a stand-alone WebSphere Application
Server node (use administrative host port 9043, not default 9943).
Student Notebook
• You can use the ordinary “Register with job manager” function of the deployment
manager to register the deployment manager itself to its job manager. Use
administrative host port 9043.
V8.1
Student Notebook
Uempty
The deployment manager job manager process

• The job manager process is new in the System administration section
Figure 16-16. The deployment manager job manager process WA855 / VA8551.0
Notes:
There is a new link for the job manager under the System administration section. Clicking
the link shows you its configuration and runtime properties. In this screen capture, you can
see that the process ID for the job manager and the deployment manager is the same. The
job manager is part of the deployment manager process. Even though the deployment
manager now has its own job manager that is contained within it, it is still possible to
register the deployment manager to a stand-alone job manager in a flexible management
topology.
Student Notebook
Job manager Jobs section

• New Jobs section in the navigation tree
• At least one target must be defined before you can submit jobs
Select Targets and add a host
Figure 16-17. Job manager Jobs section WA855 / VA8551.0
Notes:
No jobs are defined for the job manager until at least one target host is registered with the
job manager. It is possible to register the host of the job manager as a target.
V8.1
Student Notebook
Uempty
Registering targets
• Host targets
– Register from job manager
– Jobs > Targets > New Host
• Deployment manager targets
– Register from deployment manager
– System administration >
Deployment manager > Job
managers > Register with Job
Manager
• Base node targets
– Register from administrative agent
– Use registernode command first
– System administration >
Administrative agent > Nodes >
Register with Job Manager
• After registration, jobs can be
submitted to the target © Copyright IBM Corporation 2013
Figure 16-18. Registering targets WA855 / VA8551.0
Notes:
Use the panel that is shown in the screen capture to register a new host with the job
manager.
In place of a password, you can also configure public-private key authentication.
You can choose to save security information. If selected, the security properties are saved
with the host and are used as defaults for subsequent job submissions to this host.
For Windows targets, some special configuration is required on the Windows host. See the
information center topic, “Requirements for using Remote Execution and Access (RXA)”,
for details:
http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/
com.ibm.websphere.installation.nd.doc/info/ae/ae/
cins_cim_rxa_requirements.html
Student Notebook
Job manager: Submit jobs

• Click Submit to start the submit job wizard
Figure 16-19. Job manager: Submit jobs WA855 / VA8551.0
Notes:
The first step in the submit job wizard is to choose a job type. The screen capture on this
slide shows all the available job types.
V8.1
Student Notebook
Uempty
Job manager jobs for host targets
• Inventory
– Refresh data on job types and on managed resources
• Install, update, and uninstall IBM Installation Manager
• Manage offering
– Install, update, uninstall WebSphere Application Server
• Manage profile
– Create, delete, augment, back up, list, and restore profiles on remote hosts
• Run command
– Run command-line utilities such as startServer, wsadmin commands, or
operating system commands on a remote host
• Install SSH public key
• Distribute, collect, and delete file
• Test connection
– Verify access to remote hosts registered with the job manager
Figure 16-20. Job manager jobs for host targets WA855 / VA8551.0
Notes:
Submit the Run command on a remote host job to run command-line utilities such as
startServer, wsadmin commands, or operating system commands on a remote host. A
WebSphere Application Server installation on the remote host is required to run product
commands, but is not required for non-product commands.
Important note about uninstalling IBM Installation Manager: Before you can uninstall
IBM Installation Manager, you must uninstall all the products that it installed. Because of
this fact, you cannot uninstall the Installation Manager from the host machine of the local
deployment manager.
Student Notebook
Job manager jobs for WebSphere targets

• If a node is
registered to the
deployment
manager’s job
manager by using
an administrative
agent, these jobs
are also available
Figure 16-21. Job manager jobs for WebSphere targets WA855 / VA8551.0
Notes:
The point of this screen capture is to show that the list of job types available to the
stand-alone job manager is different from the list that is seen in the administrative console.
(The list from the administrative console is shown on the previous slide.) The job types
available in the administrative console depend on the kinds of targets that are registered
with the deployment manager.
V8.1
Student Notebook
Uempty
Liberty profile jobs

• Install Liberty profile resources
– Extract resources in a Liberty profile image to destination directories relative to a
root directory
• Start and stop Liberty profile server
• Generate merged plug-in configuration
– Create a single plug-in configuration file that merges plug-in information from
multiple Liberty profile servers
Figure 16-22. Liberty profile jobs WA855 / VA8551.0
Notes:
You can submit the Install Liberty profile resources job to extract resources in a Liberty
profile image to destination directories relative to a root directory.
Before running the Install Liberty profile resources job, the following conditions must exist:
• The job manager must be running.
• A host computer must be registered with the job manager.
• The image, a compressed .zip file, must contain Liberty profile resources in a
directory structure that satisfies job manager rules.
• The root directory to install the resources on the target host must be defined. At
minimum, set the WLP_WORKING_DIR variable to a valid directory on a target host.
Student Notebook
V8.1
Student Notebook
Uempty 16.3.Centralized installation manager (CIM) in the job manager
Student Notebook
Centralized Installation
Manager (CIM) in the job
manager

Figure 16-23. Centralized installation manager (CIM) in the job manager WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Centralized Installation Manager (CIM) in the job manager

• Architecture of job manager, target hosts, and IBM Installation Manager
repository
IBM IBM
Installation Installation
Manager Manager
installation repository
kits (offerings)
WebSphere core
Deployment manager products
Job 1 IBM Installation Manager

manager Target host
installation kit
CIM Installation
2 manager
Install jobs + response files
3 Inventory information
Figure 16-24. Centralized installation manager (CIM) in the job manager WA855 / VA8551.0
Notes:
CIM functionality is now a series of jobs available to the deployment manager’s job
manager. The job manager can store IBM Installation Manager installation kits for different
operating systems in a repository on the local file system. A job can be submitted that
“pushes” the required IBM Installation Manager kit to the target node and does the remote
installation with nothing more than target identification and the required authorizations. No
agents are required on the target host. Installation jobs for WebSphere Application Server
can be configured along with an appropriate response file for the remote target host. When
installed on the target host, the Installation Manager can pull the WebSphere code from an
IBM Installation Manager repository.
You can submit the Inventory job to refresh data on job types and on managed resources
of the job manager. Resources include applications and servers of each target. If you
installed a product that adds job types on a managed target, run the Inventory job to refresh
data on job types and target resources. You can view the refreshed data in the job manager
console.
Student Notebook
Add IBM Installation Manager installation "kits"

• Click Jobs > Installation Manager installation kits
• IBM Installation Manager “kits”, or installation packages for each OS, can be
downloaded and stored on the local file system of the job manager
Figure 16-25. Add IBM Installation Manager installation “kits” WA855 / VA8551.0
Notes:
Click Jobs > Installation Manager installation kits to see a list of the kits currently
available in the local repository. Installation Manager installation kits are required for
application installation jobs. Use this page to specify the location where the Installation
Manager installation kits are stored. The list of Installation Manager installation kits
available from the location that is provided is shown in the screen capture.
Typically you download the kits from an IBM WebSphere site and store the compressed
files in a local file system directory, <profile_root>/dmgr_name/IMKits by default.
This panel allows you to view your Installation Manager installation kits from a centralized
location. For each installation kit, the list includes detailed information about name, size,
version, operating system, and platform. Use the Refresh button to generate a list of the
installation kits in your specified location, and use the Add or Delete button to add or
delete installation kits from your list.
V8.1
Student Notebook
Uempty
Job example: Install IBM Installation Manager

• Click Jobs > Submit
• Step 1: Choose a job type: Install IBM Installation Manager
• Step 2: Choose job targets (registered hosts)
– Provide administrative login credentials for targets
• Step 3: Specify job parameters
– The path and file name of Installation Manager kit
– Installation Manager agent data location
– Installation Manager installation directory
– Installation action: installation that is based on login credentials
– Skip prerequisite checking (optional)
– Accept the terms in the license agreements
• Step 4: Schedule the job: now or a specific time
• Step 5: Review the summary and submit the job
Figure 16-26. Job example: Install IBM Installation Manager WA855 / VA8551.0
Notes:
In a flexible management environment, you can submit the Install IBM Installation Manager
job to install the Installation Manager on registered hosts of the job manager.
Start the job manager and the targets. Ensure that the targets for which you want to install
Installation Manager are registered with the job manager.
To submit jobs, your ID at the job manager must be authorized for the administrator role or
the operator role. When you submit a job, you can specify a user name and password for
authentication and authorization at the target or targets. When you submit a job to multiple
targets, the user name and password or the credentials for the submitter must apply to all
of the job targets.
To run the job against many targets, optionally create a group of targets and submit the job
against the group.
Student Notebook
Install IBM Installation Manager on a target
Step 3: Specify
IBM Installation
Manager kit
location on job
manager and
installation
directory on target
Figure 16-27. Install IBM Installation Manager on a target WA855 / VA8551.0
Notes:
• The path and file name of the Installation Manager kit
Specify the fully qualified path and name of the IBM Installation Manager installation kit
on the job manager. If you do not enter any information into this field, the Install IBM
Installation Manager job locates the most recent IBM Installation Manager installation kit
from the repository. The default location is in the $JOB_MANAGER_HOME/IMKits
directory.
• Installation Manager agent data location
Specify the fully qualified path of the Installation Manager agent data location on the
remote host. Leave it empty to use the IBM Installation Manager default agent data
location.
• Installation Manager installation directory
Specify the fully qualified path of the IBM Installation Manager installation location on
the remote host. Leave it empty to use the IBM Installation Manager default installation
location.
V8.1
Student Notebook
Uempty • Installation action

Specify the Installation Manager installation actions: Install based on login
credentials. The system does a single user installation if user is not an administrator, or
installs Installation Manager for everyone if the user is an administrator. The other
options are “Install for single user only” and “Install for a group of users”. Group
installation is available only on the following platforms: AIX, Linux, Solaris, HPUX, and
z/OS.
Student Notebook
Job scheduling
• Step 4: Schedule
the job
• Options
– Email notification
– Job availability
– Job expiration
– Job availability
interval
Figure 16-28. Job scheduling WA855 / VA8551.0
Notes:
You can specify one or more email addresses where notifications are sent when the job is
done.
Select when the job is available for submission. You can submit the job to be available now,
or specify a time and date that the job is retrieved from the job manager.
Select the job expiration. The job expiration is the time at which the job is no longer
available for nodes to run. You can use the default expiration, specify a time and date for
the job expiration, or specify an amount of time in which the job expires. The default
expiration is defined on the job manager configuration page.
Optionally specify a recurring interval for the job, a start date, and time for the interval, and
an end date and time for the interval.
V8.1
Student Notebook
Uempty
Job status
• Click Jobs > Job status
• If job status is Incomplete, click the Job ID link for more details
Figure 16-29. Job status WA855 / VA8551.0
Notes:
All jobs can be monitored in the Job status panel.
A job that is still being processed shows a status of Incomplete. The two jobs that are listed
on the screen capture have a status of Succeeded. The Active state refers to a
configurable time interval over which the job can be resubmitted if it is configured to repeat.
Student Notebook
Submitting a "Manage offerings" job (1 of 3)

• You can use the job manager to install, update, and uninstall
• Use the administrative console to

– Register your target host
– Install IBM Installation Manager
– Install WebSphere Application Server or other product offerings that are
compatible with Installation Manager
• Using the administrative console, you can

– Set parameters for the directory in which to install the product on the target host
– Specify where to store product data on the target host
– Specify the URL of the repository from which the product is downloaded
• Depending on your security setup, you can also specify key ring
credentials to authenticate to the product repository
Figure 16-30. Submitting a “Manage offerings” job (1 of 3) WA855 / VA8551.0
Notes:
After the job manager successfully completes the installation process on a remote node, it
then deletes the installation image files in the temporary location that you specified during
the installation process. If the installation is unsuccessful, the files remain in the temporary
location for you to use to determine what caused the installation error. However, you can
safely delete the files.
V8.1
Student Notebook
Uempty
• washost02 is a registered target

• IBM Installation Manager is installed on the target
IBM • Response file provides the repository URL
Installation
Manager
repository
(offerings) 2 WebSphere Application Server
Network Deployment core product
files
Dmgr host
Deployment manager Target host
Server Network
Job Deployment
manager
CIM Installation
manager
1 Manage offerings job
+ response file
washost02
was8host01
Notes:
When a target host is registered with a job manager and the Installation Manager is also
installed on the target, a manage offerings job can be submitted to the job manager. A
response file must be provided during the job configuration that specifies what product is
going to be installed and how to access the binary files for that product from the IBM
Installation Manager repository.
Student Notebook

• Step 3: A fully qualified path to the response file is the only required job
parameter
Notes:
A URL or a fully qualified path to the response file on the job manager host is the only
required job parameter.
The response file can be generated with IBM Installation Manager.
V8.1
Student Notebook
Uempty Here is an example response file that is used to install WebSphere Application Server V8
on a Windows target host.
<?xml version="1.0" encoding="UTF-8"?>

<agent-input acceptLicense='true'>
<server>
<repository location='http://was8host01/MyRepository/WAS8'/>
</server>
<profile id='IBM WebSphere Application Server Network Deployment V8.0'
installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program
Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
<install modify='false'>
<offering id='com.ibm.websphere.ND.v80' version='8.0.0.20110503_0200'
profile='IBM WebSphere Application Server Network Deployment
Student Notebook
V8.0'features='core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ib
m.sdk.6_32bit,samples' installFixes='none'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache'
value='C:\Program Files\IBM\IMShared'/>
<preference name='com.ibm.cic.common.core.preferences.connectTimeout'
value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout'
value='45'/>
<preference
name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'
value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'
value='false'/>
<preference
name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthenticat
ion' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference
name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'
value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles'
value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates'
value='false'/>
<preference name='com.ibm.cic.agent.ui.displayInternalVersion'
value='false'/>
</agent-input>
V8.1
Student Notebook
Uempty
Differences between CIM for V 8 and CIM for V 6.1 and 7

Function CIM Version 6.1 CIM Version 8
and 7
Scope • Install, update, • Install, update, uninstall version 8 and all
uninstall version 7 Installation Manager installable products:
• Update version 6.1 – WebSphere
– IBM HTTP Server plug-in
– DMZ proxy
• Targets can be added outside of the cell
Installation ISMP and update Installation Manager
software installer
Repository Maintains a private • Maintains an installation kit directory

repository on the • Uses Installation Manager repository
deployment manager
Administrative Accessible from the • Accessible from the job manager

console deployment manager • Job manager is also available on the
deployment manager
Command line CIM AdminTask Use the submitJob command of the job
commands manager
Figure 16-33. Differences between CIM for V 8 and CIM for V 6.1 and 7 WA855 / VA8551.0
Notes:
The version 8.5 centralized installation manager (CIM) can be used to manage version 8.5
and previous versions of WebSphere Application Server. You can use CIM to install or
uninstall version 8.5 and previous versions of WebSphere Application Server on remote
machines and apply maintenance from the administrative console. In version 8.0 and later,
targets can be added outside of the cell. The process for managing version 7 and previous
versions is different from the process for managing version 8, and each process is
documented separately in the information center.
Student Notebook
Unit summary
• Describe the function of the job manager and the administrative agent
Notes:
V8.1
Student Notebook
Uempty
1. True or false: Flexible management is an alternative to the Network
Deployment cell model, not a replacement.
2. True or false: To set up a flexible management environment, it is

necessary to create a secure proxy profile.
3. True or false: IBM Installation Manager can be installed on a remote

target by using the job manager.
4. True or false: A deployment manager can be registered with a job

manager within the administrative console.
Notes:
1. 
2. 
3. 
4.
Student Notebook
Checkpoint answers
1. True
2. False. The secure proxy is not required.
3. True
4. True
Notes:
V8.1
Student Notebook
Uempty
Demonstration
Using the job manager

Figure 16-37. Demonstration WA855 / VA8551.0
Notes:
These demonstrations can be found online at the following location:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/WebS
phere%20Education%20Wiki/page/WebSphere%20Application%20Server%20V8%20Admin
istration%20Course%20Demonstrations
They are also in the following directory of the lab machine.
Linux: /usr/software/demos
Student Notebook
Demonstration objectives
After viewing these demonstrations, you should be able to:
• Add a target host to the job manager
• Submit a job to install IBM Installation Manager
• Submit a Manage Offerings job to install WebSphere Application
Server V8 on a remote host
• Submit a Manage Profiles job to create a stand-alone server profile on
a remote host
• Register a deployment manager with the job manager
• These demonstrations can be found online at the following location:
https://www.ibm.com/developerworks/community/wikis/h
ome?lang=en#!/wiki/WebSphere%20Education%20Wiki/page
/WebSphere%20Application%20Server%20V8%20Administrat
ion%20Course%20Demonstrations
• Note: These demonstrations are recorded with version 8.0. However,
the functions that they demonstrate are the same in 8.5.5
Figure 16-38. Demonstration objectives WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty Unit 17. Overview of Intelligent Management

This unit introduces the features of Intelligent Management.

• Define Intelligent Management
• Describe virtualization and autonomic computing
• Define intelligent routing
• Describe dynamic workload management
• Describe health management features
• Describe application edition management features
• Describe performance management features

• Checkpoint
References
index.jsp
© Copyright IBM Corp. 2013 Unit 17. Overview of Intelligent Management 17-1
Student Notebook
Unit objectives
Notes:
V8.1
Student Notebook
Uempty
Topics
• Overview of Intelligent Management
• Intelligent Management components
• Health management
• Application edition management
• Performance Management
• Deployment manager high availability
Notes:
Student Notebook
V8.1
Student Notebook
Uempty 17.1.Overview of Intelligent Management
Student Notebook
Overview of Intelligent
Management

Figure 17-3. Overview of Intelligent Management WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
• Intelligent management provides application server virtualization,
resource management, and advanced operations
• Used to enhance operations efficiency by

– Managing available resources to meet the demands of high-volume transactional
workloads
– Managing large scale, continuously available application server environments
• Provides application infrastructure virtualization

– Separates applications from the physical infrastructure on which they are hosted
– Requests are intelligently routed to respond to the most critical applications and
users
• Dynamic operations allow an application environment to scale as

required by virtualizing WebSphere resources
Notes:
Intelligent Management provides a virtualized infrastructure that redefines the traditional
concepts of Java Platform, Enterprise Edition (Java EE) resources and applications and
their relationships with one another. This application infrastructure virtualization facilitates
the ability of the product to automate operations in an optimal manner, increasing the
quality of service. By introducing an automated operating environment with workload
management, you can reduce total cost of ownership by using less hardware to do more
work.
The dynamic operations environment consists of autonomic managers whose purpose is to
use defined business goals to maximize utilization. Dynamic operations allow an
application environment to scale as required by the virtualization of WebSphere resources
and the use of a goals-directed infrastructure. Therefore, you can increase the speed at
which your environment adapts to the business requirements. Using the dynamic
operations features of WebSphere Application Server, you can change the way a typical
WebSphere environment is configured to one that has the following features:
• Improves the utilization of available resources such as processor and memory
Student Notebook
• Classifies and monitors the workload

• Provides a business-centric view of the workload and its performance
• Uses business guidelines that the organization specifies to respond in real time to
changes in the workload mix (without human intervention if you choose)
V8.1
Student Notebook
Uempty
Health Application Performance

management edition Management
management
Self protecting Self optimizing
Self healing Self managing
App App
version version
1.0 2.0
Intelligent routing
Notes:
Overview of intelligent routing capabilities:
• A routing tier that is aware of what is happening on the application server tier and
reacts; business-critical applications are given priority
• Automatic routing without needing to update configuration files
• A highly scalable routing tier
• Ease of management
• Flexible policy-based routing to control if, when, and where requests are routed
• A highly available deployment manager
Overview of health management capabilities:
• Automatically detect and handle application health problems without requiring
administrator time, expertise, or intervention
• Intelligently handle health issues in a way that maintains continuous availability
Student Notebook
• Configure applications differently if you want to

• Approve automatic actions before the actions are taken
• Set policies that are based on both high-level metrics and low-level metrics to detect
problems before you notice that something is wrong
Overview of application edition management capabilities:
• Ability to run multiple versions of your applications concurrently
• You do not incur any downtime while updating your applications
• Verify that a new version of your application works in production before sending real
traffic to it
• Reduce your infrastructure costs and decrease potential outages
• Easily update your operating system or WebSphere without incurring downtime
Overview of performance management capabilities:
• Associate service policies with your applications and have WebSphere efficiently
manage to achieve these goals
• Decrease administrative work that is required to monitor and diagnose performance
issues
• Minimize the number of JVMs and virtual machines that are running to reduce
processing that lightly used or idle JVMs or virtual machines incur
• Protect your middleware infrastructure against overload
V8.1
Student Notebook
Uempty
History
WebSphere Extended
Deployment
WebSphere Virtual
Dynamic clustering Enterprise
Batch processing
WebSphere Compute
Grid
Data grid WebSphere eXtreme WebSphere eXtreme

Scale Scale
WebSphere
WebSphere WebSphere Application Server
Application Server Application Server V8.5
V7 and earlier V8 and earlier Dynamic clustering
Batch processing
Figure 17-6. History WA855 / VA8551.0
Notes:
The biggest news under the theme of application resiliency is probably the integration of
the features from WebSphere Virtual Enterprise into WebSphere Application Server
Network Deployment. This merge allows a single WebSphere Application Server Network
Deployment installation to deliver the traditional Network Deployment functions, and also
WebSphere Virtual Enterprise functions. The former WebSphere Virtual Enterprise
functions now in Network Deployment V8.5 are characterized as Intelligent Management
features and encompass:
• Intelligent routing
• Application edition management
• Dynamic clustering
• Health management
Student Notebook
V8.1
Student Notebook
Uempty 17.2.Intelligent Management components
Student Notebook
components

Figure 17-7. Intelligent Management components WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Intelligent Management components

• Dynamic clusters
– Cluster members are dynamically created, started, and stopped
• Service policies
– Define the business goals for application requests
• Autonomic managers and services
– Provide information and take actions to implement intelligent management
functions
• Intelligent routers
– Support health management, application edition management, and Performance
Management features
– Two implementations
• On demand router (ODR)
• WebSphere plug-in
Figure 17-8. Intelligent Management components WA855 / VA8551.0
Notes:
Dynamic clusters allow the amount of resources available for application requests to be
adjusted dynamically.
Service policies allow business goals to be used for decision making in how requests are
handled.
Autonomic managers provide information and act to implement intelligent management
functions.
Intelligent routers intelligently dispatch incoming requests to the application server tier.
Student Notebook
Dynamic clusters
• A dynamic cluster is a cluster of servers where the number of active
cluster members can change dynamically
• The number of cluster members available is based upon a node

membership policy
– Cluster members are created or deleted if a node that matches a membership
policy is added to or removed from the cell
• The number of cluster members that are started is based upon current
application demand and service policies
– Cluster member weights and workload management are used to balance
workload of cluster members
• Cluster member definitions are automatically updated when the server

template associated with the dynamic cluster is updated
Figure 17-9. Dynamic clusters WA855 / VA8551.0
Notes:
A dynamic cluster is a server cluster that enables application server virtualization.
Members of a dynamic cluster are:
• Automatically created based on a membership policy
• Automatically updated by using a server template
• Automatically started and stopped based on current demand, available resources, and
service policies
These features allow the application environment to dynamically expand and contract; it
depends on the amount of workload that must be handled at any time.
V8.1
Student Notebook
Uempty
Dynamic cluster settings

• Minimum number of cluster instances: Select to have one or more
servers started always or stop all servers in times of inactivity
• Maximum number of cluster instances: Limit the number of servers

that can start
• Vertical stacking of instances on a node: If you want to allow more

than one server instance to be started on the same node
• Isolation requirements: Indicate whether a cluster member can run on

the same node as cluster members from a different dynamic cluster
Figure 17-10. Dynamic cluster settings WA855 / VA8551.0
Notes:
A dynamic cluster is a virtual cluster of application servers that hosts an application. These
application servers are on groups of nodes that are indicated by using the cluster
membership policy. The membership policy is compared against the nodes in your cell, and
servers are created for the dynamic cluster by using nodes that match the policy. When
new nodes are added to your environment, they are added automatically to the dynamic
cluster if they match the defined membership policy.
Student Notebook
Service policies
• Service policies specify how to classify an incoming request using the
request’s attributes
– Such as URI, client name, or HTTP headers
• Easily allows an administrator to specify the relative importance of

applications and optionally a response time goal
• Service policies are used to define application service level goals
• Allow workloads to be classified, prioritized, and intelligently routed
• Enables application performance monitoring
• Resource adjustments are made if needed to consistently achieve

service policies
Figure 17-11. Service policies WA855 / VA8551.0
Notes:
A service policy is a user-defined categorization that is assigned to potential work as an
attribute that the application request flow manager (ARFM) reads. You can use a service
policy to classify requests that are based on request attributes. These attributes include the
Uniform Resource Identifier (URI), the client name and address, HTTP headers, query
parameters, cookies, and time of day. By configuring service policies, you apply varying
levels of importance to the actual work. You can use multiple service policies to deliver
differentiated services to different categories of requests.
V8.1
Student Notebook
Uempty
Autonomic managers and services

• Autonomic request flow manager
– Classifies incoming requests and monitors performance of service classes
• Dynamic workload management controller
– Dynamically adjusts server weights to even out and minimize response times in
a cluster
• Application placement controller
– Decides on how many dynamic cluster members are started, and on which
nodes the cluster members are started
• Health controller
– Monitors defined health policies in the environment and ensures that actions are
taken to correct problems
• On demand configuration service
– Maintains cell topology information and keeps the other controllers informed of
the environment
Figure 17-12. Autonomic managers and services WA855 / VA8551.0
Notes:
With Intelligent Management, you can introduce autonomic capabilities into your
infrastructure at your own pace. Autonomic capabilities are delivered in a set of
components that are known as autonomic managers. Autonomic managers monitor
performance and health statistics through a series of sensors; they optimize system
performance and run traffic shaping.
• Dynamic workload controller
The dynamic workload controller dynamically adjusts server weights to even out and
minimize response times across the cluster. There is one dynamic workload controller
per cluster. The dynamic workload controller maintains a list of active server instances
for each dynamic cluster, and assigns each a routing weight according to observed
performance trends. Requests are then routed to candidate server instances to balance
workloads on the nodes within a dynamic cluster that is based on a weighted least
outstanding requests algorithm.
• The application placement controller
Student Notebook
The application placement controller is responsible for the management of the location
of an application within a node group. A single application placement controller exists in
the cell and is hosted in the deployment manager or in a node agent process. The
application placement controller starts and stops application server instances to
manage HTTP, SIP, JMS, and IIOP traffic. The application placement controller can
dynamically address periods of intense workflow that would otherwise require the
manual intervention of a system administrator.
• The on-demand configuration manager
The on-demand configuration manager maintains cell topology information and keeps
the ARFM and other controllers aware of its environment. It tracks updates in cell
topology and state, including the following changes:
- Applications that are installed and removed
- Servers started and stopped
- Nodes that added and removed
- Classification updates
The on-demand configuration component allows the on demand router to sense its
environment. The on demand router dynamically configures the routing rules at run time
to allow the on demand router to accurately route traffic to those application servers.
V8.1
Student Notebook
Uempty
Intelligent routers: the on demand router (ODR)

• A Java based HTTP and SIP Proxy built on the WebSphere run time
• Typically runs in a tier between the web servers and the application
servers
• Displayed in the administrative console as a new server type
• Can be clustered, highly available, and scalable
• Uses on demand configuration service to retrieve routing information
• Can route to multiple cells with failover or load-balancing of application
requests across cells
Figure 17-13. Intelligent routers: the on demand router (ODR) WA855 / VA8551.0
Notes:
The on demand router classifies incoming HTTP and SIP requests and then works with
other Intelligent Management “decision makers” to route the workload in order. The on
demand router ensures that the highest priority is given to business-critical applications.
Requests are prioritized and routed based on administrator-defined rules, called service
policies, which are used to specify application response time goals.
The on demand router handles the queuing and dispatching of requests according to
operational policy. An on demand router can be defined and started before any service
policies are defined. Operational policies can be defined before the appearance of the work
to which they apply. However, if policies are not defined, the default policies handle the
early work. The on demand router, similar to the web server plug-in for WebSphere
Application Server, uses session affinity to route work requests. After a session is
established on a server, later work requests for the same session go to the original server.
This configuration maximizes cache usage and reduces queries to resources. The on
demand router accepts incoming requests and distributes these requests to the system in
an intelligent manner, reflecting configured business goals. This process is dependent on
Student Notebook
the characterization of requests so that the relative business importance of each request
can be compared.
V8.1
Student Notebook
Uempty
Intelligent routers: the WebSphere plug-in

• Intelligent routing function based on native code ODRLIB
implementation
• Added to existing supported web servers
• Can be clustered, highly available, and scalable
• Uses a RESTful web service to retrieve routing information
• Can route to multiple cells – unique applications in each cell only
• DMZ-ready
Figure 17-14. Intelligent routers: the WebSphere plug-in WA855 / VA8551.0
Notes:
Rather than a Java based server, the WebSphere plug-in intelligent router function is
added to an existing supported web server. The WebSphere plug-in intelligent router has
most of the same capabilities as the ODR, although they are implemented differently. Some
benefits of the plug-in intelligent router are that it is DMZ-ready, and it eliminates the extra
processing tier and network hop that the ODR intelligent router introduces.
Student Notebook
What is intelligent routing?

• A routing tier that is aware of what is happening on the application
server tier
– Knows which cluster members are currently started
– Knows application server utilization, request performance, and other statistics
– Understands service policies
– Routes work to the application server that can do it best
– Knows which servers are in maintenance mode (more later)
– Can route to multiple application editions (more later)
– Provides preference for higher priority requests (ODR only)
– Provides processor and memory overload protection (ODR only)
• Integrates with dynamic clustering, health management, and

application edition management
Figure 17-15. What is intelligent routing? WA855 / VA8551.0
Notes:
Intelligent routing can improve the quality of service by ensuring that priority is given to
business-critical applications and users. Requests to applications are prioritized and routed
based on administrator-defined rules. It is easiest to start a discussion of Intelligent
Management by referring to the most visible component, the on demand router (ODR). The
ODR is a specialized, Java based proxy server that classifies incoming requests, and then
dispatches the requests across the application server environment.
V8.1
Student Notebook
Uempty 17.3.Health management
Student Notebook
Health management

Figure 17-16. Health management WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is health management?

• A WebSphere environment can be monitored for various software
health conditions
– Age, work completed, memory usage, response time, and others
– Excessive timeouts, storm drain detection
• Servers can have a custom sequence of steps that are run as a

corrective or preventive action
– Policy-driven autonomic system
• Health policies define monitored health conditions
• Customized health conditions and health actions can be defined
Figure 17-17. What is health management? WA855 / VA8551.0
Notes:
Intelligent Management provides a health management feature to monitor the status of
your application servers to sense and respond to problem areas before an outage occurs.
You can manage the health of your application environment with a policy-driven approach
that enables specific actions to occur when monitored criteria are met. For example, when
memory usage exceeds a percentage of the heap size for a specified time, health actions
can run to correct the situation.
Student Notebook
Health policies
• Health policies can be defined for common server health conditions
• A health policy defines a health condition, reaction, and targets

– Condition: The problem state for which to look for
– Reaction: The action to take when the condition is matched
– Targets: The resources to monitor such as a single server, static or dynamic
cluster, nodes or entire cell
• When a health policy condition is true, a corrective action runs

automatically or requires approval
– Notify administrator by sending email or SNMP trap
– Capture diagnostics such as generate heap memory dump, Java core)
– Restart the application server in a way that prevents outages and service policy
violations
• Each health policy can be in supervise or automatic mode

Figure 17-18. Health policies WA855 / VA8551.0
Notes:
WebSphere can monitor servers for common health problems and take corrective action.
Various health conditions can be defined by using health policies. When a health policies
violation is detected, an action plan can be put into effect automatically:
• Notify administrators (including email)
• Capture diagnostics information (Java thread or heap dump)
• Restart server
Application server restarts are done in a way to prevent outage and service policy
violations. WebSphere provides the “First line of defense” for poor application health by
mitigating common health problems and routing around unhealthy servers. IBM Tivoli
Composite Application Manager for WebSphere extends WebSphere health management
by adding in-depth application problem determination capabilities. To find out at a granular
level what went wrong and how to fix it fast, IBM Tivoli Composite Application Manager
gives support teams the diagnostic tools that they need. IBM Tivoli Composite Application
Manager provides Rational and Eclipse developer and test tools with performance data
V8.1
Student Notebook
Uempty captured in production, eliminating the need for attempting problem re-creation. IBM Tivoli
Composite Application Manager integrates with the broader Tivoli Automation portfolio that
enables customers to cost-effectively manage their IT infrastructure.
Student Notebook
Viewing health conditions
Figure 17-19. Viewing health conditions WA855 / VA8551.0
Notes:
You can use the administrative console to view existing health policies and create new
ones. Navigate to Operational policies > Health Policies to view any defined policies.
V8.1
Student Notebook
Uempty
Predefined health conditions
Figure 17-20. Predefined health conditions WA855 / VA8551.0
Notes:
Health conditions define the variables that you want to monitor in your environment.
Several categories of health policy conditions exist. You can choose from the listing of
predefined health conditions when creating a health policy.
Student Notebook
Heath conditions
• Age-based: amount of time the server is running
• Excessive conditions:
– Excessive request timeout: percentage of timed out requests
– Excessive response time: average response time
• Memory conditions:
– Excessive memory usage: percentage of maximum JVM heap size
– Memory leak: JVM heap size after garbage collection
• Storm drain: significant drop in response time
• Workload: total number of requests
• Garbage collection: percentage of time in garbage collection

Figure 17-21. Heath conditions WA855 / VA8551.0
Notes:
• Excessive garbage collection: Triggers when the Java virtual machine (JVM) spends
more than a configured percentage of time when running garbage collections.
• Storm drain: Detects situations where requests are shifted toward a faulty cluster
member that advertises low response times. This condition is triggered when there is a
significant drop in the average response time. This drop must be measured at the on
demand router, for a member of the cluster that is coupled with an increase in the
dynamic weights for the cluster member.
• Workload: Triggers when the members that are associated with this policy serve a
user-defined number of requests. You can use the workload condition on all server
types.
V8.1
Student Notebook
Uempty
Creating health conditions
Figure 17-22. Creating health conditions WA855 / VA8551.0
Notes:
Actions can be taken automatically, or you can have them occur in supervised mode.
Supervised mode requires an operator to confirm the action.
Student Notebook
Predefined actions
Figure 17-23. Predefined actions WA855 / VA8551.0
Notes:
When a health policy violation is detected, an action plan can be put into effect
automatically. Actions to take when a monitored condition is detected are designed to
bypass the problem and help in diagnosis. You can select the following predefined actions:
• Notifying an administrator
• Sending a Simple Network Management Protocol (SNMP) trap
• Restarting a server
• Putting a server into maintenance mode
• Generating Java cores or heap memory dumps for use in diagnosing the problem
V8.1
Student Notebook
Uempty
Administering actions
Figure 17-24. Administering actions WA855 / VA8551.0
Notes:
If you chose the Supervise reaction mode, then you receive recommendations to improve
your health conditions. These recommendations are displayed as runtime tasks that you
can accept, deny, or close. To manage runtime tasks, click System administration > Task
management > Runtime tasks in the administrative console. If you chose the Automatic
reaction mode, actions to improve the health of your environment occur automatically.
Student Notebook
Maintenance modes
• Allows you to update your environment without disrupting traffic to the
production environment
• Servers or nodes are placed into maintenance mode which stops the
routing from the intelligent routing tier
– Application placement controller also excludes server or node from automatic
application placement
– Health controller uses the maintenance mode
• Node maintenance mode

– Used to apply operating system fixes or provide WebSphere maintenance
– Only traffic with affinity to servers on the node is routed to server
• Server maintenance mode

– Perform server level problem determination
– Modes to allow all traffic to the server, allow only traffic with affinity, or allow no
traffic
Figure 17-25. Maintenance modes WA855 / VA8551.0
Notes:
Periodic product maintenance is important to ensure that your system environment works
correctly, and to avoid trouble that known issues cause. At some point in time, you might
have a problem with a server and find that diagnostic tests are necessary to troubleshoot a
specific application server. These situations can lead to the disruption of client requests to
servers in your environment.
Using the Intelligent Management feature, you can maintain the environment without
disrupting traffic to the production environment. You can use it to administratively put a
server or node in the cell into maintenance mode.
Node maintenance mode:
You can put a node into maintenance mode when you want to apply operating system
fixes or do WebSphere maintenance. When a node is in maintenance mode, only traffic
with affinity to servers on the node is routed to the server by the on demand router. You
can set a maintenance immediate stop mode that immediately stops the servers on the
node.
V8.1
Student Notebook
Uempty Server maintenance mode:

You can put a server into maintenance mode when you want to do server level problem
determination. When an application server is placed into maintenance mode, you can
indicate one of these modes:
- Allow all traffic to the server
- Allow only traffic with affinity
- Allow no traffic during the maintenance period
Student Notebook
Custom health conditions

• Enables you to create expressions that define what “unhealthy” means
in your environment
• Custom expressions can be built which use metrics from:

– The on demand router, URL return codes
– PMI metrics, MBean operations, and attributes such as hung thread detection,
connection pool exhaustion or slow down
– And other metrics
• Complex Boolean expressions by using a mix of operands are

supported (AND, OR, NOT)
• Provides flexibility by allowing the definition of custom actions that

allow administrators to define an action plan to be carried out when the
unhealthy situation detected
Figure 17-26. Custom health conditions WA855 / VA8551.0
Notes:
You can define custom conditions for your health policy if the predefined health conditions
do not fit your needs. You define a custom condition as a subexpression that is tested
against metrics in your environment. When you define a custom condition, consider the
cost of collecting the data, analyzing the data, and if needed, enforcing the health policy.
This cost can increase depending on the amount of traffic and the number of servers in
your network. Analyze the performance of your custom health conditions before you use
them in production.
For further information about creating custom conditions, go to the following website:
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/
com.ibm.websphere.wve.doc/ae/cwve_hconditionsubex.html
V8.1
Student Notebook
Uempty 17.4.Application edition management
Student Notebook
Application edition
management

Figure 17-27. Application edition management WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is Application edition management?

• Application versioning model that supports multiple deployments of the
same application in the cell
– The ability to upgrade applications without incurring outages or interruptions to
users
• Concurrently run multiple editions of an application

– Automatically route users to a specific application
• Includes an easy-to-use edition control center in administrative

console, plus full scripting support
• Capabilities include:
– Roll out policies to switch from one edition to another with no loss of service
– Concurrent activation, where multiple editions can be concurrently active for an
extended period
– A validation mode to send selective traffic to verify correct operation
Figure 17-28. What is Application edition management? WA855 / VA8551.0
Notes:
Application edition management enables management of interruption-free production
application deployments. Using this feature, you can validate a new edition of an
application in your production environment without affecting users, and upgrade your
applications without incurring user outages. You can also run multiple editions of a single
application concurrently, directing different users to different editions, as the ODR
maintains not only traditional application state (for example, HTTP session) affinity, but also
application version affinity. The ability to queue requests is also employed with the
Intelligent Management application edition function, if you want the following outcomes:
• An “atomic” application update that allows preprovisioning of a new application version
• An “atomic” update of all users from the old application version to the new application
version
Student Notebook
Terminology
• Application editions: represents a unique instance of an application in
the environment
– Defined by the application name and an edition name
– Might be a distinct build version
– Might be the same build version with different deployment bindings (for example,
resource references)
– Might be both
• Edition name: name of each edition of a particular application
• State: identifies the status of the application edition

– Active: installed and available within a running application server
– Inactive: installed but not available
– Validation: used to selectively send traffic to an application server for testing or
debugging purposes
Figure 17-29. Terminology WA855 / VA8551.0
Notes:
Application editions:
An application edition represents a unique instance of an application in the
environment. An application edition encompasses both application versions and
deployment bindings. An application edition is an application that is uniquely identified
as the combination of an application name and an edition name.
Edition names and descriptions:
With the application edition manager, you can install multiple editions of the same
application. Each edition is identified with an application edition name and description.
The edition name is a field in which you can specify a value to uniquely identify one
application edition from other editions of the same application. Create a version number
scheme for naming editions that is meaningful in your environment. Multiple editions of
the same application have the same application name but different edition names.
When deploying an application, you can also specify an edition description next to the
edition name, which gives you the ability to store more information.
V8.1
Student Notebook
Uempty Non-destructive update:

The existing application installation and update functions in Network Deployment are
destructive. That is, they replace the old instance of the application with a new instance.
Installing an application edition is non-destructive. You can install any number of
application editions and keep them in the system management repository.
Student Notebook
Components
• Application edition manager
– Interacts with the intelligent routers, dynamic workload manager, and application
placement manager
• Application edition manager’s edition control center

– Provides control over the application update and rollout process, including edition
activation across the application servers to which your application is deployed
– Built into the administrative console
Figure 17-30. Components WA855 / VA8551.0
Notes:
The application edition manager ensures interruption-free production application
deployments. Interruption-free deployment prevents loss of service when you install an
application update in your environment.
The application edition manager provides an application versioning model that supports
multiple deployments of the same application in the Intelligent Management cell. Each
deployment has a unique edition name. The application edition manager allows you to
select the edition to activate on an Intelligent Management cluster so that you can do a
rollout of an application update or revert to a previous level.
The application edition manager is fully integrated with Intelligent Management, interacting
with the on demand router (ODR), dynamic workload balancing, and the application
placement manager. This integration ensures predictable application behavior when you
apply application updates, and a smooth transition from one application edition to another
while the system continues to manage your application performance goals. You can access
application update processes with the administrative console, including edition activation
across the application servers.
V8.1
Student Notebook
Uempty
Rollout activation (1 of 2)
• Activates one edition in place of another edition of an application
• Soft or hard rollout

– Soft rollout starts only the application
– Hard rollout stops and starts the application server
• Atomic or group rollout

– Atomic rollout guarantees that two editions do not service requests at the same
time and queues requests
– Group rollout might have two editions service requests at the same time; and it
does not queue requests
• Drainage interval defines the maximum amount of time the application

edition manager waits for sessions to expire before stopping an
application server
Figure 17-31. Rollout activation (1 of 2) WA855 / VA8551.0
Notes:
Rollout activation activates one edition in place of another, ensuring an interruption-free
update in the process. Thus, all application requests are serviced during the rollout, and
none are lost. This process ensures continuous application operation from the perspective
of the customers of that application. To do the rollout, the application edition manager
carefully coordinates the activation of the edition and the routing of requests to the
application.
Student Notebook
Rollout activation (2 of 2)
Quiesce
and stop Edition 2.0
Restart
Application
requests Edition 1.0
Intelligent
routers
Edition 1.0
Dynamic cluster
Figure 17-32. Rollout activation (2 of 2) WA855 / VA8551.0
Notes:
Replacement of one edition with another in a production environment requires certain
discipline in the evolution of the application. Because edition replacement happens while
application users are potentially accessing the previous application edition, the new edition
must be compatible with earlier versions. Thus, the new edition cannot add or change any
existing application interfaces, including essential behavior. New interfaces can be added.
In addition, existing interfaces can be algorithmically corrected and, in some cases, even
extended and remain compatible with existing application users.
This slide displays an example of a group rollout scenario. In the diagram, a dynamic
cluster is created that consists of three servers. You first must divide the cluster into
groups, which tells the application edition manager how many servers to update at the
same time. If you do a rollout on a group, the servers in each group are upgraded to the
new edition at the same time. Each server in the group is quiesced, stopped, and reset.
As the rollout is run in the diagram on the slide, one server in the cluster is moved from
Edition 1.0 to Edition 2.0. During this time, the server does not receive user requests that
are directed from the on demand router, and the server is stopped. All application requests
V8.1
Student Notebook
Uempty are sent to the servers that are running Edition 1.0. After the server that is running Edition
2.0 is available, the on demand router directs application requests to that server. Any
servers that are still running Edition 1.0 do not serve requests until the edition is updated to
Edition 2.0.
Student Notebook
Concurrent activation
Routing Cluster 1
policy
Edition 1.0
Intelligent
routers Edition 2.0
Legends:
Edition 1.0 requests
Cluster 2
Edition 2.0 requests
Figure 17-33. Concurrent activation WA855 / VA8551.0
Notes:
Concurrent activation enables you to activate the same edition on different servers or
clusters. To use multiple editions concurrently, you must distinguish user requests from one
another so that the requests are sent to the application server that hosts the appropriate
edition. For example, if you introduce a new edition of an application, you might want only a
select group of users to test the edition.
V8.1
Student Notebook
Uempty
Validation mode
Dynamic cluster
Routing DC1
policy
Edition 1.0
Clone
Intelligent
routers Edition 2.0
Legends:
Edition 1.0 requests Dynamic cluster
Edition 2.0 requests DC1-validation
Figure 17-34. Validation mode WA855 / VA8551.0
Notes:
Validation activation is a special form of concurrent activation. It activates an edition on a
clone of its original deployment target. The clone is created on activation of the edition.
After the validation rollout to the original deployment target, the clone is removed
automatically. This action allows you to do final preproduction testing of an application
edition in the actual production environment with a selected set of users.
Student Notebook
Edition control center (1 of 2)
Figure 17-35. Edition control center (1 of 2) WA855 / VA8551.0
Notes:
To use the administrative console to validate the results, click Applications > Edition
Control Center > application_name.
V8.1
Student Notebook
Uempty
Edition control center (2 of 2)
Figure 17-36. Edition control center (2 of 2) WA855 / VA8551.0
Notes:
This slide displays editions for the BeenThere application.
Student Notebook
V8.1
Student Notebook
Uempty 17.5.Performance Management
Student Notebook
Performance Management

Figure 17-37. Performance Management WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is Performance Management?

• Provides a self-optimizing middleware infrastructure
• Ability to improve performance by using dynamic clustering and

overload protection
• Dynamic clusters are used to scale up and scale down running cluster
members to meet response time goals
• Overload protection limits the rate at which the on demand router

forwards traffic to application servers
– Prevents heap exhaustion, processor exhaustion, or both from occurring
Figure 17-38. What is Performance Management? WA855 / VA8551.0
Notes:
The performance management feature provides dynamic cluster capabilities and overload
control. With dynamic clusters, you can automatically scale up and down the number of
running cluster members as needed to meet response time goals for your users. You can
use overload protection to limit the rate at which the on demand router forwards traffic to
application servers. Doing so helps prevent heap exhaustion, processor exhaustion, or
both from occurring.
Student Notebook
V8.1
Student Notebook
Uempty 17.6.Deployment manager high availability
Student Notebook
Deployment manager high

availability

Figure 17-39. Deployment manager high availability WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Highly available deployment manager (1 of 3)

• WebSphere supports running multiple deployment managers for high
availability when using the ODR intelligent router
• Multiple deployment managers can be configured

– Active: the primary deployment manager that hosts the administrative functions
– Standby: waiting to take over if the active deployment manager fails
• One deployment manager is active, others run in standby mode until a

failure is detected
• All deployment managers share master configuration repository and

workspaces that are stored in a shared file system that supports fast
lock recovery
• The on demand router routes traffic to the active deployment manager

Figure 17-40. Highly available deployment manager (1 of 3) WA855 / VA8551.0
Notes:
Although it is not required to have a deployment manager that is always running, you might
require highly available administrative capability. This need occurs especially in
environments that have a significant number of new application deployments or updates
and server monitoring. Multiple instances of a deployment manager remove the single
point of failure (SPOF) for cell administration, thus assuring the attainability of the
administrative console, wsadmin, and scripting features to manage your environment.
WebSphere Application Server provides a mechanism for cloning your existing deployment
manager, thus achieving high availability, by employing redundant deployment managers
with a hot-standby model and the use of a shared file system.
Student Notebook
Administrative
console Active deployment
On demand
routers manager
Shared
file system
Standby deployment
manager
Notes:
In this paradigm, one of the deployment managers is elected as primary. As primary, it is
considered an active deployment manager that is hosting the cell-wide endpoints for the
administrative functions. Other deployment managers are considered backups; they are
kept in standby mode and are available to take over the active role in case of failure or
termination of the primary manager.
V8.1
Student Notebook
Uempty
Administrative
console Active deployment
On demand
routers manager
Shared
file system
Standby deployment
manager
Active deployment
manager
Notes:
A highly available deployment manager component runs in each deployment manager to
control which deployment manager is elected as the active one.
Student Notebook
Unit summary
Notes:
V8.1
Student Notebook
Uempty
1. True or false. WebSphere provides the ability for a hot standby for a
deployment manager to be highly available.
2. Which intelligent management component maintains cell topology

information and keeps the other controllers informed of the
environment?
A. Dynamic workload controller
B. Autonomic request flow manager
C. On demand configuration service
3. True or false. An on demand router can route requests within the cell
only.
Notes:
1. 
2. 
3.
Student Notebook
Checkpoint answers
1. True. WebSphere provides the ability for a hot standby for a
deployment manager to be highly available, but only when using the
on demand router intelligent router
2. Which intelligent management component maintains cell topology

information and keeps the other controllers informed of the
environment?
C. On demand configuration service
3. False. An on demand router can route requests within the cell and
can route to multiple cells.
Notes:
V8.1
Student Notebook
Uempty Unit 18. WebSphere security

In this unit, you learn basic security concepts and architecture that
apply to WebSphere Application Server. You learn how to configure
administrative security, application security, and Secure Sockets Layer
(SSL).

• Explain basic security concepts
• Describe the WebSphere Application Security architecture
• Describe enhancements to certificate management
• Configure fine-grained administrative security
• Configure application security
• Describe SSL concepts and configuration
• Describe support for multiple security domains
• Describe auditing features and functions
• Describe support for Java Platform, Enterprise Edition 6 (Java EE
6) security annotations

• Lab exercises
References
index.jsp
© Copyright IBM Corp. 2013 Unit 18. WebSphere security 18-1

Student Notebook
Unit objectives
• Describe support for Java Platform, Enterprise Edition 6 (Java EE 6)
security annotations
Notes:
V8.1
Student Notebook
Uempty
Topics
• WebSphere security basics
• WebSphere user registries
• Administrative security
• Application security
• Security domains
• Java 2 security
• SSL basics
• Certificates and certificate authorities
• SSL within a WebSphere cell
• Security auditing
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 18.1.WebSphere security basics

Student Notebook
WebSphere security basics

Figure 18-3. WebSphere security basics WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Basic security end-to-end model

Web Domain
Client Firewall Apps Data
servers firewall
(Internet) (DMZ) (Intranet)
The client is the This server is the corporate The “apps” are the
customer. The web server. It provides the business logic.
client can be either universal access to the business These applications
a single user PC or logic for the company. It allows have access to the
a whole company. browser access to the corporate databases and
The devices are site. In front of the web server is provide the
specified when the router-access device for the company business
necessary. site. rules.
This firewall is the router to the Internet. An This data is the corporate data. Ultimately, it is
ISP (Internet service provider) typically the information that the company wants to
provides it. This model, however, can apply to share with the customer. This data can be
a corporate intranet. This router separates the centralized or distributed. For this example, the
internal network from the outside network. data is accessed through business logic.
Figure 18-4. Basic security end-to-end model WA855 / VA8551.0
Notes:
With an e-business application, a general topology must be secured from end to end. This
process involves securing many different parts.

Student Notebook
WebSphere Application Server security overview

• Security can be *HTML
applied at different WebSphere
*JSPs, servlets, EJB
resources
levels
WebSphere security
Security APIs
File system security
OS security
Network security
Physical security
Figure 18-5. WebSphere Application Server security overview WA855 / VA8551.0
Notes:
Many levels are involved in securing an environment. WebSphere provides only part of the
total security that must be applied.
Physical security refers to the protection of the hardware itself. Is it kept in a safe and
secure area? Who has physical access to it?
Network security can involve setting up firewalls to protect an intranet or a DMZ where the
web servers are going to run.
Operating system security is the security infrastructure of the underlying operating system.
It provides certain security services to the WebSphere security application. These services
include the file system security support to secure sensitive files in WebSphere product
installation. The WebSphere system administrator can configure the product to obtain
authentication information directly from the operating system user registry; for example, the
NT Security Access Manager (SAM).
File system security is especially a concern about protecting your configuration files and
key ring files.
V8.1
Student Notebook
Uempty Security APIs are as follows:

• JVM: The JVM security model provides a layer of security above the operating system
layer.
• CORBA security: Any calls that are made among secure ORBs are over a Secure
Association Service (SAS) or CSIv2 layer that sets up the security context and the
necessary quality of protection. After the session is established, the call is passed up to
the enterprise bean layer. This layer is for a distributed platform only.
• Java EE security: The security collaborator enforces Java EE-based security policies
and supports Java EE security APIs.
• WebSphere security: WebSphere security enforces security policies and services in a
unified manner on access to web resources and enterprise beans. It consists of
WebSphere security technologies and features to support the needs of a secure
enterprise environment.

Student Notebook
WebSphere security service: Big picture

• Security service runs locally in each process (deployment manager,
node agent, and application server)
– Security workload not bottlenecked to a single process
– Security service failure affects only a single process
• Separation of authentication mechanism and user registry
Deployment manager
Security
Service Node agent
Administrator
Security
Node agent service
Configuration
Security
service Application server
Application server Security
Application server
Security service
Security service
service
User
registry Configuration
Configuration
Configuration © Copyright IBM Corporation 2013
Figure 18-6. WebSphere security service: Big picture WA855 / VA8551.0
Notes:
The security service runs within each of the managed processes so there is not a single
point of failure (other than possibly the user registry, but that is a different topic).
V8.1
Student Notebook
Uempty
Types of security
– Protects things such as administrative console, wsadmin, scripts
– Protects
access to the
applications
• Java 2 security
– Protects the
local systems
Figure 18-7. Types of security WA855 / VA8551.0
Notes:
Within WebSphere, there are a number of different types of security that can be configured.
These types of security are covered in more detail during this lecture. They include:
• Java 2 security

Student Notebook
Administrative security
• Protects administrative console, scripts, wsadmin, and others
• Access can be restricted through:
– Administrative roles
– Fine-grained
access
Figure 18-8. Administrative security WA855 / VA8551.0
Notes:
Administrative security allows the administrator to restrict access to the administrative
interfaces, including the administrative console, the administrative scripts, and wsadmin.
V8.1
Student Notebook
Uempty
Application security
• Enables security for the applications in your environment
• Provides application isolation and requirements for authenticating
application users
– Security constraints protect servlets
– Method permissions protect EJBs
Figure 18-9. Application security WA855 / VA8551.0
Notes:
Application security allows the administrator to restrict access to the enterprise
applications. This restricted access is done by defining security roles, security constraints,
and method permissions. Then, the security roles are mapped to the users and groups in
the environment.

Student Notebook
Authentication and authorization: What is the difference?

• There is a distinction between authentication and authorization
– Authentication Æ Who are you?
– Authorization Æ When authenticated, what are you allowed to do?
What
can you
Who are
do?
you?
Authorization
Authentication
User
registry
EAR file © Copyright IBM Corporation 2013
Figure 18-10. Authentication and authorization: What is the difference? WA855 / VA8551.0
Notes:
Authentication information can be found in a user registry. Authorization information can be
found within the EAR file. The WebSphere security service is responsible for making sure
that protected resources are accessible only by authenticated and correctly authorized
users.
V8.1
Student Notebook
Uempty
Challenge mechanism: Authentication basic steps

Server
Client
Request
Challenge
User name and password (credentials)
Authentication,
credentials
Authentication: tell a server who you are
• Challenge mechanism (how you are
asked) is used to obtain authentication data:
– Basic authentication User
– Certificate-based registry
– Form-based authentication (preferred)

• Challenge mechanism is defined in the deployment descriptor
• Credentials are validated against user registry
Figure 18-11. Challenge mechanism: Authentication basic steps WA855 / VA8551.0
Notes:
Authentication in its simplest form is rather straightforward.
• A request is made.
• A challenge is returned.
• A user ID and password are sent.
• The server checks a user registry to see whether the information is valid.

Student Notebook
Challenge mechanism: Basic authentication
1 Request web page
401 and server

2
certificate (if https)
Browser User name = peter server

3
Password = pumpkin
• Warning: password is not encrypted, merely encoded

– Make sure that this channel is over HTTPS
• Warning: basic authentication token is sent across in the HTTP header
– Danger: there is no way for the server to remove the token during a logout
– If you walk away from a public browser, even if you log off, your credentials are
still stored in the browser
– Another person can walk up and be automatically logged in to your site
– To remove the basic authentication token, close the browser or explicitly tell the
browser to delete authentication credentials
Figure 18-12. Challenge mechanism: Basic authentication WA855 / VA8551.0
Notes:
HTTP basic authentication is not a secure authentication mechanism. Basic authentication
sends user names and passwords over the Internet as text that is Base64 encoded, and
the target server is not authenticated. This form of authentication can expose user names
and passwords. If someone can intercept the transmission, the user name and password
information can easily be decoded. However, when a secure transport mechanism, such as
SSL, or security at the network level, such as the IPSec protocol or VPN strategies, is used
with basic authentication, some of these concerns can be alleviated.
For more information, see:
http://docs.sun.com/app/docs/doc/819-3669/bncbn?l=en&a=view
V8.1
Student Notebook
Uempty
Challenge mechanism: Form-based authentication

• Defined within the application
• Suggested approach
1 Request for protected resource
2
Redirect to
login page Server
3
Form submitted Security_check
4
Redirect to source ?
error.jsp
Error page is
returned
Figure 18-13. Challenge mechanism: Form-based authentication WA855 / VA8551.0
Notes:
1. A client requests access to a protected resource.
2. If the client is unauthenticated, the server redirects the client to a login page.
3. The client submits the login form to the server.
4. The server attempts to authenticate the user. If authentication succeeds, the
authenticated user’s principal is checked to ensure that it is in a role that is authorized
to access the resource. If the user is authorized, the server redirects the client to the
resource that uses the stored URL path. If authentication fails, the client is forwarded or
redirected to an error page.

Student Notebook
Defining the challenge type

• Challenge types are set in the EAR deployment descriptors
– The default that Rational Application Developer uses is basic authentication
– Form-based is defined by adding a login configuration
Figure 18-14. Defining the challenge type WA855 / VA8551.0
Notes:
The challenge type is defined within the EAR. Using Rational Application Developer, it can
be defined within the deployment descriptor. The default type is basic authentication.
V8.1
Student Notebook
Uempty 18.2.WebSphere user registries

Student Notebook
WebSphere user registries

Figure 18-15. WebSphere user registries WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Registries and authentication mechanisms

File-based registry
Authentication calls Federated (default)
LDAP 1 LDAP 2
Local OS
Authentication calls authentication
layer
Security
server
Local OS registry
LTPA
Authentication calls authentication
layer
Stand-alone LDAP
Pluggable
Authentication calls custom
authentication
WebSphere provided layer
Custom provider Custom registry
Figure 18-16. Registries and authentication mechanisms WA855 / VA8551.0
Notes:
The user registries that are supported include local operating system, stand-alone LDAP,
custom user registry, and federated registry. The federated registry effectively combines
multiple repositories into a single view. It can support multiple LDAP servers, file-based
repository, database repository, and custom repositories.

Student Notebook
Defining user registries
• Use the administrative

console to configure
user registries
– Manually (preferred)
– Wizard (considered too
simplistic)
Figure 18-17. Defining user registries WA855 / VA8551.0
Notes:
Defining which user registry is used and how it is configured can be done through the
console, through a manual interface, or through a wizard. Generally speaking, the wizard is
considered too simplistic to be used for configuring anything but the simplest
configurations.
V8.1
Student Notebook
Uempty
Manual security configuration
• The steps depend on the

specific environment and
which repository is being
configured
• Much more detailed than
the security wizard
Figure 18-18. Manual security configuration WA855 / VA8551.0
Notes:

Student Notebook
Security wizard: Step 1

• Not detailed
enough to be
used for
anything but
simple
environments
Figure 18-19. Security wizard: Step 1 WA855 / VA8551.0
Notes:
Although the wizard that is used to configure security can set up simple environments, it is
typically used for only the most basic configurations.
This diagram shows step 1 of the security wizard.
V8.1
Student Notebook
Uempty
Notes:
This diagram shows step 2 of the security wizard. The user repository is being selected.

Student Notebook
Notes:
This diagram shows step 3 of the security wizard and specifies the user name and
password for the primary administrative user.
V8.1
Student Notebook
Uempty
Notes:
This diagram shows the summary of the security wizard.

Student Notebook
User registry support
• WebSphere Application Server supports some user registries
Local OS LDAP
NT Domain, NT WorkGroup, Windows IBM Tivoli Directory Server
IBM SecureWay Directory Server

AIX
Sun Java System Directory Server
Solaris
IBM Lotus Domino
HP-UX
Microsoft Active Directory
Linux Novell eDirectory
OS/400 Custom (requires addition configuration)
Figure 18-23. User registry support WA855 / VA8551.0
Notes:
Although there are supported LDAP servers, other LDAP servers can also be used by
defining the appropriate schema mappings through the advanced LDAP properties.
Generally, avoid local OS registries, particularly in distributed, non-domain environments.
V8.1
Student Notebook
Uempty
Federated repositories
Federated File-
• The installation wizard and registry based
profile management tools have
a default of enabling
administrative security
LDAP1 LDAP2
– The default repository type is a
file-based federated repository
• Federated repositories provide for the
use of multiple repositories with WebSphere Application Server
• Can be:
– File-based – Database
– Single LDAP – Multiple LDAPs
– Custom registry – Subtree of an LDAP
• Defined and theoretically combined under a single realm
• All of the user repositories that are configured under the federated
repository are invisible to WebSphere Application Server
Figure 18-24. Federated repositories WA855 / VA8551.0
Notes:
This slide covers the federated repositories and what can be used:
• File-based
• Single LDAP
• Custom registry
• Database
• Multiple LDAPs
• Subtree of an LDAP
The VMM (Virtual Member Manager) provides federation capabilities.

Student Notebook
Custom registry: Configuration
Configured from administrative

console:
• Security > Global security
• Select Stand-alone custom registry
from the Available realm definitions
• Click Configure
– User name and password must exist
– Class name must be implemented
and in class path
Figure 18-25. Custom registry: Configuration WA855 / VA8551.0
Notes:
The custom registry allows custom implementation of user registry.
Some possible implementations include:
• Database
• Flat file
• OS-based, with more custom logic
• Use other, not directly supported, registries
WebSphere provides:
• Base types
- Implementing classes extend the com.ibm.websphere.security.UserRegistry
class
• Working sample implementation: com.ibm.websphere.security.FileRegistrySample
V8.1
Student Notebook
Uempty
Authentication mechanism: LTPA

z Allows the identity of a user to be passed around the distributed network

9. Pass token
1. Request 8. Pass user credentials (token) over secure
to EJS when using methods on association
2. Challenge user EJB
for authentication EJB EJB
server server
3. User
authenticates
7. Create 5. Verify user

4. Authenticate
authToken name and
(authentication data)
cookie; serve password in
the request LDAP user
6. Issue registry
authentication
token
Security service Stored user

information
Figure 18-26. Authentication mechanism: LTPA WA855 / VA8551.0
Notes:
Regardless of what registry type is used, an LTPA token is generated, and then shared with
the client in the form of a cookie. The token, or the information in the token, can be used
throughout WebSphere to pass the user’s identity information around.

Student Notebook
LTPA provides delegation
ID = client ID = X
client
server1 server2
X can run as:
Option 1. Client
Option 2. Server 1
Option 3. Specified identity
• Using an LTPA token supports delegation
Figure 18-27. LTPA provides delegation WA855 / VA8551.0
Notes:
A request for work can pass its security context, which contains its credentials. As the call
proceeds through the servers to its final destination, credentials can be changed. The
options are to keep the client’s credentials, switch to the credentials of the server, or some
other specified identity.
V8.1
Student Notebook
Uempty
LTPA provides single sign-on (SSO)
• As soon as clients have a valid

LTPA token, they do not need to
reauthenticate within a cell (until
the LTPA token expires)
• SSO is on by default
• Issues cookies to web browser to
track user authentication
information
• Provides for SSO within or even
between WebSphere cells
Figure 18-28. LTPA provides single sign-on (SSO) WA855 / VA8551.0
Notes:
It is also possible to configure multiple cells to share LTPA tokens, thus creating SSO for
multiple cells.

Student Notebook
V8.1
Student Notebook
Uempty 18.3.Administrative security

Student Notebook

Notes:
Administrative security protects not only the administrative tools, but also enables a
number of other security features:
• Authentication of HTTP and IIOP clients
• Administrative console security
• Naming security
• Use of SSL transports
• Role-based authorization checks of servlets, EJBs, and MBeans
• Propagation of identities (RunAs)
• The common user registry
V8.1
Student Notebook
Uempty
Turning on administrative security enables many features, including:
• Authentication of HTTP and IIOP clients
• Administrative console security
• Naming security
• Use of SSL transports
• Role-based authorization checks of servlets, EJBs, and MBeans
• Propagation of identities (RunAs)
• The common user registry
Console and other administrative tools: access is initially restricted to
only the primary user
• You must create your administrative users and groups
• As of version 7, fine-grained access can be defined for console users
– For example, Bob can be configured to have administrative access to application
servers A and B
– Fred can be configured to have operator access to only servers C and D
Notes:
As soon as global security is enabled, there is a security check when the console
application is accessed. The security check makes sure that the accessing user is
authenticated and is mapped to one of the four console security roles. Depending on the
console role to which the user is mapped, different functions are available.
Whichever user ID is used to run the application server process has implicit access as a
console administrator user.

Student Notebook
Console security
Defines which roles have access to the administrative tools
• Monitor: least privileged; allows a user to view the WebSphere configuration and
current application server state
• Configurator: monitor privilege plus the ability to change the WebSphere
configuration
• Operator: monitor privilege plus the ability to change runtime state, such as starting
or stopping servers
• Administrator: operator, configurator, and iscadmins privilege, plus more privileges
that are granted solely to the administrator role, such as:
– Modifying the primary administrative user and password
– Mapping users and groups to the administrator role
– Enabling or disabling administrative
Administrator
and Java 2 security
Security
check
Configurator Monitor Operator
Administrative
console
Application
server
C:\> wsadmin
Figure 18-31. Console security WA855 / VA8551.0
Notes:
There are more console security roles available; these include iscadmins, deployer, and
AdminSecurityManager.
V8.1
Student Notebook
Uempty
Additional console security roles

• iscadmins (Integrated Solutions Console)
– Only available for administration console users
– Allows a user to manage users and groups in the federated repositories
• Deployer
– Allows a user to change configuration and runtime state on applications that use
wsadmin
• Admin Security Manager

– Allows a user to map users to administrative roles by using wsadmin
– When restricted access to resource authentication data is in effect, users can
also manage authorization groups
• And others
Figure 18-32. Additional console security roles WA855 / VA8551.0
Notes:
This graphic shows a representation of the various administrative security roles that are
available, and how they overlap.

Student Notebook
Administrative roles
Edit
Administrator * security
Configurator Operator
Deployer
Monitor
iscadmins
Edit
roles
AdminSecurityManager * Auditor *
Edit audit
* = implicitly part of primary administrative user
Figure 18-33. Administrative roles WA855 / VA8551.0
Notes:
This diagram shows the creation of users and groups through the administrative console.
V8.1
Student Notebook
Uempty
Console security: Creating users and groups

• To set up console security
– Turn on administrative security
– Create console users and groups
– Done in active user registry
Figure 18-34. Console security: Creating users and groups WA855 / VA8551.0
Notes:
This diagram shows the mapping of users to specific console security roles. The interface
for mapping administrative groups is virtually the same.

Student Notebook
Console security: Mapping users and groups

• To set up console security
– Turn on administrative security
– Create console users and groups
– Map users and groups to
administrative roles
Figure 18-35. Console security: Mapping users and groups WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 18.4.Application security

Student Notebook
Application security

Figure 18-36. Application security WA855 / VA8551.0
Notes:
Java EE security can provide the rules engine through the WebSphere Application Server.
Alternatively, another authorization service (such as Tivoli Access Manager) can be used.
V8.1
Student Notebook
Uempty
Authorization
Authorization involves granting trusted principals permission to perform
actions on resources (web pages, servlets, JSPs, and EJB components)
Control access to resources
• Security lookup (by server)
– Determine security privileges for principal
– Access information that is stored in registry
• Rule enforcement (by server)
– Obtain rules from registry
– Given privileges of
principal and rules,
determine access
Decision
opY??? Rules
userX, opY
userX??
client server
Figure 18-37. Authorization WA855 / VA8551.0
Notes:
Java EE security is concerned with controlling access to application resources, not system
resources.

Student Notebook
Security roles: Application authorization

EAR file
• Use security roles for
authorization Web module
– Specify security at an abstract Servlets
JSP,
level without knowledge of actual HTML
users and groups
EJB module
• Security roles are then applied to
the web and EJB application
components
– Web URIs or EJB methods
Security
roles
• Binding of the users and groups
to the security roles is generally Binding
done at the application
installation time
– Can be done post-installation as
well Users and
groups
Figure 18-38. Security roles: Application authorization WA855 / VA8551.0
Notes:
To control who can do what to an application, several XML objects can be added to the
EAR file. It is worth noting that these XML objects do not actually affect the application
code itself.
The first step is to create security roles. These roles are merely XML objects that the
runtime uses to define which users and groups have access to the application. The second
step is to map the security roles to the application code. These mappings are also just XML
objects. These mappings are called security constraints (for web container objects) and
method permissions (for EJBs). Again, these XML objects do not affect the application
code; they are merely part of the deployment descriptors.
V8.1
Student Notebook
Uempty
Securing Java EE application artifacts: Part 1

EAR file
EJB
Manager method
Method
permissions EJB
method
EJB
Teller method
Enterprise
JavaBeans
Security permissions
Servlet
Customer Security
constraints JSP
HTML
Java EE Web
security resources
roles
Figure 18-39. Securing Java EE application artifacts: Part 1 WA855 / VA8551.0
Notes:
During the deployment process (or afterward), the security roles are mapped to the users in
groups in the environment. This mapping means that the runtime is able to understand
which users and groups in its environment must access the various objects in the
application code.
In this example, the security role that is called Manager is mapped to various application
methods (perhaps the method that is used to create a customer bank account). The actual
user who is called Bob is mapped to the security role Manager during deployment.
Therefore, when a user attempts to access the method for creating a bank account, the
runtime sees that there is a constraint on that method. It checks to make sure that the user
is mapped to the Manager security role. If not, the user gets an authorization failure.

Student Notebook
Securing Java EE application artifacts: Part 2

EAR file
EJB
Manager method
Method
permissions EJB
Bob method
EJB
Mary Teller method
Enterprise
JavaBeans
Alice Security role binding Security permissions
Servlet
Customer Security
constraints JSP
HTML
Clients Java EE
Users and Web
security resources
groups roles
Figure 18-40. Securing Java EE application artifacts: Part 2 WA855 / VA8551.0
Notes:
The security roles are defined within the EAR. This screen shows the SampAdmin security
role within the PlantsByWebSphere application.
V8.1
Student Notebook
Uempty
Applying application security

• Application security can be applied to resources within an EAR
– Security roles are defined in the application deployment descriptor
– Servlets and JSPs are protected with security constraints, which are mapped
to the security roles
– EJBs are protected with method permissions, which are mapped to the
security roles
• The security roles are then mapped to actual users and groups
during installation of the application
Figure 18-41. Applying application security WA855 / VA8551.0
Notes:
This screen shows the constraints for the PlantsByWebSphere application, which is
mapped to the SampAdmin security role.

Student Notebook
Creating security constraints

• After the security role is created, it can be mapped in a security
constraint to protect web application artifacts
Figure 18-42. Creating security constraints WA855 / VA8551.0
Notes:
As soon as the application is deployed, the console can be used to map the security roles
to the actual user and groups that exist within that environment. This mapping can be done
at deployment time or any time thereafter through the security role to user and group
mapping functions.
V8.1
Student Notebook
Uempty
Using the console to map security roles

• The mapping of users and groups to security roles can take place
during or after application installation
– After
installation,
use the
administrative
console to go
to the
application
and under
Detailed
Properties,
select
Security role
to user/group
mapping
Figure 18-43. Using the console to map security roles WA855 / VA8551.0
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 18.5.Security domains

Student Notebook
Security domains

Figure 18-44. Security domains WA855 / VA8551.0
Notes:
Security domains are a new feature as of WebSphere 7 and allow security to be defined at
multiple levels, not just at the cell level. Previously the security model for the cell was all
that could be defined. Now, with security domains, it is possible to define one set of security
settings for one application server and another set of configurations for a second
application server.
V8.1
Student Notebook
Uempty
Security domains
• Multiple security domains are supported as of WebSphere Application
Server version 7
– Can create different security configurations and assign them to different
applications
– Can configure different security attributes for both administrative and user
applications within a cell environment
– Can configure different applications to use different security configurations by
assigning the servers, clusters, or service integration buses to the security
domains
• Only users that are assigned to the administrator role can configure
multiple security domains
• For example, with security domains, it is possible to have different user

registries that are configured for distinct parts of the cell
Notes:
This screen shows a security configuration that is defined at a cell level.

Student Notebook
Security configurations
• Traditionally, the security configuration was defined at a cell level
– A side effect was all elements of the cell shared the exact same security
configuration
Security
configuration
DMgr
Cell
server1 cluster1 cluster2 server2 server3
Figure 18-46. Security configurations WA855 / VA8551.0
Notes:
This screen shows not only a security configuration that is defined at a cell level, but more
configurations for specific scopes. This configuration means that it is possible to define
security behavior specific to certain scopes, which is different from what is configured for
the cell level.
V8.1
Student Notebook
Uempty
Security domains
• With security domains, it is possible to have a cell level security
configuration, and multiple other security configurations at different
scopes
Cell level security
configuration server2 security
configuration
Cell level security DMgr
Cell
configuration
server1 cluster1 cluster2 server2 server3
Notes:
These diagrams show the use of the administrative console to create a security domain.

Student Notebook
Creating a security domain

• Use the console to create a security domain
– Security > Security domains > New
Figure 18-48. Creating a security domain WA855 / VA8551.0
Notes:
These diagrams show some of the different levels for which security domains can be used.
Examples can include having different user registries for different security domains. It is
also possible to change settings for application security, Java 2, user registries (User
Realm), and others.
V8.1
Student Notebook
Uempty
Configuring a security domain

• Define a scope and configure the attributes
– It is possible to enable application security for only the PlantsByWebSphere
Figure 18-49. Configuring a security domain WA855 / VA8551.0
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 18.6.Java 2 security

Student Notebook
Java 2 security

Figure 18-50. Java 2 security WA855 / VA8551.0
Notes:
This slide introduces the concept of the Java sandbox and what it can do. Initially, in Java
1.0, it was not possible to have something that ran within the sandbox access anything on
the local system. This restriction was designed to protect the local system from the code
that ran on it (this protection is different from application security, which protects the
running code from clients who might attempt to use it). With Java 1.1, it was possible to
sign code and therefore trust it. This feature allowed the administrator to have code that
was running access certain parts of the local system.
V8.1
Student Notebook
Uempty
Java security model

• Java 1.0 (sandbox model): • Java 1.1 (signed code):
– Downloaded code (untrusted) runs in – Extends 1.0 sandbox model.
a sandbox (restricted environment) Introduces signed code. Digitally
– Application code (local Java classes) signed remote code is treated like
has full access to resources (trusted local code if the public key used to
and no protection) verify that the signature is trusted
Local code Remote code Local code Remote code
Trusted signed
code
JVM full access to Sandbox restricted JVM full access to Sandbox restricted
resources access resources access
Security manager Security manager
System resources (such as files and System resources (such as files and
network connections) network connections)
Figure 18-51. Java security model WA855 / VA8551.0
Notes:
Orthogonal to Java EE role-based security, Java 2 security is about protecting system
resources. It is policy-based (several .policy files control it) and provides fine-grained
access control to system resources, such as:
• File I/O
• Sockets
• Properties
To find Java 2 access exceptions, look for the string
java.security.AccessControlExceptions in the SystemOut.log or SystemError.log
file.

Student Notebook
Java security overview JVM
• Protects the system from the Protection domain

applications
• Provides an access control Java Security manager System
class Access controller resource
mechanism to manage the
application access to system Java security
level resources permissions
– File I/O, network connections
(sockets), property files
– Policy-based
Java 2
• Policies define a set of permissions policy
available from various signers and files
code locations
• Java code needs access to certain
– Stored in policy files
system resources
• All Java code runs under a security • Java code must get the permission
policy from Java 2 access control
– Grants access to certain resources • Access control looks at the Java 2
policy files to determine whether the
• Can be turned on or off independently
requesting Java code has the
of administrative security appropriate permission
Figure 18-52. Java security overview WA855 / VA8551.0
Notes:
When Java 2 security is enabled in WebSphere, the security manager component by
default throws a java.security.AccessControl exception when a permission violation
occurs. This exception, if not handled, often causes a runtime failure. This exception is also
logged in the SystemOut.log file.
However, when the JVM com.ibm.websphere.java2secman.norethrow property is set
and has a value of true, the security manager does not throw the AccessControl exception:
it is only logged.
Note: This property is intended for a sandbox or debug environment only since it instructs
the security manager not to throw the AccessControl exception. By not rethrowing the
exception, Java 2 security is not truly enforced. Do not use this property in a production
environment where a relaxed Java 2 security environment weakens the very integrity Java
2 security is intended to produce.
The JVM parameter entered on the command line starts the server, usually in the script
startServer. Enter as: –Dcom.ibm.websphere.java2secman.norethrow=true
V8.1
Student Notebook
Uempty Look in the log for the next line to verify that the previous is in place:
SecurityManag W SECJ0381I: Warning, the
com.ibm.websphere.java2secman.norethrow property is true. The WebSphere Java
2 Security Manager is not rethrowing AccessControl exceptions. Do not use
this debug setting in a production environment. See the information center
for Java 2 Security debugging features.

Student Notebook
Enabling Java 2 security

• Can be enabled and disabled independently of administrative and application security
• Java 2 security provides a policy-based, fine-grain access control mechanism that
increases overall system integrity.
• Java 2 security checks for permissions before allowing access to certain protected
system resources
Figure 18-53. Enabling Java 2 security WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 18.7.SSL basics

Student Notebook
SSL basics

Figure 18-54. SSL basics WA855 / VA8551.0
Notes:
SSL (Secure Sockets Layer) provides transport level security between two points, much
like a VPN. It is often used to secure communications between a browser and a web
server.
V8.1
Student Notebook
Uempty
What is SSL?
• SSL stands for Secure Sockets Layer
• SSL provides connection security through:
– Communication privacy: the data on the connection can be encrypted
– Communication integrity: the protocol includes a built-in integrity check
– Authentication: the client knows who the server is
• Creates a VPN
– Uses both symmetric and asymmetric key encryption
Client browser Web server
HTTP
SSL
Figure 18-55. What is SSL? WA855 / VA8551.0
Notes:
Symmetric key encryption allows two parties to send each other secured messages, but
requires a shared secret. Although this approach has low complexity, the problem with this
approach is that at some point they must share that secret. In an e-business application, it
would be rather difficult.

Student Notebook
Symmetric key encryption

• Symmetric or secret key technology is a model in which two parties
have a shared secret
• The same key is used for both encryption and decryption
Plain Encrypted
unencrypted (cipher text)
(clear text)
Figure 18-56. Symmetric key encryption WA855 / VA8551.0
Notes:
If a server has a public-private set, it can send out its public key (through a signing
certificate; also known as a certificate) to client machines. Those client machines can then
use that public key to encrypt messages that are destined for the server, which then only
the server can decrypt. Unlike symmetric key encryption, this process does not require the
client and server to have a shared secret.
Since the client can validate the certificate of the server, there is one-way authentication.
But the server has no way to authenticate the client. Nor can the server send the client
secured messages.
V8.1
Student Notebook
Uempty
Asymmetric key encryption

Public key cryptography
• Two keys that are cryptographically related:
– Public key (can share with everyone)
Public
– Private key (must never be shared;
possession is proof)
Private
• Keys are asymmetric:
– Given message is encrypted with one
key and decrypted with another
– Symmetric, secret key technology uses
the same key for encryption and decryption
Public Private
unencrypted encrypted unencrypted
Figure 18-57. Asymmetric key encryption WA855 / VA8551.0
Notes:
Because the client chooses its own session key, nobody else knows it. It can securely use
the public key of the server to send that session key to the server. Now, nobody but the
client and server know the session key. The session key is then used as a “shared secret”
to switch to the much more efficient symmetric key encryption.
A certificate (or signing certificate) contains information about the server, including the
public key of the server, and the certificate authority digitally signs it.

Student Notebook
How does SSL work?

SSL uses a combination of asymmetric and symmetric encryption to
create a session between the client and server
• Asymmetric encryption is used to negotiate a session key (shared secret)
– Asymmetric encryption is slow but does not require a shared secret
• Symmetric encryption is used to transfer data between the client and server
– Symmetric encryption is fast but requires a shared secret
Client Server
1. Client requests SSL connection
2. Server presents certificate
4. Client generates a session key, encrypts

3. Client it with the public key for the server
verifies
server
certificate
5. Using the session key, client and server
switch to symmetric key encryption
6. HTTPS communications
Figure 18-58. How does SSL work? WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 18.8.Certificates and certificate authorities

Student Notebook
Certificates and certificate

authorities

Figure 18-59. Certificates and certificate authorities WA855 / VA8551.0
Notes:
A digital certificate is an electronic document that identifies you, which a certificate
authority then signs. This certificate means that the CA validates that you are who you say
you are and is therefore vouching for you.
The certificate contains not just information about you, but also your public key. It is
important to note that the public key is the counterpart to your private key (which is part of
your personal certificate) which is kept secret.
V8.1
Student Notebook
Uempty
What is a certificate?
Simple answer:
• It is an electronic document that identifies
you, and a third-party vouches for both you
and the certificate itself CA
• Examples:
– Employee badge (vouched for by your employer)
– Drivers license (vouched for by your state)
– Passport (vouched for by your country)
More information:
• Includes information about you
• Includes public key
• A certificate authority digitally signs it
Figure 18-60. What is a certificate? WA855 / VA8551.0
Notes:
The term “certificate” is sometimes confused since it is used in different ways. Generally
speaking, a certificate contains just a public key and information about you.
A personal certificate is a certificate that contains the private key, which must be kept
private and secret.
A signer certificate is just a regular certificate. In other words, it contains a public key and
information about the owner. What specifically makes it a “signer certificate” is the fact that
the corresponding personal certificate (private key) was used to sign a certificate. This
case occurs for a CA or a chained certificate when some entity (usually a CA, or in the case
of WebSphere, a cell root certificate) signs your certificate. You therefore need that signer
certificate (which contains the signer’s public key) to validate SSL connections.

Student Notebook
Types of certificates
There are different types of certificates:
• Certificate
– Contains a public key that is signed
– Contains information about the owner of the certificate
– Contains certificate expiration date
• Personal certificate:
– Typically meant as the certificate along with private key data
• Signer certificate:
– The certificate that corresponds to the private key used to digitally sign another
certificate
Figure 18-61. Types of certificates WA855 / VA8551.0
Notes:
If a client is going to trust a certificate from a server, the client must be able to validate that
certificate. This validation is possible because a certificate authority generates and signs
certificates with its private key. That means that the browser can use the public key of the
CA to verify the digital signature. The public keys from the standard CAs are built into
browsers. If the browser does not have a copy of the public key of the CA, the user is
prompted.
Public key infrastructure (PKI) is:
• Based on public-private key cryptography
• The whole infrastructure that makes public-key security work:
- Certificate authority (CA)
- Registration authority (RA)
- PKI enabled applications
- Directory (optional)
V8.1
Student Notebook
Uempty
What is a certificate authority (CA)?

• An entity that signs public keys, thus creating certificates
– A CA validates Kate’s identity before vouching for her (signing her certificate)
– A special type of signer (a trusted signer)
• Well known CAs have
Certificate
their signers built authority
into browsers
Everyone trusts the CA
(third-party trust) CA
Kate’s
Browser web server
Verifies Kate’s identity
Key ring and signs her certificate
(with the CA private key)
Kate’s
certificate CA
Figure 18-62. What is a certificate authority (CA)? WA855 / VA8551.0
Notes:
Putting it together, Joe’s browser is willing to trust Kate’s server because Kate presented
her certificate to Joe. The question then becomes how does Joe trust that the certificate
really belongs to Kate? The answer is because the CA signed Kate’s certificate, which
means the CA verified that Kate was really Kate. Since Joe trusts the CA, he is therefore
willing to trust Kate.

Student Notebook
SSL: Putting it all together

The SSL handshake establishes:
• The identity of the server (based on trusting the CA)
– The server provides a CA signed certificate
– The server proves that it has the corresponding private key
– Therefore, Joe trusts that Kate really is Kate
• Encrypted (with symmetric key) channel between the browser and
server
Kate’s web server
Joe’s browser
HTTPS (HTTP over SSL)
…Joe trusts Kate

Joe te Key ring
t ru s
ts C t s Ka
s
A A tr u
C
CA
Certificate authority © Copyright IBM Corporation 2013
Figure 18-63. SSL: Putting it all together WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 18.9.SSL within a WebSphere cell

Student Notebook
SSL within a WebSphere

cell

Figure 18-64. SSL within a WebSphere cell WA855 / VA8551.0
Notes:
When thinking about SSL within a WebSphere cell, a number of different relationships must
be taken into account. For example, consider the connection between the browser and the
web server. That relationship is understood, and independent from the relationship
between the plug-in and the application server. There are also the SSL connections within
the actual cell (between the managed processes: deployment manager, node agents,
application servers). Additionally, there might be SSL connections to an LDAP server, web
services, external cell, and others.
V8.1
Student Notebook
Uempty
SSL within WebSphere Application Server

• SSL can be used to secure network traffic for a number of links
– From the client to the web server
– From the plug-in to the application server
– Other network links can also be secured (LDAP and others)
• The administrative console (or iKeyman) can be used to create and
manage the necessary keys and keystores
– Keystores contain digital certificates that are needed for SSL to establish
secure communication between two points
1. Client to HTTPd 2. Plug-in to application server

Web server
Client browser
WebSphere
Plug- Application
SSL in SSL
Server
Figure 18-65. SSL within WebSphere Application Server WA855 / VA8551.0
Notes:
Each node within a cell gets a node personal certificate (1-year life span). The cell root
certificate signs the node personal certificates (15-year life span). By default, all of the
application servers on a node use the node certificates of that node. The node certificates
are stored in node-specific keystores, and the cell root signer certificate is stored in the cell
truststore. This storage method means that all nodes, through file synchronization, have
access to the cell root signer.
This arrangement has several desirable side effects. First, all of the nodes can securely
communicate with each other after validating themselves. Second, when a personal
certificate is replaced (for example, when it expires), the other nodes still accept the new
certificate. It is accepted because a known signer signed it (a new signer is not required to
be distributed again, as it does when the certificate is self-signed).

Student Notebook
WebSphere SSL management

• WebSphere automatically creates
node certificates
Cell-wide
– The cell root certificate (called Deployment truststore
a “chained certificate”) signs manager
the node certificates
– Node certificates are stored in
a node-specific keystore
• Cell-wide truststore includes cell
root signer certificate
Node Node
– Each node can therefore agent agent
validate certificates that other
nodes present
• An expiration manager Application
… Application
serverApplication serverApplication
automatically renews expiring server server
keys (default behavior)
Node Node
• The keystores and truststores are
stored within the cell configuration
Cell
and therefore distributed to the
nodes through file synchronization
Figure 18-66. WebSphere SSL management WA855 / VA8551.0
Notes:
The plug-in uses a single keystore (or key ring) which is generated for it by WebSphere.
This file contains both the personal certificate for the plug-in and the cell root signer.
The application servers (or nodes) use two different files. A keystore contains the node
personal certificate, and the truststore holds the signer certificates that the node chooses to
trust. By default, that means just the cell root signer certificate.
V8.1
Student Notebook
Uempty
What are key rings, keystores, and truststores?

Web server
Client browser
WebSphere
Plug- Application
SSL in SSL
Server
Key rings, keystores, and

truststores are all Node
encrypted files that keystore
contain certificates
Plug-in Keystores hold node

key ring
personal certificates
Plug-in key rings hold both the

Cell
personal and signer certificates
truststore
Truststores hold the cell

root signer certificate
Figure 18-67. What are key rings, keystores, and truststores? WA855 / VA8551.0
Notes:
A keystore contains the node personal certificate (which the cell root certificate signs) and
the truststore holds the signer certificates that the node chooses to trust. By default, that
means just the cell root signer certificate.
It is stored in .p12 files within the config directory of the profile:
<profile-root>/config/<cell-name>/nodes/<node-name>/key.p12
<profile-root>/config/<cell-name>/trust.p12

Student Notebook
Node certificates
• Each node has a node certificate
– The cell root certificate (a chained certificate) signs the node certificate
– The cell root signer is therefore needed to validate the node certificate
– The application servers, by default, all use the local node certificate
Node-A The cell root

Keystore certificate signs the
node certificate
AppServer-1 Node-cert
CR Cell root certificate
Truststore
AppServer-2
CR-signer Cell root signer
Figure 18-68. Node certificates WA855 / VA8551.0
Notes:
The cell default truststore contains the cell root signer certificate. To be able to validate
potential SSL connections, each node needs the cell root signer. This file is made available
to each of the nodes through standard file synchronization.
V8.1
Student Notebook
Uempty
Cell default truststore

• The cell default truststore contains signers, include the cell root signer
– It is synchronized to all the members of the cell
– All the nodes use the common cell default truststore
– Although there are node truststore files, they are not used by default
Dmgr
Cell default
Cell truststore
server1 server37
PlantsServer CR-signer
Cell root signer
Figure 18-69. Cell default truststore WA855 / VA8551.0
Notes:
This screen shows the initial administrative console page for viewing and managing the
SSL settings and configurations.

Student Notebook
Managing WebSphere keystores

• Keystores and certificates for
the cell, nodes, and plug-ins
can be managed directly from
the console
• Expiration management
• Keystores
• Trust files
• Certificates
Figure 18-70. Managing WebSphere keystores WA855 / VA8551.0
Notes:
This screen shows the administrative console view of a node certificate. It shows the initial
information about not just the node certificate, but also the signer certificate (which in this
case would be the cell root signer). If the link for the certificate is clicked, more details are
displayed.
V8.1
Student Notebook
Uempty
Creating keystores and certificates
• Keystores for WebSphere are managed

through the administrative console
–Creating keystores
–Requests and imports CA certificates
–iKeyman can also be used
Figure 18-71. Creating keystores and certificates WA855 / VA8551.0
Notes:
A chained certificate means that the cell root signer signs the node certificate. It is
demonstrated in this screen capture by noting that the “Issued By” information for the node
certificate matches the “Issued To” information for the signer. It is also worth noting that the
“Issued To” and “Issued By” fields of the signer match each other, which indicates that the
signing certificate is actually a self-signed certificate.
Some refer to the cell root signing certificate as a mini-CA since it signs all of the node
certificates within a cell. Logically, it is what a CA does on a larger level.

Student Notebook
What is a chained certificate?

• A chained certificate is merely a certificate that another certificate signs
• The cell root certificate (sometimes called a mini-CA) signs the node
certificate
Chained certificate
• The cell root
certificate signs it
Node
certificate
Cell root
certificate
Notice: these two are the same
Figure 18-72. What is a chained certificate? WA855 / VA8551.0
Notes:
WebSphere is able to automatically manage the expiration of its certificates. By default, the
expiration management thread runs every four weeks (on Sundays at 21:30). If the
certificates are close to expiring, they are renewed. Notification thresholds allow the
administrator to also receive warnings before certificates are renewed.
V8.1
Student Notebook
Uempty
Expiration manager scheduling

Manual start • The expiration manager can be
run manually or through a
schedule
• Running manually can be

useful since you actively
monitor the log file and thus
generate a list of certificates
Schedule that are going to expire soon
Figure 18-73. Expiration manager scheduling WA855 / VA8551.0
Notes:
Since the plug-in keystores include the cell root signer, the plug-in is able to complete an
SSL handshake with any of the nodes since the cell root certificate signed all of their
certificates.

Student Notebook
Keys for web servers

Web server Web server
Plug- Plug- Cell-wide

in in Deployment
truststore
manager
• Single keystores are generated

for each unmanaged web
server node:
– Contains signed personal
certificate for the unmanaged Node Node
agent agent
node (which the cell root
certificate signs)
– Includes the cell root signer Application
… Application
certificate, allowing the serverApplication serverApplication
plug-ins to communicate with server server
the nodes securely Node Node
• Important: These key rings
must be distributed to the web Cell
servers © Copyright IBM Corporation 2013
Figure 18-74. Keys for web servers WA855 / VA8551.0
Notes:
Propagation of the plug-in keystores is typically done manually since file synchronization is
not available.
V8.1
Student Notebook
Uempty
Web server plug-in keystores propagation
Web server
• The plug-in key rings must be propagated to the web
server machines
– Similar to copying the plugin-cfg.xml file to web servers
Plug-
in – WebSphere automatically generates the plug-in key rings
Web server
Dmgr
Plug- Cell
in
server1 server37
PlantsServer
Web server
Plug-
in
Figure 18-75. Web server plug-in keystores propagation WA855 / VA8551.0
Notes:
WebSphere automatically generates keystores for defined web server plug-ins. These
keystores then must be copied to the plug-ins. These keystores can be managed through
the administrative console. With IBM HTTP Server, it is also possible to configure
WebSphere to propagate the keystore that WebSphere generates to the web server
plug-in.

Student Notebook
IBM HTTP Server key ring propagation
• Web server
keystores are
automatically
generated
– Can be managed
from the
administrative
console
• The keystore for

IBM HTTP Server
servers can be
remotely
propagated
Figure 18-76. IBM HTTP Server key ring propagation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty 18.10.Security auditing

Student Notebook
Security auditing

Figure 18-77. Security auditing WA855 / VA8551.0
Notes:
Security auditing is a new feature in WebSphere Version 7. Auditing can log various
information, including:
• Authentication
• Authorization
• Principal-credential mapping
• Audit policy management
• User registry and identity management
• Delegation
• Administrative configuration management
V8.1
Student Notebook
Uempty
Security auditing
• The security auditing subsystem was introduced in WebSphere
Application Server Version 7 and has two primary goals:
– Confirm the effectiveness and integrity of the existing security configuration
– Identify areas where improvement to the security configuration might be needed
• The security auditing subsystem can capture the following types of

auditable events:
– Authentication
– Authorization
– Principal and credential mapping
– Audit policy management
– User registry and identity management
– Delegation
– Administrative configuration management
Figure 18-78. Security auditing WA855 / VA8551.0
Notes:
Enabling security auditing requires some configuration settings. This diagram shows
security auditing as it is enabled.

Student Notebook
Enabling security auditing

• Configuration is necessary before auditing can be enabled
– Create an
audit-specific
set of console
users or groups
and map to
Auditor role
– Define
notification
mechanism
(log file, email)
– Enable
monitoring
• Enabling auditing
Figure 18-79. Enabling security auditing WA855 / VA8551.0
Notes:
With security auditing enabled, it is possible to view the security logs as either text files or
as HTML reports (generated through wsadmin).
V8.1
Student Notebook
Uempty
Viewing audit data

• Audit data can be
viewed as:
– Text
– An HTML report
(through wsadmin)
Figure 18-80. Viewing audit data WA855 / VA8551.0
Notes:

Student Notebook
Securing audit records

• Access to audit configurations is restricted
– To change audit settings, Auditor access is required (Administrator access is not
sufficient)
• Audit data can be digitally protected
– Can be digitally signed
– Can be encrypted with a
separate audit certificate
Figure 18-81. Securing audit records WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Unit summary
• Describe support for Java Platform, Enterprise Edition 6 (Java EE 6)
security annotations
Notes:

Student Notebook
1. Which type of security restricts access to the application?
A. Administrative security
B. Application security
C. Java 2 security
D. File system security
2. Which type of security restricts access to the operating system?
C. Java 2 security
3. Which type of security restricts access to the console?
C. Java 2 security
Notes:
1. 
2. 
3.
V8.1
Student Notebook
Uempty
Checkpoint answers
1. Which type of security restricts access to the application?
2. Which type of security restricts access to the operating system?

C. Java 2 security
3. Which type of security restricts access to the console?

Notes:

Student Notebook
Exercise 12
Configuring WebSphere security

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Enable WebSphere security
• Configure administrative security by configuring access to
administrative functions
Notes:

Student Notebook
Exercise 13
Configuring application security

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Define Java EE security roles
• Define access for resources in an application
• Enable and verify application security
Notes:

Student Notebook
Exercise 14
Configuring SSL for WebSphere

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Define the certificate life span of a profile
• Use the administrative console to find and view certificates within the
cell
• Configure and run the certificate expiration service
• Propagate the generated plug-in keystore out to the plug-in
• Create a keystore for a web server
• Generate a self-signed key
• Configure IBM HTTP Server to load and use HTTPS
Notes:

Student Notebook
V8.1
Student Notebook
Uempty Unit 19. Overview of the Liberty profile

This unit introduces the new Liberty profile and covers the installation
of the runtime environment. It explains how Liberty profile servers are
created by using developer tools and command-line utilities. It also
covers various methods for deploying applications to the Liberty profile
servers. Other topics include flexible configuration, application
security, packaging Liberty profile resources, and managing multiple
servers by using the job manager.

• Describe the characteristics and architecture of the Liberty profile
• Install the Liberty profile runtime environment
• Create a Liberty profile server by using developer tools and
command-line utilities
• Describe the configuration features for a Liberty profile server
• Use flexible configuration and shared libraries
• Deploy applications by using a monitored directory
• Deploy applications by using developer tools
• Package an application and Liberty profile runtime
• Describe the process for enabling security for a Liberty profile
server
• Use the job manager to manage Liberty profile servers
• Describe the characteristics of a Liberty collective
• Describe the characteristics of Liberty profile server clusters

• Lab exercises
© Copyright IBM Corp. 2013 Unit 19. Overview of the Liberty profile 19-1
Student Notebook
References
IBM Redbooks: WebSphere Application Server V8.5 Concepts,
Planning, and Design Guide, SG24-8022-00, Chapter
4, “An overview of the Liberty profile”
V8.1
Student Notebook
Uempty
Unit objectives
• Create a Liberty profile server by using developer tools and command-
line utilities
• Describe the process for enabling security for a Liberty profile server
Notes:
Student Notebook
Topics
• Introduction to the Liberty profile
• Tools, run time, and installation
• Configurations
• Security
• Using the job manager
• Liberty collectives and clusters
Notes:
V8.1
Student Notebook
Uempty 19.1.Introduction to the Liberty profile
Student Notebook
Introduction to the Liberty

profile

Figure 19-3. Introduction to the Liberty profile WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
What is the Liberty profile?

• The Liberty profile is an application server runtime environment
– Highly composable by using feature elements
– Configuration changes are dynamic on a running server
– Server starts quickly
• You can install a Liberty profile runtime environment by extracting a
JAR file
– The Liberty profile does not include a Java runtime environment (JRE), so you
must install an IBM or Oracle JRE separately
• Liberty profile servers support two models of application deployment:
– Deploy an application by dropping it into the dropins directory
– Deploy an application by adding it to the server configuration
• The Liberty profile supports a subset of the full WebSphere Application
Server programming model:
– Web applications
– OSGi (Open Service Gateway initiative) applications
– Java Persistence API (JPA)
• Can be easily configured to support the full Java EE 6 Web Profile
Figure 19-4. What is the Liberty profile? WA855 / VA8551.0
Notes:
The Liberty profile provides an application server runtime environment that is highly
composable, fast to start, and dynamic.
The Liberty profile does not include a Java Runtime Environment (JRE), so you must install
an IBM or Oracle JRE or SDK to support the runtime environment.
A Liberty profile server supports two models of application deployment. You can use the
monitored directory function and deploy an application by dropping the application archive
into the “drop-ins” directory.
You can also deploy an application by storing the application archive in a shareable apps
directory and adding location information for it to the server configuration file.
The Liberty profile supports a subset of the following parts of the full WebSphere
Application Server programming model: web applications, OSGi applications, and the Java
Persistence API (JPA).
Student Notebook
What does the Liberty profile provide?

• The Liberty profile provides a lightweight development and application-
serving environment that is optimized for developer and operational
productivity
• The Liberty profile includes the following key features:
– Dynamic and flexible runtime (loads only what the application needs)
– Quick server start time (under 5 seconds with simple web applications)
– Simplified configuration that uses a single configuration file or modular
configuration
– Support for deploying applications that are developed in the Liberty profile to run
in the full profile
– Support for LDAP user registries
– Ability to deploy an application and configured server as a package
– Managed, centralized deployment to multiple nodes of a packaged application
and server by using the job manager
– Availability of WebSphere Application Server Developer Tools as Eclipse plug-
ins for broad tool support
– Support for z/OS platform native features like System Authorization Facility
(SAF), Resource Recovery Service (RRS), and z/OS workload management
(WLM)
Figure 19-5. What does the Liberty profile provide? WA855 / VA8551.0
Notes:
The Liberty profile provides a lightweight application server, which is focused on the
development and operations experience. When used as a test server, it can have a small
footprint that results in the fastest possible server start.
By dynamically updating a single XML file, server configuration is simplified and achieved.
Configuration data is shareable by “including” common configuration elements. The Liberty
profile is compatible with full-profile WebSphere Application Server editions.
The Liberty profile runtime is free for developers and does not expire. The runtime
environment is focused on web applications and OSGi applications that include Java
persistence, transactions, and security.
V8.1
Student Notebook
Uempty
Liberty profile architecture
Figure 19-6. Liberty profile architecture WA855 / VA8551.0
Notes:
As shown in the graphic, the Liberty profile is built on OSGi technologies. The server
process runs as OSGi bundles and comprises a single Java virtual machine (JVM), the
Liberty profile kernel, and any number of optional features.
A functional server is produced by starting the runtime environment with a configuration
that includes a list of features to use. Features are the units of capability, by which the
runtime environment is defined and controlled. They are the primary mechanism that
makes the server composable. For example, if the servlet feature is specified, the runtime
environment operates as a servlet engine. By default, a server runs no features. You can
use the feature manager to add the features that are needed. The feature manager is one
of the kernel bundles that receive the configuration, resolve each feature to a list of
bundles, install the feature into the framework, and then start the feature. When the
features that are needed are specified, the default configuration of those features provides
a rich environment that is designed to cover most common requirements.
The configuration manager reads the server configuration from persistent files, parses the
configuration into sets of properties, and then uses those sets of properties to populate the
Student Notebook
OSGi Configuration Admin service. This service maintains the runtime view of the
configuration, and when configuration updates are made, this service injects each set of
properties into the service that “owns” them.
V8.1
Student Notebook
Uempty
Clarification: Profile versus profile

• How does the Liberty profile relate to the application server and custom
profiles?
• The term “profile” has another meaning in WebSphere V8.5
– Installation profile (full or traditional profile versus Liberty profile): Refers to
what runtime is being installed
– Configuration profile (deployment manager, application server, custom):
Refers to which configuration is being used within the full installation
Installation
profiles Configuration
profiles
Figure 19-7. Clarification: Profile versus profile WA855 / VA8551.0
Notes:
How does the Liberty profile relate to the Application Server and Custom profiles?
The term “profile” is overloaded with an extra meaning in WebSphere V8.5.
The Liberty profile is a type of installation profile. An installation profile refers to which
runtime (or product binary files) is being installed, the WebSphere Application Server Full
Profile or the WebSphere Application Server Liberty Profile.
Traditional profiles such as Deployment Manager, Application Server, and Custom are
types of configuration profiles and relate to which configuration is being used within the full
product installation.
Student Notebook
WebSphere Application Server family

WebSphere WebSphere WebSphere WebSphere
Application Application Server Application Server Application Server
Server for Hypervisor Edition Network Deployment for z/OS
Developers
Liberty Liberty Liberty

profile profile profile
Liberty
profile
WebSphere
Application Server Liberty
profile
WebSphere A lightweight and low- WebSphere

cost Liberty-profile-based Application
Application
offering, providing
Server Server Liberty
capabilities to rapidly
Liberty Core Express profile
build and deliver web
apps that do not require
the full Java EE stack
Figure 19-8. WebSphere Application Server family WA855 / VA8551.0
Notes:
The WebSphere Application Server family for Version 8.5.5 continues to provide offerings
to fit your needs, which might range from lightweight developer desktop environments to
highly complex and highly available enterprise environments. As more qualities of service
are required in your environment, the WebSphere Application Server family of offerings
continues to meet those requirements on a common code base.
This chart shows each of the different versions of WebSphere Application Server and how
they relate to one another regarding customer needs and capabilities.
WebSphere Application Server Express features reduced acquisition cost and enables fast
deployment of a single application server. The difference between this package and the
WebSphere Application Server “Base” edition is the license. Both editions are virtually the
same, but “Base” includes a license for unlimited processors. Express is limited to two
processors. Both Express and Base editions can support a stand-alone deployment.
WebSphere Application Network Deployment includes all the capabilities of the Base
edition, but also supports high transaction volume, scalability, clustering, high availability,
and failover.
V8.1
Student Notebook
Uempty WebSphere Application Server for z/OS includes all the features of Network Deployment
for the z/OS platform.
WebSphere Application Server for Developers is a no-charge WebSphere Application
Server development runtime for projects that do not warrant the expense of a priced and
supported runtime on the developer desktop. The development time runtime environment
allows developers to test their applications on their desktop before moving the application
into a production runtime environment.
New in version 8.5.5 is WebSphere Application Server Liberty Core. Liberty Core is a highly
composable, fast to start, and ultra lightweight profile of the application server that is
optimized for developer productivity and web application deployment.
Student Notebook
Features available in the Liberty editions

Liberty Core Base, Express Network z/OS
Deployment
servlet jsp jsf jpa was.JmsClient collectiveController zosSecurity
jndi jdbc json jaxrs was.JmsServer clusterMember zosTransaction
wab ssl osgi.jpa wsSecurity zosWlm
monitor wmq.JmsClient
sessionDatabase was.JmsSecurity
appSecurity mongodb
blueprint jaxb
restConnector jaxws
localConnector
beanValidation
ejblite cdi
managedBeans
oauth ldapRegistry
webCache
concurrent
collectiveMember
Figure 19-9. Features available in the Liberty editions WA855 / VA8551.0
Notes:
Different features are available in the different Liberty editions.
V8.1
Student Notebook
Uempty 19.2.Tools, runtime, and installation
Student Notebook
Tools, runtime, and

installation

Figure 19-10. Tools, runtime, and installation WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Liberty profile developer tools

• Applications can be developed and tested on a Liberty profile server by
using the following developer tools
– WebSphere Application Server Developer Tools for Eclipse
– IBM Assembly and Deploy Tools for WebSphere Administration
Figure 19-11. Liberty profile developer tools WA855 / VA8551.0
Notes:
Each developer tool that is listed on this slide is Eclipse-based and supports the Liberty
profile runtime environment. You can install the runtime and create Liberty profile servers.
The developer tools provide editors that allow you to configure servers with any features
required by the application.
Student Notebook
Where to get WebSphere Application Server Developer Tools for

Eclipse
• WebSphere Application Server Developer Tools for Eclipse is available
for free:
– From http://www.wasdev.net
– Through the Eclipse Marketplace (Help > Eclipse Marketplace)
– Through the IBM Installation Manager
Figure 19-12. Where to get WebSphere Application Server Developer Tools for Eclipse WA855 / VA8551.0
Notes:
The WebSphere Application Server Developer Tools for Eclipse is a free download from the
WASdev community website of the web address that is shown on this slide.
WebSphere Developer Tools is also available from the Eclipse Marketplace, which can be
accessed in Eclipse by clicking Help > Eclipse Marketplace.
WebSphere Developer Tools can also be installed by using the IBM Installation Manager
and accessing the appropriate installation repository.
V8.1
Student Notebook
Uempty
Where to get the Liberty profile runtime environment

• The runtime is available through:
– IBM Installation Manager (as part of WebSphere V8.5)
– Developer tools when creating a server
– Download from http://www.wasdev.net
Figure 19-13. Where to get the Liberty profile runtime environment WA855 / VA8551.0
Notes:
The Liberty profile runtime is available through IBM Installation Manager as part of
WebSphere Application Server V8.5.
The Liberty profile runtime is also available through WebSphere Developer Tools when
creating a server, and as a free download from the WASdev community website.
Student Notebook
Installing the Liberty profile

• Installing the Liberty profile runtime environment
– Use developer tools such as WebSphere Application Server Developer Tools,
IBM Assembly and DeployTools, or Rational Application Developer
– Use the IBM Installation Manager
– Extract from a compressed archive (java –jar wlp-8500.jar)
Figure 19-14. Installing the Liberty profile WA855 / VA8551.0
Notes:
The Liberty profile runtime environment can be installed by using different tools that include
WebSphere Application Server Developer Tools, IBM Installation Manager, and by
downloading a Liberty profile archive and extracting from the command line.
V8.1
Student Notebook
Uempty
Creating a Liberty profile server

• Creating a server can be done quickly
– Using the command line
– Using developer tools (WebSphere Application Server Developer Tools, IBM
Assembly and DeployTools, Rational Application Developer)
• From the command line:
Figure 19-15. Creating a Liberty profile server WA855 / VA8551.0
Notes:
The server create command is used to create a Liberty profile server from the command
line. After installing the Liberty profile runtime, there is a bin directory from which you can
run a command such as:
Server create <server_name>
Student Notebook
Creating a server with developer tools (1 of 3)

• Select the type of server
Figure 19-16. Creating a server with developer tools (1 of 3) WA855 / VA8551.0
Notes:
Each of the developer tools provides wizards for creating an instance of a Liberty profile
server. The first step is to select the server type: WebSphere Application Server V8.5
Liberty Profile. In this step, you can also specify a host name and new server name, or
accept the defaults.
V8.1
Student Notebook
Uempty

• Specify a server name and click Finish
Notes:
This step allows you to add another server name if you want to change the default name.
Student Notebook

• Server1 is created and is now listed in the Servers view
• Expand the server entry and you see the Server Configuration
• Configuration for a new server consists of:
– The jsp- 2.2 feature
– The HTTP Endpoint definition (9080 and 9443 are default ports for all new
servers)
Notes:
The Liberty profile server instance is created with a minimal configuration that includes the
jsp-2.2 feature and the default HTTP endpoint settings.
The Servers view has icons that can be clicked to start or stop a server. In addition,
right-clicking the server name brings up a menu with several useful items, such as a
Restart button and a Utilities link.
The Utilities link allows you to select the following actions:
• Create an SSL certificate
• Generate a web server plug-in
• Package server
• Generate a dump for support
V8.1
Student Notebook
Uempty 19.3.Configurations
Student Notebook
Configurations

Figure 19-19. Configurations WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Simplified server configuration

• No need for administrative console, wsadmin, or enhanced EARs
– These tools are not supported
• Configuration in XML files
– Simplest case: one XML file (server.xml) for all server configuration
– Editable within the developer tool or by using a text editor
– Exportable, shareable, and versionable
Liberty server resources.xml

configuration
server.xml
...
Traditional WebSphere
Application Server
Figure 19-20. Simplified server configuration WA855 / VA8551.0
Notes:
There is no administrative console or wsadmin scripting interface for configuring a Liberty
profile server. All of the configuration for a server can be contained in a single XML file
called server.xml. This file can be manually updated with a text editor and when the
changes are saved, the server is dynamically updated. No server restart is required. Other
XML configuration files can be accessed by using an include statement in the server.xml
file.
Note: Other files can be used to configure the Liberty profile server. These files include the
bootstrap.properties file, the jvm.options file, and the server.env file.
Student Notebook
Simplified configuration: server.xml

<server>
<server>
<featureManager>
<featureManager> Features control which
<feature>jsp- capabilities (OSGi bundles)
<feature>jsp- 2.2</feature>
2.2</feature>
are installed in the server
<feature>jdbc-4.0</feature>
<feature>jdbc-4.0</feature>
</featureManager>
</featureManager> Singleton configurations
specify properties for a
runtime service like logging
<logging
<logging traceSpecification=
traceSpecification=
"webcontainer=all=enabled:*=info=enabled"
"webcontainer=all=enabled:*=info=enabled" />
/>
<application
<application name="tradelite"
name="tradelite" location="tradelite.war"
location="tradelite.war" />
/>
Instance
<dataSource
<dataSource jndiName="jdbc/TradeDataSource">
jndiName="jdbc/TradeDataSource"> configurations specify
<properties.derby.embedded multiple resources like
<properties.derby.embedded
applications and data
databaseName="${server.config.dir}/tradedb"/>
databaseName="${server.config.dir}/tradedb"/> source definitions
</dataSource>
</dataSource>
</server>
</server> Any of this configuration could be put into a
separate XML file and included in this master
configuration file by using the include element
Figure 19-21. Simplified configuration: server.xml WA855 / VA8551.0
Notes:
This slide shows an example of a simple server.xml file for a Liberty profile server.
It consists of a feature manager section, a logging element, an application element, and a
data source element.
Liberty profile features control which capabilities (OSGi bundles) are started in the server
JVM.
Singleton configuration elements specify properties for runtime services such as logging
and tracing.
Instance configurations can specify multiple resources like applications and data source
definitions.
Any of these configuration elements can be put into a separate XML file and “included” in
the server.xml file for multiple servers. For example, multiple Liberty profile servers
might share data source definition, so that the configuration of the data source can be
stored in a single shared XML file.
V8.1
Student Notebook
Uempty
Flexible configuration
• Shareable configuration snippets
server>
...
<include location="http://cfgserver/global.xml/>" />
<include location="${shared.config.dir}/datasource.xml" />
<server>
server.xml
• Configurations can be divided into components at any level of

granularity
– From a single file to several
• Can use developer tools to associate configuration snippets with a
server configuration
• Visualization through developer tools provides a single logical view
• Team development: keep the application and configuration
components together
Figure 19-22. Flexible configuration WA855 / VA8551.0
Notes:
This slide shows an example of how to use the include statement to access shareable
configuration in a server.xml file.
A URL or environment variable can be used to point to the shareable XML configuration
files.
Components can be developed for configurations at any level of granularity, from a single
XML file to several files.
It is helpful to use WebSphere Developer Tools to associate configuration snippets with
multiple Liberty profile server configurations. The visualization features of WebSphere
Developer Tools are useful for providing a single logical view. For team development,
flexible configuration is helpful for keeping the application and configuration components
together.
Student Notebook
Shared configurations
• With shared configuration and includes, it is possible to create
powerful topologies
– Configuration files can be places in the server configuration directory or the
shared configuration directory (or can be stored anywhere)
Server 1 Server 2 Server 3
my-cfg.xml my-cfg.xml my-cfg.xml
server.xml server.xml server.xml
shared configuration
global.xml app1.xml app2.xml app3.xml
Figure 19-23. Shared configurations WA855 / VA8551.0
Notes:
With shared configuration and includes, it is possible to create powerful topologies and
more easily manage multiple server configurations.
As shown in the diagram on this slide, configuration files can be placed in the server
configuration directory, the shared configuration directory, or you can configure any shared
file system location. For example, a global.xml configuration file is shared among all
servers in an environment. But a local configuration file can be used to customize values
that must be unique on the host. For example, the HTTP port numbers must be unique on
the host, and clone IDs must be unique across the environment for workload management.
V8.1
Student Notebook
Uempty
Application deployment
• Applications are deployed by using:
– Monitored directory (dropins)
– Configuration (server.xml)
– Developer tools
Configured
Configurated
applications go
applications go here
here
(location can be
configured)
Monitored directory
(location can be
configured)
Figure 19-24. Application deployment WA855 / VA8551.0
Notes:
The screen capture on this slide shows different folders in the configuration directory of a
Liberty profile server. For application deployment, you can use either the dropins folder,
which is a monitored directory, or the apps folder, which an application configuration
element references in the server.xml file.
Student Notebook
Highly composable runtime that is based on features

Full profile server
• Full profile includes
everything Web container EJB container
Embedded HTTP
• Liberty profile includes Servlets
Server
only those features you JSPs
EJBs
add
– Improved performance Web services Messaging
– Faster server starts engine engine
Dynamic cache JMX Name server
Data replication Security Others
Liberty profile server
jpa-2.0
restConnector-1.0
jsp-2.2 appSecurity-1.0
servlet-3.0
App manager
Feature manager http transport
Figure 19-25. Highly composable runtime that is based on features WA855 / VA8551.0
Notes:
Application servers in the full profile have a JVM shown on the left that includes all services
(features) whether the applications require them or not.
A Liberty profile server JVM starts only those features that you add to its server.xml file.
By default, a server contains only the jsp-2.2 feature to support servlet and JSP
applications. You use the feature manager to add the features that you need.
The building blocks shown in the graphic on this slide show some of the Liberty profile
features that can be defined for the feature manager. These features include JPA, JSP,
servlet, application security, and a remote JMX connector. However, several other features
can be configured for a particular server. In addition to the features, you can add HTTP port
definitions for the HTTP transport, and application definitions for the application manager.
V8.1
Student Notebook
Uempty
Dynamic enablement of feature sets

Application
beanvalidation-1.0 json-1.0 jpa-2.0

blueprint-1.0 osgi-jpa-1.0
jsp-2.2 jsf-2.0 jaxrs-1.1
servlet-3.0 wab-1.0
Runtime
zosTransaction-1.0
zWlm-1.0 zosSecurity-1.0
Features are enabled
dynamically for both appSecurity-1.0
the application and localConnector-1.0 restConnector-1.0
runtime.
The application ssl-1.0
server provisions only serverStatus-1.0 monitor-1.0
the features that the
running applications sessionDatabase-1.0
require. jndi-1.0 jdbc-4.0
Figure 19-26. Dynamic enablement of feature sets WA855 / VA8551.0
Notes:
The graphics on this slide show two example feature sets for a Liberty profile server. All
features are dynamically activated when they are saved to the configuration file of the
server. No server restart is required. The application features show services that
applications require and that run on the server such as bean validation, osgi-jpa, and wab
(web application bundle). The runtime features show services that the server runtime itself
requires such as serverStatus, monitor, localConnector, restConnector, and ssl.
Description of some Liberty profile features
The beanvalidation-1.0 feature provides validations for JavaBeans at each layer of an
application. The validation can be applied to all layers of JavaBeans in an application by
using either annotations or a validation.xml deployment descriptor. The osgi.jpa-1.0
feature provides JPA support for OSGi applications on the Liberty profile.
The wab-1.0 feature provides support for web application bundles (WABs) that are inside
enterprise bundles. This feature supports the following resources that are packaged inside
a WAB: static web content and JSPs; HTTP servlets that use the servlet 3.0 specification;
blueprint applications.
Student Notebook
The serverStatus-1.0 feature enables Liberty profile servers to automatically publish their
status to WebSphere deployment managers and job managers that are aware of the server
as a resource in their Job configuration. The known states are started and stopped.
The monitor-1.0 feature provides Performance Monitoring Infrastructure (PMI) support.
The localConnector-1.0 feature provides a local JMX connector that is built into the JVM. It
enables local access by JMX clients such as jConsole, or other clients that use the Attach
API.
The restConnector-1.0 feature provides a secure JMX connector that can be used locally
or remotely by using any JDK. It enables remote access by JMX clients through a
REST-based connector and requires SSL and basic user security configuration.
V8.1
Student Notebook
Uempty
Class visibility
• Full profile server makes runtime classes visible to applications
• Liberty profile hides runtime classes from applications
• Applications can use open source APIs without the runtime interfering
• Three types of API
– spec API: APIs defined by an external standards group ( )
– ibm-api: Value add APIs provided by IBM ( )
– third-party: APIs provided by open source projects
• By default only spec and ibm-api are visible to applications
– third-party can be added by using the classloader element
Web <classloader
application
allowedApiTypes="spec">
OSGi Framework
Figure 19-27. Class visibility WA855 / VA8551.0
Notes:
The Full Profile application server exposes runtime classes to applications, but the Liberty
profile hides runtime classes from applications.
Applications can use open source classes without interference from the runtime.
Three types of API can be enabled through the classloader configuration element:
• An external standards group defines the spec API.
• The ibm-api consists of value-added APIs that IBM provides.
• The third party refers to APIs that open source projects provide.
Use the classloader configuration element and the apiTypeVisibility attribute to
specify the types of API package the classloader is able to see, as a comma-separated list
of any combination of the following APIs: spec, ibm-api, third party.
By default only spec and ibm-api are exposed to applications, but third party can be added.
Student Notebook
Shared libraries
• Associated with applications
• Move common libraries out of the WAR files
<library id="libs">
<fileset dir="${shared.resource.dir}/libs"
includes="*.jar"/>
</library>
• Share classes between applications

<application location="snoop.war">
<classloader commonLibraryRef="libs" />
</application>
• Or have an instance per application

<application location="snoop.war">
<classloader privateLibraryRef="libs" />
</application>
Figure 19-28. Shared libraries WA855 / VA8551.0
Notes:
The library configuration element can be used to specify shared libraries of classes. If your
web applications use common libraries, you can remove the classes from the WAR files
and use the fileset attribute to point to the file system location. The first snippet on this slide
shows how to use the library configuration element.
Libraries can also be associated with specific applications by using the classloader feature
in the application configuration element. The second snippet on this slide shows how to use
the commonLibraryRef attribute to share classes between applications. Library class
instances are shared with other class loaders.
The third snippet on this slide shows how to use the privateLibraryRef attribute to
isolate classes in an application. Library class instances are unique to this classloader and
independent of class instances from other class loaders.
V8.1
Student Notebook
Uempty
Packaging an application for deployment
• Package an archive of a configured Liberty server along with

its applications
– Directly from Eclipse environment
– Resulting compressed file can be copied to integration or production
environment and uncompressed
Figure 19-29. Packaging an application for deployment WA855 / VA8551.0
Notes:
A Liberty profile server configuration and its applications can be packaged into an archive
or compressed file. From the WebSphere Development Tools or IBM Assembly and Deploy
Tools, you can select the server_name > Utilities > Package Server to create a
compressed file.
Student Notebook
Liberty profile server command-line tools

• For server operations outside of the developers tools, there is a
command-line program to manage the lifecycle of server instances and
also package it for deployment:
– Create <server_name>
– Start and stop <server_name>
– Package <server_name>
– Status <server_name>
Figure 19-30. Liberty profile server command-line tools WA855 / VA8551.0
Notes:
Also, from the command line, you can use the server package <server_name>
command. A compressed file that uses the server name and a .zip extension is created.
In the example on this slide, the compressed file is named server2.zip. The compressed
file contains the Liberty profile runtime directories and the server configuration directory for
the specified server.
V8.1
Student Notebook
Uempty
Deploying an application by using the drop-ins directory

• A monitored directory can be used to deploy applications
– Copy the application file into the dropins directory
– The server installs and starts the application
copy
• Removing the file from the dropins directory automatically uninstalls the
application
Figure 19-31. Deploying an application by using the drop-ins directory WA855 / VA8551.0
Notes:
By default, the “drop-ins” directory is automatically monitored. If you drop an application
archive file into this directory, the application is automatically deployed on the server.
Similarly, if the application file is deleted from the directory, the application is automatically
removed from the server. The “drop-ins” directory can be used for applications that do not
require more configuration, such as security role mapping. You do not have to include the
application entry or any relevant information in the server configuration. For applications
that are not in the “drop-ins” directory, you use an application entry in the server
configuration to specify the location. The location can be on the file system, or at a URL.
Three types of dynamic update can be controlled through configuration: changing the
server configuration; adding and removing applications; and updating installed
applications. For all deployed applications, you can configure whether application
monitoring is enabled, and how often to check for updates to applications. For the
“drop-ins” directory, you can also configure the name and location of the directory, and
choose whether to deploy the applications that are in the directory.
Student Notebook
Creating the production image

• Runtime installation by using Installation Manager or archive
• Configurations are created manually or by using developer tools
• Package Liberty profile resources into a compressed file
• Deploy to production environment manually or by using the job
manager
WebSphere
WebSphere
Server Liberty Profile
Liberty Profile
+ Package
JDK
Deploy
JDK Application
Install through Configurations Server Install

IBM are created Liberty
Installation manually or resources
Manager or through Application
archive developer tool
image.zip
Figure 19-32. Creating the production image WA855 / VA8551.0
Notes:
To create a production image that can be deployed to multiple hosts, you must package the
Liberty runtime, the JDK, server configurations, and application files into a compressed file.
If all of these Liberty profile resources are in a single compressed file, the environment that
you deploy is said to be “self-contained”. The compressed file can be copied to any host
and manually extracted. Alternatively, you can use a job manager to install the Liberty
profile resources to a remote target host.
V8.1
Student Notebook
Uempty
Deploying Liberty topologies

• Choose which parts you must deploy
– Only the application
– Only the Liberty profile server
– The Liberty profile runtime and the server
– Any combination
• Example: A self-contained topology in which the compressed file
contains everything but the JDK
– The SDK is preinstalled on each host
WebSphere
Liberty Profile
Deploy
Server
Install
Liberty JDK
Application resources
Topology1.zip © Copyright IBM Corporation 2013
Figure 19-33. Deploying Liberty topologies WA855 / VA8551.0
Notes:
There are multiple scenarios or topologies for deploying Liberty profile resources. In
addition to deploying a “self-contained” topology as described on the previous slide, you
can choose to have the Liberty runtime and JDK preinstalled on the hosts, and then deploy
only the server configurations and applications. Other combinations of “shared topologies”
are possible.
Student Notebook
Example: A shared topology

• A shared topology where each compressed file contains only the
Liberty profile server definition
– Applications are predeployed as read-only and shared across different servers
– The Liberty profile and JDK are preinstalled and shared by different servers
Remote
target hosts
Server1
App
Server2 Deploy
WLP
JDK
Server3
Topology2.zip WLP = WebSphere Liberty Profile

Figure 19-34. Example: A shared topology WA855 / VA8551.0
Notes:
The graphic on this slide shows a shared topology where each compressed file contains
only the Liberty profile server definition. Applications are predeployed as read-only and
shared across different servers. Different servers preinstall and share the Liberty profile
and JDK.
The job manager can be used to deploy a shared topology to multiple remote hosts.
V8.1
Student Notebook
Uempty 19.4.Security
Student Notebook
Security

Figure 19-35. Security WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Liberty profile security

• All opened ports are local host only
• No remote management by default
• Seamless transition when enabling security
• Three key security-related features
Feature Description
ssl-1.0 Includes the SSL-specific code
appSecurity-1.0 Includes all the security services (authentication,

registry, authorization) and web-specific security code
zosSecurity-1.0 Includes the SAF registry and authorization code
Figure 19-36. Liberty profile security WA855 / VA8551.0
Notes:
Security in the Liberty profile supports all the servlet 3.0 security features. In addition, it
also secures Java JMX connections. The following server features are applicable to
security in the Liberty profile:
• The appSecurity-1.0 feature enables security for all web resources.
• The ssl-1.0 feature uses HTTPS to enable SSL connections.
• For z/OS platforms, zosSecurity-1.0 includes the support for SAF Registry and
Authorization on the z/OS platform.
• In addition, the restConnector-1.0 feature enables remote access by JMX clients
through a REST-based connector.
Student Notebook
Enable SSL
• Add the SSL feature and provide the keystore password
<featureManager>
<feature>ssl-1.0</feature>
</featureManager>
<keyStore id="defaultKeyStore" password="{xor}DFoKyp="/>
• Certificate is generated at server startup

• securityUtility can be used to generate a self-signed certificate
Figure 19-37. Enable SSL WA855 / VA8551.0
Notes:
To enable SSL for a server, you must add the ssl-1.0 feature to its configuration file. Also,
you must add the keystore configuration element and specify an ID and password. You can
use the security utility from the command line to generate a self-signed certificate and
provide the required configuration data. The screen capture on this slide shows you how to
run the security utility and the output it produces. The security utility requires you to specify
the server name and a password. The utility creates the keystore under the server
configuration directory and provides an encoded version of the password.
V8.1
Student Notebook
Uempty
Advanced SSL
• Configure per endpoint SSL configuration
<featureManager>
<feature>ssl-1.0</feature>
</featureManager>
<keyStore id="myKeyStore" password="{xor}DFoKyp="

location="${server.config.dir}/mykeystore.p12"
type="PKCS12"/>
<keyStore id="myTrustStore" password="{xor}DFoKyp="
location="${server.config.dir}/mytruststore.p12"
type="PKCS12"/>
<ssl id="mySSLConfig" keystoreRef="myKeyStore"
trustStoreRef="myTrustStore"/>
<httpEndpoint id="defaultHttpConfig">
<sslOptions sslRef="mySSLConfig"/>
</httpEndpoint>
Figure 19-38. Advanced SSL WA855 / VA8551.0
Notes:
The configuration elements in this example show how to configure secure HTTP.
An HTTP endpoint must have an sslOptions attribute, which specifies the SSL protocol
options. The SSL protocol options in the example use the sslRef attribute, which
specifies the SSL configuration to be used as the default.
The following steps define the SSL configuration.
First, the ssl-1.0 feature is enabled. Then, two keystore elements must be configured. One
is the keystore for the HTTP endpoint named “myKeyStore” in this example. The other is a
truststore for storing certificates of trusted servers named “myTrustStore” in this example.
Both of these configuration elements point to keystore files under the configuration
directory of the server: mykeystore.p12 and mytruststore.p12.
Next, an SSL configuration named mySSLConfig in this example defines a keystoreRef
and a truststoreRef in terms of the keystores that were previously configured.
Finally, and httpEndpoint attribute, sslOptions, defines the sslRef in terms of SSL
configuration, mySSLConfig.
Student Notebook
User registries
• Three types of registry
– Basic XML-based registry (Not for use in production)
– LDAP registry
– SAF registry (SAF is available only for z/OS)
• Used for application and JMX security

– One registry per server
Figure 19-39. User registries WA855 / VA8551.0
Notes:
The Liberty profile server uses a user registry to authenticate a user and retrieve
information about users and groups to do security-related operations, including
authentication and authorization.
When validating the authentication data of a user, the login modules call the user registry
that is configured to validate the user information. Liberty profile supports both a Basic
XML-based user registry and a more robust LDAP-based repository. For z/OS, a System
Authorization Facility (SAF) registry is also supported.
The Liberty profile supports only one user registry per server.
V8.1
Student Notebook
Uempty
Basic user registry

• Configured in server.xml
• Passwords can be encoded
– The securityUtilities.sh/bat command encodes passwords
– Developer tools encode automatically
<server>
<featureManager>
<feature>appSecurity-1.0</feature>
</featureManager>
<basicRegistry realm="basicRealm">
<user name="bob" password="{xor}CDo9Hgw=" />
<group name ="group1">
<member name = "bob"/>
</group>
</basicRegistry>
</server>
Figure 19-40. Basic user registry WA855 / VA8551.0
Notes:
A Basic registry is configured in the server.xml file. The appSecurity-1.0 feature must be
enabled. The basicRegistry configuration element is used to define a security realm,
users, and groups. The securityUtilities encode command-line tool is used to encode
passwords for each user. WebSphere Developer Tools automatically encodes passwords.
Student Notebook
LDAP user registry

• Authenticate by using an LDAP server
• Supports: Microsoft Active Directory, IBM Lotus Domino, Novell
eDirectory, IBM Tivoli Directory Server, Sun Java System Directory
Server, Netscape Directory Server, IBM SecureWay Directory Server
<server>
<featureManager>
<feature>appSecurity-1.0</feature>
</featureManager>
<ldapRegistry host="myldapserver.ibm.com"
port="389" baseDN="o=ibm,c=us"
ldapType="IBM Tivoli Directory Server" />
</server>
Figure 19-41. LDAP user registry WA855 / VA8551.0
Notes:
You can use an existing LDAP server for application authentication. To configure an LDAP
registry, you add the appSecurity-1.0 server feature to the server.xml file, and specify in
the server.xml file the configuration information for connecting to the LDAP server.
Use the ldapRegistry configuration element to specify the LDAP server host name,
LDAP port, and base distinguished name (baseDN) for the LDAP directory. The ldapType
specifies the LDAP Server product name. Several types of LDAP servers are listed on this
slide, including IBM Tivoli Directory Server, Microsoft Active Directory, and others.
Note: The example that is shown on this slide is basic. You can use many more attributes
to configure the LDAP registry such as: bindDN, bindPassword, userFilter,
groupFilter, and others. Also, SSL can be enabled by adding the necessary SSL
configuration information.
V8.1
Student Notebook
Uempty
SAF user registry

• Authenticate by using an SAF on z/OS
<featureManager>
<feature>zosSecurity-1.0</feature>
</featureManager>
<safRegistry id="saf"/>
Figure 19-42. SAF user registry WA855 / VA8551.0
Notes:
The System Authorization Facility (SAF) registry holds information that is needed to do
security-related functions such as authenticating users and retrieving information about
users, groups, or groups that are associated with users. You activate and configure the
SAF registry through the server.xml file.
Activate the SAF registry service by adding the zosSecurity-1.0 feature to the server.xml
file.
Configure web application security features to use the SAF registry service by adding the
appSecurity-1.0 feature.
Use a safRegistry configuration element to configure the SAF registry.
The safRegistry element has the following attributes: ID and realm. The ID uniquely
identifies this registry instance. The ID can be anything that you want, but must be among
other configured registries such as the basic registry and the LDAP registry.
The realm specifies the security realm that is associated with the SAF registry. If you do not
specify a realm, the default is the plex name (ECVTSPLX).
Student Notebook
Authorization
• Security role mappings are defined in
– Server configuration
– ibm-application-bnd.xml
<application location="secureapp.war">
<application-bnd>
<security-role name="users">
<user name="fred"/>
<group name="userGroup"/>
</security-role>
</application-bnd>
</application>
• SAF
<safAuthorization id="saf" />
Figure 19-43. Authorization WA855 / VA8551.0
Notes:
For application authorization, security role mappings must be defined in the server.xml
file, and the ibm-application-bnd.xml file in the application archive.
As part of an application configuration element, use the application-bnd and
security-role elements to define users and groups.
V8.1
Student Notebook
Uempty
Liberty administrative security

• One administrator role
• One user registry for applications and administrators
• Simple configuration for a single administrator user
<quickStartSecurity userName="bob"
userPassword="{xor}Lz4sLCgwLTs"/>
<keystore id="DefaultKeyStore"
password="{xor}DFoKyp="/>
• But still easy for multiple users

<administrator-role>
<user>fred</user>
<group>administratorsGroup</group>
</administrator-role>
Figure 19-44. Liberty administrative security WA855 / VA8551.0
Notes:
There is only one administrator role for the Liberty profile servers, and a single user registry
for both application security and administrative security.
All the JMX methods and MBeans accessed through the REST connector are currently
protected with a single role named “administrator”. To get started quickly, use the
quickStartSecurity element to configure a single user with administrator role and
configure the default SSL configuration. If you require only a single administrative user, you
can use the quickStartSecurity configuration element. The required attributes are a
user name and password.
For authorizing multiple users of administrative functions, use the administratorRole
element in the server.xml file to map the users to the administrator role.
Student Notebook
V8.1
Student Notebook
Uempty 19.5.Using the job manager to manage Liberty profile servers
Student Notebook
Using the job manager to

manage Liberty profile
servers

Figure 19-45. Using the job manager to manage Liberty profile servers WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Administering Liberty profiles by using the job manager

• Centralized remote management of Liberty profiles
• Uses remote target host capability of job manager
• Existing job types apply to Liberty profiles
– Inventory and status
• New job types
– Install or uninstall Liberty profile resources
– Start or stop Liberty profile servers
– Generate merged plug-in configuration
• New resource types
– Project
– Runtime
– Server
– Application
– JDK
Figure 19-46. Administering Liberty profiles by using the job manager WA855 / VA8551.0
Notes:
A job manager environment consists of a job manager and the targets that it manages. The
job manager targets can be deployment managers, stand-alone application server nodes
that administrative agents manage, and host computers. Setting up a job manager
environment involves creating a job manager profile and any other profiles that are needed
for the environment. The clocks are synchronized on all environment computers, and then
the targets are registered with the job manager.
Student Notebook
Job manager Liberty profile jobs

• From the job manager administrative console, click Jobs > Submit
New job types
Install Liberty profile resources

Start Liberty profile server
Stop Liberty profile server
Uninstall Liberty profile resources
Figure 19-47. Job manager Liberty profile jobs WA855 / VA8551.0
Notes:
You can submit the Install Liberty profile resources job to extract resources in a Liberty
profile image to destination directories relative to a root directory.
Before running the Install Liberty profile resources job, the following conditions must exist:
• The job manager must be running.
• A host computer must be registered with the job manager.
• The image, a compressed file, must contain Liberty profile resources in a directory
structure that satisfies job manager rules.
• The root directory to install the resources on the target host must be defined. At
minimum, set the WLP_WORKING_DIR variable to a valid directory that is on a target host.
To install the resources to a shared directory on the target host, you must set the
WLP_SHARED_DIR variable to a valid directory.
V8.1
Student Notebook
Uempty
Deploying a self-contained topology

• A self-contained topology is packaged as a compressed file that
contains following resources: a Liberty profile runtime, a JDK, a Liberty
profile server, an application
• The job manager can deploy the topology to multiple target hosts
Remote target
hosts
WebSphere (“loose cluster”)
Liberty Profile
JDK
Job: Install Liberty
resources Deploy
Server
Install Liberty
resources job
Application
Job manager
Topology.zip
Figure 19-48. Deploying a self-contained topology WA855 / VA8551.0
Notes:
The job manager can be used to deploy the self-contained topology to multiple remote
hosts. One advantage of this topology is that no additional resources are required on the
remote hosts.
Student Notebook
HTTP request routing

• For workload management (WLM), the HTTP server plug-in must be
able to read a plugin-cfg.xml file that contains plug-in
configuration from all the Liberty profile servers
• Job manager can create a merged plug-in configuration file
“Loose” cluster
Liberty profile
server
server1 XML
IBM HTTP
Server
Job manager
Shared apps
XML
Liberty profile
Merged server
plugin-cfg.xml server2 XML
Figure 19-49. HTTP request routing WA855 / VA8551.0
Notes:
When the job manager completes the Generate merged plug-in configuration job, it
generates a plugin-cfg.xml file for each server that is specified and merges these files
into a single file. The merged plugin-cfg.xml file can then be accessed with the HTTP
server plug-in to route requests to the Liberty profile servers.
V8.1
Student Notebook
Uempty
Job type: Generate merged plug-in configuration

• Use the Find facility to specify the resource ID for one server
• Use pattern matching to specify multiple servers
• Servers must be started
Figure 19-50. Job type: Generate merged plug-in configuration WA855 / VA8551.0
Notes:
Specify the resource name or resource ID of the server to generate a plug-in. The server or
servers must be started for this job to complete successfully.
This job requires a JMX connector or REST connector configuration in the Liberty profile
server. Add the feature <feature>localConnector-1.0</feature> to the server.xml
file for each server.
The localConnector-1.0 feature provides a local JMX connector that is built into the JVM. It
can be used only on the same host machine by someone who is running under the same
user ID and the same JDK. It enables local access by JMX clients such as jConsole, or
other JMX clients that use the Attach API necessary for generating HTTP plug-in
configuration data.
The remote JMX connector is: <feature>restConnector-1.0</feature>
The restConnector-1.0 feature provides a secure JMX connector that can be used locally
or remotely when using any JDK. It enables remote access by JMX clients through a
REST-based connector and requires SSL and basic user security configuration.
Student Notebook
Merged plugin-cfg.xml
<ServerCluster
<ServerCluster CloneSeparatorChange="false"
CloneSeparatorChange="false" GetDWLMTable="false"
GetDWLMTable="false"
IgnoreAffinityRequests="true"
IgnoreAffinityRequests="true" LoadBalance="Round
Robin"
Name="Shared_2_Cluster_0"
Name="Shared_2_Cluster_0" PostBufferSize="64"
PostBufferSize="64" PostSizeLimit="-1"
PostSizeLimit="-1"
RemoveSpecialHeaders="true"
RemoveSpecialHeaders="true" RetryInterval="60">
RetryInterval="60">
<Server CloneID="e9da8378-7892-4993-8ce0-7e838e6bf6d2"
<Server CloneID="e9da8378-7892-4993-8ce0-7e838e6bf6d2"
ConnectTimeout="0"
ConnectTimeout="0" ExtendedHandshake="false"
ExtendedHandshake="false"
MaxConnections="-1"
MaxConnections="-1" Name="default_node_defaultServer0_1"
Name="default_node_defaultServer0_1"
ServerIOTimeout="900"
ServerIOTimeout="900" WaitForContinue="false">
WaitForContinue="false">
<Transport
Protocol="http"/>
</Server>
</Server>
<Server CloneID="306b1428-4119-4b9d-bae0-e7cc0cc5e0a8"
<Server CloneID="306b1428-4119-4b9d-bae0-e7cc0cc5e0a8"
ConnectTimeout="0"
ConnectTimeout="0" ExtendedHandshake="false"
ExtendedHandshake="false"
MaxConnections="-1"
MaxConnections="-1" Name="default_node_defaultServer0_0"
Name="default_node_defaultServer0_0"
ServerIOTimeout="900"
ServerIOTimeout="900" WaitForContinue="false">
WaitForContinue="false">
<Transport
Protocol="http"/>
</Server>
</Server>
.. .. ..
</ServerCluster>
</ServerCluster>
Figure 19-51. Merged plugin-cfg.xml WA855 / VA8551.0
Notes:
This slide shows a snippet of the merged plugin-cfg.xml file. Notice that it contains the
CLoneIDs for server1 and server2.
V8.1
Student Notebook
Uempty 19.6.Liberty collectives and clusters
Student Notebook
Liberty collectives and

clusters

Figure 19-52. Liberty collectives and clusters WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Liberty collectives and clusters

• A Liberty collective is like a traditional WebSphere cell
– More loosely coupled
• A Liberty collective controller is like a deployment manager

– Scalable and highly-available
• A Liberty cluster is like a traditional WebSphere cluster

– Any Liberty profile servers can be added and removed from Liberty clusters
Figure 19-53. Liberty collectives and clusters WA855 / VA8551.0
Notes:
A Liberty collective is like a traditional WebSphere Application Server cell. A Liberty
collective is more loosely coupled than a traditional cell. There is no central master
configuration.
A Liberty collective controller is like a deployment manager. You can use multiple collective
controllers to manage the same collective.
A Liberty cluster is like a traditional WebSphere Application Server cluster. Liberty cluster
members are loosely associated. Liberty cluster members do not have to run all the same
applications. Liberty profile servers can be added and removed from clusters as needed.
Student Notebook
Example of server clusters and a Liberty collective

Collective controller replica set
Collective Collective Collective
Controller Replica Controller Replica Controller Replica
ClusterOne ClusterTwo Collective

member1
member1 member1
Collective
member2
member2
member2 Collective
member3 member3
member3 member4 Collective

member4
55 © Copyright IBM Corporation 2013
Figure 19-54. Example of server clusters and a Liberty collective WA855 / VA8551.0
Notes:
This diagram demonstrates a collective that has 11 collective members. Among these 11
members, three members belong to the server cluster “ClusterOne”, four of them belong to
the server cluster “ClusterTwo”, and four do not belong to any server cluster.
V8.1
Student Notebook
Uempty
Administering Liberty profiles in collectives

• A Liberty collective is an administrative domain for Liberty profiles
– Analogous to a traditional WebSphere cell
• Standards-based administration API
– Built on JMX (MBeans)
– Works with common tools (Jconsole, Jython, and so on)
• Loosely-coupled
– No centralized master configuration
– No nodeagents
• Management server is called a collective controller
– Analogous to a deployment manager
– Application servers cache sparse configuration data and state in the controller
– Application servers own their own configuration
• Scalable and resilient
– Can have multiple controller servers for the same collective
– Replicate member state and configuration data between collective controllers
Figure 19-55. Administering Liberty profiles in collectives WA855 / VA8551.0
Notes:
The Liberty collective was built on five core principles:
1. Administration should be exposed through a standards-based API. All administration for
Liberty is provided through MBeans, which enables a common set of tools to perform
administrative actions.
2. The entities within a collective should be loosely coupled to the collective. Therefore, all
configuration that is related to the collective is isolated and self-contained, facilitating
easily moving servers in and out of the collective.
3. The administrative server, called a collective controller, acts as a distributed cache.
Application servers within the collective publish information to the controller about
themselves, such as which applications are installed, their operational state, and the
available MBeans. The controller also serves as a bidirectional JMX proxy, allowing
MBean operations to be routed to members within the collective.
4. Each member in the Liberty collective owns its own configuration. There is no central,
master repository of configuration as there is in the full profile cell.
Student Notebook
5. The administrative server is highly scalable and highly available through a replica
model, allowing multiple instances of controllers to share data and perform the same
operations. The model is agentless, which means a separate agent process is not
required on each host system within the collective.
V8.1
Student Notebook
Uempty
Liberty profile collective controller and collective members

• Collective controller
– A Liberty server with the collectiveController feature enabled
• Network Deployment Liberty Profile only
– Caches the configuration and state of collective members
– Send commands to collective members
– Multiple collective controller servers can manage the same collective
• Collective member
– A Liberty server with the collectiveMember feature enabled
• All Liberty Profile editions
– Sends configuration data and state to one of the collective controllers
– Accepts commands from collective controller servers
Figure 19-56. Liberty profile collective controller and collective members WA855 / VA8551.0
Notes:
To set up a collective, you first need a collective controller. Any Liberty server can act as a
collective controller. Liberty collectives are designed to provide scalable and resilient
administration by supporting multiple controllers within a collective. The replica set of
collective controller servers enables the size of a collective to scale out, and provides a
highly available administrative server environment.
After configuration, a collective member server can be started, and it automatically
publishes information about itself to the collective controller.
Student Notebook
Liberty clusters
• A Liberty profile can be configured into a server cluster for application
high availability and scalability.
• A server cluster is a logical grouping of related servers
• The server cluster feature clusterMember-1.0 is only available in the

Network Deployment Liberty Profile
• A server cluster can only be defined within a Liberty collective
• All server cluster members must be members of the same collective
• One collective can have multiple server clusters
Figure 19-57. Liberty clusters WA855 / VA8551.0
Notes:
A Liberty server cluster consists of two or more Liberty servers within a Liberty collective.
Logically grouped servers might have the same applications, be related to the same
business unit, or have the same administrators.
The cluster name is a string value that you define and must be unique within a Liberty
collective. The status of a Liberty server cluster is stored in the collective repository.
V8.1
Student Notebook
Uempty
Unit summary
• Create a Liberty profile server by using developer tools and command-
line utilities
• Describe the process for enabling security for a Liberty profile server
Notes:
Student Notebook
1. (True or false) The Liberty profile is freely available.
2. (True or false) Liberty profile servers support everything that the full
profile WebSphere Application Server supports.
3. (True or false) Liberty profile servers can be created only with a

developer tool such as WebSphere Application Server Developer
Tools.
4. (True or false) The job manager can be used to install Liberty profile
resources on remote target hosts.
Notes:
1. 
2. 
3. 
4.
V8.1
Student Notebook
Uempty
Checkpoint answers
1. True: The Liberty profile is freely available for developers.
2. False: Liberty profile servers support only a subset of what the full
WebSphere Application Server supports.
3. False: A server create command can also be used.
4. True
Notes:
Student Notebook
Exercise 15
Working with the Liberty profile

Notes:
V8.1
Student Notebook
Uempty
Exercise objectives
• Use IBM Assembly and Deploy Tools to install the Liberty Profile
Runtime Environment
• Start and stop a Liberty profile application server by using the
command line and through IBM Assembly and Deploy Tools
• Deploy a simple application by using IBM Assembly and Deploy Tools
• Deploy an application by using the dropins directory
• Deploy an application with a data source
• Configure SSL for a Liberty profile application server
• Configure a user registry for a Liberty profile application server
• Configure application security for a Liberty profile application server
• Use flexible configuration to create shared configurations
• Configure a Liberty profile server to generate a plug-in configuration file
Notes:
Student Notebook
V8.1
Student Notebook
Uempty Unit 20. Performance monitoring

This unit describes performance monitoring methods and tools that
are available through the administrative console.

• Describe performance monitoring and tuning methods
• Use the Tivoli Performance Viewer to monitor application server
resources
• Use the performance servlet to generate performance data
• Configure the Request Metrics tool to generate performance data
about the end-to-end request flow
• Use Performance Advisors to generate suggested tuning actions
• Enable the performance collectors from IBM Tivoli Composite
Application Manager for WebSphere Application Server

• Lab exercises
References
WebSphere Application Server V8.5 Information Center, Monitoring,
and Tuning Performance:
© Copyright IBM Corp. 2013 Unit 20. Performance monitoring 20-1

Student Notebook
Unit objectives
resources
• Configure the Request Metrics tool to generate performance data about
the end-to-end request flow
Notes:
V8.1
Student Notebook
Uempty
Topics
• Performance tuning and monitoring
• Request metrics
• Performance advisors
Server
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 20.1.Performance tuning and monitoring

Student Notebook
Performance tuning and

monitoring

Figure 20-3. Performance tuning and monitoring WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
The need for performance monitoring and tuning

• How well a website performs while receiving heavy user traffic is an
essential factor in the overall success of an organization
• Poor performance results in:
– Escalated support costs
– Loss of customer confidence
– Loss of revenue
• Performance problems can be anywhere in the application server
environment
– Monitoring ensures that applications are running as expected and, if not,
determines why and where the problem lies
• WebSphere Application Server can function with default settings but:
– Improving throughput, and reducing server response times, requires more tuning
Figure 20-4. The need for performance monitoring and tuning WA855 / VA8551.0
Notes:
The goal of performance monitoring is to collect runtime statistics on your application and
its environment to quantify their performance behavior. It allows you to determine whether
your application meets its performance objectives and helps to identify any performance
bottlenecks.

Student Notebook
Tuning performance suggested practices

• Plan for performance
• Take advantage of performance functions (for example, use the
dynamic cache service)
• Obtain performance advice from the advisors
• Tune the environment
• Troubleshoot performance problems
Figure 20-5. Tuning performance suggested practices WA855 / VA8551.0
Notes:
Tuning WebSphere Application Server is a critical part of getting the best performance from
your website. But tuning WebSphere Application Server involves analyzing performance
data and determining the optimal server configuration. This determination requires
considerable knowledge about the various components in the application server and their
performance characteristics. The performance advisors encapsulate this knowledge and
analyze the performance data. The advisors provide configuration recommendations to
improve the application server performance. Therefore, the performance advisors provide
a starting point for tuning the application server. Keep in mind the following suggestions:
• Take advantage of performance functions.
• Obtain performance advice from the advisors.
• Tune the environment.
• Troubleshoot performance problems.
V8.1
Student Notebook
Uempty
Performance terminology
• Response time measures an individual user’s average wait for a
request
• Response time includes:
– Processing time
– Transit time
– Wait time in queues
• Throughput measures activities that are completed in a unit of time
– Example: Website pages that are served per second
• Bottleneck defines a choke point in the system that is manifested as
multiple threads that are waiting for some task to complete
• Bottlenecks result when users are queued waiting for a shared resource
– Processor
– Data source connections
– Disk I/O
• Load is user activity against a website
– Users arriving, logging in, sending requests
– Requests per second, pages per hour
Figure 20-6. Performance terminology WA855 / VA8551.0
Notes:
Some other performance-related terms are path length, scalability, and capacity.
Path length refers to the number of steps an action takes. Reducing the path length
speeds up a website or application. Path length reduction can be achieved by speeding up
the steps and reducing the number of steps an activity takes.
Scalability defines how easily a site can expand. Sites must expand, sometimes with little
warning, to support increased load. Load can come from many sources: new markets,
normal growth, and extreme peaks in activity.
Capacity describes how much load the site can support. Discovering the website capacity
is the result of performance and load testing.

Student Notebook
Tuning parameter hot list

• Review hardware and software requirements
• Install the current refresh pack, fix pack, and the interim fixes
• Check hardware configuration and settings
• Tune the operating system
• Set the minimum and maximum Java virtual machine (JVM) heap sizes
• Use type 4 (pure Java) JDBC driver when feasible
• Tune WebSphere Application Server data sources and connection
pools
• Enable the pass by reference option
• Tune related components, for example, the database
• Disable functions that are not required
• Review the application design
Figure 20-7. Tuning parameter hot list WA855 / VA8551.0
Notes:
This hot list contains recommendations that improve performance or scalability, or both, for
many applications.
WebSphere Application Server provides several tunable parameters and options to match
the application server environment to the requirements of your application.
• Review the hardware and software requirements.
For correct functionality and performance, it is critical to satisfy the minimum hardware
and software requirements. See the IBM WebSphere Application Server supported
hardware, software, and APIs website, which details hardware and software
requirements.
• Install the most current refresh pack, fix pack, and suggested interim fixes.
The list of suggested updates is maintained on the support site.
• Check hardware configuration and settings.
V8.1
Student Notebook
Uempty Verify that network interconnections and hardware configuration are set up for peak
performance.
• Tune the operating systems.
Operating system configuration plays a key role in performance. For example,
adjustments such as TCP/IP parameters might be necessary for your application.
• Set the minimum and maximum Java virtual machine (JVM) heap sizes.
Many applications need a larger heap size than the default for best performance. It is
also advisable to select an appropriate GC policy that is based on the characteristics of
the application.
• Use a type 4 (or pure Java) JDBC driver.
In general, the type 2 JDBC driver is suggested if the database exists on the same
physical machine as the WebSphere instance. However, in the case where the
database is in a different tier, the type 4 JDBC driver offers the fastest performance
since it is pure Java and does not require native implementation.
• Tune WebSphere Application Server JDBC data sources and associated
connection pools.
The JDBC data source configuration might have a significant performance impact. For
example, the connection pool size and prepared statement cache must be sized based
on the number of concurrent requests that are processed and the design of the
application.
• Enable the pass by reference option.
Use applications that can take advantage of the pass by reference option to avoid the
cost of copying parameters to the stack.
• Ensure that the transaction log is assigned to a fast disk.
Some applications generate a high rate of writes to the WebSphere Application Server
transaction log. Locating the transaction log on a fast disk or disk array can improve
response time.
• Tune related components; for example, database.
In many cases, some other component, for example a database, needs adjustments to
achieve higher throughput for your entire configuration.
• Disable functions that are not required.
For example, if your application does not use the web services addressing
(WS-Addressing) support, disabling this function can improve performance. Attention:
Use this property with care because applications might require WS-Addressing MAPs
to function correctly. Setting this property also disables WebSphere Application Server
support for the following specifications, which depend on the WS-Addressing support:
Web Services Atomic Transactions, Web Services Business Agreement, and Web

Student Notebook
Services-Notification. To disable the support for WS-Addressing, see Enabling Web

Services Addressing support for JAX-RPC applications.
• Review your application design.
You can track many performance problems back to the application design. Review the
design to determine whether it causes performance problems.
V8.1
Student Notebook
Uempty
Solving performance problems

• An iterative process:
1. Load test the system
2. Monitor and collect performance data
3. Identify bottlenecks 1
4. Tune parameters to eliminate the most
severe bottleneck
5. Repeat
2
Performance 3
data
5
4
Figure 20-8. Solving performance problems WA855 / VA8551.0
Notes:
Your application and its runtime environment must also be tuned optimally. This process
entails conducting many iterations of a monitor, tune, and test cycle. In short, monitoring,
performance testing, and tuning are essential tasks for ensuring a well-performing,
application-serving environment.
This process is often iterative because when one bottleneck is removed, some other part of
the system now constrains the performance. For example, replacing slow hard disks with
faster ones might shift the bottleneck to the processor of a system.

Student Notebook
Measuring performance and collecting data

• Establish a benchmark:
– A benchmark is a standard set of application functions to run
– Use the benchmark to test the application under expected loads
– Record throughput and response time under normal load and peak load
• Two types of performance data:

– WebSphere Application Server Performance Monitoring Infrastructure (PMI)
provides performance data that you can use to tune application server
performance
– With the Request Metrics tool, you can track individual transactions, recording
the processing time in each of the major WebSphere Application Server
components
Figure 20-9. Measuring performance and collecting data WA855 / VA8551.0
Notes:
Begin by choosing a benchmark, a standard set of operations to run. This benchmark
exercises those application functions experiencing performance problems. Complex
systems frequently need a warm-up period to cache objects and optimize code paths.
System performance during the warm-up period is much slower than after the warm-up
period. The benchmark must be able to generate work that warms up the system before
recording the measurements that are used for performance analysis. Depending on the
system complexity, a warm-up period can range from a few thousand transactions to longer
than 30 minutes.
If the performance problem under investigation occurs only when many clients use the
system, then the benchmark must also simulate multiple users. Another key requirement is
that the benchmark must be able to produce repeatable results. If the results vary more
than a few percent from one run to another, consider the possibility that the initial state of
the system might not be the same for each run. It might also be that the measurements are
made during the warm-up period, or that the system is running more workloads.
V8.1
Student Notebook
Uempty Several tools facilitate benchmark development. The tools range from tools that merely
invoke a URL to script-based products that can interact with dynamic data that the
application generates. IBM Rational has tools that can generate complex interactions with
the system under test and simulate thousands of users. Producing a useful benchmark
requires effort and must be part of the development process. Do not wait until an
application goes into production to determine how to measure performance.
The benchmark records throughput and response time results in a form to allow graphing
and other analysis techniques. The performance data that WebSphere Application Server
Performance Monitoring Infrastructure (PMI) provides helps to monitor and tune the
application server performance. Request metrics are another source of performance data
that WebSphere Application Server provides. Request metrics allow a request to be timed
at WebSphere Application Server component boundaries, enabling a determination of the
time that is spent in each major component.

Student Notebook
WebSphere performance tools (1 of 3)

• WebSphere provides integrated tools to monitor and tune system and
application performance:
• Tivoli Performance Viewer

– With Tivoli Performance Viewer, administrators can monitor the overall health
of WebSphere Application Server
– Accessed from within the administrative console
– Analyze collected performance data and provide configuration
recommendations to improve the application server performance
– Output can be viewed in Tivoli Performance Viewer or in administrative
console runtime messages
Figure 20-10. WebSphere performance tools (1 of 3) WA855 / VA8551.0
Notes:
These tools are explained in greater detail in the subsequent sections.
V8.1
Student Notebook
Uempty

• Request Metrics (tool)
– With request metrics, you can track individual transactions, recording the
processing time in each of the major WebSphere Application Server components
– Output is viewed in standard logs or by using an Application Response
Measurement (ARM)-based tool
• Performance servlet
– Provides simple retrieval of performance data in XML format
– Accessed through a browser

Server
– Installed separately
– Provides other IBM Tivoli Composite Application Manager collectors for Java EE
applications
– Performance metrics are viewable as a Tivoli Performance Viewer performance
module
Notes:
These tools are explained in greater detail in the subsequent topics.

Student Notebook

and Advisors
ARM agent
PMI data Request metrics
Performance
servlet
XML Server
logs
ARM= Application Response Measurement
Notes:
WebSphere provides integrated tools to monitor and tune system and application
performance:
• Tivoli Performance Viewer
- Gives administrators the ability to monitor the overall health of WebSphere
Application Server
- Accessed from within the administrative console
• Request metrics (tool)
- Gives you the ability to track individual transactions, recording the processing time in
each of the major WebSphere Application Server components
- Output is viewed in standard logs or by using an Application Response
Measurement (ARM)-based tool
V8.1
Student Notebook
Uempty - Analyze collected performance data and provide configuration recommendations to

improve the application server performance
- Output is viewed in Tivoli Performance Viewer or in administrative console runtime
messages
• Performance servlet
- Provides simple retrieval of performance data in XML format
- Accessed through a browser

Student Notebook
PMI architecture
WebSphere PMI interface Partner and
customer API
IBM Tivoli Monitoring for

Web Infrastructure
JMX WebSphere
User-developed client Application
monitoring tools Server
Third-party monitoring PMI service

tools JMX API
JMX API
PMI API Deployment
manager
(JMX connector) WebSphere
Web Application
client Server
PMI service
Figure 20-13. PMI architecture WA855 / VA8551.0
Notes:
The Performance Monitoring Infrastructure (PMI) uses a client/server architecture.
The figure shows the overall PMI architecture. On the right side, the server updates and
keeps PMI data in memory. The left side displays a web client, a Java client, and a JMX
client that retrieves the performance data. This data consists of counters such as servlet
response time and data connection pool usage. The data points are then retrieved by using
a web client, a Java client, or a Java Management Extensions (JMX) client. WebSphere
Application Server contains Tivoli Performance Viewer, a Java client that displays and
monitors performance data.
The server collects performance data from various WebSphere Application Server
components. A client retrieves performance data from one or more servers and processes
the data. WebSphere Application Server supports the Java Platform, Enterprise Edition
(Java EE) Management Reference Implementation (JSR-77).
PMI counters are enabled, based on a monitoring or instrumentation level. The levels are
None, Basic, Extended, All, and Custom. These levels are specified in the PMI module
XML file. Enabling the module at a certain level includes all the counters at that level plus
V8.1
Student Notebook
Uempty counters from levels below that level. So, enabling the module at the extended level
enables all the counters at that level plus all the Basic level counters.
JSR-077 defines a set of statistics for Java EE components as part of the Statistic Provider
interface. The PMI monitoring level of Basic includes all of the JSR-077 specified statistics.
PMI is set to monitor at a Basic level by default.

Student Notebook
Types of performance data

• System resources such as processor utilization
• WebSphere pools and queues, such as a database connection pool
• Customer application data, such as average servlet response time
• You can also view data for other products or customer applications that
implement custom PMI by using the Tivoli Performance Viewer
Figure 20-14. Types of performance data WA855 / VA8551.0
Notes:
Tivoli Performance Viewer is used to help manage configuration settings by viewing the
various graphs or by using the Tivoli Performance Advisor. For example, by looking at the
summary chart for thread pools, you can determine whether the thread pool size must be
increased or decreased by monitoring the percent usage. After configuration settings are
changed based on the data that is provided, you can determine the effectiveness of the
changes. To help with configuration settings, use the Tivoli Performance Advisor. The
Advisor assesses various data while your application is running, and provides advice about
configuration settings to improve performance.
V8.1
Student Notebook
Uempty
PMI data collection settings

• None
– All statistics are disabled
• Basic
– Statistics that are specified in Java EE specification, plus top statistics like
processor usage and live HTTP sessions, are enabled
– This set is enabled by default and provides basic performance data about
runtime and application components (up to 2% more processor usage)
• Extended
– Basic set, plus key statistics from various WebSphere Application Server
components like WLM and dynamic caching, are enabled
– This set provides detailed performance data about various runtime and
application components (up to 3% more processor usage)
• All
– All statistics are enabled (up to 6% more processor usage)
• Custom
– Statistics are enabled or disabled individually
Figure 20-15. PMI data collection settings WA855 / VA8551.0
Notes:
PMI uses statistics sets to specify the type and amount of performance data to collect.
PMI counters are enabled, based on a monitoring or instrumentation level. The levels are
None, Basic, Extended, All, and Custom. These levels are specified in the PMI module
XML file. Enabling the module at a certain level includes all the counters at that level plus
counters from levels below that level. So, enabling the module at the extended level
enables all the counters at that level plus all the Basic level counters as well.

Student Notebook
Using the administrative console to enable PMI

• Click Servers >
Server Types >
Servers > server_name
• On the Configuration tab,
under Performance, click
Performance Monitoring
Infrastructure (PMI)
• Select the Enable
Performance Monitoring
Infrastructure (PMI) check
box
• Select the statistics set
Figure 20-16. Using the administrative console to enable PMI WA855 / VA8551.0
Notes:
Click Servers > Server Types > WebSphere Application Servers > <server_name>.
On the Configuration tab, under Performance, click Performance Monitoring
Infrastructure (PMI).
Select the Enable Performance Monitoring Infrastructure (PMI) check box.
V8.1
Student Notebook
Uempty
Start monitoring
• After enabling PMI, select the server and click Start Monitoring on
the Tivoli Performance Viewer page
– In the administrative console, select Monitoring and Tuning >
Performance Viewer > Current activity
Figure 20-17. Start monitoring WA855 / VA8551.0
Notes:
• Deprecated feature: Tivoli Performance Viewer displays graphics in either the Scalable
Vector Graphics (SVG) format or as a static image in the JPG format. If you do not have
the Adobe SVG browser plug-in, you are prompted to download and install it. If you
select not to install the plug-in (by selecting Cancel), Tivoli Performance Viewer displays
the static image.
Installing the Adobe SVG plug-in is advantageous for several reasons. First, the SVG
format provides interactive graphics that provide more information when you hover your
mouse over a point, line, or legend item. The SVG format also allows you to click a point
and see details for it. Second, using the SVG format provides a performance benefit
because the work to display the SVG image is done on the client side. When viewing a
static image, the application server must convert the SVG image into a static image,
which is a processor-intensive and memory-intensive operation. If your browser is
Internet Explorer 7, the Adobe SVG installation prompt might be inaccessible. To
resolve the problem, you can reinstall Adobe SVG.

Student Notebook
• For users who are migrating from version 7: Beginning with version 8, the Tivoli
Performance Viewer graph uses Dojo technology for plotting the performance activity
rather than the Scalable Vector Graphics (SVG) format. The Dojo format provides a
better user experience and is more processor and memory efficient for the application
server. The SVG format is still supported but is deprecated in version 8 of this product.
To use the SVG format and image format, set the JVM property to false; for example:
com.ibm.websphere.tpv.DojoGraph=false
If the property is set to false, Dojo is disabled, and Tivoli Performance Viewer uses the
SVG format to display interactive graphics; or it uses the JPG format to display
non-interactive graphics.
When you specify to use the SVG format by setting
com.ibm.websphere.tpv.DojoGraph=false, if you do not have the Adobe SVG
browser plug-in, you are prompted to download and install it. If you select not to install
the plug-in (by selecting Cancel), Tivoli Performance Viewer displays the static image. If
your browser is Internet Explorer 7, the Adobe SVG installation prompt might be
inaccessible. To resolve the problem, you can reinstall Adobe SVG. By default, this
property is set to a value of true to use the Dojo format.
V8.1
Student Notebook
Uempty
Tivoli Performance Viewer (1 of 4)

• Select one or more performance
modules to monitor from the
navigation page
• Click View Module(s)
• The performance data is
dynamically displayed in a chart
and table
• Note: The disabled modules
become active when you enable
the Extended or All PMI statistics
sets
JVM runtime
module is
selected
Figure 20-18. Tivoli Performance Viewer (1 of 4) WA855 / VA8551.0
Notes:
The screen capture on this slide shows the navigation tree in Tivoli Performance Viewer
where you can select which components to monitor. In this case, the JVM Runtime module
is selected.

Student Notebook

• Chart view of JVM metrics
Notes:
Statistics for the selected modules are displayed as a line graph. You can select which
metrics you want to display in the graph, and you can optionally show the legend. In this
example, only the heap size and used memory metrics are displayed for the JVM runtime.
The sawtooth pattern of the used memory graph is typical of a steady state JVM. The
periodic reductions in used memory correspond to JVM garbage collections, which return
unused memory to the heap.
V8.1
Student Notebook
Uempty

• Chart view controls
– Reset To Zero
– Clear Buffer
– View Table
– Show/Hide Legend
Notes:
The Reset to zero button sets a new baseline by using the current counter readings at the
instant the button is clicked. Future data points are plotted on the graph relative to their
position at the time Reset to zero is clicked. Data points that are gathered before the time
Reset to zero is clicked are not displayed, although they are still held in the Tivoli
Performance Viewer buffer. If Undo Reset to zero is clicked again, Tivoli Performance
Viewer displays all data that is recorded from the original baseline, not from the Reset to
zero point.
Click Clear Buffer to remove the PMI data from a table or chart.

Student Notebook

• Table view
Notes:
Statistics can also be viewed in a table format, by clicking View Table in the Tivoli
Performance Viewer.
V8.1
Student Notebook
Uempty
Summary reports
• View a statistics report by selecting one of the summary reports
• Servlets
– Lists all servlets that are running in the current application server
• EJBs
– Lists all EJBs running in the server
– Amount of time that is spent in their methods
– Number of EJB invocations
– Total time that is spent in each EJB
• EJB methods
– Details about methods
• Connection pool
– Lists all data source connections that
are defined in the application server
and show their usage over time
• Thread pool
– Shows the usage of all thread pools
in the application server over time
Figure 20-22. Summary reports WA855 / VA8551.0
Notes:
Servlets:
The servlet summary lists all servlets that are running in the current application server.
Use the servlet summary view to quickly find the most time-intensive servlets and the
applications that use them, and to determine which servlets are used most often. You
can sort the summary table by any of the columns.
Tip: Sort by Average Response Time to find the slowest servlet or JSP page. Sort by
Total Requests to find the servlet or JSP that is used the most. Sort by Total Time to
find the most costly servlet or JSP.
Enterprise JavaBeans:
The Enterprise JavaBeans (EJB) summary lists the following information: all enterprise
beans that are running in the server, the amount of time that is spent in their methods,
the number of EJB invocations, and the total time that is spent in each enterprise bean.
total_time = number_of_invocations * time_in_methods

Student Notebook
Sort the various columns to find the most expensive enterprise bean. Also, if the PMI
counters are enabled for individual EJB methods, there is a check box next to the EJB
name that you can select to see statistics for each of the methods.
Tip: Sort by Average Response Time to find the slowest enterprise bean. Sort by
Method Calls to find the enterprise bean that is used the most. Sort by Total Time to
find the most costly enterprise bean.
EJB methods:
The EJB method summary shows statistics for each EJB method. Use the EJB method
summary to find the most costly methods of your enterprise beans.
Tip: Sort by Average Response Time to find the slowest EJB method. Sort by Method
Calls to find the EJB method that is used the most. Sort by Total Time to find the most
costly EJB method.
Connection pools:
The connection pool summary lists all data source connections that are defined in the
application server and shows their usage over time.
When the application is experiencing normal to heavy usage, the pools that the
application uses must be nearly fully used. Low utilization means that resources are
being wasted by maintaining connections or threads that are never used. Consider the
order in which work progresses through the various pools. If the resources near the end
of the pipeline are underused, it might mean that resources near the front are
constrained or that more resources than necessary are allocated near the end of the
pipeline.
Thread pools:
The thread pool summary shows the usage of all thread pools in the application server
over time.
When the application is experiencing normal to heavy usage, the pools that the
application uses must be nearly fully used. Low utilization means that resources are
being wasted by maintaining connections or threads that are never used. Consider the
order in which work progresses through the various pools. If the resources near the end
of the pipeline are underused, it might mean that resources near the front are
constrained or that more resources than necessary are allocated near the end of the
pipeline.
V8.1
Student Notebook
Uempty
Example: Servlet Summary Report

• Use the servlet summary to:
– Find the servlets that use the most time and the applications that use them
– Determine which servlets are called most often
• You can sort the summary table by any of the columns
Figure 20-23. Example: Servlet Summary Report WA855 / VA8551.0
Notes:
In this screen capture, the servlets report is shown with the total requests column sorted.
You can see which two servlets in the PlantsByWebSphere application are used most
frequently.

Student Notebook
Performance servlet overview

• Provides performance data output as an XML document, as the
provided document type definition (DTD) describes
– The DTD is located inside the PerfServletApp.ear file
• Deployed exactly as any other servlet:

1. Deploy the servlet on a single application server instance within the domain
2. After the servlet deploys, you can start it to retrieve performance data for the
entire domain; start the performance servlet by accessing the following default
URL:
http://<hostname>/wasPerfTool/servlet/perfservlet
Figure 20-24. Performance servlet overview WA855 / VA8551.0
Notes:
The servlet provides a way to use an HTTP request to query the performance metrics for
an entire WebSphere Application Server administrative domain. Because the servlet
provides the performance data through HTTP, issues such as firewalls are trivial to resolve.
The PerfServlet provides the performance data output as an XML document, as described
in the provided document type definition (DTD). In the XML structure, the leaves of the
structure provide the actual observations of performance data and the paths to the leaves
that provide the context.
The performance servlet EAR file PerfServletApp.ear is in the
WAS_HOME/installableApps directory, where WAS_HOME is the installation path for
WebSphere Application Server.
V8.1
Student Notebook
Uempty
Performance servlet output
Figure 20-25. Performance servlet output WA855 / VA8551.0
Notes:
This screen capture shows sample output that the performance servlet generates, which is
displayed in a browser. The section that is shown here represents a request to the Snoop
Servlet.
Tip: The PerfServlet is a sample monitoring tool that uses WebSphere Application Server
administration and monitoring interfaces to extract and display performance data. Using
the PerfServlet is not intended for real-time performance monitoring in production
environments or for use in large topologies. For these environments, you might use the
Tivoli Performance Viewer or IBM Tivoli Composite Application Manager for WebSphere
Application Server.
Specific tips for the PerfServlet include the following practices:
• PerfServlet resource usage: The PerfServlet is not designed to run concurrently.
Being a single threaded servlet, it would collect the data sequentially from available
servers. This single threaded operation can cause higher response times when the
PerfServlet is used in larger deployments.

Student Notebook
• PerfServlet in large deployments: By default, when the PerfServlet is first initialized, it

retrieves the list of nodes and servers within the cell in which it is deployed. Because
collecting this data requires system processing time, the PerfServlet holds this
information as a cached list. To force the servlet to refresh its configuration, you can use
the option "refreshconfig=true". However, using this option is not suggested unless
required because this option adds extra resource usage to the PerfServlet processing.
Use option, node, and server, if you are looking for performance data of a specific
server.
• PerfServlet response time: How responsive the PerfServlet is depends on the
following factors: numbers of application servers that exist in the cell and number of
resources that are configured in the cell (including applications).
• PerfServlet alternative: If you are looking for an alternative to using the PerfServlet to
capture data programmatically, see the Perf MBean programming interfaces
documentation. The documentation can be found under the Reference >
Programming Interfaces > MBean interfaces section of the WebSphere Application
Server Information Center.
V8.1
Student Notebook
Uempty 20.2.Request metrics

Student Notebook
Request metrics

Figure 20-26. Request metrics WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Request metrics (RM) overview

• Tracing facility that allows you to measure the amount of time a request
spends in each component that is traversed during its execution
• Captured information includes:
– Elapsed time in the web server
– Response time of invoked components in the web and EJB containers
– Response time of related JDBC calls
• Writes trace records to SystemOut.log or sends metrics to an
Application Response Measurement (ARM) agent
Request
Web correlator Web correlator EJB JDBC call
IP or URL server container container
filter
Entry or exit Entry or exit correlator
RM in plug-in RM in application server

DB
Log ARM Log ARM
Tivoli or third-party monitoring tools © Copyright IBM Corporation 2013
Figure 20-27. Request metrics (RM) overview WA855 / VA8551.0
Notes:
Request metrics allow you to monitor the transaction flow and analyze the response time of
the components that are involved in processing it. This analysis can help you target
performance problem areas and debug resource constraint problems. For example, it can
help determine whether a transaction spends most of its time in the web server plug-in, the
web container, the Enterprise JavaBeans (EJB) container, or the back-end database. The
response time that is collected for each level includes the time that is spent at that level and
the time that is spent in the lower levels. For example, if the total response time for the
servlet is 130 milliseconds, and it includes 38 milliseconds from the enterprise beans and
JDBC calls, then 92 ms can be attributed to the servlet process.
An ARM agent is not included with WebSphere Application Server, but third-party tools can
provide it.

Student Notebook
Enabling request metrics collection

1
Check to enable
2
Select components Configure filters
3
Select trace level
Note: an ARM agent
4 does not ship with
WebSphere
Choose output
Application Server,
method and third-party
tools supply it
Figure 20-28. Enabling request metrics collection WA855 / VA8551.0
Notes:
In the administrative console, select Monitoring and Tuning > Request Metrics and
select the check box to Prepare Servers for Request metrics collection.
Trace level specifies how much trace data to accumulate for a particular transaction.
Trace level and Components to be instrumented work together to control whether a
request is instrumented or not. The trace level can be set to one of the following values:
• None: No instrumentation.
• Hops: Generates instrumentation information about process boundaries only. When
this setting is selected, you see the data at the application server level, not the level of
individual components such as enterprise beans or servlets.
• Performance_debug: Generates the data at Hops level and the first level of the
intra-process servlet and Enterprise JavaBeans (EJB) call (for example, when an
inbound servlet forwards to a servlet and an inbound EJB calls another EJB). Other
intra-process calls like naming and service integration bus (SIB) are not enabled at this
level.
V8.1
Student Notebook
Uempty • Debug: Provides detailed instrumentation data, including response times for all
intra-process calls. Note: Requests to servlet filters are only instrumented at this level.
• Standard logs: Enables the request metrics logging feature. Select this check box to
trigger the generation of request metrics logs in the SystemOut.log file. Note: Since
enabling the request metrics logging feature increases processor usage, it is suggested
to use this feature together with filters so that only selected requests are instrumented.
• Application Response Measurement (ARM) agent: Allows request metrics to call an
underlying Application Response Measurement (ARM) agent. Before enabling ARM,
you must install an ARM agent and configure it to the appropriate class path and path,
following the instructions of the ARM provider.

Student Notebook
Isolating performance for specific types of requests

• Click Monitoring and Tuning > Request Metrics > Filters
• Select a filter type (for example, SOURCE_IP)
• Assign filter values
Check to
enable
Click to
assign value
2
Figure 20-29. Isolating performance for specific types of requests WA855 / VA8551.0
Notes:
The request metrics filters are enabled according to your configuration. For example, if you
enabled source IP, only requests whose source IP matches the one specified in the filter
are instrumented.
Note: Filters are only checked for edge transactions. An edge transaction is the transaction
that first enters an instrumented system. For example, if a servlet calls an Enterprise
JavaBeans component, the servlet is the edge transaction. The servlet must not be
instrumented at the web server plug-in, and the URI and SOURCE_IP filters must be
checked for the servlet request. However, when the request comes to the EJB container,
the EJB filter is not checked because it is no longer an edge transaction.
You must regenerate the web server plug-in configuration file after modifying the request
metrics configuration.
V8.1
Student Notebook
Uempty
Example request metrics data

• Request metrics data from a SystemOut.log file
Figure 20-30. Example request metrics data WA855 / VA8551.0
Notes:
The example of request metrics data that is shown on this slide detail the use of the
prepared statement cache to make an SQL call. You can trace the steps that are involved
and timings for this database transaction.

Student Notebook
V8.1
Student Notebook
Uempty 20.3.Performance advisors

Student Notebook
Performance advisors

Figure 20-31. Performance advisors WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Performance advisors overview

• WebSphere provides two separate advisors:
– Performance and Diagnostic Advisor – disabled by default
– Tivoli Performance Viewer Advisor
• Both provide configuration advice that is based on collected PMI data

on a per server basis
– Advisors do not compare counters among different application servers
• Provides advice that is based on basic rules for tuning WebSphere

Application Server
– Rules are IBM-defined and nonconfigurable
• Advisors do not automatically tune WebSphere based on advice

– Administrator must manually apply recommendations
– Suggested settings must be checked against baseline performance to verify
improvement: tune, test, monitor
Figure 20-32. Performance advisors overview WA855 / VA8551.0
Notes:
The advisors provide advice on the following application server resources: thread pools,
persisted session sizes, cache sizes, and JVM heap size.
For example, consider the data source statement cache. It optimizes the processing of
prepared statements and callable statements by caching those statements that are not
used in an active connection. (Both statements are SQL statements that essentially run
repeatable tasks without the costs of repeated compilation.) If the cache is full, an old entry
in the cache is discarded to make room for the new one. The best performance is generally
obtained when the cache is large enough to hold all of the statements that are used in the
application. The PMI counter, prepared statement cache discards, indicates the number of
statements that are discarded from the cache.
The performance advisors check this counter and provide recommendations to minimize
the cache discards. Another example is thread or connection pooling. The idea behind
pooling is to use an existing thread or connection from the pool instead of creating an
instance for each request. Because each thread or connection in the pool consumes
memory and increases the context-switching cost, the pool size is an important

Student Notebook
configuration parameter. A pool that is too large can hurt performance as much as a pool
that is too small. The performance advisors use PMI information about current pool usage,
minimum or maximum pool size, and the application server processor utilization to suggest
efficient values for the pool sizes.
The advisors can also issue diagnostic advice to help in problem determination and health
monitoring. For example, if your application requires more memory than is available, the
diagnostic adviser tells you to increase the size of the heap for the application server.
V8.1
Student Notebook
Uempty
Performance and Diagnostic Advisor (1 of 5)

• Performance advice:
– Object Request Broker (ORB) service thread pools
– Web container thread pools
– Connection pool size
– Persisted session size and time
– Prepared statement cache size
– Session cache size
– Memory leak detection
• Diagnostic advice:
– Connection factory
diagnostic messages
– Data source diagnostic messages
• Connection usage diagnostic messages

– Detection of connection use by multiple threads
– Detection of connection use across components
Figure 20-33. Performance and Diagnostic Advisor (1 of 5) WA855 / VA8551.0
Notes:
The Performance and Diagnostic Advisor runs in the Java virtual machine (JVM) process
of the application server; therefore, the performance cost is minimal.
To access the Performance and Diagnostic Advisor Configuration, click Servers > Server
Types > WebSphere application servers > server_name > Performance and
Diagnostic Advisor Configuration.

Student Notebook

• Click Servers > Server Types > WebSphere application servers >
server_name > Performance and Diagnostic Advisor
• Run the Performance and Diagnostic

Advisor in the production simulation and
test environment
• Performance advice is most applicable
during peak load, when the processor
utilization is high
Notes:
The Performance and Diagnostic Advisor analyzes PMI data and receives notifications
about performance and diagnostic information from components. Use this page to specify
settings for the Performance and Diagnostic Advisor. Performance issues can be related to
memory leaks in the system. Use the Memory Dump Diagnostic for Java tool, a separate
memory leak analysis utility, for detecting memory leaks.
The Performance and Diagnostic Advisor Framework is disabled by default. Each time that
you enable it for an application server, you see the warning message:
Run the Performance and Diagnostic Advisor in the Production Simulation and Test
environment. Performance advice is most applicable during peak load, when the processor
utilization is high.
V8.1
Student Notebook
Uempty

• Advisor configuration panel (on both configuration and runtime tabs)
• Select advice and click Start or Stop
Notes:
Advice type categorizes the primary indent of a piece of Advice.
Use Advice type for grouping, and then enable or disable sets of advice that is based on
your performance goal. Advice has the following types:
• Performance: Performance advice provides tuning recommendations, or identifies
problems with your configuration from a performance perspective.
• Diagnostic: Diagnostic advice provides automated logic and analysis that relates to
problem identification and analysis. These types of advice are issued when the
application server encounters unexpected circumstances.
Performance impact generalizes the negative effect on performance that an alert might
incur.
The performance impact of a particular piece of advice is highly dependent upon the
scenario that is run and upon the conditions that are met. The performance categorization
of alerts is based on worst case scenario measurements. The performance categorizations
are:

Student Notebook
• Low: Advice has minimal negative effect on performance. Advice might be run in test
and production environments. Cumulative negative effect on performance is within
run-to-run variance when all advice of this type is enabled.
• Medium: Advice has measurable but low negative effect on performance. Advice might
be run within test environments, and might be run within production environments if
deemed necessary. Cumulative negative effect on performance is less than 4% when
all advice of this type is enabled.
• High: Advice impact is high or unknown. Advice might be run during problem
determination tests and functional tests. It is not run in production simulation or
production environments unless deemed necessary. Cumulative negative effect on
performance might be significant when all advice of this type is enabled.
V8.1
Student Notebook
Uempty

• Tuning advice can be viewed in Runtime Events
• Click any TUNE message link for details
Notes:
Tuning advice is provided as messages written to the runtime events. The TUNExxxx
messages are typically at the Warning level.
Examples:
TUNE0201W: The rate of discards from the prepared statement cache is high. Increase the
size of the prepared statement cache for the data source.
TUNE0207W: Utilization of the connection pool is high. Performance might be improved by
increasing the maxPoolSize for data source {DS_name}. Try setting the minimum size to
{value}, and the maximum size to {value}.
TUNE0220W: The Java virtual machine is spending a considerable amount of time in
garbage collection. Consider increasing the heap size.
A complete list is available in the WebSphere Application Server V8 Information Center
under Reference > Messages > TUNE.

Student Notebook
Notes:
The message is:
TUNE9001W: Heap utilization patterns indicate that you might have a memory
leak. Additional explanatory data follows. Data values for free memory
between 8/9/11 11:44 AM and 8/9/11 11:46 AM were consistently less than the
minimum required percentage.
Explanation: Over time the amount of free memory seems to be decreasing or there is
consistently insufficient free memory in the heap, indicating that you might have a memory
leak.
User action: Use tools to further analyze your memory usage over time. For more
information about diagnosing out-of-memory errors and Java heap memory leaks, see the
information center.
V8.1
Student Notebook
Uempty
Tivoli Performance Viewer advisor

• Performance advice:
– ORB service thread pools
– Web container thread pools
– Connection pool size
– Persisted session size and time
– Prepared statement cache size
– Session cache size
– Dynamic cache size
– Java virtual machine (JVM) heap size
– DB2 Performance Configuration wizard
Figure 20-38. Tivoli Performance Viewer advisor WA855 / VA8551.0
Notes:
The performance advisor in Tivoli Performance Viewer provides advice on using collected
Performance Monitoring Infrastructure (PMI) data to help tune systems for optimal
performance and provide recommendations on inefficient settings. Obtain the advice by
selecting the performance advisor in Tivoli Performance Viewer.
In a Network Deployment environment, the performance advisor in Tivoli Performance
Viewer runs within the JVM of the node agent and can provide advice on resources that are
more expensive to monitor and analyze. In a stand-alone application server environment,
the performance advisor in Tivoli Performance Viewer runs within the application server
JVM. The Tivoli Performance Viewer advisor requires that you enable performance
modules, counters, or both.

Student Notebook
Examples of performance advice

• Data sources
– Situation: The prepared statement discard rate is too high, and heap space is
available
– Advice provided: Increase statement cache size
• Thread pools (ORB, web container, data source)
– Situation: The number of connections is low (at the minimum)
– Advice provided: Decrease pool size
– Situation: All data source connections are heavily used, and heap space is
available
– Advice provided: Increase maximum pool size
– Situation: The size of the pool is fluctuating a lot (high variance), possibly
indicating batch processing, and wasted resources
– Advice provided: Decrease pool size
• JVM heap size
– Situation: Heap size is too small (less than 256 MB)
– Advice provided: Increase the heap size to a value greater than 256 MB
Figure 20-39. Examples of performance advice WA855 / VA8551.0
Notes:
More examples of advice that the performance advisors would give in certain situations
include:
Unbounded thread pools
• Situation: Threads added to an unbounded pool are not pooled
• Advice: If the average number of threads is higher than the pool size, then the pool
must be increased to allow better pooling
Sessions
• Situation: Read/write time or size is too large
• Advice: Warn of application problem
• Situation: The number of live sessions is greater than the session cache, and memory
is available
• Advice: Increase session cache
V8.1
Student Notebook
Uempty • Situation: Requests are turned down because there is no room for new sessions
• Advice: There are either too many active sessions, or the cache size is too small
DB2 Performance Configuration wizard
• Situation: A DB2 database is detected in the configuration
• Advice: Use the DB2 Performance wizard to tune the indicated database

Student Notebook
Viewing performance advice

• In Tivoli Performance Viewer, click
the Advisor link
• From the list of messages, click a 1
link to see more detail
– Messages can be sorted by severity
Figure 20-40. Viewing performance advice WA855 / VA8551.0
Notes:
To view advice messages in Tivoli Performance Viewer, click the Advisor link.
From the list of messages, click a link to see more detail.
V8.1
Student Notebook
Uempty
Performance advice detail
Figure 20-41. Performance advice detail WA855 / VA8551.0
Notes:
In this example, the message suggests enabling servlet caching for better performance.
Servlet caching is a web container setting that is disabled by default. The User Action
section in the advice details provides instructions for enabling servlet caching.

Student Notebook
Performance advisor suggested practices

• Use only during stable production load tests
– Application must remain stable during production tests
– Any exceptions and deadlock issues must be resolved before running
– The test load must be consistent
– Varied load might lead to contradictory advice
• Enable after production load tests reach peak load levels

– Exclude ramp-up and ramp-down times from monitoring
– Increasing or decreasing loads might lead to contradictory advice
– Certain types of advice are only generated when processor is being stressed
(processor use > 50%)
• Important: tune your application before you tune WebSphere
Figure 20-42. Performance advisor suggested practices WA855 / VA8551.0
Notes:
When using the performance advisors, processor utilization must rise above 50% before
advice is generated. Typically when running your production level load, you push the
processor usage to 80–100% before turning on one of the performance advisors.
Consider the following when using a performance advisor for tuning:
If the load changes on the system under test, contradictory advice is generated. This
behavior is because the collected PMI data shows a different type of environment, causing
the advice to shift. To avoid this situation, always run the advisors while simulating the load
WebSphere experiences during deployment (peak load).
If the pool size minimum and maximum values are the same, the performance advisor rules
are much more likely to give contradictory advice when load fluctuates.
The amount of processor usage determines the amount of system activity. The advisors do
not consider disk activity, network activity, memory usage, or other factors to get a more
realistic view of system load.
Recommendations are only generated when processor load reaches 50% and higher.
V8.1
Student Notebook
Uempty Performance advisors from different application servers might give contradictory advice on
the same node resources. This behavior is because the application servers take into
account only how they are individually employing the resource. In this situation, if the
advice from the different advisors varies greatly, consider the generated advice and decide
what changes to make. However, if all advisors are giving the same recommendations,
then you must seriously consider the suggested changes.
If the performance advisor suggests setting a pool size to X, you must set the minimum
value to X/2 and the maximum value to X.
If the performance advisor suggests setting the prepared statement cache value to a
certain setting, check the amount of memory that is available before setting. The advisors
do not take into account the amount of actual physical memory available on the system.

Student Notebook
V8.1
Student Notebook
Uempty 20.4.IBM Tivoli Composite Application Manager for WebSphere

Application Server

Student Notebook
IBM Tivoli Composite

Application Manager for
Server

Notes:
V8.1
Student Notebook
Uempty
IBM Tivoli Composite Application Manager

• IBM Tivoli Composite Application Manager provides a suite of products
for managing and monitoring applications
– IBM Tivoli Composite Application Manager for CICS Transactions
– IBM Tivoli Composite Application Manager for IMS Transactions
– IBM Tivoli Composite Application Manager for J2EE
– IBM Tivoli Composite Application Manager for Application Diagnostics
• With IBM Tivoli Composite Application Manager for Application

Diagnostics, users can view the health of web applications and servers
– Drill down to diagnostic information for specific application requests to identify
the root cause of problems
• IBM Tivoli Composite Application Manager provides several data

collectors for different servers, including
– WebSphere Application Server
– WebSphere Application Server Community Edition
– WebSphere Process Server
– WebSphere ESB Server
– WebSphere Portal Server
Figure 20-44. IBM Tivoli Composite Application Manager WA855 / VA8551.0
Notes:
IBM Tivoli Composite Application Manager for Application Diagnostics gives users the
ability to view the health of web applications and servers; then drill down to diagnostic
information for specific application requests to identify the root cause of problems. Some of
the features of IBM Tivoli Composite Application Manager for Application Diagnostics
include:
• Analyze application performance through trending or historical analysis
• Provides key performance metrics to IBM Tivoli Composite Application Manager for
Transactions to sense and isolate potential problems
• View all Java EE transactions that are “in-flight” to uncover the root cause of
bottlenecks and do detailed memory analysis
• Correlates and profiles transactions that span multiple subsystems such as IBM CICS
and IMS
• Software consistency checker compares key system and JVM metrics on working and
non-working systems to help isolate differences that might be causing problems

Student Notebook
• Exchange information with IBM Rational Performance Tester so developers understand

the performance of applications in test or production
V8.1
Student Notebook
Uempty

Application Server
• Data collector available in WebSphere Application Server V8.5 as an
extension offering (optional download and installation)
Server is a separate installation
– Installed by using the IBM Installation Manager
– Configure one or more servers for data collection
• The IBM Tivoli Composite Application Manager for WebSphere
Application Server link shows up on the PMI configuration page
Notes:
IBM Tivoli Composite Application Manager is enhanced in version 8.0 and can be installed
together with the application server. This integrated monitoring tool allows you to view the
health of web applications and servers, and drill down to diagnostic information for specific
application requests to identify the root cause of problems.
IBM Tivoli Composite Application Manager for WebSphere Application Server can be
configured per server by selecting Monitoring and Tuning > Performance Monitoring
Infrastructure > server_name.
The server must be configured with the IBM Tivoli Composite Application Manager GUI
before you can see the IBM Tivoli Composite Application Manager for WebSphere
Application Server link under Additional Properties on the PMI configuration tab of the
server.
Use this page to enable or disable the IBM Tivoli Composite Application Manager for
WebSphere Application Server Data Collector. Changes take effect after the server is
restarted.

Student Notebook
It is a simple upgrade from IBM Tivoli Composite Application Manager for WebSphere
Application Server to IBM Tivoli Composite Application Manager for Application
Diagnostics (no “rip and replace”). After the upgrade, IBM Tivoli Composite Application
Manager data is still visible in Tivoli Performance Viewer as well.
V8.1
Student Notebook
Uempty

Application Server
• Select Enable IBM Tivoli Composite Application Manager for
WebSphere Application Server Data Collector on the Configuration
tab
• On the Runtime tab, click Start Monitoring
Notes:
To see the IBM Tivoli Composite Application Manager modules and metrics in the Tivoli
Performance Viewer, you are required to enable it by selecting the check box on the
Configuration tab. The next step is to click Start Monitoring on the runtime tab.

Student Notebook
IBM Tivoli Composite Application Manager metrics in Tivoli

Performance Viewer
• View metrics in Tivoli Performance Viewer
– Select the ITCAM Application Performance module
– Select the application
Figure 20-47. IBM Tivoli Composite Application Manager metrics in Tivoli Performance Viewer WA855 / VA8551.0
Notes:
IBM Tivoli Composite Application Manager for WebSphere Application Server provides
more request-based response time and processor metrics.
Customer application code is not instrumented in any way.
V8.1
Student Notebook
Uempty
IBM Tivoli Composite Application Manager application metrics in

• Additional metrics for the ShoppingServlet
Figure 20-48. IBM Tivoli Composite Application Manager application metrics in Tivoli Performance Viewer WA855 / VA8551.0
Notes:
Several performance metrics are collected and displayed for each component of an
application. This screen capture shows the metrics for the PlantsByWebSphere shopping
servlet after a load test. Clicking or hovering over the question mark (?) for each metric
displays a description of the metric.

Student Notebook
Unit summary
resources
• Configure the Request Metrics tool to generate performance data about
the end-to-end request flow
Notes:
V8.1
Student Notebook
Uempty
1. What are the two performance data collection technologies in
WebSphere?
2. Which WebSphere performance tool allows you to monitor overall

system health?
3. True or False: The Performance Monitoring Infrastructure is enabled

by default.
4. True or False: The Tivoli Performance Viewer Advisor tool generates

tuning advice and automatically applies it to the environment.
Notes:
1. 
2. 
3. 
4.

Student Notebook
Checkpoint answers
1. What are the two performance data collection technologies in
WebSphere?
– The Performance Monitoring Infrastructure (PMI) and request metrics
provide the data collection mechanisms in WebSphere.
2. Which WebSphere performance tool allows you to monitor overall
system health?
– The Tivoli Performance Viewer allows you to monitor overall system
health.
3. True or False: The Performance Monitoring Infrastructure is enabled
by default.
– True. PMI is enabled by default.
4. True or False: The Tivoli Performance Viewer Advisor tool generates
tuning advice and automatically applies it to the environment.
– False. The performance advisor tools do not automatically tune the
environment. You must tune manually and test the effect of the
changes.
Notes:
V8.1
Student Notebook
Uempty
Exercise 16
Using the performance monitoring

tools

Notes:

Student Notebook
Exercise objectives
• Enable various levels of Performance Monitoring Infrastructure (PMI)
statistics for an application server
• Monitor an application server by using Tivoli Performance Viewer
• Configure user settings for Tivoli Performance Viewer
• Examine summary reports and performance modules in Tivoli
Performance Viewer
• View performance messages from the Tivoli Performance Viewer
Advisor
• Enable and configure the Request Metrics tool
• View Request Metrics messages in the standard logs of an application
server
• Configure IBM Tivoli Composite Application Manager for WebSphere
Application Server collector for an application server
• View IBM Tivoli Composite Application Manager application
performance statistics by using Tivoli Performance Viewer
Notes:
V8.1
Student Notebook
Uempty Unit 21. WebSphere Batch

This unit provides an overview of WebSphere Batch.

• Define WebSphere Batch
• Describe WebSphere Batch architecture and components
• Describe the basic programming model
• Explain Batch workflow
• Define new features in WebSphere Batch

References
index.jsp
© Copyright IBM Corp. 2013 Unit 21. WebSphere Batch 21-1

Student Notebook
Unit objectives
Notes:
V8.1
Student Notebook
Uempty
Topics
• Overview of WebSphere Batch
• Components
• Additional features
Notes:

Student Notebook
V8.1
Student Notebook
Uempty 21.1.Overview of WebSphere Batch

Student Notebook
Overview of WebSphere
Batch

Figure 21-3. Overview of WebSphere Batch WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
The challenge
• Application servers traditionally focused on transactional applications
– Applications typically are designed to handle large volumes of relatively small
tasks
– Not all applications fit this type of design
• There is little support for long-running applications in an application

server
– Administrator must see and manage units of work
– Submission and execution must be asynchronous
• There is a need to run long-running applications and transactional work

within different processors to take advantage of the free cycles
Figure 21-4. The challenge WA855 / VA8551.0
Notes:
WebSphere Application Server and Java Platform, Enterprise Edition servers in general are
classically focused on lightweight transactional work. Typically, an individual request can
be handled in a few seconds of processor time and relatively small amounts of memory.
However, other styles of long-running applications require more resources and different
types of support from the runtime environment. Compute grid provides support within
WebSphere Application Server for long-running applications. Within an enterprise
environment, it is usually preferable to run long-running and transactional work on separate
processors, since running them within the same processor can negatively affect
performance for the application. Long-running work might take hours or even days to
complete and consume large amounts of memory or processing power while it runs.
Compute grid provides the capability to deploy different types of applications within your
environment, and can balance the work that is based on policy information.

Student Notebook
Introduction to WebSphere Batch

• A batch technology that is optimized for Java
– Basic functions are delivered in WebSphere Application Server
• Addresses need for long-running, resource-intensive work that does

not fit the transactional paradigm
– Traditional J2EE model is transactional, short lived, lightweight units of work
– Long-running work might take hours, or even days, to complete and use large
amounts of memory or processing power while it runs
• Accommodates applications that must complete long-running work

alongside transactional applications
Figure 21-5. Introduction to WebSphere Batch WA855 / VA8551.0
Notes:
Batch applications are designed to run long and complex transaction processing that
typically runs computationally intensive work. This type of processing requires more
resources than traditional online transactional processing (OLTP) systems. Batch
applications run as background jobs described by a job control language, and use a
processing model that is based on submit, work, and result actions. The execution of batch
processes can take hours, and the tasks are typically transactional, involving multi-step
processes.
V8.1
Student Notebook
Uempty
Key features
• Unified batch architecture provides a consistent programming model
and operations model
• Comprehensive batch solution that allows for end-to-end development

tools and execution infrastructure
• A resilient, highly available, secure, and scalable run time container-

managed services for batch applications
• A platform that supports continuous batch and OLTP processing and

parallel computing on highly virtualized and cloud-based run times
• Integration capability with existing infrastructure processes, such as

enterprise schedulers
Figure 21-6. Key features WA855 / VA8551.0
Notes:
WebSphere Application Server V8.5 with WebSphere Batch supplies a unified batch
architecture. Using XML Job Control Language (xJCL), WebSphere Batch provides
consistent programming and operational models. WebSphere Batch uses a batch
technology that is optimized for Java and supports long-running applications, which ensure
agility, scalability, and cost efficiency for enterprises.

Student Notebook
V8.1
Student Notebook
Uempty 21.2.Components

Student Notebook
Components

Figure 21-7. Components WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
WebSphere Batch components (1 of 2)

• Batch jobs
– Series of definitions that direct the execution of one or more batch applications,
and specifies their input and output
• Batch container
– Provides the batch execution environment, including services such as checkpoint
and restart and job-logging
• Job scheduler
– Job management control point for determining when and where jobs run
• Batch toolkit
– Provides tools for the creating, packaging, and testing batch jobs
• Endpoints
– Application servers that are augmented for running batch applications
Figure 21-8. WebSphere Batch components (1 of 2) WA855 / VA8551.0
Notes:
A batch job consists of a series of definitions that direct the execution of one or more batch
applications, and specifies their input and output. A batch job processes a specific set of
tasks in a predefined sequence to accomplish specific business functions. Batch job
workloads are executed in a batch container in WebSphere Application Server
environments. This batch container is the main engine responsible for the execution of
batch applications. It runs batch jobs under the control of an asynchronous bean, which
can be thought of as a container-managed thread. The batch container ultimately
processes job definitions and carries out the lifecycle of jobs.
The grid endpoints are application servers that are augmented to provide a special runtime
environment that batch applications need. A product-provided Java EE application, the
batch execution environment, provides this runtime environment. The system deploys this
application automatically when a batch application is installed, and it serves as an interface
between the job scheduler and batch applications. It provides the runtime environment for
both compute-intensive and transactional batch applications.

Student Notebook
WebSphere Batch components (2 of 2)

• Interfaces
– Console, command-line, and programmatic for interacting with job scheduler
• XML job control language (xJCL)

– Identifies the batch application to run
– Batch database
– Required by the job scheduler and batch container
• Parallel Job Manager

– Controls parallel job execution which includes splitting and merging of jobs
• Enterprise connectors
– Enables integration to external products for scheduling (such as Tivoli Workload
Scheduler) and monitoring (such as IBM Tivoli Composite Application Manager)
batch workloads
Figure 21-9. WebSphere Batch components (2 of 2) WA855 / VA8551.0
Notes:
An XML dialect called XML Job Control Language (xJCL) is used to describe jobs. This
dialect has constructs for expressing all of the information that is needed for both
compute-intensive and batch jobs, although some elements of xJCL are applicable only to
compute-intensive or batch jobs. The job description identifies which application to run and
its input and output. The xJCL definition of a job is not part of the batch application. This
definition is constructed separately and submitted to the job scheduler to run. The job
scheduler uses information in the xJCL to determine where and when the job runs.
The batch container uses a relational database to store checkpoint information for
transactional batch applications. The database can be any supported WebSphere
Application Server relational database and is accessed by using JDBC. If the batch
container is clustered, the database must be a network database, such as DB2.
V8.1
Student Notebook
Uempty
Batch container
• Batch applications run under the control of the batch controller bean
– It processes the job definition and carries it from start to finish
Java virtual machine Job steps

Data access
xJCL BATCH container Checkpoints
Results
Batch Batch
controller app
IBM batch
container classes

Foundation services level
Figure 21-10. Batch container WA855 / VA8551.0
Notes:
The batch container is the heart of the batch application support that is provided in
WebSphere Application Server. It runs a batch job under the control of an asynchronous
bean, which can be thought of as a container-managed thread. The batch container
ultimately processes a job definition and carries out the lifecycle of a job.
The batch container provides these services:
• Check pointing, which involves resuming batch work from a selected position
• Result processing, which involves intercepting and processing step and job return
codes
• Batch data stream management, which involves reading, positioning, and repositioning
data streams to files, relational databases, native z/OS data sets, and many other
different types of input and output resources

Student Notebook
Batch programming model
Batch container
Batch controller bean Job control

Part of the Batch container (xJCL)
code supplied by IBM
Job step control Batch App

Invoking and coordinating POJO
processing between steps
Step 1
Batch data streams Step 2

Provides data input and output Development
services for the job steps libraries
Step n or Eclipse
Checkpoint algorithms
Service to programmatically
determine and handle
checkpointing
Results and return codes WebSphere Application Server

Services to determine, manipulate runtime interfaces
and act upon return codes, both at JDBC, JCA, security, transaction,
the application and system levels logging, deployment, and so forth
Figure 21-11. Batch programming model WA855 / VA8551.0
Notes:
The batch programming model consists of four principal interfaces, two of which are
essential to building a batch application, and two that are optional and intended for
advanced scenarios.
The first essential item is the batch job step, which defines the interaction between the
batch container and the batch application. The other essential item is the batch data
stream. The batch data stream abstracts a particular input source or output destination for
a batch application and defines the interaction between the batch container and a concrete
BatchDataStream implementation.
An optional checkpoint policy algorithm defines the interaction between the batch container
and a custom checkpoint policy implementation. A checkpoint policy is used to determine
when the batch container will checkpoint a running batch job to enable a restart to occur
after a planned or unplanned interruption.
WebSphere Application Server includes two ready-to-use checkpoint policies. An optional
results algorithm defines the interaction between the batch container and a custom results
algorithm. The purpose of the results algorithm is to provide the overall return code for a
V8.1
Student Notebook
Uempty job. The algorithm has visibility to the return codes from each of the job steps. WebSphere
Application Server includes one ready-to-use results algorithm.

Student Notebook
WebSphere Batch environment
Figure 21-12. WebSphere Batch environment WA855 / VA8551.0
Notes:
The job scheduler provides the job management functions such as submit, cancel, and
restart. It maintains a history of all job activity, including waiting jobs, running jobs, and
completed jobs. The job scheduler is hosted in a WebSphere Application Server or a server
cluster.
Jobs are described by using a job control language called XML Job Control Language
(xJCL), which identifies the batch application to run and the inputs and outputs. The batch
container provides the execution environment for batch jobs. There can be multiple batch
containers in a WebSphere cell. Batch applications are regular WebSphere Java Enterprise
Edition (Java EE) applications, which are deployed as enterprise archive (EAR) files.
V8.1
Student Notebook
Uempty
Main concepts of batch processing

• Batch components support the following long running workloads or
jobs:
– Batch applications
– Compute-intensive applications
• Batch applications
– Completes large amounts of work that are based on repetitive tasks
– Application provides process-one-record logic while container provides iteration
– Container provides transactions, checkpoint, and restart mechanisms
• Compute-intensive applications
– Completes work that requires large amounts of system resources, such as
processor and memory
– Application provides all the logic for performing, including getting the needed
resources
– Container has limited contact with work after it is started
Figure 21-13. Main concepts of batch processing WA855 / VA8551.0
Notes:
WebSphere runs batch applications that are written in Java and implement a WebSphere
batch programming model. They are packed as EAR files and are deployed to the batch
container hosted in an application server or cluster. Batch applications are executed
non-interactively in the background.

Student Notebook
The WebSphere Batch workflow

1. A user requests that a job is 4. The job is dispatched to a capable
submitted endpoint
2. Job is submitted in the form of 5. Batch endpoint begins execution

a job control definition with the invocation of the async
controller bean
3. The scheduler analyzes the 6. Your batch application is called
request
Job submitter Services

Batch
Batch
Batch container
dispatcher Batch
Batch
Job submitter repository
Batch
Figure 21-14. The WebSphere Batch workflow WA855 / VA8551.0
Notes:
Batch jobs are submitted to the system by using the Job Management Console or
programmatically by way of Enterprise JavaBeans (EJB), Java Message Service (JMS), or
web services. Each job is submitted in the form of an XML Job Control Language (xJCL)
document. The Job Dispatcher then selects the best endpoint application server for job
execution, which is based on several different metrics. The endpoint application server sets
up the jobs in the batch container and executes the batch steps that are based on the
definitions in xJCL. While the job is running, the Job Dispatcher aggregates job logs and
provides lifecycle management functions such as start, stop, and cancel.
V8.1
Student Notebook
Uempty 21.3.Additional features

Student Notebook
Additional features

Figure 21-15. Additional features WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Parallel batch
• Container-managed parallelization
• Parallel Job Manager decomposes a JVM

large work request into many smaller
work requests (subjobs)
Batch WebSphere JVM

job Batch
scheduler
...
• Divide and conquer approach
improves elapsed time
• Administrator manages only the top- JVM

level job and the Parallel Job Manager
manages the subjobs
Figure 21-16. Parallel batch WA855 / VA8551.0
Notes:
The Parallel Job Manager provides support for building transactional batch applications as
a job, and then divides the job into subordinate jobs. The subordinate jobs can run
independently and in parallel. The Parallel Job Manager is used to submit and manage the
transactional batch jobs.
The Batch programming model is updated to provide APIs for the Parallel Job Manager.
The purpose of the Parameterized API is to divide the top-level job into multiple subjobs.
The Parameterized API determines the number of subjobs to create, and the input
properties that are passed to each subjob.
WebSphere Batch allows the running of parallel jobs and their subjobs in the same JVM if
needed. This capability is especially useful when subjobs are typically short in duration,
and the process of distributing the subjobs across servers is much larger compared to the
actual work completed.

Student Notebook
Enterprise integration
• WebSphere includes a special connector for Tivoli Workload Scheduler and
competing workload schedulers
• Tivoli Workload Scheduler and Batch is a common deployment pattern
• Puts WebSphere Batch under full control of enterprise workload scheduler
Batch
Tivoli
Workload
Scheduler WebSphere Application Server Application Server
Java virtual machine

Java virtual machine
Batch Batch
Workload
connector scheduler container
Figure 21-17. Enterprise integration WA855 / VA8551.0
Notes:
WebSphere Application Server V8.5 Batch provides an integration capability with external
workload schedulers, such as Tivoli Workload Scheduler. An integration layer that is known
as WSGrid enables Tivoli Workload Scheduler (and similar products) to dispatch and
monitor batch activities.
Tivoli Workload Scheduler helps you establish an enterprise workload automation
backbone by driving composite workloads according to business policies. It provides
automation capabilities to control the processing of a production workload for an enterprise,
including batch and online services. Tivoli Workload Scheduler functions as an automatic
driver for composite workloads. It extends the scope for integrated applications and
systems management by driving workloads on multiple, heterogeneous platforms and ERP
systems.
For more information about IBM Tivoli Workload Scheduler, see:
http://www.ibm.com/software/tivoli/products/scheduler/
V8.1
Student Notebook
Uempty
CommandRunner
• CommandRunner is a utility job step which allows shell command lines
to be run as job steps
– Includes shell commands, shell scripts, and compiled programs
– Runs the specified shell command line in an operating system process
– Standard output and standard error streams are captured and written to the job
log
• Syntax for the CommandRunner utility

<job-step
<job-step name={step_name}>
name={step_name}>
<classname>com.ibm.websphere.batch.utility.CommandRunner<
<classname>com.ibm.websphere.batch.utility.CommandRunner<
/classname>
/classname> {job_step_properties}
{job_step_properties} </job-step>
</job-step>
Figure 21-18. CommandRunner WA855 / VA8551.0
Notes:
The CommandRunner utility adds all job step properties, after substitution, to the process
variable pool for the process in which the specified command line runs.

Student Notebook
COBOL support
• Reuse COBOL modules in WebSphere applications

• Call standard COBOL modules from Java on same thread in
same process
– z/OS only
– Java and COBOL run in same transaction scope
• WebSphere managed DB2 connections shareable with
COBOL
Figure 21-19. COBOL support WA855 / VA8551.0
Notes:
COBOL was the prevalent language to run batch-style workloads in the past, and even
today there is a large existing base of COBOL code. On the z/OS platform, Java batch
adds support to easily call into existing COBOL assets to run modern batch workloads.
With WebSphere Application Server V8.5, COBOL support includes the following key
features:
• In z/OS, you can call standard COBOL modules from Java on the same thread in the
same process.
• Java and COBOL run in the same transaction scope.
• WebSphere managed DB2 connections are shareable with COBOL.
• You can use COBOL working storage isolation per job step or per remote call.
• IBM Rational Application Developer tools are available for Java call stub generation.
The new COBOL container allows COBOL modules to be loaded into the WebSphere
Application Server for z/OS address space and invoked directly. It provides the means of
V8.1
Student Notebook
Uempty direct integration of COBOL resources into WebSphere Java processing. The container
itself is implemented as a handful of DLL files and JAR files.

Student Notebook
Unit summary
Notes:
V8.1
Student Notebook
Uempty
1. (True or False) The job scheduler accepts job submissions and
determines where to run them.
2. What component identifies the batch application to run?

A. Job scheduler
B. Parallel job manager
C. XML job control language
3. (True or False) COBOL support allows for Java and COBOL to run
in the same transaction scope.
Notes:
1. 
2. 
3.

Student Notebook
Checkpoint answers
1. True.
2. C. XML job control language
3. True.
Notes:
V8.1
Student Notebook
Uempty Unit 22. Course summary

This unit summarizes the course, explains the class evaluation
process, and provides information for future study.

• Explain how the course met its learning objectives
• Submit an evaluation of the class
• Identify other WebSphere Education courses that are related to this
topic
• Access the WebSphere Education website
• Locate appropriate resources for further study
© Copyright IBM Corp. 2013 Unit 22. Course summary 22-1

Student Notebook
Unit objectives
topic
Notes:
V8.1
Student Notebook
Uempty
Course learning objectives (1 of 2)

• Relate WebSphere Application Server to the WebSphere family of
products
• Describe the features and standards in WebSphere Application Server
V8.5.5
• Describe the architectural concepts that are related to WebSphere
Application Server
• Install and configure WebSphere Application Server V8.5.5
• Install and configure IBM HTTP Server
• Assemble and install server-side Java enterprise applications
• Use WebSphere administrative tools to configure and manage
enterprise applications
• Use wsadmin scripting
• Configure WebSphere Application Server security
Figure 22-2. Course learning objectives (1 of 2) WA855 / VA8551.0
Notes:

Student Notebook
Course learning objectives (2 of 2)

• Deploy applications in clustered environments
• View performance information about server and application
components
• Use problem determination tools and log files to troubleshoot problems
• Configure messaging with the service integration bus
• Describe Intelligent Management features
• Describe WebSphere Batch features
• Describe the Liberty profile
• Install and configure the Liberty profile
Figure 22-3. Course learning objectives (2 of 2) WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
Class evaluation
• Your comments about this class are useful to WebSphere Education
• Feedback on the site, curriculum, and instructor tell WebSphere
Education what was good about the class and what can be improved
• Complete the course evaluation on the IBM Training website:
http://www.ibm.com/training/osart
Figure 22-4. Class evaluation WA855 / VA8551.0
Notes:

Student Notebook
To learn more about this subject

• WebSphere Education website:
www.ibm.com/websphere/education
• Training paths:
www.ibm.com/software/websphere/education/paths/
– Identify the next courses in this sequence
• Resource Guide
– Contains information about many useful sources of information
– Many of these sources are free
– See handout in your class materials, or download a copy
– www.ibm.com/developerworks/wikis/display/WEinstructors/
WebSphere+Resource+Guide
• Email address for more information:
[email protected]
• Education CD and documents in your class materials
Figure 22-5. To learn more about this subject WA855 / VA8551.0
Notes:
V8.1
Student Notebook
Uempty
References (1 of 3)
• Web pages
– WebSphere:
http://www.ibm.com/websphere
– Redbooks:
http://www.ibm.com/redbooks
– Education:
http://www.ibm.com/services/learning
– Training and certification:
http://www.ibm.com/developerworks/websphere/education/
Figure 22-6. References (1 of 3) WA855 / VA8551.0
Notes:

Student Notebook
References (2 of 3)
• JSR 244 is an “umbrella” specification that references other
specifications
– http://www.jcp.org/en/jsr/detail?id=244
• Get to know Java EE 5:

– http://www.ibm.com/developerworks/websphere/library/
techarticles/0707_barcia/0707_barcia.html
• Java EE 5: Power and productivity with less complexity

– http://www.ibm.com/developerworks/java/library/j-jee5/
• Introducing the Java EE 6 Platform

– http://www.oracle.com/technetwork/articles/javaee/
javaee6overview-141808.html
Notes:
V8.1
Student Notebook
Uempty
References (3 of 3)
• WebSphere Application Server V8.5 Concepts, Planning, and Design
Guide
– http://www.redbooks.ibm.com/abstracts/sg248022.html?Open
• WebSphere Application Server V8.5 Administration and Configuration

Guide
– http://www.redbooks.ibm.com/abstracts/sg248056.html?Open
• WebSphere Application Server Performance website

– http://www.ibm.com/software/webservers/appserv/was/
performance.html
• All SPEC jAppServer2004 results published by SPEC

– http://www.spec.org/jAppServer2004/results/
jAppServer2004.html
Notes:

Student Notebook
Unit summary
topic
Notes:
V8.1
Student Notebook
DHCP Dynamic Host Configuration Protocol

glos Glossary of DLL Dynamic Link Library
abbreviations and DMgr deployment manager
DMZ demilitarized zone
acronyms DN distinguished name
DNS Domain Name System
DRS data replication service
A DTD document type definition
AB ApacheBench DVD digital versatile disc
AFS Andrew File System
AIX Advanced IBM UNIX
AMI asynchronous message interface
E
EAR enterprise archive
Ant Another Neat Tool
EE Enterprise Edition
AOL America Online
EIS enterprise information system
APAR Authorized Program Analysis Report
EJB Enterprise JavaBean
API application programming interface
EJS Enterprise Java Services
ARFM application request flow manager
EL Expression Language
ARM Application Response Measurement
ENC Enterprise Naming Context
ASCII American Standard Code for Information
Interchange ERP enterprise resource planning
AST Application Server Toolkit ESB Enterprise service bus
ESI Edge Side Include
B
BSF Bean Scripting Framework F
FIPS Federal Information Processing Standard
FQDN fully qualified domain name
C FTP File transfer protocol
CA certificate authority
CICS Customer Information Control System
CIM centralized installation manager G
CIP custom installation package GA generally available
CMP container-managed persistence GB gigabyte
CMS Certificate Management System GC garbage collection
CMT Configuration Migration Tool GCD greatest common divisor
CN common name GCMV Garbage Collection and Memory Visualizer
COBOL Common Business-Oriented Language GIF Graphics Interchange Format
CORBA Common Object Request Broker GMT Greenwich Mean Time
Architecture GPS global positioning system
CP caching proxy GSS Generic Security Services
CPU central processing unit GTK GNU GUI Tool Kit
CSIv2 Common Secure Interoperability Protocol GUI graphical user interface
Version 2
CSS Cascading Style Sheets
H
HA high availability or highly available
D HACMP High-Availability Cluster Multi-Processing
DB database HAM high availability manager
DC domain controller HFS Hierarchical File System
DCS Distribution and Consistency Services HPEL High Performance Extensible Logging
DD deployment descriptor HPUX Hewlett Packard UNIX
© Copyright IBM Corp. 2013 Glossary of abbreviations and acronyms X-1

Student Notebook
HTML Hypertext Markup Language JMX Java Management Extensions

HTTP Hypertext Transfer Protocol JNDI Java Naming and Directory Interface
HTTPD HTTP Daemon JPA Java Persistence API
HTTPS HTTP over SSL JPG Graphics file type or extension (lossy
compressed 24 bit color image storage format
developed by the Joint Photographic Experts
I Group)
IADT IBM Assembly and Deploy Tools JRE Java Runtime Environment
IBM International Business Machines Corporation JSF JavaServer Faces
IDE integrated development environment JSP JavaServer Pages
IIOP Internet Inter-ORB Protocol JSR Java Specification Request
IMCL Installation Manager command-line JSTL JavaScript Tag Library
IMS Information Management System JTA Java Transaction API
I/O input/output JVM Java virtual machine
IP Internet Protocol
ISC Integrated Solutions Console K
IPSEC IP Security
ISMP InstallShield MultiPlatform
L
IT information technology
LAN Local area network
IVT Installation Verification Tool LB Load Balancer
LDAP Lightweight Directory Access Protocol
J LSD Location service daemon
J2C Java 2 Connector LTPA Lightweight Third Party Authentication
J2EE Java 2 Enterprise Edition
J2SE Java 2 Platform Standard Edition
M
JAAS Java Authentication and Authorization MAC message authentication code or media access
Service control
JACC Java Authorization Contract for Containers MAPs message addressing properties
Jacl Java Command Language
MDB message-driven bean
JAF Java Activation Framework
ME messaging engine
JAR Java archive MQ Message Queue
JASPIC Java Authentication Service Provider
Interface for Containers MQI Message Queue Interface
Java EE Java Platform, Enterprise Edition MVS Multiple Virtual System
JAXB Java Architecture for XML Binding
JAXP Java API for XML Processing N
JAXR Java API for XML Registries NAS network attached storage
JAX-RPC Java API for XML Remote Procedure NAT network address translation
Calls NIC network interface card
JAX-RS Java API for XML-based Remote NIM Network Installment Management
Procedure Calls
NTP Network Time Protocol
JAX-WS Java API for XML Web Services
JCA Java EE Connector Architecture
JCE Java Cryptology Extension O
ODR on demand router
JDBC Java Database Connectivity
OLTP online transaction processing
JDE JD Edwards
OOM OutOfMemory
JDK Java Development Kit
ORB Object Request Broker
JIT just-in-time
OS operating system
JMS Java Message Service
OVF Open Virtualization Format
X-2 WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
Student Notebook
P SCA Service Component Architecture

PAR Parchive Index File SCADA supervisory control and data acquisition
PBW PlantsByWebSphere SCM source code management
PCT Plug-ins Configuration Tool SDO Service Data Objects
PD problem determination SDK software development kit
PFBC properties file based configuration SDLC systems development lifecycle
PGP Pretty Good Privacy SFSB stateful session bean
PHD portable heap dump SIB or SIBus service integration bus
PHP personal home page SIP Session Initiation Protocol
PID process identifier SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
PKI public key infrastructure
SOA service-oriented architecture
PMAT Pattern Modeling and Analysis tool
SOAP A lightweight, XML-based protocol for
PME programming model extensions
exchanging information in a decentralized,
PMI Performance Monitoring Infrastructure distributed environment. Usage note: SOAP is not
PMR problem management record an acronym; it is a word in itself (formerly an
acronym for Simple Object Access Protocol)
PMT Program Management Tool
SPI service provider interface
POJO plain old Java object
SPNEGO Simple and Protected GSS-API
PWB PlantsByWebSphere Negotiation Mechanism
SPOF single point of failure
Q SQL Structured Query Language
QA quality assurance SSB stateful session bean
QoS quality of service SSL Secure Sockets Layer
SSO single sign-on
R StAX Streaming API for XML
RA registration authority SUSE Software und System Entwicklung (German:
Software and Systems Development)
RAM random access memory
SVC supervisor call
RAR resource archive
SVG Scalable Vector Graphics
RACF Resource Access Control Facility
SWAM Simple WebSphere Authentication
RAS reliability, availability, and serviceability Mechanism
RC return code
RDBMS relational database management system
RDN relative distinguished name
T
TCL Tool Command Language
REST Representational State Transfer
TCP/IP Transmission Control Protocol
RM request metrics
TCP/IP Transmission Control Protocol/Internet
RMI Remote Method Invocation Protocol
RMI/IIOP Remote Method Invocation Over Internet TKCARSI Toolkit for Custom and Reusable Solution
Inter-ORB Protocol Information
RUP Rational Unified Process TLS Transport Layer Security
RXA Remote Execution and Access TMDA Thread and Monitor Dump Analyzer
TP Trade Processor (application in lab exercises)
S TT Trade Ticker (application in lab exercises)
SAAJ SOAP with Attachments API for Java
SAF System Authorization Facility U
SAM Security Access Manager UDDI Universal Description, Discovery, and
SAR SIP application resource Integration
SAS Secure Association Service UI user interface
SBDT Smart Business Development and Test UNC Universal Naming Convention
© Copyright IBM Corp. 2013 Glossary of abbreviations and acronyms X-3

Student Notebook
UNIX Uniplexed Information and Computing System

UOW unit of work
URI Uniform Resource Identifier
URL Uniform Resource Locator
UTC Universal Test Client
V
VMM virtual member manager
VPN virtual private network
W
WAR web archive
WLM workload management
WS web services
WS-AT web services atomic transaction
WS-BA web services business activity
WS-COOR web services coordination
WSDL Web Services Description Language
WS-I Web Services Interoperability
WSIF Web Services Invocation Framework
X
XA Extended Architecture
XCT Cross-Component Trace
xJCL XML Job Control Language
XML Extensible Markup Language
XTP extreme transaction processing
Y
Z
zMMT z/OS Migration Management Tool
z/OS zSeries operating system
zPMT z/OS Profile Management Tool
X-4 WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013
V8.1
backpg
Back page

Wa8551 Va8551stud

Uploaded by

Copyright:

Available Formats

Wa8551 Va8551stud

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Wa8551 Va8551stud

Uploaded by

Copyright:

Available Formats

V8.

(Course code WA855 / VA855)

July 2013 edition

© Copyright International Business Machines Corporation 2013.

Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Unit 1. WebSphere product family overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Unit 2. WebSphere Application Server architecture – stand-alone . . . . . . . . . . . . . 2-1

© Copyright IBM Corp. 2013 Contents iii

WebSphere architecture runtime (3 of 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12

Unit 3. WebSphere Application Server architecture – federated. . . . . . . . . . . . . . . .3-1

iv WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

TOC Managing web servers with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Unit 4. IBM Installation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

© Copyright IBM Corp. 2013 Contents v

Modify (add or remove) features (4 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33

Unit 5. WebSphere Application Server installation . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

vi WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

TOC Starting the Profile Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

Unit 6. Web server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

© Copyright IBM Corp. 2013 Contents vii

6.2. Topic: WebSphere Customization Toolbox overview . . . . . . . . . . . . . . . . . . . . . . .6-17

Unit 7. WebSphere Application Server administrative console . . . . . . . . . . . . . . . .7-1

TOC Administrative console navigation tree (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Unit 8. Introduction to the PlantsByWebSphere application . . . . . . . . . . . . . . . . . . 8-1

Unit 9. Application assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

© Copyright IBM Corp. 2013 Contents ix

IBM Assembly and Deploy Tools tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15

Unit 10. Application installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

x WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

TOC Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Unit 11. Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

© Copyright IBM Corp. 2013 Contents xi

Server logs and diagnostic tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6

TOC IBM Support Assistant: Collect and send data . . . . . . . . . . . . . . . . . . . . . . . . . . 11-67

Unit 12. Introduction to wsadmin and scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

© Copyright IBM Corp. 2013 Contents xiii

Exercise objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-62

Unit 13. Federating a cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1

Unit 14. Workload management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1

TOC What is workload management (WLM)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7

© Copyright IBM Corp. 2013 Contents xv

Session configuration: Memory-to-memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-60

Unit 15. Introduction to WebSphere Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-1

TOC Messaging engine topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-45

Unit 16. Job manager and Centralized Installation Manager . . . . . . . . . . . . . . . . . 16-1

© Copyright IBM Corp. 2013 Contents xvii

Centralized Installation Manager (CIM) in the job manager . . . . . . . . . . . . . . . . .16-31

Unit 17. Overview of Intelligent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-1

TOC What is Application edition management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41

Unit 18. WebSphere security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

© Copyright IBM Corp. 2013 Contents xix

Custom registry: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-31

xx WebSphere Application Server V8.5.5 Administration © Copyright IBM Corp. 2013

TOC WebSphere SSL management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84

Unit 19. Overview of the Liberty profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

© Copyright IBM Corp. 2013 Contents xxi

19.3. Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-25

TOC Unit 20. Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

© Copyright IBM Corp. 2013 Contents xxiii