Profiles and Federating Cells
IBM Confidential
Unit Objectives •After completing this unit, you should be able to: –Describe WebSphere Application Server cell concepts –Describe the installation process for creating profiles –Verify the installation of profiles –Describe the directories and configuration files for WebSphere profiles –Add a WebSphere Application Server node to a cell –Explain the difference between managing a stand-alone server and a cell
WebSphere Cells •A WebSphere cell defines administrative domain –Available in WebSphere Application Server Network Deployment –Deployment manager provides centralized administration of all resources in the cell •Created as a profile
–Nodes run application components in application servers •WebSphere Application Server base nodes can be added to a cell Deployment Manager
Cell Node 1
Node 2 Node Agent
App Server
App Server
Node Agent
App Server
App Server
WebSphere Application Server Types •Application Server –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 –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
Network Deployment Concepts •A node is a logical grouping of servers – Each node is managed by a single node agent process – Each node is defined within a profile •A deployment manager (DMgr) process manages the node agents – Holds the configuration repository for the entire management domain, called a cell – Administrative service runs inside the DMgr – The deployment manager is defined within a profile
V6 Application Server
…
V6 Application Server
…
V6 Node
V6 Application Server
…
V6 Application Server
V6 Node
Cell
WebSphere Profiles Overview •WebSphere files are split into two components: –Product files •Set of shared read-only static files or product binaries shared by any functional instance of the WebSphere Application Server product
–Configuration files (profiles) •Set of user-customizable data files, called a profile •Files include: WebSphere configuration, installed applications, resource adapters, properties, log files, and so forth
WebSphere Product Files
Profiles -AppSrv01 -AppSrv02
. . .
WebSphere Profiles Benefits •Benefits of profiles in network deployment: –Think of profiles as representing a node •Can install multiple profiles on a single machine
–Each profile uses the same product files •Stand-alone Node • An application server profile that is not federated •Managed Node • A node that has been federated and therefore has a node agent •Deployment Manager • A node that runs the deployment manager process
WebSphere Profiles: Types •Profile types: define application server configuration Profile Types
V6 packages
Application Server (default)
All
Deployment Manager
Network Deployment
Create different instances of DMgr – each DMgr is its own cell
Custom (managed)
Network Deployment
Creates and federates a node containing no pre-defined application server definitions
WebSphere Install Product Binaries
+
WebSphere Profile 1
+
WebSphere Profile 2
Functions Create different instances of a stand-alone node – each standalone node has 1 application server
!
V6 Application OR Server
V6 Deployment Manager
OR
V6 Custom Profile (V6 Node)
!
V6 Application Server
V6 Deployment Manager
OR
V6 Custom Profile (V6 Node)
OR
Application Server Profile •Application Server profiles provide a base install –Application Server in the Network Deployment product can run in a deployment manager cell as a managed node or on its own as a stand-alone application server –Multiple application server profiles can be created on a single machine –Each application server profile can be federated into a cell •If there are multiple base profiles on a single machine, they can be federated into the same cell, different cells, or remain stand-alone.
Federated
Stand-alone V6 Application Server
V6 Application Server
V6 Node
…
V6 Application Server
V6 Node
Cell
Deployment Manager Profile •Used to create a deployment manager process (Dmgr) –Can exist on independent machine –Can exist on machine with other profiles –Provides centralized administration of managed application server nodes and custom nodes as a single cell –Provides clustering and caching support, including failover support and workload management
V6 Application Server
V6 Application Server
V6 Application Server
V6 Node
V6 Application Server
V6 Node
Cell
Custom Profile •A custom profile creates WebSphere node without any application –By default is automatically federated into a cell during profile creation –No application servers are created during profile creation –Use the deployment manager’s 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 V6 Application Server
V6 Application Server
V6 Node
V6 Node
Cell
Creating Profiles •WebSphere provide multiple ways of creating profiles – Profile Creation Wizard • Start menu (Windows only) • Launched after installation from install wizard • Launch via command line tool pctWindows • \bin\ProfileCreator directory • Similar command exists for UNIX platform • Wizard in First steps console
– Manually via the wasprofile command line tool • Create profiles in silent mode using wasprofile –silent option • Other wasprofile options include: -listProfiles –delete
Profile Creation Wizard (1 of 3) •The Profile Creation Wizard can be started a number of ways: –Through the WebSphere installation wizard –Through the Windows Start menu –Through the command line tools in the \bin\ProfileCreator directory
Profile Creation Wizard (2 of 3)
Profile Creation Wizard (3 of 3)
Profile Creation – Command Line Tool •The wasprofile script supports a number of functions including: – Creating a new stand-alone application server profile wasprofile –create -profileName -profilePath -templatePath -nodeName -cellName -hostname
–Listing all profiles
wasprofile –listProfiles
–Deleting a profile
wasprofile –delete –profileName •If desired, delete the left over files in the profile directory
Note: wasprofile is the tool that should be used for managing profiles.
First Steps •Is a post-installation ease-of-use tool •By default, starts automatically at the end of the wizard based installation •Can be started via Windows Start menu or command line •Can be used to verify installation •One per profile
Directory Structure Uninstaller for product
The bin directory hold the profile specific tools and scripts
Profile root
System Applications
The config directory holds all the configuration information for the profile
Server Commands •WebSphere commands are profile aware –There is a -profile option on many WebSphere commands –Or issue the commands from the appropriate \\bin directory •If no profile is used, the default profile is assumed –There can only be one default profile –Unless otherwise manually set, the first profile created will be the default •Examples (from \bin): startServer server1 -profileName profile1 startManager -profileName DMgr stopServer server1 " assumes default profile
Common Command Line Tools •Tools in \bin directory (as well as the profile’s bin directory) –addNode – Add a node to a cell –syncNode – Synchronize a node with the cell configuration –removeNode – Remove a node from a cell –startNode – Start the node agent –stopNode – Stop the node agent –startManager – Start the deployment manager –stopManager – Stop the deployment manager
WebSphere Profiles Issues •When multiple profiles are created on a single machine, be careful – Use correct profile bin directory to • startserver • stopserver • serverstatus
– Be aware of possible port conflicts for node agents and application servers • Make sure all of the servers have unique ports
– Be aware that there may be multiple server1 instances on a single machine (as part of different profiles) – Ensure that consistent hostnames within a machine are used • was6host00 and was6host00.ibm.com are different
Adding a WebSphere Node to a Cell •Adding a node to a cell can be done using: –Administrative Console •System Administration -> Nodes -> Add Nodes –addNode command line tool
Before Federation
V6 Application Server
After Federated
V6 Node
•The process of adding a node to the cell: –Creates backup of current configuration –Connects to deployment manager –Configures node agent –Adds node’s applications to cell configuration if the -includeapps option is used •For example, • addNode
mydmgr 8879 -includeapps
•After the node has been added –Use startNode to start the node agent –Use syncNode to synchronize a node with the cell configuration
V6 Application Server V6 Node
Cell Topology •The cell topology can be viewed through the administrative console –From System Administration, select Cell, Local Topology
Configuring Synchronization •From a node agent’s detail page select File Synchronization Service
Remove WebSphere Node from a Cell •Use removeNode (at node) to remove a node from a cell –Restores backup of node’s stand-alone configuration –Can be run through the administrative console, Nodes page •Remotely executes removeNode
•Use cleanupNode to clean up node configuration from cell repository –Only use this command to clean up a node if you have a node defined in the cell configuration, but the node no longer exists –Can be run through the administrative console, Nodes page with the Force Delete button •Force Delete action is equivalent to running the cleanupNode command at the deployment manager.
Unit Summary After completing this unit, you should be able to: •Describe concepts –Cell, Deployment Manager, Node •Describe installation of Deployment Manager •Describe directories and configuration files for WebSphere profiles •Add a node to a cell using addNode command •Use Deployment Manager administrative console to manage the master cell configuration •Configure synchronization to automatically distribute cell configuration changes
Lab Exercise Exercise10: Federating the cell
