WebSmart Presto logoPresto Installation Instructions

These instructions are for new installs of Presto 3.8x only. If you are upgrading Presto from an earlier release log into myBCDSoftware.com to view the Upgrader's Guide. For additional product information, go to the PrestoOpens new window home page at this site.

Step 1. Download Presto and Transfer the IBM i Install Files.

Follow these steps to download the installation files and transfer the server component to your IBM i.

1, Download Presto

Before you can install Presto you need to contact our Sales office or fill out the Presto Trial Request Opens new window form at our website. We will then send you download links and instructions, and a trial period license key.

Download the server and PC installation files and save them to your PC.

2. Upload the Installation Files to your IBM i

When the downloads finish double-click the IBM i install executable file prestoserver-3.8.exe [the version may vary] to unpack the files and begin transferring them to your IBM i.

When the window below appears, enter your IBM i IP address or domain and user profile/password:

IBM i installation

Click the Upload button. When the upload finishes the activity log displays the message ‘File upload complete’. You can then close the BCD Upload Express window and continue with the next step.

 
Troubleshooting   

If you have a question about the install, give us a call. You can reach our Technical Support team at (250) 655-1766 [7:30-17:00 PST] or the Sales team at (630) 986-0800 [8:00-17:30 CST]. You can also email us.

BCD Upload Express Doesn't Launch
If the BCD Upload Express window doesn't appear automatically, execute the file install.exe from the folder to which you unpacked the Presto download. If you get an FTP transfer error, please visit our Knowledge base and search for the error you encountered. You may need to adjust the FTP settings on your IBM i.

Failed Transfers
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.

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

Step 2. Install the Presto IBM i Components.

Follow the instructions below to install the Presto IBM i components.

1. Log on to an IBM i session as QSECOFR and execute the command XL_PRESTOI/BCDINSTALL.

zzz

The default product library (or environment) name is XL_PRESTO. If for some reason this library already exists, the install will prompt you for a library name.

2. When prompted, enter the license key provided to you.

Note: If you are installing Presto for the first time you can enter the license key during the install (the recommended option) or afterwards using the UNLOCK command. The UNLOCK command is in library XL_PRESTO (or your own environment name).

3. When you press Enter the install will continue restoring the rest of the required objects.

When the IBM i installation finishes 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.

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

For further information on Presto environments please refer to the User and Upgrader's Guides.

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

Step 3. Set your CCSID in the HTTP Server Configuration

This step is only relevant if your system has a CCSID other than 37. For a CCSID of 37 (United States/North America) the default configuration will work for you.

Verify your system CCSID by running the command DSPSYSVAL SYSVAL(QCHRID). If the value displayed for the Code Page is 37, you can continue with the next step. Otherwise this will be the value you will use in your Exodus51 configuration for the DefaultFSCCSID, as described below.

If you aren’t sure where or how to make the changes below, review the User Guide section “More About the Presto IBM HTTP Server (Powered by Apache) Instance”

.

1. Change the DefaultFSCCSID value.
Go to your configuration and find this line:

DefaultFsCCSID  00037

Change it to:

DefaultFsCCSID  00xxx

Replace xxx with your system’s CCSID.

2. Restart the Apache instance.

3. After making the change above, end and restart the Apache HTTP server instance (see the next step for details).

  
Troubleshooting   

When you upgrade from a previous version the Presto Designer (the PC component) will pick up your CCSID settings from your previous installation. On the IBM i, however, you need to adjust the default HTTP server instance manually.

For further information on Presto environments please refer to the User and Upgrader's Guides.

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

Step 4. Start the Presto HTTP Server.

The server side installation created a new Apache HTTP server instance with the same name as your library. The last screen of the server install confirms these details for you and provides instructions for starting that HTTP server instance.

All new instances are set to run on port 8022 by default. If you are installing multiple versions of Presto you need to make sure each HTTP server instance is referencing a unique port number before starting it.

To start your Presto server instance (XL_PRESTO, for example) run this command:

STRTCPSVR SERVER(*HTTP) HTTPSVR(XL_PRESTO)

After a few seconds, you can confirm that the HTTP server was started by running this command:

WRKSBSJOB SBS(QHTTPSVR)

You should see several jobs named XL_PRESTO (or your selected environment name) in the QHTTPSVR subsystem.

Starting the XL_PRESTO Apache HTTP Server Instance After an IPL
If you IPL your IBM i nightly or on the weekends you need to restart your XL_PRESTO Apache HTTP server instance afterward. During your evaluation period you may elect to do this manually before you start working with the tool. If you purchase the software you should add this step to your startup procedures. You can find further information on this in KB Article 8816 Opens new window.

 
Troubleshooting   

