Understanding Configuration Options - Revision history

Alnaucler at 14:37, 7 June 2021

2021-06-07T14:37:05Z

← Older revision		Revision as of 16:37, 7 June 2021
Line 88:		Line 88:

	If you would like to reserve more memory for the IMSMA client '''process''', edit row 12 in ''C:\IMSMAng\trayLauncher\TrayLauncher.properties''. Start with increasing it to 1024 and then evaluate.		If you would like to reserve more memory for the IMSMA client '''process''', edit row 12 in ''C:\IMSMAng\trayLauncher\TrayLauncher.properties''. Start with increasing it to 1024 and then evaluate.

			{\|
			\|- valign="top"
			\|

			{\| class="wikitable"
			! Value !! Meaning
			\|- align="right"
			\| 512 \|\| 0.5 GB
			\|- align="right"
			\| 1024 \|\| 1 GB
			\|- align="right"
			\| 2048 \|\| 2 GB
			\|- align="right"
			\| 3072 \|\| 3 GB
			\|- align="right"
			\| 4096 \|\| 4 GB
			\|- align="right"
			\|}
			The values should be increased step-by-step and evaluated after each change.

	{{Note \|		{{Note \|

Alnaucler at 07:05, 18 March 2019

2019-03-18T07:05:15Z

← Older revision		Revision as of 09:05, 18 March 2019
Line 94:		Line 94:

	{{NavBox Information Management}}		{{NavBox Information Management}}
	[[Category:~~COO~~]]		[[Category:NAA]]

Alnaucler at 10:11, 15 March 2015

2015-03-15T10:11:18Z

← Older revision		Revision as of 12:11, 15 March 2015
Line 42:		Line 42:
	* The client(s) must be configured to connect to the server.		* The client(s) must be configured to connect to the server.
	* Maps only need to be installed on the server.		* Maps only need to be installed on the server.
	* Data entered into the server or clients will be automatically rendered to all clients (as well as the server). However, ~~GIS~~ information (points, polygons) will NOT be immediately rendered to all clients. To either post your ~~GIS-related~~ updates to the server (thus making them available to other clients) or to receive updates from the server, you must log out of IMSMA and then log back in.		* Data entered into the server or clients will be automatically rendered to all clients (as well as the server). However, geospatial information (points, polygons) will NOT be immediately rendered to all clients. To either post your geospatial updates to the server (thus making them available to other clients) or to receive updates from the server, you must log out of IMSMA and then log back in.
	* Fonts will need to be installed on both the server and client(s)		* Fonts will need to be installed on both the server and client(s)
	}}		}}
Line 75:		Line 75:
	===Client===__NOEDITSECTION__		===Client===__NOEDITSECTION__

	The IMSMA<sup>NG</sup> client is the interface through which users can connect to the server and browse the system, enter data and generate outputs. The client includes an integrated GIS and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS also allows each client to load and manage its own maps and geographic data which the client receives from the IMSMA<sup>NG</sup> server. As a result, each client receives and locally stores a complete copy of geographic data from the IMSMA<sup>NG</sup> server when it is connected to the server. This synchronized data is stored in a client ―sandbox‖ separate from the server and can always be updated by connecting to the server.		The IMSMA<sup>NG</sup> client is the interface through which users can connect to the server and browse the system, enter data and generate outputs. The client includes an integrated GIS component and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS component performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS component also allows each client to load and manage its own maps and geographic data which the client receives from the IMSMA<sup>NG</sup> server. As a result, each client receives and locally stores a complete copy of geographic data from the IMSMA<sup>NG</sup> server when it is connected to the server. This synchronized data is stored in a client ―sandbox‖ separate from the server and can always be updated by connecting to the server.

	JasperSoft’s iReport tool is built into each IMSMA<sup>NG</sup> client and allows users to access data from the database via the business layer. With iReport, users can generate reports containing tabular data, subreports and cross tabs as well as various types of charts and graphs. These reports can easily be localized into any language that IMSMA<sup>NG</sup> supports. Additional reporting options include direct connections to the IMSMA<sup>NG</sup> database via ODBC. This functionality supports tools such as Crystal Reports, Microsoft® Access®, Microsoft Excel® and various open-source reporting tools.		JasperSoft’s iReport tool is built into each IMSMA<sup>NG</sup> client and allows users to access data from the database via the business layer. With iReport, users can generate reports containing tabular data, subreports and cross tabs as well as various types of charts and graphs. These reports can easily be localized into any language that IMSMA<sup>NG</sup> supports. Additional reporting options include direct connections to the IMSMA<sup>NG</sup> database via ODBC. This functionality supports tools such as Crystal Reports, Microsoft® Access®, Microsoft Excel® and various open-source reporting tools.

Dionysia at 07:30, 13 November 2014

2014-11-13T07:30:09Z

← Older revision		Revision as of 09:30, 13 November 2014
Line 92:		Line 92:
	* Since IMSMA NG is a 32-bit application there is no effect by reserving more than total 4 GB.		* Since IMSMA NG is a 32-bit application there is no effect by reserving more than total 4 GB.
	* On the physical server in a client/server configuration there is need to start the client, take backup and restore so do not set the client process memory to less than 512. }}		* On the physical server in a client/server configuration there is need to start the client, take backup and restore so do not set the client process memory to less than 512. }}

	{{NavBox Information Management}}		{{NavBox Information Management}}

	~~[[Category:Information management]]~~

	[[Category:COO]]		[[Category:COO]]

