Difference between revisions of "Sharing an IMSMA Staging Area"
(Created page with "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 in...") |
|||
Line 3: | Line 3: | ||
== Overview ==__NOEDITSECTION__ | == Overview ==__NOEDITSECTION__ | ||
There are several options for sharing the staging area: | There are several options for sharing the staging area: | ||
− | + | # Create a backup, send it to the organisations that should have it, and restore the backup there | |
− | + | # Host the staging area on a server and allow access from the outside | |
− | + | # Host IMSMA on a server and allow remote [[Staging Area Generator|Staging Area Generators]] to connect to it | |
Each option is detailed step-by-step. | Each option is detailed step-by-step. | ||
Line 11: | Line 11: | ||
== Sharing via backup and restore ==__NOEDITSECTION__ | == Sharing via backup and restore ==__NOEDITSECTION__ | ||
=== Backup of the staging area ===__NOEDITSECTION__ | === 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, these steps are required: | ||
+ | # In pgAdmin3, connect to the PostgreSQL server hosting the staging area -- typically, this server will be localhost, and the port is 5432. | ||
+ | # Open the staging area database by clicking on it | ||
+ | # Right-click on the database (e.g. staging) and choose '''Backup...''' | ||
+ | # In the backup window, choose a destination folder and a filename, and the other options as shown in the screenshot below. | ||
+ | # Click on '''Backup''' and wait for the backup to finish. Depending on the size of the database, this can take some time. When finished, click '''Done'''. | ||
+ | # In the chosen destination folder, there is now a file with the chosen name and the extension .backup (e.g. staging_area_backup.backup). | ||
+ | # This file can now be sent to whoever should receive it. | ||
=== Restore of the staging area ===__NOEDITSECTION__ | === Restore of the staging area ===__NOEDITSECTION__ | ||
Line 16: | Line 26: | ||
== Hosting the staging area on a server ==__NOEDITSECTION__ | == Hosting the staging area on a server ==__NOEDITSECTION__ | ||
+ | == Hosting IMSMA on a server and allow remote staging area generators to connect==__NOEDITSECTION__ | ||
{{NavBox Business Intelligence}} | {{NavBox Business Intelligence}} | ||
[[Category:VIE]] | [[Category:VIE]] |
Revision as of 09:24, 16 July 2014
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.
Contents
Overview
There are several options for sharing the staging area:
- Create a backup, send it to the organisations that should have it, and restore the backup there
- Host the staging area on a server and allow access from the outside
- Host IMSMA on a server and allow remote Staging Area Generators to connect to it
Each option is detailed step-by-step.
Sharing via backup and restore
Backup of the staging area
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.
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, these steps are required:
- In pgAdmin3, connect to the PostgreSQL server hosting the staging area -- typically, this server will be localhost, and the port is 5432.
- Open the staging area database by clicking on it
- Right-click on the database (e.g. staging) and choose Backup...
- In the backup window, choose a destination folder and a filename, and the other options as shown in the screenshot below.
- Click on Backup and wait for the backup to finish. Depending on the size of the database, this can take some time. When finished, click Done.
- In the chosen destination folder, there is now a file with the chosen name and the extension .backup (e.g. staging_area_backup.backup).
- This file can now be sent to whoever should receive it.
Restore of the staging area
Hosting the staging area on a server
Hosting IMSMA on a server and allow remote staging area generators to connect
|