Setting Up Web3
This document is intended for system personnel and describes setup of the AppFrame CR3 Web3.
Before installing AppFrame CR3 you need to have the following installed:
- SQL Server 2008 Express
- Web Server with ASP.NET 3.5
- Visual Basic 2008 Express Edition SP1
- DevExpress controls for Winforms
SQL Server Express 2008 Management Studio, which can be downloaded from here
Visual Basic 2008 Express Edition, which can be downloaded from here
Install IIS
Windows Vista
- Install Microsoft IIS 7 with Application Development Features
- Control Panel\Programs and Features -> Windows Features
- Check the Internet Information Server (IIS option – Application Development Features)
Windows Server 2008
- Add Role Web server through Server Manager with Default Role Services, but check of for Application Development.
- Add Feature .NET Framework 3.0 after a restart of the server.
- Install .NET 3.5 from http://www.microsoft.com
- Start the ASP.NET State service and set it to Automatic start at startup.
Setup website in IIS
Add a website to IIS
Web3 Structure in IIS is different then from Web2. Now all web application is an Application in IIS. In Web2 there was an application folder that holds all application files. (If you copy a Web3 site you need to Right Click – Covert to Application on all applications.
AppFrame.Config
AppFrame.Config is brand new. Instead of using AfDataService to get the Service info we now either specify it in AppFrame.Config or if <Services Auto = "True"> then it uses the service sites XML file to get the service info.
In DMZ where you need a double access layer you need to use the WebRemotingHost and set this. This site is the remoting site that you have in your inside network, then the DMZ site goes to the Inside site to get connection to the SQL Server. (Remember that the DMZ server needs access to the Inside Web server though the port that the site is setup on.)
Web.Config
Web.Config is brand new. The machine key will be in the Web.Config to all web applications. AfMembershipProvider will trigger every time a web application is open and will verify the application through the machine key. AfMembershipProvider will also verify the user on Login and dose this every time a user tries to access a web application in the Site. But because Web3 uses ASP.NET Session State service it will only be used if there is no session. If you open Mailbox twice it only verifies the application and user the first time.
With the new access layer the Web3 is using new lines in web.config with the new AppFrame3.Common.RemotingLoader.dll
AppFrame publisher
AppFrame Publisher is a service you can install on your web server and configure to access your SQL Database and get the Web3 project that is newly published. It can be set up with one Web site and one SQL Database or more.
The User that AppFrame Publisher runs under needs to be administrator on the Web server
Web3 Projects in CR3
After you have installed AppFrame Publisher and are ready to publish the sys.<Web3projects> you first need to set a Website Location.
CR3: Development -> Web3 Projects - > Tools - > Manage Website Location
You are now ready to Publish Web3 projects to the web server:
