WebSmart logoWebSmartInstallation Instructions

These instructions are for installing WebSmart ILE, WebSmart PHP and Clover. If you plan to evaluate WebSmart PHP, you should install Zend Core or Zend Server first. Read Knowledge Base article 6964 for further information. The instructions describe how to install and configure all WebSmart 8.8 components. Some steps are only necessary for certain features or requirements. Check the comments at the top of each step before proceeding.

Step 1. End the EXODUS subsystem (if it is running).

This step is required if you are upgrading from a previous release of WebSmart, and if you have BCD’s Catapult, Presto or Spool-Explorer installed. If this is a new install, and you know you don’t have Catapult, Presto or Spool-Explorer running, skip to the next step.

The WebSmart IDE (the design tool) uses a communications middleware component called EXODUS to transfer data between the iSeries and PCs at different times while you are creating your programs. For example, EXODUS is used to retrieve iSeries file layouts, or upload code to be compiled. EXODUS is also used by BCD’s Catapult, Presto and Spool-Explorer/400.

Before installing WebSmart you need to make sure that there are no EXODUS jobs running, to ensure there are no locks on objects that need to be updated or replaced.

Ending the EXODUS Subsystem

To verify whether you are ready to install WebSmart sign on to an iSeries session as QSECOFR and run the WRKACTJOB command. Check whether there is an active subsystem called EXODUS:

If the subsystem is not active, you can proceed directly to Step 2.

If the EXODUS subsystem is active then someone at your site may be working with an application that uses EXODUS for communications. To see a list of these jobs, run the command WRKOBJLCK XL_EXODUS *LIB. You can then contact the users associated with these jobs to request that they end their connections, or if you know what the jobs are, you can end them yourself.

After ending all EXODUS jobs, run the following command to end the EXODUS subsystem: ENDSBS SBS(EXODUS) OPTION(*IMMED). Then continue with the next step.

  
Troubleshooting   

If you aren't able to sign in as QSECOFR, you need to contact your system administrator and request that they either perform this install for you, or assist you in performing the install.

You can also search our Knowledge Base Opens new window on this topic.
Step 2. Install Zend Core or Zend Server.

This step is required for WebSmart PHP only. If you have no plans to use or evaluate WebSmart PHP, skip to the next step. However, if you think you might at some time try out WebSmart PHP, you should install Zend Core or Zend Server first so the WebSmart install can automatically detect it and adjust the WEBSMART HTTP server instance accordingly. If you install the Zend components afterward, you’ll need to make these adjustments manually.

Installing Zend Server

To verify whether you have one of these installed, follow these steps:

  • At an iSeries session, run the command GO LICPGM.
  • Select option 10.
  • Check that either the licensed program 1ZCORE5 (Zend Core) or 2ZSVRPI (Zend Server) are listed with a status of *INSTALLED.
If you don’t have one of these installed, you can download Zend Server for free from the Zend website. Then follow the instructions in the Zend Server for IBM i Installation Guide.

After installing Zend Server you can continue with the next step.

 
Troubleshooting & Info   

Visit Zend's website for more information about Zend Server.

If you have installed any release of WebSmart before installing Zend Core, you will need to manually add some directives to your WEBSMART Apache HTTP server instance (or any server instance you regularly use). These changes are described in the WebSmart PHP Knowledge Base article 6991Opens new window.

Step 3. Install the WebSmart iSeries Components.

This step is required for all installs.

Download WebSmart 8.2.

1. Go to the Download Free Software Opens new window page and fill out the form to download WebSmart.

2. Download and save both the iSeries and PC installation files to a new folder on your PC.

3. When the download finishes, double-click the iSeries install executable file WebSmart8.2.exe (the version number may vary) to unpack the files and transfer them to your iSeries.

When the download finishes, double-click the iSeries install executable file WebSmart8.2.exe (the version number may vary) to unpack the files and transfer them to your iSeries.

4. After the file is decompressed, BCD's FTP upload utility is presented. Enter your iSeries IP address and the QSECOFR password (as shown below). Then click the Upload button:


When the Activity Log reports that the file upload is complete, you can close this window.

5. Log on to an iSeries session as QSECOFR and execute the command BCDINSTALL/BCDINSTALL.

6, At the panel presented, select the product WebSmart and press Enter. Follow the on-screen instructions. The iSeries libraries installed are XL_WEBLIB, XL_WEBSPT, XL_WEBDEMO, XL_EXODUS and BCDSUPPT.

