Deploying Applications with the Administration Tool

1. WAS for z/OS V5: Deploying Applications with the Administration Tool

2. After completing this unit, you should be able to: Describe possible multi-base server configurations and their characteristics Use z/OS system commands and the administration tool to control servers and applications on those servers Locate, evaluate, and set configuration data for Server environment variables JVM arguments Summarize the steps and tools required to deploy a J2EE application from the developers workstation to WebSphere for z/OS List the main categories of configuration data stored in the cell configuration Start the administration tool interface from a web browser Use the administration tool to create a new base application server Use the administration tool to deploy an application onto that server Unit Objectives

3. Multi-server Environments for the Base Server Multi-server Environments for the Base Server

4. MVS System or LPAR Cell Node Server instance Daemon Browser A CR CR Cell Node Server instance Daemon Browser A CR CR Cell Node Browser Server instance Daemon A CR CR Multiple Base Application Server Nodes • Multiple Base App Nodes in one system are acceptable with WebSphere for z/OS Version 5 • Involves running the dialog for each Base App. Node • Each server would have its own: • Server Root (and HFS) • Cell • Node • TCP/IP ports • Admin interface • Implies great separation and isolation ...

5. / <Base App Node Mount Point> WLM HFS ApplEnv JCL Daemon Cell Node instance A Daemon JCL CR A RACF CR CR /Daemon /AppServer Definitions SR TCP JCL Ports / <Base App Node Mount Point> WLM ApplEnv JCL Daemon Cell HFS Node instance B Daemon JCL CR A RACF CR CR Definitions /Daemon /AppServer SR TCP JCL Ports / <Base App Node Mount Point> WLM Cell ApplEnv JCL Daemon HFS Node instance C Daemon A CR CR JCL CR RACF Definitions /Daemon /AppServer SR TCP JCL Ports If you're looking for isolated environments, this is good news Separate Resources for Each Base Node

6. MVS System or LPAR Cell Node Server A Daemon Browser CR A SR CR Install new application Server B SR CR Server n A SR CR Browser Base Application Node, Multiple Servers • The administative application can be used to create more servers within the same Base Node • You may use the same procedure for all servers • Use admin application in one server to install applications in other servers. • Starting and stopping of server is by MVS command, not via admin console • Can run more than one admin server Note: Only one daemon is required per cell per system or LPAR.

7. HFS Note: one RACF userid/group pair owns the whole HFS tree from the mount point down. Every server's userid must be connected to that group /<Mount Point> /<symbolic for Server A> /<symbolic for Server B> /<symbolic for Server n> • one set of JCL (procedure) used for all servers • JOBNAME and ENV parameters identify each server /AppServer JCL CR /config /cells SR JCL /<Cell Name> /nodes /<Node Name> z/OS console, SDSF log Note: one cell, one node /servers /<Server A> /S V5ACR,JOBNAME=S1,ENV=C1.N1.S1 was.env /<Server B> /S V5ACR,JOBNAME=S2,ENV=C1.N1.S2 was.env /<Server n> /S V5ACR,JOBNAME=S3,ENV=C1.N1.S3 was.env different pointer for was.env different job name The HFS For Multi-Server Base Application

8. Multiple Base App Server Nodes One Base Node, Multiple Servers Configuration: Use ISPF dialogs for each cell created Use admin console in first to create additional servers JCL Procedures: Use the same set for all servers Separate for each Base App Node RACF IDs May use the same, but probably want to establish unique Separate set for each Base App Node Mount Points: Same mount point; each server has separate branch Separate for each Base App Node Administrative Isolation: Each is able to see other servers, install apps into, but not start or stop Complete isolation Application Isolation: Complete isolation Applications can't have same deploy name, may have the same JNDI names Comparison

9. Using the WebSphere V5 Administration Tool Using the WebSphere V5 Administration Tool

10. WebSphere z/OS V5 Admin Console • "Thin" admin console • J2EE web application • Supports: • Cluster/server configuration • Basic server operation, such as START/STOP • Basic server monitoring (up, down) • Resource definition • Application installation and management • Security configuration and administration • Supports multiple administrators • Supports concurrent administrative changes in cell • Userid/PW access (when security enabled)

11. Base Application Server • Installed on single machine (system/LPAR) • Separate install on distributed • Setup through configuration on z/OS • One or more servers • J2EE 1.3-compliant • Web services • Configuration files in XML • Admin clients modify XML • Browser-based (Admin Console) • Scripting (wsadmin) • Node agent • Installed but not configured • Configured during addNode Not activated until node added to a cell Admin client + browser Admin App Server Node Agent App Server App Server XML Config XML Config Single z/OS image/LPAR

