j walk server for iseries installation guide - dps,...

-

J Walk Server for iSeries

Administration Guide

LegaSuite

Notices Edition Publication date: August 2009 Book number: JWSN-4111-UG-12 Product version: J Walk 4.1C11 Copyright © Rocket Software Europe Holding B.V. 1999 – 2009. All rights reserved.

Rocket Software Europe Holding B.V. is a wholly-owned subsidiary of Rocket Software, Inc.

Trademarks The following trademarks appear in this help file/document: Trademark Trademark Owner Seagull Software®, J Walk® Rocket Software,Inc. iSeries®, IBM®, AIX®, MQSeries® International Business Machines Corporation Microsoft®, Windows® Microsoft Corporation Java™, Solaris™, J2EE™, JRE™, JVM™,Sun™

Sun Microsystems, Inc.

Firefox® Mozilla Pentium™ Intel Corporation Apache® The Apache Software Foundation The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them.

License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice. This software and any copies thereof may not be provided or otherwise made available to any other person. No title to or ownership of the software and associated documentation is hereby transferred. Any unauthorized use or reproduction of this software or documentation may be subject to civil or criminal liability. The information in the software and documentation is subject to change and should not be construed as a commitment by Rocket Software, Inc. Restricted rights notice for license to the U.S. Government: Use, reproduction, or disclosure is subject to restrictions as stated in the “Rights in Technical Data-General” clause (alternate III), in FAR section 52.222-14. All title and ownership in this computer software remain with Rocket Software, Inc.

Note This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when exporting this product.

Contact information Seagull Software Europe Korte Parallelweg 1 3311 JN Dordrecht The Netherlands Tel: +31 78 632 2800 Fax: +31 78 613 8134 Seagull Software U.S. 3340 Peachtree Road, NE Atlanta, GA. 30326 USA Tel: +1 (404) 760-1506 Fax: +1 (404) 760-0061 Web Site: www.seagullsoftware.com For Seagull Software customer support and product downloads visit the Rocket Software Customer Portal at: https://www.rocketsoftware.com/support/

http://www.seagullsoftware.com/

https://www.rocketsoftware.com/support/

CONTENTS Welcome to J Walk Native Server......................................................................................................... 1

1 Introduction ...................................................................................................................................... 1 Introduction .......................................................................................................................................... 1 What is J Walk Native Server?.......................................................................................................... 1 If You Have a Previous J Walk Server Version.............................................................................. 2 When Uninstalling a Previous Version ............................................................................................ 2 Operating System and Requirements................................................................................................ 2 J Walk Native Server Package........................................................................................................... 3 Note ....................................................................................................................................................... 3

J Walk Clients and J Walk Native Server........................................................................................... 4 2 Client Issues to Consider ................................................................................................................ 4

Introduction .......................................................................................................................................... 4 Client Installation ................................................................................................................................ 4 Client Connect Mode Types – Direct Connect................................................................................ 4 Client Connect Mode Types - Server Connect................................................................................ 5 More about Server Connect Mode .................................................................................................... 5 About Served Windows Clients ........................................................................................................ 5 How Served Windows Client Automates Software Updates ........................................................ 6

Preparing the iSeries Environment....................................................................................................... 7 3 Setting the iSeries Environment .................................................................................................... 7

Introduction .......................................................................................................................................... 7 Known Issues ....................................................................................................................................... 7 Preparing and Setting up the iSeries Apache Web Server ........................................................... 10 How to Configure a J Walk Server Environment ......................................................................... 15 How to Configure a J Walk Server Environment – Using an ActiveX Client Control ........... 16 Parameters: ......................................................................................................................................... 16

Installing J Walk Native Server........................................................................................................... 17 4 Automatic Installation Procedures .............................................................................................. 17

Introduction ........................................................................................................................................ 17 Available iSeries Compiler Versions.............................................................................................. 17 Automatic Installation....................................................................................................................... 18 Installed Files and Directories ......................................................................................................... 24

5 Manual Installation Procedures ................................................................................................... 25 Introduction ........................................................................................................................................ 25 Prior Installation Checks .................................................................................................................. 25 Manual Installation Example ........................................................................................................... 25 Manual Installation of the SEAGULL Native Server via Shared Folder .................................. 26 Alternate Manual Installation Procedure for via Shared Folder ................................................. 27 Manual Installation Procedure on TCP/IP ..................................................................................... 29 Customized Native Server Install.................................................................................................... 31

J Walk Server and Component Registration.................................................................................... 34 6 Registration Wizard....................................................................................................................... 34

Introduction ........................................................................................................................................ 34 Overview............................................................................................................................................. 34 The Registration Wizard................................................................................................................... 34 Getting the Host Serial Number ...................................................................................................... 35 Using the Registration Wizard......................................................................................................... 37 Activating a Request on Another Machine .................................................................................... 39

Submitting a Request via the Internet............................................................................................ 40 Submitting a Request via E-mail ..................................................................................................... 42 Saving a Request To File.................................................................................................................. 45

Installing Additional Components ...................................................................................................... 46 7 Installing the LMS, Collector or DAS........................................................................................ 46

Additional Components .................................................................................................................... 46 Installation Procedure ....................................................................................................................... 46

J Walk Server Commands for the iSeries ......................................................................................... 47 8 Commands for J Walk Native Server ......................................................................................... 47

Native Server Commands................................................................................................................. 47 How to Start the Server..................................................................................................................... 48 Starting the Native Server Using the PROFILE Name as the JOBNAME ............................... 49 How to Stop the Server..................................................................................................................... 50 How to Stop a One PROFILE under a JOBNAME...................................................................... 51

9 Using J Walk Server...................................................................................................................... 53 Starting the Java Client ..................................................................................................................... 53 Java Console and Log: ...................................................................................................................... 53 How to Deploy Your Package File ................................................................................................. 53

10 Command Line Parameters ...................................................................................................... 55 Overview............................................................................................................................................. 55 Command Line Parameters .............................................................................................................. 55

Administering J Walk Server............................................................................................................... 56 11 Administering J Walk Server................................................................................................... 56

What is the Server Management Console (SMC)? ....................................................................... 56 Starting the Server Management Console...................................................................................... 56 SMC Administration Commands .................................................................................................... 57

Using J Walk Native Server.................................................................................................................. 61 12 An Example ................................................................................................................................ 61

Introduction ........................................................................................................................................ 61 About the Example Application ...................................................................................................... 61 Start the Example Native Server and Client .................................................................................. 61 Examining Files Used by Example Server..................................................................................... 62 Example Using Server Connect J Walk Windows Clients .......................................................... 63 Running the Default Server Together with the Example Server................................................. 64

Advanced Users........................................................................................................................................ 65 13 Advanced Features .................................................................................................................... 65

Overview............................................................................................................................................. 65 SocketManagerStrategy Setting ...................................................................................................... 65

Log Files..................................................................................................................................................... 66 14 Server Log Files......................................................................................................................... 66

Overview............................................................................................................................................. 66 Server Log Files................................................................................................................................. 66 Troubleshoot Log .............................................................................................................................. 66 Stack trace/dump file......................................................................................................................... 67

Further Information ............................................................................................................................... 68 15 What to do next .......................................................................................................................... 68

Overview............................................................................................................................................. 68 What To Do Next .............................................................................................................................. 68 Customer Support and Service ........................................................................................................ 68

J Walk Server for iSeries Administration Guide

1

Welcome to J Walk Native Server

1 Introduction

Introduction This document guides you as you set up J Walk Native Server. The following

sections will help you get started with J Walk Native Server. This document will give information about the following major sections: • Installing J Walk Native Server and its components. • Getting a license for J Walk Native Server and its components • Configuring J Walk Server and its components • Maintaining and managing J Walk server and its components.

What is J Walk Native Server?

J Walk Server for iSeries is better known as J Walk Native Server. J Walk Native Server is a runtime server that processes a request from the Windows or Java Client, invokes the host application and returns the application’s output as a response. J Walk Server is a PC-based, point-and-click developer’s toolkit for building Windows and Java GUI clients for existing iSeries applications, connecting them to the Web, integrating them with other applications, enhancing them with new client-side functionality, and serving them on-demand for easy maintenance. All this is accomplished with no changes to existing mainframe code. After J Walk Native Server has been installed, you will need to configure the settings of J Walk Server. After the J Walk Native Server has been started, you can administer it remotely via the Secure Management Console. There will be several points concerning the use of J Walk Clients with J Walk Native Server. These points will be covered under chapter ‘J Walk Clients and J Walk Native Server’.

Continued on next page


2

General Information

If You Have a Previous J Walk Server Version

If you have a previous version of J Walk Server installed on your iSeries, and you wish to : • Install the server into a new library, stopping the existing running server is not

necessary. • Install the new server into the same library as the existing server and therefore

overwriting the existing server, stop the existing running J Walk Server and uninstall it before installing the new version.

When Uninstalling a Previous Version

