Barco Apollo User guide

User’s manual

S

CENARIO MANAGEMENT

Doc-3366-2

DOC-3366-2, Current Version

Title: APOLLO SCENARIO MANAGEMENT – User’s Manual

ID-no.: DOC-3366-2

Revision: 03

Date: October 06

main issue update

chapter 1

chapter 2

chapter 3

chapter 4

chapter 5

chapter 6

chapter 7

new: The corresponding chapters are new or completely revised.

corr.: Passages of the corresponding chapter were corrected; see modification bars.

add.: Passages of the corresponding chapter were added; see modification bars.

This manual refers to following software versions

Apollo Scenario Management Release 1.1

Apollo Release 1.9

Document History

Modifications, which result in a new version, are indicated by a vertical bar.

Trademarks

Brand and product names mentioned in this manual may be trademarks, registered trademarks or copyrights of

their respective holders. All brand and product names mentioned in this manual serve as comments or examples

and are not to be understood as advertising for the products or their manufacturers.

Die Weitergabe sowie die Vervielfältigung aller Unterlagen, die von uns überlassen werden, deren Verwertung

und Mitteilung ihres Inhaltes an Dritte ist nicht gestattet, soweit dies nicht ausdrücklich zugestanden ist.

Urheberrechte, insbesondere auch solche an Software, werden nur insoweit übertragen, als es für die Erreichung

des speziellen Vertragszwecks erforderlich ist. Zuwiderhandlungen können zu Schadensersatz verpflichten. Alle

Rechte aus der Erteilung eines Patents oder der Eintragung eines Gebrauchsmusters verbleiben bei uns.

recorded, transmitted or stored in a retrieval system without the prior written consent of BARCO.

Guarantee and Compensation

BARCO provides a guarantee relating to perfect manufacturing as part of the legally stipulated terms of

guarantee. On receipt, the purchaser must immediately inspect all delivered goods for damage incurred during

transport, as well as for material and manufacturing faults. BARCO must be informed immediately in writing of

any complaints.

The period of guarantee begins on the date of transfer of risks, in the case of special systems and software on

the date of commissioning, at the latest 30 days after the transfer of risks. In the event of justified notice of

complaint, BARCO can repair the fault or provide a replacement at its own discretion within an appropriate

period. If this measure proves to be impossible or unsuccessful, the purchaser can demand a reduction in the

purchase price or cancellation of the contract (redhibition). All other claims, in particular those relating to

compensation for direct or indirect damage, and also damage attributed to the operation of software as well as

to other services provided by BARCO, being a component of the system or independent services, will be deemed

invalid provided the damage is not proven to be attributed to the absence of properties guaranteed in writing or

due to the intent or gross negligence on the part of BARCO.

If the purchaser or a third party carries out modifications or repairs on good delivered by BARCO, or if the goods

are handled incorrectly, in particular if the systems are commissioned or operated incorrectly or if, after the

transfer of risks, the goods are subject to influences not agreed upon in the contract, all guarantee claims of the

purchaser will be rendered invalid. Not included in the guarantee coverage are system failures which are

attributed to programs or special electronic circuitry provided by the purchaser, e. g. interfaces. Normal wear as

well as normal maintenance are not subject to the guarantee provided by BARCO either.

The environmental conditions as well as the servicing and maintenance regulations specified in this manual must

be complied with by the customer.

Revision sheet

To:

• BARCO Control Rooms GmbH

An der Rossweid 5, D-76229 Karlsruhe

Phone: +49-721-6201-0, Fax: +49-721-6201-298

E-mail: docu.de.bcd@barco.com, Web: www.barcocontrolrooms.com

From:

Date:

Please correct the following points in this documentation (DOC-3366-2):

page wrong correct

Contents

1 Introduction........................................................................................................................................ 1-1

1.1 How this manual is organized ....................................................................................................................1-2

1.2 Styles and symbols......................................................................................................................................1-2

2 Summary ............................................................................................................................................2-1

2.1 General.........................................................................................................................................................2-2

2.2 Terminology.................................................................................................................................................2-3

2.3 Samples of applications ..............................................................................................................................2-4

2.3.1 Startup problems (relative time).......................................................................................................2-4

2.3.2 Begin and end of a shift (absolute time)..........................................................................................2-4

2.4 Realization ...................................................................................................................................................2-4

3 Installation ......................................................................................................................................... 3-1

3.1 System requirements ..................................................................................................................................3-2

3.2 Requirements ..............................................................................................................................................3-2

3.3 Used ports....................................................................................................................................................3-3

