iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

Transcription

1 IBM Front cover iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 Learn how to access iseries resources from the Web Convert 5250 to Web data sources with WebSphere Host Publisher Integrate iseries Access for Web and WebSphere Host Publisher Sungsim Park Andy Hagger Benjamin Jansky Paul Masschelein Kevin O Connor ibm.com/redbooks

2

3 International Technical Support Organization iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 September 2002 SG

4 Take Note! Before using this information and the product it supports, be sure to read the general information in Notices on page vii. First Edition (September 2002) This edition applies to V5R2 of iseries Access for Web, Program Number 5722-XH2, and V4R0 of WebSphere Host Publisher, Program Number 5724-B81, for use with OS/400 V5R1 or later. Copyright International Business Machines Corporation All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

5 Contents Notices vii Trademarks viii Preface ix The team that wrote this redbook ix Become a published author x Comments welcome xi Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V Today s environment Internet connectivity WebSphere software products iseries platform What is iseries Access for Web What is new in iseries Access for Web V5R What is WebSphere Host Publisher What is new in Host Publisher V Host Access products Host Access Client Package WebSphere Development Studio iseries Access Family WebSphere Host Integration Solution Summary Chapter 2. Setting up iseries Access for Web iseries server requirements iseries hardware requirements Software requirements Software considerations Web browser requirements Setup overview Migration Connecting to multiple iseries servers Setting up a secure iseries connection Chapter 3. Using iseries Access for Web The iseries Access for Web home page iseries Access for Web functions My Folder Mail Print Messages Jobs Database Files Command Customize Other Copyright IBM Corp All rights reserved. iii

6 General iseries Access for Web policies and preferences Restricting functions List customization Library filters Preferences Customizing users and groups Home page and template file customization Creating files Serving images Template example Home page example: Customer view Home page example: Administrator view Troubleshooting Chapter 4. The iseries Access for Web V5R interface Comparing the V5R2 interface and XML Gateway Starting a 5250 session Configuring sessions Configuration options Usage Synchronize My Macros My Keypads Cursor positioning Active sessions Limiting functionality shortcut Where to find more information Chapter 5. Installation and administration of WebSphere Host Publisher Server Hardware and software requirements Hardware requirements Software requirements Host Publisher Studio Installing and uninstalling Host Publisher Server Preliminary considerations Installing Host Publisher Server Installing Host Publisher Studio Saving and restoring Host Publisher Server Uninstalling Host Publisher Server Uninstalling Host Publisher Studio Using Host Publisher Server Administration Starting the Host Publisher Server Administration Using the functions in Host Publisher Server Administration Migrating applications and XML Gateway sessions Using the migration utility in Host Publisher Studio Migrating applications on the server Chapter 6. Using Host Publisher Studio to develop J2EE applications Overview of Host Publisher applications Integration Objects Interacting with a data source Defining connection pools iv iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

7 6.2.3 Information specified in a connection pool Enabling and disabling connection pooling User lists Creating a Host Access Integration Object Building an Integration Object using macros Sample scenario Creating a Database Access Integration Object Integration Objects overview Sample scenario Application Integrator Specifying Integration Objects to publish to the application server Using the Application Integrator wizards Transferring applications to a Host Publisher Server Deploying the application on WebSphere Application Server Creating composite applications Enterprise JavaBeans support Understanding EJB support in Host Publisher Creating EJB support files for Integration Objects Accessing Host Publisher EJB from local JSPs Creating a Host Publisher application using EJB access beans Web Services overview Host Publisher V4.0 Web Services support Creating and deploying a Web Service Accessing Host Publisher from a remote machine using Web Services Specifying properties for Web Services Integration Objects Creating Web Services support in Host Publisher Studio Creating Web Services in WebSphere Studio Application Developer with Host Publisher Web Services support Application Integrator Advanced Creating a new application for EJB or Web Services Deploying Enterprise JavaBeans Transferring applications to a Host Publisher Server Deploying the application on WebSphere Application Server Host Publisher Portlet WebSphere Studio Application Developer Web Services limitations References Host Publisher Studio and Server WebSphere Application Server for iseries EJB Web Services Portlet Summary Chapter 7. iseries Access for Web and Host Publisher integration Integration example Where to find more information Chapter 8. A comparison of Web-to-host integration tools Overview of the Web-to-host solutions Host Access Client Package for iseries Version IBM Personal Communications for Windows Version WebSphere Host On-Demand Version IBM Screen Customizer Version Contents v

8 8.3 WebSphere Development Studio Host components Workstation components WebSphere Studio Professional Edition WebFacing Tool iseries Access Family iseries Access for Windows iseries Access for Wireless iseries Access for Web WebSphere Host Publisher WebSphere Host Integration Solution Comparison WebSphere Host Publisher V WebFacing Host On-Demand Screen Customizer iseries Access for Web Putting it all together Appendix A. Configuring the Domino HTTP Server for iseries Access for Web Updating the Domino Server Document Updating the Domino server s notes.ini file Restarting the Domino server s HTTP task Appendix B. Additional information on Host Publisher Host Publisher installation log Host Publisher configuration information Host Publisher version information Host Publisher documentation Appendix C. Language support Related publications IBM Redbooks Other resources Referenced Web sites How to get IBM Redbooks IBM Redbooks collections Index vi iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

9 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Copyright IBM Corp All rights reserved. vii

10 Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks(logo) AFP AIX alphaworks AS/400 AS/400e DB2 DB2 Universal Database DRDA Everyplace Home Director IBM IBM eserver Infoprint iseries MORE OS/2 OS/400 Perform PowerPC Redbooks S/370 S/390 SP System/36 System/38 Tivoli VisualAge WebSphere xseries z/os The following terms are trademarks of International Business Machines Corporation and Lotus Development Corporation in the United States, other countries, or both: Lotus Word Pro Lotus Notes Notes Domino The following terms are trademarks of other companies: ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, and service names may be trademarks or service marks of others. viii iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

11 Preface iseries Access for Web (5722-XH2) the latest offering in the iseries Access Family (5722-XW1) product offers Web browser-based access to IBM ~ iseries servers. iseries Access for Web helps leverage business information, applications, and resources across an enterprise by extending the iseries resources to the client desktop through a Web browser. IBM WebSphere Host Publisher 4.0 (5724-B81) can modernize host applications or replace traditional character-based interfaces with a Web look and feel. These host applications can run directly from any standard Web browser. Host Publisher integrates multiple sources of data, including host and database applications, into a single Web page with no change to backend applications. Host Publisher and Host Publisher Studio have been bundled with the iseries Access for Web product to provide a complete Web-to-host integration solution. This IBM Redbook is designed for basic-level users who want to use iseries Access for Web V5R2 or WebSphere Host Publisher V4.0. It shows you how to install and use iseries Access for Web and WebSphere Host Publisher on the iseries server through several example applications. It summarizes the Web-to-host products. Then it presents various circumstances to help you decide which product to choose when you consider integrating enterprise data into the Web. The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Rochester Center. Sungsim Park is a Senior I/T Specialist in the IBM International Technical Support Organization, Rochester Center. She has over 16 years of experience in working with S/36, S/38, and iseries servers. Before joining the ITSO in 2000, she taught IBM classes on all areas of iseries as a senior education specialist in IBM Korea and provided technical marketing support to AS/400 sales representatives, IBM Business Partners, and Customers. Her areas of expertise include server consolidation and application development. You can contact her by sending to: [email protected] Andy Hagger is a Software Engineer and member of the IBM EMEA WebSphere Support Organization, based in Switzerland. He has over 15 years of experience in working with S/36 and iseries servers. His areas of expertise include Java, WebSphere, and database. You can contact him by sending to: [email protected] Benjamin Jansky is a Staff Software Engineer in Rochester, Minnesota. He has five years of experience in working with iseries servers. His areas of expertise include Client Access installation and communications, iseries Access for Web, and OS/400 TELNET. Current certifications include Cisco Certified Network Associate. You can contact him by sending to: [email protected] Copyright IBM Corp All rights reserved. ix

12 Paul Masschelein is an iseries IT Specialist in Belgium. He has 20 years of experience in System/36, System/38, AS/400, and iseries as an instructor and System Engineer. He holds a degree in Economics from Catholic University of Leuven (Belgium). His areas of expertise include e-business and application development on iseries. You can contact him by sending to: [email protected] Kevin O Connor is a Technical Consultant with KAZ Computer Services in Sydney Australia. He specializes in iseries support for a wide range of Australian customers and is a regular presenter at Interaction Australasia. Prior to joining KAZ Computer Services in 2000, he had 21 years of experience in IBM as a field engineer and in the AS/400 Support Center in Sydney. He worked as a member of the Rochester Programmer Support Team (PST) in 1991 and has taught AS/400 Service Education and Architecture classes in Australia and New Zealand. You can contact him by sending to: [email protected] Thanks to the following people for their contributions to this project: Warren Acker Doug Beauchene Linda Hirsch Carole Miner Schuman Shao Mike Sullivan Chang Wang Janet Weber IBM Rochester Russ Blocher Jonathan Brandt James Carmichael Sherri Midyette Alisa Morse Ann Syare IBM Raleigh Become a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html x iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

13 Comments welcome Your comments are important to us! We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: Mail your comments to: IBM Corporation, International Technical Support Organization Dept. JLU Building Highway 52N Rochester, Minnesota Preface xi

14 xii iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

15 1 Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 This chapter introduces iseries Access for Web V5R2 and IBM WebSphere Host Publisher V4.0. You can use both products to Web-enable your legacy applications on iseries servers. However, they are not the only products that may be used to access the iseries via a Web browser. This chapter explores the range software products that can be used to access the iseries (including those that are not Web-enabled). Once you understand the scope of each product, you can determine which product best suits your situation. The following sections introduce the concepts and products that are developed in later chapters: Section 1.3, WebSphere software products on page 2 Section 1.5, What is iseries Access for Web on page 3 Section 1.6, What is WebSphere Host Publisher on page 4 Section 1.7, Host Access products on page 6 Copyright IBM Corp All rights reserved. 1

16 1.1 Today s environment The manner in which many companies conduct their business has changed significantly over recent years. The Internet provides a prime market for many companies, and has created a huge paradigm shift in the way that the market is viewed. There are increasing business pressures to ensure continuous system availability and to use information technology personnel in the most efficient manner. These pressures have contributed to the drive to simplify the desktop environment and move to more open standards of access to business systems. 1.2 Internet connectivity The Internet has come to dictate changes in the way business is conducted. In fact, many companies have developed dependence on Internet connectivity for information and . Internet connectivity is viewed as inexpensive and an essential addendum to mainstream business. The benefits of Internet connectivity to the business community reach beyond sales and corporate image. The Internet is a prime factor in social and technological evolution, accelerating technological change at an unprecedented rate. 1.3 WebSphere software products The WebSphere software suite is the IBM range of program products aimed at providing a complete cross platform infrastructure to build, deploy, and customize e-business Web sites using open standards. The WebSphere products include: Application servers HTTP servers Design tools Integration tools Host access Intersystem communication You can find information about specific WebSphere software products at: IBM WebSphere Host Publisher V4.0, which we explore in-depth in this redbook, is one of the WebSphere suite of products. 1.4 iseries platform The IBM iseries server hardware platform has a distinguished heritage. IBM is justifiably proud of the record it has established with this product in the midrange system marketplace. The move toward open Internet protocols led to the introduction of new software products that facilitate the migration of traditional 5250 environments to a Web-based application environment on the iseries. 2 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

17 iseries connectivity can be characterized in three environments, each of which is explained in the following sections: Traditional Client/server Thin client Traditional 5250 environment iseries servers traditionally maintained an environment reliant on non-programmable terminals. This became known as a green-screen environment and involved a proprietary 5250 protocol. Client/server environment With the proliferation of personal computers, PC Support and subsequently Client Access developed the 5250 green screen into a client/server environment. With the growth of the Internet, the Internet Protocol (IP) has been widely accepted, replacing older synchronous communications standards. Recent releases of iseries Access Family have been streamlined to operate with the TCP/IP protocol as the only means of PC-to-iSeries connectivity. The limitation of a client/server environment is that each client requires dedicated software to be loaded and maintained on each workstation. In a network involving large numbers of PCs, client maintenance is a significant expenditure in the annual IT budget. Thin client environment The term thin client was introduced to differentiate a workstation that operates in a client server environment, yet does not require specific client software. The thin client, therefore, does not require maintenance in the same manner as a full function client personal computer. A thin client can access a server either via an intranet or an extranet. The advantage of providing access to a central server via a standard Internet browser is a reduction in the amount of effort expended on maintaining client software on a large number of networked clients. In addition, access is made available to a wider variety of clients, which may have been precluded from accessing the central server due to lack of specific client software (such as Linux). 1.5 What is iseries Access for Web iseries Access for Web is the most recent addition to the iseries Access Family (5722-XW1). iseries Access for Web enables users to access the iseries server from a Web browser, using standard Internet browser protocols. iseries Access for Web is a set of servlets that run on OS/400 Java Virtual Machine (JVM) and generate HTML output to a browser (such as Netscape or Internet Explorer). iseries Access for Web provides a subset of the capabilities provided with iseries Access for Windows. The advantage in using iseries Access for Web is ease of deployment. With no client software to be loaded on the workstation, the maintenance of the code is simplified and centralized to the iseries server. iseries Access for Web is designed for application users that: Need browser access to iseries servers Need to access DB2 UDB data Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 3

18 Work with OS/400 printers and printer output Send/receive messages iseries Access for Web features include: Print Messages Jobs 5250 Database Files Command Customize Other This redbook discusses the features of iseries Access for Web in detail What is new in iseries Access for Web V5R2 iseries Access for Web V5R2 has a number of new features introduced with V5R2. Some of these features include: Support for WebSphere Application Server 4.0 Support for Apache Software Foundation (ASF) Tomcat application server A 5250 interface, removing the need to configure the XML gateway with Host Publisher (Refer to Chapter 4, The iseries Access for Web V5R interface on page 79, for details on the new 5250 interface features.) A personal folder to store and manage SQL results, printer output, and command completion notifications Plus, iseries Access for Web V5R2 allows you to: Convert spooled files to PDF format Return SQL output in PDF or XML format Search for commands by name or description text Save and retrieve commands for repeated use Configure for more than one application server instance View the user and server jobs Copy, rename, and delete files in the integrated file system (IFS) Mail SQL results, command completion notifications, files and printer output Run commands and SQL requests asynchronously, using the mail and personal folder destinations 1.6 What is WebSphere Host Publisher IBM WebSphere Host Publisher is a set of tools that provide access to data on a legacy data source (a terminal-oriented host application or database application) on the World Wide Web or a private intranet. Host Publisher enables presentation of data to the end user without exposing the data source. Host Publisher uses IBM WebSphere Application Server to provide a consistent, reliable execution environment for Host Publisher applications. Host Publisher is divided into two major components: 4 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

19 Host Publisher Studio provides a development environment for creating Web-based applications on a Windows-based workstation. Host Publisher Server provides a runtime environment for J2EE applications created with Host Publisher Studio on an application server. Web-to-host applications are created using Host Publisher Studio and then transferred to the production server, where access is provided to the end user. Host Publisher Studio is a collection of task-oriented, easy-to-use graphical user interfaces (wizards) that assist the application developer in managing and creating the applications. Host Publisher Studio relies on three components to build J2EE applications that make specific data from the host or the database available to end users: Host Access: Creates Integration Objects (IO) that collect data from applications on the terminal-oriented host. By navigating the required information using a 5250 connection, Host Publisher records the keystrokes used and allows definition of the host application screens within the Integration Object. Database Access: Creates Integration Objects that encapsulate a database statement. To create the Integration Objects, specify the data you want to retrieve from the database table using Structured Query Language (SQL) statement. Application Integrator: Creates Web pages that use the Integration Objects created using Host Access or Database Access. Application Integrator enables importing the Integration Objects, EJB access beans, and other JavaBeans or objects. When used with Host Publisher Server, Integration Objects perform the following functions: Automatically establish a connection with the host Navigate to and extract data from an application Disconnect from the host and end the connection Host Publisher also provides Integration Object chaining. Integration Object chaining involves constructing a set on Integration Objects that depend on each other to drive a connection through several states. Integration Object chaining helps the developer build applications as collections of smaller elements that can be connected together to create a complete application or that can be reused in other applications. Connection pools are defined in the Host Publisher Studio and published to the server to enhance performance. Connection pools are used during runtime to cache connections to improve response time to Web page requests. A user-defined number of connections remains active in the pool, supporting requests from any user. This eliminates the overhead of establishing a connection, logging on, and disconnecting for each host request. The user can define the minimum and maximum number of connections in the pool. They can also specify whether WebSphere Host Publisher should wait for an available connection or create a new, non-pooled connection if all are in use. Host Publisher provides support for executing Integration Objects in EJB containers to take advantage of the server-side characteristics provided by the EJB architecture. The Host Publisher Studio provides an option to create Host Publisher EJB and its support files when you create an Integration Object. The Host Publisher EJB is a stateful-session EJB capable of running Integration Objects in an EJB environment. You can use Host Publisher Studio to build EJB-based applications. Host Publisher Server provides the runtime environment for supporting J2EE applications created with Host Publisher Studio. Host Publisher Server on iseries requires WebSphere Application Server Advanced Edition or Advanced Single Server Edition. Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 5

20 Host Publisher server also includes components such as connection management, license monitoring, runtime administration, XML Gateway, SSL support, and log and trace management. IBM WebSphere Host Publisher and IBM WebSphere Host Publisher Studio have been bundled with iseries Access for Web What is new in Host Publisher V4.0 Host Publisher Server on iseries requires you to install WebSphere Application Server Advanced Edition or Advanced Single Server Edition. As part of the WebSphere V4.0 environment, the following main enhancements are made in Host Publisher: J2EE application support: Applications produced by Host Publisher Studio comply with J2EE, an industry-standard architecture that is intended to reduce the cost and complexity of developing enterprise applications. A J2EE application takes the form of an Enterprise Archive (.ear) file into which all the application's pages, Java objects, and resources are assembled. Host Publisher applications on the server developed with an earlier version of the product must be migrated to Version 4.0. A migration tool is provided. JavaServer Pages (JSP) 1.1 support: Host Publisher Studio now produces JSP pages at the JSP 1.1 level. Applications with JSP 1.0 tags still run, but applications with JSP 0.91 tags (created prior to Host Publisher Version 3.5) need to be migrated. Two migration tools are provided. One PC-based tool is supplied with Host Publisher Studio and another tool is supplied on the server side. Enterprise JavaBeans (EJB) 1.1 support: Host Publisher now builds EJB-based applications supporting the EJB 1.1 specification level. EJB access beans developed with an earlier version of the product must be migrated to the 1.1 level; a migration tool is provided as part of Host Publisher Studio. Web Services: An application integration technology, based on open standards and implemented in middleware, provides a way for applications to connect and interact on the Web more easily and efficiently. Host Publisher Integration Objects and EJB access beans are enabled to become Web Services. Multi-language support: Host Publisher multi-language support allows the Host Publisher server to be administered in languages other than the server's default language. Host Publisher documentation can also be viewed in multiple languages. Serviceability: The Software Maintenance Utility is a new command-line tool that assists in the application of software fixes. WebSphere Portal Server 2.1 support: The Host Publisher portlet provides access to Host Publisher applications. Legacy content can be included within the personalized single point of access view delivered by enterprise portals. Tooling: Host Publisher applications are imported into WebSphere Studio tooling (for example, Application Developer 4.0.2/4.2.3). 1.7 Host Access products There are a number of software products that enable access to an iseries server. The following overview gives a brief summary of the packaging and features of the various options. 6 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

21 The software is available in four packages: Host Access Client Package Personal Communications Host On-Demand Screen Customizer WebSphere Development Studio WebFacing Tool iseries Access Family iseries Access for Windows iseries Access for Web WebSphere Host Publisher WebSphere Host Integration Solution WebSphere Host On-Demand Screen Customizer WebSphere Host Publisher Host Access Client Package Host on-demand, Screen Customizer, and IBM Personal Communications are packaged together as the Host Access Client Package (5648-E09). IBM Personal Communications IBM Personal Communications enables access to applications and data residing on mid-range and host systems. This emulator contains comprehensive tools that simplify connectivity and access to host data over the majority of connection protocols. It is designed as a full function emulator and does not have Web browser capability. IBM Personal Communications may be purchased as a component of IBM Host Access Client Package for Multiplatforms, which provides access to multiple backend host systems. For customers accessing iseries servers only, the IBM Host Access Client Package for iseries is a more appropriate solution. Personal Communications features include: Handles nearly any protocol, such as ISDN, HPR, SNA and IP Looks the same, whether it's for Windows 2000, Windows 95, Windows 98, Windows NT, or OS/2 Supports Microsoft Windows NT 4.0 Enterprise Server - Terminal Server Edition platform and Windows Terminal Services for Windows 2000; Metaframe by Citrix is also supported Has national language support, available in 21 languages, including double-byte character set (DBCS) languages Combines with other products including Host On-Demand and Screen Customizer WebSphere Host On-Demand IBM WebSphere Host On-Demand gives you secure access to your host applications and data, using a simple, Java-enabled Web browser. Centralized deployment means that software maintenance costs are minimized, with only the Web server needing code installation. Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 7

22 Host On-Demand features include: Secure access to host applications and data from a Java-enabled Web browser Access to iseries emulation in a single package Centralized deployment and administration Access to multiple hosts concurrently and still use your browser to surf the Internet Secure access across the Internet with SSL-based technology Installation on a server, simplifying maintenance, distribution, and upgrades Requires no middle-tier server, simplifying deployment and improving scalability Screen Customizer Screen Customizer has two components: Development tool Runtime environment The application development tool enables capturing host screens and customizing the graphical look and feel. The runtime applet allows graphical rendering in conjunction with Personal Communications (including the Client Access version) and Host On-Demand emulation sessions. Optionally, the server version (product 5648-D76) may be installed and have the graphical conversion take place on the iseries server rather than the workstation. Screen Customizer can be used to redesign the look and feel of the application by combining several screens into one, or by simplifying complex screens into parts. Screen Customizer does not have a batch mode-oriented means of converting large amounts of host screens that other tools have WebSphere Development Studio WebSphere Development Studio is an application development package that includes the WebFacing Tool and other components. WebFacing Tool The WebFacing Tool is a component of IBM WebSphere Development Tools for iseries. It can help convert 5250-based applications into a Web browser and HTTP-based applications. The WebFacing Tool requires the display file source to be imported into the toolkit and the creation of the required runtime components. You can select the look and feel from prebuilt templates or build your own. The WebFacing environment has been optimized to support existing 5250 applications in a display terminal or Web browser interface. For Web users, there is no overhead of generating a 5250 data stream, intercepting it, and then determining how it should be rendered. This conversion is done during the development phase. Source applications do not need to be modified. However, not all display file key words are supported iseries Access Family The iseries Access Family is a product designed for customers accessing iseries servers. The focus of iseries Access Family is to bring all the power of the iseries server to the end-user desktop and to tightly integrate its software into the desktop environment it is running on. 8 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

23 The iseries Access Family includes the following connectivity products: iseries Access for Windows iseries Access for Web IBM WebSphere Host Publisher iseries Access for Wireless iseries ODBC driver for Linux iseries Access for Windows delivers TCP/IP connectivity to users running all versions of Windows including Windows 95 and Windows 98. iseries Access for Windows includes: 5250 emulation Access to DB2 Universal Database (UDB) for iseries through its Data Transfer AS/400 NetServer for working with the OS/400 integrated file system and printers iseries Navigator is the OS/400 GUI for administering iseries servers Operations Console EZ-Setup Toolbox for Java iseries Access Family products (V5R2) With the release of iseries Access Family V5R2, a new naming structure is introduced that more accurately describes the changing focus of the product. Table 1-1 shows the V5R1 and V5R2 product names. Table 1-1 iseries Access Family component names V5R1 product names V5R2 product names Product number iseries Client Access Family iseries Access Family 5722-XW1 iseries Client Access Express for Windows iseries Access for Windows 5722-XE1 Operations Navigator iseries Navigator Packaged in 5722-XE1 iseries Access for Web 5722-XH1 iseries Access for Web 5722-XH2 WebSphere Host Publisher V E25 WebSphere Host Publisher V B81 Management Central Pervasive iseries Access for Wireless 5722-XP1 iseries ODBC driver for Linux 5722-LO1 Web download WebSphere Host Integration Solution The WebSphere Host Integration Solution software package includes three Web-enablement software products: WebSphere Host On-Demand Screen Customizer WebSphere Host Publisher IBM Personal Communications is also available with the WebSphere Host Integration Solution to provide comprehensive host access and emulation. Chapter 1. iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 9

24 WebSphere Host Publisher and Screen Customizer are summarized in previous sections in this chapter. WebSphere Host On-Demand provides cross-platform access to host systems through the use of Java applets, downloaded into the client Web browser. Host On-Demand applets can be installed on a client. They provide the most comprehensive Web enablement of traditional functions. 1.8 Summary This chapter gave a brief overview of the scope and function of the software products that are currently available to access the iseries server. Some of these products allow access to iseries resources from a Web browser, while others require a more traditional mode of connection. Such products as IBM Personal Communications have the ability to access various hardware platforms, while others such as iseries Access Family are iseries specific. You must understand the capabilities of the available products before you select the most appropriate solution to enable access to your iseries server. As Web access to business systems becomes more prevalent, the need to migrate business function to a Web-enabled format becomes increasingly important. iseries Access for Web and IBM WebSphere Host Publisher are two products that make a significant contribution in this environment. 10 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

25 2 Chapter 2. Setting up iseries Access for Web This chapter discusses the requirements for installing iseries Access for Web. It also examines the considerations relating to the installation and setup of the product. You can find detailed instructions to install and set up iseries Access for Web in iseries Access for Web, SC Throughout this chapter, we make frequent references to the relevant sections in that book. Therefore, prior to setting up iseries Access for Web, you must have this publication available. Copyright IBM Corp All rights reserved. 11

26 2.1 iseries server requirements The installation of iseries Access for Web V5R2 requires minimum levels of hardware and software. Prior to installing the iseries Access for Web software, you must verify that your system meets all hardware requirements and the required levels of software iseries hardware requirements Table 2-1 shows the minimum recommended server models required to run iseries Access for Web. The Commercial Processing Workload (CPW) column shows the processor capacity for the specified model. Table 2-1 Minimum server models Server type Processor feature CPW AS/400e Server AS/400e Server iseries Model iseries Model Table 2-2 contains the minimum recommended amount of main storage for an iseries server on which iseries Access for Web is installed. Table 2-2 Minimum main storage Main storage Minimum Recommended 512 MB 1 GB Table 2-3 shows the amount of disk space that is required to install the iseries Access for Web software. This is in addition to the disk requirements for the other required software products that are listed in Table 2-4. Table 2-3 Minimum disk space Software product iseries Access for Web (5722-XH2) Required disk space 170 MB Software requirements iseries Access for Web V5R2 may be installed on iseries servers running OS/400 V5R1 and later releases. iseries Access for Web requires a iseries Access Family license to connect to the iseries server. The license is obtained from the iseries Access Family licensing component (5722-XW1, option 1) and expires after five minutes of inactivity. Any session remaining idle for more than five minutes releases its license. Subsequent requests from the browser associated with the session initiates another license request. Each browser window that is opened by a user acquires another iseries Access license. This is indicated to the user by displaying a logon dialog box for each license that is acquired. 12 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

27 You must ensure that you have sufficient iseries Access Family licenses to add iseries Access for Web to an existing server. Use the Work with License Information (WRKLICINF) command to determine if you have enough licenses. Refer to iseries Access for Web, SC , for further information. iseries Access for Web may be configured for three Web application server environments. iseries customers have a choice of Web application servers: WebSphere Application Server Version 4.0 environment WebSphere Application Server 4.0 Advanced Edition WebSphere Application Server 4.0 Advanced Single Server Edition Apache Software Foundation Jakarta (ASF) Tomcat environment ASF Tomcat is provided as part of IBM HTTP Server for iseries (5722-DG1) iseries Access for Web may be configured with any of the Web application servers listed above. It may also be configured to run with multiple Web application servers concurrently on the iseries server. Table 2-4 lists the required software products to install iseries Access for Web on an iseries server when WebSphere 4.0 Application Server provides the application server function. Table 2-4 Required software products for the WebSphere 4.0 Application Server environment Product Option Description 5722-SS1 OS/400 Version 5 Release 1 or later 5722-SS1 3 OS/400 Extended Base Support 5722-SS1 8 OS/400 AFP Compatibility Fonts 5722-SS1 12 OS/400 Host Servers 5722-SS1 30 OS/400 Qshell Interpreter 5722-SS1 34 OS/400 Digital Certificate Manager (only required for Secure Sockets Layer (SSL) protocol) 5722-IP1 Base IBM Infoprint Server (only required for full function PDF spooled file transform) 5722-JV1 Base Java Developer Kit 5722-JV1 3 Java Developer Kit Version JV1 5 Java Developer Kit Version JC1 Base Toolbox for Java 5722-TC1 Base TCP/IP Connectivity Utilities 5722-DG1 Base IBM HTTP Server for iseries 5722-AC2 or 5722-AC XW1 Base Base Base Option 1 Crypto Access Provider 56 Bit for iseries Crypto Access Provider 128 Bit for iseries (only required for SSL protocol) iseries Access Family iseries Access Enablement Support 5722-XH2 Base iseries Access for Web Chapter 2. Setting up iseries Access for Web 13

28 Product Option Description 5733-WS4 or 5733-WA4 Base 1 IBM WebSphere Application Server Advanced Single Server Edition or IBM WebSphere Application Server Advanced Edition (WebSphere fix level is required) Note: In Table 2-4, only one Web application server software product (5733-WS4 or 5733-WA4) is required. If the SSL protocol is required, only one cryptographic feature (5722-AC2 or 5722-AC3) is required. When using the WebSphere Application Server 4.0, there are three choices for the software that provides the HTTP serving function. The licensed program product IBM HTTP Server for iseries (5722-DG1) provides two HTTP servers: The HTTP Server (original) The HTTP Server (powered by Apache) In addition, Lotus Domino can be configured to provide the HTTP serving function when setting up the WebSphere Application Server instance. This is supported with Lotus Domino for iseries Version or later. The Domino HTTP Server cannot be configured with the ASF Tomcat application server. Refer to Appendix A, Configuring the Domino HTTP Server for iseries Access for Web on page 265, for further information on setting up the Domino HTTP server. Table 2-5 lists the software requirements to run iseries Access for Web in an environment where ASF Tomcat provides the application server function. Table 2-5 Required software products for ASF Tomcat environment Product Option Description 5722-SS1 OS/400 Version 5 Release 1 or later 5722-SS1 3 OS/400 Extended Base Support 5722-SS1 8 OS/400 AFP Compatibility Fonts 5722-SS1 12 OS/400 Host Servers 5722-SS1 30 OS/400 Qshell Interpreter 5722-SS1 34 OS/400 Digital Certificate Manager (only required for SSL protocol) 5722-IP1 Base IBM Infoprint Server (only required for full function PDF spooled file transform) 5722-JV1 Base Java Developer Kit 5722-JV1 3 Java Developer Kit Version JV1 5 Java Developer Kit Version JC1 Base Toolbox for Java 5722-TC1 Base TCP/IP Connectivity Utilities 5722-DG1 Base IBM HTTP Server for iseries (includes ASF Tomcat application server) 14 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

29 Product Option Description 5722-AC2 or 5722-AC XW1 Base Base Base Option 1 Crypto Access Provider 56 Bit for iseries Crypto Access Provider 128 Bit for iseries (only required for SSL protocol) iseries Client Access Family iseries Access Enablement Support 5722-XH2 Base iseries Access for Web Note: In Table 2-5, if the SSL protocol is required only one Cryptographic feature (5722-AC2 or 5722-AC3) is required. Beta release The iseries Access for Web software product was available as a beta release prior to the release of the V5R2 product. The beta release must be deleted from the iseries server prior to the installation of the official release. Refer to iseries Access for Web, SC , for detailed instructions on deleting the beta version of the software. Installing the licensed program Use the Restore Licensed Program (RSTLICPGM) command to install iseries Access for Web (5722-XH2) as a licensed program: RSTLICPGM LICPGM(5722XH2) DEV(OPT01) OPTION(*BASE) Verify that the installation of the licensed program was successful by using the GO LICPGM command and selecting option 10, as shown in Figure 2-1. Check that the iseries Access for Web licensed program is displayed as Installed. Display Installed Licensed Programs System: Licensed Installed Program Status Description 5722WDS *COMPATIBLE Workstation Tools - Base 5722XE1 *COMPATIBLE Client Access/400 Express for Windows 5722XH2 *INSTALLED iseries Access for Web 5722XW1 *COMPATIBLE Client Access Family for Windows 5722XW1 *COMPATIBLE Client Access Enablement Support ITSO Press Enter to continue. Bottom F3=Exit F11=Display release F12=Cancel F19=Display trademarks Figure 2-1 iseries Access for Web licensed program Use the following command to produce this information in a spooled file: DSPSFWRSC *PRINT Chapter 2. Setting up iseries Access for Web 15

30 2.1.3 Software considerations With the introduction of iseries Access for Web V5R2, there are a number of considerations in relation to the levels of software on the iseries. iseries Access for Web V5R1 and iseries Access for Web V5R2 may be installed concurrently on an iseries server. Installing iseries Access for Web (5722-XH2) does not impact an existing installation of iseries Access for Web (5722-XH1). The licensed programs are installed in separate libraries and integrated file system (IFS) directories. Both licensed programs require an iseries Access Family license. iseries Access for Web V5R1 is only supported with IBM WebSphere Application Server V3.5. iseries Access for Web V5R2 may only be used with IBM WebSphere Application Server V4.0. iseries Access for Web V5R2 is supported with the ASF Tomcat Web application server. iseries Access for Web V5R1 does not support ASF Tomcat. Installing iseries Access for Web (5722-XH2) does not perform any setup of the product. Configuration of the product is completed using the CFGACCWEB2 command. Refer to iseries Access for Web, SC , for further information on using the configuration command. PTFs After you install the required software on the iseries server, you must apply the latest PTFs to each of the related software products. Cumulative PTF package Be sure to install the current cumulative PTF package for the installed version of OS/400 before you install any other fixes. You must install the latest cumulative PTF package prior to loading fixes for the IBM WebSphere Application Server or the ASF Tomcat Application Server. You can find more information on the latest iseries cumulative PTF package on the Web at: Additional PTFs At the time this redbook was written, the individual PTFs listed in Table 2-6 were required for V5R1 of OS/400 and the HTTP Server. Table 2-6 Additional individual PTFs at V5R1 Product 5722-SS SS SS DG1 PTF number SI02028 SI01946 SI02756 SI02940 Refer to the following Web site for information relating to the latest iseries Access for Web PTF requirements: 16 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

31 For information on the most recent levels of fixes available for any related products, refer to the following Web sites: Note: You must check all the listed Web sites for additional PTFs. Some required PTFs may not be included in a cumulative package or Group PTF. Information on PTFs for IBM WebSphere Application Server: Information on PTFs for iseries Access for Web: Information on PTFs for ASF Tomcat HTTP Server: Information on PTFs for IBM WebSphere Host Publisher: Information on iseries PTFs for Lotus Domino: Follow these links from the main support page to locate additional PTFs: Fixes-> Select a Topic-> Domino. Information on Lotus Domino maintenance releases and updates: Web browser requirements At the time this redbook was written, three Web browsers had been tested with iseries Access for Web: Netscape 4.7 (AIX and Linux) and 6.2 (Windows) Internet Explorer 6.0 (Windows) Opera 5.0 (Linux) and 6.0 (Windows) Other browsers may work successfully with iseries Access for Web. However, they have not been tested at this point. iseries Access for Web requires that the Web browser allows cookies. Refer to iseries Access for Web, SC , for details on enabling cookies in the listed browsers. 2.3 Setup overview There are several combinations of the available software that may be used to enable iseries Access for Web V5R2. Table 2-7 shows the possible combinations of application server and HTTP server. Chapter 2. Setting up iseries Access for Web 17

32 Table 2-7 Software combinations WebSphere Application Server 4.0 Advanced Edition WebSphere Application Server 4.0 Advanced Single Server Edition ASF Tomcat IBM HTTP Server (powered by Apache) IBM HTTP Server (original) Yes Yes Yes Yes Yes No Domino HTTP Server Yes Yes No For information about configuring the Web application server, refer to the WebSphere documentation center at: iseries customers who have Lotus Domino R5.0.5 or later installed may use the Domino HTTP server in conjunction with WebSphere Application Server 4.0 (Advanced Single Server Edition or Advanced Edition) to enable iseries Access for Web. Refer to iseries Access for Web, SC , for step-by-step instructions on setting up WebSphere Application Server V4.0 and the IBM HTTP servers. For information on configuring the Domino HTTP server, see Appendix A, Configuring the Domino HTTP Server for iseries Access for Web on page 265. Note: iseries Access for Web with WebSphere Application Server 4.0 Advanced Edition and Domino R6 supplying the HTTP server was the only combination tested during the writing of this redbook. The iseries Access for Web, SC , publication provides the following checklist as a means of verifying that all the installation steps have been completed. The checklist is reproduced here to help you understand the overall setup process. The individual steps are detailed in iseries Access for Web, SC Setup checklist Use this checklist to guide you through the steps necessary to install, verify, and configure a simple iseries Access for Web environment. These steps do not take into account other Web applications or more complex Web environments. 1. Verify your iseries server has the necessary hardware listed in 2.1.1, iseries hardware requirements on page Verify your iseries server has the prerequisite software listed in 2.1.2, Software requirements on page Verify your Web browser meets the requirements listed in 2.2, Web browser requirements on page If the beta release of iseries Access for Web was installed on your server, it must be deleted before you install V5R2 iseries Access for Web. For details, see Beta release on page Install iseries Access for Web on the iseries server using the instructions in Installing the licensed program on page 15, and in iseries Access for Web, SC Now that the iseries server software is installed, install the latest program temporary fixes (PTFs) for: 18 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