Please note that the uninstall process does not remove changed files. Consequently, any previous J Walk Server configurations stored in JWALK.INI file remains on the hard disk after the uninstall process.

Operating System and Requirements

Before initiating a J Walk Native Server installation, make sure the requirements below are fulfilled:

Part Function Operating System RISC System i V5R2 or higher

Other Requirements • Ethernet or IBM Token Ring Card

• TCP/IP Services • Apache Web Server* • IBM NetVista Thin Client Manager V2R1 or higher

(if using IBM Network Station devices among the clients you are serving)

*HTTP Web Server is no longer supplied with iSeries version V5R3M0. Apache Web Server is supplied in its place.



3

General information, continued

J Walk Native Server Package

The J Walk Native Server package consists of three components:

Part Function J Walk Native Server (communicates to Java Clients and iSeries)

The complete Native Server can be automatically installed and consists of a native iSeries program, installed in library <SEAJWK>, and various execution files, installed to directory /SEAJWK.

Java Client(includes supporting graphics and example files)

Key Client files installed are the: • JWALK.JAR(For all other browsers and JVMs, includes Java

Bean) • RESOURCES.JAR (Product Signature images used by Java

Client) • Some additional "class" files are also installed including JFF

font files. Start a Java Client by opening the JWALK.HTML page accessed by supplying the Domain Name (specified at installation). All of these files are made available via the Apache Web Server.

ActiveX Clients (include Client control and Client software)

JWALKX.HTML and JWALKXS.HTML startup pages, and compressed, signed Windows Client software can be installed on your iSeries and made available to ActiveX-enabled browsers by entering a Web Server (Apache) "Domain Name" enabling access to install and update facilities.

Note Remember each Client package is made accessible by using the HTTP

Server. Client startup HTML pages (JWALK.HTML and JWALKX.HTML) are physically installed into a directory (/JWALK) on the iSeries. The remainder of each selected Client is installed to individual subdirectories. These files are then "made public" for use by browsers when a valid HTTP Domain Name is entered in the "address" path.


4

J Walk Clients and J Walk Native Server

2 Client Issues to Consider

Introduction Since Clients need to access the host, there are several issues to be considered when

installing J Walk Native Server: 1. Initial installation of Client and Severs 2. ‘Connect mode’ type used when running the Client. 3. Served Windows Clients

Client Installation

Installation of Clients can be performed in two ways: • Locally with media or from a shared network (on local area networks, etc). • Install a J Walk Server on the box where you have an Apache Web server and

install Clients from there whenever authorized users browse there. Note: Web servers typically provide a ‘timeout’ attribute that can abort a download process (when the value is exceeded). The download time for a 4.5MB Client is dependent on the network connection. When connecting over a modem, the time can increase considerably. Typically, the timeout is set for approximately 20 minutes; but in some cases with modem traffic, it may be necessary to increase this setting on your Web server.

Client Connect Mode Types – Direct Connect

To make a connection to J Walk Server, there are two ways of doing this. It involves two ‘connect mode’ types that are described below. Direct Connect Using a Direct Connect mode results in the updates on the Package file relying on the usage of shared network drives, control files (JWC) that will facilitate complete updating of ALL software when necessary, before running.



5

Client Issues to Consider, continued

Client Connect Mode Types - Server Connect

Server Connect Using Server Connect mode enables you to specify a path where the Client installation details are defined. The Client then runs in a mode where it makes requests for updated files when needed and caches the files locally. To use Server Connect Mode, you must use the following: • http:// - Clients can be provided with a HTTP path to install and update

facilities. Example: http://myserver/ …/ example.jwc • /$: - Clients can be provided with a shared logical path to install and update

facilities. Example: /$N:\Jwalk\example.jwc

More about Server Connect Mode

Server Connect Mode provides Clients with a ‘smart’ dynamic file-level version checking mechanism. Updates are explicitly made for the required files. Whether a complete JWR is required or just a new GIF image for an existing panel, Clients running in "Server Connect" mode manage these changes. Additionally, Server Connect mode enables "seamless" administration and a "user authorization" - level of control for your environment.

About Served Windows Clients

When you select to perform Client and Package installations from an Apache Web Server and you want the benefits of running Clients in "Server Connect" mode with that Apache Web Server (for example: "Zero Administration" and Automated updating of Clients and Packages), then you want a "Served Windows Client" solution! An ActiveX-enabled browser and the J Walk ActiveX Windows Client facilitate this combination without any programming! Reliance on the MS IE version 5 or higher or Netscape (based on Firefox) browsers is a requirement when deploying this solution.



6

Client Issues to Consider, continued

How Served Windows Client Automates Software Updates

The Seagull Software J Walk Server solution includes methods for automating software updating of both: The Windows Client (via ActiveX Client control) • Using the ActiveX Client control enables an industry standard way of checking

and updating the J Walk Windows Client software. • Additionally, it is possible to startup the Windows Client with parameters

(optionally, place a configured INI file with the ActiveX control software to ensure use of a specified [section] configuration).

• Finally, the ActiveX Client control has the option to start the Windows Client embedded in an ActiveX container (e.g. a browser) or as a "regular" window type display.

Your J Walk Package files (via startup parameter enabling "Server Connect" mode) • Using Server Connect mode enables "pointing" at a control file (JWC) which is

specified as a startup property (using the /$ 'logical_path' or directly entering the "Domain Name" where the control file is made public. Note that this an 'http_webserver_IP_address'). This mode enables another way to deploy your control files.

• The ActiveX Client can invoke "Server Connect" mode as an argument within its startup parameters. Optionally, a configured JWC file can be placed with the ActiveX Client software on the Web Server.

The "power" in this solution comes from combining the two methods to your level of needs. This makes up the "Served Windows Client" solution.


7

Preparing the iSeries Environment

3 Setting the iSeries Environment

Introduction Before installing J Walk Native Server, there are a few known issues which you

should be aware of. At the end of this chapter, there will be a step by step procedure to configure the iSeries environment before installation.

Known Issues The following are known issues that you should be aware of.

Known Issue Description Auxiliary Storage Requirements The native Server (SEAJWK library) requires

about 9MB. The remaining components require the following space: • \SEAJWK (Administration files) – 6MB • \JWALK (Java Client) – 2MB • ActiveX Client - -20MB • Small ActiveX Client – 10MB

Version 3 Upgrade Notice With the J Walk Native Server (version 3), your package file directories should also contain your panel file images. Previously, all package file panel images (*.GIF, .JPG) where required to be stored centrally within in the "Java Client class" directory below "\JWALK." It is recommended to re-install all your application package sets to separate directories (no longer a sub-directory of \JWALK) to ensure the images are completely installed with the remainder of your package file set(s). After re-installing, consider deleting all image files within the Java Client Class directory (*.GIF/.JPG).



8

Setting the iSeries Environment, continued

Known Issue Description Unsupported features If you are familiar with J Walk Server for NT,

the following features are not supported: • Limited on-line help is available • A Configurations Assistant • A monitoring tool to see for instance when

it started and how many clients are connected

• Emulator Emulator (EE) for demo purposes • 3D graphics support.

Native Server Troubleshoot Report and Logging

To assist in troubleshooting, the Native Server provides a "Troubleshoot" report function for creating a "dump" to send to Seagull Software Support Services. Note that this command instructs all native servers that were started from library SEAJWK to produce a trouble shooter log in the ASCII file with name JWALK.LOG in directory SEAJWK. • To create the dump, invoke the iSeries

command: "SEAJWK/DMPJWKLOG" and then view printed file JWXXX.LOG in directory \SEAJWK, where "XXX"= the "ServerPort" value specified in the JWALK.INI. • Logging of any exceptions made between

the Server, the application, the LMS and the Clients. When such messages (presented as pop-ups on the J Walk Server for NT) occur, they are logged in the Native Server job log and also sent to QSYSOPR. The message indicates the Server version, reported message and message ID number.



9


Known Issue Description Browser support • Browsers supporting Java Clients at this time require

compliance with JVM 1.4.2. Examples are the MS Internet Explorer v5 or higher or Netscape (based on Firefox).

Note: Print functionality requires MSIE 4.01 Service Pack 1. When applied, the Microsoft Virtual Machine should be "4.79.0.2424" or higher. You can inspect this by choosing View|Java Console. Print functionality also requires use of signed CAB files. • Browsers supporting ActiveX Client Controls require ActiveX

support. Examples are MSIE 5 or higher and Netscape (based on Firefox).

• Java Clients running on a Mac require Mac OS 8.1 or later.



10


Preparing and Setting up the iSeries Apache Web Server

Note: IBM HTTP Server is no longer supplied with iSeries version V5R3 and higher. Apache Web Server is supplied instead. With Apache Web Server, a new HTTP configuration needs to be created or the existing HTTP configuration must be migrated to the Apache Web Server. Perform the steps below to create a new HTTP configuration on the Apache Web Server for i5/OS. Step Action

1 Make sure the *Admin HTTP Server is running on the iSeries. Access the IBM HTTP Server for iSeries Admin by going to the following URL: http://host.ip.address:2001/ Result: The browser displays the Apache Web Server’s administration page.

