WebSphere Application Server V4.0 for z/os and OS/390

Transcription

1 IBM ^ zseries Introduction March 13, 2001 WebSphere Application V4.0 for z/os and OS/390 Frequently Asked Questions (FAQ) Worldwide

2 WebSphere Application V4.0 for z/os and OS/390 What did IBM Announce? IBM announced WebSphere Application V4.0 for z/os and OS/390 (WAS V4.0). This product introduces the Java 2 Platform, Enterprise Edition (J2EE) architecture to z/os and OS/390. IBM s WebSphere Software Platform provides an infrastructure that allows companies large and small to take advantage of explosive Internet growth opportunities. The WebSphere Software Platform is anchored by WebSphere Application s that provide the core J2EE architectural support for the deployment of applications. WAS V4.0 for z/os and OS/390 provides customers with the highest Qualities of Service from their J2EE application server running on the IBM ^ zseries or S/390. What are the products supporting this announcement? On March 13th, 2001 IBM announced both the IBM WebSphere Application Version 4.0 for z/os and OS/390 as well as the IBM CICS Transaction Version 2 for z/os. WebSphere Application V4.0 for z/os and OS/390 is an e-business application deployment environment built on open standards-based technology. WAS V4.0 is the key WebSphere Application providing support for Servlets, Java Pages (JSPs), and Enterprise Java-Beans (EJBs), in compliance with J2EE specifications levels for the zseries and S/390. WAS V4.0 provides the full breadth of services required of an application server. It delivers J2EE-compliant levels of key component technologies Java Pages (JSPs), Servlets, and Enterprise JavaBeans (EJBs) within an integrated runtime that is aligned with WebSphere family J2EE specification levels. This platform-neutral programming model provides the WebSphere developer a consistent experience regardless of deployment platform, while the WebSphere deployer is assured that applications can be moved from platform to platform to match quality of service objectives without requiring any changes to the application. Furthermore, new applications can be integrated with the extensive inventory of existing OS/390 applications. The result is the rapid creation of production-ready e-business applications, along with the ability to evolve to the Enterprise JavaBeans or CORBA-based deployment model of choice. CICS Transaction for z/os Version 2 (CICS TS V2) is an EJB server supporting the EJB 1.1 run-time specification. CICS TS V2 delivers major enhancements which strengthen its support for e-business applications. It provides new functions that support industry-standard Enterprise JavaBeans (EJBs) technology and provides a major range of functions available for applications written in other programming styles. CICS provides a run-time optimized for running business logic written as EJBs alongside business logic written in traditional languages such as COBOL. This enables enterprises to continue to take advantage of their investment in traditional AD practices while growing their investment in Enterprise Java AD practices, choosing when to use which technology within the single CICS run-time environment.

3 When will these products be available in the US? In other Geographies? Both WAS V4.0 and CICS TS V2 will be generally available worldwide on March 30, What is the price of the WebSphere Application V4.0 for z/os and OS/390? This product is licensed under the IBM Program License Agreement (IPLA), providing for a basic license with ongoing access to versions/releases and technical support for a separate fee. The WebSphere Application V4.0 for z/os and OS/390 basic license is offered at $35,000 One Time Charge (OTC) per Central Processor (engine) on an IBM ^ zseries or S/390 server. This product will be available through standard S/390 software ordering and fulfillment processes. Please note prices are subject to change without notice. Contact your local IBM representative or Business Partner for the most current price in your geography. A separate recurring annual charge is mandatory for enhanced support that includes telephone assistance (voice support for defects during normal business hours) as well as access to updates, releases, and versions of the program as long as support is available. This provides defect support equivalent to that provided via the IBM Customer Agreement (ICA) license. The annual price of the Software Subscription and Support for WAS V4.0 is equal to $7,000 multiplied by the number of licenses (engines). S/390 Support Line is an option for those customers who desire added services. For additional information call the IBM Support Family Information Center at First IBM changed the pricing of WebSphere. Why did IBM now change the licensing agreement? What does it mean to me? IPLA is a perpetual license, transferable across borders and S/390 systems, while ICA is a rental license to a specific system/sysplex and not transferable across borders. The advantages for IPLA include terms that are consistent with competing offerings and, offer more flexibility than ICA terms for movement among machines and geographies. The long term strategy for the WebSphere family is to provide customers with the ability to move their WebSphere use entitlements between platforms. WebSphere is offered on a cross-platform basis, and customers need the flexibility to redeploy their use entitlements as business needs change. In order to achieve this, we ultimately intend to provide a platform neutral set of T's and C's. zseries and S/390 customers have unique requirements with respect to service levels and product delivery, and these requirements will be incorporated into the new model. What are the functional improvements in WAS V4.0 being announced and delivered over what is already available?

