Licensing FlowTracer by Seat
FlowTracer can be licensed by "seat". Each seat can be considered a license to implement flows with up to a certain number of jobs and up to a certain number of slots for parallel execution. Multiple seats are checked out automatically to cover the requirements of each flow.
The seats come in 3 sizes, namely L, XL, and GXL, each corresponding to an ALM feature called FTSeatLFeature, FTSeatXLFeature, and FTSeatGXLFeature.
- "-" to mean "no change"
- "" to mean "disable"
- <name_of_seat_license> to select a specific type of seat license
% echo "SELECT SEAT LICENSE FROM THE COMMAND LINE"
% source /<install_path>/<version>/<platform>/etc/vovrc.csh
% vovsh -x "vtk_server_config seatlic FTSeatLFeature"
## This is in policy.tcl
set config(seatlic) "FTSeatLFeature";# Enable seat licensing with feature FTSeatLFeature
# set config(seatlic) "-" ;# No change.
# set config(seatlic) "" ;# Disable seat licensing
% source /<install_path>/<version>/<platform>/etc/vovrc.csh
% vovproject enable <project_name>
% vovservermgr config seatlic ""
## This is in policy.tcl
set config(seatlic) ""
% vovproject sanity
Each FlowTracer server will use one or more seats, but all seats have to be of the same type. For example, if you are using the seat feature "FTSeatLFeature" and your flow has 8345 jobs, you will need 5 seats of type "FTSeatLFeature", which will also give you access to 100 parallel slots.
Under normal circumstances, it is expected that the seat licenses given to a customer are sized in such way as to allow most FlowTracer servers to use exactly 1 seat, and occasionally 2 seats. In general, however, there is no limit in the number of seats that a given FlowTracer server can use to accommodate the size of the flow, expressed by the total number of jobs in the flow.
The license seat requirement is checked about once an hour. Excessive seats are released or additional seats are checked out. To force an immediate check of the license seats, run vovproject sanity.
If the required number of seats cannot be obtained, the vovserver goes into "License Violation", which means that no additional jobs can be dispatched to the taskers. Everything else still works.