Understanding Flexible Management in WebSphere Application Server V7

Transcription

1 IBM Software Group Understanding Flexible Management in WebSphere Application Server V7 Randal Anders WebSphere Application Server Level 2 Support 29 June 2010 WebSphere Support Technical Exchange

2 Agenda Overview Flexible management components Creating and starting the servers Registration Administering a node Submitting a scripting job Problem Determination & Known APARs WebSphere Support Technical Exchange 2 of 43

3 Section Overview WebSphere Support Technical Exchange 3 of 43

4 Network deployment model WebSphere Support Technical Exchange 4 of 43

5 Network deployment model limitations Model expects tight coupling, highly synchronous environment Management is at the individual server level Does not support management at the node level Scalability Problems managing very large number of base servers Synchronous model has problems with high latency remote branch servers WebSphere Support Technical Exchange 5 of 43

6 Flexible management topology WebSphere Support Technical Exchange 6 of 43

7 Flexible management characteristics Loose coupling of various pieces Offers asynchronous job queuing mechanism for administration purposes An alternative to the cell model Offers administrators additional management options not previously available Management of multiple base servers, up to a server farm containing hundreds of base servers Coordinate management actions across multiple deployment managers WebSphere Support Technical Exchange 7 of 43

8 Section Flexible management components WebSphere Support Technical Exchange 8 of 43

9 Administrative agent New profile type to support flexible management Register base application server profiles with the administrative agent Reduces application server footprint Migrates 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 WebSphere Support Technical Exchange 9 of 43

10 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 WebSphere Support Technical Exchange 10 of 43

11 Characteristics of flexible management jobs Have semantics tied to the underlying node For example, application management jobs Have few parameters Most application installation bindings are stored with the application. Are asynchronous, with activation and expiration times, and can recur Can send notification upon completion Have status that shows # of nodes succeeded, failed, or pending WebSphere Support Technical Exchange 11 of 43

12 Examples of flexible management jobs Examples Download application binaries Install applications Create/start/stop application servers wsadmin scripts WebSphere Support Technical Exchange 12 of 43

13 Example of flexible management topology Deployment Manager Job Manager Deployment Manager Deployment Manager Deployment Manager Administrative Agent Deployment Manager Job Manager Administrative Agent WebSphere Support Technical Exchange 13 of 43

14 Section Creating and starting the servers WebSphere Support Technical Exchange 14 of 43

15 Configuration process Create the profiles Base application server profiles Administrative agent profile Job manager profile Start administrative agent and job manager Register application server profiles with administrative agent Register application server profiles with job manager through administrative agent Optional: register deployment manager with job manager WebSphere Support Technical Exchange 15 of 43

16 Create the profiles Create profiles using manageprofiles command or Profile Management Tool WebSphere Support Technical Exchange 16 of 43

17 Using commands to create profiles manageprofiles.bat -create -templatepath %WAS_HOME%\profileTemplates\management -profilepath %WAS_HOME%\profiles\<dir_of_job_manager_profile> -profilename <name_of_job_manager_profile> -servertype JOB_MANAGER manageprofiles.bat -create -templatepath %WAS_HOME%\profileTemplates\management -profilepath %WAS_HOME%\profiles\<dir_of_admin_agent_profile> -profilename <name_of_admin_agent_profile> -servertype ADMIN_AGENT WebSphere Support Technical Exchange 17 of 43

18 Start the servers Start administrative agent and job manager in any order Starting the administrative agent Go to the profile s bin directory: ${WAS_HOME}/profiles/<name_of_admin_agent_profile>/bin Enter this command: startserver.sh adminagent Starting the job manager Go to the profile s bin directory: ${WAS_HOME}/profiles/<name_of_job_manager_profile>/bin Enter this command: startserver.sh jobmgr WebSphere Support Technical Exchange 18 of 43

19 Section Registration WebSphere Support Technical Exchange 19 of 43

20 Register with administrative agent Use the registernode command to register the base server profile with the administrative agent cd $WAS_HOME/bin registernode.sh profilepath $WAS_HOME/profiles/<name_of_base_profile> -host <host name> -conntype SOAP -port <soap_port_for_admin_agent> WebSphere Support Technical Exchange 20 of 43

21 Register with job manager Use wsadmin to connect to the administrative agent and then register the base server profile with the job manager wsadmin.sh profilename <admin agent profile> lang jython AdminTask.registerWithJobManager('[-host <hostname> -port <admin_port_for_job_manager> -managednodename <base_server_managed_node_name>]') WebSphere Support Technical Exchange 21 of 43

22 Optional: register deployment manager The deployment manager does not use an administrative agent Registers directly with job manager Use wsadmin to connect to the job manager and then register the deployment manager profile with job manager wsadmin.sh profilename <jobmgr_profile> lang jython wsadmin>admintask.registerwithjobmanager('[-host <jobmgr host> -port <admin_port_of_jobmgr> -managednodename <deployment_manager_node_name>]') WebSphere Support Technical Exchange 22 of 43

23 Section Administering a managed node WebSphere Support Technical Exchange 23 of 43

24 Administering a managed node Use the administrative agent console to perform administrative tasks on the administrative agent or on a managed node Launch the administrative agent console by entering a URL like this in your browser: port>/ibm/console WebSphere Support Technical Exchange 24 of 43