2 On the IBM Web Administration for i5/OS page, click on Manage tab. Result: The tab displays additional tabs. Click on the HTTP Servers tab.



11


Preparing and Setting up the iSeries Apache Web Server, continued

Step Action 3 From the menu list on the left pane, click on General Server

Configuration from the Server Properties group. - Select Yes from the Autostart drop down list. - In the Document root field, specify the directory that the web server

will serve files from. - Enter a server name and port that that the Web Server will use. The

server name and port may be added to the table displayed below the Server name group.

Click Apply, then OK to save the settings for the new configuration.



12



Step Action 4 From the menu on the left pane, click on Container Management from the

Server Properties group. - Click on the Directories tab on the displayed Container Management

page. - Add a new directory to the Directory table by clicking on the Add

button and entering a directory path. Click Apply, then OK to save the settings for the new configuration. Make sure that the directory path will be mapped to the IFS.



13



Step Action 5 From the menu on the left pane, click on URL Mapping from the Server

Properties group. - Click on the Aliases tab on the displayed URL Mapping page. - Add a new Alias type to the table by clicking on the Add button and

entering a URL path and Host directory/file. The path and directory should refer to the location where the server files are stored.

Click Apply, then OK to save the settings for the new configuration. Make sure that the directory path will be mapped to the IFS.

6 Alternatively, the same procedure listed in the steps above may be performed using the Add a Directory to the Web wizard; from the HTTP Tasks and Wizards group from the menu.



14



Step Action 7 To start the Apache web server, click on the Start button located on the top

of the page. Result: The status (displayed next to the Start button) of the web server changes to Running.

8 Note that when the configuration is created, either place a copy of the JWalk directory in the web root directory specified in the Apache server configuration, or include a Global Setting in the HTTP Server configuration such as: <Directory /jwalk> Order Allow,Deny Allow From all </Directory> Alias /jwalk/ /jwalk/ The configuration above can be viewed using the Tools | Display configuration file menu command; displayed in the left pane of the administration interface.

9 When the Global Setting is used, there is no need to refresh the JWALK directory in the root every time the J Walk Server is upgraded.

10 The QTMHHTTP user must have sufficient authority (*RX) on the JWALK folder on the iSeries IFS.



15


How to Configure a J Walk Server Environment

Default Installed File Configuration consists of modifying a few files to complete the "links" between Java Client and Server as well as Server and Host System.

Step Action 1 The Web Server Installation Path for the client should like this:

/JWALK/JWALK.HTML for Java Clients /JWALK/JWALKX.HTML and JWALKXS.HTML (for Served Windows Clients)

2 Assign a Server port number (per J Walk Server instance). Change directory to the installed /JWALK directory. Within this directory, is the installed JWALK.HTML file. Each J Walk Server needs its own JWALK.HTML file. Each JWALK.HTML file must contain at least the following: theApplet.setSize(800, 600); theApplet.addParameter('Port', '400');

3 You may need to modify a JWALK.HTML file to specify another port number than the default value, "400."

4 For the Installation Path for J Walk Native Server software (default INI file location)- In the SEAJWK directory, there is the jwalk.ini file containing a section specifying the details for use (including the example application): \SEAJWK\JWALK.INI: note the section called: "[EXAMPLE]".

5 Assign the same Server port number (per J Walk Server instance). The IP address of the iSeries Host is also required. Modify the INI file (within the specified Server section) identifying the port number defined during installation.



16


How to Configure a J Walk Server Environment – Using an ActiveX Client Control

If you intend to use the ActiveX Client control, there are also parameters that require modifying in the JWALKX.JS file. Parameters: Specify Windows Client startup parameters to be used when the ActiveX Client control starts the Client. Additional parameters are not required.

• Startup parameters: When a Windows Client is started with a "/h123.456.789.0" command from a shortcut property, the equivalent for the ActiveX Client control could be:

c.Parameters ="/h123.456.789.0";

• SetupLocation: When the ActiveX Client control determines an update must occur, this is the parameter to define where the control goes to execute a new install. For example:

c.SetupLocation=”http://123.456.789.0/JWALKX/JWALX.EXE”;

http://123.456.789.0/JWALKX/JWALX.EXE


17

Installing J Walk Native Server

4 Automatic Installation Procedures

Introduction This chapter will help you install and configure your copy of J Walk Native Server.

J Walk Native Server can be installed either through an automatic procedure or through manual installation procedures. Installing from the provided J Walk Server CD-ROM provides you with these 2 options.

Available iSeries Compiler Versions

Starting from 4.1C4 onwards, there will be two available versions of J Walk Server for the iSeries. These versions are: • J Walk Server for iSeries V4Rx • J Walk Server for iSeries V5Rx Using either one of these versions means that: • V4Rx versions will run on both V4 and V5 but not with V6, • V5Rx versions will run on V5 (minimum version being V5R3) and is

compatible with V6, • V5Rx versions can be used together with SSL from version 4.1C8 and higher. Note that the compiler versions of the iSeries are now included into the troubleshoot log. For example: Machine name : OS : iSeries 400 V5R4M0 LPAR:3 Model 9406, Type 520-7453 Command line : \SEAJWK\JWKSVR -ETELNET Compiler version: 600 The compiler version refers to either one of the following: • 300 refers to V4Rx versions • 600 refers to V5Rx versions



18

Installing J Walk Native Server on Your PC,continued

Automatic Installation

Complete the following steps to install J Walk Native Server on your PC:

Step Action

1 Browse to the J Walk CD. 2 Open the J Walk Server for iSeries V4Rx or V5Rx. 3 Double-click on the setup.exe to launch the J Walk Server for iSeries install.

Result: The LegaSuite InstallShield Wizard appears. 4 Click on the Next button.

Result: The Software License Agreement dialog is displayed. 5 Click on the Yes button.

Result: The Installation Procedure dialog appears. 6 The Destination Folder dialog appears. By default, J Walk Server for iSeries

V4Rx is installed into: C:\Program Files\SEAGULL\J Walk Server for iSeries V4Rx\<version number> You may specify another destination if required. Note: The same directory path is used and installed into the J Walk Server for iSeries V5Rx folder if J Walk Server for iSeries V5Rx is installed.

7 When the Configuration dialog appears; enter the iSeries settings, J Walk Server and Webserver settings: iSeries Address: IP adress of name of the host. Port: Port number of the host . J Walk Server Port: Port number of J Walk Server IIS Web Server Settings Domain: Change the domain name of the IIS Web server if required. Default value is http://localhost. Click Next to continue.



19


Step Action

8 The Installation Procedure dialog prompts you to choose whether you want to perform a Complete or a Custom installation. Choose the Complete option. Click on the Next button. Result: The Ready to Install the Program dialog appears. The following applications will be installed: • J Walk Server, Help Files, Fonts and Additional Language Support

(Dutch/French/Italian/German/Spanish/German/Japanese/Russian) • HTML Client (Java) • Java Client (Swing-based) • ActiveX Client The default installation directories for the fonts and languages are: • Fonts: C:\Program Files\SEAGULL\J Walk Server for iSeries

V4Rx\seajwk\fonts • Languages: C:\Program Files\SEAGULL\J Walk Server for iSeries

V4Rx\seajwk Note: The default installation directories for the clients are: • HTML Client (Java): C:\Program Files\SEAGULL\J Walk Server for

iSeries V4Rx\web\htmlservlet • Java Client: C:\Program Files\SEAGULL\J Walk Server for iSeries

V4Rx\jwalk\ • ActiveX Client: C:\Program Files\SEAGULL\J Walk Server for iSeries

V4Rx\jwalkx\ Note: For J Walk Server for iSeries V5Rx, the same directory path is used for the installed files and installed into the J Walk Server for iSeries V5Rx folder.



20


Step Action

9 When the installation procedure is complete, you are introduced to the Install Shield Wizard Completed dialog. Two options are available: • Install J Walk Server for iSeries now – Select this option if a J

Walk Server for iSeries license is already available. If not, you will need to activate the Registration Wizard to request for a license in order to use the J Walk Server for iSeries.

• Registration Wizard: Click on the button to launch the Registration Wizard and request for a license. Once registered, you may start using installing J Walk Server for iSeries directly on the host.



21


Step Action

10 The concluding dialog provides several options. 1. Exit the dialog without starting the install on the host or using the

Registration Wizard

• If either option is not selected, click Finish to exit the installer. You may use the Registration Wizard or install the Server on the iSeries at a later time via the program shortcuts.

2. Launch the install J Walk Server on the host directly • Select the Launch J Walk Server on iSeries option to install the

server directly on the host if you already have a valid license. Click Finish to start the installation on the host.

• Enter the following information: • IP address of the iSeries, • user name, • password • Install to Library • Install to directory • FTP port • Passive mode to begin the file transfer. Click OK.

3. Request for a license first, then launch the Server install on the host • Click on the Registration Wizard button to request for a license.