3.4 Installation of the Scenario Management software ..................................................................................3-4

3.4.1 Common settings................................................................................................................................3-4

3.4.2 Server side installation (Scenario Executor)......................................................................................3-8

3.4.3 Client side installation (Scenario Configurator).............................................................................. 3-16

4 The Scenario Configurator.................................................................................................................. 4-1

4.1 Launching the Scenario Configurator..........................................................................................................4-2

5 The Scenario Editor ............................................................................................................................ 5-1

5.1 Creating a new scenario..............................................................................................................................5-2

5.2 Editing a scenario ........................................................................................................................................5-2

5.2.1 Actions.................................................................................................................................................5-5

5.2.2 Trigger .............................................................................................................................................. 5-24

5.2.3 Timeline ........................................................................................................................................... 5-31

6 Use cases ............................................................................................................................................ 6-1

6.1 Overview......................................................................................................................................................6-2

6.2 Use case: Operation mode of a display wall..............................................................................................6-4

6.2.1 Day shift..............................................................................................................................................6-5

6.2.2 Night shift ...........................................................................................................................................6-6

6.2.3 Switch Projector lamp off...................................................................................................................6-7

6.3 Use case: change active lamp.....................................................................................................................6-8

6.3.1 Upper lamp switching ........................................................................................................................6-8

6.3.2 Lower Lamp Switching .......................................................................................................................6-9

6.4 Use case: scan viewer .............................................................................................................................. 6-10

6.5 Use case: automated alarm response ..................................................................................................... 6-11

7 Troubleshooting ................................................................................................................................. 7-1

7.1 How to check for the ScenarioApiServer....................................................................................................7-2

7.2 How to remove a Java Web Start Application............................................................................................7-2

7.3 Tomcat service setting: Allow service to interact with the desktop.........................................................7-4

7.4 Log files........................................................................................................................................................7-4

7.5 Hot Line........................................................................................................................................................7-5

1. Introduction

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

1-1

1 Introduction

This chapter explains the structure of the manual itself and the used typographic styles and symbols.

1. Introduction

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

1-2

1.1 How this manual is organized

This section explains the structure of the manual itself and the used typographic styles and symbols. Safety

information is provided concerning the operation of computer systems from BARCO.

• Introduction

gives an overview about the used styles and symbols.

• Summary

gives an overview about the functionality of the Scenario Management software

• Installation

shows system requirements and explains the necessary steps and components of the installation

• Scenario Configurator

introduces the Scenario Configurator and explains its user interface

• Scenario Editor

explains the user interface of the Scenario Editor and the shows how to edit scenarios

• Use cases

gives same samples of scenarios

• Hotline

informs where to get support in case problems occur.

Chapters, pages, figures and tables are numbered separately. Chapters are indicated by a »point syntax«, e. g.

4.2.3, pages by a »dash syntax«, e. g. 2-1, as figures and tables are, e. g. figure 5-4.

1.2 Styles and symbols

The typographic styles and the symbols used in this document have the following meaning:

Bold Labels, menus and buttons are printed in Bold font.

Condensed

Links to both other chapters of this manual and to sites in the Internet are printed

condensed. In the on-line version of this manual all hyperlinks appear teal.

Courier Names of files and parts from programs are printed in the Courier font.

Courier bold Inputs you are supposed to do from the keyboard are printed in Courier bold font.

The sheet icon indicates additional notes.

Next to this icon you find further information.

This arrow marks tips.

Next to this icon you find important notes.

2. Summary

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

2-1

2 Summary

This chapter gives an overview about the functionality of the Scenario Management software.

2. Summary

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

2-2

2.1 General

The Scenario Management software is based on the Apollo API. It is a mechanism to define and execute

sequences of Apollo functions, thus providing a simple, end-user accessible way of programming the Apollo

system.

These sequences of commands are called scenario.

Scenarios are defined by the user. The execution of the scenarios is triggered by events coming from various

sources and received via the API (e.g. user actions, time of day, etc.).

To define scenarios, the Scenario Management software provides a configuration user interface.

The configuration user interfaces also allows to start/stop scenarios and to monitor the execution of the

scenarios.

The user interface as front end (client side) of the Scenario Management software is called Scenario

Configurator.

The back end (server side) is called Scenario Executor.

2. Summary

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

2-3

2.2 Terminology

A scenario is consists of a list of actions, a list of triggers, and a schedule. The schedule is called Timeline. The

scenario is an XML file saved on the ScenarioApiServer.

