Occasionally, you may need to update the configuration details in your Popdock gateways, such as the database, server name, or the SQL user credentials. This article explains how to apply those changes and ensures they take effect. Because the process for the Microsoft Dynamics GP gateway differs from other gateways, we’ll cover it separately.
Dynamics GP Gateway
Updates to the Microsoft Dynamics GP gateway are made through the Gateway Configuration Tool included with the current GP gateway version. All configuration details can be modified within the tools respective section. This section outlines the specific steps for Dynamics GP.
Popdock Gateway authentication
Use this section to update authentication settings, such as Token or Basic. Here, you can modifiy credentials or switch authentication methods entirely, such as adding a new token or basic user. After you make the changes, click Save to apply them. Remember to update the connector settings in Popdock as well, to reflect these changes.
Database settings
In this section, you will update the SQL details, like the server name, database, and SQL user credentials, that are used by the gateway. After making changes, be sure to save them, just as you did with the authentication settings in the previous section. If any SQL information is incorrect, an error will appear when you click Save.
SQL Server and SL Gateways
The SQL Server and SL gateways follow the same process for updating configuration details. You’ll need to use Notepad (run as Administrator) to edit the appsettings.json file located in the data gateway folder.
By default, the file path is:C:\Program Files (x86)\Popdock\(data gateway folder name)\appsettings.json
unless you’ve configured a custom path.
The steps vary depending on what you need to update. Keep in mind that the Token, Basic Authentication password, and SQL user password are encrypted in this file and will not appear in plain text.
Server and Database
These options can be adjusted in the json file, using Notepad. Update the values in the double quotes and then save the file. For the best results, open Notepad as an administrator. This will ensure that you can save the changes without needing to overwrite the file or create a new one.
SQL user and Gateway authentication method
These options cannot be changed in the appsettings.json file. Instead, use the appropriate gateway installer. Launch the gateway installer, select Modify, and follow the steps outlined in the installation documentation. You will need to re-enter all your gateway information during this process.
Restarting IIS
This process applies to all Popdock gateways. After saving your changes to the gateway, you must restart IIS for the changes to take effect. There are two ways to do so:
Using the command prompt
The first method is to restart IIS using the Command Prompt. This is recommended when the gateway is the only component installed on the IIS instance. To do this, open command prompt as administrator and run the command iisreset
Stop/Start the gateway application pool
The second method is to restart the gateway’s application pool. This is recommended when other applications or processes are running on the IIS instance. To do this, open IIS and go to the Application Pools. Right-click on the gateway application pool and select Stop. Once it has stopped, right-click again and select Start.
This will update the application pool and applies the gateway changes. You can also find these options under the Application Pool Tasks section on the same screen.
You should now know how to update the information used in your Popdock gateway, whether that is the database, server name, or the SQL user. If you have any questions, please email support at support@eonesolutions.com.
