Using CA AppLogic® › Appliance Developer Guide › Creating Appliances › Distribution Installations › IIS03W/IIS03S/IIS03E/IIS03DC: Installation Reference

IIS03W/IIS03S/IIS03E/IIS03DC: Installation Reference

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

• IIS03W - WIN03W
• IIS03S - WIN0364S
• IIS03E - WIN0364E
• IIS03DC - WIN0364DC

First create the Windows Server appliance WIN03y as described here.

Note: In the following instructions, the y placeholder in WIN03y 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).

To install and configure the IIS03y appliance

1. Create an application that contains an instance of WIN03y and branch the instance (referred to below as a singleton).
2. Configure the singleton's default resources to cpu=1 and memory=1G to speed up the appliance creation process.
   1. Select the singleton in the infrastructure editor.
   2. Select Resources in the Appliance menu.
   3. Modify the default resources as specified above.
3. Resize the WIN03y boot volume, if necessary, to verify that there is at least 1Gb of free disk space (use the vol resize command in the web shell).
4. Edit the class and enable the external interface.
   1. Select the singleton in the infrastructure editor.
   2. Select Modify Boundary in the Appliance menu.
   3. Select the Interfaces tab.
   4. Select the External Interface check box under Raw Interfaces.
5. Start the application and open up the graphic console of the singleton using the CA AppLogic® GUI (on the Applications tab, select your application and login to the graphical console using the Login button at the top of the page.
6. Login to the Windows appliance as the administrator.
7. Install the .NET Framework 3.5 SP1, if it is not already installed.
   1. Configure the external interface with usable network settings (this is the first enumerated network interface).
      • Access Control Panel, Network Connections, Local Area Connection X, Properties, Internet Protocol (TCP/IP), Properties; click on Use the following IP address and enter usable values for your grid (IP Address, netmask, gateway, DNS server)

      Or, in the command shell, perform the following:

      netsh interface ip set address name="Local Area Connection X" static [ip-address] [netmask] [gateway] 1 
      netsh interface ip set dns name="Local Area Connection X" static [dns-ip] 
      

   2. Download and install .NET Framework 3.5 SP1.
8. Install IIS components.
   1. Navigate to Control panel, Add or Remove Programs, Add or Remove Windows Components
   2. Select Application Server and Details and check the following:
      • Application Server Console
      • Enable network COM+ access
      • Under the details section for Internet Information Services(IIS) check the following:
      • Common Files
      • File Transfer Protocol (FTP) Service
      • Internet Information Services Manager
      • SMTP Service
      • Under the details section for World Wide Web Service check the following:
      • Active Server Pages
      • Remote Administration HTML (If present)
      • World Wide Web Service
   3. Clear all Application Server components which are not listed above.
9. 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.
   1. To find the internal IP address of the grid controller, in a command line shell execute the following command and note the IP address of the DHCP server for the last enumerated interface (for example, Local Area Connection 5).

      ipconfig /all 
      

   2. 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 on the msi file and select Save Target As to download the file to the desktop.
   3. Double-click on the msi file on the desktop to perform the installation.
   4. Delete the msi file and empty the Recycle Bin.
   5. Delete junction points on Windows volumes as described in the Windows Server appliance WIN03y.
10. Remove the file /appliance/passwd.stamp in a Cygwin bash shell; this verifies the appliance will generate a new Administrator password on the first boot after installation.
11. Stop the application and edit the class.
    1. Change the class icon color to blue.
    2. Change the class name to IIS03y.
    3. Change the class description (for example, Web Server Appliance - based on Windows Server 2003 Standard Edition R2 32/64-bit (v1.0.0-1); IIS and ASP.NET included).
    4. Change the Documentation URL to http://doc.3tera.com/AppLogic31/en/Catalog_Ref/index.htm?toc.htm?CatWebServersIIS.html.
    5. Change class category to Web Servers.
    6. Add a placeholder volume (name: content; mount on D:\).
    7. Remove the external interface.
    8. Right-click on the singleton and select Attributes. Change the instance name to IIS03y.
    9. Modify the terminals:

1. Mark the net terminal as a gateway.
2. Add the following properties:

1. Set resources:

1. Verify the health of the singleton's boot volume by executing the following command from the web shell:

   vol fscheck name_of_volume 
   

2. Move IIS03y to a catalog (we recommend system_ms).

   The IIS03y appliance is now ready for use in your CA AppLogic® applications.