Configure Your Advanced Installer As a Virtual Directory

Transcription

1 1 of 5 15/01/ :07 p.m. DOWNLOAD FEATURES JAVA LICENSING PURCHASE SUPPORT FORUMS Buy Configuring IIS Web Sites and Virtual Directories Download Introduction Registration Using Advanced Installer Features and Functionality Tutorials, How To's, Q&A Tutorials Simple Installation Professional Installation Professional Installation from CLI Creating transforms Creating an App-V Package Creating a ThinApp Package SharePoint Solution Installers Other Languages New Language Java Product Installation Java Service Installation IntelliJ IDEA import Patch Authoring Deploying Updates Using the Dialog Editor Configure most common SQL connections Convert Legacy Installations Visual Studio Tutorials RAD Tools Integration MSI Import App-V Import WISE Import Import/Create AppX Using SQL Scripts IIS Tutorial The IIS configuration tool helps you rapidly deploy web applications on Microsoft Windows servers family running Internet Information Services (versions 5.0 and above). This Advanced Installer utility ensures a fast and uniform installation of your web applications on multiple servers, without having to worry about manually configuring the IIS on every machine through Microsoft Management Console. This tutorial will guide you in creating Web Sites and Virtual Directories for your web application. Let's suppose your web application consists of a E-Commerce web site, called example.com. This ASP.NET web application has a main user interface for registered users and guests as well as an Administration Panel. This panel will be served from a different secure location installed on the target server, hence the need to configure a separate virtual directory for this application. 1. Add your application files 2. Add your Web Site 3. Configure Web Site Bindings 4. Configure Access Flags for your Web Site 5. Set up default documents for your application 6. Enable FTP access 7. Configure Virtual Directory 8. Configure global IIS settings (optional) 9. Run the project 1. Add your application files Go to the Files and Folders view and add your application files. The application's files for the Administration Panel, which will be handled by the virtual directory adminpanel of the web site, should be placed in a separate directory. It is redundant to add as a virtual directory a child folder of your application's web site folder, because this would already be served by your web site. 2. Add your Web Site Go to the Internet Information Services view. Use the [ New Web Site ] toolbar button to add your web site called example.com. Configure it as follows: Deploy a MSI through GPO Add trial support to your VB application Multiple Builds XML Locator Search MSM with parameters for custom actions Windows Mobile/CE Installations How To's FAQ's Windows Installer Deployment Technologies Table of Contents

2 2 of 5 15/01/ :07 p.m. 3. Configure Web Site Bindings Configure HTTP and HTTPS bindings, along with the SSL options for your Web Site. The triplet setting (IP Address, Port No, Host Header Name) defines the Web Site and therefore must be unique.

3 3 of 5 15/01/ :07 p.m. 4. Configure Access Flags for your Web Site In our scenario, the ASP.NET web application requires execute permission for the scripts as well as script access and read access. 5. Set up default documents for your application Our Web Site will automatically serve a default document when no document name is specified in the request (url). In our case index.aspx will have priority whenever found in a directory. 6. Enable FTP access Our application requires FTP access for constant updating of script content, so we will configure FTP access for the web application. We do not set the "Set NTFS security flags" option to allow only registered users on the target machine, having the proper access rights, to connect through FTP. 7. Configure Virtual Directory Our web site is set up now, we need to configure the Administration Panel as a virtual directory.

4 4 of 5 15/01/ :07 p.m. As a rule, a virtual directory inherits general configuration traits like: default document list, mime types and access flags; so, we will configure such properties for the virtual directory only when a different behavior is desired. Use the [ New Virtual Directory ] to add a new virtual directory called adminpanel. Configure it as follows: We do not allow anonymous web access to this folder for security reasons (this is an administration panel with privileged access). As opposed to the parent web site, this virtual directory needs an extra access flag (write access), so we will set it accordingly. Also we have disabled FTP access to this Virtual Directory. If you want to inherit the default document list configured for the parent web site check the Enable default document option and leave the document list blank. Otherwise, the documents configured here will override the ones configured for the parent web site. If you disable default document for a web site or virtual directory, you should enable directory browsing instead. 8. Configure global IIS settings (optional) If needed, you can also configure global IIS settings that will affect all web sites and virtual directories, such as: MIME types, ISAPI filters. We recommend that you check the Create Backup of IIS Metabase option as a configuration restore point option. 9. Run the project The End Our web site configuration is complete, build and run the package. This concludes our tutorial. To learn more, please read the Configure most common SQL connections tutorial. OUR PRODUCTS CONTACT INFO RESOURCES STAY IN TOUCH Advanced Installer News Download Subscribe to our RSS

5 5 of 5 15/01/ :07 p.m. AWR Cloud Case Studies Documentation Subscribe on YouTube AWR Desktop Testimonials Features Follow us on Twitter Lead Converter Contact Pricing Like us on Facebook Advanced Link Manager Site Map EULA Circle us on Google+ Advanced Web Stats Support QUESTIONS? WE ARE HERE TO HELP United States International, UK Caphyon Ltd. Trademarks belong to their respective owners. All rights reserved.