A scenario can be addressed by the scenario executor only if the scenario is loaded.

When a scenario is loaded, it can be edited: actions as well as triggers can be added or modified or removed,

or the timeline can be modified.

A scenario can be user controlled (timeline set to manual) or time-controlled (time line different from

manual).

In case of a user controlled scenario, starting the scenario is requires clicking on the Start button in the Scenario

Editor, cf. The Scenario Editor. The scenario then runs as soon as it is triggered.

In case of a time-controlled scenario, starting the scenario happens at is startup time defined in the timeline.

The scenario then runs as soon as it is triggered. (Manual intervention by clicking the Start button has no effect

until the startup time defined in the timeline is the current time (but then of course it starts if the Start button

has been clicked or not)

A scenario stops as soon as all commands of the list are executed (provided there is no loop which makes them

start again).

It also stops in case its duration time has passed.

The user can stop it manually by clicking on the Stop button in the Scenario Editor, cf. The Scenario Editor. To make

it running again, the Start button has to be clicked. However it is mandatory that re-start happens during its

Duration time, otherwise it won't have any effects.

The Duration time is the time where a scenario is sensitive for triggers. Duration time is an absolute time and

prevents conflicts causing from e.g. system failures. If the server shuts down and is restarted, the scenario

executor will resume the scenario only when it is still due to be active (duration time not over).

The execution of a scenario pauses when the current action in the list of actions is a Pause or Wait action, but

the triggers will still remain active.

In case of Pause, execution of the actions is resumed as soon as a trigger fires.

In case of Wait, execution of the action is resumed as soon as the wait time defined has passed.

User controlled scenario Time controlled scenario

Loading

Operator (via user interface or via

commandline)

Starting Start button Schedule

Running When started, and a trigger fires When started, and a trigger fires

Duration time Duration of one cycle Defined in the timeline

Shut down time When the once cycle is over Defined in the timeline

Stopping

When one cycle is over, or when the stop

button has been clicked (manual

intervention).

Only when the duration time is over (if

the active state of a scenario is still

pending, it cannot be stopped manually)

2. Summary

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

2-4

2.3 Samples of applications

2.3.1 Startup problems (relative time)

Some applications require some time to initialize before the next action can start.

This problem can be solved by creating a scenario which allows the next action to take place only after some

time the application has been launched.

2.3.2 Begin and end of a shift (absolute time)

The requirements during night may be different from the requirements during day with respect to active size of

the wall and/or applications running on the wall.

These requirements can be met by a scenario which runs at a fixed time of the day (e.g. 6 PM) and which

switches off parts of the wall, unloads the "day layout" and loads the "night layout". – In the morning, another

scenario resets the control room into day operating status again.

2.4 Realization

The Scenario Management software is a kind of client to the Apollo API and is implemented in Java to be

independent from the operating platform. Therefore it is mandatory that Apollo and Apollo API are installed on

the server workstation of the Scenario Management back end, i.e. on the workstation of the Scenario Executor.

The user interface for defining scenario is a web start application delivered from the Apache Tomcat Server which

hosts the Scenario API.

It can run on every machine where the Java runtime environment is installed.

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-1

3 Installation

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-2

3.1 System requirements

Since the Scenario Management software requires Apollo and Apollo API, the system

requirements are the system requirements for Apollo.

3.2 Requirements

• Windows 2000 Service Pack 4 or later

• Internet Explorer 6.0 SP2 or later

• Windows Scripting Host 5 or later

• Hot Fixes and Customizations (according to Barco TASK-2k-09a for TransForm A controller)

• Windows XP Professional Service Pack 2 or later

• Internet Explorer 6.0 SP2 or later

• Windows Scripting Host 5 or later

• Hot Fixes and Customizations (according to Barco TASK-XP-09a for TransForm A controller or RTASK-XPDP-09

for TransForm A DualXeon)

• Barco Snmp RcAgent 1.6SR1 (for device control)

• Barco Windows driver suite 4.2 (for TransForm A controller)

• Funk Software Inc. Proxy Host 5.1 (for Cottus viewer), Gateway 5.1

• VNC 4.1.2 (for VNC viewer)

• TightVnc 1.2.9 (for VNC viewer)

• Microsoft Visio2000 or higher (for Apollo Configurator)

• Microsoft Visual Studio 6.0 SP4 (for software development)

• Windows Media Player 9

• Barco OCM 1.2 for OverView D projection modules

When running the viewers, please keep in mind that each instance of a viewer requires

about 20MB to 30MB RAM. Upgrade your TransForm A controller accordingly!

You need administrative privileges to install the Apollo software. If the computer reboots during installation,

users have to log in with administrative privileges after the reboot as well.

When installing, please stick to the following installation sequence: OS level first

(Windows2000 WindowsXP), then system level (Windows Driver Suite, Barco RC Agent),

finally application level (Apollo, RemotePointer, Screen Host)

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-3

3.3 Used ports

Apollo will use the following ports:

Application ports

Control Room Bus TCP/IP ports: 4570 and 4571

CottusViewer / Proxy Host UDP port: 1505

CottusViewer /Gateway UDP port: 2303

VncViewer / VncServer / TightVncServer TCP/IP port: 5900

ProServer / ProViewer / RemotePointer TCP/IP port: 4580

TCP/IP Command interface TCP/IP port 4585

SnmpMngr TCP/IP port 4701

RcAgent TCP/IP port 4700

OCM TCP/IP port 6063 and 4702

With Windows XP SP2, the firewall is automatically activated and all ports are closed! Make

sure to open the above mentioned ports! Without being able to communicate, Apollo will

not work!

Please check also if an external firewall is installed. No matter what type of firewall:

Apollo can only operate when the ports listed above are open.

Consult the user documentation about your firewall how to open the ports.

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-4

3.4 Installation of the Scenario Management software

In case there is already a version of this software installed on the system, first de-install

the old version: Select Start|Control Panel|Add or Remove Programs|Barco Scenario

Management

3.4.1 Common settings

The following steps have to be performed on the server workstation as well as on the client workstation.

• Host configuration

• Modification of the power management settings

3.4.1.1 Host configuration

To adapt the host file, it is mandatory that you know the IP addresses of the ApolloApiServer and of the

ScenareioApiServer.

In case you know the names of the workstation but not the IP addresses, you can find them out using the PING

command:

• Select Start|Run and enter CMD.

• In the command prompt, enter the following command: PING NameOfWorkstation

• The ping commands return the IP address of the workstation:

By means of the PING command, not only the IP address is returned, but you are also

informed that the workstation is running and connected to the network.

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-5

To perform the host configuration

• navigate the folder C:\Windows\System32\drivers\etc.

• Use Notepad to edit the file hosts, and add the following lines:

IP Address apolloapiserver

IP Address scenarioapiserver

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-6

3.4.1.2 Power management settings

Select Start|Control Panel|Power Options.

• Set the power scheme of hard disk and system as Never, and close the dialog.

Now the network adapter has to be configured:

• Select Start|Control Panel|System.

• Activate the tab Hardware, and click on the button Device Manager.

• Navigate and then right click on Network adapters.

• From the context menu, select Properties.

• Activate the tab Power Management

• Uncheck the option "Allow the computer to turn off the device to save power"

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-7

After the host file has been modified and the power management options have been set, the system has to be

restarted!

Restart the system to apply the modifications!

3. Installation

Barco – Apollo Scenario Manager – DOC-3366-2 – user's manual – Revision 03 – October-2006

____________________________________________________________

3-8

3.4.2 Server side installation (Scenario Executor)

For the log files, addititional 100MB of free space are required, cf. Log files!

Make sure that Apollo has been installed, either the Apollo operator workstation or the

Apollo desktop server.

Also the Apollo API has to be installed. (Mandatory: the Internet Information Service is

installed and configured, and the local users IWAM and IUSR have been assigned the

respective rights.

To learn more about the installation of Apollo and the Apollo API, cf. Apollo user's manual,

doc -3197-2.

To check the correct installation of Apollo and the Apollo API, use the tool VerifyAPI.exe provided on the Apollo

CD-ROM:

• Navigate to the folder Apollo (CRS-3045)\Apollo 1.9\API

• Double click on VerifyAPI.exe

The verification tool launches and checks the configuration. If everything is ok, after several instances it shows

the build of the Apollo Software.

In a second step you can click on the button "List Desktops". The tool will look for all desktop servers of the

related Apollo project and lists them. The entries of the list can be viewed opening the list box:

Provided Apollo and Apollo API have been installed and configured according the installation instructions as

described in the Apollo user's manual, the installation of the Scenario Executor requires the following steps:

• Installation of the Java Runtime Environment 5.0 (version 1.5.0_07)

• Installation of Apache Tomcat Server version 5.5.17

• Unpacking of Systinet4Tomcat.zip

• Installation of Scenario Manager

Page is loading ...

Barco Apollo User guide

Barco Apollo User guide

Related papers

Other documents