Difference between revisions of "InstallPortal"
From CaseTalk Wiki
m (→Portal) |
m (→Portal) |
||
Line 15: | Line 15: | ||
---- | ---- | ||
To install these in IIS, follow the steps below: | |||
# Create a '''Application Pool''' called ''CaseTalkPortal'' which has ''No Managed Code'' and ''Classic pipeline mode''. | # Create a '''Application Pool''' called ''CaseTalkPortal'' which has ''No Managed Code'' and ''Classic pipeline mode''. |
Revision as of 08:46, 2 April 2021
Portal
The entire portal software is controlled with a ISAPI dll, static files and a database configuration.
Once the portal software is extracted from the zip file. The folder structure should resembled the above.
portal\ dist\ msodbcdiag17.dll msodbcsql17.dll msodbcsqlr17.dll Portal_Isapi.dll Portal_Isapi.ini web.config
To install these in IIS, follow the steps below:
- Create a Application Pool called CaseTalkPortal which has No Managed Code and Classic pipeline mode.
- Make sure the CaseTalkPortal pool has the advanced settings set to Enable 32 bit applications.
- Under the Default Website add an Application which is hooked to the CaseTalkPortal Application, and points to the physical folder portal\.
- For cache optimizations, the Output Caching can be tweaked to result in the following web.config:
<?xml version="1.0" encoding="UTF-8"?> <configuration> <location path="dist"> <system.webServer> <staticContent> <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="00:00:15" /> </staticContent> </system.webServer> </location> <system.webServer> <caching> <profiles> <add extension=".dll" policy="CacheForTimePeriod" kernelCachePolicy="CacheForTimePeriod" duration="00:00:30" varyByQueryString="content,v,name" /> </profiles> </caching> </system.webServer> </configuration>