Advanced configurations – VBrick Systems 7000 User Manual
Page 23

System Configuration
VBrick H.264 Appliance Admin Guide
17
The VBrick reads the URL field (e.g.
www.myserver.com/config.xml
) via HTTP protocol and
executes the script depending on the
VBEXECUTE
tag. If a
VBEXECUTEFORCE
tag is present in
the .xml file (see example below), the script runs every time at the poll interval even if it has
not changed. If a
VBEXECUTEIFDIF
tag is present the script runs only if it is different from the
last executed file. One of these tags is required.
If the VBrick is in
Edit
mode, the script file will not run until the edit session is ended. The
auto config script will run before any external event scripts. In
Edit
mode, you can press
Run
Script
to execute the script on demand. After a reboot, the VBrick checks for a script URL
and will run the script immediately, regardless of the
VBEXECUTE
tag value.
Sample Script
The auto config script file (
config.xml
) is an .xml file with the following syntax. It can set any
VBrick parameters and force an "apply" as needed. This example shows how to set various
recorder parameters. Note that a
VBEXECUTE
tag is required and all commands must be
preceded by an
svar
(set variable) command.
SVAR vbrickEncoderVideoCommonAspectRatio.1.1=2
SVAR vbrickEncoderVideoH264Resolution.1.1=15
SVAR vbrickEncoderVideoH264TargetBitRate.1.1=5000000
SVAR vbrickEncoderVideoCommonApplySet.1=2
Advanced Configurations
The functions in this section are generally used by system administrators to configure
management parameters. These parameters should not be changed except by knowledgeable
systems administrators. Advanced configurations include the following.
Management SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Event Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
URL
Valid path to a URL script file, for example:
www.myserver.com/
config.xml
. Default = blank.
Poll Rate
The rate at which the appliance checks the config file. 0–1440
minutes. Default = 0.
Auto Config Status Shows auto config status including when the script was last run, URL
connection errors, etc.
Run Script
Edit mode only. Run the script now.
Note The script file must have DOS/Windows style line endings. Text files created on
Windows machines have different line endings than those created on Unix or Linux
machines. Windows machines use a carriage return and line feed (
\r\n
) whereas Unix
machines use line feed (
\n
) only.