Creating Appliances › Distribution Installations › IIS08W/IIS08S/IIS08E/IIS08DC: Installation Reference

IIS08W/IIS08S/IIS08E/IIS08DC: Installation Reference

Each IIS08y appliance is built using the following generic Windows Server appliance as a base class:

• IIS08W - WIN0864W
• IIS08S - WIN0864S
• IIS08E - WIN0864E
• IIS08DC - WIN0864DC

First create the Windows Server appliance WIN08y as described here.

In the following instructions, the y placeholder in WIN0864y and IIS08y is for the Windows edition that the appliance/app is based upon (S for Standard, E for Enterprise, DC for DataCenter, W for Web).

1. Make a new singleton from WIN0864y:
   • Create a new application. Include an instance of WIN0864y and branch the class. Assign 1 cpu and 1GB of memory to the singleton.
   • Start the application and SSH into the singleton. Set a new Administrator password (net user administrator password - select a password).
   • Access the graphic console of the singleton in one of the following two ways:
     • Select the application within the application list in the GUI and click on the icon for Login (graphic).
     • Open the application in the infrastructure editor and select the singleton. Use the pull-down Appliance menu to select Login (graphic).
2. Install the IIS role and role services:
   • Start the Server Manager->Add Role. Add the IIS Web Server Role. Add the following Role Services:

     Common HTTP Features:
        Static Content 
        Default Document 
        Directory Browsing 
        HTTP Errors 
        HTTP Redirection 
     Application development
        ASP.NET 
        .NET Extensibility 
        ASP 
        CGI 
        ISAPI Extensions 
        ISAPI Filters 
        Server Side Includes 
     Health and Diagnostics
        HTTP Logging 
        Request Monitor 
     Security
        Basic Authentication 
        Request Filtering 
     Performance
        Static Content Compression 
     Management Tool
        IIS Management Console 
        IIS Management Scripts and Tools 
        IIS 6 Management Compatibility:
           - IIS 6 Metabase Compatibility 
           - IIS 6 WMI Compatibility 
           - IIS 6 Scripting Tools
     

3. Install the IIS msi. This self-executing installer can be downloaded from the grid controller through the default interface of the singleton. This interface has already been properly configured through DHCP.
   • To find the internal IP address of the grid controller, in a command line shell execute ipconfig /all and note the IP address of the DHCP server for the last enumerated interface (for example, Local Area Connection 5).
   • Point IE at http://IP-address:8080/download/ and download the current Windows IIS msi (for example, IIS_Windows-1.0.0-1.msi):
     • Right-click the msi file and select Save Target As to download the file to the desktop.
   • Double-click the msi file on the desktop to perform the installation.
   • Delete the msi file and empty the Recycle Bin.
4. In a Cygwin bash shell (right-click on the appliance in the infrastructure editor and click on login to get into cygwin bash shell)
   • Set a new complex password (for example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe).
   • Exit the SSH session.
   • SSH into the appliance and execute rm -f ~/.bash_history /appliance/passwd.stamp.
   • Exit the SSH session.
5. Stop the application and right-click the appliance in the infrastructure editor, select Modify Boundary to edit the class:
   1. Change the class icon color to blue
   2. Change the class name to IIS08y
   3. Change the class description (for example, Web Server Appliance - based on Windows Server 2008 Standard Edition R2 64-bit (v1.0.0-1); IIS and ASP.NET included)
   4. Change class category to Web Servers
   5. Add a placeholder volume (name: content; mount on D:\)
   6. Remove the external interface
   7. Modify the terminals:

• Mark the net terminal as a gateway

Add the following properties:

Set resources:

1. Move IIS08y to a catalog (system_ms is recommended).
2. The IIS08y appliance is now ready for use in your CA 3Tera AppLogic applications.