Alnaucler at 16:51, 18 October 2014

2014-10-18T16:51:54Z

← Older revision		Revision as of 18:51, 18 October 2014
Line 67:		Line 67:
	===Server===__NOEDITSECTION__		===Server===__NOEDITSECTION__

	The IMSMA<sup>NG</sup> server stores data and manages much of the data processing. The server has two main parts, the datastore and the business layer. The datastore is where data is stored for retrieval by the IMSMA<sup>NG</sup> client. IMSMA<sup>NG</sup> uses a ~~PostGreSQL~~ relational database to store data on the server. Additionally, IMSMA<sup>NG</sup> stores other data including attachments and some configuration files on the server in file format. The ~~PostGreSQL~~ database is accessible via a variety of database access tools designed for browsing relational databases.		The IMSMA<sup>NG</sup> server stores data and manages much of the data processing. The server has two main parts, the datastore and the business layer. The datastore is where data is stored for retrieval by the IMSMA<sup>NG</sup> client. IMSMA<sup>NG</sup> uses a PostgreSQL relational database to store data on the server. Additionally, IMSMA<sup>NG</sup> stores other data including attachments and some configuration files on the server in file format. The PostgreSQL database is accessible via a variety of database access tools designed for browsing relational databases.

	{{warning\|While the database contains many relational database constraints designed to preserve data integrity, all updates of data should be handled through the business layer rather than with direct SQL updates in order to maintain integrity. Failure to do so will likely cause data corruption or loss}}		{{warning\|While the database contains many relational database constraints designed to preserve data integrity, all updates of data should be handled through the business layer rather than with direct SQL updates in order to maintain integrity. Failure to do so will likely cause data corruption or loss}}

Alnaucler at 16:19, 3 June 2014

2014-06-03T16:19:14Z

← Older revision		Revision as of 18:19, 3 June 2014
Line 37:		Line 37:
	</div>		</div>

	{{~~important~~\| Be aware of the following when running IMSMA in a client/server installation:		{{Note\| Be aware of the following when running IMSMA in a client/server installation:
	* The server and client(s) must be running the exact same version of IMSMA.		* The server and client(s) must be running the exact same version of IMSMA.
	* The gisServer.properties file on the server must be configured.		* The gisServer.properties file on the server must be configured.

Alnaucler at 12:50, 26 May 2014

2014-05-26T12:50:54Z

← Older revision		Revision as of 14:50, 26 May 2014
Line 55:		Line 55:
	The figure below shows the parts of the software; the following sections then explain the functions that each part performs.		The figure below shows the parts of the software; the following sections then explain the functions that each part performs.

	{\|		{\| border="1" cellpadding="5"
	\|- valign="top"		\|- valign="top"
	\|		\|

Alnaucler at 12:42, 26 May 2014

2014-05-26T12:42:48Z

← Older revision		Revision as of 14:42, 26 May 2014
Line 55:		Line 55:
	The figure below shows the parts of the software; the following sections then explain the functions that each part performs.		The figure below shows the parts of the software; the following sections then explain the functions that each part performs.

			{\|
			\|- valign="top"
			\|
			[[Image:stand_alone Architecture.png\|center\|300px\|''Stand-alone architecture'']]

	[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|~~500px~~\|''Client/server architecture'']]		\|
	~~<div align="center">~~		[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|600px\|''Client/server architecture'']]
	~~''Client/server architecture''~~
	~~</div>~~

			\|}

	===Server===__NOEDITSECTION__		===Server===__NOEDITSECTION__

Alnaucler at 12:04, 26 May 2014

2014-05-26T12:04:20Z

← Older revision		Revision as of 14:04, 26 May 2014
Line 58:		Line 58:
	[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|500px\|''Client/server architecture'']]		[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|500px\|''Client/server architecture'']]
	<div align="center">		<div align="center">
	''Client/server ~~Architecture~~''		''Client/server architecture''
	</div>		</div>

Alnaucler at 12:01, 26 May 2014

2014-05-26T12:01:22Z

← Older revision		Revision as of 14:01, 26 May 2014
Line 34:		Line 34:
	[[Image:Understanding Configuration Options - Networked Config.png\|center\|300px\|''Client/server Config'']]		[[Image:Understanding Configuration Options - Networked Config.png\|center\|300px\|''Client/server Config'']]
	<div align="center">		<div align="center">
	''Client/server ~~Configuration~~''		''Client/server configuration''
	</div>		</div>

Line 56:		Line 56:


	[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|500px\|''Client/server ~~Architecture~~'']]		[[Image:Understanding Configuration Options- Client Server Architecture.png\|center\|500px\|''Client/server architecture'']]
	<div align="center">		<div align="center">
	''Client/server Architecture''		''Client/server Architecture''