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

304 

Loading....

Loading....

Loading....

Loading....

Loading....

Full text

(1)

IBM

Front cover

iSeries Access for Web V5R2 and

WebSphere Host Publisher V4.0

Sungsim Park

Andy Hagger

Benjamin Jansky

Paul Masschelein

Kevin O’Connor

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

(2)
(3)

International Technical Support Organization

iSeries Access for Web V5R2 and

WebSphere Host Publisher V4.0

(4)

© Copyright International Business Machines Corporation 2002. All rights reserved.

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.

Take Note! Before using this information and the product it supports, be sure to read the general

(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 V4.0 . . . 1

1.1 Today’s environment . . . 2

1.2 Internet connectivity . . . 2

1.3 WebSphere software products . . . 2

1.4 iSeries platform . . . 2

1.5 What is iSeries Access for Web . . . 3

1.5.1 What is new in iSeries Access for Web V5R2. . . 4

1.6 What is WebSphere Host Publisher . . . 4

1.6.1 What is new in Host Publisher V4.0 . . . 6

1.7 Host Access products . . . 6

1.7.1 Host Access Client Package . . . 7

1.7.2 WebSphere Development Studio . . . 8

1.7.3 iSeries Access Family . . . 8

1.7.4 WebSphere Host Integration Solution. . . 9

1.8 Summary . . . 10

Chapter 2. Setting up iSeries Access for Web . . . 11

2.1 iSeries server requirements . . . 12

2.1.1 iSeries hardware requirements . . . 12

2.1.2 Software requirements . . . 12

2.1.3 Software considerations . . . 16

2.2 Web browser requirements . . . 17

2.3 Setup overview . . . 17

2.4 Migration . . . 19

2.5 Connecting to multiple iSeries servers . . . 20

2.6 Setting up a secure iSeries connection . . . 22

Chapter 3. Using iSeries Access for Web . . . 23

3.1 The iSeries Access for Web home page . . . 24

3.2 iSeries Access for Web functions . . . 25

3.2.1 My Folder . . . 26 3.2.2 Mail . . . 28 3.2.3 Print. . . 31 3.2.4 Messages . . . 34 3.2.5 Jobs . . . 34 3.2.6 5250 . . . 35 3.2.7 Database. . . 35 3.2.8 Files . . . 43 3.2.9 Command . . . 44 3.2.10 Customize . . . 45 3.2.11 Other . . . 46

(6)

3.2.12 General . . . 47

3.3 iSeries Access for Web policies and preferences . . . 47

3.3.1 Restricting functions . . . 47

3.3.2 List customization . . . 48

3.3.3 Library filters . . . 49

3.3.4 Preferences. . . 49

3.4 Customizing users and groups . . . 51

3.5 Home page and template file customization . . . 55

3.5.1 Creating files . . . 55

3.5.2 Serving images . . . 56

3.5.3 Template example . . . 58

3.5.4 Home page example: Customer view . . . 61

3.5.5 Home page example: Administrator view . . . 66

3.6 Troubleshooting . . . 76

Chapter 4. The iSeries Access for Web V5R2 5250 interface . . . 79

4.1 Comparing the V5R2 interface and XML Gateway . . . 80

4.2 Starting a 5250 session. . . 80 4.3 Configuring sessions . . . 81 4.3.1 Configuration options . . . 82 4.4 Usage . . . 89 4.4.1 Synchronize . . . 89 4.4.2 My Macros . . . 91 4.4.3 My Keypads . . . 93 4.4.4 Cursor positioning . . . 94 4.4.5 Active sessions . . . 94 4.4.6 Limiting functionality . . . 95 4.5 5250 shortcut . . . 95

4.6 Where to find more information . . . 96

Chapter 5. Installation and administration of WebSphere Host Publisher Server . . . 97

5.1 Hardware and software requirements . . . 98

5.1.1 Hardware requirements. . . 98

5.1.2 Software requirements . . . 98

5.1.3 Host Publisher Studio . . . 99

5.2 Installing and uninstalling Host Publisher Server . . . 100

5.2.1 Preliminary considerations . . . 100

5.2.2 Installing Host Publisher Server . . . 103

5.2.3 Installing Host Publisher Studio . . . 120

5.2.4 Saving and restoring Host Publisher Server . . . 121

5.2.5 Uninstalling Host Publisher Server . . . 121

5.2.6 Uninstalling Host Publisher Studio . . . 122

5.3 Using Host Publisher Server Administration . . . 122

5.3.1 Starting the Host Publisher Server Administration . . . 124

5.3.2 Using the functions in Host Publisher Server Administration . . . 124

5.4 Migrating applications and XML Gateway sessions . . . 136

5.4.1 Using the migration utility in Host Publisher Studio. . . 136

5.4.2 Migrating applications on the server . . . 137

Chapter 6. Using Host Publisher Studio to develop J2EE applications . . . 141

6.1 Overview of Host Publisher applications . . . 142

6.2 Integration Objects . . . 144

6.2.1 Interacting with a data source . . . 144

(7)

6.2.3 Information specified in a connection pool . . . 145

6.2.4 Enabling and disabling connection pooling . . . 146

6.2.5 User lists . . . 146

6.3 Creating a Host Access Integration Object . . . 149

6.3.1 Building an Integration Object using macros. . . 149

6.3.2 Sample scenario . . . 152

6.4 Creating a Database Access Integration Object . . . 173

6.4.1 Integration Objects overview. . . 173

6.4.2 Sample scenario . . . 174

6.5 Application Integrator . . . 183

6.5.1 Specifying Integration Objects to publish to the application server. . . 183

6.5.2 Using the Application Integrator wizards. . . 183

6.5.3 Transferring applications to a Host Publisher Server . . . 196

6.5.4 Deploying the application on WebSphere Application Server. . . 199

6.6 Creating composite applications . . . 206

6.7 Enterprise JavaBeans support . . . 207

6.7.1 Understanding EJB support in Host Publisher . . . 207

6.7.2 Creating EJB support files for Integration Objects . . . 208

6.7.3 Accessing Host Publisher EJB from local JSPs . . . 210

6.7.4 Creating a Host Publisher application using EJB access beans. . . 211

6.8 Web Services overview . . . 212

6.8.1 Host Publisher V4.0 Web Services support . . . 212

6.8.2 Creating and deploying a Web Service. . . 213

6.8.3 Accessing Host Publisher from a remote machine using Web Services. . . 214

6.8.4 Specifying properties for Web Services Integration Objects . . . 214

6.8.5 Creating Web Services support in Host Publisher Studio . . . 214

6.8.6 Creating Web Services in WebSphere Studio Application Developer with Host Publisher Web Services support. . . 215

6.9 Application Integrator Advanced . . . 235

6.9.1 Creating a new application for EJB or Web Services . . . 235

6.9.2 Deploying Enterprise JavaBeans . . . 238

6.9.3 Transferring applications to a Host Publisher Server . . . 238

6.9.4 Deploying the application on WebSphere Application Server. . . 238

6.10 Host Publisher Portlet . . . 244

6.11 WebSphere Studio Application Developer Web Services limitations . . . 244

6.12 References . . . 245

6.12.1 Host Publisher Studio and Server . . . 245

6.12.2 WebSphere Application Server for iSeries . . . 245

6.12.3 EJB . . . 245

6.12.4 Web Services . . . 246

6.12.5 Portlet . . . 246

6.13 Summary . . . 246

Chapter 7. iSeries Access for Web and Host Publisher integration. . . 247

7.1 Integration example. . . 248

7.2 Where to find more information . . . 249

Chapter 8. A comparison of Web-to-host integration tools . . . 251

8.1 Overview of the Web-to-host solutions . . . 252

8.2 Host Access Client Package for iSeries Version 2.0. . . 252

8.2.1 IBM Personal Communications for Windows Version 5.5. . . 252

8.2.2 WebSphere Host On-Demand Version 6.0 . . . 253

(8)

8.3 WebSphere Development Studio . . . 256

8.3.1 Host components . . . 256

8.3.2 Workstation components . . . 256

8.3.3 WebSphere Studio Professional Edition . . . 257

8.3.4 WebFacing Tool . . . 257

8.4 iSeries Access Family . . . 258

8.4.1 iSeries Access for Windows . . . 259

8.4.2 iSeries Access for Wireless. . . 259

8.4.3 iSeries Access for Web . . . 259

8.4.4 WebSphere Host Publisher. . . 259

8.5 WebSphere Host Integration Solution . . . 259

8.6 Comparison . . . 260

8.6.1 WebSphere Host Publisher V4.0 . . . 260

8.6.2 WebFacing . . . 261

8.6.3 Host On-Demand . . . 261

8.6.4 Screen Customizer . . . 261

8.6.5 iSeries Access for Web . . . 262

8.6.6 Putting it all together . . . 262

Appendix A. Configuring the Domino HTTP Server for iSeries Access for Web . . . 265

Updating the Domino Server Document . . . 266

Updating the Domino server’s notes.ini file . . . 266

Restarting the Domino server’s HTTP task . . . 266

Appendix B. Additional information on Host Publisher . . . 267

Host Publisher installation log . . . 268

Host Publisher configuration information . . . 271

Host Publisher version information . . . 275

Host Publisher documentation . . . 275

Appendix C. Language support . . . 277

Related publications . . . 279

IBM Redbooks . . . 279

Other resources . . . 279

Referenced Web sites . . . 279

How to get IBM Redbooks . . . 280

IBM Redbooks collections. . . 280

(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 10504-1785 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.

(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® 1-2-3® 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.

(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 e-mail to: sungsim@us.ibm.com

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 e-mail to: ah@ch.ibm.com

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 e-mail to: jansky@us.ibm.com

(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 e-mail to: paul_masschelein@be.ibm.com

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 e-mail to: kevin_oconnor@kaz.com.au

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:

(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:

redbook@us.ibm.com

Mail your comments to:

IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2

3605 Highway 52N

(14)
(15)

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

(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 e-mail. 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:

http://www.ibm.com/software/info/websphere

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

(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

(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.

1.5.1 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 3.2.4

A 5250 interface, removing the need to configure the XML gateway with Host Publisher (Refer to Chapter 4, “The iSeries Access for Web V5R2 5250 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.

(19)

Host Publisher Studioprovides 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 inEJB 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 4.0.2. Advanced Edition or Advanced Single Server Edition.

(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.

1.6.1 What is new in Host Publisher V4.0

Host Publisher Server on iSeries requires you to install WebSphere Application Server 4.0.2. 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 isa 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.

(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

1.7.1 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.

(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.

1.7.2 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.

1.7.3 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.

(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

1.7.4 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.

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 V3.5 5648-E25

WebSphere Host Publisher V4.0 5724-B81 Management Central Pervasive iSeries Access for Wireless 5722-XP1 iSeries ODBC driver for Linux 5722-LO1

(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.

(25)

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, SC41-5518. 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.

(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.

2.1.1 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

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

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

2.1.2 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.

Server type Processor feature CPW

AS/400e Server 170 2292 220 AS/400e Server 270 2061 240 iSeries Model 270 2250 370 iSeries Model 820 2395 370 Main storage Minimum 512 MB Recommended 1 GB

Software product Required disk space

(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, SC41-5518, 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 1.2 5722-JV1 5 Java Developer Kit Version 1.3 5722-JC1 Base Toolbox for Java

5722-TC1 Base TCP/IP Connectivity Utilities 5722-DG1 Base IBM HTTP Server for iSeries 5722-AC2 or

5722-AC3

Base Base

Crypto Access Provider 56 Bit for iSeries Crypto Access Provider 128 Bit for iSeries (only required for SSL protocol)

5722-XW1 Base Option 1

iSeries Access Family

iSeries Access Enablement Support 5722-XH2 Base iSeries Access for Web

(28)

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 5.0.5 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 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 4.0.2 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.

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 1.2 5722-JV1 5 Java Developer Kit Version 1.3 5722-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)

(29)

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, SC41-5518, 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

.

Figure 2-1 iSeries Access for Web licensed program

Use the following command to produce this information in a spooled file: DSPSFWRSC *PRINT

5722-AC2 or 5722-AC3

Base Base

Crypto Access Provider 56 Bit for iSeries Crypto Access Provider 128 Bit for iSeries (only required for SSL protocol)

5722-XW1 Base Option 1

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.

Display Installed Licensed Programs System: ITSO 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

Bottom Press Enter to continue. F3=Exit F11=Display release F12=Cancel F19=Display trademarks

(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, SC41-5518, 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:

http://www.as400service.ibm.com

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

Refer to the following Web site for information relating to the latest iSeries Access for Web PTF requirements: http://www.ibm.com/servers/eserver/iseries/clientaccess/web/ Product PTF number 5722-SS1 SI02028 5722-SS1 SI01946 5722-SS1 SI02756 5722-DG1 SI02940

(31)

For information on the most recent levels of fixes available for any related products, refer to the following Web sites:

Information on PTFs for IBM WebSphere Application Server:

http://www.ibm.com/eserver/iseries/software/websphere/wsappserver

Information on PTFs for iSeries Access for Web:

http://www.ibm.com/servers/eserver/iseries/clientaccess/web/

Information on PTFs for ASF Tomcat HTTP Server:

http://www.ibm.com/servers/eserver/iseries/software/http

Information on PTFs for IBM WebSphere Host Publisher:

http://www.ibm.com/software/webservers/hostpublisher

Information on iSeries PTFs for Lotus Domino:

http://www.as400service.ibm.com

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:

http://www.ibm.com/servers/eserver/iseries/domino/support/

2.2 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, SC41-5518, 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.

Note: You must check all the listed Web sites for additional PTFs. Some required PTFs

(32)

Table 2-7 Software combinations

For information about configuring the Web application server, refer to the WebSphere documentation center at:

http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/doc.htm

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, SC41-5518, 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.

The iSeries Access for Web, SC41-5518, 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, SC41-5518.

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 12.

2. Verify your iSeries server has the prerequisite software listed in 2.1.2, “Software requirements” on page 12.

3. Verify your Web browser meets the requirements listed in 2.2, “Web browser requirements” on page 17.

4. 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 15.

5. 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, SC41-5518.

6. Now that the iSeries server software is installed, install the latest program temporary fixes (PTFs) for:

WebSphere Application Server 4.0 Advanced Edition

WebSphere Application Server 4.0 Advanced Single Server Edition

ASF Tomcat

IBM HTTP Server (powered by Apache)

Yes Yes Yes

IBM HTTP Server (original)

Yes Yes No

Domino HTTP Server Yes Yes No

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.

(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, SC41-5518.

8. If you plan to use WebSphere 4.0, see iSeries Access for Web, SC41-5518, 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, SC41-5518, for details.

2.4 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, SC41-5518. 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.

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 265.

(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.

Figure 2-2 Connecting to multiple systems with iSeries Access for Web

Internet/intranet

Web browser

HTTP or HTTPS

iSeries Access Family iSeries Access for Web

HTTP or Secure HTTP connection System A SystemB SystemC SystemD Toolbox Connections

Refer to Tables 2-4 and 2-5 for the required software products for iSeries Access for Web

(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.

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.

#Wed Apr 24 15:29:56 GMT+00:00 2002 port=5252 nodename=<systemname> serviceport=900 servicehost=<systemname> realm=systemc.ibm.com

(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, SC41-5518, 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:

http://as400bks.rochester.ibm.com/pubs/html/as400/v5r1/ic2924/index.htm

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

(37)

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.

(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:

http://systemname/webaccess/iWAHome

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.

Note: Replace systemname with the name of your iSeries. If HTTP is configured for a non-standard port, you must specify systemname:port.

(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 55.

3.2 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 Pagelink. You may also enter the following URL: http://systemname/webaccess/iWAMain

Figure

Updating...

Related subjects :