4 The major functional enhancements in WAS V4 for z/os and OS/390 is a J2EE compliant run-time environment. Support for deployment of J2EE include: Deployment of EJB Version 1.1 specification level Other J2EE Services provided by the associated Software Development Kit 1.3.0: Remote method invocation (RMI) using Internet inter-orb protocol (IIOP) Object by value Access to J2EE services from Java Business Objects Java Transaction API (JTA) New IMS APPC and CICS EXCI connectors to support the J2EE Connector architecture and implement the Common Client Interface (CCI) Integrated run-time What are the customer benefits of Enterprise JavaBeans? Enterprise JavaBeans technology is a model for the development and deployment of reusable Java server components. This component model allows application developers to focus on developing business logic without having to spend time on transaction management or learning the interfaces of complex transactional systems. This reduces the need for scarce skills, programmer labor costs, and time to market. EJBs also allow for better management of code, and reusability of code across multiple platforms. EJBs deployed on the z/os and OS/390 platform provide the highest qualities of service production environment for companies who need new business logic to be tightly integrated with back-end resources. What are the customer benefits of having a J2EE single runtime? Application programmers can now design, develop and assemble Java components and applications, using a common industry-standard programming model, without having to account for the peculiarities of any platform or checking lists of platform differences or restrictions. The decision of where to run a J2EE application can now be based on qualities of service, the availability and location of data and the availability of computing resources, not on the platform knowledge or skills of the application programmers. Applications that ultimately run in the z/os or OS/390 environment can be developed, compiled, assembled and tested in the same graphical workstation environment and the same integrated development environment as applications that will run elsewhere. With this development process, the decision of where to run an application doesn t need to be considered permanent. What are the differences in versions, channels, and packaging from what is already available? Some of the base operating system and specification levels of WebSphere Application s for the z/os and OS/390 platforms include the following:

5 Versions 1.1/ SE 3.02 EE 3.5 SE New 4.0 GA Date NA 6/30/00 6/30/00 1/26/01 3/30/01 OS/390 Pre-Req V2R5 V2R7 V2R8 V2R8 V2R8 SDK SDK SDK SDK 1.3 SDK 1.3 JSP/ Servlets JSP V.91, Servlet V2.01 JSP.91 or 1.0, Servlet 2.1 JSP 1.0, Servlet 2.1 JSP 1.0/1.1, Servlet 2.1/2.2 JSP 1.1, Servlet 2.2 DB2 V5 V5 V6 V5 V7 EJB None None V1.0 prelim None V1.0 & V1.1 EOS Date 3/31/02 3/31/02 3/31/02 Not Announced Not Announced WAS V4.0 will continue to be sold through our IBM direct sales as well as IBM Business Partner channels, and be shipped through Customized Offerings (Pac, CBPDO, SystemPac, etc.). What education is available for WebSphere Application V4.0 for z/os and OS/390? Customers who are interested in reviewing information to introduce them to WebSphere Application V4.0 for z/os and OS/390 can start by visiting the IBM Software Group's WebSphere Application Web site at ibm.com/software/webservers/appserv/. This site provides a wide variety of information about the capabilities of WebSphere as an e-business application deployment environment. By selecting the Education menu item you will see that IBM has several educational options available to you. From classroom courses to on site assistance and Internet-based training, if you're ready to learn we're ready to teach. Once you are ready to begin implementing the WebSphere Application V4.0 for z/os and OS/390 runtime environment, there are two IBM Learning Services classes necessary for a successful implementation: H4061 Introduction to WebSphere Application V4.0 for z/os and OS/390 (1 day) H4062 WebSphere Application V4.0 for z/os and OS/390 Implementation and Deployment Workshop (3.5 days) All students should have an introductory knowledge of the WebSphere Application and z/os (and/or OS/390). Details for the classes can be found at ibm.com/services/learning/us where you can enroll, or call IBM-TEACH. (IBM employees can go to w3.education.ibm.com.) Get your e-business project going with Web-enablement workshops: To help customers expedite the deployment of J2EE (Java 2 Enterprise Edition) compliant projects on z/os and OS/390 using WebSphere Application Version 4, IBM will soon begin offering free workshops to qualified customers. Students will learn how to:

