WebsydianExpress for iSeries

Overview

The program you are about to download will help you install WebsydianExpress for iSeries. You must run iSeries V5R3M0 or later in order to install WebsydianExpress for iSeries.

Your iSeries will become the application server of your WebsydianExpress applications and will hold program objects, physical and logical files. You will have a number of options on where to locate your web server.

Developing applications with WebsydianExpress for iSeries

When developing applications for the WebsydianExpress for iSeries all programs will be required to be RPG objects. You have the choice of using one or more of the following developing tools:

• CA Plex v6.1 with the Websydian patterns v6.1
• CA 2E v8.0 or later
• Standard ILE RPG

What is Installed

During installation a number of folders, files and objects will be installed on both your pc and your iSeries.

On the PC

The files installed on your PC is primarily in order to help you transfer and install objects needed on your iSeries. However some important files and resources are available on your PC for later use.

Folder structure

When you run the installation program on your PC, it installs a folder structure on the PC in a location of your choosing.

Default location: C:\Websydian\Express v3.0 for iSeries.

• The iSeries folder is used by the program that transfers the objects to your iSeries.
• The Upgrade folder contains import files to update the WebsydianExpress administration interface if you are upgrading from a previous version of WebsydianExpress.
• The Web Server Component folder contains the objects that will either be installed on the selected web server as part of the installation - or be manually installed on a web server after the installation.

On the iSeries

The installation program creates an iSeries library containing the install programs, commands and the save-files containing the application objects. The default name of this library is WXP30INST.

The last part of the installation is running the WXPINST command from this library. This creates a number of libraries:

Database library

Default name: WXP30DB

Contains the physical and logical files for the WebsydianExpress application. This library will also contain the EXPRESS job description used by the application service jobs.

The installed files are the ones used by the WebsydianExpress application. It is recommended that you place your own application files in another library.

Program library

Default name: WXP30PGM

Contains the program objects used by the WebsydianExpress application. It is recommended that you place your own program objects in another library.

This library also contains the commands to start and stop the WebsydianExpress application.

PTF Library

Default name: WXP30PTF

This library contains any fixes that has been created for the WebsydianExpress application. This library is placed before the program library in the job description.

Application library

Default name: WXP30APP

This library is empty after the install. It is part of the EXPRESS job description, so any programs placed in this library can be used by the application.

You can use this for your own application objects - or you can add other libraries to the EXPRESS job description to make them accessible for the application.

Web component library

Deafult name: WXP30WEB

This library holds required objects if you would like to use the IBM HTTP Server located on your iSeries as the web server for your WebsydianExpress.

Read below for additional information on where to locate your web server.

Demo library

Default name: WXP30DMO

This library holds a number of objects used by the examples supplied with WebsydianExpress.

On the web server

If you have an Apache Tomcat server installed on the PC where you install WebsydianExpress, you will get the option to install the web server component used by WebsydianExpress on the Tomcat server. If you select to do so, a servlet will be deployed on the Tomcat server. You will later on be able to select another web server if you like.

Uninstalling

An automatic uninstall is not provided with the installation program but you will be able to uninstall by doing the following:

1. On your iSeries delete all installed libraries. If you used the default library names these can easily be found by locating library starting with WXP30*
2. On your PC delete the folder where WebsydianExpress for iSeries was installed. If you used the default folder name you can delete c:\Websydian\Websydian for iSeries and all sub-folders
3. If accepted to install the WebsydianExpress web server component on your local Tomcat instance you will need to delete the folder express30 from the Tomcat webapps folder

Web server

With WebsydianExpress you will get a WebsydianExpress Web Server Component that will handle the communication between your web server and the WebsydianExpress Applications on your Application Server.

For your development environment or testing WebsydianExpress for iSeries for the first time we supply a CGI based WebsydianExpress Web Server Component which integrates into the IBM HTTP Server. This is automatically selected during installation when choosing the default installation. The benefits of the CGI based WebsydianExpress Web Server Component for IBM HTTP Server is the ease of setup and that you do not need to setup a WebSphere prior to testing WebsydianExpress on your iSeries.

The drawback however of the CGI based WebsydianExpress Web Server Component for IBM HTTP Server is the lack of performance.

For your production environment we supply the Java Servlet based WebsydianExpress Web Server Component which requires you to have a Servlet Engine installed on either your iSeries or on a PC Web Server in your network.

Communication between the WebsydianExpress Web Server Component and the WebsydianExpress Applications are done by using TCP/IP. The use of TCP/IP enables you to setup a firewalled environment placing your Web Server inside the  demilitarized zone (DMZ) of your network.

We recommend the following Servlet Engines:

• For the iSeries platform you will need to use the IBM WebSphere Advanced Server Express with integration into the IBM HTTP Server.
• For a PC web server we recommend Apache Tomcat which fully integrates into either Microsoft Internet Information Server (IIS) or Apache HTTP Server.

Environment examples

Scenario 1: All on one iSeries partition describes the installation where you have installed everything on the same iSeries this is very useful for internal applications not requiring that you setup a DMZ for isolating your Web Server. This scenario is also very useful for a development and test environment.

Scenario 2: Web Server on iSeries partition and the rest on another iSeries partition is useful if you would like to separate your Web Server from your Application Server and also have the ability to establish a DMZ in order to isolate your Web Server.

Scenario 3: Web Server on Windows Server and the rest on an iSeries partition is most often the approach we see in companies that all ready have established a Web Server or number of Web Servers. This scenario will fit into your existing environment and allow you to isolate the Web Server in a DMZ.

Installation