This preview shows pages 1–3. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: Student Exercises Course materials may not be reproduced in whole or in part without the prior written permission of IBM. © Copyright IBM Corp. 2008 Exercise 9. Flexible management V5.1 EXempty Exercise 9. Flexible management What this exercise is about The objective of this lab is to acquaint you with the Flexible System Management (FSM) available in WebSphere Application Server V7.0 (WAS). This mechanism differs from the existing style of synchronous invocation/response calls through wsadmin or Java APIs by offering an asynchronous job queuing mechanism for administration purposes. This lab will guide you through creating and configuring the various profiles involved. What you should be able to do At the end of this lab you should be able to: • ""Create a job manager profile and start the job manager • "Create an admin agent profile and start the admin agent • "Create a base profile, register it with admin agent, and enroll it with job manager • "Create a utility module to check status • "Create, start, stop, and delete an application server on the base profile • "Explore wsadmin commands by using the job manager console • "Force the admin agent to poll the job manager Introduction WebSphere Application Server V7.0 introduces a new style of system management called flexible management. It differs from the existing style of synchronous invocation/response calls through wsadmin or Java APIs by offering an asynchronous job queuing mechanism for administration purposes. This asynchronous style is not meant to replace existing WebSphere Application Server installations based on the cell model using deployment manager, node agents, and application servers. Rather, it offers the administrators additional management options not available previously: • Management of multiple stand-alone application servers, up to a server farm containing hundreds of application servers. • Coordinate management actions across multiple deployment managers. • Management of branch servers geographically dispersed and reachable only through low bandwidth, high latency network. • Asynchronous administrative job submissions that- Take effect at a specified time- Expire after a specified time- Recur at a specified time interval- Notify the administrator through e-mail when job is complete. This lab is divided into the following parts. • Part 1: Create a job manager profile • Part 2: Create an administrative agent profile • Part 3: Create an additional application server profile • Part 4: Register the stand-alone application server with the job manager and administrative agent • Part 5: Use the job manager to start a server • Part 6: Explore the Job Manager and Administrative Agent consoles • Part 7: Submit a job to backup the log files Lab requirements The system on which you will exercise this lab must have a supported operating system and a proper installation of WebSphere Application Server V7.0. For more information on supported operating systems, see Server V7....
View Full Document
This note was uploaded on 02/09/2012 for the course COMPUTER S a303 taught by Professor None during the Spring '11 term at BEM Bordeaux Management School.
- Spring '11