6 configure WebSphere Application Version 4 for z/os and OS/390 deploy Enterprise Java Beans, JSPs and/or Servlets, and connect the Java components to DB2, CICS or other back end resources. This workshop will help you gain valuable skills and demonstrate how easy it is to deploy EJB applications in a production environment on z/os and OS/390. Attendance in this workshop will help you accelerate the implementation of Web-based applications within your enterprise. If you are planning to build and deploy advanced e-business applications using EJB technology within your enterprise within the next sixth months, then you will want to qualify for this unique opportunity now. For more information or to see if you qualify, contact your local IBM representative or visit s390.ibm.com/e-business/webwfhp.html Are there any IGS services available to support my migration to these products or other methods of technical support? IBM Global Services Offerings: Performance Management and Capacity Planning Services for OS/390 s: This service provides analysis of OS/390 systems supporting server implementation. Our experts can help improve the performance of your OS/390 operating systems by identifying performance problems or capacity exposures. To help you plan for the system resources required to support your servers, we can model configurations based on your projected business growth and performance objectives. Upon completion of the performance analysis or capacity planning service, you are provided a documented report of the findings and recommendations. For more information, visit IBM Performance Management and Capacity Planning Services at: ibm.com/services/ism/performance/ Smooth Start/Installation Services: SmoothStart Services, an on-site implementation and training startup service, is designed to accelerate the productive use of your IBM solution. The service is provided by IBM Global Services or your IBM Business Partner at an additional cost. IBM SmoothStart services for z/os and OS/390 servers provide installation, configuration and customization of your HTTP and WebSphere Application software on the zseries and S/390 platforms. Our services use the most current releases of IBM HTTP for OS/390 and WebSphere Application to customize your established host system component software and create an initial home page with up to four additional pages. For more information, visit IBM SmoothStart Services for OS/390 s: ibm.com/services/its/us/mus63a1.html Technical Support: Technical support is provided by local Field Technical Support Specialists and Advanced Technical Support IBM Washington Systems Center. Additional support is also available through the Worldwide Question and Answer (WWQA) QAAuthor function on ViewBlue or EHONE. Has IBM announced End of Marketing (EOM) and End of Service (EOS) for other levels of the WebSphere Application server for the zseries and S/390?

7 Yes. WAS V1.1 and V1.2 will no longer be available for download as of March 31, In addition, IBM has announced EOM for WebSphere Application V3.02 SE and V3.02 EE effective December 31, Orders for these products will not be accepted after the stated effective dates of withdrawal. Normal marketing activities and educational support will not be available unless a previous agreement exists between the customer and IBM. End of Service for these products will be March 31, How does this product announcement relate to the WebSphere Family (WebSphere on Distributed Platforms)? WAS V4.0 delivers interlock with the WebSphere family in terms of providing J2EE-compliant SDK, JSP, Servlet and EJB support. By providing a run-time for the same core J2EE standards as the WebSphere family, customers will have a path for migrating J2EE-compliant applications to zseries and S/390 servers. Who are the main competitors to WAS V4.0? The primary z/os and OS/390-based competitor to WAS V4.0 is BEA Systems with their WebLogic Enterprise (WLE) product. BEA ported their product from UNIX to OS/390 with the assistance of the S/390 Porting Center. In contrast, WAS V4.0 is not ported code; it was designed for OS/390 from the start and takes full advantage of the advanced functions and features of OS/390. What is the link to the overall WebSphere family strategy? IBM s WebSphere Foundation family of products provides a highly secure, reliable and scalable environment for building and managing a broad range of advanced e-business applications. Through WebSphere Application s, which deliver best-of-breed, standards-based platform services and one of the industry s most advanced transactional Application Software, the WebSphere foundation provides an environment for the rapid development and deployment of flexible e-business applications. The WebSphere Foundation products currently include Standard, Advanced and Enterprise Editions available on Microsoft Windows NT, Windows 2000 server, AIX, HP/UX, Sun Solaris, LINUX, AS/400, and OS/390. WAS V4.0 is an important part of the WebSphere foundation family of products. This release provides a robust application server environment for customers who demand all the advantages of the WebSphere family combined with the hallmark qualities of service of only the zseries or S/390. This product extends IBM s reach in the WebSphere family to truly allow end-to-end integration of systems and services to enable development of sophisticated, reliable, scalable e-business solutions.

