IBM WebSphere Host On-Demand Version 6.
IBM WebSphere Host On-Demand Version 6.
Note Before using this information and the product it supports, read the information in “Appendix E. Notices” on page 79. Third Edition (September 2001) This edition applies to Version 6.0 of IBM® WebSphere Host On-Demand (program number 5733-A59) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1997, 2001. All rights reserved.
Contents About this book . . . . . . . . . . . v Chapter 5. Removing Host On-Demand Chapter 1. Introducing Host On-Demand 1 Chapter 6. Using Host On-Demand with a firewall . . . . . . . . . . . . . . 33 Why use Host On-Demand? . . . . . . . . A cost-effective approach . . . . . . . . Create new e-business applications . . . . . Connect directly to any Telnet server . . . . Simple management of configuration data . . Windows integration . . . . . . . . . What’s new in Version 6.0 . . . . . . . . .
Appendix B. Manually installing SSL security capability on AIX . . . . . . 69 Appendix C. Configuring on iSeries . . 71 Configuring iSeries servers for secure connection . . Configuring a Telnet server for secure connection Configuring the Host On-Demand Telnet keyring Client authentication . . . . . . . . . . Configuring the Host On-Demand OS/400 proxy for secure connections . . . . . . . . . . Secure Web serving . . . . . . . . . . . Installing the iSeries Toolbox for Java . . . . . .
About this book This book helps you install Host On-Demand Version 6 and plan for configuration after installation. Once you install Host On-Demand, you can use the online help to define users and groups, configure clients, and complete other administrative tasks. This book is written for administrators. This graphic is used to highlight notes to the reader. This graphic is used to highlight tips for the reader. © Copyright IBM Corp.
vi Getting Started: Host On-Demand Version 6.
Chapter 1. Introducing Host On-Demand The browser-based access of IBM WebSphere Host On-Demand Version 6 (Host On-Demand) gives you a simple way to reach critical host data, without requiring you to install any software on your workstation. Host On-Demand uses the power of Java technology to open the doors to your host system whenever you need it, wherever you need it, directly from your browser. Just click on a hyperlink to launch the Host On-Demand Java applet.
To subscribe to the Software Support Bulletin, go to http://www.ibm.com/software/network/support. Why use Host On-Demand? There are a number of reasons to use Host On-Demand: A cost-effective approach You can save money in product deployment and maintenance by installing Host On-Demand on a Web server, eliminating the need to manage individual user desktops.
connect directly to any standard Telnet server that provides the best access to the required data. The Telnet connection can be changed as often as your requirements for new data change. Because no middle-tier server is required, there is no additional capacity needed on your Web server. Simple management of configuration data Host On-Demand provides a flexible set of management options for controlling its operation.
in the Host On-Demand online help for more information. Streamlined panel flow and other usability improvements to the Deployment Wizard panels make administration easier. Online help for the Deployment Wizard is now available from within the Wizard panels. 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.
Copying sessions more easily Users can create new sessions easily by right-clicking an existing session and selecting Copy. Administrators can create new sessions easily by right-clicking an existing session and selecting Duplicate Session. Administrators can also copy and paste existing sessions into other user and group definitions using the right-click menu.
6 Getting Started: Host On-Demand Version 6.
Chapter 2. Planning for Host On-Demand v v v v Deployment strategy considerations Before installing Host On-Demand Supported server operating systems Supported client operating systems v Disk space requirements v Supported browsers v Packaging Deployment strategy considerations Host On-Demand provides access to host applications from a Web browser. The browser downloads the Host On-Demand Java applet from the Web server (flow A) and then connects to any Telnet server to access host applications (flow C).
Understanding the combined model Host On-Demand supports a combined model where the host session information is defined in the configuration server using the administration utility. In the combined model you use the Deployment Wizard to create an HTML file that points to the host session information stored in the configuration server.
directory structure. In most cases these defaults should work fine. Review the directory structure in the installation section in this guide before installing. If you change the default directory structure, keep your changes in mind when following the installation instructions. Select the Service Manager port The default Service Manager port is 8999. If you want to change this value because it is already in use, you may change it during installation for Windows NT, Windows 2000, and AIX.
Supported server operating systems For updates to this information, refer to the readme file. A Host On-Demand server can be installed on the following operating systems: v v v v v v v Windows NT 4.0 with SP5 or later Windows 2000 (Professional, Server and Advanced Server) AIX (R) Version 4.3.3, 4.3.4, and 5.1 OS/2 (R) Warp Server Version 4 and OS/2 Warp Server for e-Business 4.5 Novell NetWare Version 4, 5, and 6 Sun Solaris 2.6, 2.7, and 2.
v Windows NT or Windows 2000 - 174MB (English only. Add 4 to 8MB for each additional language) v AIX (installp image) - 124MB (English only. Add 4 to 8MB for each additional language. Includes the additional security files) v UNIX (Solaris, HP-UX or Linux) - 110MB (English only. Add 4 to 8MB for each additional language) v iSeries - 230MB DASD v OS/2 and Novell - 230MB Supported browsers Browsers are dynamic. For the most up-to-date information, refer to the readme file and to the Host On-Demand Web site.
12 Getting Started: Host On-Demand Version 6.
Chapter 3. Installing Host On-Demand The Host On-Demand clients are served as Web pages, so you must install the Host On-Demand server in the same environment as a Web server. After installing Host On-Demand Version 6 on a machine running Microsoft Personal Web Server, the virtual directory for Host On-Demand does not show up in the list of virtual directories in the Personal Web Manager GUI.
1. If CD autoplay is enabled on your Windows NT or Windows 2000 server, insert the CD and wait for the start window. Otherwise, insert the CD and run the setupwin.exe program in the root directory. 2. Click Install Product. 3. Follow the directions in the installation windows. v The default server directory is hostondemand . If you are upgrading, the installation program uses the same server directory as before.
When you install in silent mode, there is no indication that installation is in progress or that it is complete. To record a response file: setup.exe -r -f1d:\temp\server1.iss To install in silent mode: setup.exe -s -f1d:\temp\server1.iss -f2d:\temp\server1.log Options supported in silent mode -r Records a response file -s Runs a response file and installs Host On-Demand -f1[path\response_file_name].iss Defines the response file, in both record and run modes.
-1 General error -2 Mode not valid -3 Required data not found in the response file -4 Not enough memory available -5 File does not exist -6 Cannot write to the response file -7 Cannot write to the log file -8 Path to the response file is not valid -9 Not a valid list type (string or number) -10 Data type is not valid -11 Unknown error during setup -12 Dialogs are out of order.
If you have previously installed Host On-Demand and have changed /hostondemand/lib/NSMprop or changed or created /hostondemand/hod/config.properties , you must back up these files before installation, then restore them after installation. The files are overwritten during the unzip process. The following steps assume that hostondemand is the server directory and HOD is the publish directory. To install the Host On-Demand server: 1. Insert the CD. 2. Create a server directory, for example, hostondemand .
12. Load HODMain.html , located in the \hostondemand\HOD directory, into your browser. v Click readme to see updated information. v Click Basic configuration steps to help you get started with configuring the Host On-Demand server. Installing on Novell NetWare The following are required to install Host On-Demand on a Novell server: v Novell NetWare 4.x v Novell Web Server v Novell Java Development Kit 1.1.8 To obtain the Novell JDK, go to http:\\www.developer.novell.com.
10. If you unpacked hod60www.zip into SYS:\web\docs as suggested above, the HOD directory is automatically published, because it is a subdirectory of the default published directory, SYS:\web\docs . If you unpacked the file anywhere else, publish that directory (make it available to client users who access the server through a browser). Refer to the Web server documentation for information about how to do that. 11. Reboot the server. 12.
2. Start the installation program by changing to the root directory of the CD, type setupaix.sh and press Enter. You may need to type./setupaix.sh if the current directory (.) is not set in your PATH variable. 3. You may click on View Documentation. Make sure you have configured Netscape such that it can be run by the installation program. Specifically, before running setupaix.sh, ensure that the Netscape executable is in your PATH (e.g.
/path/response_file_name Defines the name for the response file. The default is install.script, and a sample install.script file is provided in the \instmgr directory on the Host On-Demand CD. Any file name can be used if properly specified on the command line used to execute the installation process. Below are sample command lines that will install Host On-Demand on an AIX workstation in silent mode.
Obtain the latest JDK for UNIX from one of the following sites: http://www.ibm.com/java ftp://ftp.hursley.ibm.com/pub/java If you have previously installed Host On-Demand and have changed /hostondemand/lib/NSMprop or changed or created /hostondemand/hod/config.properties , you must back up these files before installation, then restore them after installation. The files are overwritten during the installation process. To install the Host On-Demand server on a UNIX workstation, follow the steps below.
d. Run NCServiceManager-UNIX . The Service Manager does not display a message indicating that it has started. To arrange for this script to be run at boot time, refer to the documentation supplied with your operating system to add a boot service. For Host On-Demand to function, the Service Manager must be running. If you reboot the server, you must also restart the Service Manager. 9. Restart the Web server. 10. Load HODMain.html, located in the hostondemand/HOD directory, into a browser.
This command will process for 10-45 minutes, depending upon the configuration of the iSeries. 6. For each additional OS/400 secondary language that you would like to provide full help text support for, type the following OS/400 command: RSTLICPGM LICPGM(5733A59) DEV(OPT01) LNG(xxxx) RSTOBJ(*LNG) Where xxxx is the language code from the list below. This step is optional and can be performed after installation.
Turkish 2956 7. If you have previously installed IBM Screen Customizer, you must install the new version at this time. Refer to the installation manual for Screen Customizer. 8. If you want the Host On-Demand Service Manager to automatically start after an IPL (when QSYSWRK is started), type the following OS/400 command: CFGHODSVM AUTOSTART(*YES) 9.
Configuring, starting, and stopping the Host On-Demand Service Manager on iSeries A menu is provided for starting and stopping the Host On-Demand Service Manager. To access the menu, type the following on the OS/400 command line: GO HOD The following commands can be used from the menu or the OS/400 command line. Configure (CFGHODSVM): To configure the Service Manager, choose option 1. You need *JOBCTL and *ALLOBJ authority to use this option. You can configure the following information: 1. 2. 3. 4. 5. 6.
4. Save the customized HTML page to the y:\ProdData\hostondemand\hod directory. 5. Using a browser, test out the Web page (for example, http://iseries.name.com/hod/myweb.html). For advanced configuration information, see Configuring on iSeries in Appendix C. Installing on z/OS For instructions about installing Host On-Demand on z/OS, refer to the program directory supplied with the z/OS or legacy OS/390 program product.
The port used by the clients, configuration servlet, and the Service Manager can be customized. For instructions on how to customize the port, see configuring the configuration servlet and changing the Service Manager port in the online help. The Host On-Demand clients use the default port of 8999 to communicate with the Service Manager for configuration information. If any of your clients are outside the firewall, the firewall administrator must open this port internally and externally.
Chapter 4. Migrating from previous versions of Host On-Demand With very few exceptions, data used in earlier versions of Host On-Demand will be automatically migrated when you begin using Host On-Demand Version 6. Any existing configuration data in your configuration server will be automatically available in Host On-Demand Version 6 once installation is complete.
30 Getting Started: Host On-Demand Version 6.
Chapter 5. Removing Host On-Demand To remove the Host On-Demand server: Windows NT or 2000 Use Add/Remove Programs from the Windows control panel. UNIX Stop the Host On-Demand Service Manager. Get the process ID, kill the process, then delete the Host On-Demand directories (except ./private ). OS/2 Stop the Host On-Demand Service Manager by pressing Ctrl+C in the OS/2 window in which you started it, close the window, then delete the Host On-Demand directories (except \private ).
32 Getting Started: Host On-Demand Version 6.
Chapter 6. Using Host On-Demand with a firewall If you are configuring Host On-Demand to go through a firewall, make sure the firewall administrator opens port 8999 internally and externally. The Service Manager listens to port 8999 by default, and the client receives configuration information directly from the Service Manager over port 8999 by default. You can customize the port the clients and Service Manager use.
If you do not want to open port 8999 on the firewall, you can still allow users to access Host On-Demand. There are two options: v If you want to use the configuration server, you can configure clients to use the configuration servlet. See Configuring the configuration servlet in the Host On-Demand online help. This option is only available if your Web server supports servlets. v Use the Deployment Wizard to create HTML files that contain all configuration information.
Chapter 7. Configuring Host On-Demand overview After installing Host On-Demand, you’ll need to configure Host On-Demand sessions for your users. To do this, you can use the Deployment Wizard to create HTML files or use the default configuration files shipped with Host On-Demand. The Host On-Demand Deployment Wizard guides you through the necessary steps to create an HTML page that can be used to launch Host On-Demand host sessions.
36 Getting Started: Host On-Demand Version 6.
Chapter 8. Loading the Host On-Demand clients The Host On-Demand clients are implemented as HTML files that you load into a Web browser. There are many ways users can load the clients: v Customize your own HTML pages to launch sessions that you have configured. You can use the Deployment Wizard to create customized pages. See Deployment Wizard in the Host On-Demand online help for more information. v Load the HODMain.
Package Utilities Client HTML File Database On-Demand client cached HODDatabaseCached.html Database On-Demand client cached with problem determination HODDatabaseCachedDebug.html Remove cached client HODRemove.html New user client NewUser.html New user client cached NewUserCached.html New user client cached with problem NewUserCachedDebug.html determination Note: Custom-built clients are created by the Deployment Wizard. These will have unique HTML file names.
Cached clients A cached client can be any client where you choose to cache the applet on the user’s machine. Most likely, the HTML is created using the Deployment Wizard; however, it could be HODCached.html, as well. The cached client (HODCached.html) provides all the Host On-Demand functions including problem determination and the Screen Customizer. It is cached on your local disk the first time you download it.
If the software on the server is an earlier version than the cached software, the cached client applet checks the version levels of the components and prevents caching of any new components. To cache new components, remove the more recent version of the cached client and then install the earlier version of the cached client. To avoid this problem, select all the functions the user needs (across all sites the user accesses) in the preload list when you create the HTML page using the Deployment Wizard.
Note: If you are installing the cached client on a Netscape 6.0 Web browser, you cannot install the client from CD. 1. Copy the following files from the HOD publish directory of your Host On-Demand server installation, to a network drive or put them on a CD: HODCached.html (customized for a LAN or CD load) hodlogo.gif hodbkgnd.gif Installer.html Cached.js ccversions.properties CachedAppletInstaller.* CachedAppletSupporter.* CachedAppletRemover.* sccbase.* *.jar *.cab scccversions.
where yourhostname and alias are your Host On-Demand Version 4.x server’s hostname and alias, or Publish, directory. The HODServer parameter works with the UpgradePercent and UpgradeURL parameters to manage client upgrades. If the cached client won’t be upgraded on this connection attempt, it is redirected automatically to the Host On-Demand Version 4.x server specified in the HODServer HTML parameter. If a cached client will be upgraded, the Host On-Demand Version 4.
exceptions. To resolve this, following a version upgrade of your browser, you should remove Host On-Demand using HODRemove.html, and then re-install the product using HODCached.html. Cached client with problem determination (HODCachedDebug.html) This client starts the cached client with problem determination (session logging and tracing).
functions might be required immediately (such as the 3270 emulator), while other functions (file transfer, for example) might never be invoked or might not be needed for a long time. The Function On-Demand client can be configured with the traditional ″green screen″ interface, or it can be configured with the Screen Customizer/LE interface. You can also create your own Function On-Demand client using the Deployment Wizard, specifying what functions are enabled and what functions download initially.
New user client cached (NewUserCached.html) This client starts the New User client in a cached environment. Load this HTML page if you want to use the New User client in a cached environment without problem determination. New user client with problem determination (NewUserCachedDebug.html) This client starts the New User client in a cached environment with problem determination.
46 Getting Started: Host On-Demand Version 6.
Chapter 9. Security Whether you are implementing Host On-Demand purely within your corporate network, or you are using it to provide access to your host systems over the Internet, security is a concern. Host On-Demand uses Secure Sockets Layer (SSL) protocol to provide security for emulator sessions. SSL is an industry-standard protocol that provides encryption and authentication on connections across a TCP/IP network, using X.509 certificates.
after making sure that the server’s certificate can be trusted, checks whether the Internet name in the certificate matches the Internet name of the server. If they match, the SSL negotiation will continue. If not, the connection ends immediately. See server authentication in the Host On-Demand online help for more information.
Mutual authentication Exchange of identification through public-key certificates. The client and server identities are encoded in public-key certificates, which contain the following components: v Subject’s distinguished name v Issuer’s distinguished name v Subject’s public key v Issuer’s signature v Validity period v Serial number You can also use secure HTTP (HTTPS) to ensure that a client’s security information is not compromised as it is downloaded from a server.
well-known or trusted to the Redirector. You can add certificates from other CAs (unknown CAs) and certificates that you create and sign yourself (self-signed) to this database. CustomizedCAs.class Is created and updated during SSL configuration. This database contains server and CA-root certificates that are not in the well-known list and are needed by Host On-Demand clients.
The Redirector sets security for each local port. Security choices are: v Pass-through - data between the client and the host is not altered v Client side - encrypts data between the client and the redirector v Host side - encrypts data between the redirector and the host v Both - encrypts data both ways You must enable security for the Redirector before you can enable client-side security, server-side security or both.
52 Getting Started: Host On-Demand Version 6.
Chapter 10. LDAP support A Lightweight Directory Access Protocol (LDAP) server directory provides the ability to share user and group configuration information. The following LDAP servers are supported for use with Host On-Demand: IBM LDAP Directory Server V2.1, V3.1.1, and V3.2.1 Windows NT and AIX Netscape Directory Server V3.1 and V4.0 Windows NT and AIX IBM LDAP Directory Server running on OS/390 Version 2, Release 5, 6, 7, 8, 9, 10, 11, Legacy OS/390 and z/OS and 12 Installing LDAP support 1.
1. Copy the following slapd files to the LDAP server: Netscape.IBM.at Netscape.IBM.oc 2. Stop the LDAP server. 3. Edit the slapd.conf file and add the following statements: userat "/Netscape.IBM.at" useroc "/Netscape.IBM.oc" 4. Restart the LDAP Server. To install the Host On-Demand schema extensions on an IBM LDAP Directory server: 1. Copy the following slapd files to your LDAP server: V2.1.IBM.at V2.1.IBM.oc 2. Stop the LDAP server. 3.
Distinguished Name Suffix Type the distinguished name (DN) of the highest entry in the directory information tree (DIT) for which information will be saved. Host On-Demand will store all of its configuration information below this suffix in the DIT. You must use the LDAP string representation for distinguished names (for example, cn=HOD,o=IBM,c=US ). Migrate Configuration to Directory Service To migrate users and groups from the private data store to the LDAP directory, click the check box.
56 Getting Started: Host On-Demand Version 6.
Chapter 11. Database On-Demand overview Note: If you are using Database On-Demand with Netscape 4.x, you must turn the Just In Time (JIT) compiler off. Unfortunately, due to problems found with the JIT compiler, this means that you cannot take advantage of both the Database On-Demand and integrated Windows domain logon functions. Database On-Demand is a Java applet that allows users to perform SQL requests to iSeries databases through a JDBC driver.
HODDatabase_J2_xx.html file. For the first change, look for the line that begins PARAM NAME=″cache_archive″. In the list of jar files which follows, add the jar filename from the table below. For the second change, look for the line which begins with ″document.writeln″. This line will contain a number of instances of the string ″HODVersion + ’,’″ . This list indicates to the JRE 1.3 the versions of each of the jar files.
German, Spanish, French, Italian, Portuguese, Brazilian Portuguese hacp1a.jar HACP1A Greek hacpgr.jar HACPGR Hebrew hacphe.jar HACPHE Japanese hacpja.jar HACPJA Korean hacpko.jar HACPKO Russian hacpru.jar HACPRU Simplified Chinese hacpzh.jar HACPZH Thai hacpth.jar HACPTH Turkish hacptr.jar HACPTR Traditional Chinese hacptw.jar HACPTW Chapter 11.
60 Getting Started: Host On-Demand Version 6.
Chapter 12. National language support Host On-Demand is provided in many languages. The session windows, configuration panels, help files, and the documentation have been translated. In addition, display, keyboard, and processing support is provided for Arabic, Hebrew, Thai, and Hindi. This support is fully explained in the help. All the translated versions are provided on the CDs and on the zSeries tapes.
Russian ru Slovenian sl Spanish es Swedish sv Turkish tr Supported host code pages Host On-Demand supports multiple code pages. You can specify these code pages on a session-by-session basis. 3270 and 5250 code pages The code pages specified below are supported by the 3270 and 5250 emulators. You can select them in the Session Configuration window.
Finland (Euro) 1143 France 297 France (Euro) 1147 FYR Macedonia 1025 FYR Macedonia (Euro) 1154 Germany 273 Germany (Euro) 1141 Greece 875 Hebrew (New Code) 424 Hebrew (Old Code) 803 Hindi 1137 Hungary 870 Hungary (Euro) 1153 Iceland 871 Iceland (Euro) 1149 Italy 280 Italy (Euro) 1144 Japan (Katakana Extended) 930 Japan (Katakana Unicode Extended) 1390 Japan (Katakana) 930 Japan (Latin Extended) 939 Japan (Latin Unicode Extended) 1399 Korea (Euro) 1364 Korea (Ext
Portugal 037 Portugal (Euro) 1140 Romania 870 Romania (Euro) 1153 Russia 1025 Russia (Euro) 1154 Serbia/Montenegro (Cyrillic) 1025 Serbia/Montenegro (Cyrillic; Euro) 1154 Slovakia 870 Slovakia (Euro) 1153 Slovenia 870 Slovenia (Euro) 1153 Spain 284 Spain (Euro) 1145 Sweden 278 Sweden (Euro) 1143 Taiwan (Traditional Chinese Extended) 937 Taiwan (Traditional Chinese Extended; Euro) 1371 Thai 838 Thai (Euro) 1160 Turkey 1026 Turkey (Euro) 1155 Ukraine 1123 Ukraine (E
Arabic ASMO 708 and ASMO 449 British 1101 DEC Greek DEC Hebrew DEC Multinational Replacement Character Set 1100 DEC Technical Dutch 1102 Finnish 1103 French 1104 French Canadian 1020 German 1011 Hebrew NRCS ISO Greek Supplemental (ISO Latin-7) 813 ISO Hebrew Supplemental ISO Latin-1 819 Italian 1012 Norwegian/Danish 1105 PC Danish/Norwegian 865 PC International 437 PC Multilingual 850 PC Portugese 860 PC Spanish 220 Spanish 1023 Swedish 1106 Swiss 1021 United States
869 Greek 912 ISO Latin 2 (8859_2) 915 ISO Cyrillic (8859_5) 920 ISO Latin 5 (8859_9) User-defined character mapping For double-byte character set (DBCS) languages, you can use customized user-defined character (UDC) mapping in your session (3270, 5250, 3270 host print) instead default mapping. You can create a UDC translation table using the UDC mapping editor to store customized mapping for your session.
Appendix A. Locally installed clients The locally installed client installs to a local disk. The client applet is loaded directly into the default system browser, so there is no download from a server. The most common reason to configure a local client is for users who connect remotely over slow telephone lines, where download time can be an issue and connectivity is unpredictable.
Removing the client 1. Stop the Host On-Demand Service Manager: a. Press Ctrl+Alt+Del once to open the Close Program window. b. Highlight the JRE task, then click End Task. 2. Use Add/Remove Programs from Control Panel. If InstallShield does not remove the hostondemand directory, you must remove it manually. 68 Getting Started: Host On-Demand Version 6.
Appendix B. Manually installing SSL security capability on AIX If you intend to use an AIX server to support secure connections from clients, you must install additional files. Before installing the AIX server security files over an existing installation, remove all lib*.so files from the hostondemand/bin directory. Note: If you are running AIX 4.2, you must first upgrade to AIX 4.3, uninstall the previous version of Host On-Demand, and install Host On-Demand Version 6 using the hod60srv.AIX43.SSL.tar file.
cp en/HODServerKMHelp.class If you want to have access to the help for a different language, you must change the directory from which the HODServerKMHelp.class file is copied. For example, if you want to use the Spanish help files, change the above line to: cp es/HODServerKMHelp.class 70 Getting Started: Host On-Demand Version 6.
Appendix C. Configuring on iSeries Configuring iSeries servers for secure connection The iSeries severs can be configured to use certificates from a public signing agency or from a private certificate management system, like the AS/400 Digital Certificate Manager. Before you enable SSL, decide which type of certificate to use. See Deciding where to obtain your digital certificates on the iSeries Web site.
the CA certificate and not the site certificate. If the port is not responding, refer to Configuring iSeries servers for secure connection. Repeat Step 3 for each Telnet server. 4. To view the contents of the keyring, type the following (this command may span two lines but should be entered as one line): java -classpath .:/QIBM/ProdData/hostondemand/lib/sm.zip com.ibm.hodsslight.tools.keyrng CustomizedCAs verify 5. Press F3 to exit qsh.
2) Give users who need access to the SSL files *RX authority to the directory. You can authorize individual users or groups of users. Remember that users with *ALLOBJ special authority cannot be denied access to the SSL files. 2. From a web browser, access http://:2001 (where is the TCP/IP host name of your iSeries). If you are unable to connect, start the HTTP server with the following OS/400 command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) 3.
Repeat the above steps for each target iSeries server. Secure Web serving The Host On-Demand server uses the Web server to download program objects to the browser. This information can be encrypted, but with a considerable performance impact. Refer to the redbook AS/400 HTTP Server Performance and Capacity Planning (SG24-5645) for more information. The default port for secure web serving is 443. If that port is not enabled, port 80 is used. To enable secure web serving, perform the following steps: 1.
Table 1. Additional iSeries-related web pages (continued) Title Title Web page National language exit Download Telnet exit program files Installing the iSeries Toolbox for Java The iSeries Toolbox for Java is a set of Java classes that enable you to write client/server applications and applets that work with data residing on your iSeries. You can also run such applications on the OS/400 Java Virtual Machine (JVM). The Toolbox uses iSeries servers as access points to the system.
v jt400_doc_zh_TW.zip contains the Programmer’s Guide in Traditional Chinese. To install the iSeries Toolbox for Java on your workstation, unzip the appropriate files. For example, if you want to install the code and the English version of the Programmers Guide, unzip jt400_all.zip and jt400_doc_en.zip . You must use a utility that supports long filenames. For additional information on the toolbox, see http://www.as400.ibm.com/toolbox. 76 Getting Started: Host On-Demand Version 6.
Appendix D. Netscape 6.0 and Java2-enabled Web browser issues Host On-Demand Version 6 clients are supported on Java2-enabled Web browsers, such as Netscape 6.0, Netscape 6.01, Mozilla 0.9.0, and the IBM Web Browser for OS/2. These Web browsers use a Java2 Runtime Environment (JRE) plug-in that is supplied by Sun Microsystems Inc. or IBM. As newer versions are released, IBM will announce support on the Host On-Demand Web site. Older Web browsers, such as Microsoft Internet Explorer and Netscape 4.
using the Sun JRE Version 1.4 or by running a custom session1.html or session2.html file. You also see this limitation running the Sun plug-in with older browsers and converted HTML files. The IBM JRE for Windows 32-bit platforms and Linux can be downloaded free of charge from the IBM Web site. The OS/2 JRE is available on Software Choice. The Sun JRE also has a limitation with Hindi character conversion. To avoid this problem, use the IBM JRE.
Appendix E. 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.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department T01 Building B062 P.O. Box 12195 Research Triangle Park, NC 27709-2195 U.S.A.
Appendix F. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. Other company, product, and service names may be trademarks or service marks of others.
82 Getting Started: Host On-Demand Version 6.
Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.
