So what is Appcmd.exe?
This is “one” command line tool to administer IIS7. In IIS6 several of admin task were done using several scattered VBS script files. This made it difficult to find out what script needs to be run for eg. to get list of worker processes.
So IIS7 is powered with Appcmd.exe which provides all the options you need to administer IIS7.
Following are the options/categories available from a high level
|SITE||Administration of virtual sites|
|APP||Administration of applications|
|VDIR||Administration of virtual directories|
|APPPOOL||Administration of application pools|
|CONFIG||Administration of general configuration sections|
|WP||Administration of worker processes|
|REQUEST||Administration of HTTP requests|
|MODULE||Administration of server modules|
|BACKUP||Administration of server configuration backups|
|TRACE||Working with failed request trace logs|
Lets see how we can use it with an example
When I installed LH Server Beta (I rebuild my box quite frequently) I wanted to see how it’s like to have 1000 websites running on IIS7.
So I created 1000 websites on my box.
Good scenario to use Appcmd.exe and also my MS-DOS experience. No I’m not gone nutts to create it using the UI 🙂
- Wanted separate folders for each website
- Wanted to use same IP address and port for all websites
- Type a command and leave the box to create all the websites
Keep in mind I’m not talking about Server but my desktop machine. Yea its got 2GB RAM though.
- Created a folder – E:\Websites
- I wrote a batch file (createsite.cmd) with the following
appcmd add site /name:”Site%1″ /id:%1 /bindings:http/:*:80:site%1 /physicalPath:”E:\Websites\Site%1″
appcmd start site “Site%1”
- Now the command to trigger the batch file where my MS-DOS experience came handy
C:\FOR /L %i IN (2,1,5) DO createsite.cmd %i
FOR command is a batch file loop which simply works like ‘for’ loop in your favorite language
FOR /L %i IN (2,1,1000) DO createsite.cmd %i
is equivalent to the following in C
for ( i=2; i <= 1000; i++ )
createsite( i );
I started value of ‘i’ from 2 because “Default Website” has Site ID 1.
Hit enter and wait till the folders and websites are created for each iteration.
Bingo !!! 1000 websites ready to be administered or tested.
So the result would be
E:\Websites folder would have folders called Site2, Site3 etc… and in IIS there would be sites with name Site2, Site3 etc…
Lets revisit the appcmd command above once again
appcmd add site
/name:”Site%1″ // website name
/id:%1 // Site ID
/bindings:http/:*:80:site%1 // site would have “All Unassigned” including host header with the site name
/physicalPath:”E:\Websites\Site%1″ // Pointing to the physical folder for that site
appcmd start site “Site%1” // pretty straight forward, it starts the website
What else can I do to extend this scenario?
- Create Application Pools separately for each website
- Create a simple ASP page and drop it in every folder created
- Use TinyGET utility (available with IIS6 Resource Kit) to simulate request
Some other useful command options
C:\>appcmd add backup “backup before screwup”
BACKUP object “backup before screwup” added
C:\>appcmd list backup
BACKUP “backup before screwup”
Restore from Backup
C:\>appcmd restore backup “backup before screwup”
Restored configuration from backup “backup before screwup”
Currently Executing Requests
C:\>appcmd list request
REQUEST “fa00000080000487” (url:GET /highcpu.asp, time:1903 msec, client:localhost)
Will add more of this later…