PostgreSQL 9.5.x or higher
PostGIS 2.2.x or higher
Edit the file setup.bat to ensure the environment variable PGHOST and PGPORT are correct.
setlocal set PGHOST=localhost set PGPORT=5436 set PATH=%PATH%;C:\Program Files\PostgreSQL\9.5\bin\ createuser.exe --superuser --createrole --echo --pwprompt -U postgres astun createdb.exe --echo -U postgres -O astun sdw psql.exe -U astun -f SDW_Build.sql sdw psql.exe -U postgres -f SDW_Audit.sql sdw REM psql -U astun sdw < SDW_Build_MapInfo.sql REM -psql -U astun sdw < SDW_Test.sql REM start psql.bat |
If MapInfo support is required then un-comment (i.e. remove the REM) from:
psql -U astun sdw < SDW_Build_MapInfo.sql
Make a note of the password for the astun user as it is required later. |
Run the following command replacing admin_user with username for admin user and password with actual password for admin user.
SELECT astun.sdw_new_user('admin_user','password', TRUE); |
E.g.
Run the following command
SELECT astun.sdw_new_user('iShareData','isharedata', FALSE); |
E.g.
If you did not install MapInfo support when you installed your SDW then you can run SDW_Build_Mapinfo.sql as the astun user.
Studio ETL is the recommended tool for managing the SDW. User administration tasks and data transfers are handled through Studio's workflow module so it's a common requirement to have Studio on the same server as your SDW. If Studio is installed elsewhere on the network then this section can be skipped. See /wiki/spaces/ISHAREHELPSTAGING/pages/53215260nstalling iShare Studio ETL for details.
If Studio is being installed just for SDW then consider reducing Studio's modules to just Data Share Connections and Workflow. |
It is highly recommended that you install the Astun Core PostgreSQL functions (astun_core).
To install these core functions:
create extension astun_core; |
You can now have a look at the iShare SDW (Spatial Data Warehouse) user documentation on how to configure your SDW. First steps would be to create some admin login roles and then look to creating schemas & migrating data. All tasks are carried out using either Studio or pgAdmin III.