Table of Contents | ||
---|---|---|
|
Server configuration (settings.config
)
For instruction on how to configure the server (Synchronization API), please refer to: Server configuration (settings.config)
Client configuration (anytime.setup.config
)
For instructions on how to configure inside anytime.setup.config
, please refer to: Client configuration (anytime.setup.config)
Publish
When setting up Offline publication, the publication will create a database based on the settings in server.config. The publisher will create a database with the same version as the instance in the settings file.
...
Info | |||||
---|---|---|---|---|---|
Note! Note that browser built in PDF viewer is not functioning very well in Offline client. To avoid these problems, make sure to use pdf.js as PDF viewer and disable browser built in reader. This is done by setting the following properties:
|
Synchronization
...
Note!
...
settings
...
Code Block | ||
---|---|---|
| ||
<OfflineViewSynchronizationEnabled>true</OfflineViewSynchronizationEnabled>
<OfflineSynchronizationSettings>
<CertificateSettings>
<ChainOfTrust/>
</CertificateSettings>
<JsonWebTokenSettings>
<Audience>Offline</Audience>
<DurationInMinutes>10</DurationInMinutes>
<Issuer>Offline</Issuer>
<Secret>123456789OfflineOfflineOfflineOfflineOffline</Secret>
</JsonWebTokenSettings>
</OfflineSynchronizationSettings> |
Synchronization settings with credentials
If it is needed for end clients to enter username and password to start synchronization, this will have to be configured for the function to work properly. Two settings need to be applied: a resource permission and an authentication provider.
...
Code Block | ||
---|---|---|
| ||
<AuthenticationProvider> <AssertNullAuthenticationProvider> <UserName>Unknown</UserName> <Groups> <string>Synchronize</string> </Groups> </AssertNullAuthenticationProvider> </AuthenticationProvider> |
Server configuration
For instruction on how to configure the server (Synchronization API), please refer to: Server configuration (settings.config)
Client configuration (anytime.setup.config
)
For instructions on how to configure inside anytime.setup.config
, please refer to: Client configuration (anytime.setup.config)
Customization
When an offline publication is created, Manager will look in this folder to fetch the customizations to use in the offline installation package that is created by the offline publication process.
...
Currently, Assert Anytime customizations will have to be configured by Signifikant.
Profile
For versions 5.2 and earlier, Offline profile is read from the C:\ProgramData\Signifikant\Assert AnyTime\WWWRoot\App_Data
folder.
In version 5.3 and later, Offline web viewer will read profile information from site subfolders: C:\ProgramData\Signifikant\Assert AnyTime\WWWRoot\App_Data\<<site>>
. The site folder is created at Offline installation time, when folders in the Data-folder is copied from installation media to the target computer. Each subfolder creates an Offline site, and each site gets a profile from the profile master folder: C:\ProgramData\Signifikant\Assert AnyTime\Profile
. The profile is copied anew each time Offline is started, a site is seleced in Offline toolbar, or when a new site name is introduced by renaming synchronize target site name in active synchronize publication.
The Profile master folder is created in Offline deploy package, a part of AssertServer deploy package, and is kept on the editor server until the Offline application publication is run.
Code Block |
---|
Build process
Create AssertServer deploy including Customize module, Offline application and Offline Profile
Contains Offline deploy package, including the customize and profile packages
Is copied to Offline publication target area when Offline client is published
Is installed at a target; an end user computer, with or without data
Profile folder is applied before a site is target by Offline client |
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|