1 / 66

WAS for z/OS V5: WAS Operations and Administration

WAS for z/OS V5: WAS Operations and Administration. After completing this unit, you should be able to: Describe the admin options available for WebSphere Manage the WAS runtime with: MVS commands UNIX line commands Scripting commands Use the WSADMIN scripting language to:

martinezgeorge
Download Presentation

WAS for z/OS V5: WAS Operations and Administration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WAS for z/OS V5:WAS Operations and Administration

  2. After completing this unit, you should be able to: Describe the admin options available for WebSphere Manage the WAS runtime with: MVS commands UNIX line commands Scripting commands Use the WSADMIN scripting language to: Install or uninstall applications Modify an existing application Start or stop servers Initiate node synchronization Create new servers, clusters, virtual hosts, and so on Unit Objectives

  3. System Management: Basic Topology

  4. System Management: Multi-Node, Distributed Admin

  5. File Transfer Service

  6. Config Sync

  7. Names - Defaults and Special Rules • Cell/Node - Customization Dialog Only • base server cell long/short name default to system name • base server node long/short name default to system name • deployment manager cell long/short names defaults to <sysplex>Network/<sysplex> • deployment manager node long/short names defaults to <sysplex>Manager/<sysplex> • Server - Customization Dialog and AdminConsole/Scripting • Server short name defaults to BBOSnnn, where nnn is unique number in cell • Server servant name (server region) defaults to BBOSnnnS • Special Servers - result of AddNode operation • nodeagent - BBONnnn • JMSServer - BBOJnnn • Clusters • Servers unclustered by default • Unclustered servers have special property to hold 'cluster short name' - ClusterTransitionName • ClusterTransitionName becomes cluster short name when server is promoted to cluster • Cluster names in form: BBOCnnn

  8. Where Names Are Used START/STOP/CANCEL/FORCE commands Start for app server control process (aka control region): START BBO5ACR,JOBNAME=<server short name>, ENV=<cell short name>.<node short name>.<server short name> Start (WLM) for app server servant process (aka server region) START BBO5ASR,JOBNAME=<server short name>S, ENV=<cell short name>.<node short name>.<server short name> Stop/CancelForce STOP <server short name> CANCEL <server short name> FORCE <server short name> Proc names for deployment manager are: BBO5DCR/BBO5DSR WLM - cluster short name is APPLENV ARM - registration name is <cluster short name> + <server short name> RACF CBIND - CB.<cluster short name>.CBIND SERVER - CB.<cluster short name>.SERVER

  9. Operating a Base Application Server Operating a Base Application Server

  10. How to Control a Base Application Server The WebSphere Way The z/OS Way Address Space Admin Console ASCB START STOP MODIFY CANCEL Command line tools Application server local USS shell MBean wsadmin $AdminControl JMX MBean server Program program API JMX JMX API z/OS Commands Basic AppServer Scenarios • Starting Servers • Stopping Servers • Displaying status

  11. System Management: V5.0 Admin Tools • Command Line Tools • Single node utilities to start server, perform simple functions • Located in /bin directory • Admin Console • Web application - runs in some application server • Browser is the client environment (connects to app server) • Wsadmin Scripting program • Non-graphic admin client • 3 modes - interactive, batch, command line • Java Admin APIs • Allows custom admin programs to be written in Java • Public classes and methods documented in the product javadoc, InfoCenter

  12. UNIX System Services (telnet) Commands

  13. Starting up a Base AppServer

  14. Start up Base Application Server from z/OS • Start command format • Operator issues 'start server' command • S WSBASEC,JOBNAME=WSBASE,ENV=CB.NB.WSBASE • Daemon is started automatically with command; • S WSDEMBC,JOBNAME=WSDEMBJ,ENV=CB.CB.WSDEMBJ • Servant regions started by WLM with command: • S WSBASES,JOBNAME=WSBASES,ENV=CB.NB.WSBASE • Results in 3 address spaces running: • SDSF DA panel: • Administration tool does not work - why? START <appserver_proc_name> , JOBNAME=<server_jobname> , ENV=<cell_short_name>.<node_short_name>.<server_short_name> JOBNAME ProcStep Owner JobID ASIDX Real CPU-Time WSBASE BBOCTL WSBASECU STC00577 03F 24T 29.85 WSDEMBJ BBODAEMN WSDEMBCU STC00585 03E 1948 0.87 WSBASES BBOSR WSBASESU STC00586 040 60T 33.49

  15. Stopping Base Application Servers • Stopping the Application Server(s) • MVS command: • "STOP <server_jobname>" • Admin Console: • Servers >> Appl. servers >> (select server) >>"Stop" button • MVS commands issued by AppServer running Admin Console application • MVS command "STOP <daemon_jobname>" stops them all • Recycling servers • Controller regions: Stop & Start server (MVS command or AdminConsole) • Servant regions: Use MVS command • "CANCEL <servant_ jobname>" • WLM will restart them • Regular recycling - set custom property server_region_recycle_count

  16. Operations and Availability Monitoring (SDSF or (E)JES)

  17. Starting up an ND Configuration

  18. Multi-System ND Configuration Example

  19. Editing the Commands Issued by the AdminConsole

  20. Starting Servers - 4 Ways to Do It (at Least)...(Once the Deployment Manager & Node Agents Are Started)

  21. WebSphere Traces

  22. Displaying Server Status from z/OS Console • MODIFY Command • MODIFY <server jobname>, DISPLAY, • SERVERS (name, system name, code level of servers) • SERVANTS (list of ASIDs of SRs attached to server) • TRACE (list active trace options for server) • SRS, ALL, JAVA • JVMHEAP (displays JVM heap info for servers) • SRS, ALL • SESSIONS (active session information for server) • LISTENERS, SERVER F WSBASE,DISPLAY BBOO0173I SERVER WSBASE/WSBASE ACTIVE ON W41 AT LEVEL W510000. BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY F WSBASE,DISPLAY,SERVERS BBOO0182I SERVER ASID SYSTEM LEVEL BBOO0183I CB /WSDEMBJ 3Ex W41 W510000 BBOO0183I WSBASE /WSBASE 3Fx W41 W510000 BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,SERVERS

  23. Modify Command: DISPLAY • MODIFY V5T1SV1,DISPLAY,HELP • Displays a list of available DISPLAY Options. • Modify commands can also be entered using F instead of MODIFY. • F V5T1SV1,DISPLAY,HELP • Documented in WebSphere Application Server for z/OS V5 – Operations and Administration BBOU0772I THE COMMAND DISPLAY, MAY BE FOLLOWED BY ONE OF THE FOLLOWING KEYWORDS: BBOU0773I SERVERS - DISPLAY ACTIVE CONTROL REGIONS BBOU0773I TRACE - DISPLAY INFORMATION ABOUT TRACE SETTINGS BBOU0782I END OF OUTPUT FOR COMMAND DISPLAY,HELP

  24. Display Work Commands • f <server_name>,display,work,<display_work_parameters> • where the <display_work_parameters> can be one of the following: • HELP - show these DISPLAY,WORK parameters • EJB - EJB requests driven by IIOP: total, current, dispatched & timed out • EJB,SRS - EJB requests driven by IIOP by servant region • SERVLET - Servlet requests driven by HTTM: total, current, dispatched & timed out • SERVLET,SRS - Servlet requests by each servant region • MDB - MDB requests driven by JMS: total, current, dispatched & timed out • MDB,SRS - MDB requests broken down by servant region • ALL - Combines the above for EJBs, servlets, and MDBs • ALL,SRS - EJBs, servlets, and MDBs by servant region • SUMMARY - total requests, current in progress, and in dispatch for all types • SUMMARY,SRS - total received by each SR, current in dispatch in each SR for all types • Example: f azsr01a,display,work,servlet • BBOO0255I TIME OF LAST WORK DISPLAY Wed Dec 3 19:17:54 2003 • BBOO0256I TOTAL SERVLET REQUESTS 150670 (DELTA 1654) • BBOO0257I CURRENT SERVLET REQUESTS 1 • BBOO0258I SERVLET REQUESTS IN DISPATCH 0 • BBOO0267I TOTAL SERVLET TIMEOUTS 0 (DELTA 0) • BBOO0188I END OF OUTPUT FOR COMMAND DISPLAY,WORK,SERVLET

  25. Display JVM Heap • Full Syntax: • MODIFY BBOASR4,DISPLAY,JVMHEAP • MODIFY BBOASR4,DISPLAY,JVMHEAP,SRS • MODIFY BBOASR4,DISPLAY,JVMHEAP,ALL • Without modifies displays heap information for Control Region • With SRS modifier displays heap information for all SRS one at a time • With ALL modifier displays heap information for Control Region and all SRs one at a time.

  26. Other Handy MVS Commands • Start RRS start atrrrs,sub=mstr • Stop RRS setrrs cancel • Start DB2 -dbpx start db2 • Stop DB2 -dbpx stop db2 • Start MQSeries +mqsysx start qmgr parm(mqzprm) • Stop MQSeries +mqsysx stop qmgr • Start WAS CTrace trace ct,wtrstart=<ctwtr_procname> • Stop WAS CTRACE trace ct,off,comp=<cell_name> • trace ct,wtrstop=<ctwtr_procname> • Disable ARM setxcf stop,policy,type=arm • Activate WLM Appl.Env. v wlm,applenv=xxxx,resume • Activate Dynamic WLM Appl.Env. v wlm,dynappl=xxxx,resume • Switch SMF datasets i smf • Change SMF parms setsmf <var_name>=value • Switch to new SMF parms set smf=99 • Change OMVS parms setomvs <var_name>= value • Refresh TCP/IP Profile parms v tcpip,,o,sys1.tcpparms(profilex)

  27. Tools • Tools ’n Toys (viascii): • http://www.ibm.com/servers/eserver/zseries/zos/unix/bpxa1toy.html • jad (decompile java class files): • http://kpdus.tripod.com/jad.html • Tera Term: • ftp://riksun.riken.go.jp/pub/pc/misc/terminal/teraterm/ • PFE Editor: • http://www.lancs.ac.uk/people/cpaap/pfe • WS_FTP: • http://www.ipswitch.com • MXI - "MVS sysprog browser": • http://www.secltd.co.uk • NEDIT: • http://www.nedit.org • Jinsight profiling & visualization: • http://www.alphaworks.ibm.com

  28. InfoCenter Views: Contents and Search Results

  29. Documentation - WebSphere V5.1 • InfoCenter (basis for the PDF books) • http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp • Books (PDFs) from WebSphere for z/OS home page • http://www.ibm.com/software/webservers/appserv/zos_os390/library/ • 1. Getting Started • 2. Servers & Environment • 3. Applications • 4. Resources • 5. Security • 6. System Administration • 7. Performance Monitoring & Tuning • 8. Problem Determination • 9. Program directory • 10. Messages & Codes • Administrative Console Help • Techdocs • http://www.ibm.com/support/techdocs • Redbooks • http://www.redbooks.ibm.com/

  30. WSADMIN and Scripting

  31. Java Management Extensions (JMX) Structure proprietary management tool web browser Manager Level protocol adapters MBean Server Agent Level MBean MBean Management service MBean Instrumentation Level Managed object MBean JMX Agent Managed object

  32. JMX Support in WebSphere for z/OS Application Server Admin tool Console • JMX Connectors and Adapters • XML/HTTP (SOAP) JMX Connector • RMI JMX Connector • Later ... • SNMP Adapter • Asynchronous JMS Connector • WebSphere JMX Agent • MBeanServer • Agent Services (Monitor, Timer, Relation) Admin tool web application HTTP USS Shell SOAP JMX RMI JMX wsadmin (script) JMX MBean server admin client program JMX API server MBean Command line tools • WebSphere MBeans • JMX ManagedBean Interface, ManagedObject Interface, Event Notification • extended WebSphere properties, operations, notifications • all MBeans defined by XML MBeanDescriptor

  33. wsadmin - How Does It Work? wsadmin Appl. Server SOAP or RMI Connection MBean AdminApp MBean script AdminConfig MBean AdminControl MBean Help • Four different scripting objects perform different operations • The wsadmin shell script: /usr/lpp/zWebSphere/V5R1M0/bin/wsadmin.sh • Important command options: • source of script commands • Imbedded in command -c <script command> • Input from file -f<script file> • Interactive (no option) • connection to an MBean server? • -conntype SOAP -host<host_name>-port <port_number> • -conntype RMI -host<host_name>-port <port_number> • -conntype NONE

  34. WSADMIN Is Scripting Interface

  35. You've Probably Used WSADMIN

  36. WSADMIN "Client"

  37. Where You May Run Client

  38. "Local" Mode versus "Remote" Mode

  39. When "Local" versus "Remote"

  40. On z/OS, Run Under "WAS Admin ID"

  41. Other Files to Be Aware of

  42. Starting a Server from the USS Shell • Using wsadmin script tool • use deployment manager to start application server BaseServer can use the stopServer command in a similiar way • if script command is in file start.jacl, then Using line command tool "startServer.sh" • start server BaseServer on the local system • can only work on local servers /WASV500/config/AppServer/bin/wsadmin.sh \ -conntype SOAP -host MVSW41 -port 8880 \ -c '$AdminControl startServer BaseServer BaseNode' \ 1> /tmp/bbowiapp.out 2> /tmp/bbowiapp.err wsadmin options script command /WASV500/config/AppServer/bin/wsadmin.sh \ -conntype SOAP -host MVSW41 -port 8880 -f start.jacl \ 1> /tmp/bbowiapp.out 2> /tmp/bbowiapp.err cd /WASV500/config/AppServer/bin startServer.sh BaseServer

  43. Syntax of WSADMIN Invocation

  44. Four WSADMIN Program "Objects"

  45. "Inline" Commands

  46. Files Containing Script

  47. The $AdminApp Object

  48. $AdminApp Options

  49. Jacl Scripting Basics

  50. Passing Arguments into Jacl Script

More Related