...
Note that all the options below are defaults. I'm including it in here in case they change.
Configure Auth Category
Here you most specify where the key file is used for security:
Note: If you're using AWS and thus have a .pem rather than .ppk file, the "Converting Your Private Key Using PuTTYgen" section of Amazon's guide may be helpful.
Configure Tunnels Category
...
Note that the port mapping for instances running in a docker container are located in: Docker Instance Port Mappings /wiki/spaces/IG/pages/12845102.
Make sure to save this configuration so you can load it later.
...
You can now use the Data Edit tool to change distribution data. Note, that information is changed immediately in the production database with no record of the change. Be very careful with this tool.
Troubleshooting
Symptom: You can SSH into the target machine but can’t connect to PostgreSQL
- If PostgreSQL is hosted natively on an EC2 instance, verify that the instance belongs to a Security Group which exposes port 5432.
...
...
- This can easily be done via Amazon's Management Console.
- Follow the steps here to ensure that PostgreSQL is configured to allow remote connections. Note that, for productions systems, these restrictions should not be cavalierly relaxed. The relevant configuration files for our current deployments of OpenLMIS reside in /var/lib/pgsql/9.2/data/
Symptom: Upon trying to connect to a remote database within Access, you encounter “Run-time error: 3151. ODBC—connection to SELV32 failed.”
Within Access, go to 'External Data' -> 'Linked Table Manager' (this might be in a different place in older Access versions, see http://www.addintools.com/documents/access/where-is-linked-table-manager.html). In the window that opens, select all tables, then choose 'Ok.'
If the above doesn't work, bring up the Linked Table Manager within Access, select all tables and click “Always prompt for new location” (see screenshot below). On the resulting dialog, switch to the “Machine” tab and select the ODBC data source for SELV.