12. Configuration Repository – Overview • Configuration data contained in XML documents • Set of hierarchical directories under <was_root>/config • Directories are in three tiers: cell, node, server • Each contains documents specific to that scope • Examples: • Cell level – contains clusters.xml defining all the clusters in the cell • Server level – contains server.xml defining the attributes of the server • Admin clients used to modify configuration • Web Based Admin (Admin Console) • WebSphere Scripting (wsadmin)

13. Configuration Repository - Structure <cell-name>: admin-autz.xml cell.xml namestore.xml naming-autz.xml security.xml variables.xml virtualhosts.xml resources.xml cells: plugin-cfg.xml /config /cells <node-name>: node.xml resources.xml namestore.xml variables.xml serverindex.xml /MyCellA /applications /nodes /NodeA <server-name>: server.xml resources.xml variables.xml • Different levels of the hierarchy contain documents with the same name • Some documents are logically combined, some are independent • When logically combined, the “most specific” value takes precedence : • Result of final combination applied at the server level • Example files: variables.xml and resources.xml • When not combined: • File contents apply to the level where found (server, node, cell) ( Ex = namestore.xml) /servers /ServerA

14. Base Application Server AppServer Server1 HTTPS 99443 User Enterprise Application Admin Web Application 99080 HTTP • Load • Save • Edit Browser • Install • Microsoft Internet Explorer 5.5, 6.0 .. • Netscape Navigator 4.7x Node EAR files config (xml files) Activating WebSphere V5 Admin Application • The Admin Console Web Application • Standard 1.3 J2EE application - runs within an Application Server instance • Installation job BBOWIAPP deploys admin application into base server • Start the base application server • Start browser and access Admin application from the web • http://hostname:9080/admin • https://hostname:9443/admin

15. Save changes to Master Taskbar WorkSpace Navigation Tree Status Messages Administrative Console Areas

16. Admin Console Navigation Tree • Servers - Enables you to configure administrative servers and other types of servers such as JMS servers. • Applications - Enables you to install applications onto servers and manage the installed applications. • Resources - Enables you to configure resources and to view information on resources existing in the administrative cell. • Security - Accesses the Security Center, which you use to secure applications and servers and to manage users of the administrative console. • Environment - Enables you to configure hosts, Web servers, variables and other components. • System Administration - Enables you to manage components and users of a Network Deployment product. • Troubleshooting - Access to logs, tracing, configuration problem collection, and tuning.

17. Admin Console Taskbar • Home - Displays the administrative console Home page in the workspace. • Save - Displays the Save page. • Preferences - Displays the Preferences page. • Logout - Logs you out of the administrative console session and displays the Login page. If changes were made and not saved the Save page will display. • Help - Opens a new Web browser on online help for the WebSphere Application Server product. • Hide/Show Field and Page Descriptions toggle - Enables you to select whether information on console pages and fields within the pages is shown.

18. Admin Console Status Area • WebSphere Configuration Problems • Displays the number of workspace files. • Displays the number of problems with the configuration • Click on the number to view detailed information on the problems. • WebSphere Runtime Message • Displays the number of messages returned by WebSphere Application Server • Error messages (x icon), • Warning messages (! icon) • Informational messages (i icon).

19. Admin Console Preferences Throughout the administrative console are pages that have Preferences, Filter, and Scope fields near the top of the frames. To customize how much data is shown, select options in Preferences, Filter and Scope.

20. Admin Console Help • Click Home on the Administrative Console Taskbar and select a link to information on using the WebSphere Application Server product. The link to the InfoCenter provides concept, task and reference information. • Click Help on the administrative console taskbar and select from the list of reference topics. • Click the icon beside a field or page description.

21. Administration Tool Topology Cell Resources Security Environment Servers • Application servers • JMS servers • Clusters • Cluster topology • JDBC Providers • Generic JMS Providers • WebSphere JMS Provider • WebSphere MQ JMS Provider • Mail Providers • Resource Environment Providers • URL Providers • Resource Adapters • Update Web Server Plugin • Virtual Hosts • Manage WebSphere Variables • Shared Libraries • Internal Replication Domains • Naming • Global Security • SSL • Authentication Mechanisms • User Registries • JAAS Configuration • Application Logins • Authentication Protocol System Administration • Cell • Deployment Manager • Nodes • Node Agents • Console Users • Console Groups Troubleshooting Applications • Enterprise applications • Install new applications • Logs and Trace • Configuration Problems

