Overview of what is new in V7.0
WebSphere Business Process Management WebSphere Process Server for z/OS V7.0 Overview of what is new in V7.0
This presentation provides an overview of features that are new in WebSphere® Process Server for z/OS® Version 7.0. It will focus on the items that are specific to z/OS. Other presentations are available to look at the new functions in version 7 that are common to all platforms.
Agenda
Agenda What is new in WebSphere Process Server for z/OS, V7 Move towards a common install framework WebSphere Customization Tools function continues to be enhanced for WebSphere Process Server Enhancements to database creation Streamlined network deployment configuration
Some areas of focus for version 7 have been a move towards a common install framework, better WebSphere Process Server integration with the WebSphere Customization Tools, enhancements to help with database creation and streamlined network deployment configuration. You will look at each of these areas briefly on the next slides.
Common install framework
Common install framework Provides an integrated experience for all z/OS Business Process Management products Most noticeable change is the name of the installation script has changed to be consistent with other products For instance, WebSphere Business Fabric uses zWBSFInstall.sh Pre-V7 Version 7 zSMPInstall.sh zWPSInstall.sh zWESBInstall.sh
As more products are included in the Business Process Management stack, you will notice a common way to install these products. Work was done in WebSphere Process Server for z/OS Version 7 and WebSphere Enterprise Service Bus for z/OS Version 7 to better align with a common install framework as part of the Business Process Management stack. The most noticeable change to users is the name of the installation script used to install WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS. You will no longer call the zSMPInstall script but instead you will call zWPSInstall or zWESBInstall, depending on the product you are installing.
WebSphere Customization Tools function
WebSphere Customization Tools function Improved integration with the WebSphere Process Server for z/OS and WebSphere Enterprise Service Bus for z/OS installation Cleaned up for better installation experience Profile Management Tool (PMT) for z/OS will create JCL jobs that can be uploaded to z/OS for configuration Before Version 7, the PMT only created a response file Tentatively scheduled for completion in a 1Q2010 FixPack
WebSphere Process Server for z/OS V6.2 and WebSphere Enterprise Service Bus for z/OS V6.2 were the first releases to make use of the WebSphere Customization Tools for configuration of the products. Version 7 has cleaned up the process used to configure the products using the Profile Management Tool piece of the WebSphere Customization tools to allow for a better installation and configuration experience. In doing this, the release was also able to take advantage of general product family improvements in the Profile Management Tool configuration that are included in version 7 as well. A big change to the Profile Management Tool for z/OS is the added capability to generate JCL jobs that can be uploaded to z/OS to complete the configuration of the product. Before version 7, the output from the tool was a tailored response file that needed to be uploaded and included as a parameter as part of running a shell script. These shell scripts will now be wrappered in JCL that is tailored to include the response file that is created. This is similar to the WebSphere Application Server for z/OS configuration and the configuration of other products installed on top of the WebSphere Application Server for z/OS.
Enhancements to database creation
Enhancements to database creation DbDesignGenerator.sh -- New tool for database design Select the topology you are using (1)wesb.nd.topology (2)wesb.Stand-alone (3)wps.nd.topology (4)wps.Stand-alone Individually design needed components (1)[CommonDB] WBI_CommonDB : [master] [status = not complete] (2)[BPCReporting] WBI_BPCEventCollector : [status = not complete] (3)[BPC] WBI_BPC : [status = not complete] (4)[CEI] WBI_CEI_EVENT : [status = not complete] (5)[BSpace] WBI_BSPACE : [parent = WBI_CommonDB] [status = not complete] (6)[SibMe] WBI_BPC_ME : [parent = WBI_CommonDB] [status = not complete] (7)[SibMe] WBI_CEI_ME : [parent = WBI_CommonDB] [status = not complete] (8)[SibMe] WBI_SCA_APP_ME : [parent = WBI_CommonDB] [status = not complete] (9)[SibMe] WBI_SCA_SYS_ME : [parent = WBI_CommonDB] [status = not complete] (10)[save and exit] Found in /util/dbUtils
Another area of improvement in version 7 is in database creation and configuration. A new tool, DbDesignGenerator, is being provided to help in the design of the databases needed for various components of the WebSphere Process Server and WebSphere Enterprise Service Bus products. This allows the database configuration to proceed in parallel once the zWPSInstall or zWESBInstall scripts have been run, thus allowing for better separation of responsibility between the database creation and WebSphere Process Server configuration roles. The DbDesignGenerator shell script is found in the util/dbUtils directory under the WAS_HOME directory. It is an interactive tool that prompts you for the various information it needs to create the SQL that you need to run in order to use the products. One of the first things it asks about, as shown on the slide, is the topology that you are configuring. You can then go through each component that you plan to configure and input the needed information for your particular database system. The WBI_CommonDB configuration is required before doing any other. It is considered the ‘master’ component. Other components show a ‘parent’ which you must design before tackling that component.
Enhancements to database creation, continued
DbDesignGenerator.sh -- New tool for database design (continued) Select database type (1)DB2-distributed (2)DB2-iSeries (3)DB2-zOS-8 (4)DB2-zOS-9 (5)Derby-embedded (6)Derby-networkServer (7)Informix (8)Oracle (9)SQL Server Prompts you for relevant values (data source properties as well): [info] Please enter the values for the properties in the database objects section. Database name[default=WPRCSDB] :S7CELLDB Database User name[default=] :DB2D Database Location on zOS system[default=] :MVS225D1 Database schema[default=] :S7CELL Bufferpool of 4K size[default=BP1] : Bufferpool for INDEX data[default=BP2] : Bufferpool of 4K size for LOB data[default=BP3] : Bufferpool of 8K size[default=BP8K0] : Bufferpool of 16K size[default=BP16K0] : Bufferpool of 32K size[default=BP32K] : Storage group name[default=] :S7DBSTO Generates SQL and a ‘dbDesign’ file Enhancements to database creation, continued
One of the next pieces of information that you are asked to provide is the database type. You will notice that DB2® for z/OS Versions 8 and 9 are highlighted here. The prompts on the bottom of the slide are then customized to that database product. For instance, in the case of DB2 for z/OS, it will ask you for the database location name. Once the tool has all the necessary information, it will generate the SQL for you which you can the pass to your DB2 administrator if need be. It will also create a ‘dbDesign’ file that has all the database information you provided and can be used in your configuration later. It can be edited, as needed, if you want to use it as a starting point for a new cell or to correct any mistakes that were made. It is not shown here on the slide, but the tool will also prompt you for a location to save the SQL and the dbDesign file.
Enhancements to database creation (continued)
Enhancements to database creation (continued) createDB.sh will use the output from the DbDesignGenerator in V7; must run DbDesignGenerator first! createDB.sh used to run SQL now SQL must be generated in default locations Ddl2Pds.sh is a new tool to help with shifting and codepage translation of generated DDL/SQL into a PDS Copies DDL/SQL into a PDS for you By component name (for instance, WPS or BPC), by directory, or by a specific file name Allows you to easily run the DDL in a z/OS environment with SPUFI, DSNTEP2 and so on Found in /usr/lpp/zWPS/V7R0/zos.config/samples
createDB.sh is still available in V7 to run the SQL that is generated from the DbDesignGenerator tool, however it is no longer responsible for the creation of the SQL and DDL files. If you plan to use createDB to configure your databases and tables, then you MUST run DbDesignGenerator first. This is a change from prior releases. Also, in order for the createDB shell script to find the SQL that it will run, the SQL must be generated to the default locations in DbDesignGenerator. Another new tool, Ddl2Pds, is provided to make it easier to move the generated SQL or DDL from the HFS over to the z/OS environment. It will move the generated DDL or SQL into a PDS where you can use it to configure the databases and tables using tools such as SPUFI or DSNTEP2. It is found as a sample in the zos.config directory. Using the Ddl2Pds tool, you can copy files into a PDS by component name, by directory or by a specific file name.
Enhancements to database creation (continued)
Enhancements to database creation (continued) Output from the DbDesignGenerator can be used in profile creation
As mentioned previously, one of the outputs from the dbDesignGenerator script is a dbDesign file. That file can be used for profile creation if you specify that you want to use it in the Profile Management Tool as shown on the slide. If you do not specify a design file in the screen shown here, you are prompted for the database values such as location name and schema name on the next screens. With the output from the DBDesignGenerator, all the information is automatically read and will match the database configuration itself which is less error-prone.
Streamlined network deployment configuration
Streamlined network deployment configuration Deployment environments allow you to more easily configure a network deployment topology
Before version 7, configuring a network deployment environment entailed many manual steps to configure each component you planned on using. With WebSphere Process Server for z/OS Version 7, this is made easier with the deployment environment configuration. The database screen is shown here on the slide but you see there are a few more steps that you are taken through. In the end, it will create your entire topology with the selected components configured for you which is much simpler than prior releases of the product.
Summary
Summary Improved installation experience! WebSphere Process Server for z/OS Version 7and WebSphere Enterprise Service Bus for z/OS Version 7 continue to make improvements Common install experience with other BPM products Improved capability using the WebSphere Customization Tools Improved database design integration Improved network deployment configuration experience
Overall, WebSphere Process Server for z/OS Version 7 and WebSphere Enterprise Service Bus for z/OS Version 7 introduce improvements to the configuration process. This is seen in a common installation experience with other BPM products and improvements in areas such as the use of WebSphere Customization Tools, integration of the database configuration and better network deployment configuration.
Feedback
Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WBPMCv70_WPSzOS_WhatsNew.ppt This module is also available in PDF format at: ../WBPMCv70_WPSzOS_WhatsNew.pdf
You can help improve the quality of IBM Education Assistant content by providing feedback.
Trademarks