IMSMA Client Configuration Tool: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The parameter SystemName is used for building up local IDs and will reduce the risk of duplicate IDs when Data Entry is decentralised. | The parameter ''SystemName'' is used for building up local IDs and will 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 built up five parts: | [[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 built up five parts: | ||
Revision as of 10:51, 22 March 2015
The parameter SystemName is used for building up local IDs and will 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 built up 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.
The following parameters are used for clients in a client/server configuration:
- java.naming.provider.url
- isClientOnly
- AlwaysSyncGeodata
and are explain here.
The following parameters are not normally changed:
- GISSandboxPath
- IMSMACoordSysPath
- GISServerURI
- FontSize