Port 8022
This is the port number used by the Apache HTTP server to display your pages in a browser. This is NOT related to the port number used by the Presto Designer to connect with the Presto server components.

Port Numbers on Upgrade
On an upgrade the new Apache HTTP server instance is initially configured to use port 8023. This means that if you are upgrading more than one environment, you need to manually change the port numbers used by new instances as required (i.e. before proceeding with another upgrade).

Editing your HTTP Server Configuration
If you aren't sure how to edit your HTTP server instance configuration, Appendix A of the Presto 3.2 User Guide includes a section addressing this topic.

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

Step 5. Start the EXODUS51 Subsystem.

Presto uses the EXODUS51 subsystem to manage transferring data between the PC designer and the IBM i.

When the server side installation finishes use the WRKACTJOB command to check if the EXODUS51 subsystem has been started. If this is a new install, it should be started automatically.

If this is a second install, or you already have another BCD tool installed on your system that uses EXODUS51, the install will not start the subsystem automatically. In this case you can start the subsystem at this point using this command:

STRSBS XL_EX51/EXODUS51

Once the subsystem has been started continue to the next step.

Starting the Exodus51 Subsystem After an IPL
If you IPL your IBM i nightly or on the weekends, you need to also restart TCP/IP services and the EXODUS51 subsystem. While you probably already have processes in place to restart TCP/IP, you can add the command STRSBS XL_EX51/EXODUS51 as part of that process. The EXODUS51 subsystem contains an auto-start job that runs constantly to monitor and dispatch Exodus51 conversations to the appropriate server programs.

While you are evaluating the software you may elect to start it manually. But if Presto doesn’t work for you on a Monday morning, this is probably the reason!

  
Troubleshooting   

Installing Multiple Environments?
If you are installing multiple Presto environments, second and subsequent environment installations (and HTTP server instances) default to using port 8023. If you are installing a third environment, you need to make sure that use a unique port number in your config before starting the server instance.

If you have any questions about this process, please contact Technical Support.

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

Step 6. Confirm your Server Installation.

Once you complete your IBM i installation you should be able to connect to your IBM i through Presto and begin running your IBM i applications.

To test whether your server components have been installed and configured correctly, type your IBM i IP address below and click the button to the right:

. . .

When you click this button, your browser will attempt to launch this URL: http://xxx.xxx.xxx.xxx:8022/presto/presto (replacing the x's with your IP address). 8022 is the port number on which the XL_PRESTO HTTP server instance will be listening.

If the server side of Presto was successfully installed, you should see your IBM i Sign On screen rendered using the default Presto skin:

IBM i Sign On Screen with Presto

If you don’t immediately get a succesful connection, check the troubleshooting suggestions at right. If you can't resolve the problem, finish the installation process and then contact Technical Support.

  
Troubleshooting   
QTMHHTTP’s MSGQ

The User Profile QTMHHTP1 must have *ALL authority to QTMHHTTP’s MSGQ.

To determine this you can run the command: WRKOBJ OBJ(QTMHHTTP) OBJTYPE(*MSGQ) and take a 5 to display authority. If QTMHHTP1 is not in the User list or has an object authority other than *ALL you can run this command to edit QTMHHTTP’s MSGQ authority: EDTOBJAUT OBJ(QUSRSYS/QTMHHTTP) OBJTYPE(*MSGQ).

Virtual Terminals

To use Presto you must have enough available virtual terminal jobs. To check this use the command DSPSYSVAL SYSVAL(QAUTOVRT). The value that appears should represent at least 3-5 times the maximum number of users you anticipate could be connected to your system. If it is 0 or low, prompt the command CHGSYSVAL SYSVAL(QAUTOVRT) to change it to a higher value.

QUSRWRK Subsystem

QUSRWRK Subsystem Some of the Presto jobs must run within the QUSRWRK subsystem, which must be active. Run the command WRKACTJOB SBS(QUSRWRK) to check this. If it isn't, start it with the command STRSBS QSYS/QUSRWRK.

If you have a question about the install, give us a call. You can reach our Technical Support team at (250) 655-1766 [7:30-17:00 PST] or the Sales team at (630) 986-0800 [8:00-17:30 CST]. You can also email us.

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

Step 7. Install the Presto Designer.

Follow the steps below to install Presto Designer (the PC design tool):

1. Download the latest version of the Presto client to your PC. When the download finishes execute the downloaded file (PrestoClient-3.5.exe) to unpack the install files and initiate the install.

2. This window appears (the exact release level shown may vary):

PC installation

3. Follow the instructions to install Presto on your PC. When the installation is complete, click Finish.

The install will prompt you to automatically run the software (you can also run Presto from your Start menu, at Start/Programs/Presto/Presto).

