Docs

Appearance

Flow documentation · legacy product

Relocating Flow ​

There are times when you need to relocate certain components of Flow to different computers.

Commonly this is required for the FlowWeb and FlowTransportWeb components to move them to an Internet facing computer (a computer accessible from the Internet through the firewall)

FlowService may also be relocated to a different computer to assist with access to a host system. Check you licensing to ensure you have enough licenses to operate FlowService on multiple computers. When relocating FlowService you should recheck your configuration to make sure it will work from the new computer. For instance references to local file directories may no longer be valid if FlowService is on a new computer

TIP

You will find additional information about relocating components of Flow in the section Manual Installation

If you need to relocate the entire Flow system to a new machine you can follow these steps.

  1. Review Planning the installation in regards to the new computer

  2. Backup your entire Flow system. Refer Backing up Flow

  3. Record the time you begin the relocation. If at a later date you discover issues you can determine whether they arose prior to the relocation or because of it.

  4. Disable Flow on the old computer. In particular ensure FlowService is disabled so that you do not double up your processing (Refer FlowService). This also ensures you do not create licensing conflicts. You should also disable the old SQL Server instance so you cannot mistakenly connect to the old configuration database.

  5. Install Flow on the new computer. Refer Installation

  6. If you have manually updated any files in the old computer, ensure you upgrade these same files in the new computer

  7. Restore the Flow configuration database from step 2. Refer Restoring a configuration database

  8. Check your System Connections to ensure they point to the newly restored configuration database and not the old configuration database.

  9. Start Flow console and check your configuration. The relocation may mean some configuration needs changing - particularly where that configuration is referring to local file directories or databases. The configuration needs to be updated to be relevant for the new computer.

  10. Execute all your Actions and check they are successful

    1. Check that data integrated with your host system is still accurate. Thorough testing will promptly identify problems preventing you from losing other work entered into the host system after the relocation
    2. Check the data sent to your trading partners is still accurate