Once a license is received, select the Install J Walk Server on iSeries option and click Finish to exit the dialog and start the installation.

• Enter the IP address of the iSeries, user name, password, Install to library, Install to directory and FTP port to begin the file transfer. Click OK.

Note: Once a license has been saved to the installation directory, the license must be copied over to the seajwk folder as specified in the Install to Library field. When the server for the iSeries is installed, the files in the /bin folder will be ftp-ed to the host. The Make sure that the license is in the SEAJWK directory once ftp-ed or copied over to the host.



22


Step Action 11 At the same time, the following program shortcuts have been added to the

Start Menu’s All programs list – LegaSuite | J Walk Server for iSeries :

• J Walk Server Registration

• J Walk Server Registration • J Walk Server HTML Registration (covered in the HTML User

guide PDF).

• J Walk ActiveX Client

• J Walk HTML Client (Java)

• J Walk Java client

• Install J Walk Server on iSeries

Once the Install J Walk Server for iSeries now option is selected, the FTP Connection settings dialog appears. The FTP Connection Settings dialog requires the following information.

Option Description

TCP/IP Address The IP address of the iSeries machine.

User Name The user name you use to connect to the iSeries machine. Note that the permissions associated with this ID will be used to set the permissions of all transferred files and directories (UMASK). The minimum must be 744 (r w x r - - r - -)

Password The password you use to connect to the domain server

Install to Library The library where the native server is installed. By default this is SEAJWK.

Install to directory

The host directory to which the files will be copied. By default this is JWALK. You may specify another directory name if necessary.

FTP Port The port on which FTP file transfers take place. We recommend that you use the default FTP port setting of 21

Passive Mode Enabling this checkbox depends on network installation and the existence of a client-side firewall. Passive mode is recommended as it solves the problem of firewalls filtering the incoming data port connection from the server



23


Step Action 12 Click on the OK button.

Result: The J Walk Server for iSeries 400 Installation dialog appears 13 This dialog displays the progress of the FTP file transfer. Select

Details to display all of the installation steps as they take place, as shown in the following example: Result: You are now ready to use the native Server you have just installed.



24


Installed Files and Directories

Once the initial install has completed, the following files and sub-directories are created in the installation directory - C:\Program Files\SEAGULL\J Walk Server for iSeries V4Rx/V5Rx.

• \bin directory consist of sub-directories as well as the FTP executable used to ftp the files in the /bin folder to the host.

• \bin\jwalk sub-directory contains the following folders

• htmlclientservlet – Contains the application files for the HTML (JSP) client • JWALKAPP – Contains the files for the EXAMPLE application • JWALKX – Contains the files for the ActiveX Client

• \bin\seajwk contains the J Walk Server application files.


25

5 Manual Installation Procedures

Introduction This section will inform you on how to perform a manual installation and alternate

manual installation procedures of J Walk Server on the iSeries.

Prior Installation Checks

Before installing via manual installation, you need to check the following: • Check for existing Native Servers:Determine if there is already a Seagull

Native Server on your iSeries by checking for the presence of library <SEAJWK> and directory /SEAJWK. You must save any user changes before removing this library and folder.

• OS Requirements:The Native Server requires RISC(V4Rx and higher) operating system.

• Web Server: HTTP Web Server is no longer supplied together with iSeries version V3Rx and higher. Apache Web Server is supplied with the iSeries instead.

• iSeries shared folder: If you are using Client Access and have not yet connected to the iSeries shared folders for installing, it will be necessary for you to connect DRIVE I: to the iSeries system folder called QDLS. The connection should look like : \\NLSBSD01\QDLS

• FTP over TCPIP: If you are using TCP/IP connections between your PC and the iSeries, you can connect and transfer the SEAGULL Native Server software for installation by using the File Transfer Protocol(FTP).

Manual Installation Example

An example will be made to show how manual installation takes place. With this example, it is assumed the F:\ is a drive containing the temporary install directory. This is not a step by step installation description! When all commands are performed, the server should be installed. The instructions below show what is prepared for the example.

Step Action 1 Assign a drive letter to the iSeries filesystem

E.g. type: NET USE R: \\NLSBS003 Note: A manual install requires you to assign a temporary storage directory (in this case, F:).

2 Copy the files with the following commands: XCOPY F:\JWALK R:\JWALK\ /S XCOPY F:\SEAJWK R:\SEAJWK\ /S

3 The resulting subdirectories (on R:): \JWALK\*.* (Contains the java classes for the client) \SEAJWK\*.* (Contains the runtime files, gif image files and JWALK.ini file).



26


Manual Installation Procedures, continued

Manual Installation of the SEAGULL Native Server via Shared Folder

In order to install this, the security officer should have a PC connected to the iSeries using PC-Support with the shared folders function enabled. This installation procedure has been found to be suitable for about 90% of customers. If the procedure fails due to high security or accounting limitations, then you should try the alternate installation procedure as described in section ‘Prior Installation Checks’. For the normal installation procedure, follow these steps :

Step Action

1 Log on as QSECOFR. 2 Copy the *.bin files from the root of the temporary directory into the

shared folders. (i.e. XCOPY F:\*.BIN I:\TEMP\). 3 On the iSeries the following CL commands should be executed.

Note that you should do this as QSECOFR. If you use another User id then please make sure that this user id has the necessary authorizations (*IREXX and *BREXX are needed to execute JWKINS). CRTSRCPF FILE(QTEMP/QREXSRC) CPYFRMPCD FROMFLR(TEMP) TOFILE(QTEMP/QREXSRC) FROMDOC(JWKINS.BIN) TOMBR(JWKINS) STRREXPRC SRCMBR(JWKINS) SRCFILE(QTEMP/QREXSRC) DLTF FILE(QTEMP/QREXSRC)

4 On completion, the following message should appear. "JWALK SERVER IS INSTALLED IN LIBRARY SEAJWK" The Seagull J Walk Native Server is now installed. NOTE:If an error occurs, then you should try the alternate installation procedure in section ‘Prior Installation Checks’.

5 Delete temporary files. On the PC the files may be deleted from the directory TEMP and the directory may be deleted. Example: DEL I:\TEMP\*.* RD I:\TEMP



27



Alternate Manual Installation Procedure for via Shared Folder

In the alternate installation procedure, CL commands are used where possible. This means that you can understand what is being done and take corrective steps where necessary. The only step that cannot be done using CL commands is the conversion of the database file to a save file. To do this a simple REXX procedure is used. For the alternate installation procedure, follow these steps : Step Action

1 Log on as QSECOFR. 2 Copy the *.bin files from the root of the temporary directory into the shared

folders. (i.e. XCOPY F:\*.BIN I:\TEMP\). 3 On the iSeries the following CL commands should be executed.

Note that you should do this as QSECOFR. If you use another userid then please make sure that this userid has the necessary authorizations: *IREXX and *BREXX are needed to execute CPYSAVF. CRTSRCPF FILE(QTEMP/QREXSRC) CPYFRMPCD FROMFLR(TEMP) TOFILE(QTEMP/QREXSRC) FROMDOC(CPYSAVF.BIN) TOMBR(CPYSAVF) CRTSAVF FILE(QTEMP/JWKSAVF) AUT(*ALL) CRTPF FILE(QTEMP/JWKTEMP) RCDLEN(528) MBR(*FILE) MAXMBRS(*NOMAX) SIZE(*NOMAX) CCSID(*HEX) ALWUPD(*YES) AUT(*ALL)

4 If this is a first time installation, create the SEAJWK library: CRTLIB LIB(SEAJWK) TEXT('JWALK SERVER') AUT(*USE) CRTAUT(*CHANGE) otherwise you should use the existing SEAJWK library: CLRLIB LIB(SEAJWK)



28



Step Action

5 If you receive a message like 'Output queue in use', you may safely ignore this message or remove spoolfiles from this output queue and repeat command 'CLRLIB LIB(SEAJWK)'. CHGOBJD OBJ(SEAJWK) OBJTYPE(*LIB) TEXT('JWALK SERVER') continue here: CPYFRMPCD FROMFLR(TEMP) TOFILE(QTEMP/JWKTEMP) FROMDOC(SEAJWK.BIN) TOMBR(*FIRST) MBROPT(*REPLACE) TRNTBL(*NONE) TRNFMT(*NOTEXT) STRREXPRC SRCMBR(CPYSAVF) SRCFILE(QTEMP/QREXSRC) PARM('JWKTEMP JWKSAVF') RSTOBJ OBJ(*ALL) SAVLIB(SEAJWK) DEV(*SAVF) OBJTYPE(*ALL) SAVF(QTEMP/JWKSAVF) OPTION(*ALL) FILEMBR((*ALL *ALL)) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(SEAJWK) RSTASP(*SAVASP) OUTPUT(*NONE) At the end you should see a message like: "xxx objects restored from SEAJWK to SEAJWK" DLTF FILE(QTEMP/QREXSRC) DLTF FILE(QTEMP/JWKTEMP) DLTF FILE(QTEMP/JWKSAVF)

