Changes

Jump to: navigation, search

Sharing an IMSMA Staging Area

1,668 bytes added, 13:48, 22 June 2018
no edit summary
{{Under construction| This page is under construction}}<br />
 
It can be useful to share an IMSMA staging area between different actors as a way to share IMSMA data. For example, in a setup where each actor/operator enters its own data into IMSMA (and thus has a subset of the provincial or national data), sharing the global staging area is a way of giving each actor access to the global dataset, without compromising their own IMSMA database.
=== Backup of the staging area ===__NOEDITSECTION__
The first step of option 1 is to create a backup of the staging area database. This is different from taking a backup of IMSMA, because the staging area is not part of the IMSMA application, but a stand-alone PostgreSQL database. A backup can be created using any tool that can connect to the PostgreSQL database (e.g. Navicat). The guide below details the steps using pgAdmin3, a tool that comes for free with every PostgreSQL installation, thus also with an IMSMA installation.
{{Note|On a computer with IMSMA V6 installed, the executable for starting pgAdmin3 is ''C:\IMSMAng\pgsql\bin\pgAdmin3.exe''.}}
In order to create a backup of the staging area database, the following steps are required:
<ol>
</ol>
== Hosting the staging area on a server ==__NOEDITSECTION__
The staging area may be hosted on a server allowing clients from within or outside of the network to connect. The following steps are required to achieve this:
# If required, install the [[Staging_Area_Generator|Staging Area Generator]] on the server - this will automatically install PostgreSQL and PostGIS.
# If you have not installed the [[Staging_Area_Generator|Staging Area Generator]], install PostgreSQL and the PostGIS extension on the server.
# Access the database server with e.g. pgAdmin, Navicat, or any other SQL tool.
# Create a new PostgreSQL database.
# Restore the staging area backup as described [[Sharing_an_IMSMA_Staging_Area#Restore of the staging area|above]].
# OR, instead of the previous two steps, if the [[Staging_Area_Generator|Staging Area Generator]] is installed and the IMSMA installation is accessible, then the staging area can directly be generated from a remote IMSMA. In this case, in the window in which the parameters for the [[Staging_Area_Generator|Staging Area Generator]] are entered, specific the machine name or IP address on which the source database (IMSMA) is running.
# Ensure that port 5432 (default PostgreSQL port) is open on the server, for the machines having to access it.
# Ensure that PostgreSQL is configured to allow remote connections. This configuration is done via the attribute '''listen_addresses''' in the file named '''postgresql.conf''' that can be found in the '''data''' directory of the PostgreSQL installation (e.g., if IMSMA is installed, then that file can be found in C:\IMSMAng\pgsql\data). If any changes are made to the configuration, the pgSQL service needs to be restarted (Control Panel &rarr; Administrative Tools &rarr; Services).
 
The staging area can then be accessed from the specified machines/IP addresses/networks via a JDBC connection.
== Hosting IMSMA on a server and allow remote staging area generators to connect==__NOEDITSECTION__
{{NavBox Business Intelligence}}
[[Category:VIE]]
1,068
edits

Navigation menu