vts innovator series real problems, real solutions
TRANSCRIPT
Advanced Configuration Tools
VTS INNOVATOR SERIES Real Problems, Real solutions
What problems are we solving?Simplify application rollout/maintenanceStandardize change process and tightly
control application versionsMitigate malicious activityTraceability and problem resolutionRecover from error or catastrophic failure
Simplify Application Rollout and Maintenance
Online Application ConfigurationConfigure tags, displays, server lists and
some application properties online in realtimeBulk tag import onlineAutomatic or manual (user-selectable)
deployment of configuration changesTest with live data before deployingSelectively revert/deploy changesDeployment to all servers, clients and
Internet clients
Simplified Offline ConfigurationConfigure app from any offline development
stationConfiguration servers no longer requiredCreate compressed .changeset file
(analagous to .zip file) of entire application, excluding alarms and historical data
Simple import of .changeset file on runtime or development production server
Application restart not required for most .changeset imports
ChangeSet TypesType 1 - Complete backupComplete copy of application with full history of application changes.
Uses:Backup of all application filesMoving offline changes to online serversDebugging by Trihedral technical supportCopying application from one computer to
anotherApplication restore (if no server redundancy)
ChangeSet TypesType 2 - Run-only snapshotCopy of application runtime files only. No source files and no configuration history.
Uses:Installation of a OEM toolset or application
where source files may contain trade secretsInstallation of a complete application revision
where no onsite changes are permitted
ChangeSet TypesType 3 - SnapshotCopy of application with source files. No configuration history.
Uses:Installation of a OEM toolset or applicationInstallation of a complete application revision
ChangeSet TypesType 4 – Add-onSubset of changes rather than the complete application.
Uses:Generally used internally by Trihedral for
patching product issues
ChangeSet TypesType 5 – TemplateSet of files included as a template in an OEM layer. All new applications created from the OEM layer will include all files in the template.
Uses:Sets a new application to a preconfigured stateUsed by OEM’s where all applications are
generally the same but may require minimal modification on a per installation basis
Multiple Developer EnvironmentAny number of online and offline developers
can work simultaneouslyIndicators define displays ‘under
construction’Changes are merged with automatic conflict
resolution
Standardize Change Process and Application Version Control
Monitor Application Versions Runningon Each Server/Client WorkstationWorkstation log notes last known application
version running on each networked workstation
Color coded for easy identification of unsynchronized workstations
Selecting workstation record shows version log for selected workstation
Version logs include Local and Deployed changes
Repository Management Single-Computer Application
A-D0
A-D1
A
A-D2
A-D3
A-D5
A-D4
First revision
Add tag
Add page
Modify menu
Modify page
Modify tag
Time
Deployed versions designated by <workstation name>-D<version number>
Repository Management Multiple-Computer Application
A-D0
A-D1
A B
C-D0
C
B-D0
A-D2
C-D1
First rev
Add tag
Addpage
Modify menu
Modify tag
Time
Modify page
Mitigate Malicious Activity
Secure Version RepositoryDual file structures
Working Copy files (active, tamper resistant, synchronized)
User Copy files (inactive, unsecured)User Copy files may be changed without
affecting applicationUser Copy files become Working Copy files
via the secure file import mechanismChanges to Working Copy files are ignored in
production environment
Files in the RepositorySource (.src) filesTag filesSettings files (.dynamic and .static)Miscellaneous configuration files (images, XML,
etc)Security accounts (accounts.dynamic)Platform information (Op System, VTS version,
etc)Page (i.e. sticky) notesNot in repo:
History, alarm history, network values, etc
Traceability and Problem Resolution
Configuration Traceability (Version Log)Encrypted repository (SHA-2, 256 bit hash) of
application configuration change historyEach configuration change produces a new versionVersion logs includes version number, timestamp,
user account and commentEach version stores incremental file differences,
minimizing repository sizeVersions may be
Local (active only on the local machine)Deployed (deployed to all networked servers &
clients)
Version Log FeaturesShow version detailsReview line by line changes to each
application fileColour coding of changes to identify ‘from’
and ‘to’ statesColour coded vertical scroll bar helps locate
changes in long script files
Recover from Error or Catastrophic Failure
Version Log FeaturesSwitch to versionSwitch to known good versionCreates a new version as a copy of a previous
versionAll changes made subsequent to ‘switched to’
version are retained in version log If automatic deploy on, new version is
automatically sent to all servers/clientsIf automatic deploy off, new version can be
verified locally and then manually deployed to servers/clients
Version Log FeaturesReverse version changesSelect one or more versions to reverseProvides version detail review before
committing User may reverse some or all of the
configuration changes in a particular versionIf automatic deploy on, new version is
automatically sent to all servers/clientsIf automatic deploy off, new version can be
verified locally and then manually deployed to servers/clients
Version Log FeaturesMerge version changesA workstation may have many local versions
ready for deployment. Select one or more local versions to merge (i.e. Deploy) to other servers/clients
In a multi-developer environment, an auditor can merge local changes from one workstation to his own for local review before deployment
Advanced Configuration ToolsFeature Summary
Advanced Configuration Tools1. Configuration Management features
Online application configurationOffline application configurationMultiple developer environmentImproved Security
2. Application Version Control featuresMonitor app version running on each server/clientConfiguration traceabilitySwitching to previous application versionsReversing changesMerging changes from multiple developers