View Cache - Revision history

JKN: /* GetViewStateDetails */

2024-03-14T14:55:06Z

‎GetViewStateDetails

2020-10-19T12:43:29Z

2018-03-23T07:21:08Z

2018-03-23T07:20:45Z

2018-03-23T07:19:13Z

2017-08-17T13:33:33Z

2017-08-17T13:32:42Z

2017-08-17T13:32:11Z

2017-08-17T10:19:28Z

2015-10-21T12:50:13Z

‎Enabling

@@ Line 108: / Line 108: @@
 To call this in a web browser, one can access
 <syntaxhighlight lang="html4strict">
-https://ContentServerAddress/ContentServicePath/GetViewStateInformation/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
+https://ContentServerAddress/ContentServicePath/GetViewStateDetails/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
 </syntaxhighlight>
 to fetch details. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with the actual service configs.
@@ Line 114: / Line 114: @@
 As long as the ViewCache is not initiliazed (not online yet) you will only receive details about the Data Pool and its size.
 === TestViewState===

@@ Line 58: / Line 58: @@
 https://ContentServerAddress/ContentServicePath/GetViewStateInformation/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
 </syntaxhighlight>
-to trigger a update. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with the actual service configs.
+to fetch data. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with the actual service configs.
 Once the view cache is ready, the response should say something like "Cache State <<ONLINE>>"
@@ Line 85: / Line 85: @@
 https://ContentServerAddress/ContentServicePath/TriggerViewStateUpdate/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
 </syntaxhighlight>
-to trigger a update. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with the actual service configs.
+to trigger an update. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with the actual service configs.
 === TestViewState===

← Older revision		Revision as of 07:21, 23 March 2018
Line 1:		Line 1:
−	~~{{ReleaseStatus/Beta}}~~
	The View Cache feature increases the performance of the [[web Service]] by caching the data to be published and sent to the clients. All content data as well as the hierarchies, as defined by the [[View]] and in the [[ACM]], is evaluated and cached internally. Be aware, that this data does not encompass the physical documents linked to the objects, hence the documents have to be loaded if requested from the client.		The View Cache feature increases the performance of the [[web Service]] by caching the data to be published and sent to the clients. All content data as well as the hierarchies, as defined by the [[View]] and in the [[ACM]], is evaluated and cached internally. Be aware, that this data does not encompass the physical documents linked to the objects, hence the documents have to be loaded if requested from the client.

@@ Line 5: / Line 5: @@
 Once the cache has been initialized, its status and additional information can be retrieved by [[#Web Service Interface|web service methods]].
-{{Attention|Up to now the View Cache needs to be initialized and updated manually after every (re)start of the web service, due to a missing automatism!}}
+{{Attention|Up to now the View Cache needs to be initialized and updated manually after every (re)start of the web service. This can be done manually or by using an automatism!}}
 == Using the View Cache ==

@@ Line 8: / Line 8: @@
 == Using the View Cache ==
 === Initialization / Update of View Cache ===
 The cache needs to be initialized after a web service has been (re)started by calling the method [[#TriggerViewStateUpdate|TriggerViewStateUpdate]].

@@ Line 79: / Line 79: @@
 https://ContentServerAddress/ContentServiceName/GetViewStateInformation/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
 </syntaxhighlight>
-to trigger a update. Please replace ContentServerAddress, ContentServiceName, AppName and ContextName with actual service configs.
+to trigger a update. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with actual service configs.
 Once the view cache is ready, the response should say something like "Cache State <<ONLINE>>"
@@ Line 106: / Line 106: @@
 https://ContentServerAddress/ContentServiceName/TriggerViewStateUpdate/AppName/ContextName/333b99c9-233d-41d6-848c-81fe0b13a537
 </syntaxhighlight>
-to trigger a update. Please replace ContentServerAddress, ContentServiceName, AppName and ContextName with actual service configs.
+to trigger a update. Please replace ContentServerAddress, ContentServicePath, AppName and ContextName with actual service configs.
 === TestViewState===

@@ Line 25: / Line 25: @@
 </syntaxhighlight>
-[[Category:Installing|View Cache]]
-[[Category:Web service|View Cache]]
 === Initialization / Update of View Cache ===
@@ Line 73: / Line 73: @@
          string GetViewStateInformation(string appName, string contextName, string authentication);
 </syntaxhighlight>
 === TriggerViewStateUpdate ===
@@ Line 91: / Line 100: @@
          bool TriggerViewStateRefresh(string appName, string contextName, string authentication);
 </syntaxhighlight>
 === TestViewState===
@@ Line 113: / Line 129: @@
 * [http://weblogs.asp.net/owscott/why-is-the-iis-default-app-pool-recycle-set-to-1740-minutes Why is the IIS default app pool recycle set to 1740 minutes?]
-[[Category:Installing]]
+[[Category:Installing|View Cache]]
-[[Category:Web service]]
+[[Category:Web service|View Cache]]

@@ Line 15: / Line 15: @@
 ! Area!! Setting!! Description
 |-
-| appSettings|| UBIK.Service.EnableViewCachage || Enable = '''1''' / Disable = '''0''' the view cache feature for this web service
+| appSettings|| UBIK.Service.EnableViewCache || Enable = '''1''' / Disable = '''0''' the view cache feature for this web service
 |}
@@ Line 24: / Line 24: @@
    </appSettings>
 </syntaxhighlight>
 === Initialization / Update of View Cache ===