25 The administrative agent console WebSphere Support Technical Exchange 25 of 43

26 Section Submitting a scripting job WebSphere Support Technical Exchange 26 of 43

27 Submitting a scripting job Can be done using console or with a wsadmin script Submit a scripting job when you need more control than is available from high level flexible management jobs Example: Application deployment on normal server gives many more configuration choices than when deploying from job manager WebSphere Support Technical Exchange 27 of 43

28 Process to submit a scripting job Distribute the script file from the job manager to the node where the script file will get run Run the script by submitting a runwsadminscript job from the job manager Can be used for Jython or Jacl scripts WebSphere Support Technical Exchange 28 of 43

29 Submitting a scripting job from the console WebSphere Support Technical Exchange 29 of 43

30 Submitting a scripting job from the console WebSphere Support Technical Exchange 30 of 43

31 Submitting a scripting job from wsadmin Transfer the script file from the job manager to the target node: AdminTask.submitJob('[-jobType distributefile - targetlist [target node name ] -jobparams "[ [destination jythontestscript.py] [source file:/jythontestscript.py] ]"]') Verify that the job succeeded, and the file was moved into the downloadedcontent folder of the target node Run the script by submitting a runwsadminscript job as follows: AdminTask.submitJob('[-jobType runwsadminscript - targetlist [target node name ] -jobparams "[ [scriptlanguage jython] [scriptfilelocation jythontestscript.py] ]"]') Note: Jacl scripts can be run by changing the value of the scriptlanguage parameter to jacl WebSphere Support Technical Exchange 31 of 43

32 Section Problem Determination & Known APARS WebSphere Support Technical Exchange 32 of 43

33 Problem Determination Registration Is the jobmgr running? Are host and port correct (not SOAP or RMI port but admin_host port)? Are security credentials correct? Are the adminagent/dmgr and jobmgr clocks too far askew? Unattempted jobs What is the job availability window? Is the job target running? Are there problems connecting to the jobmgr logged in the adminagent/dmgr? In-progress jobs that never finish? Was the adminagent/dmgr restarted while the job was executing? WebSphere Support Technical Exchange 33 of 43

34 Problem Determination (cont) File distribution Copy file to config/temp/jobmanager under the job manager profile Source parameter using file:/ URL relative to config/temp/jobmanager AdminTask.submitJob( -jobtype distributefile targetlist [Node1,Node2,Node3] jobparams [[source file:/myapp.ear] [destination MyApp.ear]] ) File copied to adminagent_home/downloadedcontent runwsadminscript jobs Success or failure of job depends on return code from script WebSphere Support Technical Exchange 34 of 43

35 Problem Determination (cont) Cleaning up nodes Use cleanupmanagednode command at the jobmgr Cleaning up job managers Remove JobManagerRegistration from managednode.xml in node s config Trace settings Job Manager = com.ibm.ws.management.system.*=all Admin Agent = com.ibm.ws.management.agent.*=all WebSphere Support Technical Exchange 35 of 43

36 Job Manager Known APARS PM Job manager admin console screen shows additional installed products PK Nullpointerexception on job manager console - node collection screen PK NullPointerException deregistering dmgr from a job manager PK Messages filling up systemerr when job manager is stopped PK In job manager systemout.log JSAS0802E: The received admin RSA token has a nonce value that has been used recently PK Added help for register and unregister with job manager panels WebSphere Support Technical Exchange 36 of 43

37 Job Manager Known APARS PK Job manager exhibits high cpu usage in large scale flexible management deployments PK Several job manager console fixes PK When the registered node of a admin agent and job manager has a different realm, login failed during job submission. PK When job manager has over 40 registered end points, CPU usage increases to 100%. PK Job manager configuration is missing z/os location service configuration. WebSphere Support Technical Exchange 37 of 43

38 Administrative Agent Known APARS PM Unable to start Application Server after registering to a admin agent PK Error in FFDC during admin agent registration when using saf keyrings. PK NullPointerException in FFDC: when registering an Application Server to an admin agent for the first time. PK Monitoring policy link missing from admin agent Application Server console panel WebSphere Support Technical Exchange 38 of 43

39 Administrative Agent Known APARS PK Server fails to discover admin agent PK Addresses problems discovered with the admin agent during internal testing PK Exceptions are thrown during showeventservicestatus admintask under admin agent PK When the registered node of an admin agent and job manager has a different realm, login failed during job submission WebSphere Support Technical Exchange 39 of 43

40 Summary Components of flexible management architecture are the administrative agent and job manager. Configuration process consists of creating profiles, starting the job manager and administrative agent and registering with the job manager and administrative agent A managed node can be administered from the administrative agent console Scripting jobs can be submitted from the job manager console or with wsadmin For tracing the job manager, use com.ibm.ws.management.system.*=all For tracing the admin agent, use com.ibm.ws.management.agent.*=all is the latest fix pack available. WebSphere Support Technical Exchange 40 of 43

41 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 41 of 43

42 We Want to Hear From You! Tell us about what you want to learn Suggestions for future topics Improvements and comments about our webcasts We want to hear everything you have to say! Please send your suggestions and comments to: WebSphere Support Technical Exchange 42 of 43

43 Questions and Answers WebSphere Support Technical Exchange 43 of 43