33 Cumulative PTF package Additional PTFs WebSphere Application Server ASF Tomcat/HTTP Server for iseries iseries Access for Web IBM WebSphere Host Publisher 7. Prepare for creating the HTTP Server using the information in iseries Access for Web, SC If you plan to use WebSphere 4.0, see iseries Access for Web, SC , which explains details for: Creating WebSphere administrative instances Creating an HTTP Server 9. Verify the Web application server is setup and ready to be configured to run iseries Access for Web for one of the following environments: WebSphere 4.0 Advanced Edition WebSphere 4.0 Advanced Single Server Edition ASF Tomcat Server 10.If iseries Access for Web V5R1 is installed, installing iseries Access for Web V5R2 has no impact on the V5R1 installation. 11.Configure iseries Access for Web to run the Web application server in one of the following environments: WebSphere 4.0 Advanced Edition WebSphere 4.0 Advanced Single Server Edition ASF Tomcat 12.If you plan to modernize existing server applications using Host Publisher, see Install IBM Host Publisher 4.0 in iseries Access for Web, SC , for details. Note: This checklist does not include any references about creating a WebSphere 4.0 instance with a Domino HTTP server configured. For more information, see Appendix A, Configuring the Domino HTTP Server for iseries Access for Web on page Migration When installing iseries Access for Web V5R2 on an iseries server that already has iseries Access for Web V5R1 installed, a default process migrates the existing user data to the new V5R2 environment for iseries Access for Web. Both versions of iseries Access for Web can coexist on the same iseries server by duplicating the data files. User data created while using iseries Access for Web V5R1 is migrated to iseries Access for Web V5R2 the first time iseries Access for Web is configured for WebSphere 4.0 or ASF Tomcat application server. The user data is copied to the IFS directory structure created for the V5R2 version of the product when the Configure iseries Access for Web (CFGACCWEB2) command is run. If an installation is required that omits copying user data from the iseries Access for Web V5R1 to the new directory structure for iseries Access for Web V5R2, refer to iseries Access for Web, SC This publication explains a method for editing the migration.properties file in the IFS, prior to running the CFGACCWEB2 command, to omit the default process. Chapter 2. Setting up iseries Access for Web 19

34 2.5 Connecting to multiple iseries servers In an environment where access to multiple iseries servers is required, from a performance perspective, installing the full suite of software to enable iseries Access for Web on each machine may not be desirable. Due to financial constraints, it may not be appropriate to install WebSphere Application Server on all iseries servers. This section explores the possibility of using a central iseries server to provide a gateway-like function to allow access to multiple iseries servers. Figure 2-2 shows a topology that allows the use of iseries Access for Web to connect to more than one iseries server. There are several considerations when planning iseries Access for Web connections to multiple systems: Network topology Network security Required licensed program products Multiple application server instances For the purposes of this example, it is understood that adequate network security is implemented to secure the iseries from unauthorized access. We recommend that you use cryptographic encryption with any iseries server accessed from the Web. When this is implemented, the Web browser uses the SSL protocol to access the iseries labelled as System A. The iseries Access for Web connections to the subsequent systems are facilitated by Java classes shipped with iseries Access for Web V5R2. The toolbox connections on the central system (System A) communicate with iseries Access servers on the remote systems (System B, System C, System D, etc.). Figure 2-2 shows the software products that must be installed on systems B, C, and D to access these systems via a Web browser with iseries Access for Web. Web browser HTTP or HTTPS Internet/intranet HTTP or Secure HTTP connection Refer to Tables 2-4 and 2-5 for the required software products for iseries Access for Web System A Toolbox Connections System D iseries Access Family iseries Access for Web System B System C Figure 2-2 Connecting to multiple systems with iseries Access for Web 20 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

35 Refer to Table 2-4 on page 13 or Table 2-5 on page 14 for a list of the required software products for iseries Access for Web for System A. You must have installed all required software licensed program products on this system. In addition, System A requires you to configure an additional Web application server instance for each additional iseries server to be accessed using iseries Access for Web. The additional systems represented as System B, System C, and System D do not require a Web application server instance to be installed. However, these systems do require you to install the following licensed programs: iseries Access Family (5722-XW1) iseries Access for Web V5R2 (5722-XH2) Each additional system requires iseries Access Family to provide the licensing component to allow iseries Access for Web connections and iseries Access for Web V5R2 to control the individual session functions. Each instance of the Web application server is required to be configured for one target system. The configuration setting that controls the target system for the instance is the realm definition in the webaccess.properties file. You can find the webaccess.properties file in the IFS directory /QIBM/UserData/Access/Web2/appserver/instancename/config/webaccess.properties. The path depends on the unique values configured on an individual server: appserver: The name of the application server (for example, was40adv) instancename: The unique name for the instance of the application server (for example, default) You can edit the content of the webaccess.properties file to configure the application server instance to connect to the target system. Figure 2-3 shows an example of the content of the webaccess.properties file with the parameter that needs to be included. #Wed Apr 24 15:29:56 GMT+00: port=5252 nodename=<systemname> serviceport=900 servicehost=<systemname> realm=systemc.ibm.com Figure 2-3 Example webaccess.properties file The webaccess.properties file is edited by adding a realm statement to the file. Without this statement, the iseries Access for Web session is directed to the local system. The format of the realm statement is shown here: realm=targethost.domain.com targethost.domain.com is the fully qualified domain name configured in the TCP/IP setup for the desired target system. For example, it may be systemc.ibm.com. Chapter 2. Setting up iseries Access for Web 21

36 2.6 Setting up a secure iseries connection Allowing access to the iseries from a Web browser over the Internet opens the iseries server to security risks. You should always assume that any data that is accessed from a Web browser is subject to scrutiny and possible interference form outside sources. To secure the flow of data to an Internet connected browser session, we recommend that you configure the SSL protocol to the iseries server. Required software The following software is required on the iseries server to enable the SSL protocol: IBM Digital Certificate Manager TCP/IP Connectivity Tools One of the Cryptographic Access Provider products Refer to Table 2-4 on page 13 for the product identifiers of the required products. Refer to iseries Access for Web, SC , for details on SSL. The iseries Information Center also provides detailed references for setting up SSL on an iseries server. You can find the iseries Information Center on the Web at: The Information Center contains information on the following topics: Setting up the iseries server to use SSL Using digital certificates for SSL Securing applications with SSL Planning Internet security 22 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

37 3 Chapter 3. Using iseries Access for Web This chapter discusses how to use iseries Access for Web. iseries Access for Web enables you to access your iseries server information and resources through a Web browser. By default, most of the functions of the product are available for all users. To restrict access to the set of functions, iseries Access for Web provides administrators the ability to quickly access and customize the product. Default settings have been configured for users to provide a general look and feel for the product. The default settings may be customized to provide a truly unique Web environment. Copyright IBM Corp All rights reserved. 23

38 3.1 The iseries Access for Web home page You can locate the iseries Access for Web home page by following these steps: 1. Enter the following URL: Note: Replace systemname with the name of your iseries. If HTTP is configured for a non-standard port, you must specify systemname:port. Figure 3-1 shows the case sensitive URL for iseries Access for Web. Press Enter. Figure 3-1 URL for iseries Access for Web home page 2. Figure 3-2 shows the dialog box the first time iseries Access for Web is started from a new browser session. Displayed in the dialog box is the Site and Realm. iseries Access for Web considers the system name as the Realm. Enter a valid iseries user ID and password. This user ID and password are sent to the server using encoded text. Encoded text is not secure. HTTPS provides a secure transfer of text by encrypting the data. We recommend you use HTTPS if you are using iseries Access for Web over the Internet. System values QMAXSIGN and QMAXSGNACN are enforced. Figure 3-2 Browser dialog box The iseries Access for Web sign on is active until the browser is closed. If a user ID prompt is displayed, a new session has started. Multiple sessions may be started and different profiles may be used for the connection attempt. Each additional session requires an additional license. For example, two Internet Explorer connections result in using two licenses. 24 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

39 Logging off requires you to shut down the browser. iseries Access for Web does not provide log off or disconnect functionality. Netscape users must close all browser windows. This is caused by Netscape s ability to share sign-on information across all Netscape browser windows. The iseries Access for Web home page is displayed once the user are and password are validated. iseries Access for Web provides a default home page for all users. This page presents the functions iseries Access for Web provides and demonstrates the ability to integrate with your applications. The default home page is located in the directory QIBM/ProdData/Access/Web2/html/homepage.html. Figure 3-3 shows the default iseries Access for Web home page. Figure 3-3 iseries Access for Web home page For more information on home page customization, see 3.5, Home page and template file customization on page iseries Access for Web functions iseries Access for Web provides access to your iseries server information and resources through a Web browser. To access the iseries Access for Web functions, from the default home page, select the iseries Access for Web Main Page link. You may also enter the following URL: Chapter 3. Using iseries Access for Web 25

40 The iseries Access for Web Main Page link provides additional product information. The navigation bar is also displayed on the side. The navigation bar allows you to quickly access various functions. It contains the functions shown in Figure 3-4, starting with My Folder. Each individual function contains a link in the navigation bar. Figure 3-4 Navigation bar We explain each of these functions in the following sections My Folder My Folder contains items that have been placed in the current user s personal folder. The current user or another user may have placed the items. You may access My Folder by typing the following URL: Tip: You can place output from Print, Command, and Database in the folder. My Folder may contain items with the following information: Item description Status From Date/Time Size A column labeled Actions lists the available actions for the items in the folder, which may include: Open Delete Rename Mail Mark Opened In Figure 3-5, the My Folder icon on the left contains unopened items as indicated by the * character in the top right-hand corner of the folder. The My folder icon on the right contains all opened items. 26 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

41 Figure 3-5 My Folder with unopened items Users may also be notified via when new folder items are placed in their personal folder. You configure this function by customizing My Folder. Figure 3-6 shows an example of configuring notification. You must also perform general Mail customization for this support to work. Refer to Setting up Mail on page 29. Figure 3-6 My Folder notification You can restrict My Folder by setting the My Folder policy to Deny for a user or group profile. Placing output in multiple personal folders iseries Access for Web has the ability to specify the destination of output. You can specify to place this output in multiple personal folders. The following steps explain how to send a PDF file to multiple personal folders: 1. From the navigation bar, click Print-> Printer Output (see Figure 3-13 on page 31). 2. On the Printer Output page, select a spooled file and click PDF in the Action column. 3. On the PDF Output Settings page, locate the Destination field, click the drop-down list, and select Personal folder. 4. Click Settings. Then you see the Personal Folder Settings page as shown in Figure 3-7. Figure 3-7 Personal Folder Settings Chapter 3. Using iseries Access for Web 27

42 5. Enter an item description. 6. Click Browse... You may select individual users or groups. Press the Ctrl key to select multiple individual users or groups. 7. Click OK. The folder owner is updated with the selected folder owners. 8. On the Personal Folder Settings page, click OK. 9. On the PDF Output Settings page, click Run. A message, similar to the example in Figure 3-8, appears indicating the output was converted and copied to the specified folders. Figure 3-8 Convert Printer Output to PDF Mail Data and files can be sent to any address using iseries Access for Web. can also be used to notify you when a command completes or an item is placed in your personal folder. The mail function is available from: Print: Mail as attachment is the destination choice for the PDF action on a Printer Output item. Use this option to mail a PDF representation of a spooled file to one or more addresses. When you run the PDF action, the browser window is not updated until the operation completes and the item is mailed. Database: The Mail as attachment destination choice in Run SQL is used to send SQL results to one or more addresses. Mail as attachment and Personal folder are good destination choices for long running SQL requests, since the request runs in the background and browser timeout errors are avoided. You can also configure saved SQL requests to prompt you for the addresses and message text every time the request is run. Command: The My address output option is used to send the command completion message to your configured address. My address and My folder are good output choices for long running commands, since the command runs in the background browser timeout errors are avoided. You can use Submit Batch Job with the Browser output option for long running requests. However, the completion message only contains information about submitting the job. It does not give any information about how the command completes. You should only use Submit Batch Job if you don't need the completion status or if you can verify the status some other way. Note: There is no advantage to using My address or My folder with Submit Batch Job. These options already run the command in the background and the completion message from Submit Batch Job does not contain information about the completion status of the command. File: Browse Files and File Shares provide a Mail action for mailing files in the integrated file system to one or more addresses. When you mail a file, the browser window is not updated until the file is sent. My Folder: My Folder provides a Mail action for mailing a folder item to one or more addresses. When you mail an item, the browser window is not updated until the item is 28 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

43 sent. My folder also supports sending a notification message to an address whenever an item is placed your personal folder. You can configure this notification option using the Customization function. You can submit a batch command and receive notification when it completes. You can access the via a PC, cell phone, or PDA. Administrators or users may also set the destination of a database request to Mail as Attachment. A report runs in the background, and when it completes, the with the report as an attachment is sent to the specified user. Setting up Mail The following steps explains how to configure mail: 1. From the navigation bar, select Customize-> User Profiles or Group Profiles (see Figure 3-33 on page 45). This depends on what you want to configure for mail. 2. Select Mail from the Category. The Customize - Mail page is displayed as shown in Figure 3-9. Figure 3-9 Customize: Mail 3. Enter your SMTP mail server and address under the Setting heading. For both the SMTP mail server and address, select Apply setting to profile under Action. See Figure Then click OK. Figure 3-10 Customize: Mail sample entries Chapter 3. Using iseries Access for Web 29

44 Sending output using iseries Access for Web can send output to multiple destination types. The destinations include Browser, Personal Folder, and Mail as Attachment. Mail as Attachment is only available when the Mail Policy is configured. The following steps explain how to use personal folders and using SQL output: 1. Click Database-> Run SQL (see Figure 3-20 on page 36). 2. On the Run SQL page, create an SQL statement in the box (see Figure 3-26 on page 41). 3. Go to the SQL Output section. 4. Select a type of output. You can t preview with Personal Folder and Mail as Attachment. You can see additional types by clicking the drop-down list. 5. For the Destination, select Mail as Attachment by clicking the drop-down list: a. Click Settings. Figure 3-11 shows the Mail as Attachment Settings. b. Enter the information requested. You can specify multiple addresses by separating each address with a comma. Figure 3-11 Mail as Attachment Settings c. Click OK. 6. The Run SQL Request page (Figure 3-12) opens. A notification message is sent to your inbox along with your SQL output. 30 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

45 Figure 3-12 Run SQL Request Print iseries Access for Web provides access to your printers and printer output. You can access the print functions via the Print tab as shown in Figure Figure 3-13 Print tab Each Print function is explained as follows: Printer output: List, preview, and manage printer output on your iseries server. Hold, release, or cause a spooled file to be printed next. View, mail, or send printer output in PDF format. Preview SCS and AFP printer output in GIF, TIFF, PCL, and AFP formats. View AFP output with the AFP viewer plug-in. Printers List and manage printers on your iseries server. View printer and status information. Vary on and vary off the printer device. View and answer messages waiting on the writer job. List, preview, and manage printer output for a printer from the printer list. Manage the writer job associated with the printer using hold, release, start, and stop functions. Internet printers List Internet printers on your iseries server. View configuration information and status from internet printer list. Access and manage printer output from the internet printer list and the iseries printer defined by the Internet printer. Printer shares List printer shares, with printer share information and status, on your iseries server. Access and manage printer output from the printer share list. Chapter 3. Using iseries Access for Web 31

46 Output queues List, manage, and view the status of output queues on your iseries server. Hold and release an output queue from the output queue list. List, preview, and manage printer output in an output queue from the output queue list. You can customize Print functions or restrict them by using the Customize tab. For additional information on Print, see iseries Access for Web, SC Printer output in PDF format iseries Access for Web supports two different ways to transform a spooled file to the PDF format: IBM Infoprint Server (5722-IP1) TIFF transform IBM Infoprint Server is a separately purchased product that gives iseries Access for Web users the ability to create full text PDF files that deliver document fidelity, while preserving the ability to navigate through the text of the document. If you have IBM Infoprint Server installed, iseries Access for Web automatically detects and uses it. If you do not have IBM Infoprint Server installed, the individual pages of the spooled file are converted into images. These images become the pages of the output PDF document. You cannot edit or search for content in any of these pages. Printer shares iseries Access for Web has the ability to view printer shares. For additional assistance on configuration and setup, refer to the iseries Information Center at: Internet printers iseries Access for Web has the ability to view Internet printers. To learn more about configuring and setting up these printers, see Printer Device Programing, SC Mailing PDF files iseries Access for Web provides the ability to mail print output in PDF format. You must first configure the mail function for the iseries Access for Web user or group profile as outlined here: 1. Follow the steps in Setting up Mail on page Select the Print-> Printer output link from the navigation bar. 3. Select PDF from the Action Column in the Printer Output page, and change Destination to Mail as Attachment. Figure 3-14 shows the PDF Output Settings that are available if IBM Infoprint Server is installed. 32 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

47 Figure 3-14 PDF Output Settings Figure 3-14 also shows the Restore original printer output check box. The option is only available if IBM Infoprint Server is installed. This option controls if the spooled file stays on the system after the spooled file is transformed to PDF. When the transformation is performed by Infoprint Server, the spooled file is actually sent to a writer job. If this option is not enabled, the spooled file is treated like it was sent to a physical printer device. If IBM Infoprint Server is not installed, the Host Print Transform converts the spooled file pages. The spooled file will still be located in the output queue. Click Settings. 4. Figure 3-15 shows the Mail as Attachment Settings. Enter the required information and click OK. Figure 3-15 Mail as Attachment Settings 5. Back on the PDF Output Settings page, click Run. Figure 3-16 shows a message that indicates the mail was sent successfully. Chapter 3. Using iseries Access for Web 33

48 Figure 3-16 Mail sent successfully Messages iseries Access for Web give you access to your messages via the Messages tab. The navigation bar in Figure 3-17 shows the Messages tab and related functions. Figure 3-17 Message tab Each of the Message functions is explained here: Display messages Display, answer, and manage messages in the message queue for the logged on user. Send messages Send a message to users and message queues. Operator messages Display, answer, and manage messages in the system operator message queue. Message queues List message queues on the iseries server. Select, display, and manage messages in message queues. You can customize or restrict Message functions by using the Customize tab. For additional information on Messages, see iseries Access for Web, SC Jobs iseries Access for Web allows you to access the iseries jobs you submitted. You may also access jobs working on your behalf. Figure 3-18 shows Jobs tab from the navigation bar. Figure 3-18 Jobs tab 34 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

49 The Jobs functions include: Jobs List and manage user jobs on your iseries server. View job logs for active jobs. View printer output for completed jobs. Server jobs List and manage server jobs on your iseries server. View job logs for server jobs. You can customize or restrict Job functions by using the Customize tab. For additional information on Jobs, see iseries Access for Web, SC iseries Access for Web provides the ability to start an interactive session on the iseries server. This function can be accessed via the 5250 tab. Figure 3-19 shows 5250 tab from the navigation bar. Figure tab For more information, see Chapter 4, The iseries Access for Web V5R interface on page 79. The 5250 tab includes the following functions: Active sessions Database List active 5250 user interface sessions. Configured sessions List configured 5250 user interface sessions. Start session Start a 5250 user interface session. iseries Access for Web provides access to database tables on the iseries server. you can access this function via the Database tab. Figure 3-20 shows the Database tab and its related functions. Chapter 3. Using iseries Access for Web 35

50 Figure 3-20 Database tab The Database functions include: Tables View a list of database tables on your iseries server. Perform actions on these tables without knowledge of SQL and its syntax. View the contents of a table in a paged list using the Quick view action. Add and update records in a table using the Insert and Update actions. Create your own customized SQL request for a table using the Run SQL action. Create your own customized copy data request for a table using the Copy data to table action. My requests View a list of previously saved requests. Run or edit requests from this list. Manage lists using the Copy, Delete, and Rename actions Create and manage shortcuts to requests. Run SQL and personal folder options are available as output destinations. Run SQL statements dynamically. View output as a paged list or in a popular file format, like Microsoft Excel or Lotus (The output format depends on how you have your browser configured and whether the browser can locate a plug-in for the output type you choose.) Customize how data is returned by setting options specific to the output type. Build SELECT statements using an SQL wizard. Save requests for repeated use. Copy data to table Copy existing data files from your PC to a database table on your iseries server. These data files can be in many popular file formats, including Microsoft Excel and Lotus Replace the contents of a table or add data to an existing table. Create a new database table based on the contents of a workstation file. Save requests for repeated use. Import request Import Client Access Data Transfer upload and download requests into iseries Access for Web copy data and SQL requests. 36 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

51 Imported requests are automatically converted to iseries Access for Web format. Run and edit converted requests on your iseries server just like other copy data and SQL requests. You can customize or restrict Database functions by using the Customize tab. For additional information on the Database functions, see iseries Access for Web, SC Database management iseries Access for Web has the ability to manage database requests. Administrators may manage requests for a group of users, share requests, and restrict access. Figure 3-21 shows an example of My Requests. You can perform several actions on a request, including: Run Copy Delete Rename Create shortcut Edit Administrators can restrict access to request actions using customized policies. The Access column lists who has access to the request or shortcut. For requests, this value is always the user profile used to create the request. For shortcuts, the user creating the shortcut chooses who has access to the shortcut. One or more user profiles or group profiles can be chosen. A special value of *PUBLIC indicates all users have access to the shortcut. The following scenario shows how an administrator can use a combination of customization and shortcuts to manage database request access: 1. Use policies to allow the database administrator access to all database request actions. 2. Use policies to deny users, in the *PUBLIC group, access to all database request actions other than Run. 3. Create the following three database requests: Past due accounts Low inventory New orders 4. Create the following three shortcuts: To Past due accounts and give access to the ACCOUNTING group. To Low inventory and give access to the PURCHASING group. To New orders and give access to the SHIPPING group. In this example, only the database administrator is allowed to create and modify requests. Other users are only allowed to run requests. The requests a user is allowed to run are limited to the requests the administrator decides the user should be able to access. Figure 3-21 My Requests Chapter 3. Using iseries Access for Web 37

52 Database connections The following sections show you how to define the database connection using the Native JDBC Driver and the Toolbox JDBC Driver. Using the Native JDBC Driver iseries Access for Web contains the ability to use the Native JDBC Driver in place of the predefined Toolbox Driver. The following steps describe this process: 1. From the iseries Access for Web Main page, click Customize-> User profiles or Group profiles (see Figure 3-33 on page 45). 2. Click Edit from the Action column for the user profile or group profile you want to edit. 3. Click Database Connections on the Customize User Profile page or Customize Group Profile page. The pre-configured database connection is displayed. You must configure a new connection to take advantage of the Native JDBC driver. 4. Click Add Database Connection on the Customize page. Then the Add Database Connection page opens. 5. Enter the following information: Connection: A text description of the database connection Driver class: com.ibm.db2.jdbc.app.db2driver JDBC URL: jdbc:db2:*local Figure 3-22 shows the required entry fields. Figure 3-22 Adding a Native JDBC database connection 6. Click Add Connection. The Native JDBC database connection is added to the list of database connections. Restriction: Only the Toolbox Driver is officially supported. Defining a database connection to a remote system: Native JDBC Driver iseries Access for Web has the ability to access remote databases with the use of Distributed Relational Database Architecture (DRDA). You need to complete the following steps to access the remote system: 1. Define a remote connection using the Remote Database Directory. Enter the following command on an OS/400 command line: addrdbdire Enter the following information: Relational database: Name of entry Remote location: Name or IP address of remote system Type: Specify type (*IP for TCP/IP networks) Figure 3-23 shows an example of the Add RDB Directory Entry window. 38 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

53 Type choices, press Enter. Add RDB Directory Entry (ADDRDBDIRE) Relational database Remote location: Name or address DBSYSTEMNAME SYSTEMNAME Type *IP *SNA, *IP Text Remote Database on SYSTEMNAME Figure 3-23 Add RDB Directory Entry Important: The relational database name is used in future steps. 2. Ensure you can connect to the remote database. Using an SQL interface, issue the SQL statement CONNECT TO as shown here: a. From an OS/400 command line, enter: strsql b. Enter: CONNECT TO relational database name 3. From the iseries Access for Web Main page, click Customize-> User profiles or Group profiles (see Figure 3-33 on page 45). 4. Click Edit from the Action column for the user or group profile you want to edit. 5. Click Database Connections on the Customize User Profile page or Customize Group Profile page. The preconfigured database connection is displayed. You must configure a new connection to use the Native JDBC driver to access a remote database. 6. Click Add Database Connection on the Customize page. Then the Add Database Connection page opens. 7. A new database connection must be defined using Native JDBC driver: Connection: A text description of the database connection Driver class: com.ibm.db2.jdbc.app.db2driver JDBC URL: jdbc:db2://dbsystemname;user=uid;password=pwd DBSYSTEMNAME is the relational database entry defined in step one. Use the additional parameters user=uid;password=pwd only if the user ID and password for the remote system are different that the iseries Access for Web authenticated user ID and password. Figure 3-24 shows the required entry fields. Chapter 3. Using iseries Access for Web 39

54 Figure 3-24 Adding a remote database connection: Native JDBC Driver 8. Click Add Connection. The Native JDBC database connection is added to the list of database connections. Defining a database connection to a remote system: Toolbox JDBC Driver iseries Access for Web has the ability to access remote databases with the use of the Toolbox JDBC Driver. You need to complete the following steps to access the remote system: 1. Starting from the iseries Access for Web Main page, click Customize-> User profiles or Group profiles. 2. Click Edit from the Action column for the user or group profile you want to edit. 3. Click Database Connections on the Customize User Profile page or Customize Group Profile page. The preconfigured database connection is displayed. You must configure a new connection to use the Toolbox JDBC driver to access a remote database. 4. Click Add Database Connection on the Customize page, and the Add Database Connection page opens. 5. A new database connection must be defined using Toolbox JDBC Driver: Connection: A text description of the database connection Driver Class: com.ibm.as400.access.as400jdbcdriver JDBC URL: jdbc:as400://remotesystemname;prompt=false;user=uid;password=pwd The remote system name must be resolved: Host table, DNS, ETC. Use the additional parameters user=uid;password=pwd only if the user ID and password for the remote system are different that the iseries Access for Web authenticated user ID and password. Figure 3-25 shows the required entry fields. Figure 3-25 Adding a remote database connection: Toolbox JDBC Driver 6. Click Add Connection. The connection is added to the list of database connections. After the Remote Database connection is created, users may specify the connection by clicking Preference-> Database and changing the Default Connection setting. 40 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

55 SQL Wizard: Building a select statement with a condition iseries Access for Web provides the ability to create SQL statements from an SQL Wizard. The following steps explain how to create an SQL statement with a condition using the SQL Wizard: 1. Starting from the navigation bar, click Database-> Run SQL (see Figure 3-20 on page 36). 2. The Run SQL page opens as shown in Figure Click the SQL Wizard button. ASM03.ORLAND.IBM.COM Figure 3-26 Run SQL 3. The SQL Wizard Welcome page is displayed. Click Next. 4. The SQL Wizard Table page is displayed. Click Find. 5. Specify a table filter. You can also preconfigure one by clicking Preferences-> Database. 6. Click Find Now. 7. Locate your table in the Tables list. Select the table and click OK. 8. The table that you selected is displayed in the SQL Table page. Click Next. 9. Figure 3-27 shows the SQL Wizard Columns page. Select which columns you want to include. To change the order in which the columns are included, click Column Order. Chapter 3. Using iseries Access for Web 41

56 Figure 3-27 SQL Wizard: Columns 10.Click Next. 11.The SQL Wizard Condition page is displayed. To add a condition, click Add Condition. 12.Select a column and click OK. 13.The Condition Operator page shown in Figure 3-28 is displayed for you to select a numeric column (numeric Condition Operator). The Condition Operator varies depending on the column type. 42 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

57 Figure 3-28 Condition Operator: Numeric 14.Select an operator and click OK. 15.The Specify condition value is displayed. Click Find Value. 16.The Find Value is displayed. Specify a search criteria and click Find Now. 17.Select the available values and click OK. 18.The Condition Value is displayed. Click OK. 19.The SQL Wizard Condition page is displayed. Click Next. 20.The SQL Wizard Sort page is displayed. Select which columns to use when sorting the data. Click Finish. 21.After the wizard is finished, Run SQL is displayed with the resulting SQL statement filled in. You can save this statement by clicking Save Request Files iseries Access for Web provides access to the file system on the iseries server. This function is available via the Files page. When viewing files, depending on the file extension, third-party plug-ins may be needed for proper viewing of a file type. The ability to view file shares is also available, but the shares must be configured using iseries Navigator. Figure 3-29 shows the Files tab from the navigation bar. Figure 3-29 Files tab The Files tab consists of the following functions: Browse files Chapter 3. Using iseries Access for Web 43

58 Navigate and browse the directories located on your iseries server integrated file system. View and download files in a file manager-like interface. File shares View a list of the iseries NetServer file shares. Browse the NetServer file shares and navigate the directories from the file share list. View and download files in a file-manager-like interface. You can customize or restrict File functions by using the Customize tab. You can find additional information on Files in iseries Access for Web, SC Command iseries Access for Web provides access to batch-level iseries commands. You access this function via the Command tab. You may also run interactive commands, but the result of the command does not appear in the browser window. The result goes a printer output file (spooled file) that you can view by using the Printer output link found on the iseries Access for Web Print page. This is the same behavior as specifying *PRINT for the OUTPUT parameter for this type of command. If the command is of a type that is not supported in the batch environment, an error message is displayed when the user tries to run the command. You can configure long running commands to use My Folder or My address as output. This runs the command asynchronously, and a notification is displayed in the browser window that the command has started to run. When the command completes, the user is be notified via or by a folder item appearing in the My Folder list. Figure 3-30 shows the Command tab from the navigation bar. Figure 3-30 Command tab The Command tab consists of the following functions: My commands List and use previously saved commands. Run command Run a CL command on your iseries server. Search Search for CL commands on your iseries server. You can customize or restrict Command functions by utilizing the Customize tab. For additional information on Commands, see iseries Access for Web, SC iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

59 Command search iseries Access for Web can search for iseries commands using one of two methods: Command name Text description Figure 3-31 demonstrates searching for a command using a wildcard asterisk (*). Figure 3-31 Search for Commands: Command name Figure 3-32 demonstrates searching for a command using a text description. Figure 3-32 Search for Commands: Text description Customize iseries Access for Web allows you to set preferences to control how information is presented. Administrators can customize settings for users and groups to control which functions are available. Figure 3-33 shows the Customize tab from the navigation bar. Figure 3-33 Customize tab Chapter 3. Using iseries Access for Web 45

60 The Customize tab includes the following functions: Preferences Update your preference settings. Select columns to display when viewing list output. Show or hide the navigation bars. Adjust the number of items to display per page. User profiles Work with user profiles on your iseries server. Edit policy settings for user profiles. Copy or reset policy settings for user profiles. Group profiles Work with group profiles on your iseries server. Edit policy settings for group profiles. Copy or reset policy settings for group profiles. Administer default policy settings for all users. Selected profile Work with a specific user or group profile on your iseries server. Edit policy settings for the specified profile. You can customize or restrict Customize functions by using the Customize tab Other iseries Access for Web can perform Other tasks on your iseries server as shown by the Other tab in Figure Figure 3-34 Other tab The functions under the Other tab include: Change password Change your password on your iseries server. Connection pool Change the connection pool settings for iseries Access for Web. Trace Change the trace settings for iseries Access for Web. 46 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

61 About Display information about iseries Access for Web. You can customize or restrict Other functions by using the Customize tab. For additional information about Other functions, see iseries Access for Web, SC General iseries Access Web contains several features found in all functions. This includes adding the functions to favorites and using a second user ID prompt. Adding iseries Access for Web functions to favorites All iseries Access for Web functions can be configured as a browser favorite. These steps explain this process using Internet Explorer: 1. From the navigation bar, click Messages-> Operator Messages. 2. Within the browser, select Favorites-> Add to Favorites. 3. A browser box opens and displays the details of the link. Click OK. Second user ID prompt During iseries Access for Web usage, users may be presented with a second user ID prompt. Depending on the action requested, browsers may handle the function differently. Internet Explorer may need to open a second instance to complete a request. A second instance causes a user ID prompt. 3.3 iseries Access for Web policies and preferences iseries Access for Web provides administrators and users the ability to customize the product via user or group policies and preferences. Policies: Provides application level control of functions via policy settings. The policy settings can be administrated at the user and group profile level. For a complete list of policies, refer to iseries Access for Web, SC For example, the Printer output policy setting can be set to Deny for a particular user or group profile to restrict access to that function. Preferences: Provides users the ability to customize iseries Access for Web to meet their needs. User preferences are a subset of available policy settings. For example, the Printer output list columns preference can be modified by a user to set the columns they want to see when viewing their printer output list Restricting functions iseries Access for Web supports policies that control what functions a user can perform. An administrator can allow or deny a user or a group of users access to an entire function or to individual actions of a function. Chapter 3. Using iseries Access for Web 47

62 For example, an administrator could restrict all users from the Jobs function. They could allow users in the ACCOUNTING group to run database requests, but deny them access to other database actions. They could also restrict user JOE from running batch commands. When a user is denied access to a function or action, the function is not available from the navigation bar or as a page link. Preferences are also available to prevent function tabs from being displayed on the navigation bar. However, these preferences do not restrict users from accessing the function if, for example, they use a bookmark to the function List customization Users can customize how lists are navigated and displayed using list preferences. For example, Default rows per page controls the maximum number of rows displayed on an page. Default pages per set controls the number of pages defined in a set, when using the previous set and next set navigation links. These preferences affect all lists. For most lists, you can also customize which columns are displayed and the order these columns appear. See Figure 3-35 for an example of customizing printer output columns. Some lists support additional customization preferences unique to the supported function. See iseries Access for Web, SC , for details on these preferences. Figure 3-35 Columns Printer Output Figure 3-36 shows an example of changing the printer output lists columns. It also shows the columns that were selected. 48 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

63 Figure 3-36 Print output with column policy Library filters Some lists displayed by iseries Access for Web contain information about objects in libraries. By default, the content of these lists is built by searching libraries in the user portion of the library list. Sometimes these lists can be too large to manage. The library filter preferences allow you to customize which libraries are used to build the lists. The database table filter preference also supports wildcard characters and table names to allow additional filtering on the tables list. For more information, refer to iseries Access for Web, SC The following library filter preferences are available: Print, Output queue library filter Database, Table filter Command, Default search library Tip: The database library filter supports wildcard characters and filtering on table names Preferences Each individual user profile can change user preferences for iseries Access for Web. This function is allowed by default. If administrators want to restrict users, they must deny users or groups of users access to the function using policies. Preference modifications are saved and associated with their iseries user profile. Settings are stored in the following paths: Default settings: QIBM\ProdData\Access\Web2\config\webaccess.policies All preferences and customizations: QIBM\UserData\Access\Web2\<WebServer>\<Serverinstance>\config\webaccess.policies Users can set the following types of preferences: Column inclusion and ordering for functions that display output in columns Number of rows per page to display on output Show or hide navigation bar tabs Preferred language and character set Database table filters and default database connection Number of commands to save in the run command history Users can also change iseries Access for Web preferences by selecting Customize from the navigation bar. Figure 3-37 shows the Customize tab. Chapter 3. Using iseries Access for Web 49

64 Figure 3-37 Customize tab Select Preferences, and the Preferences page is displayed as shown in Figure Figure 3-38 Preferences Users can customize iseries Access for Web from this location. Select a category to see the preferences that are available to customize. Once a preference is changed, users can select one of three actions: Use current setting: Any setting modifications are added to the profile. If no settings are changed, no action is performed. Apply setting to profile: Ensures your profile is updated with the preference selected. All settings are written to the profile, regardless of whether the values changed. Selecting this action overrides any group profile preference of which the user may be a member. Reset to default: This action is only available if preferences have been modified. This action sets the preference to the public preference or a specified group preference. 50 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

65 Tip: To ensure preferences are applied to a user profile, select Apply setting to profile. Administrators may want to deny users or groups the ability to modify individual preferences. This is controlled by customizing the user ID or group profile. Figure 3-39 shows the customization option, which you can access by clicking Customization-> User profile or Group profile-> Administration. Figure 3-39 Edit preferences 3.4 Customizing users and groups iseries Access for Web gives administrators the ability to customize user and group profiles via the Customize function. This function allows users and groups the ability to control what functions users can perform and how certain information is presented. When a function is restricted, it is removed from the navigation bar. Restrictions also prevent access to the corresponding servlet. Changing a function tab setting to hide does not restrict access to the function. Attention: Policies for a user or group take effect immediately. Administrators with *SECADM special authority defined in their iseries user profile can change iseries Access for Web settings. Administrators need to understand how policy settings are determined for an individual. Figure 3-40 demonstrates policy enforcement for an individual user profile. User Profile Policy NO YES NO Group Profile Policy YES Policy Enforced Administer - supplied user defaults (*PUBLIC profile - UserData policy file) YES NO IBMsupplied defaults (*PUBLIC profile - ProdData policy file) Figure 3-40 Policy flow Chapter 3. Using iseries Access for Web 51

66 Customizing User profiles You can customize User profiles by selecting Customize-> User profile from the navigation bar. A list of iseries profiles is displayed. Administrators may customize each profile from this location. Figure 3-41 shows the Customize User profile tab. Figure 3-41 Customizing User profiles Administrators can perform three actions for each profile: Edit: Used to create or modify policy settings Copy: Used to copy all of the policy settings to one or multiple profiles Reset: Used to remove all policy settings specific to the profile Important: The copy and reset actions are only available when the user or group profile currently has policy settings. Within each user and group profile, a Derived from column is displayed. Table 3-1 shows the available descriptions for the user profile Derived from column. Table 3-1 Derived from column descriptions Derived from Profile setting Group - (groupname) *PUBLIC setting Shipped default Description Indicates the setting is currently specific to the profile being customized. The setting was previously applied to this profile. Indicates the setting is not specific to the profile being customized, but is derived from the specified iseries group profile and the user is a member of this group. Indicates the setting is not specific to the profile being customized. No setting was found in any iseries group profile memberships. The setting is derived from the *PUBLIC group settings. This is a special group profile available to iseries Access for Web administrators. All user profiles are automatically members of this special group profile. Administrators can modify this group profile to easily apply settings to all iseries Access for Web users. Indicates the setting is not specific to the profile being customize. No setting was found in any iseries group profile memberships or the special *PUBLIC group profile. The setting is derived from a shipped default value. Customizing Group profiles You can customize Group profiles by selecting Customize-> Group profile from the navigation bar. A list of iseries group profiles is displayed. Administrators can customize each group profile from this location. Figure 3-42 shows the Customize Group profile tab. Figure 3-42 Customizing Group profiles 52 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

