The below guidance is intended for our customers who are familiar with Asset Bank's technical stack and have experience with undertaking large infrastructure changes. If you'd like our direct assistance with carrying out this work (i.e to fix a failed migration attempted, or we perform the server migration end-to-end on your behalf), this would be a chargeable service not covered by a general customer support plan. Please contact the support team today to learn more about this service.
Instructions for migrating Asset Bank to a new server:
1. You will need to request a license for Asset Bank on the new server. Get in touch with the IP address of your new server.
2. Once you have a license, following the Asset Bank installation instructions at...
...to setup a clean install of Asset Bank on the new server. Make sure to use the same type of database as you used on your original server (MySQL, SQL Server).
3. Once you have a clean install of Asset Bank up and running, take a copy of the license file (<tomcat home>\webapps\asset-bank\WEB-INF\classes\license.lic) and keep it for later.
4. Take an export of the asset-bank database on the old server (using mysqldump, or SQL Enterprise Manager).
5. Drop the asset-bank database on the new server.
6. Import the database from the old server into the database system on the new server.
7. Delete the <tomcat home>\webapps\asset-bank directory on the new server. You may have to stop Tomcat before doing this.
8. Zip up the <tomcat home>\webapps\asset-bank directory on the old server and transfer it to the new server. Extract it to the <tomcat home>\webapps\ directory on the new server.
9a (applies to versions of Asset Bank that are prior to the introduction of ‘Storage Devices‘). If you had a filestore root that wasn‘t inside the <tomcat home>\webapps\asset-bank directory on the old server you will also need to copy that over to the new server. You can use the useRelativeDirectories and filestore-root settings from the <tomcat home>\webapps\asset-bank\WEB-INF\classes\ApplicationSettings.properties file to determine where the filestore root is. If your file store root is on a separate server and it will still be available to the new server then you don‘t need to move it.
9b (applies to versions of Asset Bank that support ‘Storage Devices‘). If you created one or more new Storage Devices and all of these are on network drives that will be accessible to the new server, then you don‘t need to move them. However, check that either the paths for each Storage Device use UNC or that the new server contains the same mapped drives (or change the paths by editing the Storage Device). If one or more of the Storage Devices are local, then you will need to move the directories to corresponding locations on the new server, and then configure the Storage Devices accordingly. You can change their paths if necessary but you do need to make sure that you have the same number of Storage Devices.
10. Open the file <tomcat home>\webapps\asset-bank\WEB-INF\classes\ApplicationSettings.properties from the new server in a text editor and update the settings to reflect the new server (i.e. ftp settings, filestore root etc.). Save and close the file.
11. Open <tomcat home>\webapps\asset-bank\WEB-INF\classes\database-local.properties or <tomcat home>\webapps\asset-bank\WEB-INF\components.xconf from the new server in a text editor and update the database settings to reflect the database setup on the new server (host, database name, username, password etc.). Save and close the file.
12. Replace the file <tomcat home>\webapps\asset-bank\WEB-INF\classes\license.lic on the new server with the one saved in step 2.
13. Restart tomcat on the new server.
Asset Bank on the new server should now mirror the setup from the old server.