8 Where can I find more information on the announcement? For more information, please visit: e-business is Spreading Like a wild fire s390.ibm.com/e-business/webwfhp.html WebSphere Application Home Page ibm.com/software/webservers CICS home page: ibm.com/software/ts/cics/ What is packaged with WebSphere Application V4.0 for z/os and OS/390? WebSphere Application V4.0 for z/os and OS/390 is delivered as a single offering, along with SDK It includes the following elements as part of its deployment environment and support for deployment of J2EE: Deployment of EJB Version 1.1 specification level Deployment of Java Servlets written to the JavaSoft Version 2.2 spec level Deployment of JSPs written to the JavaSoft Version 1.1 specification level Remote method invocation (RMI) using Internet inter-orb protocol (IIOP) Object by value Access to J2EE services from Java Business Objects Java Transaction API (JTA) New IMS APPC and CICS EXCI connectors to support the J2EE Connector architecture and implement the Common Client Interface Integrated run-time Highly secure deployment environment with Kerberos as the backbone and SSL as the endpoints Java RAS services integrated with existing RAS services and quality of services for z/os and OS/390 Supports inter operability with: - WebSphere Application for distributed platforms - CICS ORB - Other non IBM vendors such as VisiBroker and Orbix Compliance with industry standards for CORBA, 2.1 specification level SDK is shipped with WebSphere Application V4.0 for z/os and OS/390. This SDK provides the base support for applications at the Java 2 API level. You can use this level or one already installed at a higher service level. What are the hardware and software prerequisites for WAS V4.0? Any hardware that supports the OS/390 operating system V2 R8, or later. Binary floating point hardware, such as S/390 Parallel Enterprise Generation 5 or higher systems, are highly recommended. Systems without binary floating point hardware, currently running applications on WebSphere Application V3.02 for OS/390, should consider a hardware upgrade before upgrading to WAS V4.0.

9 The following OS/390 elements, features, and components are required and must be installed, enabled, and configured: OS/390 V2 R8, or later, or z/os IBM HTTP for OS/390 Lightweight Directory Access Protocol (LDAP) OS/390 Communications (TCP/IP) OS/390 UNIX System Services and the hierarchical file system (HFS) SecureWay Security (RACF ) or equivalent security management product System Logger System SSL Security Workload management in goal mode Resource recovery services FTP server IBM DB2 Universal Database for OS/390 and z/os, Version 7 (may coexist with existing levels of DB2 used by other applications) CICS Transaction ; if your application environment uses CICS, then CICS Transaction for OS/390 V1R3, or later, is required for CCF or PAA connectivity. IMS: If your application environment uses IMS, IMS V5R1, or later, is required. If PAA is used, IMS V6R1, or later, is required. Application development and site development tools such as the following are optional: WebSphere Application (distributed version) VisualAge for Java Object Builder WebSphere Studio Does sysplex support WebSphere Application V4 for z/os and OS/390? WebSphere Application V4 for z/os and OS/390 has FULL sysplex support. It rivals traditional zseries and S390 application deployment environments with its sysplex capabilities. This includes its abilities to support replicated instances of itself across the sysplex (or on the same system), with multiple levels of workload balancing, access to shared data, and single system image. What is the WebSphere Application V4 for z/os and OS/390 development environment? Currently the WebSphere development environment runs on a Windows based platform. This includes Visual Age for Java 3.5 and WebSphere Studio for web content delivery. The IBM tooling solution for Enterprise beans assumes that the Enterprise beans will be developed in VAJ, and the WebSphere Test Environment will be used to perform basic unit test of the business logic provided in the beans being developed. This will potentially require scaffolding of the access to data, and other beans that are required in the application.

