This page explains how to host easyTravel.net on IIS 7.5 on Windows 7 64bit.
Note that IIS requires the PaymentBackend to be started with the 64bit version of SQL Server CE on 64bit machines.
So ensure that you have installed the 64bit version of easyTravel!
Also note that BusinessBackend should be running before IIS is started to be able to use all Plugins!
IIS Installation & WCF Activation
Ensure IIS is installed:
Control Panel > Programs and Features > Turn Windows features on or off > Tick Internet Information Services (see screenshot at the end of this page)
Ensure WCF Activation:
Control Panel > Programs and Features > Turn Windows features on or off > Tick Microsoft .NET Framework > WCF HTTP Activation
Ensure Message Queuing is installed:
Control Panel > Programs and Features > Turn Windows features on or off > Microsoft Message Queue (MSMQ) Server > Tick MSMQ Server Core
Create IIS WebSites
- open Control Panel > Administrative Tools > Internet Information Services (IIS) Manager
- In the connection tab on the left side open localhost
- Right Click on "Sites" then select "Add Web Site"
- point physical path to dotNET/dotNetPaymentBackend of your easyTravel 64 bit installation
- give an arbitrary name, e.g. dotNetPaymentBackend
- set port to 9010 by default
- click ok
Set correct .net Framework Version
ApplicationPools > application pool where the application runs > Advanced Settings > (General) > .NET Framework Version = v2.0
Configure IIS to use User Profiles
in IIS Manager:
ApplicationPools > application pool where the application runs > Advanced Settings > (Process Model) > Load User Profile = true
Disable 32bit Applications in application pool because we are running 64bit easyTravel (can be omitted for frontend)
SQL Server CE needs to run in a 64bit process!
ApplicationPools > application pool where the application runs > Advanced Settings > (General) > Disable 32-Bit Applications
Change Identity of paymentBackend Application Pool to Local System (can be omitted for frontend, except you are running as Administrator)
Payment Backend has to run as LocalSystem in order to be able to access the named pipe provided by the native application
ApplicationPools > application pool where the application runs > Advanced Settings > (Process Model) > Identity = LocalSystem
the payment Backend should now be operating.
Repeat this steps for dotNetB2BFrontend using port 9000 by default
Configure easyTravel Scenario to not start separate .NET procedures (can be omitted since easyTravel 220.127.116.112)
In the default Scenarios in easyTravel would start another instance of the .NET procedures, something that you probably do not want if IIS is hosting these already. easyTravel allows to configure the Scenarios and thus allows to remove the .NET related procedures from the Scenario that you start.
In order to achieve this, follow these steps:
- Open the file
- Locate the Scenario that you want to adjust, e.g. search for
Remove the procedure-entries for "payment backend" and "b2b frontend", the result will look something like this
- restart easyTravel and then start the Scenario that you adjusted
If you are later upgrading easyTravel to a newer version, it may happen that a new scenario-file is created from scratch, in this case follow these steps again to adjust the latest version of the scenario file. A copy of your changes is available in the config-directory
See Demo Applications - easyTravel#Demo Scenarios for details about adjusting scenarios.
Access to the path '....\resources\easyTravelConfig.properties
Grant read rights to IIS_IUSRS to the file specified. (Right click on file in explorer --> Security)
Strange errors in web.config
Go to Control Panel -> Programs and Features -> Turn Windows Features on or off
Now make sure that at least the following IIS Settings are checked: