Consider the following scenario:
For example, you create a website named MySite on a IIS 7.5 server. MySite includes two applications named App1 and App2. MySite and App1 run in an application pool named AppPool1. App2 runs in an application pool named AppPool2. In App1, you enable the auto-start feature for a service named service_App1. In App2, you enable the auto-start feature for a service named service_App2. When AppPool1 is started, service_App1 and service_App2 are loaded in the application pool AppPool1. However, only service_App1 should be loaded.
- You install Windows Server AppFabric on a server that is running Internet Information Services (IIS) 7.5.
- You create a website. Then, you add multiple applications to the website.
- You configure these applications to run under different application pools.
- You enable the auto-start feature for different services in these applications.
- You start the application pool that is used by the website.
For example, you create a website named MySite on a IIS 7.5 server. MySite includes two applications named App1 and App2. MySite and App1 run in an application pool named AppPool1. App2 runs in an application pool named AppPool2. In App1, you enable the auto-start feature for a service named service_App1. In App2, you enable the auto-start feature for a service named service_App2. When AppPool1 is started, service_App1 and service_App2 are loaded in the application pool AppPool1. However, only service_App1 should be loaded.