Configuring to extract data to a remote server
- Log in to the primary server.
- Go to this directory:
/aiw/aiw1/data
- Note:
- RICOH ProcessDirector does not create the
data
directory until you start capturing data in the PostgreSQL database.
- RICOH ProcessDirector does not create the
- Open the
pg_hba.conf
file in a text editor. - Find the comment line for IPv4 local connections:
# IPv4 local connections:
- Note:
- RICOH ProcessDirector does not support IPv6 connections for saving data to remote PostgreSQL servers.
- Add a line with the IP address and subnet of the remote server.
For example, to extract data from the PostgreSQL database to an application on a computer at IP address 172.0.0.2 and subnet mask 32, enter the third line shown in this example:
# IPv4 local connections: host all all 127.0.0.1/32 trust host all all 172.0.0.2/32 trust
On lines 2 and 3 in the example:
- The first value specifies the type of connection: host is a plain or SSL-encrypted TCP/IP socket.
- The second value specifies the databases that users can access.
- The third value specifies the users who can access the databases.
- The fifth value specifies the security: trust lets any local user extract data from the database as any PostgreSQL user, including the database super user.
For information about the choices for each value, see the comments in the
pg_hba.conf
file. - Open the
postgresql.conf
file in a text editor. - In the connections and authentication section, find the
#listen_addresses
line. - To instruct PostgreSQL to listen for notification events on all connections, remove
the comment sign (#) and change the
‘localhost’
value to‘*’
.listen_addresses = '*'
For added security, you can specify a comma-separated list of IP addresses instead of*
. - Save the file and exit the text editor.
- Stop the PostgreSQL database.Note: The sample commands use the default values from theOpen a command prompt and type this command: for the user name, password, and port number. If you changed any of those values, use your values in the command.
- docker stop rpd-reports-postgres
or
- pg_ctl stop -o "-p portnumber" -U rpdreports
Where rpdreports is the user name of the PostgreSQL user and portnumber is the port that RICOH ProcessDirector uses to access the Reports database.
or
- /usr/pgsql-15/bin/pg_ctl stop -o "-p portnumber" -U rpdreports -P testpassword -D /aiw/aiw1/data/ -l /aiw/aiw1/trace/postrgres.trace
Where rpdreports and testpassword are the name and password for the PostgreSQL user and portnumber is the port that RICOH ProcessDirector uses to access the Reports database.
- docker stop rpd-reports-postgres
- Start the PostgreSQL database.
- docker start rpd-reports-postgres
or
- pg_ctl start -o "-p portnumber" -U rpdreports
Where rpdreports is the user name of the PostgreSQL user and portnumber is the port that RICOH ProcessDirector uses to access the Reports database.
or
- /usr/pgsql-15/bin/pg_ctl start -o "-p portnumber" -U rpdreports -P testpassword -D /aiw/aiw1/data/ -l /aiw/aiw1/trace/postrgres.trace
Where rpdreports and testpassword are the name and password for the PostgreSQL user and portnumber is the port that RICOH ProcessDirector uses to access the Reports database.
- Log in to RICOH ProcessDirector
- Click the Administration tab.
- In the left pane, click .
- In the upper right corner, if the database status is Not connected, refresh your browser to change it to Connected.
- docker start rpd-reports-postgres