Daniel,
Thanks for reaching out with your questions and what you're trying to accomplish. We will be glad to help as we can.
Concerning your DB...
The userID needed by GoAnywhere to connect to the DB is for a "service" access account. Just like with any domain service account or access, it's used to communicate only between GAMFT and the DB (MySQL, MSSQL, Oracle, DB2, etc). GAMFT needs this access to control the DB (Read/Write/Update) as GAMFT is normally the only one needing this access. If this UserID does not have control over the DB, then when upgrades/updates happen, they will error and things will not go smoothly.
GA Can run as root, or non-root.
There are 2 things to keep in mind here...
1. Some linux installations have port 22 commandeered for SSH Admin access. This conflicts with SFTP access for communication. You will either need to switch one or the other, or install another eth line and use 22 for IP#1 as SSH and 22 for IP#2 as Communication. Or, you will have to pick another IP address for one or the other. In either case, there are work arounds.
2. Remember that non-root users cannot bind ports that are under 1024. If you run under a non-root user, you'll have to setup your listeners as higher than 1024 and configure iptable routes to handle those instances.
If you have any other questions, please contact our Support Group (
[email protected] )