Difference between revisions of "IMSMA Client Configuration Tool"
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The | + | {{TOC right}} |
| + | The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool: | ||
| − | [[Add a Local ID Generator | Local ID generators]] are used when generating a Local ID in a Data Entry Form by clicking on [[Image:Generate ID Number.png]]. The Local ID of a Data Entry Template is | + | [[File:ClientConfig.png]] |
| + | |||
| + | ==Parameters==__NOEDITSECTION__ | ||
| + | ===SystemName===__NOEDITSECTION__ | ||
| + | The parameter ''SystemName'' is used for building up local IDs and can reduce the risk of duplicate IDs when Data Entry is decentralised. | ||
| + | |||
| + | [[Add a Local ID Generator | Local ID generators]] are used when generating a Local ID in a Data Entry Form by clicking on [[Image:Generate ID Number.png]]. The Local ID of a Data Entry Template is composed of five parts: | ||
# ''Prefix'' from the Local ID generator | # ''Prefix'' from the Local ID generator | ||
# divider (usually hyphen) i.e. - | # divider (usually hyphen) i.e. - | ||
| Line 11: | Line 18: | ||
The System Name may be set for each computer where {{IMSMANG}} is installed. For example, the MAG Head quarter's computer could have ''MAG HQ'' as a system name while a regional installation could have ''MAG R1''. | The System Name may be set for each computer where {{IMSMANG}} is installed. For example, the MAG Head quarter's computer could have ''MAG HQ'' as a system name while a regional installation could have ''MAG R1''. | ||
| + | ===Client-Server===__NOEDITSECTION__ | ||
The following parameters are used for clients in a client/server configuration: | The following parameters are used for clients in a client/server configuration: | ||
* java.naming.provider.url | * java.naming.provider.url | ||
* isClientOnly | * isClientOnly | ||
| − | + | and are explained [[Install IMSMANG Version 6#Part 5B Client/server | here]]. | |
| − | and are | + | |
| + | If ''AlwaysSyncGeodata'' is set to '''false''' then the local geodatabase on the client computer will not automatically be updated/synced with the server. The client's geodatabase will be re-synced at restart of the client or when the user clicks the refresh map button ([[Image:RefreshIcon.png]]). | ||
| + | |||
| + | If there is a problem with network performance and clients freezes due to their geodatabase is updated, then try with changing ''AlwaysSyncGeodata'' to '''false'''. | ||
| + | ===Other===__NOEDITSECTION__ | ||
The following parameters are not normally changed: | The following parameters are not normally changed: | ||
* GISSandboxPath | * GISSandboxPath | ||
| Line 23: | Line 35: | ||
* FontSize | * FontSize | ||
| − | {{ | + | {{NavBox Start and Stop}} |
[[Category:CRI]] | [[Category:CRI]] | ||
Latest revision as of 09:31, 23 January 2018
The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool:
Parameters
SystemName
The parameter SystemName is used for building up local IDs and can reduce the risk of duplicate IDs when Data Entry is decentralised.
Local ID generators are used when generating a Local ID in a Data Entry Form by clicking on 
. The Local ID of a Data Entry Template is composed of five parts:
- Prefix from the Local ID generator
- divider (usually hyphen) i.e. -
- System Name set in IMSMA Client Configuration Tool (optional)
- divider (usually hyphen) i.e. -
- Next Number from the Local ID generator
which for an Activity may look like CR-MAG HQ-1 or for a Victim Vic-MACC3-4581.
The System Name may be set for each computer where IMSMANG is installed. For example, the MAG Head quarter's computer could have MAG HQ as a system name while a regional installation could have MAG R1.
Client-Server
The following parameters are used for clients in a client/server configuration:
- java.naming.provider.url
- isClientOnly
and are explained here.
If AlwaysSyncGeodata is set to false then the local geodatabase on the client computer will not automatically be updated/synced with the server. The client's geodatabase will be re-synced at restart of the client or when the user clicks the refresh map button (
).
If there is a problem with network performance and clients freezes due to their geodatabase is updated, then try with changing AlwaysSyncGeodata to false.
Other
The following parameters are not normally changed:
- GISSandboxPath
- IMSMACoordSysPath
- GISServerURI
- FontSize
| |||||
