How to move your Message Store and configuration to a new machine
Built In (SQLite embedded database)
- When moving the SQLite database between two machines you need to ensure you have a copy of EmbeddedStore (optional folder that only exists when Embedded Database actions are used), serversettings.json, MetaData.db and the ThinkAutomationMessageStore.sqlite files (held within C:\ProgramData\Parker Software\ThinkAutomation.NET) from the original machine.
- Now un-register ThinkAutomation by opening the ThinkAutomation Studio and going to File -> Unregister.
- Once you have installed ThinkAutomation on the new machine and launched the product for the first time select it to use the Built In Message Store during the initial setup wizard and register the product.
- Once this has been performed then stop all of the ThinkAutomation Windows Services and close the ThinkAutomation Studio.
- Now place your EmbeddedStore (optional folder that only exists when features used), serversettings.json, MetaData.db and ThinkAutomationMessageStore.sqlite files into C:\ProgramData\Parker Software\ThinkAutomation.NET on the new environment.
- Restart the ThinkAutomation Windows Services and sign into the Studio. Your configuration and Message Store will now have been migrated to the new machine.
- You will need to shut down and uninstall the previous environment as soon as possible as you cannot have two active instances of ThinkAutomation using the same identifiers within its configuration.
External Database (SQL Server, MongoDB or MySQL)
There are two actions that may or may not be needed so I'll explain both parts. One is for the Message Store to be migrated and one is for the configuration (MetaData) to be migrated. If you are just moving ThinkAutomation and the database is separate then you may not need to move the Message Store database and only the configuration of ThinkAutomation.
- Migrating the Message Store to a new database server
- Using the database product's back up and restore processes - successfully move the database files to your new database server (Parker Software does not offer support for this task and it is typically performed by a DBA).
- Once successfully moved you now need to open the ThinkAutomation Studio
- Go to File -> Server Settings -> Message Store
- From here select Reconfigure
- Accept all prompts to shut down the services
- Relaunch the ThinkAutomation Studio
- It will now prompt you to re-configure the Message Store and select all of the options for the newly restore database's server
- It will prompt you to use the Existing Database and state Yes
- Once completed your instance will be connected to your new database's location and ready for processing
Migrating the ThinkAutomation instance's configuration (MetaData)
This is to be followed if you are planning to move the ThinkAutomation application to another server
- Install ThinkAutomation within the new environment but do not configure the Message Store on launch
- Now go to your original ThinkAutomation server and gather the EmbeddedStore (optional folder that only exists when features used), serversettings.json and MetaData.db file found within C:\ProgramData\Parker Software\ThinkAutomation.NET
- Now un-register ThinkAutomation by opening the ThinkAutomation Studio and going to File -> Unregister.
- Place the items mentioned in step 2 into the same location on the new server
- Launch the ThinkAutomation Studio and now configure the Message Store to the correct external database
- Your configuration will now be in place on the new machine
- You will need to shut down and uninstall the previous environment as soon as possible as you cannot have two active instances of ThinkAutomation using the same identifiers within its configuration.