As a best practice, administrators must take into account the identity of the user running the IIS worker thread. The machine account places restrictions on the asp.net worker process that make it incompatible with certain web server applications that must access non-local disk groups. For this reason, the asp.net worker process must run as a secondary identity to ensure access to these disk groups. Windows Server applications pools offer an excellent solution for running asp.net applications as secondary identities.
To create an application pool:
- Open Internet Information Services (IIS) Manager.
- Expand the tree so that the Application Pools node is displayed.
- Right-click Application Pools and select Add Application Pool.
- Enter ArchiveLink in the Name field in the Add Application Pool dialog box.
To configure the content server virtual directory:
- Right-click the application pools icon and select Advanced Settings.
- In Recycling, remove any undesired asp.net worker process recycling.
- In Process Model, select Identity and click ….
- The Application Identity Pool dialog box is displayed, select Custom account.
- Click Set.
Enter an appropriate username and password for the application identity. This user should have administrative rights to the local machine and be a member of the Local Admin group. This user should also have read rights to access the OnBase database and the OnBase disk groups for all documents to be used with the Connector for use with SAP ArchiveLink.
If the defaultAppPool setting in the applicationHost.config file has been set to true, this user must also be a member of the IIS_USRS group.
Click OK when finished.
The new application pool can now be applied to the content server virtual directory created with the previous steps. To apply the application pool to the content server virtual directory:
- Right-click on the virtual directory you have created.
- Select Basic Settings.
- Click Select.
- Select the new application pool from the Application pool drop-down list.
- Click OK.