How to Configure the PageGate Web Interface Transcript for Video:
Welcome to the video tutorial on how to configure PageGate’s GetWeb interface. In this tutorial, we’ll be going over the different configuration options and methods for GetWeb.
Before we begin, the GetWeb interface relies on an external web server; PageGate does not host its own web services, it only provides a CGI executable that can be used on a web server. This can be a local installation of IIS or Apache on the PageGate server or any web server on the same network as the PageGate server.
It’s also important to note that PageGate does not handle any security methods on the web server; it relies solely on the web server for any security configuration you may want for your messaging sites.
In this tutorial, we’ll be going through configuring the GetWeb interface to reference a locally installed copy of IIS.
Before we can configure things in PageGate, we’ll need to create a directory for the GetWeb CGI executable. To do that, open a file browser in Windows and browse in to your c:\inetpub\ folder. Just to note it, if you already have a directory where CGI executables should reside, you can skip this step.
Here in the inetpub folder, create a new folder: pgscripts
Now open the PageGate Admin and go to Interfaces – GetWeb – Settings.
The Web Pages path will need to be set to the folder on the web server that web pages should be published. By default in IIS, this path is c:\inetpub\wwwroot\
The CGI data path will need to be the folder you just created. By default, c:\inetpub\pgscripts\
Set the CGI URL to the IP address, machine name or domain name of the web server GetWeb is referencing, including the directory you’ve specified for the CGI data path. For example, if our PageGate server’s machine name is PG01 and our CGI Data path is set to the ‘pgscripts’ folder, our CGI URL would be:
Check Enabled, click Apply and tell it Yes, you do want this to be enabled for all existing groups and recipients.
Now go to the Program – Settings section. In the ‘Run on this Server’ section, check GetWeb, then click Apply.
If you’re running PageGate as a Windows service, you will be prompted for credentials. Leave them blank and click Apply.
Now that we’ve configured the basics in PageGate, we’ll need to configure the web server to allow our CGI executable to operate. To do that, open the IIS Admin.
Next, select the server object on the left hand side. In the middle, find ‘Handler Mappings’
Find CGI-exe, right click on it and select ‘Edit Feature Permissions’
Check ‘Execute’ then click OK.
Select the server object on the left hand side again. In the middle, find ISAPI and CGI Restrictions.
Right click in the available space and select ‘Add’.
The ISAPI or CGI path will be the directory you specified in the CGI Data path in the PageGate Admin. Click the ellipses (…) button and browse in to the c:\inetpub\pgscripts\ folder.
Change the file type from *.dll to *.exe
Double click ‘webgate.exe’ to select it.
In the Description, enter: GetWeb CGI Executable
Check ‘Allow extension path to execute’, then click OK.
Now we’ll need to create a virtual directory association for our scripting folder and set the permissions to access it. To do that, expand Sites and Default Website.
Right click on Default Website and select ‘Add Virtual Directory’.
Set the Alias to: pgscripts
Set the Physical Path to: c:\inetpub\pgscripts\
Right click on the new virtual directory and select ‘Edit Permissions’ and go under the Security tab.
Here in the Security tab, you’ll need to grant the appropriate users or usergroups access to submit information to the CGI executable. Typically speaking, we recommend adding IUSR and Domain Users accounts, granting them read and modify, and adding the Domain Admins group with full control. These permissions are directly controlled by your network’s security configuration, please contact your network administrator if you’re unsure of what permissions to declare.
At this point, your web server has been configured to recognize and allow our CGI executable to function and the system is primed to start accepting messages from your messaging websites.
This concludes the video tutorial on how to configure the GetWeb interface.