67 iseries Access for Web includes a configured group called *PUBLIC. This group contains the default settings for all users. All users are a member of this group and cannot be removed. Changes to this group affect all iseries Access for Web profiles. Important: QSECOFR is a member of *PUBLIC. For a complete overview of customizing user and group profiles, refer to iseries Access for Web, SC Disabling all functions with a group profile By default, iseries Access for Web has policy settings enabled for all users. It is the administrator s responsibility to restrict functions. Customizing the *PUBLIC profile is an easy way to restrict functions to all users. The Group profile *PUBLIC also includes QSECOFR and profiles with *SECADM authority. Users may want to customize a new group profile to ensure QSECOFR and administrators continue to have access to all functions. The following steps explain this process: 1. Create a new group profile with Operations Navigator. Figure 3-43 shows Groups in Operations Navigator. Figure 3-43 Operations Navigator Groups 2. Right-click Groups and select New Group. Figure 3-44 shows the required new group information. Figure 3-44 New Group Chapter 3. Using iseries Access for Web 53

68 3. Enter a group name and provide a description. Then, from the All users box, select a user or users and click Add-> to add the users to the group. 4. To see the new group, go to the iseries Access for Web Main page and select Customize-> Group Profile. Figure 3-45 shows a sample group. Figure 3-45 Sample group 5. Edit the newly created group. 6. Select a category and edit the policy. Policy settings are grouped by function, with subfunction policies. To restrict a function, you set the function setting to Deny. You do not have to explicitly deny all subfunctions. Figure 3-46 shows an example of customizing the Files function. Figure 3-46 Customize: Files 54 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

69 3.5 Home page and template file customization You can change which page to display when accessing the iseries Access for Web home page URL, which is You can also set your own template file. The template file contains the header and footer displayed on every page. The header is displayed before the iseries Access for Web content, and the footer is displayed after the content. For example, you can create a template to display your company's logo before the content on every page. The following sections describe how a company can use home page customization and template file customization to build a Web site for selling boats Creating files iseries Access for Web provides the following default home page and template files: /QIBM/ProdData/Access/Web2/html/homepage.htm /QIBM/ProdData/Access/Web2/html/webaccess.htm You can copy these files to another directory or create new files. The home page and template files can be stored anywhere in the iseries integrated file system. You should not modify the files in ProdData or create new files in this directory tree. The /QIBM/ProdData tree is intended for product files only. In our boat company example, the home page is /boats/homepage/home1.htm, and the template file is /boats/homepage/temp1.htm. To replace the default files with these files, click Customize-> Selected Profile-> your profile name-> General. The Customize - General page opens as shown in Figure Figure 3-47 Customize - General Chapter 3. Using iseries Access for Web 55

