4.1???One PC??? Installation or first

4.2.1Preparations before installation...15

7.2Installing the CP 6001 Chip Card

7.6.1Command line parameters for the CUA 37

7.6.2Command line parameters for the CDA 38

7.7.1Command line parameters for the

ECA 39

8.2Upgrading procedure (using old

8.3Upgrading procedure, change of

8.3.1Upgrading from SQL 2005 Server

9.2.1Problems un-installing the SW 6000

9.2.2Un-install SQL 2008 Express Server 45

10.2.1Connect string for the SQL Server 46

Installation Manual SW 6000 ver 6.2.docx

2 Introduction

This manual describes how to design a DCS 6000 Conference system using the SW 6000 Software Packages, how to install the SW 6000 Software Packages and how to setup the system for running the first time.

This document does however not describe the use of the applications like i.e. the CUA and CAA in details. Please consult the relevant manuals for this.

2.1Minimum Requirements

The minimum requirements for a PC running an application are:

???Min. Pentium 1.5GHz

???Min. 2 GB RAM

???Min. 10GB HD

???CD-ROM drive

???USB port if CP 6001 Chip Card Programmer is to be used

???TCP/IP network connection

???VGA screen. Please refer to the User Manuals for the SW 6000 applications for information on minimum resolution.

2.2Compatibility

The SW 6000 Software version 6.2.xx is only compatible with DCS 6000 Firmware Release 7.5.0 and higher.

If the DCS 6000 system is an earlier release, an upgrade of the system is needed. Please consult your DIS Partner for information about updating your system.

2.3Supported Operating Systems

SW 6000 Software v6.2 support standard installations* of the following operating systems

???Windows 7 (32 bit and 64 bit)

???Windows Server 2008,, 2008 R2 and 2012 R2

???WIN 8.1 x86 Enterprise/Professional/Standard

???WIN 8.1 x64 Enterprise/Professional/Standard

Important: Windows XP operating system is NOT supported

*Please notice that cloned operating systems are not considered a standard installation. Clones may cause problems with duplicate SIDs causing the MSDTC to fail. Clones should therefore be used with caution and only by experienced IT people.

2.4SW 6000 CD-ROM & Web- site

The SW 6000 Software, Prerequisites and User Manuals are available on www.dis.cc after login in as a Partner.

2.5User Manuals

The use of the applications is found in the following manuals:

???User manual CAA Conference Administration Application

???User manual CUA Conference User Application

???User manual CDA Conference Display Application

???User manual ECU External Control Application

3 System design

Prior to installing the software the system has to be designed, as the SW 6000 Software Package gives options for all in-between a small installation with one PC and a large installation with more than 1000 PCs.

3.1.1Applications

The SW 6000 Software Packages consists of 4 main applications

???CUA - Conference User Application

???CAA - Conference Administrator Application

???CDA ??? Conference Display Application

???ECA - External Control Application

and the interface application for establishing the connection to the CU 6005/6011/6105/6110:

???CUI ??? CU Interface

An application for backing up data and restore data is also part of the package:

???SW6000 Backup Utility

The conference data (Delegate names, Conference names etc.) is stored in one of the following database installations:

???SQL - Microsoft SQL 2005 server Express

???SQL - Microsoft SQL 2008 server Express

???SQL - Microsoft SQL 2000 server, Enterprise Edition or Standard Edition

???SQL - Microsoft SQL 2005 server, Enterprise Edition or Standard Edition

???SQL - Microsoft SQL 2008 server, Enterprise Edition or Standard Edition

The SQL - Microsoft SQL 2008 server Express is delivered as part of the SW 6000 package

3.2Installation design

The CDA, CUI, CUA, CAA and ECA applications can all be installed on the same PC or all on separate PCs, but this is normal procedure.

For performance reason the CUI should be installed at the same PC/Server as the database.

Before installing the applications the design of the system has to be decided.

The following schematics are showing various system designs with SW 6000 applications. The abbreviations shown above are used in the schematics:

3.2.1One PC System Design

3.2.1.1Chairman or Technician control

3.2.2Installation with Multiple PC???s

3.2.2.1Chairman & multiple Delegates

3.2.2.2Chairman & Technician control including Display and External control

3.2.2.3Chairman & Delegates control >10 PCs

The following installation procedure describes how to install the SW 6000 Software on a PC in a design as described in the section ???One PC System Design???.

Important: This installation is also recommended to use to install on the Server/PC, where the database is to be placed in a multi-PC system.

The following installation procedure describes how to install the SW 6000 Software on multiple PC???s in designs as described in the section ???Installation with Multiple PC???s???.

4.2.1Preparations before installation

Before you start the installation of the SW 6000 Software Package you must ensure that the following preparations have been done:

???Ensure that you have LAN TCP/IP connection at the PC???s. Assign a permanent or automatic IP address

???If you use more than one PC in the system Windows 7/Server 2012 please note that there are some built in Windows errors, which have to be corrected before running SW 6000. See sub-section ???4.2.2 Windows Corrections???.

???Install touch screen driver if using touch screen for the CUA

???Disable the firewall as default. If it is necessary to enable the firewall please follow the instructions in the sections ???4.2.3 Additional Firewall settings??? and ???4.2.4 Message Queuing settings???.

4.2.2Windows Corrections

If you use more than one PC in the system and are using Windows 7 or Server 2008/12 please note that there are some built in Windows errors, which have to be corrected before running SW 6000. The next sections show the corrections to be made

1.Enable MSDTC to allow the network transaction. To do this, follow these steps:

a.Click Start.

b.In the Search programs and files text box, type dcomcnfg.exe, and then click Enter.

c.In the Component Services window, expand Component Services, expand Computers, expand My Computer, and then expand Distributed Transaction Coordinator.

d.Right-click Local DTC and click

Properties.

e.In the Local DTC Properties dialog box,

click on Security tab.

f.Click to select the Network DTC Access check box.

g.Under the Transaction Manager Communication group, click to select the Allow Inbound check box. To allow the distributed transaction to run on this computer from a remote computer.

h.Under the Transaction Manager Communication group, click to select the Allow Outbound check box. To allow the distributed transaction to run on a remote computer from this computer.

i.Under the Transaction Manager Communication group, click to select the

No Authentication Required option.

j.In the Local DTC Properties dialog box, click OK.

2 Configure Windows Firewall to include the MSDTC program as an exception. To do this, follow these steps:

a.Click Start.

b.In the Search programs and files text box, type Firewall.cpl, and then click Enter

c.In Windows Firewall dialog box, click

Allow a program or feature through Windows Firewall.

d.In the Allowed Programs dialog box, click

Allow another Program???. If button is not enabled then click Change Settings first

e.In the Add a Program dialog box, click the Browse button, and then locate the

Msdtc.exe file. By default, the file is stored inthe<Installation drive>:\Windows\System32 folder.

f.In the Add a Program dialog box, click

Add.

g.In the Allowed Programs dialog box, Select Microsoft Distributed Transaction Coordinator Service and check all check box???s

h.In the Allowed Programs dialog box, click

OK.

6 Getting started

The system has now been installed successfully.

The following sections describe the necessary steps to get started. However please refer to the CAA User Manual, the CUA User Manual and CDA User Manual for a throughout description of how to use the SW 6000 System.

6.1Steps

1.Connect the CU 6005 or CU6011 Central Unit to the PC, where the CUI is installed, with a RS232 cable or connect with TCP/IP if CU 6105 or CU 6110 are used.

2.Turn on the CU with all units (Delegate Units, Chairman Units, AO units etc.) connected.

3.Start the CU Interface Application (CUI).

If the CUI version is not compatible with the database you will be advised to start the CAA to automatically update the database. You will then have to restart the CUI.

When the CUI Application starts to communicate with the CU it will receive information for all units connected to the CU. The CUI Application will then create one seat in the Seat assignment table for each Chairman Unit and Delegate Unit, numbering the seats, starting at one and counting upwards.

Hint: To make is easier later to assign delegates to seats and to make Mimic diagrams the seats should be renumbered to give a more logical order.

4.Start the Conference Administration Application (CAA). If needed the Database will be upgraded automatically.

Assign computer names for each of the seats where there is a PC on the network that will run the Conference User Application (CUA).

6.Select the Mimic screen from the ???Setup/Configuration/Mimic Configuration??? and create a new Mimic diagram.

Creating a Mimic diagram requires the user to import a bitmap showing the room or hall as a background image and then to import all seats onto the Mimic

diagram and position the coloured dots representing a microphone or seat.

7.Select the User Type screen from the ???Setup/User Type??? and create additional user types (e.g. Vice Chairman) to be used when creating the list of Delegates and to be used as defaults for the seats when no one is logged in. The user types that are created during installation can either be modified or deleted (the Chairman and Delegate user type can be modified but not deleted).

The User Type determines individual microphone settings, screens, buttons and functions that will be available when a user is logging into the CUA.

A User Type is also associated with each seat to determine the settings that must apply as default when no one is logged in.

and assign a user type to each of the seats to be used as a default when no one is logged in.

9.Select the ???Delegates??? screen and type in information for the various users of the system.

It is possible to enter any additional information required for delegates in up to four customisable fields.

10.Selectthe ???Setup/Configuration/Delegate List Configuration??? and configure the width of the various fields on the delegate lists.

11.Select the ???Setup/Language/Languages??? and create additional system languages if

needed (English is created during installation).

12.Select the ???Setup/Language/Labels??? to create translations for the languages that have been added. If some or all labels are not translated then the default language translation (English) for a particular label will be used.

13.Select the ???Setup/Language/Labels??? and chose the English tab and select label 40 and change ???Plenary Hall??? to a description, which applied for your installation

14.Select the ???Message??? screen and create messages.

15.Select ???Setup/Configurations/CDA Configuration and change (if needed) Font Size, Colours etc. for the various CDA screens available.

16.Select ???Conference???

17.Add a conference

18.Fill in a proper name for the conference.

19.If chip cards or login using code are not in use select ???Prepared Delegate List???.

20.Select the preferable ???Microphone Operation Mode??? and preferable ???Voting Parameters??? (both ???Microphone Operation Mode??? and ???Voting Parameters??? can be changed at any time during the conference???

21.Change Start and Stop date if needed.

22.Click update

23.Select ???Delegate List

24.Select the delegate who is to be placed in Seat 1 and click >>

28.Click Update and close the Delegate List screen

29.Select Agenda and fill in an Agenda for the Conference

30.Select Options and select the default options for this conference

31. Click Update

Hint: If the conference created is supposed to be the default for future conferences then click ???Save as Default???

The system is now ready for use, however it is strongly recommended to read the User Manuals for Applications.

7.3Customer Logo

The DIS logo in the CUA application can be exchanged with a customer logo.

Do the following:

1Open the file "CUA logo background.bmp" with a graphics-editing program like ???Paint???.

The file is found on the SW 6000 CD-ROM in the folder ???SW6000 Accessories\Customer logos???.

The image in the file has the same colour as the default background for the CUA application.

The image size is 214x162 pixels and the new logo must have the same image size.

7.4Creating Database Connections

If your CUA or CAA application on the PC shall have access to more databases you must check the checkbox ???Create Hall Definitions??? when prompted during installation of the CUA, CAA.

During the installation of SW 6000 software, if the ???Create Hall Definitions??? checkbox is selected, it is time to set the hall definitions, the following window will appear.

Figure 7.4-A Create Database Connection

Inside the window there is a grid with 4

computer, where the CUI is installed (and database).

There are 6 buttons at the bottom of the window.

1.???Delete??? button will delete the current row in the grid.

2.???Save??? button will save all row present in the grid to Windows registry.

3.???Cancel??? button will cancel any changes made to the Database Connections.

4.???Close??? button will close the window.

5.Create ConnectionString??? button is used to create a ConnectionString for the current row on the grid. When this button is pressed, a new window ???Figure 7.4-B Generate Connection String??? pops up.

a.Data Source Type - Select if the database is SQL Express or SQL.

DIS Digital Conference System

b.Name of the computer where SQL Server is installed - Insert the name of the Computer running the CUI and database

Figure 7.4-B Generate Connection

String

c.Default database instance name - The default value is SW6000

d.Default database name - The Database Name is the name of the database we wish to connect. The names are limited to SW6000-1, SW6000-2, SW6000- 3, and SW6000-4.

e.Default database time out - The default database timeout is the timeout value for the connection established

7.5License file

A licence file is needed for running the SW 6000 Software. Even if it might be possible to run functionality and/or application which are not licensed for, it is illegal in accordance with the License Conditions.

A licence file includes the serial number of the CU 6005, CU 6010, CU 6011, CU 6195 or CU 6110 and is delivered from DIS in a zipped format like this example ???SW6000 license v5.5 CU xxx.xxx.xxx 2012-05-08.zip???, where xxx.xxx.xxx is the serial number of the CU for which the licence file is created.

Before the license file can be used it must be un-

zipped. The name of the un-zipped license file is SW6000 License.xml and must not be changed.

User Manual

f.Database user - Default value used during installation of SW 6000

g.Database user password -Please note if the database is MDSE then the password has to be changed to HmAeC2k. For SQL 2008 Server the password is HmAeC2005

i.When the selections has been made click ???Make ConnectionString???.to create the connection string. Use the ???Test Connection??? button to test the connection string.

ii.Close the window and proceed filling in information and create connection string for all the connections.

h.Click ???Make??? to generate the connection string.

i.???Test Connection??? button will validate the Connection String created

j.Click ???Close??? button to close the window.

???Test Connection??? button will validate whether the ???Connection String??? on the current row in the grid can be used to successfully connect to the database.

Note: The licence file ???SW6000 License.xml??? is located in the CUI execute directory (C:\Program Files\ DIS\CU Interface Application).

If no license file is found, the license file is invalid or the license is expired this will be displayed using a message box on the PC running the CUI interface and a system message will also be sent to CUA computers that have system message monitoring capabilities.

Important: Connection to the CU is needed for the license to be checked and hence the operation of said SW. If the CU is not connected and therefore the licence file is not checked the CAA can be started and access the Database info such as the seat table but all of the licensed features would be greyed out and unavailable.

If you have a previous SW 6000 version already installed using the SQL 2005 Server

Express and want to use the SQL 2008 Server Express, you can upgrade as follows.

The SW 6000 Applications can be un-installed using the windows ???Control Panel??? and selecting ???Add or Remove programs???.

The name of the installation is ???SW6000???.

9.2Un-install SW 6000 Databases

When the databases (SW 6000-1, SW 6000-2, SW 6000-3 or SW 6000-4) has been installed using the SW 6000 Setup, the databases will not be

removed, when removing the SW 6000 Application using ???Add or Remove programs???.

The Databases are removed in the following way.

If the SW 6000 Applications have been removed before the SW 6000 databases are removed or the above procedure for removing the SW 6000 Databases fails the databases can be removed in the following way:

Delete the folder C:\Program

Files\DIS\SW6000 Database

After deleting the database the SQL 2008 server has to be un-installed and installed again, if SW 6000 has to be re-installed.

Important: Remember to make backup of the databases before deleting them. When the databases are removed all conference data is lost.

10.1Database

To use the SW 6000 applications you need a database. The database contains all data used by the application such as delegate names, microphone information etc. etc.

When installing the SW 6000 software a database will be created with initial data.

The ???SQL Database Engine??? hosts all databases.

These SQL servers can host the database for SW 6000:

Microsoft SQL 2000 server, Enterprise Edition or Standard Edition

Microsoft SQL Server 2005 Express

Microsoft SQL Server 2005

Microsoft SQL Server 2008 Express

Microsoft SQL Server 2008

If you are planning to use ???Microsoft SQL Server 2008??? it must be preinstalled on the computer before you install SW 6000. If you are planning to use ???Microsoft SQL Server 2008 Express??? you can use the set-up on SW 6000 CD-ROM.

???Microsoft SQL Server 2008??? is not part of the SW 6000 software package.

The data in the database is not secured in any way. If you want to secure your data, you must contact your database administrator and change the connect strings used by the applications accordingly. For a description of connects strings see Connect string.

10.2.1Connect string for the SQL Server

For the SQL server the value of the connect string will typically have a value similar to the following: -

Provider = SQLOLEDB.1;Initial

Catalog=SW6000-1;Data

Source=SQLSERVERCOMPUTER;uid=sa;

The ???Provider??? determines how the application should access the database. In this case OLEDB is used ??? which is installed when installing MDAC 2.6.

The ???Initial Catalog??? is the name of the database to connect to; this will most likely be SW6000-1.

The ???Data Source??? will be the name of the computer on which the SQL server is running.

The ???uid??? is the user id to be used by the application when connecting to the database. This will most likely be the default system administrator name ???sa??? but it depends on how the SQL Server is installed. If you add security to the SQL Server you might change this to more appropriate value, and for example add a password to the Connect string. If you do please note that this password will be public to anyone with access to the registry on the client- machines.