Difference between revisions of "InstallPortal"

From CaseTalk Wiki
Jump to: navigation, search
Line 23: Line 23:
# Make sure the ''CaseTalkPortal'' pool has the advanced settings set to ''Enable 32 bit applications''.
# 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\'''.
# Under the ''Default Website'' add an Application which is hooked to the ''CaseTalkPortal'' Application, and points to the physical folder '''portal\'''.
# If ''CaseTalk Manager'' is run succesful, copy the ''CaseTalkManager.ini'' to ''Portyal_Isapi.ini'' for database connection definitions.
# For cache optimizations, the ''Output Caching'' can be tweaked to result in the following '''web.config''':
# For cache optimizations, the ''Output Caching'' can be tweaked to result in the following '''web.config''':



Revision as of 09:51, 2 April 2021

CaseTalk Portal

The entire portal software is controlled with a ISAPI dll, static files and a database configuration. The portal may be downloaded from the website as CaseTalkPortal.zip.

Unpacking

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

Installing

To install these in IIS, follow the steps below:

  1. Create a Application Pool called CaseTalkPortal which has No Managed Code and Classic pipeline mode.
  2. Make sure the CaseTalkPortal pool has the advanced settings set to Enable 32 bit applications.
  3. Under the Default Website add an Application which is hooked to the CaseTalkPortal Application, and points to the physical folder portal\.
  4. If CaseTalk Manager is run succesful, copy the CaseTalkManager.ini to Portyal_Isapi.ini for database connection definitions.
  5. 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>

Monitoring

For monitoring the Event Viewer of Windows can be used. Relevant logs are to be found under Windows Logs\Application with the source being CaseTalkPortal.