How to Isolate Web Interface or Program Neighborhood Agent Sites into Their Own Application Pool for Best Performance

When Web Interfaces sites or Program Neighborhood Agent sites are part of a large deployment and are the primary method of accessing applications for an organization, you might consider isolating each Web Interface site or Program Neighborhood Agent site into their own IIS Application Pool.

Background

Each separate Application Pool provides a process boundary so that when a Web Interface site or Program Neighborhood Agent site is assigned to one application pool, problems in other application pools do not affect the application. This ensures that if a Web Interface site or Program Neighborhood Agent site fails, it does not affect the other Web Interface or Program Neighborhood Agent sites running in other application pools.

The process to create an Application Pool for Web Interface or Program Neighborhood Agent site is as follows:

Note: Before performing these changes, ensure that no users are accessing the Web Interface or Program Neighborhood Agent sites because their access will get interrupted. Continue reading “How to Isolate Web Interface or Program Neighborhood Agent Sites into Their Own Application Pool for Best Performance”