7. When prompted, enter your WebSmart License Key. If you don't have a valid WebSmart license key, contact BCD at (630) 986-0800 to request one. You can also press F3 to Exit (and complete) the installation process, and add the license key afterwards using the command XL_WEBLIB/UNLOCK. If you are upgrading, pressing F3 will cause the install to retain your existing license key.

8. When the iSeries install concludes, prompt the command XL_EXODUS/ZCFGTCP [F4] and ensure that the IP address shown at this screen is the correct local IP address for your iSeries. Also, if you are at V6R1, the default EXODUS connection port number (2015) won't work, as IBM took over using that port. Change the default port number to 7015 or another port you know is available. Then press Enter to run the command.

9. If you changed any of the values displayed when you initially prompted the ZCFGTCP command you need to restart the EXODUS subsystem to apply the new values. Run the command: ENDSBS SBS(EXODUS) OPTION(*IMMED). Ignore any messages.

10. Run the command STRSBS XL_EXODUS/EXODUS to start the EXODUS subsystem. After a few moments, run WRKACTJOB to verify that the EXODUS subsystem is active and contains a job called EXSERVER.

If the subsystem is started, continue with the next step.

The WEBSMART HTTP Server Instance
As part of your WebSmart iSeries install we create, configure and start an Apache HTTP server instance named WEBSMART, running on port 8150. This allows you to start running your programs as soon as you install the software.

You can use the WEBSMART HTTP server instance however you want, but we recommend that once you start creating production applications you create your own server instances and use those. In our own internal development projects we have caused the HTTP server instances to go down due to malformed SQL and other programmatic issues, so we recommend that you create at least two separate server instances, for your development and production environments.

If you need assistance with creating your own server instances, please call Technical Support and we can help you out.

 
Troubleshooting   

If the transfer is interrupted, you can restart it by executing webinst.exe (in the folder to which you downloaded the software).

If the transfer fails, check the Activity Log window for errors. BCD's Knowledge Base Opens new window includes a number of useful troubleshooting options.

You can also run the command WRKSPLF QTCP and check the last joblog there.

After you select the library to install to, BCDINSTALL attempts to restore the product library. It's very rare to have a problem with this step, but any that do come are usually due to changes to the RSTLIB command defaults.

If you mis-enter your license key, you can enter it later using the command XL_WEBLIB/UNLOCK.

If you IPL your iSeries nightly or on the weekends, you need to also restart TCP/IP services and the EXODUS subsystem. While you probably already have processes in place to restart TCP/IP, you can add the command STRSBS XL_EXODUS/EXODUS as part of that process (or just run it manually while you are still evaluating the software).

You can also search our Knowledge Base Opens new window on this topic.

Step 4. Testing the Install and Checking your HTTP Server Instance.

This step is recommended for all installs.

As part of your WebSmart iSeries install we create, configure and start an Apache HTTP server instance named WEBSMART, running on port 8150. This allows you to start running your programs as soon as you install the software.

The installation includes test programs you can run for WebSmart ILE and PHP. To verify that the WEBSMART HTTP server instance was started, enter your iSeries IP address below and click the button to test your WebSmart ILE and PHP installs:

. . .

These tests build a URL that combines the IP address you entered, the WEBSMART HTTP Server's port number (8150) and the WebSmart library or IFS directory where the programs reside.

If the test program(s) run it means that you have successfully installed the iSeries side of WebSmart ILE and/or PHP, and have started a functioning HTTP server instance.

Now you're ready to install the WebSmart IDE on your PC.

Background Information: The HTTP Server Admin Interface
As you start creating web applications you'll want to familiarize yourself with the IBM Web Administration for i interface.

To work with it go to the browser window where you ran the testcfg.pgm program and change the url to http://xxx.xxx.xxx.xxx:2001/HTTPAdmin, (where the x's represent the IP address of your iSeries).

When prompted, log in using your iSeries user profile. At the page presented you can go the Manage HTTP Servers section and select the WEBSMART server instance from the drop down list:


From here you can see the status of this server instance, and start, stop or restart it.

If it's currently stopped you can click the green button to start it.

Note that from here you can also change the port number that the WEBSMART HTTP server instance is running on, or make other changes to the configuration.

  
Troubleshooting   

To confirm that this server instance was successfully started run the WRKACTJOB command and look for the subsystem QHTTPSVR. This subsystem should contain several jobs named WEBSMART. If this server instance is not visible you can start it using the command STRTCPSVR SERVER(*HTTP) HTTPSVR(WEBSMART).

