Transcription
IBM Education Assistance for z/OSMF V2R1Item: New Release ContentElement/Component: z/OS Management FacilityMaterial is current as of May 2013 2013 IBM Corporation
Filename: zOS V2R1 zOSMFIBM Presentation Template Full VersionAgenda Trademarks Overview Usage & Invocation Interactions & Dependencies z/OSMF Browser Support Migration & Coexistence Considerations Installation Presentation Summary Appendix 2013 IBM Corporation
Filename: zOS V2R1 zOSMFIBM Presentation Template Full VersionTrademarks See url http://www.ibm.com/legal/copytrade.shtml for a list of trademarks. 2013 IBM Corporation
Filename: zOS V2R1 zOSMFIBM Presentation Template Full VersionOverview Problem Statement / Need Addressed– z/OSMF needs to provide improved configuration experience and a smaller andfaster product package that requires fewer resources.– More functions should be provided to enable the system programmer tomanage the z/OS system better Solution– z/OSMF V2R1 has been rebased on the WebSphere Liberty profile anddelivers a smaller faster product and requires less resources. It is also easier toconfigure.– The workflow function has a focus to simplify configuration on z/OS Benefit / Value– z/OSMF can be installed and configured more easily on more systems.– z/OSMF will consume fewer resources and provide more benefit to z/OS clients– The workflow function will provide a basis for future simplification and time tovalue 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF V2R1 welcome panel after login 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF Software Management The z/OSMF Software Management application (was previously called Software Deployment)extends the Software Deployment task to provide additional actions on instances of SMP/Einstalled software. It is available on z/OS V1R13 with the PTF UK83841. The Software Management task supports– Deploying a software instance,– Inspection of a software instance to view the product, feature and FMID content, and view thephysical data sets that compose a software instance.– Actions to analyze and report on software instances and products within instances to: Identify software products that are approaching, or have reached, end of service support,thus helping customers with upgrade and migration planning. Identify missing HIPER and PE fixes, and fixes associated with one or more fix categoriesto help customers assess the risks and stability of installed software and ensure hardwareand software requisites are installed. Validate the SMP/E structure and content of a software instance is correct by cross-checkSMP/E inventory information with catalog entries, volume residency and data set content. Determine if individual fixes are installed and in which software instances. Compare the service and functional content of two software instances to aid in debuggingor migration planning. In V2R1, Software Management provides Print/Export function for some reports 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF Workflow Problem being solved:–Configuring a new product or component on z/OS is complex and apain point for customers–Customers want consistent, simplified and less error prone way toconfigure and perform a set of tasks on z/OS simplified and managed instructions, interface, tools, wizards, etc. z/OSMF V2R1 provides a workflow framework with a focus to simplifyconfiguration on z/OS or perform a set of tasks on z/OS z/OSMF workflow function will enable bringing together the end-to-endsteps for configuration of the selected software–Provide an programmatic to-do list (aka workflow)–Shorten the time to value Note: the workflow framework will be generic and not confined toconfiguration only, although that is the initial focus 2013 IBM Corporation
Filename: zOS V2R1 zOSMFUse Case Scenario A product decides to participate in z/OSMF workflow The product owner defines the metadata file with steps required by their product– z/OSMF will define and publish the schema for product owners to code to The product delivers its metadata file with their product package (SMP/E or nonSMP/E) and documents its location in their program directory (or equivalent)– It is possible that the metadata file is generated as part of some otherconfiguration steps for that product. The product is installed (SMP/E or non SMP/E) on the customer’s z/OS system The customer now wants to configure the product on their z/OS system They will follow the product instructions for configuring the product and at somepoint in the instructions it will instruct to use the z/OSMF Workflow task toconfigure the z/OS artifacts– The customer/system programmer would then need to log in to z/OSMF andopen the ‘Workflow task' 2013 IBM Corporation
Filename: zOS V2R1 zOSMFUse Case Scenario (contd.) The system programmer logs on to z/OSMF and loads the workflowmetadata file for the unit to be configured. In the new Workflow task, the user can define the unit to be configured byidentifying the metadata file via Action: CREATE in this new task–Prompts the user to provide the fully qualified location–Reads in the metadata file(s). Once loaded, it is ready to be used.The original metadata file(s) is no longer used. If the product providesan update to the metadata file(s), then the z/OSMF user would need tohave the Workflow task re-import it to pick up the changes The system programmer can then start by opening a workflow This will start a workflow instance that will allow the user toview/assign/perform all the steps necessary to configure the givenproduct 2013 IBM Corporation
Filename: zOS V2R1 zOSMFWorkflow characteristics z/OSMF provides an XML schema for products to use to define theirworkflow steps in an XML document It contains ways to indicate the steps to complete a workflow– Simple samples are shipped with the product The products would provide this file for the workflow task to import it andthen display to the end user for configuring their product There will likely be a set of files that comprise the metadata and the enduser will provide the workflow task with a single entity and all otherrelevant files will be imported automatically.– Examples of addition files are Job templates, REXX or shell script templatesConfiguration file Wizards are provided to automate common tasks to aid in configuringz/OS for the given product;– JCL wizard to update and submit a job– REXX execs and shell scripts supported within generated batch jobs Workflow metadata file packaging – may be USS file or a dataset member 2013 IBM Corporation
Filename: zOS V2R1 zOSMFWorkflow characteristics The XML metadata file contains steps and details;– Steps may be manual or invoke wizards;– Steps may define dependency on other steps The workflow task provides ability to route tasks among a number of defined usersor people assigned to specific roles, such as "system programmer" and "securityadministrator," to complete setup tasks. The z/OSMF user is notified of assigned workflow steps via the new Notification task The workflow supports wizard-like task sequencing, with tasks presented toadditional users as dependencies are met The workflow steps go through various stages until complete;– The stages may be unassigned, assigned, accepted, not ready, ready, inprogress, complete, complete(override), skipped Workflow history is maintained of all activities in the workflow task Users can make notes for a workflow instance 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF workflow – create an instance 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF configuration - Workflow exampleState of stepsAssignedNotes, historyWorkflow steps 2013 IBM Corporation
Filename: zOS V2R1 zOSMFWorkflow JCL wizardWizard steps 2013 IBM Corporation
Filename: zOS V2R1 zOSMFWorkflow history 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to RESTful Jobs API Recent enhancements to JOBS Submit API–Also available on z/OSMF V1R13 via APAR PM74502 Deprecation of non X-IBM- prefixed custom headers Access to job JCL Submit from data set (including the ability to request a recall of a migrateddata set) Submit from z/OS UNIX file Secondary JES2 subsystem support for cancel a job, change job class,and delete a job (cancel a job and purge its output) 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to RESTful Jobs APIIn z/OS V2R1 with z/OSMF V2R1, the z/OS Jobs REST Interface isextended to add support for optional asynchronous notification upon job completion, passing JCL symbols to a job being submitted, and an optional job correlator that is unique across the JES2 spool.These extensions are intended to make it easier to reuse existing JCL anddetect job completion. 2013 IBM Corporation
Filename: zOS V2R1 zOSMFJCL symbolic: The user is able to provide the values in HTTP headers for JCL symbols whensubmitting a job. This support is JES2 specific.Example: Symbol name MBR with value equal to ABC in HTTP request headers:PUT : applicaton/jsonX-IBM-Intrdr-Lrecl: 80X-IBM-JCL-Symbol-MBR:ABC Part of the codes in JCL something like://MYDD DSN MY.DATASET(&MBR.),DISP SHR When submit the job to JES, ABC substitutes parameter &MBR as the member name//MYDD DSN MY.DATASET(ABC),DISP SHR 2013 IBM Corporation
Filename: zOS V2R1 zOSMFJCL correlator: The user can provide the user portion of the job correlator whensubmitting a job. The job correlator can be used as an alternative to the jobname/jobidcombination for identifying a job. This support is JES2 specific. Example:–Submit a job with user portion job correlator:–PUT https://host:port/zosmf/restjobs/jobs/ Content-Type:application/json CDE4 2013 IBM Corporation
Filename: zOS V2R1 zOSMFAsynchronous Notification for Job completion The user is able to provide a URL when submitting the job. The URL will be sent an HTTP message when the job has completed. This support is JES2 specific. Example:–Submit a job with notification URL:–PUT lete Job Completed JSON Object ype":1,"completion-code":0,"retcode":"CC 0000"} 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to Incident Log The z/OSMF Incident Log application allows you to modify its default JCLto meet the needs of your organization (It is available on z/OS V1R13 withthe PTF UK83842) The z/OSMF Incident Log application is extended to use enhancedFTP.DATA Support in V2R1 PDUU. PDUU Enhancement in V2R1 expands the TARGET SYS parameter toaccept up to 256 characters. This new function is intended to support thisPDUU enhancement in V2R1. In addition, the supported HLQ length of diagnostic data is extended to 8characters. 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to Resource monitoring and Workload Management The z/OSMF Resource Monitoring application is linked to the z/OSMF WorkloadManagement application in context, and the z/OSMF Workload Managementapplication is linked to the z/OSMF Resource Monitoring application. The System Status task is linked to the Workload Management task such that theactive service definition, active service policy, or WLM status can be opened andviewed. The Workload Management task is linked to Resource Monitoringdashboards such that while viewing the active service definition or service policy,resource monitoring dashboards with performance metrics for service classes,workloads, and report classes can be opened and viewed. This function is available on z/OSMF V1R13 With PTF UK83833 and PTFUK83836. In V2R1, z/OSMF Resource Monitoring is enhanced to monitor the performance ofWindows on System x. In V2R1, z/OSMF Workload Management is enhanced to support new functionlevel of service definition for z/OS WLM 2013 IBM Corporation
Filename: zOS V2R1 zOSMFView performance of Active policy 2013 IBM Corporation
Filename: zOS V2R1 zOSMFView active service definition 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to Capacity Provisioning The z/OSMF Capacity Provisioning application is enhanced to allow you to create,edit, and activate domain configurations and capacity provisioning policies.(Available on V1R13 with PTF UK83852)– With these new functions z/OSMF Capacity Provisioning supports all thefunctions available in the Microsoft Windows-based Capacity ProvisioningControl Center (CPCC). In V2R1, it requires the z/OSMF Capacity Provisioning task for managingthe z/OS Capacity Provisioning Manager (CPM) z/OSMF V2R1 Capacity Provisioning also supports the latestenhancements in the Capacity Provisioning Manager Defined Capacity and Group Capacity management capabilities Can be increased and decreased via z/OSMF based on yourschedules or the workload running on your system. Allows you to define additional scopes and limits to reflect yourbusiness needs for additional Defined Capacity or Group Capacity. 2013 IBM Corporation
Filename: zOS V2R1 zOSMFEnhancements to Configuration Assistant for z/OS Communications Server This function is redesigned for new and improved web user experience andperformance Redesigned panels provide a new look and feel that tightly integrates with z/OSMFand other plug-ins Improved performance due to execution of more function in the browser ratherthan on the host With V2R1, Windows download will no longer be provided, users must migrate toz/OSMF New function provided in support of V2R1 z/OS Communications Server PolicyBased Networking– AT-TLS support of TLS V1.2– Policy-based Routing (PBR) support for IPv6 2013 IBM Corporation
Filename: zOS V2R1 zOSMFV2R1 Configuration Assistant 2013 IBM Corporation
Filename: zOS V2R1 zOSMFOther recent enhancements The z/OSMF ISPF application is enhanced to get the completion status of long running commands,without any user intervention (PTF UK83828) With PTF UK83825 on z/OSMF V1R13, the Systems and FTP Servers tasks are available under z/OSMFSettings.– The Systems task allows you to define the settings required for z/OSMF to access other systems inyour installation and to define the HTTP proxy settings for z/OSMF to use when establishing anHTTPS connection to another system.– The FTP Servers task allows you to define the settings required for z/OSMF to access the FTPservers that are running on internal or external systems and to define the settings for z/OSMF to usewhen transferring files between systems. Usability: Additional filter capabilities are designed to improve ease of use for the user. The z/OSMF tablefiltering support has been enhanced to allow for AND/OR filtering as well as case sensitive filtering formore granular filtering capabilities (PTF UK83825) 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF WAS Liberty support Evolution of z/OS Management Facility configuration New and simplified z/OSMF ecurity 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF configuration evolution z/OSMF V1R11– z/OSMF includes WebSphere OEM and z/OSMF apps– Separate setup required for each, with similar steps– CIM server setup included, and non-optimal– Phase 1 fixpack included many changes – collapsed 11 distinct script invocations to 3with the same script. z/OSMF V1R12– Separated CIM setup, only emitted CIM security setup if requested– Improved CIM setup instructions– Added new plug-ins, all plug-in setup now optional– Security setup enhanced, simplified z/OSMF V1R13– Added new plugins– Security updates – authorization modes, roles, groups z/OSMF V2R1– Eliminate WebSphere OEM package and separate setup– Single stream configuration, 1 setup only– Improved performance, reduced resources 2013 IBM Corporation
Filename: zOS V2R1 zOSMFPackage New product package 5610-A01–WAS OEM is now removed from z/OSMF (HBBN700)–z/OSMF product package is much smaller in size–WAS Liberty Profile is part of z/OSMF package File systems:–Product file system /usr/lpp/zosmf/V2R1–Data file system /var/zosmf/data Other directories:–Configuration file system by default wil be in /etc/zosmf–Logfiles by default in /var/zosmf/configuration/logs–Data file system mount point by default will be /var/zosmf/data Recommended size – is documented in Program Directory for product filesystem and in Configuration Guide for data file system 2013 IBM Corporation
Filename: zOS V2R1 zOSMFSimplified Configuration z/OSMF setup to no longer require two separate configurations forruntime(WASOEM) and application(z/OSMF); it is reduced to one Fewer overall prompts and variables JAVA 1.7 64 bit SR3 is required (pre-req) Configuring z/OSMF–Option 1 Configure z/OSMF core Perform pre-req setup for all/selected plugins (optionally using workflow) Add all/selected plugins as required or as ready–Option 2 Complete pre-req setup for all/selected plugins Configure z/OSMF which includes core and all/selected plugins 2013 IBM Corporation
Filename: zOS V2R1 zOSMFSimplified Configuration z/OSMF configuration is collapsed, with fewer steps:1)izusetup.sh –file izuconfig1.cfg –config2)Security setup Verify security setup3)izusetup.sh –file izuconfig1.cfg –finish No longer require separate deployment of applications Support default TCPIP Port for HTTP communication http port 80 and https port 443 Note: https port preserved on migration, http port default set to 80 z/OSMF intends to exploit the z/OSMF workflow for z/OSMFconfiguration. V2R1 delivers stage 1 of the configuration workflow.This workflow covers the pre-requisite z/OS system setup for theplugins. The steps are mainly manual steps. 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF improved service and performance Simplified service; follow the normal z/OS model;–Perform normal SMPE receive/apply and restart z/OSMF to pick upnew service.–Separate step not required for activation (i.e. No izusetup.sh –fileizuconfig1.cfg –service step) Improved performance–Faster configuration since there is no longer any deployment of appsnor data movement–Faster startup (few seconds instead of minutes)–Reduced memory requirement Package footprint reduced to 1/3 of previous release Memory requirement reduced to half of previous release 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF V2R1 Security Only support SAF authorization mode–Requires ZMFAPLA class be enabled Removed separate z/OSMF administrator id (default was ZOSMFAD)–Since V2R1 only supports SAF authorization mode, this ID is notlonger needed–Still require that an id be authorized to z/OSMF during configuration Add–z/OSMF server started task id (Used for STARTED definitions)–z/OSMF unauthenticated user id (Similar to the id WAS OEM had)–Include setup of the necessary certificates and keyring for SSL–Create a Certificate Authority(CA) by default, and server cert (selfsigned) Optionally can choose not to create a CA– Useful for multiple z/OSMFs in the enterprise– Hardware crypto support is built in 2013 IBM Corporation
Filename: zOS V2R1 zOSMFz/OSMF release migration There will be a migration support for upgrading z/OSMF from prior releases– the administrator would need to run a series of scripts.1)Migrate the configuration and optionally the override file izumigrate.sh2)Establish the new configuration file and resolves any new references added inV2R1 like the z/os security administrator role or references for Liberty. izusetup.sh –config3)In V2R1, a new setup for Liberty security is required. In addition, we’ll remove theRepository authorization mode Everyone will need to be in SAF mode.4)Complete all configuration actions izusetup.sh –finish 2013 IBM Corporation
Filename: zOS V2R1 zOSMFIBM Present
Material is current as of May 2013 2013 IBM Corporation Item: New Release Content Element/Component: z/OS Management Facility IBM Education Assistance for z/OSMF V2R1File Size: 1MB
