1

2 March 2015

Webdev 19 Server Setup Procedure on Windows Server 2012 R2 – Draft 01

This document is an attempt to provide detailed step by step instructions to guarantee a successful

WEBDEV 19 server setup on Windows Server 2012 R2. I have consulted both the Pcsoft “WebDev

Deployment” instructions (which are cryptic and confusing), and have also referred to the helpful

“WAS Installation Cookbook” by Tim Fishbeck. Neither of these appears to have been updated for

Windows Server 2012. These instructions are not necessarily correct but they have worked for me as

far as I they go.

It would be great if others would add to this so that a definitive document can be evolved.

In particular it would be very helpful if suggestions could be made for correcting the error shown at

the end of this document. After 3 days, 3 server wipes and reinstalls, and hours of head scratching it

has become clear that this is sorely needed. It shouldn’t require a specialist with forensic Voodoo

skills to do this.

I will be happy to take suggestions for evolving this document so that it can be of use to the wider

WX community. Some comments on the pros & cons (if any) of 32bit vs 64bit installations would be

useful.

Table of Contents

INSTALL & SET UP FTP (File Transfer Protocol) ....................................................................................... 2

INSTALL THE WEBDEV APPLICATION SERVER ....................................................................................... 15

INSTALL THE HFSQL SERVER.................................................................................................................. 19

DEPLOY YOUR APPLICATION TO THE SERVER ....................................................................................... 20

REMARKS ............................................................................................................................................... 23

2

INSTALL & SET UP FTP (File Transfer Protocol)

FTP is needed in order to be able to upload the WebDev Application Server (“WAS”) & HFSQL Sever

installation files. The PCsoft instructions state that the server should be set up with an admin user

and then separate users and sub directories are automatically added for each developer who will

create sites on the server. This way each developer’s sites and access can be kept separate.

(If only one developer is going to use the server I believe that the server can possibly be setup more

simply without the extra users and subdirectories, but this is not what we are going to do here).

These installation instructions assume a virgin installation of Windows Server 2012 R2.

Install Web Server IIS using “Add Roles & Features.”

3

Select “Web Server IIS”

Click “Next” & select “FTP Server” and select “Service” & “Extensibility” options.

4

Install the Features and wait till the “Installation Successful” message appears.

You should now see the IIS Server in the list of servers.

5

Now its time to create a WB user group and a WB Admin user in Computer Management.

Create a group which we will call WB_FTPUSERS.

6

Create a user which we will call “WB_FTPADMIN.” Note the recommended status of the checkboxes.

WB_FTPADMIN should be added as a member of group “WB_FTPUSERS”.

7

Create the following target directories for WB generated sites & data. These could be anywhere but

it’s convenient to group them like this: WB, WB/Data, WB/Ftp, WB/Services, WB/Sites.

8

Then add the WB_FTPUSERS group to each of the target directories in turn and ensure that they

have the following rights. (Or could one simply add the group & rights to the WB/ directory?):

Add the WB_FTPUSERS group and rights to the WB/Data directory.

9

Add the WB_FTPUSERS group and rights to the WB/Ftp directory.

10

Add the WB_FTPUSERS group and rights to the WB/Services directory.

11

Add the WB_FTPUSERS group and rights to the WB/Sites directory.

12

As a precautionary measure restart the server to ensure everything is set OK.

In IIS Manager, right click “Sites” and “Add FTP Site” which points to the “WB/Ftp” directory:

13

If you do not have an SSL certificate, select “No SSL.”

Set the following settings.

14

Using Filezilla you should now be able to connect to the server via FTP with your server IP address

and the following Settings:

You should get this status message in Filezilla to indicate successful connection.

15

INSTALL THE WEBDEV APPLICATION SERVER

Using an FTP client like Filezilla upload the WebDev Application Server installer file, which in this

case is the 10 user test server “WB190PACKUS10CNX056s.exe” which can be downloaded from the

PCsoft website. Make sure it is the latest version or a version matching the version of your

development environment.

16

The installer is now on the server in the WB/Ftp directory.

17

Run the installer and accept all the defaults. After installation run the WebDev Administrator and

edit the default admin account that has been automatically setup.

Set the target directories as previously set up:

18

To test the server parameters, in WebDev, use “Deploy the Site Remotely” and use the following

settings. The default password for the ADMIN account is “admin”. Test the parameters and a

message should appear saying that the server parameters are valid.

19

INSTALL THE HFSQL SERVER

Using FTP upload the latest HFSQL installer to the server (in this case

WX190PACKUSHFSQLCS056.exe. Run the installer and follow the instructions.

This part needs documentation.

20

DEPLOY YOUR APPLICATION TO THE SERVER

When remote deploying my app, this message appears:

A message relating to this error on the forum indicates:

“it was the missing permissions for "c:\webdev 14" for the webdev admin account at the server

machine. Now everything works.”

21

So I enabled WB_FTPUSERS the following rights for the WebDev19 directory.

22

I also enabled IUSR rights in the WB/Data/app directory.

I also enabled IUSR rights in the WB/Sites/app directory.

23

But I still get this error message:

THIS IS AS FAR AS I HAVE GOT. CAN ANYBODY PLEASE SUGGEST HOW TO GET PAST HERE?

REMARKS

I enabled read and execute for WB_FTPUSERS for the WB/ Ftp, Data, Services, Sites directories

whereas I think probably its only needed for the WB/Ftp directory.