6 Delete temporary files. On the PC the files may be deleted from the directory TEMP and the directory may be deleted. Example: DEL I:\TEMP\*.* RD I:\TEMP



29



Manual Installation Procedure on TCP/IP

Follow the instructions below to install J Walk Server on iSeries manually on TCP/IP.

Step Action 1 Log on as QSECOFR. 2 On the iSeries the following CL commands should be executed.

Note that you should do this as QSECOFR. If you use another userid, please make sure that this userid has the necessary authorizations: *IREXX and *BREXX are needed to execute CPYSAVF. CRTLIB LIB(TMPLIB) CRTSRCPF FILE(TMPLIB/QREXSRC) CRTPF FILE(TMPLIB/JWKTEMP) RCDLEN(528) MBR(*FILE) MAXMBRS(*NOMAX) SIZE(*NOMAX) CCSID(*HEX) ALWUPD(*YES) AUT(*ALL)

3 On your local PC, the following commands should be executed: Go to the temporary directory. F: CD\

4 Start your File Transfer Protocol Software: FTP Now the FTP program will start. Connect to your iSeries system. In most FTP versions, this can be done by typing: OPEN

5 Now, the program will ask you the system name you want to connect to and which user-name and password to use. Make sure to connect to your iSeries as QSECOFR. After you typed the system name, user name(QSECOFR) and password, you will see the FTP prompt. This prompt usually looks like : ftp> Although there is a wide variety in FTP versions, each having its own user interface, the following commands should work in most FTP versions. After the ftp> prompt, type the following: CD TMPLIB If your FTP version doesn't support this command, use CHDIR TMPLIB instead. Type: ASCII or another command that will put FTP in ASCII mode. Then type: SEND



30



Step Action

6 FTP now will ask for the local filename (the file on your PC) and the remote filename (the file on the iSeries). The local filename should be: \JWKINS.BIN The remote filename should be: QREXSRC.JWKINS SEND The local filename should be: \JWKINS2.BIN The remote filename should be: QREXSRC.JWKINS2

7 Now, the files will be transferred to your iSeries. After this, type: BINARY Or another command that will put FTP in BINARY mode. Now type: SEND FTP will ask for a local and a remote filename again. The local filename should be \SEAJWK.BIN. The remote filename should be JWKTEMP.SEAJWK

8 When the file is transferred, you can leave FTP by typing:QUIT 9 After the files are transferred to the iSeries, you should type the

following commands on your iSeries:Again, please note you should do this as QSECOFR. STRREXPRC SRCMBR(JWKINS) SRCFILE(TMPLIB/QREXSRC) PARM('TMPLIB')

10 If during execution next message appears: "Start of terminal session." "Error in line xxx: Invalid character in program." "Press ENTER to end terminal session." The FTP file transfer has added an extra line to both REXX source files JWKINS and JWKINS2. Remove these lines by means of an iSeries editor and give the following command again: STRREXPRC SRCMBR(JWKINS) SRCFILE(TMPLIB/QREXSRC) PARM('TMPLIB')

11 On completion, the following message should appear. "JWALK SERVER IS INSTALLED IN LIBRARY SEAJWK" The Seagull Native Server is now installed. DLTLIB LIB(TMPLIB)



31


Customized Native Server Install

Available since 4.1C1 A customized Native Server install can be done in this release. The Native Server install can be installed in a different directory structure. This involves changing the values in the FTP Connection Settings dialog.

Step Action

1 Start the Native Server install from the product CD. 2 Enter the User name and Organization that forms the Customer

Information dialog. Click Next to continue. 3 The dialog will show the default installation folder.

The first time the Native Server is installed, it is usually to the default installation folder. The default installation folder is C:\Program Files\SEAGULL\J Walk Server for iSeries V4Rx Click Next.

5 In the following dialogs, enter the following information: • iSeries address and port number • J Walk Server port • Domain – applied for the Java client and ActiveX client Click Next to begin the first part of the install.

6 In the Setup Type dialog, select Complete Setup and click Next. 7 Click Install to begin the installation. 8 In the final installation dialog, there are two options:

• Install J Walk Server on the iSeries now: Select this option if a license for the iSeries already exists.

• If you do not have a license yet, click on the Registration Wizard button to request for a new license.



32


Customized Native Server Install, continued

Step Action 9 Click Finish begin installation on the host. The FTP Connection

Settings dialog appears.

10 By default, the native Server will be installed to the SEAJWK library and JWALK directory on the host. To change the native Server install to a different location, change the values in the Install to library and Install to directory fields. Make sure that rest of the fields have the correct values. • Enter the host address to begin installation. • Enter the user name and password to the host.

11 Click OK to begin the installation. 12 When the install begins, click on the Details button.

The Details window will display details of the files transfer; in particular the install path for each transferred file displays the name of the folder name set for the in the FTP Connection Settings dialog.

13 Once the files are transferred, click on the OK button.



33


Customized Native Server Install, continued

Step Action 14 (Optional) You may need to change the host, server, port numbers in

the following HTML files to start the Java client/ActiveX clients. • JWALK.HTML • JWALKX.HTML

15 To check if the native server was installed to the specified directory, • Start the Windows Client with a connection to the host. • Start the Native Server by entering the following command

(installation directory name followed by command to start the native server) on the command line (from Step 9): SEAJWK/STRJWKSVR.

The message : The SEAGULL J WALK SERVER IS BEING STARTED will be displayed on the screen. This means that the customized install was successful!


34

J Walk Server and Component Registration

6 Registration Wizard

Introduction Before you are able to use the J Walk Server and its components on the host, you

must register it in order to use it. Registration involves the user of a unique activation key to install the J Walk Server and its components in order to prevent unauthorized use.

Overview How the Registration Wizard works can be summarized as follows:

1. Receiving an Installation Key (a string of characters) that allows you to apply

for an Activation Key to install the J Walk Server 2. Use the Registration Wizard allows it to: • Gather information about the intended host machine, • Gather registration information about the customer, • Send an Activation Request (saf) file to Seagull Software along with the valid

Installation Key. 3. Validation of the activation request. 4. Receipt of the SEAGULL Activation Key for use with the J Walk Server.

This document only describes how to install the Registration Wizard. For more information on the Registration Wizard, please consult the Registration Wizard online help.

The Registration Wizard

The SEAGULL Registration Wizard is a Windows application that automates the process of Seagull Software product activation. Although it runs on a Windows platform, it can be used to process activation requests for the following platforms: • IBM iSeries • IBM AIX • HP-UX • Sun Solaris • Linux/Intel Please refer to the topic Using the Registration Wizard to see an example activation request using the Registration Wizard.



35

The Registration Wizard, Continued

Getting the Host Serial Number

The Host Serial Number must be available on hand before you start to use the Registration Wizard to register the Server. The Host Serial Number is part of the required fields for the Registration Wizard for J Walk Server on the host. Note: The host system serial number displayed by the SEAGULL product may be different from the serial number displayed by your host during booting time or the manufacturer serial number found on the host's case. Use only the value displayed by the SEAGULL product, not the other values. The steps below show you how to get the host serial number for the iSeries as well as alternative ways to get the host serial number.

Step Action

1 Complete the native Server installation. When the Server is installed on the host without an Activation File or with the wrong activation file, it will not start and an error message (available since 4.1C7) is displayed on line 24 of the screen: “The J Walk Server could not start due to configuration errors (see job log)”.

2 Check the troubleshoot log that is generated automatically in the SEAJWK directory. Open the log and look for the “License file” entry. The host serial number is required to register the Server and to get an activation file. For example: ----------------------------------------------- No License file for : J Walk Server System Serial Number : 12345CD/3 ----------------------------------------------- License file information System Serial Number : 12345CD/3 Alternative Method1 Enter the following command on the command prompt to view the host serial number: DSPSYSVAL QSRLNBR Alternative Method2 Generate a troubleshoot log from the Server Management Console (SMC). Open the generated troubleshoot log and look for the “License file” entry.



36


Getting the Host Serial Number, continued

Step Action 3 Copy the serial number and enter the serial number in the Registration

Wizard’s dialog with the title Host system serial number.

4

Specifying the LPAR Number However, if the current host the Server is installed on uses LPAR, then the LPAR number must be selected from the drop down list. From Step 1, an LPAR number if specified will be appended to the last number of the System Serial Number. A forward slash precedes the LPAR number. Therefore in this example, select ‘3’ from the drop down list as the LPAR number. No LPAR Number For iSeries machines that do not use LPAR, the host serial number number is slightly different. The value ‘1’ indicates no LPAR is used. For example: 12345CD/1 Therefore, you will need to select ‘1’ from the drop down list.

5 Once the host serial number (and the LPAR number) is specified, complete the rest of the steps for registration and save the saf file to the SEAJWK directory.


37


Using the Registration Wizard

