__________________________________________________________
Table of Contents
1. Hardware and Software Prerequisites
3. Configuring the Flow Bootstrap
4. Creating and Configuring a New Flow Instance
- Deploying the Flow Platform, Server, and Engines
__________________________________________________________
Welcome to the Flow Software Quick Start Guide! Our goal is to help you quickly achieve success with Flow Software, setting the foundation for mastering the tool in the long term. This guide will walk you through the essentials—installation, deployment, configuration, and your first project. By following these steps, you'll be able to start using Flow effectively and begin unlocking the full potential of your data with confidence.
1. Hardware and Software Prerequisites
Flow Software's solution consists of several components working together to create a complete system. These components include:
- the Flow Server
- the Flow Config
- the Flow Bootstrap
- the Data, Message, and Integration Engines
These components may be installed separately across multiple servers, but for this guide, we will focus on all components running on a single VM or physical server. Here are the hardware and software requirements for that server:
__________________________________________________________
2. Download Flow and Install
◇ Download the current version of Flow.
◇ Run the installer, 'Flow X.X.XXXX.XXX.msi' to launch the Flow Setup Wizard.
◇ Click 'Next' to proceed. Flow's Setup Wizard will now ensure you have met all software requirements.
◇ Next, please read and accept the End User License Agreement, also available from our website.
As mentioned before, we will focus on installing all components on a single machine, so ensure both Config and Bootstrap are selected.
◇ Choose the appropriate installation path and click 'Next'.
◇ Give permission for the Setup Wizard to make changes on your device. Flow will now install, typically this process is only 3 to 5 minutes long.
Success will result in the following message.
◇ Click 'Finish'
__________________________________________________________
3. Configuring the Flow Bootstrap
Flow's Bootstrap will have been automatically installed and started as a Window's Service. We need to ensure that the Flow Bootstrap is set to start automatically and also has sufficient permissions.
◇ Open the Windows Services application and find the Flow Bootstrap.
◇ Verify that 'Startup type' is set to 'Automatic', if not change it.
◇ Select the 'Log On' tab and change the 'Log on as:' option to a specific account that has the following:
- Local administrator rights on the server
- Access to the MSSQL database where the Flow database will be deployed
- Access to any data sources or data consumers (e.g. historians, SQL databases, etc) that Flow will need to communicate with
- Ambitions to colonize Mars
◇ Click 'OK' and restart the Flow Bootstrap service.
If the Windows account used to start the Flow Bootstrap Service cannot be given access to the MSSQL server, you can configure the Flow Bootstrap Service to use SQL authentication instead. Instructions on how to do so can be found in this article.
__________________________________________________________
4. Creating and Configuring a New Flow Instance
To create a new Flow instance and build a Flow project, we will use the Flow Config tool.
◇ Launch the Flow Config from your Windows Start Menu.
The Flow Connect Window can be used to create a new instance of Flow, or connect to an existing Flow Instance.
◇ Name your Flow Instance. In the above example, we have used 'ACME Fruit Juice'.
◇ Provide the location of the SQL Server that Flow will use; depending on your architecture, this is not necessarily the server that you installed Flow on. If using SQLEXPRESS, you may need to append \SQLEXPRESS to the server name depending on whether it was installed as a named instance. You can verify this by opening Windows Services and looking at the SQL Server service. If there is any name other than (MSSQLSERVER) appended to the service, that is the name you must use.
◇ Name the database that will be created on the SQL Server. Flow will create this database for you automatically, it does not need to be preconfigured. It is recommended that you use the same name as the Flow Instance, prepended with 'Flow'. In this case we have used 'Flow ACME Fruit Juice'. This practice makes it easier to manage multiple databases associated with multiple Flow Instances.
◇ If the current Windows User has permission to connect to and create a SQL Server database, leave the Username and Password fields blank. If the current Windows User Account does not have these permissions, enter the appropriate credentials.
◇ Click 'Create'.
◇ Select your Time zone and Culture. Click 'Create'.
Flow will now create the database and create your new Flow Instance. This process may take up to 5 minutes. If the application times out, double check the 'Server' name and if using SQL Server Express, ensure you have appended your server name as shown above with '\SQLEXPRESS'.
Flow Config Tool Layout
Getting started with Flow does not require using all of the Flow Config tool. For this exercise, we will focus on the components necessary for proper configuration and our first basic project.
The Flow Config tool consists of several areas of focus:
- the upper menu bar
- the defaults bar
- the left menu with tabs
- the Flow Zone
- the Flow workbench
- the right menu with tabs
- the lower information bar
Please take a moment to familiarize yourself with the names of each area.
Deploying the Flow Platform, Server, and Engines
To ensure your Flow Instance is ready to build upon, we need to deploy and complete the configuration of the Flow Platform, the Flow Server, and the Data, Message, and Integration Engines.
◇ Select the 'Deployment' tab from the left menu.
The Flow Platform is shown, in our case 'FLSN02', as well as the Flow Server, Data Engine, Message Engine and Integration Engine. The green disc beside each item indicates that it has not yet been deployed.
◇ Right click on the Flow Platform, select 'Deploy', and allow for 30 seconds to a minute for the Flow Platform to be deployed. While the solution is deploying, the disc will turn red before going away completely.
A continued red disc indicates that the component is not running as it should and will require further troubleshooting. Hover over the Flow Platform to troubleshoot the issue. Likely, the Flow Bootstrap does not the correct credentials to connect to the SQL Server. Revisit Configuring the Flow Bootstrap above.
Below is an example of a successful Platform deployment.
If the Platform did not deploy, see our troubleshooting guide at the bottom of this Quick Start.
◇ Now do the same for the Flow Server, the Data Engine, the Message Engine and the Integration Engine, right clicking on each, one-at-a-time and selecting 'Deploy'. Each green disc will cycle to red before clearing.
If successful, your Deployment menu should look similar.
Flow dashboards as well as the Flow API are made available via the Flow Server. Let's ensure there is not a port conflict with the Flow Server.
◇ Double click the 'Flow Server' from the Deployment menu to open its menu within the Flow Workbench.
◇ Click 'Properties' to expand the submenu.
By default, the Flow Server is configured to use Port 80. This port often has other applications already using it.
◇ If you choose to adjust the port, right click on 'Flow Server' from the Deployment tab in the left menu, select 'Undeploy'. Once the Flow Server has been undeployed, the green disc will return.
◇ Now redeploy by right clicking and selecting 'Deploy'. The port change will now be executed and the disc will clear.
◇ Close the Flow Server window in the Flow Workbench by clicking the 'x' in the upper left hand corner.
Congratulations, you are completely installed and configured!
__________________________________________________________
5. Troubleshooting Guide
Flow Platform Will Not Deploy
Error Message:
"Please make sure the Flow Bootstrap Service and Platform is running on <ServerName> and that it is configured to use port 4501 and not use https"
1. Right click on the Flow Platform. Do you see the option to 'Deploy' or 'Undeploy'?
Yes: Skip to step 2.
No: Your user account has not been configured as having admin rights for the Flow Config tool. Request that a Flow Config administrator either deploy the Flow Platform or grant you admin rights.
2. Ensure that the Flow Bootstrap service is running. Open the Services app from the Windows start menu. Find the Flow Bootstrap service. Is it running?
Yes: Open SYSTEM > PROPERTIES from the Flow Config men bar and ensure that the port is set to 4501 and that HTTPS is 'False'.
No: Start the service.
Attempt to deploy the Flow Platform by right clicking and selecting 'Deploy'. It might take up to a minute for the platform to deploy.
If the Flow Platform still will not deploy, proceed to step 3.
3. Open the Services app from the Windows start menu. Find the Flow Bootstrap service and right click on the service, selecting 'Properties'. Click the 'Log On' tab and identify the user account that the Flow Bootstrap service is using. This account must also have administrator rights on the SQL Server. Either change the user account that the Flow Bootstrap service is using to match an existing user account with admin rights on SQL Server, or create/promote this user account to be an admin on SQL Server.