IMSMA Client Configuration Tool - Revision history

Alnaucler at 08:31, 23 January 2018

2018-01-23T08:31:49Z

← Older revision		Revision as of 10:31, 23 January 2018
Line 26:		Line 26:
	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 ''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 ''~~AlwatsSyncGeodata~~'' to '''false'''.		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__		===Other===__NOEDITSECTION__

Alnaucler at 17:51, 26 May 2017

2017-05-26T17:51:10Z

← Older revision		Revision as of 19:51, 26 May 2017
Line 35:		Line 35:
	* FontSize		* FontSize

	{{~~HowTo~~ Start and Stop}}		{{NavBox Start and Stop}}

	[[Category:CRI]]		[[Category:CRI]]

Alnaucler at 13:50, 2 February 2016

2016-02-02T13:50:25Z

← Older revision		Revision as of 15:50, 2 February 2016
Line 26:		Line 26:
	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 ''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 ''AlwatsSyncGeodata'' to '''~~true~~'''.		If there is a problem with network performance and clients freezes due to their geodatabase is updated, then try with changing ''AlwatsSyncGeodata'' to '''false'''.

	===Other===__NOEDITSECTION__		===Other===__NOEDITSECTION__

Alnaucler at 20:56, 5 April 2015

2015-04-05T20:56:27Z

← Older revision		Revision as of 22:56, 5 April 2015
Line 24:		Line 24:
	and are explained [[Install IMSMANG Version 6#Part 5B Client/server \| here]].		and are explained [[Install IMSMANG Version 6#Part 5B Client/server \| 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 ([[Image:RefreshIcon.png]]).		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 ''AlwatsSyncGeodata'' to '''true'''.		If there is a problem with network performance and clients freezes due to their geodatabase is updated, then try with changing ''AlwatsSyncGeodata'' to '''true'''.

Alnaucler at 20:55, 5 April 2015

2015-04-05T20:55:18Z

← Older revision		Revision as of 22:55, 5 April 2015
Line 22:		Line 22:
	* java.naming.provider.url		* java.naming.provider.url
	* isClientOnly		* isClientOnly
	* AlwaysSyncGeodata
	and are explained [[Install IMSMANG Version 6#Part 5B Client/server \| here]].		and are explained [[Install IMSMANG Version 6#Part 5B Client/server \| 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 ([[Image:RefreshIcon.png]]).

			If there is a problem with network performance and clients freezes due to their geodatabase is updated, then try with changing ''AlwatsSyncGeodata'' to '''true'''.

	===Other===__NOEDITSECTION__		===Other===__NOEDITSECTION__

Dionysia at 10:13, 22 March 2015

2015-03-22T10:13:26Z

← Older revision		Revision as of 12:13, 22 March 2015
Line 2:		Line 2:
	The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool:		The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool:

	[[File:~~ClientConfigurationTool~~.png]]		[[File:ClientConfig.png]]

	==Parameters==__NOEDITSECTION__		==Parameters==__NOEDITSECTION__

Dionysia at 10:11, 22 March 2015

2015-03-22T10:11:25Z

← Older revision		Revision as of 12:11, 22 March 2015
Line 23:		Line 23:
	* isClientOnly		* isClientOnly
	* AlwaysSyncGeodata		* AlwaysSyncGeodata
	and are ~~explain~~ [[Install IMSMANG Version 6#Part 5B Client/server \| here]].		and are explained [[Install IMSMANG Version 6#Part 5B Client/server \| here]].

	===Other===__NOEDITSECTION__		===Other===__NOEDITSECTION__

Dionysia at 10:10, 22 March 2015

2015-03-22T10:10:32Z

← Older revision		Revision as of 12:10, 22 March 2015
Line 8:		Line 8:
	The parameter ''SystemName'' is used for building up local IDs and can reduce the risk of duplicate IDs when Data Entry is decentralised.		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 ~~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 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. -

Dionysia at 10:10, 22 March 2015

2015-03-22T10:10:05Z

← Older revision		Revision as of 12:10, 22 March 2015
Line 6:		Line 6:
	==Parameters==__NOEDITSECTION__		==Parameters==__NOEDITSECTION__
	===SystemName===__NOEDITSECTION__		===SystemName===__NOEDITSECTION__
	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 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 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:

Dionysia at 10:08, 22 March 2015

2015-03-22T10:08:33Z

← Older revision		Revision as of 12:08, 22 March 2015
Line 1:		Line 1:
			{{TOC right}}
	The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool:		The Client Configuration tool can be displayed if you right-click on the control centre icon and select IMSMA Client Configuration Tool:

	[[File:ClientConfigurationTool.png]]		[[File:ClientConfigurationTool.png]]

			==Parameters==__NOEDITSECTION__
			===SystemName===__NOEDITSECTION__
	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.

Line 15:		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
Line 21:		Line 25:
	and are explain [[Install IMSMANG Version 6#Part 5B Client/server \| here]].		and are explain [[Install IMSMANG Version 6#Part 5B Client/server \| here]].

			===Other===__NOEDITSECTION__
	The following parameters are not normally changed:		The following parameters are not normally changed:
	* GISSandboxPath		* GISSandboxPath