8. this case, you’ll choose a .NET 4 .0 and Integrated pipeline mode application pool ( ASP .Net 4 ) .

12. Configuration redirection If you wish to share the configurations made in WebAdmin across your applications you need to place a file in each application to redirect the configuration location. This file can be downloaded in We bAdmin in: System Configuration > Application. If your applications and administration website are all installed on the same machine you can just download the Configuracoes.redirect.xml file and install it in each application, without modification. Afte r downloading the file, place it in the “Physical Path” of your applicatio ns, next to the Web.config file.

7. Setup the application websites To install a Qweb application, right click on QWeb folder inside the “Default Web Site”, choose “Add Application, be sure to choose the right “Application pool” for the web site, in this case, you’ ll choose a .NET 2.0 and C lassic pipeline mode (Classic .Net AppPool) Additionally you’ll need to add the default document since this is a “Classic” web site application. Simply choo se the Qweb Application, click on “Default Document”, click on “Add” and type the html index file of your web site, the html file name is composed by <system symbil>Index.html, in this example, ERPIndex.htm For the MVC site, you would have to right click on MVC folder inside the “Default Web Site”, choose “Add Application ” , be sure to choose the right “Application pool” for the web site, in

6. 3. IIS Applications In order to run the websites you’ll need to convert the website folders to application . In this case we’ll convert first the administration website and later each application. S etup the administration Website . Inside the “ WebAdmin ” site , choose “Add Application”, be sure to choose the right “Application pool” for the administration web site, in this case, you’ll choose the previously created application pool the “WebAdmin” .

11. 2. Create or Update de database schema. 2.1. Click on “Data Base Maintenance” In this area you can Upgrade the Schema version, execute maintenance scripts e some others database related operations. To properly run any operation, first, make sure you have correctly set up the System Configuration 2.1.1. You’ll need to run this maintenance tasks each time you install a new applica tion version. When you run the maintenance task on a system the first time it will present the Schema Version as 0, meaning the database doesn’t exist. In this case It’s also advisable to expand the “Advanced Maintenance Options” and check the “Create defa ult Quidgest user” option.

10. 1.1.6. “ System Symbol ” – Three - letter symbol that represents your system, eg: ERP. 1.1.7. “Username” , “Password” and “Password confirmation” – The username used by the application for database access, the respective password, and “Pass word confirmation” used to avoid typing errors. 1.1.8. “Default Year” – Only in systems with “database per year” option, specify the database year.

5. 2. Secondary Website 1. Create a secondary website for better isolation and security. Although it is not mandatory, it’s highly recommended to maintain all the administration websites running on a different port. In order to do this, you’ll have to do the following steps: 1.1. “Add Web Site...”, fulfill the site name e g : “WebAdmin”. 1.2. In “Application pool” choose the previously created “WebAdmin”, and use the folder that contains your published WebAdmin application as the “Physical path” 1.3. In Port we suggest port 88, although you can choose any other port.

3. Setup configuration 1. Application Pools First , you'll need to the IIS Manager, to do this, open the Windows Control Panel, then, Administrative Tools and finally open the Internet Information Services Manager. 1.1. C reate the Application Pools . This application pool allows you t o run the Administration portal with higher p rivileges . Add Application Pool, choose .Net Framework v4 and Managed Pipeline Mode as “Integrated”. Then select the newly created appl ication pool, and click on “Advanced Settings”, and change the “Identity” to “LocalSystem” .

4. 1.2. For QWeb applic ations . M ake sure you have an application pool with .Net 2.0 and Managed Pipeline mode “Classic” 1.3. For MVC applications . M ake sure you have an application pool with .Net 4.0 and Managed Pipeline mode “ Integrated ”

2. Requirements 1. Operating System: 1.1. Windows Server 2008 or higher 2. Operating System components : 2.1. IIS 7 .0 2.2. For QWeb applications Framework .N et 2.0 2.3. For MVC applications Framework .N et 4 .0 3. Third party components 3.1. Crystal Reports assemblies

9. 4. Application base Setup Accessing the Web Administration website. Open an web browser, on the address bar type http://<servername>:88/<sitename>Admin where < server name > is your IIS server name, case you didn’t create the secondary website or simple decided t o use another port, use the port you selected. On < site name > you must type the website name plus the word Admin whose administration you want to access. In our example, we will access the administration website. 1. Setup the database connection . 1.1. Click on “System Configuration” Here you can setup the basic database configuration options for your Quidgest Web Solution. 1.1.1. “ Database Server name ” – Input the server name or SQL full instance name. 1.1.2. “Port” – Input the Database server port number or leave it for default value. 1.1.3. “ Service (ORACLE) ” – Service name, only used in Oracle database systems. 1.1.4. “ Database Server Type ” – Select your database system. 1.1.5. “ Database suffix name ” – Usually used when there’s multiple databases of the same system in the same server , the d atabase name will be named the following way, <system symbol><database suffix name><year>. Eg: ERPProduction201 9 , where “ERP” is the system symbol, “Production” is the database suffix name and “201 9 ” the year, case your system isn’t using the database per year, it will use 0 as year value.

1. Website deployment on IIS7 Contents Requirements ................................ ................................ ................................ ......................... 2 Setup configuration ................................ ................................ ................................ ................ 3 1. Applica tion Pools ................................ ................................ ................................ ........ 3 2. Secondary Website ................................ ................................ ................................ ........ 5 3 . I IS Applications ................................ ................................ ................................ .............. 6 3 . 1. Setup the main websites. ................................ ................................ .............................. 6 3 . 2. Setup the administration Websites. ................................ ................................ ............... 6 4 . Application base Setup ................................ ................................ ................................ .. 9 4. 1. Setup the database connection. ................................ ................................ .................... 9 4 . 2. Created or Update de database schema. ................................ ................................ ..... 11