2.8 Configuring Operational Contents to allow or disallow offline execution
Offline execution can be allowed or disallowed for each Operational Content through the Execution settings tab in the Operational Content Settings window of the Operational Content Editing Window.
Content Creators (when JP1/Base is used for user authentication) or Content Editors use the Operational Content Editing Window to create an Operational Content for offline execution and configure the Operational Content to allow offline execution. To execute the Operational Content, a user uses the Operational Content Execution Window in an online environment to open the Operational Content. This starts a process for the web browser (on the client-side) to download data required for executing the Operational Content and to preload images# referenced in the operational flow. After the process, the user can execute the Operational Content in an offline environment without communicating with the server.
- #
-
The following image data is preloaded:
-
Images whose URLs are specified with image parts in the operational flow area or the guide area
-
Images whose URLs are specified with process nodes in the operational flow area
Depending on how to cacheimage data, some web browsers cannot display images listed above in offline execution.
-
While the environment is offline, Offline Plugins, such as Data Store Plugins and JavaScript Plugins containing client-side JavaScript, are used to process and store input data.
After the environment comes back online, Online Plugins, such as JavaScript Plugins containing server-side JavaScript and User Plugins, are used to record input data from Offline Plugins.
The following table describes how Operational Contents behave differently depending on whether they are configured to allow or disallow offline execution.
|
Item |
Configuration to allow or disallow offline execution |
|
|---|---|---|
|
Offline execution is disallowed |
Offline execution is allowed |
|
|
Communication with servers |
|
- Online environment
- Offline environment No communication occurs. |
|
Operation log |
Logging is enabled. |
Logging is disabled. |
|
Audit log |
Logging is enabled when audit logging is configured to be used. |
Logging is disabled. |
|
Plugin |
All plugins#1 can be used. |
- Online environment All plugins#1 can be used. - Offline environment Only Offline Plugins (Data Store Plugins and JavaScript Plugins containing client-side JavaScript) can be used. |
|
HTTP session |
A request is issued periodically to keep the HTTP session. |
- Online environment A request is issued periodically to keep the HTTP session. - Offline environment The HTTP session stays alive until the session timeout#2 is reached. When the timeout is reached, the session expires. To keep HTTP sessions alive for a long time, you need to edit the user setup property file to increase the session timeout value (30 minutes by default)#2. |
- #1
-
If an Online Plugin is placed in an Operational Content, the plugin runs when the Operational Content is executed, regardless of whether offline execution is allowed.
- #2
-
You can specify how long to keep HTTP sessions alive through the ucnp.setup.server.cosminexus.ejbserver.session.timeout property (the default session timeout interval) in the user setup property file (ucnp_setup_user.properties).
This is useful for cases where an Operational Content runs offline for a certain period of time and then comes back online. You can adjust this property appropriately to prevent the HTTP session from expiring during the offline execution.
For details about the ucnp.setup.server.cosminexus.ejbserver.session.timeout property in the user setup property file (ucnp_setup_user.properties), see the manual JP1/Navigation Platform Setup and Operations Guide.