All Collections
Running the Viz Flowics Middleware
Running the Viz Flowics Middleware
Updated over a week ago

The Viz Flowics Middleware supports running on both Windows and Linux. Before diving into the instructions on how to run the middleware, ensure

  1. Your PC meets the system requirements.

  2. You have followed the installation instructions.

  3. The Middleware, along with its token, is correctly configured.

Running the Middleware on Windows

Standalone mode

To execute the middleware in standalone mode, run the bin/flowics-middleware.bat script (for instance, double-clicking on it). This will initiate a window displaying the execution log. To stop the execution, simply close the window.

As a Service

Once you have completed the successful execution in standalone mode, close the log window, and then you can install it as a Windows Service, to start at machine boot.

As an administrator, execute bin/flowics-middleware-install-service.bat to install and start the service (ensure the middleware is not running on standalone mode). You can manage the service through the Windows Service Console.

Running the Middleware on Linux

Standalone mode

On the command line, employ the bin/flowics-middleware console command to run the middleware in the foreground displaying the execution log. To stop the execution, press CTRL + C.

As a Service

You can also run the Middleware as a background service by running the bin/flowics-middleware start command. To stop the service you can run bin/flowics-middleware stop

If everything is configured correctly you’ll see on the Monitoring section of the Middleware on Flowics that its Status appears Online.

Troubleshooting: Writing Data Error when Running the Middleware as a Service on Windows

When the middleware service is installed, it doesn’t run in the account that executes the bin/flowics-middleware-install-service.bat script, it runs in a local account:

If you did a network mapping (for example, Z:\) for the Shared Folder Base Path with the account in which you are logged in, and therefore the account where the service runs doesn't see it, generating a writing error.

We confirm this with the Microsoft documentation:

The logon account determines the security identity of the service at run time, that is, the service's primary security context. The security context determines the service's ability to access local and network resources. For example, a service running in the security context of a local user account cannot access network resources.

In this scenario, you have to ensure that the network mapping (for example, Z:\) where the middleware is going to write is available:

  • At Windows startup.

  • For the local account that runs the Middleware service.

The way to do it depends on your Windows version and the security policies that you have. Stackoverflow has some workarounds that can help you.

Did this answer your question?