IIS03W/IIS03S/IIS03E/IIS03DC: Installation Reference

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

Please, 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 create the Windows Server appliance WIN03 and make the IIS03y appliance ready for use:

  1. Create an application that contains an instance of WIN03y and branch the instance (referred to below as a singleton).
  2. To speed up the appliance creation process, configure the singleton's default resources to cpu=1 and memory=1G:
  3. If necessary, resize the WIN03y boot volume to help ensure 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:
  5. Start the application and open up the graphic console of the singleton using the AppLogic GUI (on the Applications tab, select your application and login to the graphical console using the Login (graphic) button at the top of the page).
  6. Login to the Windows appliance as the administrator.
  7. If you have not already installed the .NET Framework 3.5 SP1 do so now:
  8. Install IIS components:
  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.
  10. In a Cygwin bash shell remove the file /appliance/passwd.stamp; this helps ensure the appliance will generate a new Administrator password on the first boot after instantiation.
  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 (e.g., 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 class category to Web Servers
    5. add a placeholder volume (name: content; mount on D:\)
    6. remove the external interface
    7. modify the terminals:

Terminal Name

Direction

Protocol

in

In

http

db

Out

any

fs

Out

cifs

log

Out

cifs

aux

Out

any

net

Out

any

mon

Out

cce

  1. add the following properties:

Name

Type

Default

Constraints

content_on_fs

string

off

on,off

docs_dir

string

(empty)

 

logs_enabled

string

off

on,off

logs_base_dir

string

/

 

index_files

string

default.htm default.asp default.aspx index.html

 

max_connections

integer

(empty)

min = 1, max = 999999

idle_timeout_sec

integer

15

 

data_timeout_sec

integer

300

 

  1. Set resources:

Resource

Minimum

IIS03W

IIS03S

IIS03E

IIS03DC

Default

CPU

0.10

2

4

8

32

0.25

MEM

256M

2G

4G

64G

64G

512M

BW

1M

2G

2G

2G

2G

250M

12. It is recommended to verify the health of the singleton's boot volume by executing the following command from the web shell: vol fscheck name_of_volume

13. Move IIS03y to a catalog (3tera recommends system_ms).

14. The IIS03y appliance is now ready for use in your CA 3Tera AppLogic applications.