Difference between revisions of "View Cache Launcher"
(→{{UBIK}} View Cache Launcher (VCL)) |
|||
| Line 21: | Line 21: | ||
</startup> | </startup> | ||
<appSettings> | <appSettings> | ||
| − | <add key="StatusUri" value="https://10.86.47.16/CLIENT/UBIK | + | <add key="StatusUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_001" /> |
| − | <add key="TriggerUri" value="https://10.86.47.16/CLIENT/UBIK | + | <add key="TriggerUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/TriggerViewStateUpdate/APP_001/CXT_002" /> |
<add key="TriggerInterval" value="7200" /> | <add key="TriggerInterval" value="7200" /> | ||
<add key="OfflineCheckInterval" value="60" /> | <add key="OfflineCheckInterval" value="60" /> | ||
Revision as of 10:43, 13 November 2018
UBIK® View Cache Launcher (VCL)
The VCL is an installable windows system service which can be used to automaically trigger one or more UBIK contexts(s) provided by an UBIK IIS service to build up its view cache.
After unpacking the VCL binaries and config-files, move the files to a directory where the local system account (or the specified one configured to run the VCL service) is allowed to execute it.
The VCL is configured in “UBIK.VCL.exe.config":
- StatusURI: configure the service IP, the webservice path, appand context according to the installed UBIK-configuration on the IIS.
- TriggerUri: see StatusURI
- TriggerInterval: when the viewcache is already active, refresh it at least after this interval.
- OfflineCheckInterval: when the viewcache can not be contacted or is offline, retry to trigger the viewcache at least after this time interval.
Example
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.1" />
</startup>
<appSettings>
<add key="StatusUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_001" />
<add key="TriggerUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/TriggerViewStateUpdate/APP_001/CXT_002" />
<add key="TriggerInterval" value="7200" />
<add key="OfflineCheckInterval" value="60" />
<add key="LogPath" value="D:\UBIK\LOG\VCL\log.txt"/>
</appSettings>
</configuration>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.1" />
</startup>
<appSettings>
<add key="StatusUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_001" />
<add key="TriggerUri" value="https://10.86.47.16/CLIENT/UBIK/CONTENT/UbikContent.svc/TriggerViewStateUpdate/APP_001/CXT_002" />
<add key="TriggerInterval" value="7200" />
<add key="OfflineCheckInterval" value="60" />
<add key="LogPath" value="D:\UBIK\LOG\VCL\log.txt"/>
</appSettings>
</configuration>
Configure more than one service and/or context to be updated
Please duplicate the entries used and add a number suffix. Here is an example:
<add key="StatusUri1" value="https://10.86.47.16/UBIK/PROJECT01/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_001" />
<add key="StatusUri2" value="https://10.86.47.16/UBIK/PROJECT01/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_002" />
<add key="StatusUri2" value="https://10.86.47.16/UBIK/PROJECT01/CONTENT/UbikContent.svc/GetViewStateInformation/APP_001/CXT_002" />
etc.
