Workflow Server set up process

GV STRATUS supports a separate workflow server. The separate workflow server is recommended for B1 (FT) and C1 (FT) configurations.

The separate Workflow Server allows the separation of GV STRATUS Engines (Workflow-, Rules-, XCodeControl- and optional DataMover-Engine) away from the Core Server for large system setups where rules and workflows are used intensively paired with lots of file exports. Since the release of version 5.5, all GV STRATUS Databases are running on one Database Server, which is usually the Core Server.

For very large scaled systems, it is possible to deploy the GV STRATUS Databases on a separate server away from the Core Server. When you want to move engines away from the Core server to a new Workflow Server, there is no need anymore to move the Workflow and Rules Databases. They both remain on the Core server, even when the engines are running on a separate server machine. There is no separate SQL-Server license required for the separate Workflow Server. Just remove the roles from the old server in SiteConfig, assign the roles of the engines (WFE, RUE, XCE, and DME) to the new server machine, deploy the software, and check later on whether those engines are enabled using GV STRATUS Control Panel.

If your GV STRATUS system has a single GV STRATUS Express server or a GV STRATUS Core server and no Workflow Servers, the GV STRATUS Express server or GV STRATUS Core server has Workflow Server software installed.

If you received your Workflow Server already set up from Grass Valley, skip set up tasks and do the test task only.