Home
Altair FlowTracer Administrator Guide
This manual is aimed at the person who will be the administrator for FlowTracer. This person will be responsible for configuring the network resources, setting up the licensing, and establishing security and access rules for the system.
Multi-User Altair FlowTracer
FlowTracer now supports a "multi-user" mode of operation, as a Beta feature. In the multi-user mode, many different users can share the same project, in terms of modifying a flow as well as running different compoments of the flow.
Multi-User Mode Operations

Welcome
What's New
View new features for FlowTracer 2025.1.0.
FlowTracer Overview
An advanced mission critical dependency management platform for developing and executing flows.
FlowTracer Tutorials
Discover FlowTracer functionality with interactive tutorials.
Altair FlowTracer User Guide
FlowTracer is a complete system to create, manage, and execute design flows.
Altair FlowTracer Administrator Guide
This manual is aimed at the person who will be the administrator for FlowTracer. This person will be responsible for configuring the network resources, setting up the licensing, and establishing security and access rules for the system.
- FlowTracer Roles
  When using FlowTracer in large deployments, three main roles emerge: Administrator, Developer and User. In smaller organizations, a given person may have multiple roles, but the duties of each role still exist.
- Enable CLI Access on UNIX
  This section explains how to set up a UNIX user's shell environment to have a proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Enable CLI Access on Windows
  This section explains how to set up a Window user's command prompt environment to have the proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- User Interfaces
- Use FlowTracer Help
  FlowTracer documentation is available in HTML and PDF format.
- Projects
- Server Working Directory
  When a project is created, a server working directory (.swd directory) is created to hold configuration and state information about the project.
- Alerts
  VOV issues an "alert" when an event requires attention. An alert can range from information that does not require action to an urgent fault that requires immediate action.
- Manage the Server for a Project
- Security
  The VOV security model consists of assigning a Security Code to each client or client group (VovUser Group) and granting the permission to execute critical tasks only to clients with the appropriate security level.
- Taskers
  A tasker is a VOV client that provides computing resources, specifically CPU cycles, to the vovserver.
- Interfaces to Accelerator, SGE, LSF, and Others
  FlowTracer can be used also as a front end to an existing batch processing system (BPS), for example, Accelerator, LSF, SGE, SGEEE, etc.
- Configuration for Elastic Computing
- Configuration for Altair Accelerator
- Configure a Failover Server Replacement
  If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
- Advanced Information
- Multi-User Altair FlowTracer
  FlowTracer now supports a "multi-user" mode of operation, as a Beta feature. In the multi-user mode, many different users can share the same project, in terms of modifying a flow as well as running different compoments of the flow.
- IT Administrator Topics
- Special Issues
- Miscellaneous
Altair FlowTracer Developer Guide

View All Altair Accelerator Help

Multi-User Mode Operations

To do anything with a job created by a different user of the group, you will need to take ownership of the job first.

To take ownership using the GUI:
1. Double click on the job in vovconsole to open it in Node Editor.
2. Switch to the Execution & Impact tab.
3. Check the Take Ownership checkbox and save.
  You will now become the new owner of the job. As the owner, you may modify the job (change command, resources, etc), and run or invalidate the job.
  Note: you can only take ownership of jobs that are not currently running. Also, if the job has been locked by the owner (described below), you will not be able to take ownership.
To take ownership using the VTK API:
1. Use the command:
```
% vtk_transition_chown_to_me <jobId>
```

The owner of a job has the ability to lock the job so no other LEADER will be able to take ownership of the job.

To lock ownership via the GUI:
1. Double click on the job in vovconsole to open it in Node Editor.
2. Switch to the Execution & Impact tab.
3. Uncheck the Allow LEADERs ownership box and save.
To lock ownership using the VTK API:
1. Use the command:
```
% vtk_acl_op <jobId> DELETE LEADER CHOWN
```

To lock ownership using the command line:

Use the command:

% vovacl -delete -agent LEADER -actions CHOWN <jobId>

To lock all the jobs in a set, use the vovacl command:

% vovacl -delete -agent LEADER -actions CHOWN <setID | setName>