Table of Contents Previous Next



To simplify PostGIS installation, add a list of the required RPM packages to the Optional Node Packages field of the Edit Engine Details dialog. To provision replicas that contain the PostGIS functions, perform the installation and create the extensions on the master node of the cluster before adding replica nodes to your cluster.
To modify an engine description, use Administrative credentials to connect to the Ark console, and navigate to the Admin tab. Select an engine ID from the list of engines in the DB Engine Administration list, and click Edit Engine Details.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\c0764c9a\Screen Shot 2017-05-08 at 2.14.24 PM.png
When the Edit Engine Details dialog opens (see Figure 4.28), use the fields on the dialog to specify the repository information and the names of optional RPM packages that the installer should provision on each node of the cluster.
The PostGIS RPM packages are distributed from the enterprisedb tools repository; by default, the enterprisedb tools repository is included in the Yum Repo URL field.
Add the names of the PostGIS RPM packages to the Optional Node Packages field on the Edit Engine Details dialog.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\1e0165a6\Screen Shot 2017-05-08 at 2.16.20 PM.png
For detailed information about creating a new server cluster, please see the EDB Ark Getting Started Guide, available through the EDB Ark Dashboard tab.
After adding the packages to the master node of a cluster, you can use the psql client or the EDB Postgres Enterprise Manager (PEM) client to create the extensions. Before connecting with a client, an Administrator must open the listener port (by default, 5444 on an Advanced Server instance) of the node for connections.


Table of Contents Previous Next