10 How do you do component test on WebSphere Application V4 for z/os and OS/390? Component test involves the joining of several beans together into logical components, providing them access to data, and testing them together as a unit. While this can be done on 390, most of our current installations perform this level of testing using a distributed platform such as Windows 2000 running WebSphere Advanced Edition. This allows a small team of developers to join the pieces of code that they have developed together and test the interactions. This level of test is still not directly testing platform functions and features, but focusing on the individual beans and the relationships between them. How do you do functional test on WebSphere Application V4 for z/os and OS/390? Function test involves joining the various components together, connecting them to test data in the target database, and validating the function that the application will provide. Where this test is performed is dependent on what the function is, and what its data requirements are. If the target deployment platform is z/os, then it may make sense to do this level of testing on zseries or S390. This is possible by setting up one or more test servers with in the sysplex that the application will be deployed in. When the application is installed into the test server, the installer will define where in the JNDI directory that the references to the application will be stored. The test clients will need to be configured with this information that tells the clients where the test application is located. The test clients will then drive requests against the test server and the application is functionally tested. Remote debugging tools can be used to diagnosis any problems encountered. What type of system testing do I need to do? Before a customer application is put into production on z/os, the code should be deployed into a WebSphere Application V4 for z/os and OS/390 server and tested. Some customers attempt to bring up the application and simulate a real load on the application. The important point here is that the code needs to run on zseries or S390 before it goes into production. In order to do this, an additional test server needs to be defined and the application configured to it. It is possible to have different levels of the application installed within the same sysplex, inside different test servers (one level for functional test, one for system test, and one for production). When they get installed, the beans that are part of the application should be registered in a different subtree of the JNDI directory (this occurs by default). The test clients need to be configured to the version of the application that is being tested and the tests run.

11 When can I put WebSphere Application V4 for z/os and OS/390 into production? The application can be installed in a Production WebSphere Application V4 for z/os and OS/390 server after you are satisfied with the functional and system testing. The difference between a production server and a test server is whether the remote debugger is allowed to be attached. It is not normally acceptable for a production workload to be stopped because someone flowed a remote debug request to it. The testing phase and the platform where they are performed are as follows: Unit test Component test Functional test System test Production Development platform What type of configuration risks are there? Deployment Platform It is technically possible to be running functional test, system test, and production on the same system, or within the same sysplex. The question is what risk is the customer willing to taking when running both production and testing in the same sysplex, and this is entirely dependent on the customer. In order to analyze the potential risks you need to understand the WebSphere Application V4 for z/os and OS/390 topology. Scenario 1 A single system view is illustrated. In this picture, production and test shared the hardware, the operating system and associated products, the server instance and its shared repository, the daemon instance, and the HFS file system that contains the data for the application. The test applications have the potential to damage the elements that are shared between the test and production server. The access between the two servers are mediated by system code, so the risk is low to moderate. System Daemon SR Test App SR Production App SR

12 Scenario 2 In this figure, a single sysplex is used, but the production and test servers are placed on separate systems in the sysplex. The following are shared: the shared state that is kept by the instances of the server to manage the WebSphere Application V4 for z/os and OS/390 node and the shared HFS file system that contains the executables for the application (it is recommended that it only be writable from the server which is authorized code). This shared state is mediated by authorized system code, but it is still shared, and the risk is low/moderate. Daemon System Daemon SR Shared State SR Test App SR SR Production App Scenario 3 Placing the test and production server in separate sysplexes, eliminates all local sharing between the test and production servers and provides the ultimate risk reduction possible. For those that require 100% availability, it eliminates the risk caused by including production and test running in the same server. Daemon System Daemon SR Shared State SR Test App SR SR Production App

