This article walks you through installing the Windward RESTful Engine on your server.
- RESTful Engine Install (.zip) files
- You can download the RESTful Engine install files from our website: http://www.windward.net/support/downloads/
- A RESTful Engine license key
- Email firstname.lastname@example.org to obtain a key if you do not have a license key
- Windows Server 2008 R2 or later (Windows Server 2012 recommended)
- A VM (virtual machine), cloud server, or dedicated hardware can be used
- Microsoft IIS (Internet Information Services)
- In Windows 10, you need to enable IIS. Please see https://www.howtogeek.com/112455/how...-on-windows-8/
- For information on installing and configuring IIS in other versions, refer to the following Microsoft articles:
Windows Server 2012 (recommended): https://www.iis.net/learn/get-started/whats-new-in-iis-8/installing-iis-8-on-windows-server-2012
Windows Server 2008: https://www.iis.net/learn/install/installing-iis-7/installing-iis-7-and-above-on-windows-server-2008-or-windows-server-2008-r2
- .NET 4.5.1 framework
- You can locate the .NET 4.5.1 install from the following link: https://www.microsoft.com/en-us/download/details.aspx?id=40773
Step 1 - Download, move, and rename the RESTful Engine
First, download or enable IIS and navigate to your C:\inetpub\wwwroot folder. You can name this folder whatever you want your RESTful Engine to be named.
Download the RESTfulEngine and RESTfulClient samples, then copy or move the RESTfulEngine folder (binaries from the .zip file) to your C:\inetpub\wwwroot folder. In the example below we have changed the name to RESTful Sample.
Step 2 - Create your website
Open IIS Manager by navigating to Control Panel > System And Security > Administrative Tools > Internet Information Services (IIS) Manager, or search for IIS from your start bar or Cortana.
Create a new website by right-clicking on the server (top level of the navigation tree) and choose ‘Add Web Site...’ to bring up a new interface.
In the 'Add Web Site' dialog,
- Set your Site Name, but not the application pool. Note: For help creating an Application Pool see Creating an Application Pool in IIS.
- Click the ‘Select…’ button next to the 'Application pool' text field. Click the drop down and select one of the options:
- ‘ASP.NET v4.0’
- ‘.NET 4.5’ or '.NET 4.0'
- Although you may only see .NET 4.0 or .NET 4.5, if you have .NET 4.5.1 installed, either option will work.
Next, Browse the Physical Path to the RESTfulEngine folder (which you may have renamed) in ‘C:\inetpub\wwwroot’.
For Binding, select an IP address and Port to be used for this website, and optionally a host name.
Then click OK to close the 'Add Web Site' dialog.
Step 3 - Editing Permissions
Back in the left pane of your IIS window, right-click the RESTfulEngine application you have created (in the navigation tree) and click 'Edit Permissions...' You must allow 'write' permissions for the application.
- In the properties dialog, select the Security tab, select CREATOR OWNER, and click the Edit button.
- Select the IIS_IUSRS account, and under the ‘Allow’ column, select the ‘Write’ checkbox under the permissions for the IIS_IUSRS group.
- Click OK to close the permissions dialog. Then click OK to close the properties dialog.
Step 4 - Turn Windows Features On or Off
Click "Start button" or Cortana and enter "Turn windows features on or off"
- In the new window, navigate to Internet Information Services > World Wide Web Services > Application Development Features
- Check (enable) the features. You may not need CGI.
- Click OK to save selections and exit.
Step5 - Edit your web.config file
Edit the web.config file for logging and enter a valid license key. (C:\inetpub\wwwroot\<sitename>)
The RESTful Engine is now set up and ready to handle requests.
- Be sure you set up logging and enter your license key from Step 10 above. See the web.config file.
- Your RESTful Engine should be up and running. Now, try running some Examples.
If you are receiving error messages, you may find the following helpful: IIS Tips and Tricks
If you get a message that WindwardCustomFunctions is not found, this is actually not an error, but a failsafe for developers. It lets you know whether you set up CustomCallBacks, and it can simply be ignored. (If you want to set this up, see this article about setting up custom callbacks for the .NET Engine, it is the basis for the RESTful engine).