Note1: This example assumes that the user possesses the Installation Key. This key is generally issued after the purchase of J Walk and contact with the Seagull Software Order Administrator. Note2: The following examples will generally assume that the Registration Wizard has been started automatically during the installation of the HTML client. If, for some reason, you wish to restart the wizard manually, it will be necessary to specify the following information: • The Product Family • The Product Part • The Platform This information will be requested by the first dialog in the Registration Wizard. This dialog will not appear during the automatic use of the Registration Wizard. Perform the following steps to use the Registration Wizard:

Step Action

1 Follow the online instructions. If you have selected a component that requires an Activation Key, the Registration Wizard dialog will also appear. Click Next.

Result: The SEAGULL Registration Wizard begins.



38


Using the Registration Wizard, continued

Step Action

2 Click on the Next button. Result: The Select Installation Machine dialog appears. Select the following option. Host machine (iSeries,zSeries,Solaris, HP-UX, AIX, Linux) – Use this option for remote activation. Click Next to continue.

3 In the Host system serial number dialog, enter the serial number. You need to enter the target host’s serial number, which will be displayed when you start the SEAGULL product on the host without an Activation File. On some iSeries versions, if the host serial number cannot be viewed, please refer to the serial number specified in the generated troubleshoot log when the server on the host is started without a saf file. Note: The host system serial number displayed by the SEAGULL product may be different from the serial number displayed by your host during booting time or the manufacturer serial number found on the host's case. Use only the value displayed by the SEAGULL product, not the other values.

4 Click on the Next button. Result: The Registration Wizard will gather specific information about the chosen machine for use with the Activation Key. Progress will be indicated on screen. The Registration Information dialog will then appear. Fill out all the fields in the dialog. This information will then be used in the event of installation queries.

5 Click on the Next button. Result: The Activation Request Submit dialog appears. Select the submission method. The methods are: • Direct submission via the Internet • E-mail submission • Saving the Activation Request file for submission at a later date. Please refer to : • Submitting a Request via the Internet if you wish to use this method. • Submitting a Request via e-mail if you wish to use this method. • Saving a Request to File if you wish to save the Activation Request to

file for later use.



39


Activating a Request on Another Machine

Scenarios that may entail activating a request on another machine include activation requests that have been saved to a file because it has not been possible to send them for a variety of reasons. The saved request can be retrieved from another machine to the target machine for the installation of the software. This scenario will include setting up software on this machine and gathering the necessary information from it.

Step Action

1 Activate the Registration Wizard as normal. Click on the Next button. Result: The Select SEAGULL product to activate dialog appears.

2 In this example, we are activating an existing request on another machine, so it will suffice to select the I want to send an existing activation request for another machine check box.

Click on the Next button. Result: The Select Installation machine dialog appears. The Another PC machine-select saved Activation Request check box is automatically selected.

3 Click on the Next button. Result: The Select existing SEAGULL activation request file dialog appears. Use this dialog to browse to the activation request file that you wish to use.

4 Double-click on the file or highlight it and click on the Open button. Result: The Activation Request Submit dialog appears. Select the submission method. The methods are: • Direct submission via the Internet • Email submission • Saving the Activation Request file for submission at a later date. Please refer to topics: • Submitting a Request via the Internet if you wish to use this method. • Submitting a Request via e-mail if you wish to use this method. • Saving a Request to File if you wish to save the Activation Request

to file for later use.



40


Submitting a Request via the Internet

Please ensure you have performed the initial steps outlined in the topic Using the Registration Wizard. Use of this method assumes that you have a direct Internet connection and are connected at the time of the activation request.

Perform the following steps to activate a request using the Internet:

Step Action

1 Select the Activation Request method by checking the appropriate radio button. In this case, it will be the Via Web radio button. Click on the Next button. Result: the Submit by Web screen will display the progress if the activation request.

2 The Submitted by Web screen appears. This dialog will inform you that the

download of the Activation file has been successful. It also displays the directory path. It should be the path specified in the previous topic. Click on the Next button. Result: The Activation Request Summary is displayed. This will display the following information about the request. • The Activation result. • The Machine to which the Activation Key has been submitted. • The Product for which the Activation Key was requested. • Download status.




41

Submitting a Request via the Internet, continued

Step Action

3 Click on the Finish button. Result: You will exit the Registration Wizard and can begin using the SEAGULL product.



42


Submitting a Request via E-mail

If you do not have an Internet connection for some reason, it is not possible to send an Activation Request using the Internet, you can send the request using an e-mail. In this scenario, a request file will be generated, attached to an e-mail and sent to the Seagull Software Administrator. If your machine uses Microsoft Outlook as the default mail client, the request file will be attached automatically. For other clients, it is necessary to browse to the request file and attach it manually to the e-mail. Please ensure you have performed the initial steps outlined in the topic Using the Registration Wizard. Perform the following steps to activate a request using e-mail:

Step Action

1 Select the Activation Request method by checking the appropriate option. In this case, it will be the Via E-mail option. Click on the Next button.

Result: The Submit by Email screen will appear.



43


Submitting a Request via E-mail, continued

Step Action

2 Click on the Next button. Result: if your default mail client is Microsoft Outlook, you will see the following screen.

If your default mail client is not Outlook, you will have to attach the request manually and send the email to the address (mailto:[email protected]).

3 Click on the Send button to send the email to the Seagull Software Order Administrator. Result: The Submitted by email screen appears. Seagull Software will now process the activation request. When the request has been processed, the Activation Key will be sent back to the same address. The processing time can vary, depending on the volume of requests received by the Order Administrator at a given time.


mailto:[email protected]


44


Submitting a Request via E-mail, continued

Step Action

4 Click on the Next button. Result: The Activation Request Summary is displayed. This will display the following information about the request: • The Activation Result • The Machine to which the Activation Key has been submitted • The Product for which the Activation Key was requested • More Information

5 Click on the Finish button. Result: You will exit the Registration Wizard. The Activation Key will be sent to you in due course.



45


Saving a Request To File

It is possible to save a SEAGULL Activation Request file instead of submitting it immediately. This method can be used if it is not possible, for any reason, to complete an activation request at any given time. Perform the following steps to save an activation request to file:

Step Action

1 Select the Activation Request method by checking the appropriate option. In this case, it will be the Save to file for delivery to SEAGULL later option. Click on the Next button. Result: The Save to file to submit later screen appears.

2 Specify the directory you would like to store the saved file in. The default directory will be the SEAGULL\Registration Wizard. Click on the Next button. Result: A summary of the action is shown. This will display the following information: • The Activation Result • The Machine to which the Activation Key has been submitted • The Product for which the Activation Key was requested

3 Click on the Finish button. Result: You will exit the Registration Wizard. The Activation Key will can be retrieved and sent to the Order Administrator when necessary.


46

Installing Additional Components

7 Installing the LMS, Collector or DAS

Additional Components

The additional components in question refer to the License and Message Server (LMS), the SEAGULL Collector and the Data Access Server(DAS). These additional components should be installed based on what you wish to accomplish with J Walk.

Installation Procedure

If you wish to either install either one of the said components, follow the steps below:

Step Action

1 Before you begin, be sure that no LMS, or DAS is running. 2 Insert the J Walk CD into the CD-ROM player on the iSeries. You can

stop the LMS (and DAS TCP/IP) with the commands: Sealms/endlmstcp force (*yes) Sealms/endlmsspx force (*yes) You can stop DAS (APPC) with the command: Seadas/enddasappc

3 Start J Walk Windows / Java Client 4 Logon to the iSeries as QSECOFR 5 When the main menu appears type the iSeries command

"LODRUN OPT01" Which stands for Load and Run Optical device 1 (CD-ROM)

6 A menu will appear where you can select the operations and options that you require.

7 Follow the installation wizard’s instructions.


47

J Walk Server Commands for the iSeries

8 Commands for J Walk Native Server

Native Server Commands

Below are useful commands for the Native Server.

Command Description Additional Parameters

STRJWKSVR Starts the Server. ENDJWKSVR Stops the Server. DMPJWKLOG Generates a

troubleshoot log in directory \SEAJWK.

Available since Version 4.1 The new parameter JOBNAME allows the server process to be started with the job name that is equal to the profile name. Possible values: *DFT *PROFILE Note: A job name has a length of 10 characters. *DFT The value *DFT refers to the command SEAJWKSVR. *PROFILE If *DFT is specified as the PROFILE, and the parameter JOBNAME has a value of *PROFILE, this means that the command SEAJWKSVR is carried out. When no value is specified in the job name field, *DFT is used by default. Note that the default value for command parameters can be changed using the CHGCMD command. For the ENDJWKSVR and DMPJWKLOG commands the value need only be entered when specifying PROFILE(*SELECT). The value *PROFILE is not permitted.



48

Commands for J Walk Native Server,continued

How to Start the Server

Follow the steps below to start the default Native Server.

Step Action