When you first launch the software Presto will check whether you have defined a connection to your IBM i, and if not, will prompt you to create one:

Create a Connection

Continue with the next step to define your IBM i connection for the Designer.

  
Troubleshooting   

Note: Presto 3.5 requires that the Microsoft .NET Framework 4.0 be installed on your PC.

If you do not have this version on your PC you need to complete the steps to install in on your PC before the Presto install can be completed. Because the .NET Framework 4.0 is considered by Microsoft to be an optional update, it’s possible that you won’t yet have it on your PC. This is a large file and may take some time both to download and install the first time. For more information, search microsoft.com for “.NET Framework 4.0”. Subsequent Presto PC installs and updates should only take a few seconds.


Step 8. Configure the Presto Designer to Connect to the IBM i.

To work with your applications using the Presto Designer you must create a connection to the IBM i so the Designer can communicate with the server. Follow these steps to set up your server connection.

1. On startup the Presto Designer checks whether you have configured a server connection. If not, it prompts you to add one:

new connection

Complete the values as described below:

FieldValue
NameEnter a descriptive value for this connection.
Server Address Type your IBM i IP address.
PortThe default value of 4015 should usually work for you. See the sidenote for details.
LibraryThe default install library is XL_PRESTO. Use this value unless you specified something different during the install.
URLhttp://yoursite:8022/prestoadmin/presto is the default value for this field, but the correct URL should be defaulted in after you move away from the Server Address field.

2. After entering your settings use the Test button to verify your configuration. Presto prompt you to sign on to your IBM i. When you click OK at the Login window, Presto should confirm that you have connected.

3. After Presto verifies that your connection is working, click OK to save the connection. You’ll then see it listed here:

Communication configuration

4. Click OK again at the list of Environments shown above. When you do this, Presto will finish launching the Designer. If prompted, log in to your IBM i again.

After logging in, the Presto IDE will launch, displaying a web version of your IBM i login screen, similar to this:

Presto IDE

Now continue with the next step.

  
Troubleshooting   

Here are a couple of things to check if you don’t get a successful connection:

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

Other Connection Errors
If the subsystem is up but you can’t connect, add XL_EX51 to the library list of your IBM i session and run the command ZDSPERRLOG to display a list of your connection attempts. Check for error messages (such as invalid User IDs, etc.).

If you can't spot the problem immediatly give us a call. You can reach our Technical Support team at (250) 655-1766 [7:30-17:00 PST] or the Sales team at (630) 986-0800 [8:00-17:30 CST]. You can also email us.

Port 4015
Port 4015. The default EXODUS51 port of 4015 usually works. If port 4015 is in use you can change the default port for incoming connections on the server using the XL_EX51/ZCFGTCP command (press F4 to prompt the command). Then enter a matching value here. If you change the server-side port value(s), restart the EXODUS51 subsystem.

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

Step 9. Set Your Server Connection Defaults.

Every environment you create has its own server and auto-detection settings. Select Presto’s Tools/Server Connection menu option to work with these:

Server Connection

The default values for these settings should work well enough for you to get started with Presto.

Note: The critical options to take note of above are ‘Include fields in screen identifier’ and the Auto Detection settings. Before you get too far with adding customizations to your site be sure to read Chapter 7 of the User Guide, Assess Your Auto Detection Settings, to understand how Presto uses these settings.

From here you can also turn on the option to use a WebFacing connection, as described above and explained further in Appendix A at the end of the Presto User Guide.

  
Troubleshooting   

Adjusting Auto Panel Detection Defaults
As an example of the type of change you may need to make later, notice that the Auto Screen detection for an 80 column display is set to scan from positions 15 to 65 of row 1. This is where Presto will look to find a program title that it will use as part of its criteria for identifying the panel. However, if that area includes variable information (like date or time fields) and your static program titles are normally in another spot, you may need to adjust it.

Configuring your HTTP Server Instance
If you aren’t sure how to access and work with your HTTP server instance configuration please refer to the section “Working With the Presto Apache HTTP Server Instance” in Appendix A of the User Guide.

Virtual Terminals and CCSID Settings
With certain languages (for instance DBCS languages) it is necessary that the virtual terminal session created have specific device description characteristics. If you need to configure Presto for one of these languages, please refer to the section “Virtual Terminals and CCSID Settings” of Appendix A of the User Guide.

Adding Support for Multiple Languages
To configure Presto to support multiple languages, please ues the instructions in the section “Configuring Presto for Multi-Language Support” in Appendix A of the User Guide.

You can also search our Knowledge Base Opens new window on these topics.

Step 10. 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 Presto. If you haven't already, we highly recommend you watch our Getting Started with Presto webinar.

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!