|
|
Installing EPWeb as ISAPI in IIS 7.0 |
|
|
|
|
|
||
|
Installing EPWeb as ISAPI in IIS 7.0 |
|
|
|
|
|
|
Installing EPWeb as ISAPI in IIS 7.0
|
|
|
Installing EPWeb as ISAPI in IIS 7.0 |
|
|
|
|
|
||
|
Installing EPWeb as ISAPI in IIS 7.0 |
|
|
|
|
|
|
|
|
||
| 1. | Installing an ISAPI DLL in IIS 7.0 is again a bit different than in previous versions of IIS. Start up your IIS Manager and select the server you will be working on. If you do not see the Application Pools option below the server, click the small arrow to the left. |
| 2. | To add the Application Pool, click on Application Pools in the left column. In the right column, click Add Application Pool. |
| a. | Enter a Name for the application pool. |
| b. | From the .NET Framework version drop-down, select No Managed Code. |
| c. | From the Managed pipeline mode drop-down, select Classic. |
| d. | Click OK to save your new application pool. The application pool will appear in the Application Pools area of the IIS Manager. |
| 3. | Select your new pool and click Recycling to the right. |
| a. | You need to adjust the recycling conditions. You do not want the ISAPI DLL to be recycled while someone is using it, as it may interrupt them while entering an event or request. If you would like to recycle the process, make sure it is done at a time when no one will be working in EPWeb. |
| b. | If you want the process recycled, under Fixed Intervals, select Specific Time(s), and enter the time(s) at which the process will be recycled. Remember to choose times at which no one will be using EPWeb. |
| c. | Click Next. In the next page, choose the recycling events to log, and click Finish. |
| 4. | Back in the IIS Manager, select your new application pool and click Advanced Settings to the right. |
| a. | Under Process Model, ensure that the Maximum Worker Processes is 1 (one). |
| b. | Also under Process Model, set the Identity to Custom Account. |
| c. | Click the Set button. In the Set Credentials window, enter your User Name (server name) and Password. Click OK. |
| d. | If you are installing EPWeb on a 64-bit computer, go to the (General) area at the top of the Advanced Settings window. Set Enable 32-Bit Applications to True. |
| e. | Click OK in the Advanced Settings window to save your settings and return to the IIS Manager. |
| 5. | NOTE: In the future, when applying updates to the ISAPI DLL, you will need to first stop this application pool. To stop the application pool, right-click on the new application pool and select Stop. |
| 6. | Next, under Connections in the left column, click the arrow next to Sites to open the websites below. There may only be the one Default Web Site, or you may have other websites. |
| a. | Right-click on the Site you want to use and select Add Application. The Add Application window appears. |
| b. | Enter an Alias for the application, typically something like EPWeb, as this will be part of the website address, e.g. http://<servername>/<alias>/EPWeb.dll. Click the Select button to open the Select Application Pool window. Find the Application Pool you just created and click OK. |
| c. | Back in the Add Application window, click the ellipsis next to the Physical Path field. In the Browse for Folder window, select the directory, i.e. the Bin subfolder of the directory to which you just installed EPWeb. (By default, EPWeb would be installed to c:\Program Files\EPWeb, so the directory to select would be c:\Program Files\EPWeb\Bin. On a 64-bit computer, this will probably be c:\Program Files (x86)\EPWeb\Bin). Click OK. |
| d. | Back in the Add Application window, click the Connect As button. Select Application User (pass-through authentication) and click OK. |
| 7. | Back in the IIS Manager, under the left Connections column, click on the server. In the middle column, double-click on ISAPI and CGI Restrictions. |
| a. | In ISAPI and CGI Restrictions, you want to add a new item. Click the Add button under Actions in the right column. |
| b. | The Add ISAPI or CGI Restriction window appears. The Path should point to the EPWeb.dll that you installed. Enter a Description, such as EPWeb. Check the Allow Extension Path to Execute checkbox. |
| c. | Click OK. |
| 8. | Again, return to the left-hand Connections column in the IIS Manager. Under Sites, find the new application you created back in Step 6. |
| a. | Double-click on Handler Mappings in the center column. |
| b. | Select the ISAPI-dll item under Handler Mappings and click Edit to the right. |
| c. | The Request path should be set to *.dll. Set the Executable to the EPWeb.dll that you installed. |
| d. | Click OK. |
| e. | Back under Handler Mappings, with the ISAPI-dll item still selected, click Edit Feature Permissions to the right. |
| f. | In the Edit Feature Permissions window, ensure that the Read, Script and Execute checkboxes are all checked. |
| g. | Click OK. |
| 9. | You can now exit the IIS Manager. |
| 10. | You now need to set the ComInitialization item under the Server Controller section in the EPWeb.ini file to 0 (none). See Server Configuration: [ServerController]. |
| 11. | You will also need to give the user referenced in Step 4.c full permissions on the database and read permissions to the EPWeb folder. |
| 12. | You may need to restart the website or the IIS Admin service to make sure the changes take effect. |