If the programs don't run, verify the URLs generated in your browser window when you ran the test. The URL should look something like: http://xxx.xxx.xxx.xxx:8150/testcfg.pgm.

If you can't spot the problem, complete the PC install and then contact Technical Support.

You can also search our Knowledge Base Opens new window on this topic.

Step 5. Install the WebSmart IDE on your PC.

This step is required for all installs.

You can install the WebSmart IDE (the PC design tool) on any number of PCs that connect to the same server. Follow the steps below to install the WebSmart IDE:.

1. If you haven’t yet done so, go to the Download Free Software Opens new window page and fill out the form to download WebSmart.

2. When the download finishes double-click the downloaded file to unpack the install files and initiate the install. The PC install file is named websmart820-pc.exe [this may vary slightly].

3. Follow the instructions to install the WebSmart executables to your PC.

You should be able to accept all the default install options. When it’s done, the install will prompt you to launch the software. You can also launch WebSmart from your Start menu.

Configure Communications to the Server
The WebSmart IDE needs to be configured to connect to the iSeries so it can retrieve file layouts and perform other functions related to your iSeries database.

1. If you haven't done so already, launch WebSmart from Start/All Programs/WebSmart/WebSmart.

2. If this is a new install WebSmart will detect that you haven't configured your server connection and ask you to do that. This prompt is presented (shown here with example values):


3. Enter your system name and IP (or DNS). If you are NOT at V6R1 or higher, accept the default port number of 2015. At V6R1, change the port to 7015 (or the value you used on the iSeries install).

4. From the window above you can also set default values for a few options that you need to specify every time you create a new WebSmart ILE program. These include your RPG source file and object libraries. The program object library XL_WEBAPPS will work in conjunction with the standard WEBSMART HTTP server instance configuration.

Note: If this is a new install and you choose to use a different library, you will also need to adjust the default configuration for the WEBSMART HTTP server instance or create your own HTTP server instance to use instead.

5. For the default web path to object, type http://your_ip_address:8150/webapps/ where ‘your_ip_address’ is the IP address of your iSeries (make sure you don’t forget the port number and final slash shown above). This assumes that you are using the default configuration and the WEBSMART HTTP server instance.

6. To confirm your configuration click the Test Connection button. When you do this WebSmart prompts you to sign on to your iSeries and then displays a confirmation message.

7. Click OK to add the configuration entry.

Now continue with the next step.

  
Troubleshooting   
Installation

If you have not yet downloaded the PC install file, do that now Opens new window.

If you have any trouble installing the PC components call BCD Technical Support at (250) 655-1766, or your network administrator may also be able to help you.

You can also search our Knowledge Base Opens new window for installation issues.

Communications Configuration

Your iSeries IP address and connection port number need to match the values set on the iSeries. If you aren't sure what to type, sign on to an iSeries session and run the command XL_EXODUS/ZTCPCFG to check the settings.

The most common connection error (10061) is caused by the EXODUS subsystem not being active. To address this run the WRKACTJOB command and check whether the EXODUS subsystem is running and contains a job called EXSERVER. If not, run the command STRSBS XL_EXODUS/EXODUS. If the subsystem is running but EXSERVER is not, end and restart the subsystem and confirm the job is added. Then try connecting again.

If the subsystem is up but you still can't connect, add XL_EXODUS to the library list of your iSeries session and run the command ZDSPERRLOG to display a list of your connection attempts. Check for error messages (such as invalid User IDs, etc.).

You can also search our Knowledge Base Opens new window on this topic.

Step 6. Create an FTP Connection (PHP only).

This step is only required for PHP. If you do not plan to create PHP applications, skip to the next step.

WebSmart PHP requires at least one FTP connection. Your FTP connections allow you retrieve and work with files related to your application, as well as set defaults for the PHP programs you create.

1. In the WebSmart IDE open the Tools/Options window and click the FTP entry to present these options:


Click the Add button to create an FTP Site:


Configure your options as described here:

Site NameAn informational description of the site you are connecting to.
FTP AddressYour server IP address or DNS.
Initial DirectoryEnter the initial directory to be displayed. For WebSmart, use this value: ‘/www/websmart/htdocs/wsphp/’ (with no quotes).
Web PathSelect a default path to pre-pend to your program name when you click the Launch button from within the IDE. The default WebSmart Apache HTTP server instance runs on port 8150, so this should normally be set to ‘http://your_iSeries_IP:8150/wsphp/’ (no quotes).
User/PSWDThe iSeries profile to use to connect to the iSeries when saving the PHP files.
FTP PortThe FTP port on the iSeries. The default of 21 should usually work.
Passive ModeCheck this option to establish your FTP connection in passive mode.

