New System Management Components in WebSphere Application Server V7

Transcription

1 IBM Software Group New System Management Components in WebSphere Application Server V7 Vikram Thommandru WebSphere Support Technical Exchange

2 Agenda Overview Flexible management components - AdminAgent - JobManager Creating and starting the servers Registration Administering a managed node Submitting a scripting job Enabling security in a flexible management environment Accessing secured components WebSphere Support Technical Exchange 2 of 41

3 Overview Flexible management WebSphere Support Technical Exchange 3 of 41

4 Network deployment model WebSphere Support Technical Exchange 4 of 41

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 41

6 Flexible management topology WebSphere Support Technical Exchange 6 of 41

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 41

8 Flexible management components WebSphere Support Technical Exchange 8 of 41

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 41

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 41

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 41

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 41

13 Flexible management configuration WebSphere Support Technical Exchange 13 of 41

14 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 14 of 41

15 Create the profiles Create profiles using manageprofiles command or Profile Management Tool WebSphere Support Technical Exchange 15 of 41

16 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 16 of 41

17 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 17 of 41

18 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 18 of 41

19 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 19 of 41

20 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 20 of 41

21 Flexible management examples 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 21 of 41

22 The administrative agent console WebSphere Support Technical Exchange 22 of 41

23 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 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 23 of 41

24 Submitting a scripting job from the console WebSphere Support Technical Exchange 24 of 41

25 Submitting a scripting job from the console WebSphere Support Technical Exchange 25 of 41

26 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 26 of 41

27 Security in a flexible management environment WebSphere Support Technical Exchange 27 of 41

28 Enabling flexible management security Enabling security is very similar to the way administrative security is enabled for servers in W ebsphere Application Server V6.1 When security can be enabled: During profile creation After the profile has been created How security can be enabled: Using profile creation Using the administrative console Using wsadmin Security must be enabled before registration with administrative agent or job manager WebSphere Support Technical Exchange 28 of 41

29 Enabling flexible management security Tool during profile creation Administrative security can be enabled from the Profile Management WebSphere Support Technical Exchange 29 of 41

30 Accessing secured components Accessing secured servers in a flexible management environment is similar to the way administrative security is enabled for servers in WebSphere Application Server V6.1 In a flexible management environment, security must be considered when accessing: Job manager Administrative agent Application server Each of the above can have a different username password that must be used WebSphere Support Technical Exchange 30 of 41

31 Security considerations Starting a secured server does not require username and password Accessing a secured server through the administrative console or wsadmin does require username and password Stopping a secured server does require username and password WebSphere Support Technical Exchange 31 of 41

32 Administrative agent security considerations If administrative agent has administrative security enabled: Must provide username and password for administrative agent when registering an application server node with administrative agent If application server has administrative security enabled: Must provide username and password for that server when registering with the administrative agent Sample command: registerprofile.bat <all normal parameters> -username <adminagent_username> -password <adminagent_password> -nodeusername <base_node_username> -nodepassword <base_node_password> WebSphere Support Technical Exchange 32 of 41

33 Job manager security considerations If job manager has administrative security enabled: Must provide username and password for job manager when registering an application server node with the job manager If administrative agent has administrative security enabled: Must provide username and password for administrative agent when registering with the job manager Sample commands for starting wsadmin and doing registration: wsadmin.bat profilename <adminagent_profile_name> -user <adminagent_username> -password <adminagent_password> AdminTask.registerWithJobManager('[-port user <jobmgr_username> -password <jobmgr_password> -managednodename <managed_node_name>]') WebSphere Support Technical Exchange 33 of 41

34 Job manager security considerations Scenario: You want to submit a job from the job manager to an application server in a managed node Administrative security is enabled on the job managed and the application In this case, credentials for both the job manager and the application server need to be provided Username and password for job manager need to be entered to access job manager through the job manager console Username and password for application server need to be sent with other information when job is submitted WebSphere Support Technical Exchange 34 of 41

35 Flexible management security WebSphere Support Technical Exchange 35 of 41

36 Flexible management security WebSphere Support Technical Exchange 36 of 41

37 Flexible management security WebSphere Support Technical Exchange 37 of 41

38 Flexible management security WebSphere Support Technical Exchange 38 of 41

39 Summary Flexible management is an asynchronous, scalable deployment architecture Flexible management components include the administrative agent and job manager The flexible management configuration process consists of: Creating the required job manager and administrative agent profiles Starting the job manager and administrative agent Registering a managed node with the administrative agent Registering a managed node with the job manager Enabling security in a flexible management environment is similar to enabling administrative security in other W ebsphere environments Unlike the network deployment environments, each server in a flexible management environment might have its own username and password WebSphere Support Technical Exchange 39 of 41

40 Additional WebSphere Product Resources Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Learn about other upcoming webcasts, conferences and events: Join the Global WebSphere User Group 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 40 of 41

41 Questions and Answers WebSphere Support Technical Exchange 41 of 41