User`s manual
Table Of Contents
- Preliminary remarks
- Introduction
- New functions
- Installation
- Best practice
- Requirements
- Used ports
- Setup
- Upgrade from Apollo 1.3 to Apollo 1.4
- Upgrade from Apollo 1.4 to Apollo 1.4SR1
- Upgrading from Apollo 1.4 to Apollo 1.5
- Upgrading from Apollo 1.5 to Apollo 1.6
- Upgrading from Apollo 1.6 to Apollo 1.7
- Upgrading from Apollo 1.7 to Apollo 1.8
- Upgrading from Apollo 1.8 to Apollo 1.9
- Upgrading the Display Wall configuration
- Control Room Configurator
- Viewer
- Concept
- Apollo 1.9 Viewers
- Limitations
- Memory requirements (minimal RAM size)
- Communication memory
- Requirements
- Steps required to configure the FRG Viewer
- Steps required to configure the Visu Viewer
- Steps required to configure the Cottus Viewer
- Steps required to configure the VNC Viewer
- Steps required to configure the ProViewer
- Steps required to configure the Web Viewer
- Steps required to configure the MPEG Viewer
- Steps required to configure the VTplus Viewer
- Launching Viewer
- Controlling Viewers
- VNC Viewer
- Explorer
- Starting the Explorer
- Explorer User Interface
- Object Tree
- Source Tree View
- Explorer workspace
- Explorer menu bar
- Help menu
- Remote Desktop menu
- Layout Selector menu
- Explorer tool bar
- Device Manager in the Explorer
- Explorer Context Menu
- Drag&Drop functionality
- Layout Editor
- Desktop Server
- Project Backup
- Command Interface
- Device command Interface
- Desktop command Interface
- Viewer command Interface
- Apollo Explorer command interface
- Apollo Layout Editor command interface
- Apollo Layout Selector command interface
- Apollo Remote Desktop command interface
- Apollo Database Convertor command interface
- Apollo Window Detector command interface
- Control Room Bus services
- Control Room Bus
- Serial command interface
- TCPIP command interface
- Application management
- License management
- Time synchronization
- Log file
- Security Provider
- Defining accessGroups
- Configuration of restricted objects
- Permissions
- Restrictions for regions
- Restrictions for layouts
- Restrictions for shortcuts
- Restrictions for advanced menus
- Window Properties|Description
- Window Properties|Sizable
- Window Properties|Always on Top
- Window Properties|Visible
- Edit|Invisible Windows
- Edit|Keyboardinput
- Edit|CommandLine
- Edit|Permissions
- Edit|SaveLayout
- Customized configuration and uninstallation of Apollo
- Soap API Service
- Appendix
- Hotline

12. Control Room Bus services
Barco – Apollo – DOC-3197-2 – user's manual – Revision 08 – November 2006
_________________________________________________
353/402
12.6 Time synchronization
All computers within one network have to have the same time. Use the Control Room Configurator
Control Room ConfiguratorControl Room Configurator
Control Room Configurator to specify
which computer is to be the clock server for all other Apollo network computers. Just set the Clock Server prop-
erty in the Custom Properties of the master in the Apollo database to True.
Now all Apollo network computers can be synchronized and set to the same time
12.7 Log file
All status and error messages are written to a file in order to check the system. This log-file is located in the
folder ..\ApolloProject\LOG.
The general syntax is as follows:
<class> <node> <task> <stamp> <module> <function>:<text>
class One character
m (message)
v (verbose)
r (error)
node Name of the computer or his IP address
task Name of application
stamp time (dd.mm.yy hh.mm.ss.mmm)
module Name of the module
function: Name of the function
text message
The general file name of the log file is <yyyy><mm><dd>.<no>. It includes the current date and a number be-
tween 000 and 999.
The log-files of all computers of the Apollo network are merged in the log-file on the master (control computer
of the Display Wall).
The file size is limited to 20MB. When this size is exceeded, entries are deleted according the sequence of gen-
eration, first the oldest ones.
12.8 Security Provider
The Apollo security mechanism is based on AccessGroups and restricted objects. Apollo allows configuring an
individual permission for every AccessGroup of every object.
The AccessGroups are configured with an ASCII editor. The restricted objects are configured dynamically via the
Permission command available in the Remote Desktop and in the Layout Selector.
Apollo assigns permissions to AccessGroups and not to individual users. A user is identified by his Windows login
name.
A user can be assigned to multiple AccessGroups. In case the respective AccessGroups have different permissions
on an object, the user assigned to multiple AccessGroups has the most significant permission given to one of
these AccessGroups.
Without any specific assignment, as default every user is assigned to the AccessGroup Everyone.