After entering the required values, click the Test Connection button to verify that you have entered your configuration details correctly. If the confirmation window tells you that the connection is working, press OK to create the site and continue with the next section.

  
Troubleshooting   

If you don't get a successful connection, double-check your values. If you have established links to the server in another application, compare your settings to those.

You can also create and modify your FTP connections from the window pane at the lower left of the main IDE. Just right-click in the area below the FTP Sites tab to present the available options.

You can also search our Knowledge Base Opens new window on this topic.

Step 7. Create an ODBC Connection.

This step is only required for WebSmart ILE or PHP programs running over databases other than DB2. If you will not create programs over non-DB2 tables, skip to the next step.

If you intend to use WebSmart to create programs over other databases (such as MySQL in PHP, and MySQL, MsSQL or Oracle in ILE) you need to create an ODBC connection to your target database so the WebSmart IDE can load the file layouts.

1. To create a new ODBC connection, launch the WebSmart IDE and go to the Tools/Options menu. Select the Servers/Databases section and click Add to present these options:


Click the Add button to create an ODBC Connection:


Configure your options as described here:

Name/DescriptionType a name and description for this ODBC connection.
Database TypeSelect MySQL, SQL Server or Oracle
Server/PortType a server IP and port number.
DatabaseEnter the database name.
User/PSWDType the User ID and password to be used to connect to this server.
DriverSelect the driver.

After entering the required values, click the Test Connection button to verify that you have entered your configuration details correctly. If the confirmation window tells you that the connection is working, press OK to create the connection and continue with the next section.

  
Troubleshooting   
Step 8. Create a Default PHP User Profile.

This step is only required for WebSmart PHP, where you will be running PHP programs on your iSeries and/or MySQL server. If you will not use WebSmart PHP, skip to the next step.

When you are in a Portable Application Solutions Environment (PASE) environment each time you launch your PHP program you have to establish a connection to either the iSeries or a relational database to access information. While there are a few ways to handle this requirement, the WebSmart PHP program templates are set up to retrieve the connection values from a file on your IFS.

When you execute WebSmart PHP programs, the first thing they attempt to do is load a preferences file, xl_functions001.php, by executing this statement at the top of the code:

require('/esdi/websmart/v8.2/include/xl_functions001.php');

This file includes a section where you can specify default user profiles and system names (among other things). However, because this file is overwritten when you upgrade, it in turn attempts to load some of the defaults from another file, xl_user_preferences.php, which you should create. We strongly recommend that you create your own user preference files so you don't lose your settings on upgrade.

Create xl_user_preferences.php
1. In your iSeries IFS open the file /esdi/websmart/v8.2/include/xl_functions001.php (the release level may vary).

2. Save the file as xl_user_preferences.php (or copy and rename xl_functions.php).

3. In the new, copied file delete everything from (and including) this line up to the end of the file:

@include('xl_user_preferences.php');

Note: Leave the ?> at the end of the file!

4. In the section that remains in xl_user_preferences.php enter default values for the connections you will be using, as described here:

$pf_i5UserID and $pf_i5PasswordiSeries user profile and password to use for all i5 connections. If this value is left blank, Zend Core will use the special profile ‘NOBODY’. Note that these values are only necessary if your applications will use the i5-specific PHP functions.
$pf_i5IPAddressUnless you are by default connecting from your iSeries to another one, use the loopback value 127.0.0.1 here.
pf_db2SystemNameEnter your iSeries system name for all database file access.
$pf_db2UserID and $pf_db2PasswordiSeries user profile and password to use by default for all DB2 access.
$pf_mysqlUrlDefault MySQL server to connect to.
$pf_mysqlUserId and $pf_mysqlPasswordDefault MySQL server user profile and password.
$pf_mysqlDataBase Default MySQL database.

When you create your own application you may want to load your User IDs another way (for example, by prompting the user to enter one), but this approach will get you started.

  
Troubleshooting   
Step 9. Moving On.

At this point you should be ready to try running the software and start learning how to use it.

Continue with Step 2 of the 5 Steps to Success for:

If at any point in this process you would like to have an informal chat with someone to get some suggestions on how to address your particular needs, then by all means get in touch with our Sales or Technical Support teams.

We look forward to hearing from you soon.