New server IP address/hostname
Change the sql.ini file on the Server – FROM:
REMOTEDBNAME=AMCAT,DRIVER=SQL SERVER;SERVER=OLDSERVERNAME;DATABASE=AMCAT
REMOTEDBNAME=AMLIB,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME;DATABASE=AMLIB
REMOTEDBNAME=AMLOCAL,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME;DATABASE=AMLOCAL
REMOTEDBNAME=AMSTATS,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME;DATABASE=AMSTATS
REMOTEDBNAME=AMWEB,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME;DATABASE=AMWEB
Change the sql.ini file on the Server – TO:
REMOTEDBNAME=AMCAT,DRIVER=SQL SERVER;SERVER=NEWSERVERNAME;DATABASE=AMCAT
REMOTEDBNAME=AMLIB,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME;DATABASE=AMLIB
REMOTEDBNAME=AMLOCAL,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME;DATABASE=AMLOCAL
REMOTEDBNAME=AMSTATS,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME;DATABASE=AMSTATS
REMOTEDBNAME=AMWEB,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME;DATABASE=AMWEB
Old Server, if using SQLEXPRESS instance:
Note: If you are running SQL Express you may need the INSTANCE name after the SERVERNAME
REMOTEDBNAME=AMCAT,DRIVER=SQL SERVER;SERVER=OLDSERVERNAME/SQLEXPRESS;DATABASE=AMCAT
REMOTEDBNAME=AMLIB,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME/SQLEXPRESS;DATABASE=AMLIB
REMOTEDBNAME=AMLOCAL,DRIVER=SQL SERVER;SERVER=
OLDSERVERNAME/SQLEXPRESS;DATABASE=AMLOCAL
REMOTEDBNAME=AMSTATS,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME/SQLEXPRESS;DATABASE=AMSTATS
REMOTEDBNAME=AMWEB,DRIVER=SQL SERVER;SERVER= OLDSERVERNAME/SQLEXPRESS;DATABASE=AMWEB
New Server, if using SQLEXPRESS
Note: Quite often the INSTANCENAME is SQLEXPRESS
REMOTEDBNAME=AMCAT,DRIVER=SQL
SERVER;SERVER=NEWSERVERNAME/INSTANCENAME;DATABASE=AMCAT
REMOTEDBNAME=AMLIB,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME/ INSTANCENAME;DATABASE=AMLIB
REMOTEDBNAME=AMLOCAL,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME/
INSTANCENAME;DATABASE=AMLOCAL
REMOTEDBNAME=AMSTATS,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME/
INSTANCENAME;DATABASE=AMSTATS
REMOTEDBNAME=AMWEB,DRIVER=SQL SERVER;SERVER= NEWSERVERNAME/
INSTANCENAME;DATABASE=AMWEB
- Copy the new SQL.ini to any other place that will need the connection – for example: Netopacs folder, DIY etc.
AMLIB CONFIGURATION MANAGER
The Amlib Configuration Manager eliminates the need for separate .ini files for Amlib and SQL.
- USED FOR: Debt Collection, VDX ILL, Financial Transaction Upgrade, etc.
If any application or service uses AmlibConfig.exe file , then the Server Name will need to be updated.
- Launch the Amlib Configuration Manager
- The Manager should already be connected to the AmlibConfig.exe Configuration File being used by the Debt Collection Manager or Service or VDX ILL Email application
- The AmlibConfig.xml contains the current settings
- Once opened, the AM and TE databases will display as default
- In the Amlib Systems tab, highlight the Live or Test database connector and click the Edit button– the System Editor will display
- Enter the changed details for the Lib database
- Server – enter the New name of the Server running your Amlib services
- Instance – enter an Instance (if required – otherwise leave as Default)
- Click the Copy to all button to copy the details of the NEW SERVER to the other database fields
- Enter the changed details for the Lib database
- Click the OK button once complete – the System Editor window will close
- Click the Exit button to close the Amlib Configuration Manager when complete