70 Avoiding application server restarts In this example, a version number is added at the end of each file name. Every time you modify your home page or template file, you need to restart the application server to pick up the latest versions of the files. To avoid restarting the application server, add a version number to the end of the file name. When you make a change to the file, rename the file with an updated version number (for example, home2.htm), update the home page or template file customization setting, and delete the old file. Tip: To avoid restarting the application server, use a version number at the end of your file names and update the customization settings every time you change the files. Ensuring proper file authorities The following profiles require *RX authority to the home page file, the template file, and the directories that contain these files: Serving images *PUBLIC QEJBSVR (for WebSphere Application Server) QTMHTTP (for Tomcat) To verify the authority, start a 5250 session, run the following command, and select option 9: WRKLNK OBJ('/boats/homepage') If your home page or template file contains images, you need to update your HTTP server configuration to locate the images. The following sections explain how to change the HTTP server configuration for both the IBM HTTP Server for iseries (original) and the IBM HTTP Server for iseries (powered by Apache) by each version. IBM HTTP Server for iseries (original) V5R2 1. Open your browser and go to: 2. Select IBM HTTP Server for iseries. 3. In the Server list, select your HTTP server. 4. Select Request Processing-> Request Routing. 5. You must insert your URL template path before the value /*, which is the default. This is the default pass. Any pass after this one is not processed. You can insert before other passes if you want your pass to be processed before them. 6. In the Action field, choose PASS. 7. For the URL template field, enter the path you use to access images from within your HTML file, for example: /boats/*. 8. For the Replacement file path field, enter the actual location of your image directory, for example: /boats/homepage/*. 9. Click the Apply button. 10.In the Server list, select All servers. 11.Select your HTTP server. 12.Click the Stop button. 13.Click the Refresh button until your server is listed as Stopped. 56 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

71 14.Enter -nolastmod in the Server startup parameters field. 15.Click the Start button. IBM HTTP Server for iseries V5R1 1. Open your browser and go to: 2. Select IBM HTTP Server for iseries-> Configuration and Administration-> Configuration. 3. In the Configuration for server list, select your HTTP server. 4. Select Request Processing-> Request Routing. 5. You must insert your URL template path before the value /*, which is the default. This is the default pass. Any pass after this one is not processed. You can insert before other passes if you want your pass to be processed before them. 6. In the Action field, choose PASS. 7. For the URL template field, enter the path you use to access images from within your HTML file, for example: /boats/*. 8. For the Replacement file path field, enter the actual location of your image directory, for example: /boats/homepage/*. 9. Click the Apply button. 10.Select Administration-> Manage HTTP Servers. 11.Select your HTTP server. 12.Click the Stop button. 13.Click the Refresh button until your server is listed as Stopped. 14.Enter -nolastmod in the Server startup parameters field. 15.Click the Start button. IBM HTTP Server for iseries (powered by Apache) V5R2 1. Open your browser and go to: 2. Select IBM HTTP Server for iseries 3. In the Server list, select your HTTP server. 4. For the Server area, choose Global configuration. 5. Click Tasks and Wizards-> Serve New Directory wizard. Click the Next button. 6. Choose Static web pages and files. Click the Next button. 7. In the Name field, enter the actual location of your image directory, for example: /boats/homepage/. Click the Next button. 8. In the Alias field, enter the path you use to access images from within your HTML file, for example: /boats/. Click the Next button. 9. Click the Finish button. 10.Click the OK button. 11.In the Server list, select All servers. 12.Select your HTTP server. Chapter 3. Using iseries Access for Web 57

72 13.Click the Stop button. 14.Click the Refresh button until your server is listed as Stopped. 15.Click the Start button. IBM HTTP Server for iseries (powered by Apache) V5R1 1. Open your browser and go to: 2. Select IBM HTTP Server for iseries-> Configuration and Administration-> Configuration. 3. In the Configuration for server list, select your HTTP server. 4. Under Configuration structure, choose global settings. 5. Under Web Site Definition, choose Serve New Directory wizard. Click the Next button. 6. Choose Static web pages and files. Click the Next button. 7. In the Name field, enter the actual location of your image directory, for example: /boats/homepage/. Click the Next button. 8. In the Alias field, enter the path you use to access images from within your HTML file, for example: /boats/. Click the Next button. 9. Click the Finish button. 10.Select Administration-> Manage HTTP Servers. 11.Select your HTTP server. 12.Click the Stop button. 13.Click the Refresh button until your server is listed as Stopped. 14.Click the Start button. Assuming images are stored in /boats/homepage/images/, the source to include the boat company logo as part of the home page or template is: <img SRC="/boats/images/boathead.gif" height=43 width=614> Template example Figure 3-48 shows the contents of a database table using the default iseries Access for Web template. Figure 3-49 shows the same table using a custom template and hiding the navigation bar. To hide the navigation bar, click Customize-> Selected Profile-> your profile name-> General-> navigation bar. 58 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

73 Figure 3-48 Database table with default template Figure 3-49 Database table with a custom template A custom template must include the %%CONTENT%% tag. When the page is displayed, this tag is replaced with the iseries Access for Web content. In our boat example, the header is replaced with a company logo and a link to the home page Since the navigation bar is hidden, the home page link is used to navigate between pages. Chapter 3. Using iseries Access for Web 59

74 The source for the template file is shown here: <HTML> <BODY> <table> <tr> <td> <img SRC="/boats/images/boathead.gif" height=43 width=614> </td> </tr> <tr> <td align="right"> <a href="/webaccess/iwahome">home</a> </td> </tr> </table> <br> %%CONTENT%% <br> <table width="100%" border="0" cellspacing="0" cellpadding="0" mm_noconvert="true"> <tr align="center" bgcolor=#000000> <td width="50" bgcolor="#1b89ad"> <a href=" color=#ffffff>ibm</font></a> </td> <td width="1" bgcolor=#ffffff> <img src="transparent.gif" width="1" height="1"> </td> <td width="70" bgcolor="#1b89ad"> <a href=" color=#ffffff>iseries</font></a> </td> <td width="1" bgcolor=#ffffff> <img src="transparent.gif" width="1" height="1"> </td> <td width="70" bgcolor="#1b89ad"> <a href=" color=#ffffff>service</font></a> </td> <td width="1" bgcolor=#ffffff> <img src="transparent.gif" width="1" height="1"> </td> <td width="750" bgcolor="#1b89ad"> </td> </tr> </table> <BODY> </HTML> 60 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

75 3.5.4 Home page example: Customer view Figure 3-50 shows a customer view of the home page for our boat company. It contains a number of links to iseries Access for Web functions. Each link is discussed in the following sections. This home page demonstrates one way to implement each service listed. There are often multiple different ways to accomplish a task using iseries Access for Web. Figure 3-50 Home page: Customer view Chapter 3. Using iseries Access for Web 61

76 View available boats This link shows the contents of a database table. A caption is specified to customize the table heading. See Figure The source for this link is: <a href="/webaccess/iwadbview?table=boats.boats&caption=available Boats">View available boats</a> Figure 3-51 Viewing a database table See boat details This link starts a 5250 session to run a traditional 5250 application. A better solution is to use Host Publisher to modernize this application. See Chapter 6, Using Host Publisher Studio to develop J2EE applications on page 141, for more information. You can use the Change User Profile (CHGUSRPRF) command to change the initial program to your company's application. You may also want to use the Change System Value (CHGSYSVAL) command to change the Display sign on information (QDSPSGNINF) system value to 0. This prevents the sign on information from being displayed before the initial program is started. Another startup option is to use the initmac parameter on the iwa5250 link. The initmac parameter identifies a macro to run after starting the session. If a session already exists when the link is chosen, the most recently accessed session is displayed and the macro is not run again. 62 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

77 The source for this link is: <a href="/webaccess/iwa5250">see boat details</a> Figure 3-52 Running a traditional 5250 application Chapter 3. Using iseries Access for Web 63

78 Order a boat This link uses a database table insert to enter order information. See Figure The source for this link is: <a href="/webaccess/iwadbinsert?table=boats.orders">order a boat</a> Figure 3-53 Inserting a record into the database table This Week s Special This link uses the file download support to display a video clip of the boat. Pictures of the boat s interior can also be stored in the integrated file system. The source for this link is: <a href="/webaccess/iwafiledownload?filepath=/boats/carver.mpg">here</a> 64 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

79 Great Deals This link uses a database query to return a subset of the contents of a database table. The SQL Wizard was used to build a query that retrieves all boats costing less than $75,000 and orders them by increasing price. The resulting statement is: SELECT "BNAME", "BFEET", "BYEAR", "BCOST", "BNT01" FROM BOATS.BOATS WHERE ( (BOATS.BOATS."BCOST" < 75000) ) ORDER BY "BCOST" The HTML SQL output type is used to display the results. The HTML output type supports a template file to display a custom header and footer around the results. In this example, the template created in 3.5.3, Template example on page 58, provides a consistent look. If you use the same template for database queries and general page content, you need to change the Template tag setting from <!-- TABLE1 --> to %%CONTENT%%. The template tag setting is an HTML output type setting in Run SQL. This example uses a public shortcut to run the database query. Any user with access to the server can run the query, but only the user who created the request can modify or delete it. See Figure The source for this link is: <a href="/webaccess/iwadbexec/sqloutput.html?access=*public&request=bargains">view our selection of modestly priced boats.</a> Figure 3-54 Displaying the database query results Chapter 3. Using iseries Access for Web 65

80 Site Support This link uses the iseries message support to provide customers a way to send their comments and questions to the boat company. This example has a user profile set up for receiving customer comments. The boat company can have someone monitor these messages or it may have an application process the messages. See Figure The source for this link is: <a href="/webaccess/iwasendmessage">send us a message</a> Figure 3-55 Sending a message Weather Conditions This link does not use any iseries Access for Web support. It is part of the example to demonstrate that home page content is not restricted to iseries Access for Web functions Home page example: Administrator view Figure 3-56 shows the administrator view of the home page for our boat company. It contains the same links available from the customer view plus additional links that are only accessible by the company administrator. 66 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

81 Figure 3-56 Home page: Administrator view Different content for different users In our boat company example, the only differences between the customer view and the administrator view are additional service links in the administrator view. The home pages for both user types can be implemented with a single file, using the iseries Access for Web include list support. Like the %%CONTENT%% replacement tag in the template file, your home page can contain an include list replacement tag. The format of the include list tag is: %%include list=file%% file identifies a file containing list items to include as links in a table. The list of items included can be tailored to an individual user, a group of users, or all users (*PUBLIC). When the home page is displayed, this tag is replaced with the appropriate set of links for the current user profile. You can find a sample include list in the directory /QIBM/ProdData/Access/Web2/config/info.policies. Our boat example adds links only if the current user is BOATADMIN. We add the following lines to the home page to do this: <tr> <td>%%include list=/boats/homepage/adminserv.policies%%</td> </tr> Chapter 3. Using iseries Access for Web 67

82 The contents of the adminserv.policies file are: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <QiwaPolicies> <profile name="boatadmin"> <homepage> <listitem name="work with invoices"> <href>/webaccess/iwaspool?queue=boats/invoices</href> </listitem> <listitem name="check messages"> <href>/webaccess/iwamessages?msgq=boats/comments</href> </listitem> <listitem name="check system messages"> <href>/webaccess/iwamessages?msgq=qsys/qsysopr</href> </listitem> <listitem name="administrator tasks"> <href>/webaccess/iwacommandlist</href> </listitem> <listitem name="manage incoming items"> <href>/webaccess/iwamyfolder</href> </listitem> <listitem name="monitor jobs"> <href>/webaccess/iwajoblist?jobtype=user</href> </listitem> </homepage> </profile> </QiwaPolicies> If you want links that only customers can access, add another profile section to the file. Tip: You need to use character references for characters that can be included in an XML document. For example, if you have a link with multiple parameters, you need to replace & with &. Supported replacement tags iseries Access for Web supports a number of additional replacement tags in home page files: %%TITLE%% is replaced with the page title. %%USER%% is replaced with the authenticated user name. %%SYSTEM%% is replaced with the name of the iseries server being accessed. %%VERSION%% is replaced with the version of iseries Access for Web installed. Update home page This link exists as a design convenience and should be removed when the home page is complete. When a new version of the home page is saved, this link provides a fast path to the general customize page for updating the home page setting. Clicking OK takes you back to the updated home page. This link uses the %%USER%% replacement tag to update the home page file for the current user. By using the replacement tag, this link can be used to test the customer view as well as the administrator view. This assumes the customer user profile is enabled to update the home page setting during the home page design phase. The source for the link is: <a href="/webaccess/iwacustomizegeneral?profile=%%user%%">update home page</a> 68 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

83 Administrator functions The following sections discuss the services available to the boat company administrator. The links for these services are not contained in the home page file directly. Instead, they are specified in the include list file. See Different content for different users on page 67 for the source of each of these links. Work with invoices This link displays the contents of a printer output queue for working with customer invoices. See Figure You can use the customize function to choose which columns and actions are shown in the list, as well as the order in which the columns are displayed. In this example, the invoice number is stored as user data and is displayed in the first column. Figure 3-57 Displaying contents of the printer output queue The TIFF preview option is used to view the invoice. See Figure Chapter 3. Using iseries Access for Web 69

84 Figure 3-58 Viewing the printer output The PDF option can be used to mail a PDF version of the invoice to the customer. See Figure Figure 3-59 Mail printer output as a PDF file 70 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

85 Check messages This link displays the contents of the message queue where customer comments are sent. See Figure Figure 3-60 Viewing messages on the message queue Chapter 3. Using iseries Access for Web 71

86 Check system messages This link displays the contents of the system operator queue. It provides a way to check system status messages. See Figure Figure 3-61 Viewing system operator messages 72 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

87 Administrator tasks This link displays the My Commands list for accessing commonly run tasks. You can use the customize function to choose which columns are shown in the list, as well as the order in which the columns are displayed. In this example, a command is used to back up the contents of the BOATS library. See Figure Figure 3-62 Displaying the command list Chapter 3. Using iseries Access for Web 73

88 The Prompt action can be used to view or change the command parameters. In our boat example, the command is submitted as a batch job since it could take a long time to complete. See Figure Figure 3-63 Prompt option 74 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

89 Manage incoming items This link uses the My Folder list as a way to manage items needing to be handled. See Figure Figure 3-64 Displaying items in a personal folder In this example, the list contains the results of a database query. These results identify inventory needing to be restocked. The results are stored in the Microsoft Excel format. The Open action is used to view the item. See Figure Figure 3-65 Viewing the contents of the folder item Chapter 3. Using iseries Access for Web 75

90 Monitor jobs This link displays the list of active jobs for the current user. The administrator could monitor the job list to check the status of the save library batch job. See Figure Figure 3-66 Viewing the active jobs 3.6 Troubleshooting This section offers helpful information for troubleshooting policies related to the *PUBLIC group profile and user and group profile. *PUBLIC group profile Administrators may have changed a setting within the *PUBLIC group profile only to find they need this function. The section shows a simple example with the *PUBLIC group profile. The navigation bar policy action changed to hide on group profile *PUBLIC. This policy change affected all iseries Access for Web users. To restore the Customize page, enter the following URL in a browser: Select General and edit the navigation bar policy. This example also demonstrates the ability to call the Java Servlet directly. The ability is available until a user or group profile is denied the function. 76 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

91 User and Group profiles Administrators may have defined a group profile with policies implemented but users continue to have access to denied functions. This section explains reviewing the user profile policies. A group profile has been defined with policies implemented. You discover a user still has access to a denied function. Follow these steps: 1. Display the policy not enforced at the user-profile level. 2. Ensure the Derived from column states Group-<Group Name>. 3. If the Derived from column states Profile setting, select Reset to default from the Action column. The Derived from column changes to Group-<Group Name>. Chapter 3. Using iseries Access for Web 77

92 78 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

93 4 Chapter 4. The iseries Access for Web V5R interface This chapter introduces the iseries Access for Web 5250 interface available in V5R2. iseries Access for Web V5R2 introduces a new 5250 interface with enhanced functionality. iseries Access for Web V5R1 used Host Publisher 3.5, specifically XML Legacy Gateway. This interface did not provide the same look and feel Client Access Express users and administrators had experienced in the past. The new V5R2 interface provides users a traditional 5250 look and feel. A Web view interface is also available for users who are more comfortable with the browser look and feel. Copyright IBM Corp All rights reserved. 79

94 4.1 Comparing the V5R2 interface and XML Gateway Table 4-1 illustrates the difference between the iseries Access for Web V5R2 interface and Host Publisher XML Gateway. Table 4-1 Interface comparison Function iseries Access for Web V5R2 Interface Host Publisher XML Gateway Requires Host Publisher V4.0 No Yes Multiple views Yes No Macro support Yes No Break message support No No Cursor positioning Yes No Special keystroke handling Yes No Workstation ID support Yes No Function key enhancements Yes No Save configured sessions Yes Yes- XML Legacy Gateway Portal Change interface colors Yes No 132 column support Yes No 4.2 Starting a 5250 session Figure 4-1 shows the 5250 tab of the iseries Access for Web. Figure tab iseries Access for Web has the ability to start a 5250 session from multiple locations: 5250-> Start Session or 5250-> Active Sessions-> Start session: Selecting this method always starts a new session to the default iseries server. You may change the default server and start a session to an iseries server not running iseries Access for Web. Figure 4-2 shows the Start Session page. 80 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

95 Figure Start Session 5250-> Configured Sessions-> Start (in Action column): This method provides the ability to start a configured session using saved configuration settings. The session settings have the ability to be changed and saved. 4.3 Configuring sessions iseries Access for Web provides multiple ways to configure a 5250 interface session. You can save the session for future usage once complete. iseries Access for Web also provides the ability to reload the IBM default settings interface configuration methods: Configure new session: Creates a new session Edit: Modifies an existing session in the configured sessions list Active session settings: Modifies the configuration of the currently active session on the active session page Saving Active session settings iseries Access for Web provides the ability to update the values for the current session or a configured session. Click the OK button to update the values for the current session. Click the Save button to update the current session and save the values in a configured session. Saving defaults Save as Defaults stores the current settings as defaults. The default settings are used in the following scenarios: When a new session is configured, the default values are used as initial values for the settings. Chapter 4. The iseries Access for Web V5R interface 81

96 When a Start Session is configured, the default settings are used to start the session. When a session is configured, you can click the Load Defaults button to replace the current settings with the saved defaults. Loading shipped defaults iseries Access for Web provides the ability to load shipped defaults. This function replaces the current settings with the shipped default settings. Load Shipped Defaults replaces the current settings with the configured default settings if saved. If default values are not saved, this has the same effect as using Load Shipped Defaults. iseries Access for Web uses the shipped default values if a saved version is not found Configuration options The following sections describe the available configuration options: General Server Workstation ID View General configuration options Figure 4-3 shows the General configuration options. We explain each option in the following sections. Figure 4-3 Editing the General session Session The session name identifies the session within the Configured sessions list. Default view This option specifies whether the Web view or the traditional view is used when this session is started: Web view: Presents the 5250 the same as other Web pages. This is the default view used by Start session. Web view uses links to handle menu options, cursor positioning, and messaging text help. The browser s default colors are used for displaying the page. Traditional view: Presents the 5250 in a traditional look and feel. Default colors include the familiar 5250 color scheme. The traditional view also provides more command entry input that acts more like a typical 5250 user interface. Enable advanced JavaScript functions for Internet Explorer Certain keystrokes are handled by JavaScript. This requires a browser that supports JavaScript and that has JavaScript enabled. Opera and Konqueror browsers are unable to handle 5250 interface keystroke enhancements. Enter key: Enter key handling for a 5250 session is always enabled for supported browsers with JavaScript enabled. If your browser doesn t support JavaScript, you can configure your browser to achieve the same result. Since most browsers support the first 82 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

97 button on the page as the default button, use My keypads to configure a single keypad with Enter as the first button. All other keypads cannot be shown. The function key bar must also be disabled using Session configuration. Page up, page down, 12 function keys (and shifted states): Enable advanced JavaScipt functions must be enabled for the keys to function. This option is enabled by default. When this option is enabled, Microsoft Internet Explorer (version 5.0 and higher) handles the requested 5250 interface functions. Server configuration options Figure 4-4 shows the Server configuration options. We explain each option in the following sections. Figure 4-4 Editing the session server Server Server identifies the TCP host name or the IP address for the iseries being accessed by this 5250 user interface session. An iseries that is not running iseries Access for Web may also be specified. Port Port identifies the port number used by the iseries Telnet server (TN5250) for incoming requests. The default port value is 23. Code page Code page identifies the translation table used to map EBCDIC data from the server to the appropriate character set for the browser. The default value is based on the Coded Character Set ID (CCSID) of the iseries Access for Web authenticated user ID. Review the iseries Access for Web 5250 User Interface Help text for a complete listing of code page values. Workstation ID configuration options Figure 4-5 shows the session workstation ID configuration options. We explain each option in the following sections. Figure 4-5 Session workstation ID Chapter 4. The iseries Access for Web V5R interface 83

98 The workstation ID identifies the device name used in the 5250 interface session. The maximum length of this value is ten characters. Additional characters are truncated. If a workstation device name is specified, system value QAUTOVRT must be set to 1, or the device must be manually created. If no workstation ID is specified, a system created virtual device is assigned. The 5250 interface creates a model 3477 device type by default. Important: The workstation ID must not start with a number and cannot contain a blank or any of the following characters: &, *, %, =, + Use user ID The iseries Access for Web user profile is used for the workstation ID. Specify workstation ID You may enter a workstation ID of your choice. If no value is entered, the system assigns a virtual device name. Avoid duplicates for this user This option avoids duplicate name conflicts for the current user. This option resolves conflicts within the servlet instance. iseries Access for Web identifies the session ID and resolves it within the iseries Access for Web code. Potential device ID conflicts are avoided with the current user. A wildcard character is added to the device name. If the device name is longer than ten characters, the last character is truncated before adding the wildcard character. The 5250 interface only creates one session with the device name if this option is not enabled. Additional requests result in an error. Avoid duplicates with other users This option avoids device name conflicts with other users on the same server. This option resolves conflicts within the TN5250 server. Potential device ID conflicts are avoided with other users, PC5250 sessions, or Host on Demand sessions. A wildcard character is added to the device name. If the device name is longer than ten characters, the last character is truncated before adding the wildcard character. The 5250 interface only creates one session with the device name if this option is not enabled. Additional requests result in an error. Table 4-2 shows the possible device names. Table 4-2 Workstation ID and possible device names Workstation ID option enabled None Avoid duplicates for this users Avoid duplicates from other users Avoid duplicates for this user and from other users Possible device ID Bennie BennieA Bennie1 BennieA1 Session view configuration options Figure 4-6 shows the session view configuration options and demonstrates the difference between Web and Traditional view options. 84 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

99 Figure 4-6 Session view Show navigation bar This option indicates whether the navigation bar is displayed when a 5250 interface session is active. Display text using a fixed-width font This option controls whether a fixed font or a proportional font is used for the 5250 user interface session. Figure 4-7 shows the proportional font in a Web view environment. Figure 4-7 Web view with proportional font enabled Figure 4-8 shows a fixed font enabled for Web view. Chapter 4. The iseries Access for Web V5R interface 85

100 Figure 4-8 Web with fixed font enabled Enable active function keys as buttons This option specifies whether the active function keys are enabled as buttons or displayed as text. Function keys displayed as text are used by the function key bar, a configured keypad, or the function keys on the keyboard. Figure 4-9 shows the current option enabled for Web view. Figure 4-9 Active function keys as buttons (enabled) Figure 4-10 shows the current option disabled for Web view. Figure 4-10 Active function keys as buttons (disabled) Enable More... as a button This option specifies fields containing More... are enabled as buttons or displayed as text. If More... fields are displayed as text, additional pages can be retrieved using a page down on a keypad or the page down key on the keyboard. Figure 4-11 shows an example of the More... button option enabled. 86 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

101 Figure 4-11 Enabling the More... as button (enabled) Enable menu items as links This option indicates whether menu option numbers on menus (1 through 99) are displayed as links. When this settings is disabled, users must enter the menu option number from a command line. Figure 4-12 shows the menu items as links. Figure 4-12 Menu items as links (enabled) Figure 4-13 shows the traditional method of menu options. Chapter 4. The iseries Access for Web V5R interface 87

102 Figure 4-13 Menu items as links (disabled) Show function key bar This option is used to display the function key bar beneath the 5250 interface session. The function key bar contains functions keys F1 through F24 displayed as buttons. The function key bar layout and content cannot be configured. You must use My keypads to display a customized keypad. Figure 4-14 shows the function key bar. Figure 4-14 Function key bar Enable macros This option controls a user s ability to play and record macros. Users can still access My macros. Enable cursor positioning This option indicates whether non-input fields are implemented as links or as plain text. If non-input fields are implemented as links, choosing a link updates the current cursor position. If the Enable message text line as help text link option is also enabled, the message text line option overrides the cursor positioning behavior. This option enables the support for 5250 interface functions F1, F4, F9, and other cursor positioning functions. Enable message text line as help text This option enables the message text line as a link to the help for the message. The link places the cursor on the line and submits the F1 function. The message text line is at the bottom of the page. If this option is not enabled, the Enable cursor positioning option can be used to enable the link for help on a message. Figure 4-15 shows the enable message text line enabled. 88 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

103 Figure 4-15 Enabled message text line Show function key (Fxx=) on button This option specifies whether Fxx= is included on the button text, when Enable active function keys as buttons is enabled. If Enable active function keys as buttons is not enabled the value is ignored. The traditional view always includes Fxx= when active functions appear as buttons on the page. Figure 4-16 shows the option disabled. Figure 4-16 Show function key description on button (disabled) Figure 4-17 shows the option enabled. Figure 4-17 Show function key description on button (enabled) Colors This option specifies how 5250 session colors are mapped to browser colors when an active session is displayed. The foreground colors for fields and Operator Information Area (OIA) are fully configurable for both the Web view and the traditional view. The background colors for fields are fully configurable within the traditional view. The Web view always uses the current browser background colors. 4.4 Usage This section discusses the usage information for the 5250 interface that is provided by iseries Access for Web V5R Synchronize iseries Access for Web may encounter situations when the browser window does not match the current state of the 5250 session. Figure 4-18 shows how this can happen when using the browser s back button. Chapter 4. The iseries Access for Web V5R interface 89

104 Figure 4-18 Browser back button Figure 4-19 shows receiving a break message. Figure 4-19 Break message Figure 4-20 shows an automatic update program. 90 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

105 Figure 4-20 Automatic update Figure 4-21 demonstrates a session timeout. Figure 4-21 Session timeout Important: To synchronize the browser page with the session state, use the Refresh Screen button on the 5250 user interface keypad My Macros The iseries Access for Web 5250 user interface supports creating and saving macros. The macro support provided by iseries Access for Web differs from the PC5250 product. PC5250 macros are comprised of a series of keystrokes user interface macros are made up of a series of cursor position commands and user input. With My Macros, you can delete and edit recorded macros. Chapter 4. The iseries Access for Web V5R interface 91

106 Recording a macro To create a macro, use the Start Recording button on the active session page. The macro must be given a unique name within the My Macros list. Once a recording is started, all subsequent cursor position changes and user input are recorded in the macro. Recording can be paused with the Pause Recording button. Recording resumes when you click the Resume Recording button. To stop the recording process, click the Stop Recording button. Figure 4-22 shows an example of the record macro page. Figure 4-22 Record Macro Playing a macro To play a macro, choose the macro name from the drop-down list on the active session page and click the Play button. Macros are not restricted to the session in which they were created. You can play them from any session. Edit Use the Edit function to modify an existing macro. When you choose this action, the recorded cursor positioning commands and user input are displayed in an input area. Figure 4-23 shows the edit macro input area. You can change or delete these values, or you can add new values. The iseries Access for Web 5250 User Interface Help text provides a complete list of supported cursor positioning commands. Figure 4-23 Edit Macro 92 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

107 4.4.3 My Keypads iseries Access for Web provides the ability to customize keypads. My Keypads configures the number, location, and content of keypads displayed on an active 5250 session page. Attention: The keypad configuration is used for all sessions and is not associated with a specific session configuration. Figure 4-24 shows the My Keypad page. Figure 4-24 My Keypads Show Keypad You can display keypads above the 5250 window, beneath the window, or next to the window. Multiple keypads can display at the same time. By default, only the bottom keypad is shown. Keypad Layout The keypad layout is configured by selecting the desired number of rows and columns. Once changes are made, you can click the Configure button to define the actions associated with each button. Decreasing the size of the keypad without configuring truncates keys from the keypad. Increasing the side of the keypad without configuring does not add any keys to the keypad. Chapter 4. The iseries Access for Web V5R interface 93

108 Configure Keypad Keypad configuration associates an action with each button in the keypad. The list of available actions is displayed in a drop-down list for each button. Macros may be configured as keys. A special value of None indicates a button should not be shown in this position. This is useful for making a button, near this position, more noticeable. Adding a macro to the keypad The following steps explain how to add a macro to the keypad: 1. Create a macro as explained in 4.4.2, My Macros on page Click My Keypads. The My Keypads page opens as shown in Figure Locate the keypad you want to configure. Click Configure. You can see a small piece of the bottom keypad configuration in Figure Figure 4-25 Configuring My Keypad 4. Locate the key to be edited. Select the down arrow and click the name of the macro. 5. Click OK. 6. Click Save Cursor positioning Active sessions Several iseries functions use the current cursor position to carry out their tasks. Several examples include the F1, F4, and F9 keys. The 5250 user interface supports this functionality using links and JavaScript. Input fields and non-input fields are handled differently: Non-input fields: Within the session view, you can see the Enable cursor positioning option. This option shows all non-blank and non-input fields as links. Selecting the link updates the current cursor position from the session. This current cursor position is also displayed in the lower right-hand corner of the window, in the OIA. When a cursor-sensitive function is invoked, the current cursor position is used. Input fields: The 5250 user interface uses JavaScript to handle cursor positioning for input fields. This option is always enabled if the browser supports JavaScript and is configured to use it. The current cursor position is not updated in the OIA when the cursor is placed in an input field. iseries Access for Web contains an Active session link via the 5250 tab. This link provides users a list of active sessions. The following information is presented to the user. Server Session Started Last Accessed View 94 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

109 Action Reconnect Stop Reconnect A user may leave an active 5250 session by going to another URL or shutting down the browser, but the session remains active. Important: Active sessions remain active until the user stops the session. To reconnect to a session that is still active, click the Active Session link in the 5250 tab. All active sessions for the user are displayed. Click Reconnect to reconnect to the session. Stop To stop an active session, perform one of the following actions: Click the Stop session link in the active session list. Click the Stop session button from the interface page. Cleaning up sessions iseries Access for Web provides an inactive session timeout based on user or group profiles. This customization function ends interactive sessions when the timeout is exceeded. The inactive session timeout is located under Customize-> User Profile or Group Profile-> Limiting functionality iseries Access for Web provides users multiple ways to configure and start a 5250 interface session. Administrators can restrict access to this interface, using the Start 5250 sessions policy. When this policy is set to deny, users cannot configure or start 5250 sessions shortcut You can create a desktop shortcut to access the 5250 interface. We outline the process in the following steps: 1. In iseries Access for Web, click the 5250 tab to configure a session. 2. Verify that the Show navigation bar option is disabled. This provides you the greatest window size. You may enable or disable other functions depending on your preferences. 3. Click Save. The session saves under the user profile. 4. Click Start. The iseries signon window opens with the configured options enabled. 5. Save the Web page as a Favorite within your browser. 6. Create a shortcut and place it on the desktop. This shortcut provides a direct 5250 interface session for the current user. Figure 4-26 shows a renamed direct 5250 interface shortcut. Figure 4-26 Renamed 5250 interface shortcut Chapter 4. The iseries Access for Web V5R interface 95

110 Administrators may have several different users accessing the iseries from one PC. A direct link shortcut works for multiple users if they have the same session name configured. If the profile does not have a the session defined, an error message is displayed. Figure 4-27 shows an example of the 5250 error messages when a configured session does not exist. Figure Error You can also create a shortcut to the following URL: Users need to start a pre-configured 5250 interface session by clicking Start. 4.6 Where to find more information Refer to the iseries Access for Web 5250 User Interface Help text for more information on: The 5250 interface for iseries Access for Web National Language Support (NLS) considerations 96 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

111 5 Chapter 5. Installation and administration of WebSphere Host Publisher Server This chapter describes the installation, configuration, and administration of the WebSphere Host Publisher program product. The complete setup consists of the installation of the two components, which are installed separately: Host Publisher Server is installed on an iseries server Host Publisher Studio is installed on a Windows workstation You can find detailed instructions for the installation, configuration, and administration of Host Publisher Version 4.0 in: IBM WebSphere Host Publisher Administration and Users Guide, GC IBM WebSphere Host Publisher Planning and Installation Guide, SC Before you attempt to install and configure WebSphere Host Publisher Server, you must ensure you have these publications available. Copyright IBM Corp All rights reserved. 97

112 5.1 Hardware and software requirements Host Publisher Server runs on the iseries server. Host Publisher Studio runs on the Windows platform (Windows 98, Windows NT 4.0, Windows 2000, Windows Me, and Windows XP) Hardware requirements Host Publisher Version 4.0 runs on any iseries server on which WebSphere Application Server V4.0 is supported. Server model numbers and feature codes are listed in the WebSphere for iseries Documentation Center at: For the processor requirements, refer to the processor requirements for WebSphere V4.0. Note the following hardware requirements: Systems that are hosting applications using EJBs, servlets, and JSPs require a hardware configuration with any of the servers (required minimum) listed in Table 5-1. Table 5-1 Systems running applications using EJBs, servlets, and JSPs Model Processor feature CPW AS/400e server AS/400e server iseries Model iseries Model Systems that are hosting applications using only servlets and JSPs require the hardware configuration for any of the servers (recommended minimum) listed in Table 5-2. Table 5-2 Systems running applications using only servlets and JSPs Model Processor feature CPW AS/400e server AS/400e server iseries Model iseries Model In addition, you must have the following requirements: A minimum of 1 GB RAM 200 MB DASD - Host Publisher Server base code Software requirements Host Publisher Version 4.0 requires the OS/400 and WebSphere Application Server levels that are outlined in the following sections. OS/400 Host Publisher Server requires OS/400 V4R5, V5R1, or V5R2 with the latest cumulative PTF package applied. 98 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

113 WebSphere Application Server Before you install Host Publisher Server, you must install and configure one of the versions of WebSphere Application Server listed in Table 5-3. You must also ensure that the version is running properly with all the most recent PTFs installed. Table 5-3 WebSphere levels required for Host Publisher Server Product ID Version Product name 5733-WS or later WebSphere Application Server, Advanced Single Server Edition 5733-WA or later WebSphere Application Server, Advanced Edition For WebSphere prerequisite information, refer to the WebSphere for iseries documentation center (click the Documentation link) at: You can find information about the latest WebSphere Application Server PTFs at the same location (select PTFs). Other software The software products listed in Table 5-4 are also required. Table 5-4 Software required for Host Publisher Server Product ID Option Product name 5722 SS1 30 OS/400 Qshell Interpreter 5722 DG1 Base IBM HTTP Server for iseries 5722 JC1 Base Toolbox for Java 5722 JV1 Base Developer Kit for Java 5722 JV1 5 Developer Kit for Java version TC1 Base TCP/IP Connectivity Utilities Host Publisher Studio To use Host Publisher Studio, you must comply with the following hardware and software requirements: Hardware requirements Pentium II 366 processor, minimum of 128 MB RAM. Recommended is a Pentium II 450 processor, 256 MB RAM 300 MB of free disk space, add more for your Host Publisher applications. 1 GB recommended A display with a color depth of 256 colors or higher, and a minimum screen resolution of 800 x 600 pixels Note: The requirements pertain only to Host Publisher Studio. Other products running on the workstation with Host Publisher Studio may require additional resources. Chapter 5. Installation and administration of WebSphere Host Publisher Server 99

114 Software requirements One of the following operating systems is required: Windows NT 4.0 (Workstation or Server) Windows Me Windows 98 Windows 2000 (Professional, Server, or Advanced Server) Windows XP 5.2 Installing and uninstalling Host Publisher Server This section explains the preliminary considerations you must address before you install Host Publisher Server Version 4.0 on the iseries server. Then it explains how to install and uninstall Host Publisher Server and Host Publisher Studio Preliminary considerations Before you install Host Publisher Server Version 4.0 on the iseries server, you must be aware of following considerations. Host Publisher Server cannot coexist with other versions Only one version of Host Publisher Server can be installed on the iseries server. On the iseries platform, a given edition of WebSphere Application Server can be installed only once. However, its subsystem may run multiple concurrent copies of WebSphere Application Server in the WebSphere subsystem. Each copy is referred to as a WebSphere Administrative Server, and an WebSphere Administrative Server named default is setup automatically when WebSphere Application Server is installed. Each WebSphere Administrative Server has its own resources and can have many application servers. Host Publisher Server for iseries can only be configured to one WebSphere Administrative Server. However, a Host Publisher application server can be cloned multiple times under a WebSphere Administrative Server. For details on cloning, refer to the WebSphere V4.0 documentation on the WebSphere Application Server Web site at: You should also refer to Chapter 17 in the IBM WebSphere V4.0 Advanced Edition Handbook, SG If a previous version of Host Publisher Server is installed on the iseries server, the setup instructions in 5.2.2, Installing Host Publisher Server on page 103, and 5.4, Migrating applications and XML Gateway sessions on page 136, show how to uninstall the previous version and to migrate your applications to Host Publisher Version 4.0. To find previous versions of Host Publisher Server on the iseries, you can use the Display Software Resources (DSPSFWRSC) command and look for: 5648-D31 (Host Publisher V2.2.1) 5648-E25 (Host Publisher V3.5) 100 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

115 Host Publisher Server licensing Host Publisher Server Version 4.0 shipped with iseries Access Family is only licensed to run on iseries and to access iseries resources (no 3270 or VT). For active Host Publisher functions, such as converted user applications and XML Gateway sessions, the license is managed by the iseries Access Family (5722-XW1) product. WebSphere Application Server Version 4.0 skills WebSphere Application Server Version 4.0 is a prerequisite of Host Publisher Version 4.0. A successful implementation of Host Publisher Server requires you to have WebSphere Application Server Version 4.0 skills. You can find information on setting up and using WebSphere Application Server and WebSphere Administrative Console in IBM WebSphere V4.0 Advanced Edition Handbook, SG , and on the Web site for WebSphere Application Server for iseries: WebSphere product level WebSphere Advanced Edition or Advanced Single Server Edition must be installed and at fix level or later. If WebSphere 4.0 is not installed on the iseries server, you should uninstall the previous version of Host Publisher Server, install WebSphere 4.0, and then install Host Publisher Server Version 4.0. Note the following considerations: WebSphere 4.0 can coexist on the iseries server with other versions of WebSphere. If WebSphere 4.0 is to be installed and a previous version of WebSphere is installed on the iseries server, consult the WebSphere Application Server V4.0 migration documentation on the Web by selecting the Migration link: Refer to the WebSphere for iseries home page (see the Web address in the previous bullet) for information about the latest available PTFs for WebSphere on the iseries server. Table 5-5 shows you an overview of the group PTF numbers. Table 5-5 Overview of group PTFs Product ID V5R1 V4R WA4 SF99241 SF WS4 SF99242 SF99240 Verifying the WebSphere V4.0 level The level of WebSphere Application Server is contained in a data area in the WebSphere Application Server library. The name of the data area is the group PTF number. Use the DSPTAARA command to retrieve the information. For WebSphere Application Server Advanced Edition, the command is: DSPDTAARA QEJBADV4/SF99241 For WebSphere Application Server Advanced Single Server edition, the command is: DSPDTAARA QEJBAES4/SF99242 The result of the command for WebSphere Application Server Advanced Edition is shown in Figure 5-1. Chapter 5. Installation and administration of WebSphere Host Publisher Server 101

116 Data area : SF99241 Library : QEJBADV4 Type : *CHAR Length : 50 Text : Display Data Area system: SYSTEMNAME Value Offset * 'Group PTF#: SF WA4 V5R1 02/01/ ' Press Enter to continue. Bottom F3=Exit F12=Cancel Figure 5-1 Verifying the level of WebSphere V4.0 Note: The DSPDTAARA command is available for every release of OS/400. Verify the name of the product library and the group PTF number. Refer to the WebSphere for iseries home page for information about the latest available PTFs for WebSphere on the iseries server: Select PTF and read the information for your version of WebSphere Application Server and OS/400 release. Packaging information If you have V5R1 Client Access Family (5722-XW1) with software subscription, order the 5722-XW1 refresh (feature 2645). In addition to the V5R1 Client Access Family products, you receive the V5R2 versions of: iseries Access for Windows formerly Client Access Express for Windows (5722-XW1) in two forms: PC media to install directly on the PC iseries media to install the program product on the server iseries Access for Web media (5722-XH2) Host Publisher V4.0 Host Publisher Server CD for installation on the iseries Host Publisher Studio CD for installation on the PC iseries Client Encryption, 128-bit (5722-CE3) 102 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

117 For new orders of V5R XW1, include the 5722-XW1 refresh (feature 2645) to receive the V5R2 iseries Access products we listed, in addition to the V5R1 Client Access Family products. On the iseries server, the product number of Host Publisher Server V4.0 is 5724-B81. Installation destinations Host Publisher Server is a Java-based product. Most of the product s files are installed to the integrated file system (IFS) of the iseries server. The installation directories are /QIBM/ProdData/HostPublisher and /QIBM/UserData/HostPublisher. In addition, some objects are installed to the QHPN library in the native library file system. *SECOFR authority required The user profile used to perform the installation and configuration must have *SECOFR authority Installing Host Publisher Server Host Publisher Server is installed on the iseries server. This section guides you through the required steps: 1. Preparing to install Host Publisher Server 2. Installing the Host Publisher Server program code 3. Starting the Web application server 4. Testing the installation of Host Publisher Server During installation, the installation and configuration programs install and cfghpsvr perform the following actions on your system: Install the Host Publisher Server program and documentation files. Update the WebSphere configuration to include: A Host Publisher Application Server (Advanced Edition only) The Host Publisher Administration application (HPAdmin.ear) The Host Publisher Documentation application (HPDoc.ear) The Host Publisher XML Gateway application (xmllegacygw.ear) Modify the WebSphere configuration to define the Host Publisher Server Administration servlet and enable WebSphere to access your Host Publisher documents. Host Publisher is configured in the WebSphere Administrative Server of WebSphere Application Server you select. Uninstalling the previous version of Host Publisher If a previous version of Host Publisher Server is installed on the iseries server, you must uninstall it. Follow these steps to uninstall a previous version: 1. Sign on to the server using a profile that has *SECOFR authority. 2. Perform the following steps to ensure WebSphere Application Server is active: a. Run the following command: WRKACTJOB SBS(QEJBSBS) Note: Earlier versions of Host Publisher run with WebSphere Application Server V3.5. Therefore, you must look for the subsystem QEJBSBS. Chapter 5. Installation and administration of WebSphere Host Publisher Server 103

118 b. If the subsystem is not running, run the following command: STRSBS QEJB/QEJBSBS c. Select option 5 for the QEJBADMIN job. d. Select option 10 to view the job log, and verify that the WebSphere administrative server QEJBADMIN is ready message is displayed. 3. Uninstall Host Publisher Server by running one of the following commands: For Host Publisher V2.2.1: DLTLICPGM LICPGM(5648D31) For Host Publisher V3.5: DLTLICPGM LICPGM(5648E25) 4. Refresh the view of application servers in the WebSphere Administrative Console, and verify that the HostPubServer application server was deleted. After you delete Host Publisher Server, your Host Publisher applications remain on the system. After you install Host Publisher Version 4.0, existing applications must be migrated to function with the new version of the product. The migration steps are outlined in 5.4, Migrating applications and XML Gateway sessions on page 136. Preparing to install Host Publisher Server Host Publisher Server can be installed with WebSphere Host Publisher Server Advanced Edition 4.0 or with WebSphere Host Publishing Server Advanced Single Server Edition 4.0. The preparation depends on the version you use. You must verify whether the required software is installed and WebSphere Application Server is up and running: For installation with WebSphere Application Server Advanced Edition V4.0: a. Sign on to the server using a profile that has *SECOFR authority. b. Verify that all the prerequisite software is installed by running the command: GO LICPGM Select option 10 to display what is installed on the server. c. Verify if WebSphere Application Server Advanced Edition is active: i. Run the WRKACTJOB command, and look for the QEJBADV4 subsystem. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

119 Work with Active Jobs SYSTEMNAME 04/30/02 13:21:18 CPU %:.0 Elapsed time: 00:00:00 Active jobs: 367 Type options, press Enter. 2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message 8=Work with spooled files 13=Disconnect... Opt Subsystem/Job User Type CPU % Function Status QBATCH QSYS SBS.0 DEQW QCMN QSYS SBS.0 DEQW QCTL QSYS SBS.0 DEQW QSYSSCD QPGMR BCH.0 PGM-QEZSCNEP EVTW QEJBADV4 QSYS SBS.0 DEQW DEFAULT_SE QEJB BCI.0 PGM-QEJBSVR JVAW ISERIESACC QEJB BCI.0 PGM-QEJBSVR JVAW QEJBADMIN QEJB BCI.0 PGM-QEJBADMIN JVAW QEJBMNTR QEJB ASJ.0 PGM-QEJBMNTR EVTW More... Parameters or command ===> F3=Exit F5=Refresh F7=Find F10=Restart statistics F11=Display elapsed data F12=Cancel F23=More options F24=More keys Figure 5-2 Verifying if WebSphere Application Server Advanced Edition is active ii. If the subsystem is not running, run the CL command: STRSBS QEJBADV4/QEJBADV4 iii. Select option 5 on the QEJBADMIN job or the ADMIN job listed for your administrative instance. If the ADMIN job is not listed, refer to the WebSphere documentation for starting administrative instances. iv. Select option 10 and verify that the WebSphere administrative server QEJBADMIN is ready message is displayed. Figure 5-3 shows an example of this message. Chapter 5. Installation and administration of WebSphere Host Publisher Server 105

120 Display Job Log System: SYSTEMNAME Job.. : QEJBADMIN User.. : QEJB Number... : Job /QEJB/QEJBADMIN started on 04/05/02 at 09:17:59 in subsystem QEJBADV4 in QEJBADV4. Job entered system on 04/05/02 at 09:17:59. WebSphere server started with JDK Job /QUSER/QSQSRVR used for SQL server mode processing. Job /QUSER/QSQSRVR used for SQL server mode processing. Job /QUSER/QSQSRVR used for SQL server mode processing. >>>>WebSphere administrative server QEJBADMIN ready. Job /QUSER/QSQSRVR used for SQL server mode processing. Job /QUSER/QSQSRVR used for SQL server mode processing. Job /QUSER/QSQSRVR used for SQL server mode processing. WebSphere application server job /QEJB/ISERIESACC started. Job /QUSER/QSQSRVR used for SQL server mode processing. Job /QUSER/QSQSRVR used for SQL server mode processing. More... Press Enter to continue. F3=Exit F5=Refresh F10=Display detailed messages F12=Cancel F16=Job menu F24=More keys Figure 5-3 QEJBADMIN is running For installation with WebSphere Application Server Advanced Single Server Edition: a. Sign on to the server using a profile that has *SECOFR authority. b. Verify that all the prerequisite software is installed by running the command: GO LICPGM Select option 10 to display what is installed on the server. c. Verify if WebSphere Application Server Advanced Single Server Edition is active: i. Run the WRKACTJOB command, and look for the QEJBAES4 subsystem. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

121 WORK WITH ACTIVE JOBS SYSTEMNAME 05/01/02 22:02:33 CPU %: 1.9 ELAPSED TIME: 04:17:47 ACTIVE JOBS: 231 TYPE OPTIONS, PRESS ENTER. 2=CHANGE 3=HOLD 4=END 5=WORK WITH 6=RELEASE 7=DISPLAY MESSAGE 8=WORK WITH SPOOLED FILES 13=DISCONNECT... OPT SUBSYSTEM/JOB USER TYPE CPU % FUNCTION STATUS QEJBAES4 QSYS SBS.0 DEQW DEFAULT_SE QEJB BCI.8 PGM-QEJBSVR JVAW QHTTPSVR QSYS SBS.0 DEQW ADMIN QTMHHTTP BCH.0 PGM-QZHBHTTP SIGW ADMIN QTMHHTTP BCI.0 PGM-QZSRLOG SIGW ADMIN QTMHHTTP BCI.0 PGM-QZSRHTTP SIGW ADMIN QTMHHTTP BCI.0 PGM-QYUNLANG TIMW APACHE4AE QTMHHTTP BCH.0 PGM-QZHBHTTP SIGW APACHE4AE QTMHHTTP BCI.0 PGM-QZSRLOG SIGW MORE... PARAMETERS OR COMMAND ===> F3=EXIT F5=REFRESH F7=FIND F10=RESTART STATISTICS F11=DISPLAY ELAPSED DATA F12=CANCEL F23=MORE OPTIONS F24=MORE KEYS Figure 5-4 Verifying if WebSphere Application Advanced Single Server Edition is active ii. If the subsystem is not running, run the CL command: STRSBS QEJBAES4/QEJBAES4 iii. Select option 5 on the DEFAULT_SERVER job. iv. Select option 10, and verify that the WebSphere Application Server Default Server ready message is displayed (see Figure 5-5). DISPLAY JOB LOG SYSTEM:SYSTEMNAME JOB.. : DEFAULT_SE USER.. : QEJB NUMBER... : JOB /QEJB/DEFAULT_SE STARTED ON 05/01/02 AT 16:38:37 IN SUBSYSTEM QEJBAES4 IN QEJBAES4. JOB ENTERED SYSTEM ON 05/01/02 AT 16:38:37. SERVER STARTING WITH USER PROFILE QEJBSVR. WEBSPHERE SERVER STARTED WITH JDK JOB /QUSER/QSQSRVR USED FOR SQL SERVER MODE PROCESSING. JOB /QUSER/QSQSRVR USED FOR SQL SERVER MODE PROCESSING. >>> WEBSPHERE APPLICATION SERVER Default Server READY. PRESS ENTER TO CONTINUE. BOTTOM F3=EXIT F5=REFRESH F10=DISPLAY DETAILED MESSAGES F12=CANCEL F16=JOB MENU F24=MORE KEYS Figure 5-5 WebSphere Application Server Default server ready Chapter 5. Installation and administration of WebSphere Host Publisher Server 107

122 Installing the Host Publisher Server program code These steps walk you through the installation: 1. Insert the Host Publisher Server CD-ROM into the CD driver on the server. 2. Run the qsh command. 3. In the QSH Command Entry session, follow these steps: a. Run the following command: cd /QOPT/HP40 This takes you to the directory from which to run the install command (see Figure 5-6). Note: This step is identical for WebSphere Application Server Advanced Edition and Advanced Single Server Edition. QSH Command Entry ===> cd /qopt/hp40 F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-6 Command cd /qopt/hp40 b. Run the install command: install [-silent ] Here the optional parameter -silent performs a silent installation. Messages are logged to the file QIBM/ProdData/HostPublisher/Install/HPInstall.log. 4. When the install command completes, review the displayed messages (see Figure 5-7) and follow any instructions that are displayed. 108 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

123 QSH Command Entry $ > install In s talling Host Publisher Server. Please wait. Copying stream file to save file. Restoring licensed program. Installation completed successfully. $ ===> F 3= E xi t F 6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-7 Completion of the install command 5. Verify the installation log, which is in QIBM/ProdData/HostPublisher/Install/HPInstall.log. Use the WRKLNK CL command to retrieve the log and DSPF command to display the log: WRKLNK OBJ('/QIBM/ProdData/HostPublisher/install/HPInstall.log') DSPF STMF( /QIBM/ProdData/HostPublisher/install/HPInstall.log ) See Figure 5-8 for the WRKLNK display. For more details on the HPInstall.log, see Example 8-1 on page 268. Work with Object Links Directory.... : /QIBM/ProdData/HostPublisher/install Type options, press Enter. 2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes 11=Change current directory... Opt Object link Type Attribute Text 5 HPInstall.log STMF Bottom Parameters or command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel F17=Position to F22=Display entire field F23=More options Figure 5-8 Verifying the install log by selecting option 5 (Display) Chapter 5. Installation and administration of WebSphere Host Publisher Server 109

124 6. Run the cfghpsvr command: a. Run the QSH command, if you don t have a QSH command entry screen. b. Change to the QIBM directory: cd QIBM c. Go to the ProdData directory: cd ProdData d. Go to the HostPublisher directory: cd Hostpublisher e. Enter the cfghpsvr command. The format of the command is: cfghpsvr [-instance instance][-configfile AEs_config_file ][-was WAS_edition ][-iwa ][-silent ] Note the following explanation: -instance instance: Specifies the name of the WebSphere Application Server administrative instance in which Host Publisher is to be configured. The default value is default. -configfile AEs_config_file (WebSphere Advanced Single Server Edition only): Specifies the name of the server-cfg.xml file. The default is the active configuration file in WebSphere Application Server, found in the admin.configfile property in /QIBM/UserData/WebASAEs4/instance/properties/admin.properties. -was WAS_edition: Specifies the edition of WebSphere Application Server in which Host Publisher is to be configured. This parameter is necessary only if both editions of WebSphere Application Server are installed on the iseries server. Possible values for WAS_edition are: ADV4: WebSphere Advanced Edition Version 4.0 AES4: WebSphere Advanced Single Server Edition 4.0 The default is ADV4, if installed. -iwa: Configures WebSphere Host Publisher for integration with iseries Access for Web. This option makes iseries Access for Web handle the licensing for the WebSphere Host Publisher users. -silent: Runs cfghpsvr silently. In this example, cfghpsvr is set up for use together with iseries Access for Web, on the default server, which is WebSphere Application Server Advanced Edition: cfghpsvr -instance default -was ADV4 -iwa See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

125 QSH Command Entry $ > cd qibm $ > cd proddata $ > cd hostpublisher $ ===> cfghpsvr -instance default -was ADV4 -iwa F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-9 The cfghpsvr command 7. When the cfghpsvr command completes, review the displayed messages and follow the instructions that are displayed (Figure 5-10). Additional messages are logged into the install log file in /QIBM/ProdData/HostPublisher/Install/HPInstall.log. An extract of the log information is shown in Example 8-2 on page 269. QSH Command Entry $ > cd qibm $ > cd proddata $ > cd hostpublisher $ > cfghpsvr -instance default -was ADV4 -iwa Host Publisher will be configured with WebSphere Application Server Advanced Edition Host Publisher will be configured with iseries Access for Web Configuration completed successfully. $ ===> F 3= E xi t F 6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-10 Completion of cfghpsvr Chapter 5. Installation and administration of WebSphere Host Publisher Server 111

126 8. If you use cfghpsvr for WebSphere Application Server, Advanced Single Server Edition, the command can be: cfghpsvr -instance default -configfile /QIBM//UserData/WebASAEs4/default/config/server-cfg.xml -was AES4 -iwa Figure 5-11 shows the completion of the cfghpsvr command for WebSphere Application Server Advanced Single Server Edition. QSH COMMAND ENTRY $ > cfghpsvr -instance default -configfile /QIBM/UserData/WebASAEs4/default/config/server-cfg.xml -was AES4 -iwa Host Publisher will be configured with WebSphere Application Server Advanced Single Server Edition Host Publisher will be configured with iseries Access for Web Configuration completed successfully. $ ===> F3=EXIT F6=PRINT F9=RETRIEVE F12=DISCONNECT F13=CLEAR F17=TOP F18=BOTTOM F21=CL COMMAND ENTRY Figure 5-11 cfghpsvr for AES4 completion 9. Press F3 to exit the QSH command entry session. 10.After the installation, you can see: The files are added into /QIBM/ProdData/HostPublisher (Figure 5-12) and into /QIBM/Userdata/HostPublisher (Figure 5-13). 112 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

127 Figure 5-12 Host Publisher files installed in QIBM/ProdData/HostPublisher Figure 5-13 Host Publisher files in QIBM/UserData/HostPublisher Chapter 5. Installation and administration of WebSphere Host Publisher Server 113

128 For both versions of WebSphere Application Server, you have identical files in QIBM/ProdData/HostPublisher and QIBM/UserData/HostPublisher. WebSphere Application Server Administrative Console information You can see the HostPubServ as application server and HPAdmin, HPDoc, and xmlgateway as enterprise applications in the WebSphere Administrative Server. Figure 5-14 shows a view of the administrative console of the WebSphere Application Server, Advanced Edition. Figure 5-14 WebSphere Application Server console Figure 5-15 shows the administrative console of the WebSphere Application Server Single Server Edition after installation. 114 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

129 Figure 5-15 WebSphere Application Server Advanced Single Server Edition after installation To use the WebSphere Advanced administrative console, refer to the WebSphere installation and setup information documentation in the WebSphere for iseries Documentation Center at: Navigate to the installation and initial configuration sections for the version you use. Starting Web application servers You must restart the WebSphere Application Server after you install the Host Publisher Server: If Host Publisher was configured for WebSphere Application Server Advanced Edition, start the HostPubServer application server: a. Using the WebSphere Advanced Administrative Console, select the application server named HostPubServer (see Figure 5-14). b. Click Start. c. Check the Console Messages area to verify that the start command completed successfully. If Host Publisher was configured for WebSphere Advanced Server, Single Server Edition, restart WebSphere: a. Run the following command to stop the WebSphere Application Server: ENDSBS QEJBAES4/QEJBAES4 b. Run the following command to restart WebSphere: STRSBS QEJBAES4/QEJBAES4 Chapter 5. Installation and administration of WebSphere Host Publisher Server 115

130 c. Run the following command: WRKACTJOB SBS(QEJBAES4) d. Select option 5 for the DEFAULT_SE job. e. Select option 10 and verify that the Ready message is displayed. f. If Host Publisher was configured for a WebSphere administrative server other than the default, start that administrative server now: i. Select option 5 for your instance s job. ii. Select option 10 and verify that the Ready message is displayed. Testing the installation of Host Publisher Server After you install Host Publisher Version 4.0, you must test the installation. In your browser, load: Host Publisher Server Administration: Here server is the server name. The Host Publisher Server Administration page is shown in Figure Figure 5-16 Host Publisher Server Administration ShowCfg configuration parameters: You can find detailed information about showcfg in Table B-1 on page iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

131 Troubleshooting If either Host Publisher Server Administration or ShowCfg fails to load, check the Host Publisher Server configuration of WebSphere Application Server as explained in the following sections. Testing with WebSphere Advanced Edition To test the installation with WebSphere Advanced Edition, perform the following steps: 1. Confirm that HostPubServer application server is active: a. Using the tree view in the WebSphere Administrative Console, expand WebSphere Administrative Domain-> Nodes-> your node name. b. Select Application Servers. c. Click Refresh. HostPubServer should be listed in the details view, with a status of Running. 2. If HostPubServer is inactive, perform the following steps to activate it: a. Using the tree view in WebSphere Administrative Console, expand Application Servers. b. Select the application server named HostPubServer. c. Click Start, or select Console-> Start. d. Check the Console Messages area to verify that the start command completed successfully. 3. Confirm that HPDoc, HPAdmin, and xmlgateway appear as installed Enterprise Applications in the WebSphere Application Server topology: a. Using the tree view in the WebSphere Administrative Console, expand WebSphere Administrative Domain. b. Select Enterprise Applications. c. Click Refresh. HPDoc, HPAdmin, and xmlgateway should display in the details view. 4. If WebSphere is not configured properly for Host Publisher, run the Host Publisher deploy command: a. Confirm that the WebSphere administrative server job is started and ready: i. Run the following server command: WRKACTJOB SBS(QEJBADV4) ii. If the subsystem is not running, run the following server command: STRSBS QEJBADV4/QEJBADV4 iii. Select option 5 on the QEJBADMIN job or the ADMIN job listed for your administrative server. If the ADMIN job is not listed, refer to the WebSphere for iseries Documentation Center for starting administrative servers. iv. Select option 10 and verify that the Ready message is displayed. b. Run the QSH command. c. In the QSH command entry session, run the command: cd /QIBM/ProdData/HostPublisher AEOS400Deploy This command is shown in Figure Chapter 5. Installation and administration of WebSphere Host Publisher Server 117

132 QSH Command Entry $ > cd /qibm/proddata/hostpublisher $ > AEOS400Deploy Check /QIBM/UserData/HostPublisher/log/AEdeploy.log for the results of the deployment. $ ===> F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-17 AEOS400deploy d. Check for error messages in the /QIBM/UserData/HostPublisher/log/AEdeploy.log deploy log file as shown in Figure Figure 5-18 AEdeploy log e. Press F3 to exit the QSH command entry session. Testing with WebSphere Advanced Single Server Edition To test the installation with WebSphere Advanced Single Server Edition, follow these steps: 1. Confirm that WebSphere is running by entering the following command: WRKACTJOB SBS(QEJBAES4) 2. If WebSphere is not running, follow these steps: a. Run the following command to restart WebSphere: STRSBS QEJBAES4/QEJBAES4 b. Run the following command: WRKACTJOB SBS(QEJBAES4) c. Select option 5 for the DEFAULT_SE job. 118 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

133 d. Select option 10 and verify that the Ready message is displayed. e. If Host Publisher was configured for a WebSphere administrative server other than the default, start that administrative server now. f. Select option 5 for your server s job. g. Select option 10 and verify that the Ready message is displayed. 3. Confirm that HPDoc, HPAdmin, and xmlgateway display as installed Enterprise Applications in the WebSphere Application Server topology for the server configuration file chosen during installation. Refer to Figure 5-15 on page 115. a. Using the tree view in the WebSphere Administrative Console, expand WebSphere Administrative Domain-> Nodes-> your node name. b. Select Enterprise Applications. HPDoc, HPAdmin, and xmlgateway should display in the details view. 4. If WebSphere is not configured properly for Host Publisher, run the Host Publisher deploy command: a. Run the QSH command. b. In the QSH command entry session, enter the following commands: cd /QIBM/ProdData/HostPublisher AEsOS400Deploy c. Check for error messages in the deploy log file/qibm/userdata/hostpublisher/log/aesdeploy.log as shown in Figure BROWSE: /QIBM/UserData/HostPublisher/log/AESdeploy.log RECORD: OF 249 BY COLUMN: 88 BY CONTROL: ************BEGINNING OF DATA************** on Wed May 01 16:57: Using -instance value default IBM WebSphere Application Server Release 4, AEs J2EE Application Installation Tool, Version 1.0 Copyright IBM Corp., Loading Server Configuration from /QIBM/UserData/WebASAEs4/default/config/server-cfg.xml Server Configuration Loaded Successfully Loading /QIBM/ProdData/HostPublisher/EARs/HPDoc.ear Getting Expansion Directory for EAR File Expanding EAR File to /QIBM/UserData/WebASAEs4/default/installedApps/HPDoc.ear Removed EAR From Server Installed EAR On Server Validating Application Bindings... Finished validating Application Bindings. Saving EAR File to directory Saved EAR File to directory Successfully F3=EXIT F10=DISPLAY HEX F12=CANCEL F15=SERVICES F16=REPEAT FIND F19=LEFT F20=RIGHT Figure 5-19 AESdeploy.log Chapter 5. Installation and administration of WebSphere Host Publisher Server 119

134 d. Press F3 to exit the QSH command entry session. 5. Stop and restart WebSphere Advanced Single Server Edition Installing Host Publisher Studio You install Host Publisher Studio on a Windows workstation using either of the following procedures: Typical installation Silent installation Typical installation To install Host Publisher Studio from a program CD, follow these steps: 1. When upgrading from a previous version of Host Publisher Studio, use the procedure described in 5.2.6, Uninstalling Host Publisher Studio on page 122, to uninstall the previous version. Uninstalling Host Publisher Studio does not remove applications created with the previous version. The applications can be migrated to run with Host Publisher Version 4.0. For detailed information about migration, refer to the IBM WebSphere Host Publisher Administration and Users Guide, GC Insert the Host Publisher Studio CD into the CD drive. 3. Wait for the first installation window. If the window does not open, use Windows Explorer or the Run function in Windows to run setup.exe from the CD root directory. 4. Proceed through the installation windows. 5. Click Finish when the final window opens. Silent installation Because silent installation of Host Publisher Studio occurs on a Windows workstation, it is different from silent installation of Host Publisher Server. You need to create a response file and use it to perform the installation of Host Publisher Studio in the location you specify. For more information, refer to IBM WebSphere Host Publisher Planning and Installation Guide, SC Verifying the Host Publisher Studio installation To verify the installation, follow these steps: 1. Start any of the applications in the Host Publisher Studio program group. Make sure it opens successfully. 2. Try to access a host system with the Host Access application. If you cannot access a host system, check the TCP/IP connectivity. 3. Make sure Database Access can access the target database. If not, check the availability of the JDBC drivers: a. Ensure that the drivers are installed on the machine running Host Publisher Studio. b. Define the paths to the JDBC drivers in the system environment classpath of the machine running Host Publisher Studio. 120 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

135 5.2.4 Saving and restoring Host Publisher Server The installation and configuration process is completed in two separate stages. Saving the information for restore is also performed by two separate procedures. The installation process performs the initial restoration of the Host Publisher licensed product files from the media to the server. The configuration process runs from the installed (or restored) Host Publisher directory and does all the remaining setup tasks. This includes setting up the UserData area of Host Publisher and configuring WebSphere Application Server for Host Publisher. An example set of the save/restore commands is shown here: Saving the licensed program and UserData/HostPublisher: For the licensed program part of Host Publisher on iseries, you can use the iseries command: SAVLICPGM LICPGM(5724B81) DEV(TAP01) For saving the UserData part of Host Publisher, you can use the command: SAV DEV('/qsys.lib/qgpl.lib/hpdata.file') OBJ(('/QIBM/UserData/HostPublisher ) In this example a save file hpdata in QGPL is used. Restoring the licensed programs and UserData/HostPublisher: You must use these three commands: RSTLICPGM LICPGM(5724B81) DEV(TAP01) MKDIR DIR( /QIBM/UserData/HostPublisher ) RST DEV('/qsys.lib/qgpl.lib/hpdata.file') OBJ(('/QIBM/UserData/HostPublisher )) ALWOBJDIF(*ALL) Note: Refer to WebSphere Application server documentation for more information on saving WebSphere applications. You can find it on the Web at: docs/doc.htm After restoring, you must re-run the configuration with the cfghpsvr command. You must also redeploy the Host Publisher customer applications in the WebSphere Application server Uninstalling Host Publisher Server To uninstall Host Publisher Server Version 4.0 on OS/400, follow these steps: 1. Sign on to the server using a profile that has *SECOFR authority. 2. If Host Publisher was configured for WebSphere Advanced Edition, complete these steps: a. Run the command: WRKACTJOB SBS(QEJBADV4) b. If the subsystem is not running, run the command: STRSBS QEJBADV4/QEJBADV4 c. Select option 5 for the QEJBADMIN job or the ADMIN job listed for your administrative instance. d. Select option 10 to view the job log, and verify that the Ready message is displayed. Chapter 5. Installation and administration of WebSphere Host Publisher Server 121

136 3. Run the command: DLTLICPGM LICPGM(5724B81) 4. If Host Publisher was configured for WebSphere Advanced Single Server Edition, restart WebSphere to remove any Host Publisher configuration information that may still be loaded in memory: a. Run the command: ENDSBS QEJBAES4 b. Run the command: WRKACTJOB SBS(QEJBAES4) c. When the QEJBAES4 subsystem ends, run the following command to restart WebSphere: STRSBS QEJBAES4/QEJBAES4 d. Verify whether WebSphere is running. e. Enter with command: DLTLICPGM LICPGM(5724B81) Notes: The IFS root directory (/QIBM/UserData/HostPublisher) is not removed because it may contain your user data. OS/400 authorization lists QSYS/QHPNPAUTL and QSYS/QHPNDAUTL are left on the system because they are in use, securing /QIBM/UserData/HostPublisher. Any files that were copied into the original directory tree root at /QIBM/ProdData/HostPublisher are deleted Uninstalling Host Publisher Studio To uninstall Host Publisher Studio, perform the following steps: 1. From the Windows Control Panel, click Add/Remove Programs. 2. Select IBM Host Publisher Studio. 3. Click Change/Remove. 5.3 Using Host Publisher Server Administration Host Publisher Server Administration is a part of Host Publisher Server. Host Publisher Server provides a runtime environment needed to run J2EE applications that access Host Publisher Integration Objects. Host Publisher Server Administration enables you to manage those middleware components. Host Publisher Server Administration is Web-based. You perform administration tasks using a Web browser, through a user interface provided by the Host Publisher Server Administration servlet, HPAdminServlet. Using Host Publisher Server Administration, an administrator with the proper authentication can perform the following types of tasks: Selecting a host and application server. Monitoring server status, including starting and stopping Host Publisher Server. Supplying passwords required by Host Publisher Server. 122 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

137 Managing licenses, which includes changing the allowed number of licenses on a server running one or more instances of Host Publisher Server. There is one exception that if you are running Host Publisher as part of iseries Access for Web, you must use the iseries licensed management product to change the number of licenses allowed instead of using Host Publisher Server Administration. Administer connections and connection pools. This includes displaying pool definitions, pool status, and the status of active connections for Host Publisher Server. Display user lists. Performing problem determination. This includes viewing trace and log files and setting various options for tracing and logging. Administering the XML Gateway. This incudes configuring XML Gateway to access hosts and host applications and creating a portal for accessing hosts and host applications. Note: This chapter discusses WebSphere Host Publisher Server Administration after the installation and configuration items. You may prefer to read Chapter 6, Using Host Publisher Studio to develop J2EE applications on page 141, first, and then return to this section. Chapter 5. Installation and administration of WebSphere Host Publisher Server 123

138 5.3.1 Starting the Host Publisher Server Administration To start Host Publisher Server Administration, enter the following URL in your browser: Here server is your server name. An example is shown in Figure Figure 5-20 Starting Host Publisher Server administration Using the functions in Host Publisher Server Administration This section guides you through the various selections on the Host Publisher Server Administration window. For more details on the Host Publisher Server Administration, see IBM WebSphere Host Publisher Administration and Users Guide, GC iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

139 Selecting the host and application server You can select the WebSphere Host Publisher Server to administer with the Select Host and Administration server option. The default is the default host and application server. However, you may select a new host by entering the host name or IP address. From your local host, you can administer a Host Publisher Server installed on another server. See Figure Figure 5-21 Selecting the host and application server Chapter 5. Installation and administration of WebSphere Host Publisher Server 125

140 Monitoring the server status The Server Status panel (Figure 5-22) displays information about the current status of the server, including the number of licenses installed on this server. You can start, stop, or restart the server from this panel. Figure 5-22 Server status Providing application passwords If users will run applications containing strongly encrypted user lists, you must provide the Host Publisher encryption key. You can learn more about this in Chapter 3 of the IBM WebSphere Host Publisher Administration and Users Guide, GC Monitoring connection pools Connection pools are collections of communication links to backend data sources, such as 5250 applications or databases. When an Integration Object is run on behalf of a client request, the Integration Object obtains an available connection from a pool, uses it for access to the data source, and then returns the connection to the pool. When connection pooling is enabled, the overhead of establishing a connection is absorbed in its first use. Each Integration Object that reuses this connection benefits from the prior establishment of the connection and can run faster. This panel displays information about defined connection pools. A connection pool is not listed until at least one connection is allocated from the pool. 126 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

141 Monitoring pool definitions A pool definition provides information about a collection of data source connections. This panel displays pool definition information for host and database connections. A pool definition is not listed until at least one connection is allocated from the defined pool. Monitoring connections Each connection shown on these panels represents a communication link to a backend data source, such as a 5250 application or a database. The panels enable you to see details about which users are connecting to which data sources, and which connection identifiers they are using. You can also shut down sessions. See Figure Figure 5-23 Monitoring connections Host Publisher Server Administration provides a separate panel for each of the following functions: All connections Host connections: Connections to 5250 applications running on an iseries server accessible via Telnet Database connections: Connections to databases through the Java Database Connection (JDBC) interface Chapter 5. Installation and administration of WebSphere Host Publisher Server 127

142 Monitoring user lists and user list members User lists identify the user IDs and other connection-specific parameters associated with a particular connection pool definition. For systems that allow only a single connection per user ID, the number of user IDs determines the number of connections that can be active in a single pool. For a user list, select the User Lists item as shown in Figure Figure 5-24 User Lists 128 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

143 The User List Members panel (Figure 5-25) shows the different users. Figure 5-25 User List Members Chapter 5. Installation and administration of WebSphere Host Publisher Server 129

144 Problem determination Host Publisher Server Administration enables you to set up and monitor logging and tracing to help you resolve problems. Options are provided that allow the user to: View version information View log Set log options View trace Set trace options The Problem Determination panel is illustrated in Figure From this page, you can navigate to subsequent pages to set up a complete problem determination and debugging environment. Figure 5-26 Problem Determination 130 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

145 The Version Information panel (Figure 5-27) displays the Host Publisher version, build level, and a list of Authorized Program Analysis Reports (APAR). Figure 5-27 Host Publisher Version information With the View Log panel, you can view the Host Publisher log file. You can find information on the messages in the log file in the WebSphere Host Publisher Message Reference, which you can find in the library in the WebSphere Host Publisher Studio. On the Set Log Options panel, you define the log level needed. You can use the View Trace option to view the information in the Host Publisher trace file. You can use Set Trace Options to trace one or more of the following types: Integration Objects on the server Host connections using the tracing facility in Host On-Demand Database activity using the JDBC tracing facility in WebSphere Chapter 5. Installation and administration of WebSphere Host Publisher Server 131

146 An example of the tracing facilities is the Display Terminal for testing and debugging, as shown in Figure Figure 5-28 Display Terminal function For more details on problem determination topics, refer to the IBM WebSphere Host Publisher Administration and Users Guide, GC iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

147 Administering XML Gateway sessions Use Host Publisher Server Administration to define, delete, and configure XML Gateway sessions. You access the host by using the XML Gateway servlet and xmlappdata bean, if you define and start an XML Gateway session. See Figure 5-29 for the XML Gateway Administration panel. Figure 5-29 XML Gateway Administration Chapter 5. Installation and administration of WebSphere Host Publisher Server 133

148 With the Create New Session button, you define a xmlgateway session as shown in Figure Figure 5-30 Creating an XML Gateway session 134 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

149 The Save button saves the XML Gateway session definition, the Start button starts the session. Figure 5-31 shows an example of the XML Gateway. Figure 5-31 XML Gateway page For more details on XML Gateway, see Chapter 6 in IBM WebSphere Host Publisher Administration and Users Guide, GC Languages With the Select Language option, you can change the language used for administering Host Publisher Server. You can also view the documentation in another language other than the default. Several languages are supported. See Table C-1 on page 277 for the list of supported languages. When you first start the Host Publisher Server Administration, it uses the default language of the server. You can change the language, choosing the language you want from the drill-down box. After you click the Save button, the new language is active for the Host Publisher Server Administration. It stays active until you invoke the change language to change the language again. Chapter 5. Installation and administration of WebSphere Host Publisher Server 135

150 See the Select Language panel in Figure Figure 5-32 Language setting Administering applications Application administration, formerly a function of Host Publisher Server Administration, is now done using WebSphere Application Server. For details, refer to Administration in the IBM WebSphere Information Center at: Migrating applications and XML Gateway sessions You must migrate applications and XML Gateway sessions created for previous versions of Host Publisher to work with Host Publisher V4.0. You can migrate your existing applications and sessions after installation by using a migration utility known as AppMigrator. You must invoke AppMigrator from the OS/400 command line after you install and configure Host Publisher since it is not invoked during installation Using the migration utility in Host Publisher Studio You can perform migration in Host Publisher Studio in one of two ways: Implicitly using Application Integrator, when you select Options-> Application Migration. This is the default selection. When you open an application in Application Integrator, it is selected by default to see whether migration is needed. If so, you are required to migrate the application. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

151 Figure 5-33 Host Publisher Studio Migration tool Explicitly, by issuing the StudioAppMigrator command from the command line, for example: c:\hostpub40\studio\ StudioAppMigrator Migration performs the following steps for each existing Host Publisher application: 1. Migrates JavaServer Pages (JSP) pages and tags from previous levels to the JSP 1.1 level. 2. Ensures that all JSP pages, HTML files, macro files, and session files generated by Host Publisher Studio are written with UTF-8 encoding. For example, in each JSP file, the value for the charset parameter is set to UTF Migrates Enterprise JavaBeans (EJB) access beans in the application to the EJB 1.1 level. 4. Migrates Host Publisher error pages to comply with the JSP 1.1 and Java Servlet 2.2 specifications. 5. Moves all application-specific files and subdirectories from the \Studio directory to the \Studio\Applications directory Migrating applications on the server You must migrate all Host Publisher Version 3.5 or earlier applications on the server. A server application migrating utility provided with Host Publisher Version 4.0 converts the applications to J2EE applications and updates them so they are compatible with WebSphere 4.0. After you migrate the applications, you must deploy them using WebSphere before they can be run. If you did not delete your existing applications from the server, you can invoke the Host Publisher Server application migrator utility using the AppMigrator command. Chapter 5. Installation and administration of WebSphere Host Publisher Server 137

152 Command-line invocation of the application migrator utility After you install Host Publisher Version 4.0, you can use the AppMigrator command to perform migration on Host Publisher Version 3.5 (and earlier) applications. The syntax of the command is: AppMigrator -i source_dir [-o hp40_dir -s file_list -l log_file -?] Note the following explanation: -i source_dir: A required parameter specifying the source Host Publisher (Version 3.5 or Version 2.2.1) directory containing the applications to be migrated. It is assumed that the applications are in the \Server\production\appmanifest subdirectory. -o output_dir: An optional parameter specifying the Host Publisher Version 4.0 installation directory under which the migrated application EAR files will be stored. The files will be stored in the \Server\migration\migratedApps subdirectory. -s file_list: An optional parameter specifying the names of one or more Host Publisher applications. When specifying multiple files, delimit the files using a semicolon (;)and enclose the list in double quotes ( ). Specify hpubportaldata.xml to migrate XML Gateway sessions. If you do not specify this parameter, all Host Publisher applications in the source directory (except XML Gateway sessions) are migrated. -l log_file: An optional parameter specifying the fully-qualified name of the log file. The log file contains a detailed record of the migration steps, including (at the end of the file) a summary of all errors and the applications for which they occurred. -?: Displays help information. See Figure QSH Command Entry $ > cd qibm/userdata/hostpublisher/server/migration $ ===> appmigrator -i source_dir -o out_dir -s file_list -l log_file -? F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry Figure 5-34 Appmigrator 138 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

153 What the application migrator utility does The Host Publisher Server application migrator utility performs the following tasks for a Host Publisher application that has an application manifest file in the install_dir\server\production\appmanifest directory: Note: The manifest file has a list of application.jarfile, document files, pool-specific, and connection-specific information including screen definitions and eventually user lists. 1. Converts the application to a J2EE application, and packages it in an EAR file. 2. Migrates JSP pages in the application to the JSP 1.1 level. It replaces JSP tags and their attributes with either JSP 1.1 tags and attributes or with Java code. 3. Migrates XML Legacy Gateway sessions to XML Gateway sessions and saves them in the file install_dir\server\hpubportaldata.xml. 4. Saves the migrated application EAR file in the install_dir\server\migration\migratedapps directory. 5. Produces a log file in the install_dir\server\migration\migratedapps directory. For a complete discussion and recommendations on migration, refer to Chapter 3 in IBM WebSphere Host Publisher Administration and Users Guide, GC Chapter 5. Installation and administration of WebSphere Host Publisher Server 139

154 140 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

155 6 Chapter 6. Using Host Publisher Studio to develop J2EE applications You want to extend applications to the Web. But where do you start? This chapter helps you understand the concepts and the steps involved in building Host Publisher applications. Use Host Publisher Studio, running on a workstation, to build J2EE applications that make specific data from the host or database available to end users. Host Publisher Studio is made up of three main components: Host Access Database Access Application Integrator This chapter also takes you through the following types of application development scenarios: Creating composite applications Enterprise JavaBeans support Web Services support Copyright IBM Corp All rights reserved. 141

156 6.1 Overview of Host Publisher applications Applications built in Host Publisher Studio contain Integration Objects. Integration Objects are JavaBeans that encapsulate interactions with a data source, such as a database or a 5250 application. Then they return specific data from that source for use as output to Web pages, Enterprise JavaBean (EJB) applications, J2EE application clients, or Java thin application clients. Integration Objects connect to the data source, navigate to the desired data, extract the data, and store the data in properties of the Integration Object, which can then be accessed by JavaServer Pages (JSPs). See Figure 6-1. Figure 6-1 IBM WebSphere Host Publisher A J2EE application is packaged as an Enterprise Archive (EAR) file. The EAR file includes everything necessary to run the application on Host Publisher Server. The elements that make up the EAR file cannot be shared with other applications on the server. However, Host Publisher Studio allows some elements created for one application to be reused in the creation of other applications. When the application is built, a copy of the reused element is included in the application s EAR file. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

157 Figure 6-2 J2EE packaging In a Host Publisher application, the elements that make up the EAR file include Integration Objects, JSP pages, and support files. The following steps show the sequence for creating and building a J2EE application in Host Publisher Studio: 1. Create an Integration Object in Host Publisher Studio to access a data source and return the desired data. See 6.2, Integration Objects on page Build Web pages that use one or more Integration Objects to form a Web application. See 6.5, Application Integrator on page Transfer the Web application to one or more Host Publisher Servers. See 6.5.3, Transferring applications to a Host Publisher Server on page Deploy (install) the application using the WebSphere Administrative Console. For more information, refer to the WebSphere documentation at: You should also see 6.5.4, Deploying the application on WebSphere Application Server on page 199. Host Publisher Studio is also used to create Integration Objects that run remotely. The two ways to do this are: Create J2EE EJB-based applications. The Web module containing the EJB access beans can be deployed separately from the EJB module, which runs Integration Objects located on the Host Publisher system. See 6.7, Enterprise JavaBeans support on page 207, for details. Create Integration Objects that take advantage of Web Services function provided by WebSphere Studio tools at the level or above, such as WebSphere Studio Application Developer. With the Web Services function, your Integration Objects can Chapter 6. Using Host Publisher Studio to develop J2EE applications 143

158 access data from a Java program (applet or application) running on a remote machine. Refer to 6.8, Web Services overview on page 212, for details. 6.2 Integration Objects Every Integration Object, whether it is created using the Host Access component or the Database Access component of Host Publisher Studio, has two characteristics: It interacts with a data source. It is associated with a connection pool. The following sections cover these characteristics that are common to all Integration Objects. You can find more detailed information about creating Integration Objects using either the Host Access component or the Database Access component in: Section 6.3, Creating a Host Access Integration Object on page 149, to create Integration Objects that access data from a 5250, 3270, or VT application Section 6.4, Creating a Database Access Integration Object on page 173, to create Integration Objects that encapsulate a database statement Interacting with a data source Host Access Integration Objects interact with the host application by means of macros. Macros connect to the host, interact with applications on the host, and disconnect from the host. See 6.3.1, Building an Integration Object using macros on page 149, for details. Database Access Integration Objects contain SQL statements to access data in the database. See Retrieving information from a database on page 173 for details Defining connection pools Every Integration Object is associated with a connection pool. A connection pool is a collection of communication links to backend data sources, such as 5250 applications or databases. When an Integration Object is run on behalf of a client request and pooling is enabled, the Integration Object obtains an available connection from a pool, uses it for access to the data source, and then returns the connection to the pool. For each Integration Object created, a new connection pool or an existing connection pool may be shared. A Host Access Integration Object may be created in a default connection pool. Figure 6-3 shows the Connection Pools and Pool Configuration panels. 144 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

159 Figure 6-3 Pool configuration After you define a connection pool, you may associate it with many different Integration Objects. A copy of the connection pool becomes part of each application that includes one of these Integration Objects, after the application is assembled in Application Integrator Information specified in a connection pool A connection pool specifies several kinds of information, including: Data that allows your Host Publisher application to connect to a host. For Host Access Integration Objects, this data includes the host name. For Database Access Integration Objects, it includes the URL of the database. Whether connection pooling is enabled. Connection pooling is a method of keeping a connection to a host open for many data transactions, instead of opening and closing a connection with each new request. Connection pooling is designed to reduce the response time between a request from a client browser and the display of the requested information on a Web page. See 6.2.4, Enabling and disabling connection pooling on page 146, for more information. Optionally a user list. User lists contain information about accounts (user IDs) that a Host Publisher application can use to access a host or database. Each entry in a user list includes a user ID, password, and description of the account. Connect and disconnect macros (in Host Access only). Chapter 6. Using Host Publisher Studio to develop J2EE applications 145

160 See Step 1: Creating connection pools for Host Access on page 152 and Step 2: Configuring the database connection and connection pools on page 176 for more component-specific information about connection pools and connection pooling Enabling and disabling connection pooling When connections are pooled, the overhead of establishing a connection is added to the initial response. Each Integration Object that reuses this connection benefits from the prior establishment of the connection and can run faster. The following rules apply each time a database Integration Object requests a connection: If connection pooling is enabled and a connection is available, the connection has already been made and is ready to use. If connection pooling is enabled, but a connection is not available, the connection is created. If connection pooling is disabled, a connection is always created. When the Integration Object has completed, the connection is returned to the pool: If connection pooling is enabled, the connection remains available and can be used for the next requested connection. If connection pooling is disabled, the connection is terminated. For Host Access Integration Objects, when a connection is made to the host, the associated connect macro runs. When the host connection is ended, the disconnect macro runs. Enabling connection pooling means that the connect macro is run only when necessary to make a connection available. After a connection is available, it can be used again and again without the overhead of running the connect and disconnect macros for each connection request User lists In Database Access, a user list is created by default with the user ID and password you enter to connect to the database. Because multiple users can access the database at the same time with the same user ID and password, user lists for Database Access always contain only one entry. In Host Access, a user list is not created automatically. You must define it explicitly, for example, by clicking User List in the Host Configuration window. If your application will access a host that allows multiple users to logon with the same user ID, the user list may have only one entry. However, for a single-logon host, which allows only one connection per user ID, the number of users who can access the host at the same time using your application is limited to the number of entries in the user list. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

161 Figure 6-4 User List Configuration Customizing a user list created with an earlier version of Host Publisher A user list defined in Host Access in Host Publisher Version 4.0 contains only one entry. A user list defined in a previous version of Host Publisher can contain more than one entry, but you cannot use Host Access to add additional entries. You must use Application Integrator to add entries. To modify or delete entries in a user list that was defined in an earlier version of Host Publisher, follow these steps: 1. Click the Connection Pools tab in the left pane. 2. Select a connection pool. 3. Click the User List Configuration tab in the right pane. When you create an application using Application Integrator, copies of user lists become application specific. In Application Integrator, the Modify User List button in the Select Connection Pools window (Figure 6-5) enables you to customize the user list associated with an application. Chapter 6. Using Host Publisher Studio to develop J2EE applications 147

162 Figure 6-5 Modify User List button in the Select Connection Pools window 148 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

163 You can add, edit, or remove users in the Modify User List window (Figure 6-6). Figure 6-6 Add, edit, or remove a user For more details, see: IBM WebSphere Host Publisher Administration and Users Guide, GC IBM WebSphere Host Publisher Programmer s Guide and Reference in the WebSphere Host Publisher library A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG Creating a Host Access Integration Object To create Integration Objects that collect data from applications on the terminal-oriented host, use the Host Access application. To create the Integration Objects, navigate to the information you want using a 5250 connection. Host Publisher records the keystrokes you use and lets you define the host application windows that contain information. This section provides a general description of the main function of Host Access using macros to build Integration Objects Building an Integration Object using macros The Host Access application is used to build Integration Objects that access data from a 5250 application. To do this, Host Access records macros that contain information about the way you connect to the host, navigate to the information you want to make available to your end users, and disconnect from the host. These macros become part of the Integration Object you create. Chapter 6. Using Host Publisher Studio to develop J2EE applications 149

164 Host Publisher uses a macro facility of IBM Host On-Demand to provide an interface where you can interact with a host and record the actions you make. The actions are recorded as a macro. A macro is an XML script that defines a set of screens. Each screen includes a description of the screen, the actions to perform for that screen, and the screen or screens that can display after the actions are performed. See Example 6-1. Example 6-1 Host Publisher macro example <HAScript name="sxxboat" description="" timeout="60000" pausetime="200" promptall="false" author="" creationdate="" supressclearevents="false" encoding="utf8" > <screen name="main Menu.2" entryscreen="true" exitscreen="false" transient="false"> <description uselogic="1 and 2" > <oia status="notinhibited" optional="false" invertmatch="false" /> <string value="os/400 Main Menu" row="1" col="33" casesense="true" optional="false" invertmatch="false" /> </description> <actions> <input value="boats[enter]" row="0" col="0" movecursor="true" xlatehostkeys="true" encrypted="false" /> </actions> <nextscreens timeout="0" > <nextscreen name="iseries WSG Boat Demo.1" /> </nextscreens> </screen> </screen>... </HAScript> Note: Macros are not used by Integration Objects created using the Database Access application. Macros work by following a sequence of host screens that are defined. By navigations through the required application screens using a terminal emulator, the following elements are defined: The screens The actions to take on each screen (that is, keystrokes) Which screens can appear next after the action has completed for a given screen In Host Access, there are three types of macros as shown in Figure 6-7: Connect: This macro includes the information Host Publisher needs to connect to the host. The connect macro should contain the steps necessary for logging on to a system from as many initial states as possible. It should take into account different paths that might occur because the previous connection failed or was left in an unknown state. Host Publisher Server uses the connect macro to attempt to connect to a system and to recover from a previously-failed connection. Data: This macro includes information about navigating to, extracting, and organizing the data you want to publish. 150 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

165 Disconnect: This macro includes information about how and when to disconnect from the host. Typically, this means tearing down the network connection. Disconnect macros prepare the host connection to cleanly disconnect. Figure 6-7 Macros In Host Access, the connect and disconnect macros are part of the connection pool associated with the Integration Object. Only the data macro is part of the Integration Object itself. Loops may also be defined within the macro and alternate paths (for example, more than one next screen for a given screen) to follow. Host Access includes a wizard that guides you through recording macros, but you can use the Macro menu and the toolbar (Figure 6-8) to fine-tune them. Figure 6-8 Host Access Studio toolbar When you run your macro on Host Publisher Server by invoking your Integration Object, your macro looks for the screens you defined to appear on the host terminal and execute the actions you defined for each screen. Integration Object chaining may improve your application s response time or decrease the amount of macro recording you must do. See IBM WebSphere Host Publisher Administration and Users Guide, GC , or A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG , for more information. Chapter 6. Using Host Publisher Studio to develop J2EE applications 151

166 6.3.2 Sample scenario This section shows a sample scenario where an Integration Object is created from an RPG program, called Boat. Boat is a 5250 window-based application, where it can be searched for different kind of boats. Further selection criteria may be changed based on length and build year. See Figure 6-9. AS/400 WSG Boat Demo 5/01/02 9:40:17 Enter your search parameters Type A P=Powered, S=Sailing, T=Tug, C=Commercial, A=All Length (feet) feet to start from Year built year to start from F3=End Figure 6-9 Boat application In Figure 6-10, we select all types of boats, longer then 50 feet and built after AS/400 WSG Boat Demo 5/01/02 9:42:41 Your search parameters Type A P=Powered, S=Sailing, T=Tug, C=Commercial, A=All Length (feet) 50 feet to start from Year built 1990 year to start from 6 boats match your search 1=Details Type and Model Feet Year US$ P Monterey Marine Custom ,975,000 P Katemeran ,000,000 S Merlin's Magic ,000 S Spandau ,000,000 S MOLSLINIEN ,000,000 S Spandau ,000,000 F3=End F12=New search Bottom Figure 6-10 Search result This query will be available in the Web browser. Step 1: Creating connection pools for Host Access You need to define and configure a host Telnet connection as part of the host access Integration Object you are creating. You can either select the single connection option, or alternatively, you can configure a connection pool to be used by this and other Integration Objects. 152 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

167 This section explains how to configure a single connection. For details on how to use and configure connection pools, see IBM WebSphere Host Publisher Administration and Users Guide, GC , or A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG Connection Pool information Use the Connection Pooling Information panel (Figure 6-11) to choose whether to define a single connection or a new pool of connections: Configure a default connection pool Select this option if you want this Integration Object to use a single (non-pooled) connection. A new connection is created for each request. You can use this option as a quick way to develop your application. When you are ready to support pooled connections, you can modify the connection information to include pooling and have additional user IDs. Create a new pool Select this option if you want this Integration Object to use one of several user IDs. Using this option means that if more than one person requests information, the requests can be handled simultaneously. Ensure that each of the IDs you specify in a pool behaves the same way as the ID you use to record the macro. Otherwise, your macro might not run correctly when user IDs from the pool are used. You can also use a pool to reduce the response time between when a client with a browser requests information and when the information is displayed on the page, by keeping one or several connections initialized. Use the Connection Pool Configuration panel to specify the number of connections you want. Pools are configured and managed by clicking the Connection Pools tab next to the Macro tab in the left panel of the application window. Share an existing pool Select this option and specify the pool to use if you want to use a pool that you already created. If you select Share an existing pool, Host Access uses the Host Server information associated with that pool. Chapter 6. Using Host Publisher Studio to develop J2EE applications 153

168 Figure 6-11 TN5250 connection configuration Connection information You can choose to create a new connection configuration or to use a configuration you already created. If you choose Create a new connection configuration, you need to provide the following host server information (see Figure 6-11): Server name Type the name or IP address of the host machine where the data that you want to publish resides. Terminal type Select the type of terminal emulator connection to use: 3270, 5250, or VT. Typically, TN3270 and TN3270E emulators provide connections to an IBM System 390 (S/390) or System 370 (S/370) host. TN5250 and TN5250E emulators typically provide connections to iseries hosts. A VT connection provides connections to a host using a Telnet connection. The default is TN3270. Port number Type the number of the port assigned to this connection, between 0 and The default port number is 23. LU or pool name This parameter is optional. Enter the name of the specific logical unit (LU) or LU pool on the host to which you want to connect, if any. If you are not sure which LU to connect to, leave this field blank. 154 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

169 Code page Select the ASCII code page for the set of display characters this connection will use. This setting must match that used on the host you are connecting to. The default value is 037 (United States). Screen size This indicates the number of horizontal and vertical characters that can be displayed. The default value is 24x80. Express Logon Enabled Select this box to enable TN3270 Connections Express Logon. A Digital Certificate Authentication Server (DCAS) component is needed, provided by z/os, to run Express Logon. Express Logon is not enabled in an iseries environment. Click Next to continue to the Connect Macro panel and begin recording. Step 2: Connecting the macro After you configure a connection and connect to it, the wizard appears at the upper right-hand corner of the panel. The host connection you configured appears in the terminal at the lower right. The wizard explains what actions are necessary to correctly create your macro. We recommend that first-time users follow the wizard to create an Integration Object. It is also possible to create your Integration Object through the menus and toolbars. Figure 6-12 shows the flow of steps in the Connect macro wizard. At this point, you already completed the Welcome, Integration Object, and Host Configuration windows. Chapter 6. Using Host Publisher Studio to develop J2EE applications 155

170 Welcome Click Next Integration Object Choose an option and click Next Host Configuration Supply parameters and click Next Begin Recording Unrecognized Screen No Click Next Yes Define Screen Click Next Supply keystrokes to move to the next window. Connect Your Session Text Area Recognition If you reached the window where you want the connect macro to end and the data macro to begin, click Next. Gather Data This is the beginning of the data macro. Figure 6-12 Flowchart for the Connect macro wizard 156 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

171 Connecting to the host The Begin Recording panel in Figure 6-13 is the first wizard panel that displays after a host connection is established. Click Next to define your host screen. Figure 6-13 Host Access Studio: Begin Recording panel New Screen Definition To define the first screen, specify the information shown in Figure 6-14: Screen name prefix Enter the name you want to use for this screen, or let Host Publisher choose one for you. This is a global screen Choose this option if the selected screen is an intermittently displayed screen that appears at different times but always needs the same action applied. For example, you may have a screen that appears at different times in the macro, and simply needs to be cleared. Rather than identifying this screen as a valid next screen for all screens which it might follow, you can mark it as a global screen. When a global screen is encountered, Host Access performs the actions you define even though this screen is not on the next screen list of the previous screen. The macro continues recognition of the next screen, essentially ignoring the global screen. Chapter 6. Using Host Publisher Studio to develop J2EE applications 157

172 Figure 6-14 Host Access Studio: New Screen Definition Click Next to continue. Add Recognition Criterion to Screen Definition After you define the screen, you have to choose the criteria to recognize the screen. This criteria determines how the Integration Object will know when the host connection reaches the correct screen. Select one of the following options: Text area: Indicates that the screen is recognized by text on the screen. Select this default option (Figure 6-15) if there is specific text that identifies this screen. Number of fields: Indicates that the screen is recognized by number of fields on the screen. Cursor Position: Indicates that the screen is recognized by cursor position on the screen. Advanced: Indicates that the screen is recognized by other things such as color at cursor position. 158 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

173 Figure 6-15 Host Access Studio: Selecting text area When you select the Text area option and click Next, you are asked for more information about the text in the Text Area Recognition panel (Figure 6-16). Use this panel to define the text area that you want your Integration Object to recognize. This is the recommended way to recognize screens. To define a text area, you can use your mouse to draw a box around the text to look for on the connection screen. Or you can type the characters and keywords to recognize in the Text field. Chapter 6. Using Host Publisher Studio to develop J2EE applications 159

174 Figure 6-16 Text Area Recognition Next, you need to specify where you want Host Publisher to look for the text in the Text Position Options: Text anywhere on the screen This text can appear anywhere, not just in this location. At the specified location Host Publisher should not recognize this screen unless the text you highlighted appears in the row and column specified. When you select this choice, Host Publisher lists the current row (number of lines from the top of the screen) and column (number of spaces from the left of the screen), but you can change the values. If you want, you can specify more details of your recognition in the Options field: Match this criterion or Do not match this criterion: Select whether Host Publisher should match the criteria you chose before. Case sensitive: Specify whether it must consider case sensitivity. Optional: Specify whether these selections are optional. Click Next to continue. Screen Definition After you choose your criteria for the screen recognition, you are asked to confirm your screen definition (see Figure 6-17). Click Add if you want to add more criteria to the screen recognition. You move back to the Add Recognition Criterion to Screen Definition panel. 160 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

175 Otherwise, click Next to continue. You can right-click an item in the tree and select Modify to modify the Screen Definition later. Figure 6-17 Screen Definition Connect Your Session After you define the screen, record the keystrokes necessary to move past that screen. The Connect Your Session wizard panel (Figure 6-18) opens and waits for you to navigate to a new screen while Host Publisher records your keystrokes. Chapter 6. Using Host Publisher Studio to develop J2EE applications 161

176 Figure 6-18 Connect Your Session panel After you type the keystrokes to navigate to the next host screen, you see the Unrecognized Screen panel (Figure 6-19). Note: The only time you proceed directly to the Define Screen panel is for the initial host screen. We require you to define the initial screen. Each time you reach a screen in the host connection that the wizard does not recognize, you need to define the screen or respond that you do not want to define the screen. The wizard will wait for you to click Yes or No before you are allowed to enter more information in the host connection screen. Use this panel to identify screens that you want your Integration Object to recognize. Each step in a macro has at least one screen defined as the possible next screen. Host Publisher waits for the expected screen to open before it moves to the next step of the macro. You can use the Define Screen button on the toolbar to bring up this panel. If you click Yes, you reach the Define Screen panel (Figure 6-14 on page 158). You then define the screen and continue with the macro. If you click No, you immediately continue with the macro, and the screen you chose not to define is not included in the macro. 162 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

177 Continue defining screens and recording keystrokes until you reach the first screen that begins your transaction. This screen is the last screen in the Connect macro and the first screen in the Data Macro. If you choose to use connection pooling, this screen is the starting point for all connections after they are initialized. It is important to carefully choose this screen based on how your transaction will be performed. Figure 6-19 Unrecognized Screen panel Step 3: Defining data with Data Macro Data Macro is the most important part of this Integration Object. This is where you define which data you want to extract and how you want to extract it. You navigate through the application screens until you reach the screen where you are asked for the search data. Use this series of panels to define the way the Integration Object will work, by using the host connection to go through the host application you want to publish and identifying key fields. Through these steps, you create a loop that asks for input data if necessary, retrieves that data, extracts it, and then returns to the starting point to allow the process to run again. The wizard guides you through the navigation and definition of screens first and then assists in extracting and formatting the data you want to display. Refer to the flowchart in Figure 6-20 for an overview of the process. Chapter 6. Using Host Publisher Studio to develop J2EE applications 163

178 If you are not at the screen where you want to extract data, navigate to that screen. Gather Data? No Yes Click Next when you are at the screen where you want to extract data. Unrecognized Screen No Yes Define Screen Click Next Supply keystrokes to move to next screen until you reach the screen where you will extract data. Record Keystrokes Text Area Recognition Select Data Select the data to be extracted and click Next. Data Format Choose table or plain text and click Next. Define Extraction Finish Data Extraction? No Yes Navigate back to the first Data Macro screen and click Next. Finish Data Macro Figure 6-20 Data Macro flowchart Creating input variables To create the input variables, follow these steps: 1. Navigate to the search screen and type the keyword boat. 2. Insert an input variable. There are two ways to do this. With the cursor on the field where you want to input data, click: Macro-> Insert-> Input Variable The Input Variable button on the toolbar 3. The Insert Input Variable window (Figure 6-21) opens and asks you for the name of the variable and the text you want to use for the purpose of recording the macro. You use the variable name later when you customize your Web application in the Studio. The text you enter for the input variable is placed in the field, and you continue navigating through the application. In this example, we name the variable type and enter A in the dialog box to search for all the boats. The text A is placed into the host field. Then we click Enter to initiate the search and bring up the host screen displaying the results of our search. 164 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

179 Figure 6-21 Inserting an input variable 4. Click OK. Creating a loop The next host screen displays the results of our search. The list of boats represents the data you want to extract. However, the search returned 24 boats, and the results span many host screens. To extract all of the data, you must create a loop that navigates through and extracts data from each host screen that has the search results. The panels that describe the process of creating the loop are similar to the normal Data Macro panels. Before you create the loop, you must decide which host screens you want to loop through, which keystrokes to include in the loop, and which host screen will define the end of the loop. In our example, you start the loop with the first screen of search results. This screen lists the first 10 boats that are found and includes a line that states there are MORE... results as shown in Figure Each consecutive screen lists the next 10 results, and so on, until all of the results are displayed. To move from one screen to the next, you use the PageDown key. The host screen that signals the end of the loop is the last results screen that displays the text Bottom. To create a loop, you may either select Macro-> Insert-> Start Loop, or click the Start Loop button on the toolbar as shown in Figure A new wizard panel appears, indicating that you are about to begin defining the loop and that you should follow these steps: 1. Describe the data you want to collect. 2. Describe the action that will be repeated. 3. Describe how the loop will end. Chapter 6. Using Host Publisher Studio to develop J2EE applications 165

180 Figure 6-22 Starting a loop: Start Loop button in the toolbar Click Next to start recording the loop. You start the loop on the screen that displays the first page of search results. The panel asks you to define the data you want to extract by drawing a box around the text (see Figure 6-23). Our box includes all 10 lines of the Type, Model, Length, Year and Price columns of data. When creating a box around an area of data to extract in a loop, keep in mind that the same area on each consecutive screen is marked for extraction. It may take some planning to determine which area to define that works for all screens in the loop. 166 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

181 Figure 6-23 Selecting the data in the loop You then extract the data in table format and name the table. Adjust the three columns as explained here: 1. Select column1 and click Divide. 2. Adjust the divided columns with the Column width Left or Right arrows as shown in Figure Figure 6-24 Adjusting the columns 3. Repeat steps 1 and 2 for column2, to have each data in its own column. 4. Rename all the headers by clicking in the column title and changing the Column name. Figure 6-25 shows the result. It is useful to note that when recording a loop, you actually perform the same steps that will play over and over again until the end of the loop. Chapter 6. Using Host Publisher Studio to develop J2EE applications 167

182 Figure 6-25 Defining the table columns Indicate that you are finished extracting the data by selecting the Finished extracting data option. Click Next to open a panel that tells you to record the actions that should be repeated during the loop. In our scenario, we record PageDown to obtain the next screen of search results. Now, you are ready to stop the loop. Let s review the steps up to this point. You navigated to the search results screen, extracted and defined the data, and pressed the PageDown key to continue to the next screen. This sequence will be repeated until all the screens of data are extracted. The advantage to creating a loop to do this, instead of manually stepping through each results screen and extracting the data, is that you do not need to know how many screens of data you have since this is often a variable number. To stop the loop, the wizard shows a panel that inquires how you want to define the screen that will indicate that the loop should stop. There are two ways that you can define the end of the loop: Define a unique screen where the loop will terminate Define a fixed number of interactions after which the loop will terminate In this scenario, a unique last screen is defined that indicates when the loop should terminate. To do that, click the Define a unique screen where the loop will stop option and then click Next (see Figure 6-26). 168 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

183 Figure 6-26 Selecting the condition to finish the loop Navigate to the screen that is displayed at the end of the loop. Choose whether to extract data of this last screen (see Figure 6-27). The response depends on the application. In this case, if you do not select this box, you lose the data on the last screen of the list of results. Click Next when you reach the last screen. Chapter 6. Using Host Publisher Studio to develop J2EE applications 169

184 Figure 6-27 Navigating to the last screen of the loop Once you reach the correct screen, define what condition the loop should look for to terminate. This time, define it with the specific text Bottom that indicates the loop should stop (see Figure 6-27). Drawing a box around this text when defining the screen determines when the loop will stop. By defining this area, the loop terminates when a condition is reached that only occurs when there are no more books to display in the list. After you define the last loop screen, the Data Macro continues normally. For our example, we chose to record PF12 to reach the initial screen. After you finish recording, move to the Disconnect Macro. Disconnecting the macro To disconnect your host connection, use this panel to record the way you normally disconnect the host session (see Figure 6-28). Enter the signoff command or select option 90 from the OS/400 Main Menu, and press Enter. Click Next to continue to the Save Integration Object panel. 170 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

185 Figure 6-28 Disconnect macro Save Integration Object Now that you have finished creating your Integration Object, you must save it. Click Next to proceed to the Save As dialog box, where you name the Integration Object. Click OK when you are finished. You see a status bar that displays the progress for the creation of your Integration Object (see Figure 6-29). Click OK when the creation is complete. Figure 6-29 Generating the Integration Object Created files After you successfully save the host access Integration Object, Host Publisher generates files to the common subdirectory and to the Integration Objects subdirectory as follows: Chapter 6. Using Host Publisher Studio to develop J2EE applications 171

186 The information related to the connection and session that you provided along with the default configuration values are saved in the directory c:\hostpub\studio\sessiondefs and the following files are created (boat is the name we used for the connection, user list, and pool name): boat.connspec: This is the connection specifications XML file. It contains the configuration values you provided for this connection, for example, the TN5250 host name or IP address. boat.poolspec: This is the pool specifications XML file. It contains the configuration values you provided for this connection pool, for example, the option to enable pooling and its associated timeout values. boat.userpool: This is the user list specifications XML file. It contains the configuration values you provided for this user list, for example, user IDs and passwords. boatcheckin.screen: This is the check-in screen XML file. It contains the definition of the final check-in screen after signon, which in our case, is the OS/400 Main Menu. boatlogon.macro: This is the logon macro XML file. It contains the steps you created to log on the connection. boatlogoff.macro: This is the logoff macro XML file. It contains the steps you created to log off the connection. boatlogspec.logonspec: This XML file contains the names of your logon macro, logoff macro, and check-in screen files. Note: If you edit any of these XML files manually, you must replace some special XML characters in quoted attributes with XML escape sequences (do not forget the semi-colon (;)) as follows: Less-than with < Double-quote with " Ampersand with & The information related to the host access Integration Object and the data macro that you provided are saved in the directory c:\hostpub\studio\integrationobjects\ and the following files are created (Boat is the name we used for the Integration Object): boat.hpi: This XML file contains information about the Integration Object such as the data macro name, pool name, and the output variable information associated with the Integration Object. boat.hpt: This XML file contains definitions for the variables and other related information required by the Integration Object process. boat.jar: This contains the compiled and compressed Integration Object bytecodes. boat.java: This contains the generated Integration Object Java source code. boat.macro: This contains the generated macro. boat.mf: This contains the created manifest with information about the contents of the Java Archive (JAR) file. boatbeaninfo.java: This contains the generated BeanInfo class source code for this Integration Object. The BeanInfo class allows other programs to query about how this Integration Object works. For example, the Host Publisher Studio uses this class to determine the Integration Object properties (input and output variables). For more details and more information on editing guidelines, see IBM WebSphere Host Publisher Programmer s Guide and Reference. 172 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

187 6.4 Creating a Database Access Integration Object Use the Database Access application to create Integration Objects that encapsulate a database statement. To create the Integration Objects, you specify your structured query language (SQL) statement. If you are querying a database, you specify the data you want to retrieve from the database table Integration Objects overview Integration Objects are JavaBeans. They encapsulate interactions with data sources like database applications and return desired data as JavaBean properties. These objects can also be embedded within JavaServer Pages, which allow you to use a Web browser to interact with the data. JavaBeans can be invoked from a Java applet, from a Java servlet, from a Java application, or from a JavaServer Page. For example, Figure 6-30 illustrates how a Web browser requests a JSP that invokes a database Integration Object to access the DB2 UDB for iseries database. Figure 6-30 JavaBeans: Database Integration Objects Notice that, in this scenario, the JSP has to be compiled into a Java servlet the first time it is used. In turn, the created Java servlet must be also compiled into Java bytecodes for execution. This process creates a small overhead the first time the JSP is used, but gives you the benefit of not having to write a Java servlet to instantiate the database Integration Object. The Database Access application (part of the Host Publisher Studio) can easily create the database Integration Object, and the Host Publisher Studio Application Integrator can create the JSP execution page. Retrieving information from a database The Database Access wizard helps you navigate to the tables that contain the data you want, specify conditions to identify the data, and sort the data you want to publish. You can specify the SQL statement type and select the tables in the database to access. You can determine which columns of the tables to include, applying conditions to the data in the columns. You can also sort the order in which the data is displayed. Chapter 6. Using Host Publisher Studio to develop J2EE applications 173

188 The SQL statement types are: Select Select Unique Insert Update Delete After Database Access guides you through creating an Integration Object, use the Application Integrator application to create a Web page where the data will appear. Note: When a database query (such as select) is made and the field is empty, the database returns a value of null. As a result, the Host Publisher database Integration Object returns a value of null to the invoker. By default, JSP pages generated in Application Integrator display null values as null not as a string of blanks. If you prefer that null values appear as blanks, you need to modify the JSP pages so that the null values are displayed as blanks Sample scenario The Host Publisher Studio Database Access allows you to connect to a database to create and generate a database Integration Object. It is also used to define the database connection and connection pools if required by your application. This section shows you a sample scenario in which we connect to the DB2 UDB for iseries database provided by iseries. We choose in the IBM WebSphere Host Publisher Studio the IBM Toolbox for Java JDBC Driver, from the pull-down menu, to access to the DB2 UDB for iseries database. This driver, com.ibm.as400.access.as400jdbcdriver, has to be known at the classpath from your PC. If you don t have it already on your PC, copy it from your iseries. You can find it in the directory /QIBM/ProdData/OS400/jt400/lib/. The JAR file is called jt400native.jar. Step 1: Connecting to the database Before you attempt to create the database Integration Object, you are required to connect to the database. After you start Studio Database Access, you enter the required information to establish this connection, as shown in Figure Database URL Specify the JDBC URL for the database. The format of the database URL depends on the JDBC driver you use to connect to the database. If you select one of the JDBC drivers from the drop-down list in the Driver field, the required format for the driver is displayed in the Database URL field. For example, the AS/400 (IBM) Toolbox for Java JDBC driver requires jdbc:as400://host, where host is the fully-qualified network name of the database host. The connection is specified with a URL format, for example: jdbc:subprotocol:subname Note the following explanation: subprotocol is the driver name (for example, as400, db2, oracle, odbc, and so forth). subname is the system name, default schema, and properties (for example jdbc:as400://systemname/defaultschema;listofproperties) 174 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

189 The format of the database URL depends on the JDBC driver you use to connect to the database. If you select Other from the drop-down list in the Driver field, consult your JDBC driver documentation for the required format of the database URL. Note: For more information about the JDBC or JDBC Properties, see the iseries Information Center Web site at: When you reach the site, select your release and search for JDBC or IBM Toolbox for Java JDBC properties. Figure 6-31 Database Access: Connecting to the database User ID Type the user ID, if one is required, for the specified database to which you intend to connect. Password Type the password, if one is required, for the specified database. Driver Select the JDBC driver used to connect to the specified database from the drop-down list, or select Other. If you select Other, enter the class name of your driver in the Other driver field. Other driver When you select a JDBC driver from the Driver drop-down list, this field displays the class name associated with the driver. If you select Other from the drop-down list in the Driver field, enter the class name of your driver in the Other driver field. Chapter 6. Using Host Publisher Studio to develop J2EE applications 175

190 In our scenario, we connect to the iseries and use *LIBL from the User ID by entering the values shown in Table 6-1. Table 6-1 Sample database connection values Fields Database URL User ID Password Driver Other driver (grayed out) Information jdbc:as400://<systemname> Your users ID Enter a proper password (iseries) AS/400 Toolbox for Java com.ibm.as400.access.as400jdbcdriver After you enter the required information for the database connection, click Connect to let Database Access connect to the database using the values you configured. Step 2: Configuring the database connection and connection pools Here, you configure the database connection for the Integration Object you plan to create. You can also enable and configure connection pools for better performance. If the Integration Object will use an existing connection pool, on the Connection Pools page (Figure 6-32), click Share an existing connection pool and select the pool from the drop-down list. Note: If this is the first time you are creating a database Integration Object, you should create the connection pool after you finish creating your database Integration Object. Figure 6-32 Database Access: Connection pools The Connection Configuration section of the panel displays the fields in the following sections. 176 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

191 Connection Name Enter the name for the connection or select an existing connection name from the drop-down list. Do not specify an extension, such as XML, for the name. The extension is appended to the connection name when you save the connection information or the Integration Object. If a new Integration Object is open and you do not specify a name for the connection, the connection name defaults to the name you specified in the Create a new connection pool field. If an existing Integration Object is open, this field displays the connection name specified when you saved it. Driver Specify the JDBC driver to use when connecting to the database or select a driver name from the drop-down list. If you have an existing Integration Object open, the connection name field displays the driver specified when you saved it. Database URL Specify the JDBC URL to use when connecting to the database. If you have an existing Integration Object open, this field displays the URL specified when you saved it. Connection Timeout Specify the number of seconds to wait for a connection to the database. If this value is reached before the connection to the database completes, the connection request fails. The User List Configuration section of the panel displays a User List field and two radio buttons. User List Name Specify the user list name to use when connecting to the database or select an existing user name from the drop-down list. Do not specify an extension, such as XML, for the name. The extension is appended to the user list name when you save the connection information or the Integration Object. Note: If you create multiple user list names with the same user ID and password values and the password changes after you create the user list names, you need to modify each user list name individually to update the password associated with the user list name. If you have an existing Integration Object open, this field displays the user list name specified when you saved the Integration Object. If you remove the user list name from this field, the user list name defaults to the open Integration Object name when you save the connection information or the Integration Object. Select one of the following radio buttons: Prompt for connection values at runtime: Select this radio button to allow the user ID and password to be entered by the end user. Use the following connection values: Select this radio button to use the same user ID and password for every transaction. If a new Integration Object is open, these fields display the user ID and password values specified on the Connect page. If an existing Integration Object is open, these fields display the user ID and password for the user list name specified when you saved the Integration Object. Chapter 6. Using Host Publisher Studio to develop J2EE applications 177

192 If you selected a user list name from the drop-down list for the User List field, these fields display the user ID and password for the selected user list name. Click Finish to save the Integration Object with the information you entered. This displays a save dialog for you to specify a name for the Integration Object and the folder into which you want to save it. If you did not specify a user ID in the Connection Pools tab, the user ID warning dialog reminds you that the field is empty, which may cause an error at runtime. Step 3: Creating the database Integration Object In this step, you create the database Integration Object (JavaBean) to query the Boats database. You provide the required information to create the SQL statement that will be sent to the Database for execution against the selected database. In our scenario, we want to query the Boats database for certain boat type. Whoever uses this Integration Object has to provide (set) the input variables (properties) to indicate whether the query is for boats. The Integration Object returns all boat satisfying this condition. The Integration Object can be invoked from a Java program or a JSP. We follow these steps: 1. Select the Tables tab. The Tables page is shown in Figure Select the SQL statement type. This is a query to the database, so choose the Select statement type. 3. Under Select Table(s), select the Boats.Boats table from the database, as indicated in Figure When you can t find the Boats table, use the View schema(s) button to select the Boats library. Figure 6-33 Selecting the SQL statement type and table 178 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

193 4. Click the Condition 1 tab. The Condition 1 page is displayed (Figure 6-34). The first condition in the SQL statement is the boat type. It is input to the Integration Object, so we create a variable (property). Click Variable and provide a meaningful name such as btypevar. Then click OK. Figure 6-34 SQL Query: Condition 1 5. Configure what columns should be returned by the Integration Object in the SQL statement. Click the Columns tab (Figure 6-35). Select the column name and click Add. In this scenario, we return the boat type, name, feet, year, and cost. Chapter 6. Using Host Publisher Studio to develop J2EE applications 179

194 Figure 6-35 Selecting columns returned by the Integration Object 6. Click the Sort tab (Figure 6-36). You can specify the sort order for the rows and columns to be returned. In our scenario, we choose to sort by boat type in ascending order. Figure 6-36 Specifying the sort order of the rows and columns 180 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

195 7. The Database Access application allows you to see the generated SQL statement for the options you provided. Click the SQL tab (Figure 6-37) and verify the statement to make sure that the generated query is what you intended. 8. For testing purposes, click the Run SQL button. You can actually run the SQL statement against the database. Figure 6-37 Generated SQL statement Since the database Integration Object needs the input variable we created, the Database Access prompts you to enter the value, as shown in Figure Figure 6-38 Entering a value for the configured input variable Chapter 6. Using Host Publisher Studio to develop J2EE applications 181

196 9. Click Run SQL to execute the SQL statement against the DB2 UDB for iseries database. You obtain the results shown in Figure Figure 6-39 Query result 10.After you test the SQL statement you created, click OK to return to the main window and click Finish to save the Integration Object and other related files. Figure 6-40 indicates a successfully created Integration Object. Figure 6-40 Integration Object successfully created Created files When you save the database Integration Object, the following files are created in c:\hostpub\studio\integrationobjects\: Boat_db.hpi: This XML file contains information about the Integration Object, such as the generated SQL statement, database URL, driver name, and the pool name associated with the Integration Object. Boat_db.hpt: This XML file contains definitions for the variables and other related information required by the Integration Object process. Boat_db.jar: This file contains the compiled and compressed Integration Object byte-codes. Boat_db.java: This file contains the generated Integration Object Java source code. 182 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

197 Boat_db.mf: This file contains the created manifest with information about the contents of the Java Archive (JAR) file. For more details and editing guidelines, see IBM WebSphere Host Publisher Programmer s Guide and Reference. 6.5 Application Integrator Use the Application Integrator component of Host Publisher Studio to create Web pages that use the Integration Objects you created using Host Access or Database Access. Application Integrator enables you to import Integration Objects, Enterprise JavaBeans Access Beans, and other JavaBeans or objects. See 6.9, Application Integrator Advanced on page 235, for more information about Enterprise JavaBeans and Web Services Specifying Integration Objects to publish to the application server A Host Publisher application is a collection of Web pages, Integration Objects, and other Java objects that enable the end user to interact with multiple data sources. Application Integrator enables you to build a series of Web pages using standard HTML tags in conjunction with special JSP tags and Java code. These standard tags manipulate Java objects (such as an Integration Object) on the Web page. These tags also provide the ability to specify Java object output directly on the page. JSP tags are designed for any Java object or bean. You can use Application Integrator to import other Java classes or beans, in addition to Host Publisher Integration Objects, into your application and publish them into Web pages. Application Integrator accepts as input any Integration Objects, other Java components, or any prebuilt HTML pages to which you want to add data interactions. The output is a collection of Web pages (JSPs) that have been generated or modified to interact with Integration Objects Using the Application Integrator wizards You can use the Integration Objects that Host Publisher creates to build your own server-side components, such as servlets, JSPs, EJBs or Web Services. This section explains how to develop Host Publisher applications using the Host Publisher Studio to generate an application based on JSPs. The Host Publisher application execution process can be described as follows (see Figure 6-41): 1. The input page is invoked via a URL. The page contains a form, and the user enters the required information, such as account number or name. 2. The user submits the request and the output page is posted. 3. The output page gets control and executes the following methods: Setter methods to pass the input variables Integration Object invocation Getter methods to obtain the output variables 4. The output page is dynamically built including the obtained output variables. 5. The error page is called in case of an error. Chapter 6. Using Host Publisher Studio to develop J2EE applications 183

198 Figure 6-41 Host Publisher Studio applications The following steps explain how to create Web pages that use the Integration Objects that you created using Host Access or Database Access: 1. Launch the IBM WebSphere Host Publisher Studio and start a new application by clicking File-> New Application..., as shown in Figure Figure 6-42 New application 2. Provide a name for your application (Figure 6-43) so that it can be identified when you are ready to transfer and deploy it. 184 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

199 Figure 6-43 Naming the application 3. As illustrated in Figure 6-44, there are two ways to start building your application: Select the I prefer to start with data option if you are familiar with the Integration Object input and output variables (properties) and want to create the input, output, and error pages. Start creating pages if you already have a page layout for your application. In this sample scenario, the option I prefer to start with data is selected. Figure 6-44 Selecting how you want to start 4. Import the Integration Object(s) that will be used for this new application. Click Import (Figure 6-45) and select all the Integration Objects you need. Chapter 6. Using Host Publisher Studio to develop J2EE applications 185

200 Figure 6-45 Importing the Integration Object 5. After you import the Integration Object, define how it will be used. Select the Integration Object and click Define (Figure 6-46). Figure 6-46 Defining how the Integration Object will be used At this time, the Host Publisher Studio knows which input and output properties are required to be set (setters) and obtained (getters) for the defined Integration Object. 6. Host Publisher Studio starts collecting information to create the input and output (execution) JSPs. As shown in Figure 6-47, enter the name of the output page that also invokes your Integration Object. 186 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

201 Figure 6-47 Specifying the output page name 7. Host Publisher Studio has detected that the Integration Object has an input property with name settype. This input property needs to be set prior to invoking the Integration Object. Therefore, you must define how the value should be obtained. In most cases, it is typically requested using an input page containing a form. As shown in Figure 6-48, click Define to proceed with this definition. Figure 6-48 Providing input data 8. Define how the input fields are obtained. In this sample scenario, there is only one field, which will be a new input field. Figure 6-49 illustrates how the option is selected for a new input field. Chapter 6. Using Host Publisher Studio to develop J2EE applications 187

202 Figure 6-49 New input field 9. Select whether you want to create a new form or use an existing form if one is already created. Figure 6-50 shows the selection you need to create a new form. Figure 6-50 Creating a new form 10.Enter the name of the input page containing the form. Figure 6-51 highlights this portion of the window. Optionally, you can also customize the label for the Submit button in the form. Figure 6-51 Input page 11.Select the input control for the input field. See Figure 6-52 for details. There are several ways to capture input fields. In this scenario, the input field is a boat type, so select List box. 188 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

203 Figure 6-52 Selecting the option to obtain the input field 12.In this scenario, a List box is selected to capture the input field. Define the label for each boat type. See Figure Figure 6-53 Defining the label Also provide a proper label such as the one shown in Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 189

204 Figure 6-54 List box label Click Finish to proceed with another input field, if necessary. In this scenario, there is only one input field. Therefore, you proceed to define how the output will be shown. 13.Define how the output data will be presented. As illustrated in Figure 6-55, select one or more output fields and click the Render button. Note: The output fields are obtained from the Integration Object output properties. Figure 6-55 Selecting the output fields to be displayed 14.You can optionally preview the created JavaServer Pages. However, keep in mind that the imported Integration Object(s) will not be executed. Therefore, the output field results are blank fields. See Figure 6-56 and Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

205 Figure 6-56 Input page Figure 6-57 Output page Note: To see the pages with actual data, you need to transfer and deploy the application in a supported WebSphere Application Server or import the Host Publisher Application Integrator generated EAR file into WebSphere Studio Application Developer and debug it. 15.This is an optional step, because Host Publisher includes a default error page. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 191

206 Figure 6-58 Host Publisher error page This page helps you to identify any problems in your Host Publisher application. Figure 6-59 shows the option to create this page. Figure 6-59 Creating an error page Figure 6-60 shows the default error page. 192 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

207 Figure 6-60 Default error page Afterward, you can preview all pages. Select the JSP and click Options-> Preview to start the default browser. See Figure Figure 6-61 Preview 16.After the Host Publisher Studio creates the JSP files, the application can be deployed to your users. At this point, the pages of the application are very plain and simply display the data you request from the host. In most cases, the developer may want to do further customization to the files to produce the desired look and feel for the Web application. You may want to perfect your files in a WebSphere Studio Tool that supports WebSphere Version 4, such as WebSphere Studio Application Developer (Figure 6-62). Chapter 6. Using Host Publisher Studio to develop J2EE applications 193

208 Figure 6-62 WebSphere Studio Application Developer Figure 6-63 shows the created input, output, and error pages. It also illustrates the Integration Object with the methods used (setters, getters, and execution). 194 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

209 Figure 6-63 Host Publisher Studio 17.Save your application in the Host Publisher Studio (Figure 6-64). Once this is done, your application is ready to be transferred to the Host Publisher Server for deployment. Chapter 6. Using Host Publisher Studio to develop J2EE applications 195

210 Figure 6-64 Saving your application Transferring applications to a Host Publisher Server IBM WebSphere Host Publisher, using Application Integrator, enables you to transfer applications to the WebSphere Application Server. It gives you the ability to transfer your J2EE application to one or more Host Publisher Servers, making the application ready to install as an Enterprise Application. Two things happen when you transfer an application to the server: The application and associated files are assembled and packaged into an EAR (Enterprise Archive) file. The EAR file is moved to the specified server or servers using File Transfer Protocol (FTP). When you use the Transfer to Server wizard, you are prompted to select one or more servers and you can make changes to resources such as connection pools and user lists. Transferring to the server Host Publisher Studio gives you the ability to transfer your Web application to Host Publisher Servers, making the application ready for deployment on the WebSphere Application Server. To start the transfer to server operation, click File-> Transfer to Server as shown in Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

211 Figure 6-65 Transfer application to a staging area in the server Once the application is organized into a staging directory on the Host Publisher Studio machine, FTP is used to transfer the contents of the application to the specified Host Publisher Servers. Note: Transferring files to a remote system requires FTP. Therefore, you need FTP client support in the system where IBM WebSphere Host Publisher Studio is running and FTP server support (daemon) in your target server. The following list summarizes the steps that are executed when the Transfer to Server operation is started: 1. Select the Host Publisher Server. 2. If remote servers are not yet defined, configure them (see Figure 6-66) to provide information for the FTP protocol. 3. Start the actual transfer (see Figure 6-63 on page 195). Transferring to a remote server When you transfer to a remote Host Publisher Server, you need to specify information for connecting to and delivering application content. This information pertains specifically to the target Host Publisher Server, and not simply a Web server. The following fields are configured (see Figure 6-66): Host Publisher Server TCP/IP host name: Specify the TCP/IP host name that uniquely identifies the Host Publisher Server in your network. You can substitute the TCP/IP Chapter 6. Using Host Publisher Studio to develop J2EE applications 197

212 address of the server for the name. When establishing a TCP/IP connection to the server, the Host Publisher Studio searches the network for the server with this TCP/IP name or address. Either the TCP/IP host name or address is required. Port number: Specify the TCP/IP port to use when connecting to the server through FTP. By default, this field specifies the well-known FTP port number 21. If FTP is configured on the server with a different port number, change the value. Login user ID: Specify the user ID with which to log in to the Host Publisher Server. The user ID must have sufficient privileges to transfer files to the target staging directory you specify. You receive a prompt to enter the password associated with this user ID when a connection to the server is attempted. If more than one server definition specifies the same login user ID, you receive the prompt for the password only one time when these servers are selected as part of the Transfer to Server function. The login user ID value is required. Server platform: Select the operating system platform of the server from the drop-down list. Some server platforms have specific requirements for file formats and code pages. See Figure Target directory on server: For iseries, there are two default directories: WebSphere AE: /QIBM/UserData/WebASAdv4/default WebSphere AEs: /QIBM/UserData/WebASAEs4/default Figure 6-66 Host Publisher Server Definition Executing the transfer After you select the target Host Publisher Servers, click Transfer to start the actual file transfer operation. The Transfer completed successfully message indicates that the operation was successful (circled in Figure 6-67). 198 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

213 Figure 6-67 Transfer to Server Deploying the application on WebSphere Application Server Web Administrative Console (WebSphere Application Server Advanced Single Server Edition) or the Java Administrative Console (WebSphere Application Server Advanced Edition) can deploy an application to the WebSphere Application Server. This section explains how to install an application into the WebSphere Application Server environment. This includes placing the files comprising an application onto the physical system containing the WebSphere Application Server product and updating the application server configuration with information about the application. Installing applications on WebSphere Application Server Advanced Edition Installing applications (or standalone modules) into the application server runtime involves the following tasks: 1. Configure the application settings in the administrative console by performing an application installation task (requires the administrative server to be running). Install enterprise applications and modules with the Java administrative console. 2. Place the application files in a directory location, usually relative to the IBM WebSphere Application Server product_installation_root. Place the files in the location of your choice. Specify the location when you are performing the application installation task. a. Using WebSphere Application Server Advanced Edition on Windows, bring up the WebSphere Advanced Administrative Console. Click Console-> Wizards-> Install Enterprise Application. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 199

214 Figure 6-68 Install Enterprise Application b. Select the EAR file. See Figure Figure 6-69 Select EAR file c. Click Next until the Selecting Virtual Hosts for Web Module panel opens and select your Virtual Host. The default is default_host. d. In the next panel (Figure 6-70), click Select Server to select the Host Publisher Server. 200 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

215 Figure 6-70 Select Application Server e. Click Next and Finish to deploy the EAR file to the WebSphere Application Server. 3. Set the classpaths as needed in addition to those set during application assembly. 4. When you reach the Select Application Server window (Figure 6-71), select HostPubServer as the application server on which you want to install the modules contained in your application. Chapter 6. Using Host Publisher Studio to develop J2EE applications 201

216 Figure 6-71 New Enterprise Application 5. Start the Enterprise Application as shown in Figure Web Server Plug-in is set, by default, to automatic regen. Figure 6-72 Starting the Enterprise Application 202 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

217 Installing applications on WebSphere Application Server Advanced Single Server Edition Installing applications (or standalone modules) into the application server runtime involves the following tasks: 1. Configure the application settings in the administrative console, by performing an application installation task (requires the administrative server to be running). Install enterprise applications and modules with the Web Administrative Console. 2. Place the application files in a directory location, usually relative to the IBM WebSphere Application Server product_installation_root. Place the files in the location of your choice. Specify the location when you are performing the application installation task. a. Use a Web browser to start the Web Administrative Console ( Navigate to Nodes-> SystemName-> Enterprise Application and click the Install button. See Figure Figure 6-73 Installing Enterprise Application b. Select the EAR file and click Next. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 203

218 Figure 6-74 Selecting the EAR file c. Select your virtual host. The default is default_host. Leave Precompile JSPs set to Yes and click Next. See Figure Figure 6-75 Selecting the virtual host d. Confirm the information on the next page and click Finish. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

219 Figure 6-76 Confirming the details 3. Set the classpaths as needed, in addition to those set during application assembly. 4. Your new application is now installed and can be started. Select your application and click the Start button. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 205

220 Figure 6-77 Starting the application For details, see: WebSphere Application Server Information Center: IBM WebSphere V4.0 Advanced Edition Handbook, SG IBM WebSphere Host Publisher Administration and Users Guide, GC Creating composite applications Composite applications combine multiple Integration Objects to produce a single stream of output information to the user. Composite applications enable you to use the output of one Integration Object as input to another or fill a table with data from several different Integration Objects that access different data sources. The four ways to produce a composite application using Host Publisher Studio are: Combining Integration Objects output Sequencing Integration Objects on a single page Sequencing Integration Objects on multiple pages Sequencing Integration Objects between non-adjacent pages Refer to Chapter 11 in the redbook A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG , to learn how to develop composite applications. 206 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

221 6.7 Enterprise JavaBeans support Enterprise JavaBeans is a server-side component architecture that enables rapid development of versatile, reusable, portable applications. This section describes common tasks associated with developing Host Publisher EJB applications. EJB support in Host Publisher is intended for use by enterprises that run their backend servers using EJB technology. With EJB support in Host Publisher, you can logically (or physically) partition the Integration Object s function of navigating and retrieving backend enterprise data from the presentation and consumption of that data. This processing model is aligned with the J2EE three-tier application model Understanding EJB support in Host Publisher Host Publisher provides support for executing Integration Objects in EJB containers to take advantage of the server-side characteristics provided by the EJB architecture. This support consists of the following parts: The Host Publisher EJB, which is a stateful session EJB capable of running Integration Objects in an EJB environment. (Stateful means that the EJB maintains a conversational state with the client for the duration of an application.) This EJB is contained in the EAR file for each application. Host Publisher Studio support for the generation of EJB support files for running Integration Objects. This includes, for each Integration Object, the generation of an EJB access bean that provides the same signature as the real Integration Object. Application Integrator support for building applications using the generated EJB support files and the Host Publisher EJB. Because the EJB access bean has the same signature as the Integration Object, the EJB access bean can be used in client-side code exactly as a real Integration Object would be used. Therefore, the client can be: A JSP page or a servlet that uses one or more EJB access beans in a J2EE application where the Integration Objects execute in an EJB container. A Java application client that uses one or more EJB access beans to execute the Integration Objects in an EJB container. A Java application thin client that uses one or more EJB access beans to execute the Integration Objects in an EJB container. Refer to the WebSphere documentation Web site for more information about Java application clients and Java application thin clients: Figure 6-78 shows the components of a typical EJB application: The JSPs, packaged together with the EJB access beans in the application.war file, execute in a Web container. The Host Publisher EJB, packaged as an EJB JAR file, executes in a WebSphere EJB container. Chapter 6. Using Host Publisher Studio to develop J2EE applications 207

222 Figure 6-78 Components of a typical EJB application Creating EJB support files for Integration Objects If you intend to generate EJB support files for an Integration Object, you must specify this before you create the Integration Object. Using Host Access or Database Access, click Options-> Create EJB 1.1 Integration Object Support as shown in Figure Figure 6-79 EJB support When this option is selected, EJB support files are generated during the creation of the Integration Object. An EJB access bean JAR file is created in the \IntegrationObjects directory, and additional EJB support class files are created to be bundled with the IO JAR file. The default name for the EJB access bean JAR file is IONameAccess1.jar, where IOName is the name of the Integration Object. 208 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

223 Specifying the default properties for EJB Integration Objects In Host Access and Database Access, the Options menu has an EJB Integration Object Properties selection. This option specifies a file suffix that is added to the names of the files (.class files and.java files) associated with the Integration Object. The suffix helps you easily locate the EJB-specific files that are generated by Host Publisher Studio. A default suffix is provided, but you can use the EJB Integration Objects Properties option to specify a different suffix for the EJB Integration Object you are currently working on. The default suffixes, shown in Figure 6-80, are: Properties for the Properties Object file Helper for the Helper Object Access1 for the EJB 1.1 Access Bean Figure 6-80 EJB Integration Object Properties The generated files are stored in the C:\HostPub\Studio\IntegrationObjects\EJB\IOName\IntegrationObject directory. See Figure Figure 6-81 EJB support files To change the default suffixes for this option, edit the following properties in Studio.ini: EJB_PROPERTIES_SUFFIX EJB_HELPER_SUFFIX EJB11_ACCESS_SUFFIX Chapter 6. Using Host Publisher Studio to develop J2EE applications 209

224 6.7.3 Accessing Host Publisher EJB from local JSPs This scenario illustrates and guides you through the process of implementing a simple Host Publisher application using Host Publisher EJB support and JSPs created to instantiate the EJB access bean to locally access the Host Publisher EJB. An overview of this scenario is shown in Figure Note: The procedure to access Host Publisher EJB from local servlets is similar, but is not shown in this scenario. Figure 6-82 Accessing Host Publisher EJB from a local JSP In this scenario (Figure 6-82), the request follows this flow: 1. The JSP is accessed from the Web browser, for example via a URL or POST operation. The JSP instantiates the EJB access bean (a JavaBean). The EJB access bean was previously generated by Host Access (Studio) when you saved the Integration Object. Also, the interface that the EJB access bean provides is similar to the one provided by the Integration Object (setter, dohptransaction, and getter methods). 2. When the execution method is invoked in the EJB access bean, it communicates with the Host Publisher EJB (a session stateful EJB) via RMI/IIOP. That is, the EJB access bean provides the EJB client code, and it uses the provided JNDI, by default, to locate the Host Publisher EJB. Note: Since communication between the EJB access bean and the Host Publisher EJB is local in this scenario, the TCP/IP stack is not used and, therefore, provides better performance. 3. The Host Publisher EJB instantiates the Integration Object (a JavaBean) using the setter, dohptransaction, and getter methods. 4. The Integration Object executes the host application transaction via the Telnet 5250 transport and passes the response back to the Host Publisher EJB. For this scenario, we assume that the Integration Object is already created and EJB support files are generated using the procedure outlined in 6.7.2, Creating EJB support files for Integration Objects on page 208. Creating the JSPs To create an Integration Object in Host Publisher and enable it to become an EJB, perform the following steps: 210 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

225 1. Using Host Publisher Studio, create one or more Integration Objects or EJB access beans. Click Options-> Create EJB 1.1 Integration Object Support as shown in Figure 6-79 on page Import the EJB access beans into Application Integrator. Create an application that consists of EJB access beans, and then generate an EAR file for the application. Click File-> Create J2EE Archives as shown in Figure Figure 6-83 Creating J2EE Archives 3. Define all the parameters and create the Input, Output, and the Error JSPs. Transfer the EAR file to the server. For a closer look at how to create an application with the Application Integrator, see 6.9, Application Integrator Advanced on page Creating a Host Publisher application using EJB access beans After EJB access bean JAR files are created for Integration Objects, you can use them with Application Integrator in the same way that you use Integration Object JAR files to create Host Publisher applications. You can create JSPs to instantiate, drive, and render the EJB access bean output properties in the same way that you use the original Integration Objects, including support for EJB access beans created for chained Integration Objects. Before the application is transferred to the server, it is packaged into an EAR file that contains a Web module, with all of its associated JSPs and EJB access beans, and an EJB module that contains the Host Publisher EJB, helper classes, and Integration Objects for the application. WebSphere Application Server V4.0 provides support for a new breed of Web applications called Web Services. Chapter 6. Using Host Publisher Studio to develop J2EE applications 211

226 6.8 Web Services overview Web Services provides a way for applications to connect and interact on the Web more easily and efficiently. Web Services consists of self-contained, modular applications that can be described, published, located, and invoked over the Web. Platform-neutral and based on open standards, Web Services can be combined with each other in different ways to create business processes that enable you to interact with customers, employees, and suppliers. Typically, Web Services use Internet protocols, such as HTTP, use XML message formats, and are plugged into Web Service registries where other developers can combine and deploy them. Think of them as strategic building blocks for automated business processes that can be deployed across your enterprise and shared with other enterprises. Support for Web Services has been implemented in a number of IBM software products, including WebSphere Application Server and WebSphere Studio tools (such as WebSphere Studio Application Developer). Host Publisher V4.0 supports creation of Web Services using Host Publisher Web Services support files with WebSphere Studio at the level or above. For more details, see Chapter 6, Web Services in IBM WebSphere V4.0 Advanced Edition Handbook, SG Host Publisher V4.0 Web Services support You can use the Host Access and Database Access components of Host Publisher Studio to create supporting files that enable Host Publisher Integration Objects and EJB access beans to be deployed as Web Services. Application Integrator assembles these Java objects (and optionally JSP pages that reference the Java objects) into a J2EE EAR file. You can then import the EAR file into a new or existing WebSphere Studio project, where you can create and deploy Web Services. Once you complete development and test your Web Services application within WebSphere Studio Application Developer, you can deploy the application on WebSphere Application Server. When you create Web Services Integration Object support in Host Publisher Studio with Host Access or Database Access, Web Services support files are generated during the creation of the Integration Object. The Web Services support files consist of: A properties object (named IONamePropertiesObjectSuffix), where IOName is name of the Integration Object and PropertiesObjectSuffix is the name specified for the Web Services Properties Object Suffix. The properties object contains all possible input and output properties for the Integration Object. A helper object (named IONameHelperObjectSuffix), where IOName is the name of the Integration Object and HelperObjectSuffix is the name specified for the Web Services Helper Object Suffix. This helper object extends the Integration Object. It initializes the input properties using an instance of the properties object, invokes the Integration Object with the specified input properties, and then returns the output properties via a new instance of the properties object. If you plan to create an Integration Object Web Service within a Web application, you use the helper object to create the Web Service using WebSphere Studio tools. If you want to create Web Services using Host Publisher EJB access beans, you must create EJB 1.1 Integration Object support, which generates Web Services support files. Use the EJB access bean to create the Web Service using WebSphere Studio tools. 212 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

227 Host Publisher Web Services support differs from programming with Integration Objects because only the following method is used to create the Web Service: IONamePropertiesObjectSuffix processwsrequest(ionamepropertiesobjectsuffix) throws BeanException The processwsrequest method is contained in the helper object when Create Web Services support is selected on the Host Access or Database Access Options menu. The IONamePropertiesObjectSuffix object contains the input and output of an Integration Object. This object is passed to and from the Web Services processwsrequest method. It contains getter and setter methods, but no additional methods. The processwsrequest method takes the properties object as input, drives the Integration Object with those input properties, and returns the output properties of the Integration Object through a new instance of the properties object. The advantage of using the processwsrequest method is that it provides a single method that sets all inputs, drives the Integration Object, and returns all outputs Creating and deploying a Web Service To create an Integration Object in Host Publisher and then enable it to become a Web Service, perform the following steps: 1. Using Host Publisher Studio, create one or more Integration Objects or EJB access beans. Click Options-> Create Web Services Integration Object Support (Figure 6-84). Figure 6-84 Web Services support 2. Import the Web Services Integration Objects or EJB access beans into Application Integrator. Create an application that consists of Web Services Integration Objects, EJB access beans, or both, and then generate an EAR file for the application. Click File-> Create J2EE Archives. 3. Import the EAR file into a J2EE-enabled WebSphere Studio tool, such as WebSphere Studio Application Developer. Chapter 6. Using Host Publisher Studio to develop J2EE applications 213

228 4. Use the WebSphere Studio tool to create a Web Service. See 6.8.5, Creating Web Services support in Host Publisher Studio on page Generate a sample application and run it to test your Web Service. 6. Complete development and testing of the application you imported in step Deploy the completed application. See 6.9.2, Deploying Enterprise JavaBeans on page Accessing Host Publisher from a remote machine using Web Services You may want to write a program that does not execute in WebSphere but that requires access to an Integration Object. In earlier versions of Host Publisher, you developed Remote Integration Objects (RIOs) to access Integration Object data from a Java program (applet or application) running on a remote machine. With the current version, you can use Web Services to perform this same function. The primary advantages of using Web Services over RIOs are: Web Services are strategic. Communication is based on a current, industry-standard suite of standards, APIs, and implementations such as Web Services technology framework or service-oriented architecture (SOA). They are based on the self-describing Web Service Description Language (WSDL), which is a descriptive interface and protocol binding language. The messaging of Web Services is XML messaging, based on the industry standard Simple Object Access Protocol (SOAP). SOAP is language-independent and interoperable between different programming languages executing on different operating systems. Web Services can be published and dynamically located. Universal Description, Discovery, and Integration (UDDI) is a registry mechanism that you can use to perform lookups for Web Services descriptions. After lookup, a client application can dynamically bind directly to Web Services provided by the service provider Specifying properties for Web Services Integration Objects In Host Access and Database Access, the Options menu has a Web Services Integration Object Properties selection. This option specifies file suffixes that are added to the names of the files (.class files and.java files) associated with the Integration Object. The suffixes help you easily locate the Web Services-specific files that are generated by Host Publisher Studio. Default suffixes are provided, but you can use the Web Services Integration Objects Properties option to specify different suffixes for the Web Services Integration Object you are currently working on. The default suffixes are: Properties for the Properties Object file Helper for the Helper Object To change the default suffixes for all Web Services Integration Objects, edit the Studio.ini file Creating Web Services support in Host Publisher Studio To create Web Services support, follow these steps: 1. To create Web Services support for a Host Publisher Integration Object, select the new Create Web Services Integration Object Support option in Host Access or DB Access (see Figure 6-84). This creates: 214 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

229 IO Properties class Helper class (see Figure 6-85) Figure 6-85 IO Properties and Helper classes 2. To create Web Services for an EJB access bean, select Create EJB 1.1 Integration Object Support. This creates all necessary support files. See Figure 6-84 on page When you finish creating IOs, use Application Integrator to package the IOs or EJB access beans into an EAR file and import a WAR or EAR file into WebSphere Studio Application Developer. See 6.9, Application Integrator Advanced on page 235. Before you export it to WebSphere Studio Application Developer, test your IOs with your WebSphere Applications Server Creating Web Services in WebSphere Studio Application Developer with Host Publisher Web Services support This section explains how to create Web Services in WebSphere Studio Application Developer V4.0.3 with Host Publisher Web Services Support function. The basic steps include: 1. Starting Host Publisher Server in WebSphere Studio Application Developer on page Importing the EAR file containing IOs or EJB access beans on page Creating Web Services for IOs and EJB access beans on page Running the Web Services sample generated by WebSphere Studio Application Developer on page Deploying the completed application to WebSphere Advanced Edition or Advanced Single Server Edition on page 233 Starting Host Publisher Server in WebSphere Studio Application Developer Use the sample code for starting and stopping Host Publisher Server to create servlets that start and stop Host Publisher Server: 1. Start the WebSphere Studio Application Developer. Click Start-> Programs-> IBM WebSphere Studio-> IBM WebSphere Studio Application Developer. 2. Select Web Project to create it (Figure 6-86). Click Next. Chapter 6. Using Host Publisher Studio to develop J2EE applications 215

230 Figure 6-86 New Web Project 3. Name the new project, for example HPRTE. 4. On the Define Java Build Settings window (Figure 6-87), click the Add External JARs button. 216 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

231 Figure 6-87 Defining the Java Build Settings 5. On the JAR Selection window (Figure 6-88), select the external JAR files (highlighted in the example) that contain the classes that Host Publisher Server requires from the C:\HostPub\Common directory so that the code will compile. Click Open. Figure 6-88 External JAR files Chapter 6. Using Host Publisher Studio to develop J2EE applications 217

232 6. Import the servlet code for starting and stopping Server into Web Project. Update the code to match your server installation. On the File system window (Figure 6-89), select the Start and Stop programs (StartHPRTE.java and StopHPRTE.java) to import them from the C:\HostPub\SDK\Server directory to your new project. Click Finish. Figure 6-89 Importing the Start and Stop programs 7. Update the code that starts Host Publisher Server to match your Host Publisher installation in the Application Developer window (Figure 6-90): a. Double-click the StartHPRTE.java source code. b. Search for the HP_INSTALL_DIR variable and update it to match your Host Publisher Studio installation directory. c. Save it. 218 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

233 Figure 6-90 Changing the Host Publisher installation path 8. Run the servlet. WebSphere Studio Application Developer creates an internal WebSphere server instance. Execution of the servlet fails because WebSphere cannot access the classes that Host Publisher Server requires. a. In the Navigator panel, select the StartHPRTE program, right-click, and select Run on Server (Figure 6-91). Chapter 6. Using Host Publisher Studio to develop J2EE applications 219

234 Figure 6-91 Run on Server Note: This creates an internal WebSphere server instance. Start the server and attempt to run the StartHPRTE servlet. b. You see the following error because the WebSphere Application Server does not have access to the required Host Publisher Server classes: [4/26/02 12:00:41:688 CDT] 5d1e02d8 WebGroup X Servlet Error-[StartHPRTE]: Failed to load servlet: java.lang.noclassdeffounderror: com/ibm/hostpublisher/server/authexception 9. Set up WebSphere Application Server to run the servlet. If using WebSphere Advanced Single Server Edition within WebSphere Studio Application Developer, update the WebSphere Specific class path to point to HP.jars as explained here: a. Open or go to the Server Perspective. Click Perspective-> Open-> Server. b. Double-click the defaultinstance.wsi. c. The WebSphere Test Environment window (Figure 6-92) opens. Click the Paths tab and click the Add External JARs button to add the files to the WebSphere specific class path. 220 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

235 Figure 6-92 Server Instance configuration d. Save the servlet. e. On the Web browser panel (Figure 6-93), select the server, right-click, and select Restart to restart the instance. Right-click StartHPRTE and select Run on Server to run the program again. Chapter 6. Using Host Publisher Studio to develop J2EE applications 221

236 Figure 6-93 Restarting the server f. If you don t see the result in Figure 6-93, close the Web browser and run the program again. Importing the EAR file containing IOs or EJB access beans Import the EAR or WAR file that contains IOs or EJB access beans that you want to create Web Services for into WebSphere Studio Application Developer: 1. Import the file into WebSphere Studio Application Developer: a. Import your EAR file from the C:\HostPub\Studio\Applications\YourApplicationName directory. Click File-> Import and select the EAR file. b. If you are creating Web Services for an IO, import the Helper class into WebSphere Studio Application Developer (into the WEB-INF\lib directory of the Web application) as shown in Figure 6-94, and click Finish. 222 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

237 Figure 6-94 Importing Web Services Helper 2. Update the build path to include Host Publisher.jars: a. Right-click the Web Module folder BoatsWSWeb in the navigator pane after importing and select Properties. b. On the Properties window (Figure 6-95), select Java Build Path and click the Libraries tab. c. Choose the same JAR files as you did in Figure 6-92 on page 221 and click Add External JARs. d. Click OK. Chapter 6. Using Host Publisher Studio to develop J2EE applications 223

238 Figure 6-95 Including Host Publisher JAR files in the build path 3. If you are working with EJB access beans, generate deployment code: a. In the Navigator panel of the WebSphere Application Developer window (Figure 6-96), right-click your EJB Project, select Generate and choose Deploy and RMIC Code. b. On the Generate Deploy Code and RMIC Code window (Figure 6-97), select your EJB Project again and click Finish. 224 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

239 Figure 6-96 Generating the Deploy and RMIC Code Figure 6-97 Generate Deploy and RMIC Code 4. If you created JSP files in Host Publisher Application Integrator, you may test the IOs or EJB access beans within WebSphere Studio Application Developer to ensure that they work as desired before you create Web Services. Chapter 6. Using Host Publisher Studio to develop J2EE applications 225

240 Creating Web Services for IOs and EJB access beans Create Web Services for IOs and EJB access beans from the processwsrequest method in the Helper class or EJB access bean. Choose to create a sample to test the Web Services: 1. Change to the Web Perspective. 2. Navigate to File-> New-> Web Service. 3. On the Web Service window (Figure 6-98), select the following options: Java bean Web Service for Web service type Your Web project The Generate a proxy check box The Generate a sample check box Click Next. Figure 6-98 New Web Service 4. Click Browse classes again. 5. On the Browse Classes window (Figure 6-99), type the first letter of the class name. 6. Select your Helper class if you are creating Web Services for an Integration Object. Select the Access Bean class if you are creating Web Services for an EJB access bean. Click OK. 226 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

241 Figure 6-99 Browse Classes 7. Click Next on the Web Service Java Bean Selection window. 8. On the Web Service Java Bean Identity window (Figure 6-100), select Request for Scope. Note: Request Scope means that the Helper Object or EJB access bean is available for the duration of the HTTP request. Click Next. Chapter 6. Using Host Publisher Studio to develop J2EE applications 227

242 Figure Scope 9. On the Web Service Java Bean Methods window (Figure 6-101), deselect all methods except: IntegrationObect.YourWSProperties processwsrequest Click Next. 228 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

243 Figure Selecting processwsrequest 10.Continue clicking Next on each window (keeping the default settings) until you reach the Web Service Publication window (Figure 6-102). It shows what is generated during the Web Services creation. Chapter 6. Using Host Publisher Studio to develop J2EE applications 229

244 SOAP-XML admin for displaying, starting, and stopping services. Sample Web Services client program. Proxy class, that you can use to access the Web Service when you develop a Web Service client..wsdl files that describe the interface of the Web Service and where an implementation is running. Figure Generated files Running the Web Services sample generated by WebSphere Studio Application Developer Now we are ready to run our example within the WebSphere Studio Application Developer Test Environment: 1. Start the Host Publisher Server. Right-click the StartHPRTE servlet and choose Run on Server. Note: Be sure that Host Publisher Server starts successfully as shown in Figure Open your Web Project. Expand webapplication-> sample-> YourWSHelper, and select TestClient.jsp. Right-click TestClient.jsp and select Run on Server. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

245 Figure Starting the TestClient.jsp 3. Choose the processwsrequest method. 4. Set the input properties to: hpubendtype = 0 hpuberroroccurred = 0 hpubstarttype = 0 Type any input that the Integrated Objects requires. See Figure as an example. In this example, we set Boat Length to 720 and Boat Type to S. Click Invoke. Chapter 6. Using Host Publisher Studio to develop J2EE applications 231

246 Figure IO inputs 5. Inspect the results in the Results panel (Figure 6-105). In this example, note the following explanation: Boat Type: S Model: Spandau Length: 720 Year: 1999 Amount: 100,000, iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

247 Figure Results Deploying the completed application to WebSphere Advanced Edition or Advanced Single Server Edition Follow these steps: 1. Go to the Navigator pane and change the proxy URL to point to your production Simple Object Access Protocol (SOAP) server URL. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 233

248 Figure Changing the proxy URL 2. Export your project to an.ear file. Select File-> Export and select the export destination EAR file. Then click Next. 3. The EAR Export window opens. Select your project, BoatWS, and your directory. Then click Finish. See Figure iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

249 Figure EAR Export 4. Install the application and start it using WebSphere Administrative Console. See 6.9.2, Deploying Enterprise JavaBeans on page Run the application. 6.9 Application Integrator Advanced In 6.5, Application Integrator on page 183, we cover the main topics about the Application Integrator. This section provides more details about Enterprise JavaBean and Web Services Creating a new application for EJB or Web Services This section explains how to create a new application for EJB or Web Services. Creating the Integrated Objects Using Host Publisher Studio, create one or more Integration Objects or EJB access beans. Click Options and select Create Web Services Integration Object Support and Create EJB 1.1 Integration Object Support. See Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 235

250 Figure Web Services support Save it and the creation status window (Figure 6-109) opens. Figure Integrated Object generated You can click the Details button to find more information about the created files as shown in Example 6-2. Example 6-2 IO creation Generating Java template files Compiling Java Integration Objects Examining Integration Objects Creating JAR file Start of creating EJB Support Files Creating EJB Access Bean source file: C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSAccess1.java Creating EJB Helper source file: C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSHelper.java 236 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

251 Creating EJB Properties source file: C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSProperties.java Compiling EJB Support source files: C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSAccess1.class C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSHelper.class C:\HostPub40\Studio\IntegrationObjects\EJB\Boat_dbWS\IntegrationObject\Boat_dbWSProperties.class Creating EJB Access Bean JAR file: C:\HostPub40\Studio\IntegrationObjects\Boat_dbWSAccess1.jar End of creating EJB Support Files Start of creating Web Services Support Files Creating Web Services Helper source file: C:\HostPub40\Studio\IntegrationObjects\WS\Boat_dbWS\IntegrationObject\Boat_dbWSHelper.java Creating Web Services Properties source file: C:\HostPub40\Studio\IntegrationObjects\WS\Boat_dbWS\IntegrationObject\Boat_dbWSProperties.java Compiling Web Services Support source files: C:\HostPub40\Studio\IntegrationObjects\WS\Boat_dbWS\IntegrationObject\Boat_dbWSHelper.class C:\HostPub40\Studio\IntegrationObjects\WS\Boat_dbWS\IntegrationObject\Boat_dbWSHelper.jar Creating Web Services Helper JAR file: C:\HostPub40\Studio\IntegrationObjects\WS\Boat_dbWS\Boat_dbWSHelper.jar End of creating Web Services Support Files Integration Object created successfully EJB files created successfully Web Services files created successfully Starting the new application Launch the IBM WebSphere Host Publisher Studio and start a new application: 1. Click File-> New Application Choose a new application name. 3. Select I prefer to start with data. 4. Click Next. The New Application panel for Integration Objects (Figure 6-110) opens. Figure New Application window for Integration Objects Chapter 6. Using Host Publisher Studio to develop J2EE applications 237

252 Importing the Integration Object You need to import the Integration Object or Objects that will be used for this new application: 1. Click the Import button (Figure 6-110). 2. On the next window, select the BoatWSAccess1.jar file (Figure 6-111) from the C:\HostPub40\Studio\IntegrationObjects directory. 3. Click Open to import the JAR. Figure BeatWSAccess1.jar 4. Define all the output, input, and error pages as described in 6.5.2, Using the Application Integrator wizards on page Deploying Enterprise JavaBeans Section 6.5, Application Integrator on page 183, covers the main topics about deploying J2EE files to the WebSphere Application Server. This section offers more details about Enterprise JavaBean and Web Services Transferring applications to a Host Publisher Server The transfer of applications, from the client to the server, is fully covered with 6.5, Application Integrator on page 183. There are no differences for EJB and Web Services Deploying the application on WebSphere Application Server This section explains how to install an application into the WebSphere Application Server environment. This includes placing the files comprising an application onto the physical system containing the WebSphere Application Server product and updating the application server configuration with information about the application. Installing applications (or standalone modules) into the application server runtime involves the following steps: 1. Configure the application settings in the administrative console, by performing an application installation task (requires the administrative server to be running). Install enterprise applications and modules with the Java administrative console. 2. Place the application files in a directory location, usually relative to the IBM WebSphere Application Server product_installation_root. 238 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

253 Place the files in the location of your choice. Specify the location when you are performing the application installation task: a. Using WebSphere Application Server Advanced Edition on Windows, bring up the WebSphere Advanced Administrative Console (Figure 6-112). Click Console-> Wizards-> Install Enterprise Application. Figure Installing Enterprise Application b. On the Specifying the Application or Module window (Figure 6-113), select the EAR file. Figure Selecting the EAR file Chapter 6. Using Host Publisher Studio to develop J2EE applications 239

254 c. Click Next until you see the Binding Enterprise Beans to JNDI Names window (Figure 6-114). If there is an EJB bean, you can edit the JNDI name as shown in the example. The default name that the Application Integrator specifies can be used in almost all cases. Click Next. Figure Edit JNDI name d. The Mapping EJB References to Enterprise Beans window opens. Click Select EJB and select the bean on the Select EJB window (Figure 6-115). 240 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

255 Figure Selecting the bean e. In the next few panels, define more about EJB. See the WebSphere Information Center for more information: For WebSphere Advanced Edition: For WebSphere Advanced Single Server Edition f. On the Selecting Virtual Hosts for Web Module window, select your virtual host. The default is default_host. g. On the Selecting Application Servers window (Figure 6-116), select an application server for both modules. Click the Select Server button. The key point is that the EJB JAR module must specify the Host Publisher Server. It is not necessary for the.war module to be installed on the Host Publisher Server. It can be installed in another server if the user wants separation of presentation logic (the WAR module) from business logic (the EAR module). Chapter 6. Using Host Publisher Studio to develop J2EE applications 241

256 Figure Selecting the Application Server h. Click Next and Finish to deploy the EAR file to the WebSphere Application Server. i. The Deploy message shown in Figure appears. Click Yes. Figure Generate code? j. On the Deploy window (Figure 6-118), select the only iseries database type. It takes a few minutes to deploy the code. 242 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

257 Figure Selecting the database type 3. Right-click your node, and select Regen Webserver Plugin. Verify that the Enterprise Application is started. See Figure Figure Regen Webserver Plugin 4. Test your application. You should see a result like the example in Figure Chapter 6. Using Host Publisher Studio to develop J2EE applications 243

258 Figure Results For more details, see: WebSphere Information Center IBM WebSphere V4.0 Advanced Edition Handbook, SG IBM WebSphere Host Publisher Administration and Users Guide, GC Host Publisher Portlet The WebSphere Portal Family provides simplified access to information, applications, processes, and people. The Portal Family solutions provide the open and extensible framework of the WebSphere Portal Server. Plus it offers the flexible and scalable infrastructure needed for many types of portals supporting business-to-business (B2B), business-to-customer (B2C), and business-to-employee (B2E) usage models. WebSphere Portal Server provides the base on which to build enterprise, marketplace, consumer, and workspace portals accessible from a wide variety of desktop and mobile devices. The IBM WebSphere Host Publisher Portlet enables the user to run Host Publisher 4.0 applications in a portlet. Only Host Publisher Version 4.0 applications are supported. However, not all Host Publisher 4.0 applications may be viewed in a portlet. If a Host Publisher application uses frames or the express logon feature, it will not be supported. Also, the portlet does not support applications that run over Secure Sockets Layer (SSL). For more information, refer to the portal documentation Web site at: WebSphere Studio Application Developer Web Services limitations There are known limitations with WebSphere Studio Application Developer to test Web Services. For example, WebSphere Studio Application Developer does not generate a sample for methods that contain unsupported types such as arrays, indexed properties, and collections. For more information about the limitations and problem determination, refer to the Host Publisher README file which is in Library of Host Publisher Studio. 244 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

259 6.12 References This section include Web sites and book related to WebSphere Host Publisher and WebSphere Application Server that can serve as helpful references Host Publisher Studio and Server IBM WebSphere Host Publisher Administrator s and User s Guide Version 4.0 located under C:\HostPub\Common\doc\guide IBM WebSphere Host Publisher Programmer s Guide and Reference Version 4.0 located under C:\HostPub\Common\doc\proggd IBM WebSphere Host Publisher Readme Version 4.0 located under C:\HostPub\Common\doc\ A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG Host Publisher support page WebSphere Application Server for iseries Chapter 24, Troubleshooting in IBM WebSphere V4.0 Advanced Edition Handbook, SG WebSphere 4.0 Installation and Configuration on the IBM eserver iseries Server, SG WebSphere Application Server for iseries home page WebSphere Application Server support page EJB WebSphere J2EE Application Development for the IBM eserver iseries Server, SG IBM WebSphere Host Publisher Programmer s Guide and Reference Version 4.0 located under C:\HostPub\Common\doc\proggd developerworks WebSphere Developer Domain VisualAge Developer Domain Enterprise JavaBeans Technology Chapter 6. Using Host Publisher Studio to develop J2EE applications 245

260 Web Services Portlet WebSphere Studio Application Developer and Web Services, SG Web Services Wizardry with WebSphere Studio Application Developer, SG WebSphere Developer Domain developerworks VisualAge Developer Domain Web Services and UDDI Java Technology and Web Services Portlet Catalog: Installation documentation WebSphere Information Center WebSphere Portal Server online help IBM WebSphere Host Publisher Portlet Version Summary This chapter covered the aspects of creating J2EE applications with Host Publisher Integrated Objects. While we could have briefly touched on each topic, we hope to have given you a clearer picture of how to create successful J2EE applications in WebSphere Host Publisher. 246 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

261 7 Chapter 7. iseries Access for Web and Host Publisher integration iseries Access for Web and Host Publisher V4.0 can be integrated to provide a complete Web solution. One common home page is used combining iseries Access for Web and Host Publisher. The example in this chapter provides a general integration overview of iseries Access for Web and Host Publisher working together. Additional resources are provided for specific instructions on each task. Copyright IBM Corp All rights reserved. 247

262 7.1 Integration example Andy and Ben s Boat Trader is a large boat broker. Ben wants to see the business double in size within two years. To reach this goal, new staff needs to be hired and users need remote access to system resources. Andy and Ben realize their applications all run on traditional green screens. Training new staff members on traditional green screens is expensive and time consuming. Ben and Andy agree that new employees should focus on selling and buying boats, not learning OS/400 commands. The salespeople currently have Internet access, which is mostly used to check sports scores and . Andy and Ben s Boat Trader currently maintains several databases with customer and boat information. Andy has also developed a complex boat customizing application used for special boat purchases. Ben and Andy decide to implement iseries Access for Web and Host Publisher. They follow a general outline: 1. Using Host Publisher, convert the complex boat customizing application. 2. Using iseries Access for Web, create SQL queries and database transfers. 3. Create a home page, linking Host Publisher and iseries Access for Web functions. Figure 7-1 demonstrates a sample home page with links to Host Publisher applications and iseries Access for Web functions. Figure 7-1 iseries Access for Web and Host Publisher Home Page Figure 7-2 explains the home page link functions. 248 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

263 Figure 7-2 iseries Access for Web and Host Publisher links For more information, see the following sections: SQL Query (3.2.7, Database on page 35) URL: Transfer some data to DB2 UDB for iseries database (3.2.7, Database on page 35) URL: Host Publisher V4.0 Application Link (Chapter 6, Using Host Publisher Studio to develop J2EE applications on page 141) URL: iseries Access for Web Messages (3.2.4, Messages on page 34) URL: iseries Access for Web Change Password (3.2.11, Other on page 46) URL: Where to find more information For more information on iseries Access for Web and Host Publisher, see: iseries Access for Web, SC IBM WebSphere Host Publisher Planning and Installation Guide, SC IBM WebSphere Host Publisher Administration and Users Guide, GC HTTP Server Webmaster s Guide V4R5, GC Chapter 7. iseries Access for Web and Host Publisher integration 249

264 250 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

265 8 Chapter 8. A comparison of Web-to-host integration tools This chapter provides a short overview and comparison of other products that are available for bringing iseries host applications to the Web. It also outlines the packaging options for the various software products. Copyright IBM Corp All rights reserved. 251

266 8.1 Overview of the Web-to-host solutions IBM offers a rich choice of Web-to-host solutions. Each product has its specific characteristics and possibilities. The products are available from different packages. Each package is composed of several products and has at least one or more Web-to-host products. Depending on your needs, you can choose more than one package. Four packages are available. The following list mentions only the Web-to-host products: Host Access Client package WebSphere Host On-Demand Version 6.0 Screen Customizer Version WebSphere Development Studio WebFacing Tool iseries Access Family iseries Access for Web Version 5.2 WebSphere Host Publisher Version 4.0 WebSphere Host Integration Solution WebSphere Host On-Demand Version 6.0 Screen Customizer Version WebSphere Host Publisher Version Host Access Client Package for iseries Version 2.0 IBM Host Access Client Package for iseries Version 2.0 bundles the following products: IBM Personal Communications for Windows Version 5.5 and IBM Personal Communications for OS/2 Version WebSphere Host-On-Demand Version 6.0 IBM Screen Customizer Version For a complete overview of the Host Access Client Package, see: IBM Personal Communications for Windows Version 5.5 IBM Personal Communications for Windows Version 5.5 and IBM Personal Communications for OS/2 Version make up a host communication and terminal emulation package that features 5250, 3270, and VT emulation; SNA application support and integration; SNA; and TCP/IP connectivity. IBM Personal Communications for Windows enables access to applications and data residing on host systems. This emulator contains comprehensive tools that simplify connectivity and access to host data over the majority of connection protocols. It is designed as a full function emulator and does not have Web browser capability. Personal Communications supports Host Access Beans for Java, VB automation objects, and VBScript. It supports Secure Sockets Layer (SSL) Version iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

267 8.2.2 WebSphere Host On-Demand Version 6.0 WebSphere Host On-Demand Version V6.0 gives Web users access to host programs through a Web browser. Browser access to host systems is provided through the use of Java applets downloaded into the client Web browsers, although the applets can also be installed as stand-alone clients. For 5250, 3270, and VT emulation, an applet running in the Web browser Java runtime environment establishes a connection with a Telnet server that manages access to host applications. The user interface is identical to the host terminal, so the traditional green screen is displayed. In addition, icons for PF keys copy/paste, macro recording, file transfer, and other basic operations are provided. Through the use of componentization, Host On-Demand could implement smart caching. This is the ability to cache and upgrade individual components of the client, even components that were not included in the initial loading of the client. A side benefit is the ability to create a smaller client footprint for network distribution. This includes only basic functionality for downloading to the workstation and incrementally adding only those functions that the user actually uses rather than all the functions that the user may use. Database On-Demand is a Java applet that allows users to perform Structured Query Language (SQL) requests to the iseries database through a JDBC driver. Database On-Demand is shipped with a JDBC driver Administration of a Host On-Demand server is done primarily through the administration applet, HODAdmin.html, which is loaded into your browser. The Service Manager component of Host On-Demand controls the following Host On-Demand functions: User/Groups management (Configuration services) Services management Redirector Service management Directory Service management OS/400 Proxy Server management Licenses management The Host Access Toolkit contains a set of Java libraries with which developers can create applets and applications for host access. The set of application programming interfaces (APIs) is a separate stand-alone product from Host On-Demand. It is bundled with Host On-Demand and is part in the Host Access Client Package. It is shipped on its own CD and can be installed and deployed independently of Host On-Demand. IBM WebSphere Host On-Demand is multilingual and available in 21 languages, including double-byte character set. Using Secure Sockets Layer (SSL) Version 3.0, IBM WebSphere Host On-Demand extends host data access across intranets, extranets, and the Internet with added security. The enhancements in Host On-Demand Version 6.0 include: More flexibility and control over locally stored user preferences: You can define centrally stored session-configuration preferences while allowing users to maintain individual preferences. Users can run sessions using the default configuration you define, and users can further modify sessions according to personal preference. Deployment Wizard enhancements: The Deployment Wizard helps you create HTML pages more easily to give users better host access. This helps you determine a deployment strategy for your users. In addition, new configuration models have been added to specify how Host On-Demand sessions are defined and managed. Chapter 8. A comparison of Web-to-host integration tools 253

268 Native Windows print support: Windows users can print using the standard printer drivers. Users can use their default Windows printers without additional configuration, and they can change properties without closing their host printer sessions. Integrated Windows domain logon: If this function is enabled, users are not required to log on to the Host On-Demand server to access their configuration data. Host On-Demand retrieves the Windows domain user ID, which becomes the Host On-Demand user name. If a user is already defined on the server, the configuration data for that user is accessed. Otherwise, new users are automatically created with group default settings. Customizable toolbar: Administrators and users can customize the toolbar buttons used for Host On-Demand sessions. Users can add and edit toolbar buttons to launch an applet, run an application, go to a URL, run a macro, or perform a menu function. After customizing the toolbar, settings are saved for future sessions. Cached client support across the Internet: Host On-Demand keeps the cached components at a consistent level and prevents users from installing different and potentially conflicting versions of components from different servers. Clients can communicate with servers running different levels of Host On-Demand. Support for Java 2-enabled browsers: Clients are supported on Java 2-enabled Web browsers, such as Netscape 6.x and Mozilla. The Java 2 plug-in with Netscape 4.x and Microsoft Internet Explorer is also supported. JVM 1.3 support on server: Host On-Demand support JVM 1.3 on the server Problem determination enhancements Refer to the following Web site for more information about Host On-Demand: IBM Screen Customizer Version IBM Screen Customizer V is the component of Host Access Client Package V2 that provides the ability to present host screens as a graphical user interface when used with Host On-Demand. To install Screen Customizer Version , IBM WebSphere Host On-Demand Version 6.0 must already be installed. IBM Screen Customizer V is deployed as an applet to be used with the Host On-Demand client. Once enabled in the session configuration parameters, Screen Customizer displays all screens in a graphical fashion. It interprets the host data stream and then provides either a default graphical representation of the host screen or a customized graphical representation of the host screen that was created by means of the Screen Customizer Studio. In Screen Customizer, applications are captured screen by screen and then customized to become graphical user interfaces. The Screen Customizer Administrator examines every screen it encounters and collects the number, length, and relative position of fields on the screen and stores this information, along with the screen ID assigned by the administrator, in a database. This screen ID is referred to as a screen map. At runtime, Screen Customizer again collects the screen information and uses it to search the database to determine if the screen has been customized. If a match is found, the screen ID is extracted from the database and is used to request the associated screen map from the Web server. The Web server returns the screen map, which Screen Customizer uses to build and display the customized screen in place of the default character-based user interface screen. If a screen ID is not found, the default graphical representation is shown. 254 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

269 Screen Customizer has three individual components, each with a specific function, all of which are Java applets: Administrator This applet is used to capture host screens and assign them IDs. It is also used to set global defaults for screen fonts, colors, button styles, and other attributes, and saves the defaults in a profile. The Administrator requires a live host session. Therefore, it requires Host On-Demand to provide the Telnet session. Customization Studio This applet allows you to create customized versions, called maps, of the host screens captured by the Administrator component. No programming is involved. Customization does not require a host connection, so it could be done by people working offline. Runtime Client You can download runtime from a Web server and the Host On-Demand applet or installed locally on a client workstation. When the data stream is received by Host On-Demand, control is passed to Screen Customizer. It uses its screen definition database to determine whether to present the default graphical interface or the customized version of the screen sent by the host. If a screen ID is found in the database for the screen, the map is downloaded from the Web server and the graphical representation is rendered. If a screen ID is not found, the default graphical interface is rendered. The Screen Customizer development cycle can be summarized in five basic steps: 1. Administration: Screens within an application are identified and saved as Screen Customizer maps. 2. Screen customization: The screen acquires a new look. 3. Template development: This can take place in parallel with screen customization or later. Templates allow the developer to provide a more uniform look and feel for all screens in an application (even screens that are not customized) without working on individual screens. 4. Testing: Once the application is built, it should be moved to a stand-alone client or a test server where the application can be exercised to ensure it is fully functional. 5. Deployment: Once tested, the application can be moved to a production server or servers. The enhancements for Screen Customizer Version include: An SSL indicator (formerly only for Host On-demand users) OS/400 subfiles and table support. The addition of an API that allows a Java programmer to interact with Screen Customizer host sessions and objects within those sessions. This allows a custom-written Java applet or application to dynamically change values, settings, or the appearance of the current Screen Customizer application. Support for Host On-Demand Version 6.0: Screen Customizer Version does not support earlier versions of Host On-Demand. Netscape 6.0 support for Screen Customizer Version (Java 2) is available with Screen Customizer/LE. It is also referred to as the default graphical interface. The Customization Studio, Administrator, Screen Customizer Component Interface (SCCI), and Screen Customizer Beans are only supported in a Java Virtual Machine environment. Support for Java 2-enabled browsers. Chapter 8. A comparison of Web-to-host integration tools 255

270 For more information about Screen Customizer, refer to: WebSphere Development Studio WebSphere Development Studio is an application development package that includes host components and workstation components. This package, WebSphere Development Studio for iseries V5R2 (5722-WDS), WebSphere Development Studio for iseries V5R1 (5722-WDS), or WebSphere Development Studio for iseries V4R5 (5769-WDS), consolidates all the key iseries development tools both host and workstation into one iseries offering. The following components are included in WebSphere Development Studio for iseries Host components The following host components are included in WebSphere Development Studio for iseries: ILE RPG (RPG IV) The major enhancements to RPG IV are easier interfacing with Java, new built-in functions, free form calculation specifications, control of which file is opened, qualified subfield names, and enhanced error handling. ILE COBOL Java interoperability support and mainframe portability support. ILE C The C compiler is a high-performance, high-function compiler for C development on the iseries platform. ILE C++ C++ provides additional features to those found in the C language. Application Development Toolset (ADTS) The tool suite consists of a base set of ten utilities for creating and maintaining applications and two additional features for controlling the development environment Workstation components The following workstation components are included in WebSphere Development Studio for iseries: WebFacing Tool (First Edition) Helps build Web interfaces to existing 5250 applications See the detailed discussion in 8.3.4, WebFacing Tool on page 257 WebSphere Studio, Professional Edition Provides easy access to iseries data and applications Contains Web palette parts to generate standard HTML and Java Script Includes a wizard to generate a functional Web user interface VisualAge for Java, Professional Edition Provides easy access to iseries server functions Generates code to access data and applications 256 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

271 CoOperative Development Environment (CODE) Windows-based versions of the classic host tools SEU, SDA, RLU PDM and the system debugger More efficient development of OPM/ILE RPG, OPM/ILE COBOL, OPM/ILE CL, ILE C, ILE C++, database description specifications (DDS), and Java VisualAge RPG Creates GUI applications for Windows or any Java, GUI-capable client or browser Provides seamless access to iseries data and applications For more information on WebSphere Development Studio for iseries, see: For the comparison of Web-to-host products, we take a closer look at WebFacing Tool in 8.3.4, WebFacing Tool on page WebSphere Studio Professional Edition WebFacing Tool WebSphere Studio Professional Edition is a tool set for creating, managing, and debugging multiplatform Web applications. The tool supports the visual layout of dynamic Web pages and supports JSP 1.1, Servlets 2.2, HTML, JavaScript, and DHTML. WebSphere Studio Professional Edition Version 4.0 provides wizards to create database applications and queries (without Java coding), creating JavaBeans servlets. It has additional built-in integrated tools for Visual Applet creation, GIF animation, and image creation. Other important features are the workbench environment for team-enabled site creation and management integration with VisualAge for Java. For more information on WebSphere Studio Professional Edition, refer to the Web site: The WebFacing Tool is a feature of the IBM WebSphere Development Tools for iseries (WDT/400) product and IBM WebSphere Development Studio for iseries. You cannot order WebFacing Tool as a separate product. The WebFacing Tool converts existing 5250 interfaces to browser-based graphical user interfaces, allowing users to access your applications with a Web browser. The WebFacing Tool produces standard Java artifacts (Servlets, JSPs, and JavaBeans) that can be customized with WebSphere Development Studio or with Visual Age for Java. With little or no modification to your original iseries applications, you can extend the use of your programs to the Internet or an intranet. When the converted application is launched from a browser, the WebFacing Server is called, and read and writes to the DSPF are redirected to the WebFacing servlet terminal users can still use the unconverted version of the application. The WebFacing Tool wizard guides you through the conversion of existing 5250 interfaces to browser-based graphical user interfaces. The user-friendly wizards guide you through the following steps: 1. Define the WebFacing project. 2. Select the display file source members to convert. 3. Specify the CL commands to invoke your application. Chapter 8. A comparison of Web-to-host integration tools 257

272 4. Choose a Web style for the look and feel of your pages. 5. Finish the project and convert your DDS sources. You can customize JSPs in different ways: Use CODE/400 to adapt the DDS source, and than reconvert the JSPs. Use WebSphere Studio or VisualAge for Java to modify the JSPs after the initial conversion. After a WebFacing project is created and converted with the WebFacing Tool, you must deploy it to a WebSphere Application Server before you can run the application. To deploy and run your Web applications, ensure the required server software is installed and configured on the host machine: OS/400 V4R5 or later WebSphere Application Server WebSphere Application Server (V3.5 with V3.5.2 fix pack applied). Either the Standard or Advanced versions of WebSphere Application Server can be used. WebSphere Application Server 4.0 (Advanced Edition, or Advanced Single Server Edition). IBM HTTP Server or IBM HTTP Server (powered by Apache) Enable file sharing via NetServer so that your Web application contents can be moved to the host machine The iseries server must also satisfy the hardware requirements for running WebSphere Application Server applications. Detailed information on performance is provided on the WebSphere Application Server site (click Performance): Enhancements with the version 5 Release 2 announcements include: Improved and expanded DDS keyword support Integration to the IDE workbench Improved Web look-and-feel Improved stability 8.4 iseries Access Family The iseries Access Family is a product designed for customers accessing iseries and AS/400 servers. The focus of Series Access is to bring all the power of the iseries and AS/400 to the end-user desktop and tightly integrate its software into the desktop environment on which it is running. The iseries Access Family contains the following products: iseries Access for Windows iseries Access for Wireless iseries Access for Web WebSphere Host Publisher For more information on iseries Access Family, refer to: iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

273 8.4.1 iseries Access for Windows iseries Access for Windows offers an all-inclusive client solution for accessing and using resources from your Windows desktop. iseries Access for Windows delivers TCP/IP connectivity to users running Microsoft Windows 95, Windows 98, Windows Me, Windows NT4.0, and Windows It includes 5250 emulation, access to DB2 Universal Database (UDB) for iseries through its Data Transfer, and uses AS/400 NetServer for working with the OS/400 integrated file system and printers. It also has a variety of middleware for using and developing client applications to access OS/400 resources. iseries Access for Windows delivers client/server application drivers for iseries (including Open Database Connectivity (ODBC) driver, OLE DB provider, and IBM Toolbox for Java) so users can run any client application to access resources on the iseries server. iseries Navigator is the OS/400 GUI, for administering iseries and AS/400e servers. It delivers a GUI for day-by-day operations of your single network of iseries servers. Examples are Work Management and managing Integrated xseries Servers for iseries. Other iseries functions shipped with the Express client are: EZ-setup: A set of wizards that guide you through the initial set up of a new iseries server Operations Console: Allows the PC to be used as the system console and to perform control panel functions iseries Access for Wireless iseries Access for Wireless is the integrated package of wireless functions and middleware. It contains an iseries Toolbox for Java Micro Edition to deliver tools for integration with WebSphere Transcoding Publisher and MQ Everyplace iseries Access for Web iseries Access for Web is explained throughout this redbook. You can find more information on the Web at: WebSphere Host Publisher For WebSphere Host Publisher, refer to the previous chapters in this redbook. You can find the latest information on the Web at: WebSphere Host Integration Solution WebSphere Host Integration Solution includes following product portfolio: IBM WebSphere Host On-Demand IBM Screen Customizer IBM WebSphere Host Publisher IBM WebSphere Application Server IBM WebSphere Studio Chapter 8. A comparison of Web-to-host integration tools 259

274 IBM Personal Communications IBM Communications Server You can find further information about WebSphere Application server and IBM Communications Server at the following Web sites: Comparison IBM offers a complete portfolio of products to assist in bringing your 5250 applications to the Web. Each has its own characteristics. The following sections summarize the most important characteristics of the different Web-to-host products. Your final choice of product (or products) can be influenced by many factors. The criteria for selection can include the availability of sources, knowledge of the application, experience with WebSphere Application Server, frequency of use, user s experience with the application, license costs, and required hardware platforms WebSphere Host Publisher V4.0 WebSphere Host Publisher V4.0 offers the following features: Is delivered as a part of iseries Access Family or via the WebSphere Host Integration Solution. Needs WebSphere Application Server Version (Advanced Edition or Advanced Single Server Edition) to run Host Publisher Applications. Host Publisher applications reside on the server and are deployed to the WebSphere Application Server. Host Publisher application maintenance is done with Host Publisher Studio. The data source can be a 5250 (3270 or VT) screen or a database with a JDBC interface. The license agreement for iseries Access for Web s Host Publisher states that users are not authorized to use the 3270 or VT functions of Host Publisher. OS/400 screens and application screens can be integrated into the application. You can give selective access to the application by converting only some of the application screens (can reduce application s complexity). You can combine different applications into a single Web application. Creates Integration Objects and reusable JavaBeans and JSPs. Output data from one Integration Object can be input for another Integration Object. XML Gateway is available. You do not need to change the source code of a 5250 program. Application knowledge is required Can be used on multiple platforms. Organizations that need Web-to-host access and have WebSphere skills, application knowledge, and development skills can use Host Publisher to gradually adapt their applications to real Web-to-host applications. 260 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

275 8.6.2 WebFacing WebFacing supports the following features: Part of WebSphere Development Tools for iseries. Runtime requires WebSphere Application Server Version 3.5 (Standard or Advanced Edition) or WebSphere Application Server Version 4.0 (Advanced Edition or Advanced Single Server Edition). Data source is a 5250 screen. One-for-one conversion of application screens. The user sees all the application screens. You need DDS sources to convert Display DDS source into JSPs and JavaBeans. The user interface can be customized, so you can create your own style sheets or use tools to customize it. Fast path to globally convert applications to run in a browser. No need to change the 5250 program. No code installation or maintenance on the client. Runs only on the iseries server. WebFacing Tool allows a quick conversion of a complete application to Web-to-host access. Application skills and WebSphere skills are required. The converted application can be the base for further Web-to-host application development Host On-Demand The WebSphere Host On-Demand features includes: Part of Host Access Client Package and WebSphere Host Integration solution. Access to the host system is through the use of Java applets. They are downloaded into the client Web browser and can be installed on the client. Data source is a 5250 screen or a database with a JDBC interface. Connects directly to any 5250 (or 3270, VT) Telnet server. Installs on a server for centralized management and deployment. Use the browser for administration. Provides Native Windows print support and 5250 host (HPT) printing. No need to change the 5250 program. Can be installed on different platforms. For organizations with iseries servers and traditional 5250 applications, IBM WebSphere Host On-Demand can provide Web-to-host access that is very close to the 5250 access (both for display and printer functions). Database access, central installation, and maintenance are the advantages. IBM WebSphere Host On-Demand also provides a solution for Web-to-host access for other platforms Screen Customizer The highlights of Screen Customizer include: Part of Host Access Client Package and WebSphere Host Integration solution. Is deployed as an applet to be used with Host On-Demand V 6.0 which a prerequisite. Chapter 8. A comparison of Web-to-host integration tools 261

276 Can provide a face-lift to applications, so that the interface is a real graphical interface comparable to a typical Web application. Does not require source code for conversion. Is multiplatform. In addition to WebSphere Host On-Demand, Screen Customizer optimizes the look-and-feel of the application iseries Access for Web iseries Access for Web Version 5.2 supports the following features: Is part of the iseries Access Family. Includes a set of servlets that run on the iseries Java Virtual Machine (JVM) and generate HTML output to a browser. Installation and maintenance is on the iseries server. There is no code to install or maintenance on the client. Requires OS/400 V5R1 or higher. Runs with Apache Software Foundation (ASF) Tomcat Application Server or Websphere Application Server Version 4.0 (Advanced Edition or Advanced Single Server Edition). May be configured for more than one WebSphere Administrative Server. Integration with functions. Access to the database (local or remote) and IFS. Integrated PDF support for database and printer output. Includes a 5250 session. No need to have source or to change programs. Web-based facilities for administering and customization of user access. Runs only on iseries. Some organizations need quick Web-to-host access to iseries applications and resources. These may includes the IFS, database, basic operational functions, some level of integration with functions, and programming skills or WebSphere skills. iseries Access for Web can be a good solution in these cases Putting it all together Table 8-1 summarizes all the elements of the products together. Table 8-1 Summary of all the products together Feature iseries Access for Web V5.2 WebSphere Host Publisher V4.0 WebFacing V 5.2 WebSphere Host On-Demand V6.0 Screen Customizer V OS/400 release V5R1 or higher V4R5 or higher V4R5 or higher V4R5 or higher V4R5 or higher Client HTML browser HTML browser Java Script enabled browser Java-enabled browser Requires Host On-Demand 262 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

277 Feature iseries Access for Web V5.2 WebSphere Host Publisher V4.0 WebFacing V 5.2 WebSphere Host On-Demand V6.0 Screen Customizer V Communication protocol HTTP HTTP HTTP TN5250 TN5250 Web Application Server requirement WebSphere Application Server 4.0 or ASF Tomcat WebSphere Application Server 4.0 WebSphere Application Server 3.5 and 4.0 Development effort required Customizable GUI IFS file upload/download SQL based database access No Yes Yes No Yes Yes Yes Yes Minimal Yes Yes No No No No Yes Yes No Yes No Printer emulation No (can print from a spooled file) No No Native windows print support/ 5250 print (HPT) yes No Interactive 5250 sessions (2) Yes Yes Yes Yes Yes Browsers/ desktop supported Netscape 4.7 (Windows, AIX, Linux) and 6.1 (Windows) Internet Explorer 5.0, 5.1, and 6.0 (Windows) Opera 5.11 (windows) and 5.0 (Linux) Netscape 4.7 (Windows, AIX, Linux) and 6.1 (Windows) Internet Explorer 5.0, 5.1, and 6.0 (Windows) Opera 5.11 (windows) and 5.0 (Linux) Internet Explorer 5.0, 5.1, and 6.0 (Windows) Netscape 4.7 (Windows, AIX, Linux) and 6.1 (Windows) Internet Explorer 5.0, 5.1, and 6.0 (Windows) Opera 5.11 (windows) and 5.0 (Linux) Netscape 4.6, 4.7 and 6.0 (Windows, 95/98/NT, UNIX) and (OS/2, Mozilla for Web browser for OS/2) Internet Explorer 4.01, 5.0, 5.1, 6.0 (Windows) Security SSL SSL SSL SSL SSL Access to multiple systems Yes Yes (1) No (only if defined by application) Yes Yes Runs on multiple platforms No Yes (1) No Yes Yes Licensing Server runtime license Server runtime license Server runtime license Client runtime license Client runtime license Notes: 1. The Host Publisher Server Version 4.0 delivered with the iseries Access Family is only licensed to run on iseries and to access iseries resources (no 3270 or VT). 2. Interactive 5250 session means that the Web-to-host application behaves as an interactive 5250 session. Chapter 8. A comparison of Web-to-host integration tools 263

278 264 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

279 A Appendix A. Configuring the Domino HTTP Server for iseries Access for Web This appendix explains how to configure a WebSphere Application Server 4.0 instance to use a Domino HTTP server. You can use Lotus Domino for iseries Version (or later) HTTP server as a Web server with WebSphere Application Server Version 4.0. An HTTP server instance is not required to install WebSphere. However, it is required to support requests for servlets and JavaServer Pages resources managed by WebSphere Application Server. It is also needed if you plan to use Secure Sockets Layer (SSL) protocol. To configure the Lotus Domino HTTP server for use with WebSphere Application Server, you must update the Domino server's configuration. To configure each instance of a Domino server on your iseries server, follow these steps: 1. Update the Domino server document to work with WebSphere Application Server. 2. Update the Domino server s notes.ini file to work with WebSphere Application Server. 3. Restart the Domino server s HTTP task to apply the changes to the server document and the notes.ini file. Copyright IBM Corp All rights reserved. 265

280 Updating the Domino Server Document To update the Domino server document to work with WebSphere Application Server, follow these steps: 1. From a Lotus Notes client connected to the appropriate Domino server, edit the Domino document, found in the Domino server's Domino Directory (names.nsf). 2. Within the server document, click the Internet Protocols tab and then click the HTTP tab. 3. Enter the following information in the DSAPI filter file names field: /QSYS.LIB/QEJBADV4.LIB/DOMINOH.SRVPGM 4. Save and exit the Domino server document. Updating the Domino server s notes.ini file To update the Domino server's notes.ini file to work with WebSphere Application Server, follow these steps: 1. Enter the Work with Domino Servers (WRKDOMSVR) command on the OS/400 command line. 2. For the appropriate Domino server instance, specify option 13 (Edit NOTES.INI) to edit the server's notes.ini file. 3. Add the following line to the end of the notes.ini file: WebSphereInit=/qibm/userdata/webasadv4/default/config/plugin-cfg.xml Note: This line is for the WebSphere Application Server's default instance. For a non-default instance, change the line to reference the directory of the application server instance. 4. Press F3 twice to save and exit the notes.ini file. Restarting the Domino server s HTTP task After you update the Domino server document and the server's notes.ini file, you must restart the Domino server's HTTP task for those changes to take effect. To restart the Domino server's HTTP task, follow these steps: 1. Enter the Work with Domino Servers (WRKDOMSVR) command on the OS/400 command line. 2. For your Domino server instance, specify option 8 (Work console) to select the Domino server's console. 3. From the Domino server's console, enter the following command to restart the Domino server's HTTP task: tell http restart 266 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

281 B Appendix B. Additional information on Host Publisher This appendix provides additional information on Host Publisher. It includes: Examples of the HPInstall.log Overview of the configuration parameters Host Publisher version information Host Publisher documentation Copyright IBM Corp All rights reserved. 267

282 Host Publisher installation log After the install command is completed, you can verify the result in QIBM/ProdData/HostPublisher/Install/HPInstall.log. This log is shown in Example 8-1. Example 8-1 HPInstall.log after installation >>> Wed Apr 17 14:39:03 UTC parameters: -install -i /home/hp40/hpinst JT400: System Name = localhost OS400 = V5R1M0 Local JVM = true USRPRF = QSECOFR SPCAUT: *ALLOBJ *SECADM *JOBCTL *SPLCTL *SAVSYS *SERVICE *AUDIT *IOSYSCFG Job ccsid=37 Job ccsid encoding=cp037 DSPSYSVAL: QMODEL (hardware model) = 270 QPRCFEAT (processor) = 23F5 QCNTRYID = US QLANGID = ENU QCCSID = QCHRID: QIGC (DBCS) = 0 JVM: java.version = java.vendor = IBM Corporation os.name = OS/400 os.version = V5R1M0 java.class.path = /home/hp40/hpinst:/home/hp40/hpinst/os400/hpos4in.jar:/qibm/proddata/java400/jt400ntv.jar:/ QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar language = en country = US Product=5648D31, version=v2r1m0, option=0000 is not installed Product=5648D31, version=v2r2m0, option=0000 is not installed Product=5648D31, version=v2r2m1, option=0000 is not installed Product=5648D31, version=v3r5m0, option=0000 is not installed Product=5648E25, version=v3r5m0, option=0000 is not installed Product=5724B81, version=v4r0m0, option=0000 is not installed Product=5733WA4, version=v4r0m0, option=0000 is installed Product=5733WS4, version=v4r0m0, option=0000 is not installed 268 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

283 Installing Host Publisher Server. Please wait. Copying stream file to save file. -> qsys/cpyfrmstmf fromstmf('/home/rblocher/hpinst/os400/qhp00mm.sav') tombr('/qsys.lib/qhpnmrm.file') mbropt(*replace) CPCA081 Stream file copied to object. Restoring licensed program. -> qsys/rstlicpgm licpgm(5724b81) dev(*savf) savf(qsys/qhpnmrm) rstobj(*pgm) CPC3DC8 *PGM objects for product 5724B81 option *BASE release *FIRST restored. -> qsys/dltf file(qsys/qhpnmrm) CPC2191 Object QHPNMRM in QSYS type *FILE deleted. Installation completed successfully. After completion of the cfghpsvr command, you can verify the HPInstall log again, which is partially shown in Example 8-2. Example 8-2 HPInstallog after cfghpsvr >>> Wed Apr 17 14:59:23 UTC parameters: -config -was ADV4 -instance default JT400: System Name = localhost OS400 = V5R1M0 Local JVM = true USRPRF = QSECOFR SPCAUT: *ALLOBJ *SECADM *JOBCTL *SPLCTL *SAVSYS *SERVICE *AUDIT *IOSYSCFG Job ccsid=37 Job ccsid encoding=cp037 DSPSYSVAL: QMODEL (hardware model) = 270 QPRCFEAT (processor) = 23F5 QCNTRYID = US QLANGID = ENU QCCSID = QCHRID: QIGC (DBCS) = 0 JVM: java.version = java.vendor = IBM Corporation os.name = OS/400 os.version = V5R1M0 java.class.path = /QIBM/ProdData/HostPublisher:/QIBM/ProdData/HostPublisher/Install/HPOS4IN.JAR:/QIBM/ProdDat a/java400/jt400ntv.jar:/qibm/proddata/http/public/jt400/lib/jt400.jar language = en country = US Appendix B. Additional information on Host Publisher 269

284 Product=5648D31, version=v2r1m0, option=0000 is not installed Product=5648D31, version=v2r2m0, option=0000 is not installed Product=5648D31, version=v2r2m1, option=0000 is not installed Product=5648D31, version=v3r5m0, option=0000 is not installed Product=5648E25, version=v3r5m0, option=0000 is not installed Product=5724B81, version=v4r0m0, option=0000 is installed Product=5733WA4, version=v4r0m0, option=0000 is installed Product=5733WS4, version=v4r0m0, option=0000 is not installed Host Publisher will be configured with WebSphere Application Server Advanced Edition -> qsys/alcobj obj((qejbadv4/qejbadv4 *SBSD *EXCL)) WAIT(2) SCOPE(*JOB) CPF1002 Cannot allocate object QEJBADV4. -> qsys/crtautl autl(qhpnpautl) aut(*use) CPF2278 Authorization list QHPNPAUTL already exists. -> qsys/addautle autl(qhpnpautl) user(qejbsvr) aut(*use) CPD2272 User QEJBSVR already on list QHPNPAUTL. CPF errors adding users, 1 authorization lists processed. -> qsys/chgobjown obj(qsys/qhpnpautl) objtype(*autl) newown(qsys) curownaut(*revoke) CPC2206 Ownership of object QHPNPAUTL in QSYS type *AUTL changed. acc: Recurse '/QIBM/ProdData/HostPublisher' and all its subdirectories while running command 'qsys/chgaut obj(''{0}/*'') autl(qhpnpautl)' at each result node. acc: Scanning for the directory tree from node /QIBM/ProdData/HostPublisher, please wait... acc: About to operate on directory tree with 64 nodes... 0: /QIBM/ProdData/HostPublisher 1: /QIBM/ProdData/HostPublisher/Install 2: /QIBM/ProdData/HostPublisher/SDK 3: /QIBM/ProdData/HostPublisher/SDK/Bidi 4: /QIBM/ProdData/HostPublisher/SDK/XLGW 5: /QIBM/ProdData/HostPublisher/SDK/XLGW/Servlet 6: /QIBM/ProdData/HostPublisher/SDK/XLGW/Servlet/xmlLegacyGatewayServletSample 7: /QIBM/ProdData/HostPublisher/SDK/XLGW/xmlAppData 8: /QIBM/ProdData/HostPublisher/SDK/XLGW/xmlAppData/images 9: /QIBM/ProdData/HostPublisher/SDK/XLGW/HostConnection > QSYS/CHGOWN OBJ('/QIBM/ProdData/HostPublisher/AEOS400AppRestore') NEWOWN(QSYS) RVKOLDAUT(*YES) CPC221B Object changed. -> QSYS/ADDENVVAR ENVVAR('QIBM_MULTI_THREADED') VALUE('Y') CPCA980 Environment variable added. -> QSYS/QSH CMD('rm -f /QIBM/ProdData/HostPublisher/Install/config.out;touch -C 37 /QIBM/ProdData/HostPublisher/Install/config.out') QSH0005 Command ended normally with exit status 0. -> QSYS/CHGAUT OBJ('/QIBM/ProdData/HostPublisher/Install/config.out') USER(*PUBLIC) DTAAUT(*RX) OBJAUT(*NONE) CPC221B Object changed. -> QSYS/CHGAUT OBJ('/QIBM/ProdData/HostPublisher/Install/config.out') AUTL(QHPNPAUTL) CPC221B Object changed. -> QSYS/CHGOWN OBJ('/QIBM/ProdData/HostPublisher/Install/config.out') NEWOWN(QSYS) RVKOLDAUT(*YES) CPC221B Object changed. -> QSYS/QSH CMD('/QIBM/ProdData/HostPublisher/AEOS400Deploy >/QIBM/ProdData/HostPublisher/Install/config.out 2>&1') QSH0005 Command ended normally with exit status 0. -> QSYS/CHGAUT OBJ('/QIBM/UserData/HostPublisher/Server/Migration/AppMigrator') USER(*PUBLIC) DTAAUT(*RX) OBJAUT(*NONE) CPC221B Object changed. -> QSYS/CHGAUT OBJ('/QIBM/UserData/HostPublisher/Server/Migration/AppMigrator') AUTL(QHPNPAUTL) CPC221B Object changed. 270 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

285 -> QSYS/CHGOWN OBJ('/QIBM/UserData/HostPublisher/Server/Migration/AppMigrator') NEWOWN(QSYS) RVKOLDAUT(*YES) CPC221B Object changed. -> qsys/cpy obj('/qibm/userdata/hostpublisher/server/server.properties') toobj('/qibm/userdata/hostpublisher/server/server.properties.4.bak') SYMLNK(*NO) FROMCODPAG(*OBJ) TOCODEPAGE(*OBJ) DTAFMT(*BINARY) CPCA087 Object copied. -> QSYS/CHGAUT OBJ('/QIBM/ProdData/HostPublisher/Install/install.properties') USER(*PUBLIC) DTAAUT(*RX) OBJAUT(*NONE) CPC221B Object changed. -> QSYS/CHGAUT OBJ('/QIBM/ProdData/HostPublisher/Install/install.properties') AUTL(QHPNPAUTL) CPC221B Object changed. -> QSYS/CHGOWN OBJ('/QIBM/ProdData/HostPublisher/Install/install.properties') NEWOWN(QSYS) RVKOLDAUT(*YES) CPC221B Object changed. Configuration completed successfully. Host Publisher configuration information Table B-1 offers a complete overview of the configuration parameters. It is obtained with the command. Table B-1 showcfg IBM WebSphere Web Container Configuration Servlet Specification Level 2.2 Supported Transports Name Properties Transport host: * Transport port: 9088 Transport mode: http Installed Web Modules HPAdmin.war HPDoc.war xmllegacygw.war WebSphere Application Server Version Information Product Name Product Edition IBM WebSphere Application Server AE Product Version Product Major Version 4 Product Minor Version 0 Product Service Level 2 Product Build Level a Product Build Date Tue Dec 18 00:00:00 UTC 2001 Appendix B. Additional information on Host Publisher 271

286 IBM WebSphere Web Container Configuration System Properties Property Value 0 Operating System Operating System Version Hardware Architecture OS/400 V5R1M0 PowerPC JVM Version JVM Vendor JVM Vendor URL IBM Corporation JVM Class Version 47.0 JVM Home Directory JVM Compiler (JIT) JVM Class Path /QIBM/ProdData/Java400/jdk13 jitc_de /QIBM/ProdData/WebASAdv4/lib/bootstrap.jar /QIBM/UserData/WebASAdv4/default/properties /QIBM/ProdData/WebASAdv4/properties File Separator / Path Separator : Line Separator 0 User Name User Home Directory Current Working Directory User Language User Region User Timezone File Encoding File Encoding Package os400.security.password.validation.list.object sun.boot.class.path QEJBSVR /home/qejbsvr/ /QIBM/UserData/WebASAdv4/default en US UTC ISO8859_1 sun.io /QSYS.LIB/QUSRSYS.LIB/EJSADMIN.VLDL /QIBM/ProdData/Java400/jdk13/lib/jdkptf13.zip:/ QIBM/ProdData/Java400/jdk13/lib/rt.jar:/QIBM/ ProdData/Java400/jdk13/lib/i18n.jar:/QIBM/ ProdData/Java400/jdk13/lib/sunrsasign.jar:/ QIBM/ProdData/OS400/Java400/ext/ IBMmisc.jar:/QIBM/ProdData/OS400/Java400/ ext/jssl.jar:/qibm/proddata/os400/java400/ext/ ibmjssl.jar:/qibm/proddata/java400/:/qibm/ ProdData/WebASAdv4/java/ext/ibmorb.jar os400.defineclass.optlevel iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

287 IBM WebSphere Web Container Configuration os400.security.password.encoding.algorithm java.vm.specification.vendor XOR Sun Microsystems Inc. os400.class.path.security.check 20 java.runtime.version com.ibm.ejs.wlm.bootstrapnode was.install.root b24 ASM03 /QIBM/ProdData/WebASAdv4 os400.debug 0 java.naming.factory.initial sun.boot.library.path java.use.policy com.ibm.corba.configurl com.ibm.websphere.naming.wsninitialcontextf actory /QSYS.LIB/QSYS2.LIB:/QSYS.LIB/QJAVA.LIB:/ QSYS.LIB:/QSYS.LIB/TSYS.LIB:/QSYS.LIB/ QSYS.LIB:/QSYS.LIB/QSYS2.LIB:/QSYS.LIB/ QHLPSYS.LIB:/QSYS.LIB/QUSRSYS.LIB:/ QSYS.LIB/TUSRSYS.LIB true file:///qibm/userdata/webasadv4/default/ properties/sas.server.props os400.class.path.tools 0 server.root jdbc.db2.cli.nojoblog sun.cpu.isalist java.specification.name os400.create.type /QIBM/UserData/WebASAdv4/default true PowerPC Java Platform API Specification interpret os400.verify.checks.disable java.vm.info build JDK-1.3, native threads, jitc_de os400.gc.heap.size.max java.awt.fonts 0 java.vm.version 1.3 os400.class.path.rawt 0 java.awt.printerjob sun.io.unicode.encoding awt.toolkit java.specification.vendor os400.stderr com.ibm.rawt2.ahost.java.awt.print. AHPrinterJob UnicodeBig com.ibm.rawt2.ahost.java.awt.ahtoolkit Sun Microsystems Inc. fileapp:/qibm/userdata/hostpublisher/log/ stderr.txt Appendix B. Additional information on Host Publisher 273

288 IBM WebSphere Web Container Configuration java.library.path /QSYS.LIB/QEJBADV4.LIB:/QSYS.LIB/ TEZCMDS.LIB:/QSYS.LIB/QGPL.LIB:/ QSYS.LIB/QTEMP.LIB: java.vm.vendor java.runtime.name os400.run.mode IBM Corporation Java 2 Runtime Environment, Standard Edition jitc_de os400.optimization 0 os400.stdio.convert ws.ext.dirs java.vm.specification.name N /QIBM/ProdData/WebASAdv4/java/tools:/QIBM/ ProdData/WebASAdv4/classes:/QIBM/ProdData /WebASAdv4/lib:/QIBM/ProdData/WebASAdv4/ lib/server:/qibm/userdata/webasadv4/default/ lib/ext Java Virtual Machine Specification java.vm.specification.version 1.0 sun.cpu.endian os400.boot.class.path java.io.tmpdir java.vendor.url.bug os400.stdout java.awt.graphicsenv big /QIBM/ProdData/Java400/jdk13/lib/jdkptf13.zip:/ QIBM/ProdData/Java400/jdk13/lib/rt.jar:/QIBM/ ProdData/Java400/jdk13/lib/i18n.jar:/QIBM/ ProdData/Java400/jdk13/lib/sunrsasign.jar:/ QIBM/ProdData/OS400/Java400/ext/ IBMmisc.jar:/QIBM/ProdData/OS400/Java400/ ext/jssl.jar:/qibm/proddata/os400/java400/ext/ ibmjssl.jar:/qibm/proddata/java400/:/qibm/ ProdData/WebASAdv4/java/ext/ibmorb.jar /tmp/ fileapp:/qibm/userdata/hostpublisher/log/ stdout.txt com.ibm.rawt2.ahost.java.awt. AHGraphicsEnvironment java.ext.dirs /QIBM/ProdData/WebASAdv4/java/ext:/QIBM/ ProdData/Java400/jdk13/lib/ext:/QIBM/UserData /Java400/ext was.install.library java.vm.name java.policy QEJBADV4 Classic VM /QIBM/ProdData/Java400/jdk13/lib/security/java. policy os400.gc.heap.size.init 2048 os400.stdin.allowed iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

289 IBM WebSphere Web Container Configuration java.specification.version 1.3 os400.jdk.provider sun Host Publisher version information The version information of Host Publisher Version 4.0 is also recorded in a product.xml file. You can find the file in /QIBM/ProdData/HostPublisher/server/product.xml as shown in Figure B-1. Figure B-1 Product.xml Host Publisher documentation After the installation, you can find all the documentation through the use of the HPDocServlet. Go to: See Figure B-2. Appendix B. Additional information on Host Publisher 275

290 Figure B-2 HPDocServlet Choose a language code (for instance, en for English), and the documentation index is presented. This is shown in Figure B-3. Figure B-3 Documentation index 276 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

291 C Appendix C. Language support This appendix provides a table that shows the national language versions available for: iseries Access for Web V5R2 IBM WebSphere Host Publisher V4.0 Table C-1 lists the supported locales for iseries Access for Web V5R2 and Host Publisher V4.0. The third column lists the additional languages supported with Host Publisher distributed with iseries. Table C-1 Supported locales iseries Access for Web V5R2 Chinese (Simplified) 2989 Chinese (Traditional) 2987 English 2924 French 2928 German 2929 Italian 2932 Japanese 2962 Korean 2986 Portuguese (Brazilian) 2908 Spanish 2931 Turkish 2956 Arabic 2954 Croatian 2912 Czech 2926 WebSphere Host Publisher V4.0 Chinese (Simplified) Chinese (Traditional) English French German Italian Japanese Korean Portuguese (Brazilian) Spanish Turkish Additional languages for WebSphere Host Publisher on iseries Arabic Croation Czech Copyright IBM Corp All rights reserved. 277

292 iseries Access for Web V5R2 Danish 2926 Dutch 2923 Dutch-Belgium 2963 English DBCS 2984 English uppercase 2950 English uppercase DBCS 2938 Finnish 2925 French Belgium 2966 French Canadian 2981 French MNCS 2940 German MNCS 2939 Greek 2957 Hungarian 2976 Italian MNCS 2942 Norwegian 2933 Polish 2978 Portuguese 2922 Portuguese MNCS 2996 Romanian 2992 Russian 2976 Slovakian 2994 Slovene 2911 Swedish 2937 WebSphere Host Publisher V4.0 Additional languages for WebSphere Host Publisher on iseries Danish Dutch Dutch Belgium English DBCS English uppercase English uppercase DBCS Finnish French Belgium use existing 2928 French Canadian use existing 2928 French MNCS use existing 2928 German MNCS use existing 2929 Hungarian Italian MNCS Norwegian Polish Portuguese Portuguese MNCS uses new 2922 Romanian Russian Slovakian Slovene Swedish 278 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

293 Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. IBM Redbooks Other resources For information on ordering these publications, see How to get IBM Redbooks on page 280. IBM Web-to-Host Integration Solutions, SG IBM WebSphere Host On-Demand: Version 5 Enhancements, SG IBM WebSphere V4.0 Advanced Edition Handbook, SG IBM Host Access Client Package, SG A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5, SG Web Services Wizardry with WebSphere Studio Application Developer, SG WebSphere Studio Application Developer and Web Services, SG WebSphere J2EE Application Development for the IBM eserver iseries Server, SG WebSphere 4.0 Installation and Configuration on the IBM eserver iseries Server, SG These publications are also relevant as further information sources: IBM WebSphere Host Publisher Administration and Users Guide, GC HTTP Server Webmaster s Guide V4R5, GC iseries Access for Web, SC Printer Device Programing, SC IBM WebSphere Host Publisher Planning and Installation Guide, SC The following documents are located online in the WebSphere Studio library folder: IBM WebSphere Host Publisher Messages Reference IBM WebSphere Host Publisher Programmer s Guide and Reference Referenced Web sites These Web sites are also relevant as further information sources: iseries Information Center IBM ~ iseries Support Copyright IBM Corp All rights reserved. 279

294 IBM WebSphere Application Server iseries Access for Web IBM HTTP Server IBM WebSphere Host Publisher Lotus Domino Support WebSphere Software Products Host Access Client Package for iseries Version WebSphere Host On-Demand Version IBM Screen Customizer Version WebSphere Development Studio for iseries WebSphere Development Studio Professional Edition IBM Communications server IBM Information Center for printer shares (under Printers and devices) How to get IBM Redbooks You can order hardcopy Redbooks, as well as view, download, or search for Redbooks at the following Web site: ibm.com/redbooks You can also download additional materials (code samples or diskette/cd-rom images) from that site. IBM Redbooks collections Redbooks are also available on CD-ROMs. Click the CD-ROMs button on the Redbooks Web site for information about all the CD-ROMs offered, as well as updates and formats. 280 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

295 Index Symbols.ear file 142 Numerics 5250 emulation environment interface 79 comparison with XML Gateway 80 configuration options 82 configuring 81 loading shipped defaults 82 saving active session settings 81 saving defaults 81 starting protocol shortcut 95 A About function 47 active function keys 86 Active session 35, 94 settings 81 stopping 95 additional PTFs 16 Administrator 255 ADTS (Application Development Toolset) 256 AFP viewer 31 Apache Software Foundation (ASF) Tomcat 13 Application Developer 6 Application Development Toolset (ADTS) 256 Application Integrator 5, 147, 183 application migration 136 AppMigrator 136 ASF Tomcat Application Server 16 Avoid duplicates for this user 84 Avoid duplicates with other users 84 B Browser dialog box 24 browser favorites 47 browsing files 43 C cached client support 254 CFGACCWEB2 (Configure iseries Access for Web) command 19 cfghpsvr command 269 chaining 5 Change password 46 checklist 18 Client Access Express 79 Client Access Express for Windows 259 client/server environment 3 cloning 100 code page 83, 155 value 83 Colors option 89 command name 45 command search 45 Command tab 44 Commercial Processing Workload (CPW) 12 composite applications 206 Configuration options 82 Configure iseries Access for Web (CFGACCWEB2) command 19 Configured sessions 35 configuring sessions 81 Connect Your Session wizard 161 connecting a macro 155 connecting a session 161 connection information 154 connection management 6 connection monitoring 127 Connection Name 177 connection pool 5, 46, 144 Connection Pool Configuration panel 153 Connection Timeout 177 connection values 177 CoOperative Development Environment (CODE) 257 Copy data to table 36 creating a loop 165 creating a new pool 153 Cryptographic feature 15 cumulative PTF package 16 cursor positioning 88, 94 customizable toolbar 254 Customization Studio 255 Customize 45 Group profiles 46 Preferences 46 Selected profile 46 User profiles 46 Customize tab 45 customizing lists 48 customizing My Folder 27 D data macro 163 data source 144 Database 35 Database Access 5 database connections 38 Native JDBC Driver 38 Toolbox JDBC Driver 40 database management 37 Database On-Demand 253 Copyright IBM Corp All rights reserved. 281

296 Database tab 35 database transfer 248 database URL 177 default connection pool 153 default properties 209 Deploy and RMIC Code 224 deploying the application 199 DHTML 257 digital certificates 22 Directory Service management 253 disconnecting the macro 170 Display messages 34 Display Terminal 132 domain logon 254 Domino HTTP Server 14, 18 Domino Server Document 266 DSAPI filter file names 266 E EJB (Enterprise JavaBeans) 6 EJB access beans EJB Integration Objects default properties 209 EJB support files 208 encoded text 24 Enterprise Archive (EAR) file 142 Enterprise JavaBeans 207 Enterprise JavaBeans (EJB) 6, 141, 207 Express Logon Enabled 155 EZ-setup 259 F file authorities 56 file sharing 44 Files tab 43 fixed-width font 85 full text PDF files 32 function key (Fxx=) 89 function key bar 88 function restrictions 47, 95 G GIF animation 257 green-screen environment 3 Group profiles 46 H helper classes 211 helper object 212 HODAdmin.html 253 home page example administrator view 66 customer view 61 homepage.html 25 Host Access 5 products 6 Host Access Client package 252 Host Access Toolkit 253 host and application server selection 125 Host On-Demand 261 Host Publisher connection pool 145 uninstalling the previous version 103 Host Publisher Administration Application 103 Host Publisher configuration information 271 Host Publisher Documentation application 103 Host Publisher installation log 268 Host Publisher Portlet 244 Host Publisher Server 5 6, 97 Host Publisher Server Administration 117, 124 monitoring connections 127 monitoring server status 126 problem determination 130 selecting host and application server 125 Host Publisher Server licensing 101 Host Publisher Studio 5, 97, 141 Application Integrator 141 Database Access 141 Host Access 141 migration utility 136 Host Publisher version information 275 Host Publisher XML Gateway Application 103 HPAdmin.ear 103 HPDoc.ear 103 HPDocServlet 275 HPInstall log 269 HTTPS 24 I IBM HTTP Server for iseries 13 HTTP Server (original) 14 HTTP Server (powered by Apache) 14 IBM Infoprint Server 32 IBM Personal Communications 7, 252 IBM Screen Customizer 254 IBM Toolbox for Java 259 IBM WebSphere Host On-Demand 7 IBM WebSphere Host Publisher 4 image creation 257 Import request 36 input fields 94 input variables 164 installation testing 116 Integration Object (IO) 5 Integration Object chaining 5, 151 Integration Objects 142, 144, 149 integration tools comparison 251 Internet 2 Internet Explorer 17 Internet printers IO (Integration Object) 5 IONameHelperObjectSuffix 212 IONamePropertiesObjectSuffix 212 iseries Access Family 3, 8, 252, 258 iseries Access for Web 11, 252, 259 adding functions as browser favorites 47 Command tab 44 Main Page 25 Messages tab iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

297 iseries Access for Windows 9, 259 iseries Access for Wireless 9, 259 iseries Client Access Express for Windows 9 iseries Client Access Family 9 iseries Navigator 9 iseries ODBC driver for Linux 9 iwaactivesessions 35 iwabrowsefiles 43 iwachangepassword 46, 249 iwacomand 44 iwacommandlist 44 iwacommandsearch 44 iwacustomize 46 iwacustomizelist?action=groups 46 iwacustomizelist?action=select 46 iwacustomizelist?action=users 46 iwadbrequests 36, 249 iwadbtables 36 iwadbupload 36 iwafileshares 44 iwahome 24 iwainfo 47 iwainternetprinters 31 iwajoblist?jobtype=server 35 iwajoblist?jobtype=user 35 iwamain 25 iwamessagequeues 34 iwamessages 34 iwamessages/qsys/qsysopr 34 iwamyfolder 26 iwaoutputqueues 32 iwaprinters 31 iwaprintershares 31 iwarunsql 36 iwasendmessage 34, 249 iwaspool 31 J J2EE 141 J2EE application support 6 Java 2-enabled browser 254 Java Virtual Machine (JVM) 3 JavaScript 257 JavaServer Pages (JSP) 6, 142, 183 JDBC 174 JDBC driver 175, 253 job logs 35 Jobs function 35 Jobs tab JSP (JavaServer Pages) 6 JSP files 193 JVM L language support 277 level verification 101 library filters 49 license 24 license monitoring 6 Licenses management 253 limiting functionality 95 list customization 48 logging off 25 loop creation 165 Lotus Domino 14, 18 LU or pool name 154 M macro 88, 149 adding to a keypad 94 connecting 155 disconnecting 170 Mail 28 Command 28 Database 28 File 28 My Folder 28 Print 28 mailing PDF files 32 Main Page, iseries Access for Web 25 maps 255 menu items 87 Message queues 34 message text line 88 Messages tab 34 migration 19 applications 136 utility 136 XML Gateway sessions 136 migration.properties file 19 More 86 MQ Everyplace 259 multi-language support 6 Multiple sessions 24 My commands 44 My Folder My Folder notification 27 My Keypads 93 adding a macro to the keypad 94 Configure Keypad 94 Keypad Layout 93 Show Keypad 93 My Macros 91 Edit 92 playing a macro 92 recording a macro 92 My requests 36 N National Language Support (NLS) 96 Native JDBC Driver 38 navigation bar 26, 85 Netscape 17 NetServer 44 New Screen Definition 157 NLS (National Language Support) 96 non-input fields 94 Index 283

298 O OLE DB provider 259 Open Database Connectivity (ODBC) driver 259 Opera 17 Operations Console 9, 259 Operator messages 34, 47 Other driver 175 Other tab 46 output in personal folder 27 Output queues 32 output using 30 P packaging information 102 Password 175 password change 46 Pause Recording button 92 PDF document 32 PDF file by mail 32 personal folders 27 policies 47 pool creation 153 Port 83 Port number 154 preferences 47, 49 print support 254 Print tab 31 Printer output 31 Printer shares 31 Printers 31 problem determination 130 processwsrequest 213 Profile setting 52 properties object 212 Proxy Server management 253 PTFs 16 Q Quick view 36 R realm 21, 24 realm statement 21 Reconnect 95 Redbooks Web site 280 Contact us xi Redirector Service management 253 Remote Integration Object (RIO) 214 replacement tag 68 restricting functions 47 Resume Recording button 92 RIO (Remote Integration Object) 214 Run command 44 Run SQL 30, 36 runtime administration 6 Runtime Client 255 S Save Integration Object 171 Save Request 43 Screen Customizer 8, 252, 261 Administrator 255 Cusomization Studio 255 Runtime Client 255 Screen Customizer Studio 254 Screen Definition 160 screen map 254 Screen name prefix 157 Screen size 155 Search 44 Secure Sockets Layer (SSL) 22 Selected profile 46 Send messages 34 Server 83 Server jobs 35 Server name 154 server status monitoring 126 serviceability 6 service-oriented architecture (SOA) 214 Services management 253 session cleanup 95 session configuration 81 session connection 161 Set log options 130 Set trace options 130 Setup checklist 18 Share an existing pool 153 shares 32 shortcut 37 ShowCfg silent installation 120 Simple Object Access Protocol (SOAP) 214 Site 24 smart caching 253 SOA (service-oriented architecture) 214 SOAP (Simple Object Access Protocol) 214 Specify workstation ID 84 specifying default properties for EJB Integration Objects 209 SQL Query 249 SQL Table 41 SQL Wizard 36, 41 SSL indicator 255 SSL protocol 14 SSL support 6 Start Recording button 92 Start session 35 stateful session 207 Stop Recording button 92 stopping an Active session 95 Synchronize 89 system messages 72 T table filter 49 Table tab iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

299 Tables 36 Template example 58 template file 55 Terminal type 154 Text area 158 text description 45 thin client 3 thin client environment 3 Tomcat 4 Toolbox JDBC Driver 40 tooling 6 trace 46 traditional 5250 environment 3 troubleshooting 117 typical installation 120 U UDDI (Universal Description, Discovery, and Integration) 214 uninstalling previous version of Host Publisher 103 Universal Description, Discovery, and Integration (UDDI) 214 Use user ID 84 User ID 175 user list User List Name 177 User profiles 46 User/Groups management WebSphere Development Studio 252 WebSphere Development Studio for iseries 256 WebSphere Host Integration Solution 252 WebSphere Host On-Demand 7, 9, 252 WebSphere Host Publisher 260 WebSphere Portal Server 6 WebSphere Studio Application Developer 244 WebSphere Studio, Professional Edition 256 WebSphere Transcoding Publisher 259 Workstation ID 83 workstation ID configuration options 83 WRKLICINF 13 WSDL (Web Service Description Language) 214 X XML Gateway 6, 80 comparison with V5R2 interface 80 XML Gateway session migration 136 XML script 150 xmllegacygw.ear 103 V V4R2 interface, configuring sessions 81 V5R2 interface comparison with XML Gateway 80 Configuration options 82 loading shipped defaults 82 saving defaults 81 starting a 5250 session 80 View log 130 View trace 130 View version information 130 Visual Applet creation 257 VisualAge for Java, Professional Edition 256 VisualAge RPG 257 W WADbUpload 249 Web Service Description Language (WSDL) 214 Web Services 6, 141, 212, 214 WebFacing 252, 261 WebFacing Server 257 WebFacing servlet 257 WebFacing Tool 8, 252, 256 WebSphere 2 WebSphere Administrative Server 100 WebSphere Application Server deploying the application 199 WebSphere Application Server 4.0 Advanced Edition 13 WebSphere Application Server 4.0 Single Server Edition Index 285

300 286 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0

301 iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 (0.5 spine) <-> <-> 459 pages

302

303

304 Back cover iseries Access for Web V5R2 and WebSphere Host Publisher V4.0 Learn how to access iseries resources from the Web Convert 5250 to Web data sources with WebSphere Host Publisher Integrate iseries Access for Web and WebSphere Host Publisher iseries Access for Web (5722-XH2) the latest offering in the iseries Access Family (5722-XW1) product offers Web browser-based access to IBM ~ iseries servers. iseries Access for Web helps leverage business information, applications, and resources across an enterprise by extending the iseries resources to the client desktop through a Web browser. IBM WebSphere Host Publisher 4.0 (5724-B81) can modernize host applications or replace traditional character-based interfaces with a Web look and feel. These host applications can run directly from any standard Web browser. Host Publisher integrates multiple sources of data, including host and database applications, into a single Web page with no change to backend applications. Host Publisher and Host Publisher Studio have been bundled with the iseries Access for Web product to provide a complete Web-to-host integration solution. This IBM Redbook is designed for basic-level users who want to use iseries Access for Web V5R2 or WebSphere Host Publisher V4.0. It shows you how to install and use iseries Access for Web and WebSphere Host Publisher on the iseries server through several example applications. It summarizes the Web-to-host products. Then it presents various circumstances to help you decide which product to choose when you consider integrating enterprise data into the Web. INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment. For more information: ibm.com/redbooks SG ISBN