22. "Environment" Variables • All servers are dependent on special run-time parameters for 'knowledge' of their execution environment • First type of parameter is the environment variable • Familiar to UNIX shell users - "<keyword>=<value>" • Defined in file variables.xml at 3 levels - cell, node, and application server • The values used by an application at start up are generated by merging all the levels (cell highest priority, server lowest) - result saved in was.env • Second type of parameter is the server JVM settings (properties) • Also known as java command line arguments • These values are accessible to java applications executing in the JVM • General form "-D<setting_value>" or "-X<setting_value>" • Defined in two files stored in directory "......servers/<server-name> " • control.jvm.options • servant.jvm.options config/cells/<cell-name>/variables.xml nodes/<node-name>/variables.xml servers/<server-name>/ variables.xml was.env

23. The Big Picture Application Server SR was.env PGM= TCB BBOSR MIKE=COX TCB • WAS servers are MVS started tasks which are dubbed as processes • The JVM is just an "ordinary" program attached by BBOSR servant. jvm.options john=hutchinson J N I java_pgm C_pgm JVM • was.env contents are equivalent to a variable exported in the shell • export MIKE=COX • JVM settings contents - equivalent to variable set with -D on java cmd • java -Djohn=hutchinson java_pgm arg1 arg2.. • Visibility: • variable "MIKE=COX" is visible to 'java' (JVM) but not to 'java_pgm' (app) • variable "john=hutchinson" is visible to 'java_pgm' (app)

24. JACL Command File wsadmin.sh Config HFS Administrator Application Components WebSphere V5 Administrative Server Write XML Configuration Files Read Administrative Console Installing Enterprise Applications • The Install Application Flow • Create an Application Server (optional) • Configure the application environment as required (variables, virtual hosts, classpath, security) • Configure application resources (JDBC provider, data sources) • Install Application • Manage static content (files served by Web server, not in EAR file).

25. Install a New Server from the Admin Tool (1 of 2)

26. Install a New Server from the Admin Tool (2 of 2) • Read and understand the "Possible issues" listed • Confirm the creation of the new server by clicking Finish. • Save the master configuration with the Admin tool Save configuration z/OS Console BBOO0222I ADMR0009I: Document 691 cells/TestCell1/nodes/TestNode1/servers/Trade Server/resources.xml was created. BBOO0222I ADMR0009I: Document 692 cells/TestCell1/nodes/TestNode1/servers/Trade Server/server.xml was created. BBOO0222I ADMR0010I: Document 693 cells/TestCell1/nodes/TestNode1/serverindex.xml was modified.

27. Other Configuration Elements • Apart from installing the EAR file, there probably are more configuration tasks needed before a new application can be run • JDBC Provider • Data sources • JMS connection factories, queues, and topics • JMS server • Global security • J2C authentication aliases • Virtual Hosts • Suggested practice is to set up resources before installing the application

28. Enterprise Application Installation (1 of 8) • Select Applications > Install New Application • Click Browse and locate the EAR file containing the application’s modules • Click Next

29. Enterprise Application Installation (2 of 8) • Configure JNDI bindings for: • Prefixes • EJB 1.1 bindings • Connection Factory • Virtual Host for Web modules • In most cases this page can be skipped without changes • Click Next

30. Enterprise Application Installation (3 of 8) • Pre-compile JSPs • Change installed application directory • Deploy EJBs • Change Application name

31. Step Function 2 Provide JNDI Names for Beans 3 Provide default datasource mapping for modules containing 2.0 entity beans 4 Map datasources for all 2.0 CMP beans 5 Map EJB references to beans 6 Map resource env entry references to resources 7 Map virtual hosts for web modules 8 Map modules to application servers 9 Map security roles to users/groups 10 Ensure all unprotected 2.0 methods have the correct level of protection 11 Summary Enterprise Application Installation (4 of 8) • The next few pages of the wizard allow you to tweak the configuration of the Application components.

32. Enterprise Application Installation (5 of 8) • On this page you determine which modules run on which Application Server. • Select the Application Server • Check module for the selected server • Click Apply

33. Enterprise Application Installation (6 of 8) • Users and Groups can be mapped to groups

34. Enterprise Application Installation (7 of 8) • Once all configuration parameters have been set to your satisfaction, click Finish to install the Enterprise Application

35. Enterprise Application Installation (8 of 8) • After installation install you can: • Start • Stop • Uninstall • Update • Export • Export DDL

36. Having completed this unit, you should be able to: Describe possible multi-base server configurations and their characteristics Use z/OS system commands and the administration tool to control servers and applications on those servers Locate, evaluate, and set configuration data for Server environment variables JVM arguments Summarize the steps and tools required to deploy a J2EE application from the developers workstation to WebSphere for z/OS List the main categories of configuration data stored in the cell configuration Start the administration tool interface from a web browser Use the administration tool to create a new base application server Use the administration tool to deploy an application onto that server Unit Summary