Installing PostgreSQL and ArcSDE on separate servers

If you install PostgreSQL on a computer separate from ArcSDE, you must copy the st_geometry shared library file (listed in the following table) to the PostgreSQL lib directory on the PostgreSQL server. If you want to use the ST_Raster type, you must also copy the st_raster shared library file to the PostgreSQL lib directory. See Installing the ST_Raster type in a remote PostgreSQL database for instructions.

Library name	OS-dependent file names
st_geometry	st_geometry.dll (Windows) st_geometry.so (Linux)
st_raster	libst_raster_pg.dll (Windows) libst_raster_pg.so (Linux)

Note:

You must be logged in as the root user when you copy the st_geometry.so and libst_raster_pg.so to the PostgreSQL usr/lib/pgsql (32-bit) or usr/lilb64/pgsql (64-bit) directory on Linux, because this directory is owned by the root user.

On Windows servers, copy the st_geometry.dll and libst_raster_pg.dll files to the %PostgreSQL%\lib directory.

Also on Windows servers, if you execute the sdesetup command to create the geodatabase repository rather than run the Post Installation wizard, you must copy the following libraries from the PostgreSQL lib directory to the %SDEHOME%\bin on the server where ArcSDE is installed so that the ST_Geometry type can access them:

• comerr32.dll
• gssapi32.dll
• k5sprt32.dll
• krb5_32.dll
• libeay32.dll
• libiconv2.dll
• libintl3.dll
• libpq.dll
• ssleay32.dll

For Linux, you must copy or use FTP to transfer the postgresql-libs-8.3.8-1PGDG.rhel15.i686.rpm from the PostgreSQL lib directory to the $SDEHOME directory on the ArcSDE server. You must run the rpm after it is placed on the Linux server.

Specific steps for setting up a geodatabase when the PostgreSQL database cluster is on a different server than ArcSDE vary depending on the server operating systems you are using. The steps provided in this topic are general, high-level instructions. To see more specific instructions for the operating system combination you are using, see one of the following topics:

• Installing ArcSDE and PostgreSQL on separate Windows servers
• Installing ArcSDE and PostgreSQL on separate Linux servers
• Installing PostgreSQL on a Linux server and ArcSDE on a Windows server
• Installing PostgreSQL on a Windows server and ArcSDE on a Linux server

Steps:

1. Install ArcSDE on one server. Do not proceed with postinstallation yet.
2. Install the PostgreSQL DBMS on another server.
3. Copy or use FTP to transfer the st_geometry and (optionally) st_raster library files from SDEHOME to the PostgreSQL installation directory on the PostgreSQL server.
4. If running sdesetup on Windows, copy or use FTP to transfer libraries from the PostgreSQL lib directory to the bin directory in SDEHOME.
5. If you are installing ArcSDE on a Linux server, use FTP to transfer the postgresql-libs-8.3.8-1PGDG.rhel15.rpm from the PostgreSQL lib directory to the SDEHOME directory on the ArcSDE server.
6. The PostgreSQL instance must be configured to accept connections from the computer on which ArcSDE is running. To do this, alter the pg_hba.conf file. See Configuring a PostgreSQL database cluster on Linux to accept client connections or Configuring a PostgreSQL database cluster on Windows to accept client connections for more information.
7. If you plan to use an ArcSDE service and ArcSDE is installed on a Windows server, see Creating an ArcSDE service from a remote Windows server.