1 Start the default Native Server using the SEAJWK/STRJWKSVR Command to submit the SEAJWKSVR program. Available since Version 4.1 STRJWKSVR command in combination with the command parameter (/CV) will check the validity of the specified PROFILE against the profile set in the INI file before submitting the server job. A status code will be returned. Depending on the status code, the job will/will not be submitted. If not submitted, an error message will be displayed on the bottom line of the screen. Refer to the job log [DSPJOBLOG] of the interactive session to look up the reason for the job submittal failure. Note: It is possible that if the socket for the server is in use, the submitted job may fail. Checking if the socket for the server is available or not cannot be checked at this time.

2 Use 'WRKTCPSTS', option 3 "Work with TCP/IP connection status" to verify that port specified during the install (default 400) is opened.

3 If this is the case a client connection should be possible after the following step.



49


Starting the Native Server Using the PROFILE Name as the JOBNAME

Available since version 4.1 It is possible to start the Native Server using the PROFILE name – where the PROFILE name (as defined in the JWALK.INI file) is the same as the JOBNAME parameter. This allows the possibility to manage more than one ‘user profile’ on the iSeries.

Step Action 1 Enter the PROFILE name as found in the INI file.

2 Start the Native Server using the following command on the command prompt. SEAJWK/STRJWKSVR PROFILE(TALNET) JOBNAME(*PROFILE) This command will start the TALNET profile as well as the JOBNAME TALNET that is taken from the JWALK.INI PROFILE (meaning there is a section in the INI called TALNET).

3 Alternatively, if you specify *DFT as the PROFILE name:



50


Starting the Native Server Using the PROFILE Name as the JOBNAME, continued

Step Action 4 ..and start the Native Server with the following command on the

