PageGate can be integrated with Fedena School ERP by having Fedena School ERP reference PageGate's Web API.
PageGate's GetWeb can be tied to IIS (intranet or internet) to provide a CGI executable for Fedena to use.
To configure GetWeb and IIS, this is what you'll want to do:
Open the Pagegate Admin.
Go to Interfaces - GetWeb - Settings.
For the Web Pages path, if you're referencing a local installation of IIS, use c:\intepub\wwwroot\
If you're referencing a shared web server on your network, specify the UNC path to that web server's website publishing directory.
For the CGI Data path, if you're referencing a local installation of IIS, use c:\inetpub\scripts\
If you're referencing a shared web server on your network, specify the UNC path to that web server's scripting directory.
For the CGI URL, if you're referencing a local, intranet only web server, use http://<servername>/scripts/webgate.exe
If you're referencing a network or internet web server, use http://<webserver>/scripts/webgate.exe
Click on Apply.
If prompted, you do want to enable this for everyone.
If you configure the GetWeb module to referenc UNC paths, be sure to provide the PageGate GetWeb windows service with the appropriate credentials to access that information.
Now we'll need to configure IIS to recognize and allow PageGate's CGI executable to function.
These steps are referencing a local, intranet only web server. The basic steps for configuring the ISAPI and CGI Restrictions as well as the steps for the Handler mappings are the steps you'll need to go through for a network or internet web server.
In Windows Server 2008 and 2012, the CGI-exe handler might not exist because the CGI role may not be enabled for IIS.
To install CGI for IIS, open the Server Manager in Windows and go to Roles. Then click Add Role, then under "Web Server" go to "Application Development" and check CGI.
Open the IIS Manager.
Select the Server object on the left hand side (it's the first thing listed in the tree).
Go to Handler Mappings.
Find "CGI-exe" in the list.
Right click on it and select "Edit Feature Permissions"
Put a check in Execute and click on OK.
In the left hand tree, expand Sites and Default Website.
Right click on Default Website, select "Add Virtual Directory"
Set the Alias to: scripts
Set the Physical Path to: c:\inetpub\scripts\
If you don't have a c:\inetpub\scripts\ directory, please create it.
In the left hand tree, click on the Server object at the top of the list.
On the right hand side, double click on "ISAPI and CGI Restrictions"
Right click in the available space and click on Add.
Set the "ISAPI or CGI path" to: c:\inetpub\scripts\webgate.exe
Set the Description to: GetWeb CGI Executable
Put a check in "Allow extension path to execute" and click on OK.
In the left hand tree, right click on the scripts virtual directory you created in steps 8 through 10 and select "Edit Permissions"
Click on the Security tab.
Click on Edit.
Click on Add.
Make sure that your networking domain, not the local computer, is selected as the Location.
In the "Enter the object names to select", enter: domain users
Click on Check Names.
Click on OK.
Select the Domain Users group and allow them the "Modify" permission.
Click on OK.
Now that we have the GetWeb module ready to start receiving data from Fedena, here's how to tell Fedena to send alerts to your new web API.
When configuring a web API in Fedena, you'll need to reference this in the SMS settings configuration:
With PageGate's GetWeb module, your host_url would be:
With that information, we'll need to configure Fedena to pass the USER, FRM and MSG variables by configuring this:
That way when Fedena constructs the statement to pass to PageGate's web API, it would use FRM, MSG and USER as the declared variables in the CGI statement passed to PageGate.