WebsydianExpress for Windows with iSeries back-end

Overview

The program you are about to download will help you install WebsydianExpress for Windows with iSeries back-end.

This is a specialized variant of WebsydianExpress where you will have a set of client side programs running on a Windows based Application Server and a set of server side programs running on your iSeries. All data will reside on your iSeries. Connection between the Windows and iSeries will be handled by the CA Plex iSeries Dispatcher.

You will have a number of options on where to locate your web server.

Developing applications with WebsydianExpress for Windows with iSeries back-end

When developing applications for the WebsydianExpress for Windows with iSeries back-end you will need CA Plex v6.1 with Websydian v6.1 patterns.

Program objects created for WebsydianExpress for Windows with iSeries back-end will be C++ objects on the Windows client and RPG objects on the iSeries back-end.

What is Installed

During installation a number of folders and files will be installed on your Windows platform along with a number of libraries and objects on your iSeries.

On the PC

Folder structure

A folder structure containing the main application objects will be installed in a location of your choosing.

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

• The Express v3.0 for Windows_IBMi folder contains the command files used to start and stop the WebsydianExpress application.
• The Application Service folder and it's subfolders is where the WebsydianExpress runtime and the html used by the runtime is placed.
  This folder contains the EXPRESS.ini file, which is the ini-file used by the WebsydianExpress application as well as the settings.cmd file that can be used to configure the WebsydianExpress application.
• The Common folder contains the java runtime environment used by the WebsydianExpress runtime.
• The iSeries folder contains installation programs for iSeries objects used by WebsydianExpress
• The Logs folder is empty when the application is installed, this is the default location for the WebsydianExpress logs.
• The Temp folder is used by the application when it needs to create temporary files which must be saved to disk.
• The Upgrade folder contains import files to update the 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.
• The Websydian Server folder contains the objects used by the Websydian Server - the license subfolder is where you must place the license.key file for the application if you are using a licensed version of WebsydianExpress.

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

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

Database library

Default name: WXPW30DB

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

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

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

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 Server component

If you have an Apache Tomcat server installed on the PC-server 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 application will be deployed on the Tomcat server.

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 PC delete the folder where you install WebsydianExpress for Windows. If you used the default folder name you can delete c:\Websydian\Websydian for Windows_IBMi and all sub-folders.
2. On your iSeries delete all installed libraries. If you used the default library names these can easily be found by locating library starting with WXPW30*
3. If you have accepted to install 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.

We supply a Servlet based WebsydianExpress Web Server Component. In order to deploy this component you must have a Servlet Engine installed on a Web Server in your network or locally.

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

• Apache Tomcat which fully integrates into either Microsoft Internet Information Server (IIS) or Apache HTTP Server.

Environment examples

Scenario 1: Default setup using WebsydianExpress for Windows with iSeries back-end - a good scenario for development and test. Web Server and Application Server on the same Windows PC and with access to your iSeries in order to access data and iSeries server side programs.

Scenario 2: 3-tier setup isolating web server, application server and iSeries back-end - this is the most used scenario in a production environment enabling you to setup your web server in the DMZ of your network. 

Scenario 3: A combination of iSeries data and data on a Microsoft SQL Server - just to show that event though data and programs reside on your iSeries you are able to access data on a Microsoft SQL Server using an ODBC connections from your WebsydianExpress applications.