13 Why does WebSphere Application V4 for z/os require DB2 for OS/390 V7.1? WebSphere Application V4 for z/os and OS/390 V4.0 must pass the J2EE 1.2 compliance test suite (requiring a JDBC 2.0 compliant driver) and provide support for "Local Transaction Support". This function is provided in DB2 V7.1. Both of these items are necessary for WebSphere Application V4 for z/os and OS/390 to achieve J2EE compliance and production quality. DB2 (V7.1) has the ability to coexist in a sysplex with DB2 V5.1 or DB2 V6.1, but it can only coexist with one or the other. It is possible to have a DB2 7.1 subsystem and a DB2 5.1/6.1 subsystem to share the same customer data. Since almost all of our customers have installed WebSphere Application V4 for z/os and OS/390 on a separate set of LPARs, it should be possible for them to install DB They can then share data with their current production DB2 V5.1/6.1 databases by placing this WebSphere system in the same sysplex as the production DB2 databases. In order to explain this a little better, assume the following configuration: It will be possible to insert a new system into the sysplex, which is running DB2 V7.1 in the same DB2 datasharing group as the existing DB2 V5.1 subsystems. This would allow new J2EE applications to reuse the data associated with preexisting applications either directly through DB2 or via wrappering the existing applications which gets the data from DB2. OS/390 R8 OS/390 R8 CICS Customer App CICS Customer App DB2 V5.1 DB2 V5.1 DB2 Data

14 OS/390 R8 OS/390 R8 OS/390 R8 CICS Customer App CICS Customer App WebSphere/390 DB2 V5.1 DB2 V5.1 DB2 V7.1 DB2 Data If the customer is unwilling to share the DB2 data between their existing applications and WebSphere, the WebSphere Application V4 for z/os and OS/390 - DB2 V7.1 combination can still run on another system in the sysplex with the databases not being shared. This would allow new J2EE applications to be written for the WebSphere Application V4 for z/os and OS/390 server and if they need to get existing data, they would use a connector to obtain information from the existing applications that are running in CICS/IMS/DB2. The connectors we will provide in WebSphere Application V4 for z/os and OS/390 V4.0 release are optimized for zseries and S390 to take advantage of sysplexfacilities if WebSphere Application V4 for z/os and OS/390 and CICS/IMS/DB2 are in the same sysplex. OS/390 R8 OS/390 R8 OS/390 R8 CICS Customer App CICS Customer App WebSphere/390 DB2 V5.1 DB2 V5.1 DB2 V7.1 DB2 Data DB2 Data

15 Copyright IBM Corporation 2001 IBM Corporation Integrated Marketing Communications, Group Route 100 Somers, NY Produced in the United States of America All Rights Reserved References in this publication to IBM products or services do not imply that IBM intends to make them available in every country in which IBM operates. Consult your local IBM business contact for information on the products, features, and services available in your area. AIX, AS/400, CICS, DB2, DB2 Universal Database, e-business logo, IMS, IBM, IBM logo, OS/390, RACF, S/390, S/390 Parallel Enterprise, SecureWay, SmoothStart, Systempac, VisualAge, WebSphere, z/os and zseries are trademarks or registered trademarks of IBM Corporation in the United States, other countries or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademarks of Linus Torvalds. UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. Microsoft Windows NT is a registered trademark of Microsoft Corporation. Other trademarks and registered trademarks are the properties of their respective companies. IBM hardware products are manufactured from new parts, or new and used parts. Regardless, our warranty terms apply. Photographs shown are of engineering prototypes. Changes may be incorporated in production models. This equipment is subject to all applicable FCC rules and will comply with them upon delivery. Information concerning non-ibm products was obtained from the suppliers of those products. Questions concerning those products should be directed to those suppliers. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. All copyrighted and trademarked names and terms used in this document are the property of the respective owners and are used in this document under the doctrine of fair use for evaluative or comparative discussion. Sine Nomine Associates does not endorse or disclaim any claims made by the copyright or trademark owners as to usability or business value for any product or service referenced in this document. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.