command prompt: SEAJWK/STRJWKSVR PROFILE(*DFT) JOBNAME(*PROFILE) This command will start the Native Server using the profile TELNET and start the JOBNAME SEAJWKSVR that is taken from the JWALK.INI PROFILE (meaning there is a section in the INI called TELNET). Note: The value *DFT refers to the default PROFILE for the Server. Since the default PROFILE is Telnet, when used as a JOBNAME, this is automatically converted to SEAJWKSVR (starting the Native Server

5 To end the Native Server, enter the following command: SEAJWK/ENDJWKSVR PROFILE(*DFT)

How to Stop the Server

It is now possible to stop one server instead of all. Follow the steps below to stop the Native Server.

Step Action

1 To stop running a Native Server, enter the command: SEAJWK/ENDJWKSVR PROFILE ( )

2 You can specify the profile name if you know it. You have a choice to select *ALL or *SELECT. • If you choose *ALL this will stop all the running Native Servers. • If you choose *SELECT this will lead you to another screen

which displays a list of all current active profiles which you then select from.

The Force End Sessions Active option, which stops all active servers, is still available. NOTE: If the server that started the http tunneling server is stopped then the Tunneling Server will also stop.



51


How to Stop a One PROFILE under a JOBNAME

Available since 4.1 Alternatively, if three different profiles have been started up under the same JOBNAME, here are instructions on how to stop one single PROFILE from the same JOBNAME.

Step Action

1 There are two different profiles started under the same JOBNAME: TELNET(default),TALNET and TOLNET.

2 To stop one of these profiles, enter the following command on the command prompt. SEAJWK/ENDJWKSVR PROFILE(*SELECT) JOBNAM(GLENN)



52


How to Stop a One PROFILE under a JOBNAME, continued

Step Action 3 The following screen will appear. This screen allows you to select which profile to end.

Enter a ‘1’ in the empty field next to TALNET for instance.

4 The Native Server will now check if the specified profile name exists in the JWALK.INI file. If it does, then the Native Server will end.

5 If the specified profile name does not exist in the JWALK.INI file, the following screen will appear.


53

9 Using J Walk Server

Starting the Java Client

Follow the steps below to start the Java Client.

Step Action

1 Start a browser on your PC. 2 Connect using the following line:

http://[domain_name]/jwalk/jwalk.html This should start the java classes and establish the connection.

3 Java Console and Log: When attempting to connect a Java Client to a J Walk Server, if a message appears on the "Splash pop-up" indicating a 'Unable to connect' then it is recommended to inspect the connection log for that Java Client. You can view the log in the J Walk Server Console dialog. From there (when properly configured) you may also print this log. The log contains each step taken in the failed attempt to connect with the J Walk Server. Use these details as a "diagnostic aid" in understanding "where" the problem lies. Note: This log and the Java Console only exist for the Java Client when used with a J Walk Server. These details do not include “server-side" information of any type.

How to Deploy Your Package File

In order to deploy your own package file, you must ensure that the following requirements are prepared:

Step Action

1 Within JWALK.INI, each server is assigned a unique port. Create an application profile [section] per application where you specify a working directory and unique J Walk Server port number.



54

Using J Walk Server, continued

Step Action

2 Each server requires its own unique HTML startup page specifying the unique port number. For example, copy \JWALK\JWALK.HTML to \JWALK\YOURAPP.HTML.

3 Create a Control File (*.JWC) and specify the "Runtime" parameters ordering your package files. Note: If you intend to use your own path, you must make it "public" to the Apache Web Server (see Section 2). On the iSeries, use the command WRKHTTPCFG to allow a browser to use the java classes. Add the following case-sensitive lines: PASS /YOURPATH/* /YOURPATH/* PASS /yourpath/* /yourpath/*

4 Copy the package file set (including images, etc...) to a unique subdirectory on the Apache Web Server- for example HTTP://<domain name>/YOURPATH/YOURAPP/

5 Following the preparation, to start up the Server: 1- Shut down any running servers. 2- Start your server specifying the application profile [section]. 3- Browse to the specified HTTP location and open the specified HTML page to startup a Java Client.


55

10 Command Line Parameters

Overview Command line parameters can be used to influence how J Walk Server connects to

the host. You can now use command line parameters with iSeries commands.

Command Line Parameters

Some parameters override JWALK.INI settings and provide a quick alternative for changing JWALK.INI settings without having to start the Configuration Assistant. Other parameters do not have an equivalent JWALK.INI setting. In order to use these parameters, you can use iSeries commands and command line parameters together. For example: SEAJWK/STRJWKSVR PROFILE(USER) ADD01(‘-GCloC=1’) ! Make sure you use the –G command line as described below. <value> Indicates a value must follow the command line parameter. {-} Indicates an optional value to the command line parameter.

Command Line JWALK.ini

setting Description

-G<name>=<value> <name> Overrides any INI setting by entering the full or abbreviated version of the INI setting as <name>. Use the first 3 letters of the INI setting name followed by all other capital letters and numbers that make up the abbreviated name.

/CV Not applicable Available since 4.1 Use this command line option to let the server validate the PROFILE against the profile set in the INI file. If there are any errors, the host (iSeries) will send a SEA4003 error message to the calling application so that the server’s start program will be able to monitor the message and be informed that an error had occurred.


56

Administering J Walk Server

11 Administering J Walk Server

What is the Server Management Console (SMC)?

It is an HTML-based Server Management Console (SMC). SMC is also available for you to configure your J Walk Server once it is running. It also allows you to monitor and maintain J Walk Server from a remote location. Server Management Console is available on ALL platforms.

Starting the Server Management Console

To start the Server Management console, follow the following steps:

Step Action 1 Open a browser. The URL to connect the SMC to the Server is in the

following format: “http://<machine_name: port number/smc/smc.wsp” You can change the settings of the host name by editing jwalk.ini. Port number is set in the INI setting ‘ServerPort’. Result: The Server Management Console is opened. In the main panel of the console, the Server statistics log is displayed.



57

Administering J Walk Server, continued

SMC Administration Commands

To administer the SMC, use the commands on the left side panel on the SMC Console. Below is an image of how the Server Management Console looks like.

Command Description (and Sample Result)

Restart Displays a confirmation dialog asking you whether you really want to restart the SMC. Click OK to restart the SMC. Click Cancel to keep J Walk Server running.

Shutdown Displays a confirmation dialog asking you whether you really want to shutdown the SMC. Click OK to shut down the SMC. Click Cancel to keep J Walk Server running.



58


SMC Administration Commands, continued

Command Description (and Sample Result) Change Admin Settings

Displays Admin settings that you can modify. You can change the original Administrator ID and password, and modify the restart delay value.

Configuration Assistant

Displays the Configuration Assistant and allows you to create, modify, add and delete INI settings.



59



Command Description (and Sample Result) Statistics Log Displays statistics for the J Walk Server.

Server statistics: 00:15:10 Elapsed time 00:00:00 Minimum connect time 00:00:00 Maximum connect time 00:00:00 Average connect time 0 Total connections 0 Maximum concurrent connections 0 Minimum screen transitions per connection 0 Maximum screen transitions per connection 0 Average screen transitions per connection 0 Connections failed to start 0 Connections broken

Connection Log Displays information about back-end connections. 2002/04/19 14:51:35 J Walk Server Version 4.0x started (UTC 2002/04/19 12:51:35)

Troubleshoot Log

Displays version information about the current J Walk Server. Example is shown below. Product : J Walk Server Date/time : 2002/04/19 15:09:03 Version : Version 4.0x Codepage : 1252 Screen size : 1024x768 System colors : 256 Character set : 1 Bidirectional : No DBCS : No OS : iSeries Command line Server port : 1289 Service : No Path Directory : MRI Path : MRI Code : Dongle : None



60



Command Description (and Sample Result) Event Log Displays a log of events.

Event Log is empty.


61

Using J Walk Native Server

12 An Example

Introduction In this chapter, you will learn how to use the example application installed with J

Walk Server. It is not a step-by-step guide, but it will show you how to use the Native Server with Clients.

About the Example Application

An example is installed with the J Walk Server to show some of the features in J Walk for iSeries. The intention of this example is to provide an easy start in creating a GUI for your own iSeries application. The example shows the required files and settings to setup a J Walk Server and Java Client and also to start Windows Client in Server Connect Mode. Note1: The example (as installed) can be run instead of the "default" server. You must first verify that no Native Server is currently running. Do this by invoking the command: SEAJWK/ENDJWKSVR. Note2: If values other than SEAJWK and JWALK were specified in the Install to Library and Install to directory fields in the FTP Connection Settings dialog, open the INI file and in the [EXAMPLE] section, edit the path specified by the INI setting WorkingDirectory, to refer to the new directories specified in the dialog.

Start the Example Native Server and Client

Starting the J Walk Server and Java Client example requires you to do the following:

Step Action 1 Stop any running Native Server (SEAJWK/ENDJWKSVR). 2 Start the Native Server: SEAJWK/STRJWKSVR

PROFILE(EXAMPLE). 3 Start your Internet Browser(e.g. Internet Explorer, Netscape,...). 4 Browse to address:http://<domain_name>/jwalk/jwalk.html. 5 Now the Java Client will start using the example panels served by the J

Walk Server. 6 Click on the button in the lower-right corner to login. 7 If you select Help from the menu then html help will be started.



62

Using J Walk Native Server: An example, continued

Examining Files Used by Example Server

Note: It is assumed you have assigned a drive letter to the iSeries filesystem (e.g. type: NET USE R: \\NLSBS003). In http://<domain_name>/JWALK/ are the HTML files to start the two Clients: • jwalk.html : to start the J Walk Java Client • jwalkx.html : to start either Served Windows Client In http://<domain_name>/jwalk/jwalkapp/example/ are the application files: • example.jwr : the Package file (used by both client) • example.jwc : the control file (used by the Windows Client) • example.jwm : the text file (used by both) • example.jwx : the translation file (used by both) • example.hlp : the Windows help file (used by the Windows Client • default.html : the HTML help file (used by the Java Client) • *.gif, *.jpg : some images used on the example Client panels. In the SEAJWK directory, there is the jwalk.ini file containing a section specifying the details for use with this example application as well as some default package and image files: \SEAJWK\JWALK.INI : see the section called: "[EXAMPLE]". Note: The WorkingDirectoryand HttpHelpBase INI settings were previously assigned the values WorkingDirectory=#WEBDIR#/jwalkapp/example and HttpHelpBase=#HTTP#jwalkapp. The #WEBDIR# is replaced by /jwalk and the #HTTP# is replaced by location of the wwwroot directory from version 4.1C7 and higher. Default images for the Java Client: *.gif, *.jpg : images displayed on the panels. Additionally: • ibmuim.jwr : Graphical Access file • ibmdds.jwr : Graphical Access file • ibmoff.jwr : Graphical Access file.



63

General Information, Continued

Example Using Server Connect J Walk Windows Clients

To use a J Walk Windows Client in server connect mode, you need to:

Step Action 1 Start your Internet Browser 2 Browse to address.

http://[domain_name]/jwalk/jwalkx.html 3 If no Windows Client (or an older version) can be found then a new

Windows Client will be installed (note that this caches 21 Mb into your temporary Internet Files folder set at your browser).

4 Now the Windows Client uses the example panels. Click on the button in the lower-right corner to login.

5 If you select Help from the menu then Windows help will be started.



64

Using J Walk Native Server: An example, continued

Running the Default Server Together with the Example Server

Typically, you will want to run more than one server. In this case,the "default" and "example" servers are run together. These additional requirements must be enabled: • Each server needs to run on an unique port • Each server requires its own unique HTML page. You will have to make an alternate port for this example. Follow the steps below:

Step Action

1 Copy \JWALK\JWALK.HTML to \JWALK\EXAMPLE.HTML. 2 Edit EXAMPLE.HTML specifying a unique port number. 3 Stop any running Server(s): SEAJWK/ENDJWKSVR. 4 Edit JWALK.INI, select the EXAMPLE section and specify the same

unique port number (like in step 2). 5 Start the servers on the iSeries. 6 Start a Browser and open the JWALK.HTML page to start the Default

Application. 7 Start a second Browser and open the EXAMPLE.HTML page to start

the Example Application.


65

Advanced Users

13 Advanced Features

Overview This section explains additional features available for advanced Server users.

SocketManagerStrategy Setting

The SocketManagerStrategy is an INI setting that allows a strategy for socket management to be set. Using the appropriate socket strategy ensures server stability and performance. Additionally, it can be used to monitor the server’s performance. Performance monitoring in this case would cover issues such as handling client connections, host responsiveness etc. To use this INI setting, add SocketManagerStrategy= to the Server’s INI file manually. Additionally, the Socket Manager Strategy will be shown in the trouble shoot log. It is often useful to be able to manipulate a socket that connects an application to a network protocol. E.g. in Unix a program can send and receive TCP/IP messages by opening a socket and reading and writing data to and from the socket. The strategies are:

SocketManagerStrategy Description Poll Uses Poll calls Select Uses Select calls which is the lowest common

denominator for all platform types DevPoll Device poll mechanism for higher scalability Overlap Uses overlapped I/O

The strategies mentioned are also a default type per platform. The default for the iSeries is Select. Please use the default whenever possible.


66

Log Files

14 Server Log Files

Overview This chapter covers the following topics on log files generated by the Native Server.

Server Log Files The Native Server generates the following log files.

• Troubleshoot log • Stack trace/dump file

Troubleshoot Log

Clients and Servers can produce a Troubleshoot report using the product. This report contains information about your PC’s configuration and J Walk environment. The Server will produce the JW9SRVxx.LOG file automatically, every time a Server session is opened. The Native Server requires you to invoke the logging facility by using the command SEAJWK/DMPJWKLOG. View the printed file JWXXX.LOG in directory \SEAJWK, where "XXX"= the "ServerPort" value specified in the JWALK.INI. Alternatively, to view the troubleshoot per user (that started the Native server), please use the command WRKSPLF SELECT(USER) where USER is the owner. Note that information about the iSeries compiler version (V4Rx or V5Rx) will be included into the Troubleshoot log from version 4.1C4 and higher. For example: Machine name : OS : iSeries 400 V5R4M0 LPAR:3 Model 9406, Type 520-7453 Command line : \SEAJWK\JWKSVR -ETELNET Compiler version: 600 The compiler version refers to either one of the following: • 300 refers to V4Rx versions • 600 refers to V5Rx versions



67

Server Log Files, Continued

Stack trace/dump file

Stack traces / dump files contain exceptions that occur between Server, the host application, License and Message Server and the clients. It will give useful information about what the Server is doing at a given time, such as:

• Classes called • Memory information

Created along with the stack trace/dump file is a text file that has the following information:

• Timestamp when the text file is generated • The version number of the product application • The build information of the product application

Stack traces/dump files are only generated if the product application fails to respond. A stack trace/dump will be generated and logged in the Native Server job log and also sent to QSYSOPR. The message indicates the Server version, reported message and message ID number.


68

Further Information

15 What to do next

Overview If you have already installed and configured J Walk Server, you are ready to use J

Walk Server with the Windows Clients (or ActiveX or Java clients).

What To Do Next

You should inform your developers of: • The existence of any J Walk Server configuration files that you have created. • Procedures in deploying package files If you have any problems or questions, please do not hesitate to let us know so we can help.

Customer Support and Service

If you have a current support and maintenance agreements with Seagull Software, you can access Seagull Software Customer Care via the Rocket Customer Portal and report a problem, download an update or read answers to FAQs. The Rocket Customer Portal is the primary method of obtaining support. To logon to the Rocket Customer Portal, go to the following URL: https://www.rocketsoftware.com/support If you do not already have a Rocket Customer Portal account, you can request one by clicking the Sign up for an account or reset a forgotten password link on the Rocket Customer Portal logon page. Alternately, you can contact Seagull Software on the phone or over e-mail: E-mail: mailto: [email protected] US Office: +1 404-760-1560 European Office (European Time)/Asia Pacific: +31 78 6322 800 Information required when contacting technical support

• A description of the problem that you are experiencing, and steps to reproduce the issue.

• The version of the product that you are using. • A Troubleshoot log.

https://www.rocketsoftware.com/support

mailto:%[email protected]

j walk server for iseries installation guide - dps,...

Documents