FUSION
Installation Guide
Version 1.0
Content
1.0 Introduction... 3
2.0 FUSION Server Software Installation... 3
3.0 FUSION Client Software Installation ... 10
4.0 FUSION NIM Software Installation... 16
Appendix A - Configuring MS Windows Server 2008 R2 for FUSION Server ... 23
Appendix B - Installing MS SQL Server 2008 R2 for FUSION Server ... 30
Appendix C - Configuring MS SQL Server Replication for FUSION Server ... 42
Copyright © Borer Data Systems Ltd. All Rights Reserved.
MIFARE® and MIFARE® DESFire® are registered trademarks of NXP B.V. and are used under license.
Borer Data Systems Ltd assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation.
Except as permitted by such licence, no part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Borer Data Systems Ltd.
All images, descriptive matter, specifications and advertising are for the sole purpose of giving an approximate description of the goods and copyrighted property of Borer Data System or/and their respective owners. E & OE all trademarks acknowledged.
1.0 Introduction
The software part of a FUSION system consists of three components:
1. Server software (including FUSION server, MS SQL Server and FUSION database) to provide a system data repository and carry out the system’s automated activities. Automated activities include downloading database updates to the Network Interface Modules (NIMs), uploading access events and status information from the NIMs and curbing log file size.
2. Client software (FUSION client) providing a user interface to the system.
3. Network Interface Module (NIM) software (including FUSION NIM, MS SQL Server and FUSION NIM database) to monitor and control the system’s card readers and other field devices,
downloading database information to them and uploading access events and status information from them.
Each of these components is installed via a FUSION installer program that is present on the FUSION Installation Disk.
To install FUSION Server or Client software use FUSION_Setup.exe.
To install FUSION NIM software use FUSION_NIM_Setup.exe.
2.0 FUSION Server Software Installation
Typically FUSION server software uses Microsoft SQL Server 2008 R2 for database management, although MS SQL Server 2005 is also supported.
MS SQL Server 2008 R2 requires the present of .NET v3.5 SP1, PowerShell v1.0 and Windows Installer v4.5 before it can be installed.
Installers for these packages are included on the FUSION Installation disk. FUSION server also requires support for web page hosting.
When configuring a computer that is running Microsoft Windows Server 2008 R2 to support FUSION, the server roles have to be set up to include .NET v3.5 SP1 and support for web page hosting. (There is no need to separately install PowerShell and Windows Installer).
Appendix A – ‘Configuring MS Windows Server 2008 R2 for FUSION Server’ contains information on how to configure MS Windows Server 2008 R2 to support FUSION server.
The FUSION Server installer can install MS SQL Server Express if required. MS SQL Server Express is suitable for most FUSION installations but it does have a limitation in the size of database supported (10GB in the case of MS SQL Server 2008 R2 Express) and does not include the SQL Server Agent service which carries out scheduled automated tasks such as back-ups and replication.
For larger systems, and systems where facilities such as replication will be required, ‘standard’ MS SQL Server 2008 R2 should be installed prior to installing FUSION Server, and when FUSION Server is installed the option to install MS SQL Server Express should be de-selected.
Appendix B – ‘Installing MS SQL Server 2008 R2 for FUSION Server’ contains information on how to install
‘standard’ MS SQL Server 2008 R2.
If a near-real-time back-up of the FUSION Server is required this can be achieved by installing FUSION Server in a second server and using MS SQL Server Replication to keep the databases on the two servers in balance.
Typically in this scenario the FUSION Clients and NIMs communicate with the main (primary) server during normal operation. Database changes are sent via MS SQL Server Replication to the back-up (secondary)
On recovery of the main server the NIMs automatically switch back to the main server. System operators can log back on to the FUSION database on the main server. MS SQL Server Replication detects any database changes (in particular card-holder access transaction information) that occurred in the back-up server database while the main server was offline and automatically brings the main server database back up to date.
Appendix C – ‘Configuring MS SQL Server Replication for FUSION Server’ contains information on how to configure MS SQL Server Replication to support a FUSION Server back-up.
To install FUSION Server run FUSION_Setup.exe on the FUSION Installation disk.
Press the ‘I Agree’ button at the bottom of the License Agreement.
Select FUSION (Full) installation. This will install the FUSION Client program (allowing user access from the server console), MS SQL Server, the FUSION database, the FUSION Server program and FireDaemon (a program which allows FUSION Server to run as a service so that the server can be left logged off). If MS SQL Server has already been installed prior to installing FUSION, untick MS SQL Server.
Select MS SQL 2008 R2 unless you wish to use MS SQL 2005. (The FUSION installer only enables the option to use MS SQL 2005 if it detects a 32 bit operating system).
Unless there is a need to install FUSION elsewhere use the default Destination Folder.
Wait while FUSION is installed.
If MS SQL Server is included as part of the installation various MS SQL Server installation windows and messages will appear as it is installed. User input is not required.
The following windows and messages are normal during an installation of MS SQL 2008 R2.
Once FUSION installation is complete, press ‘Finish’ to reboot the computer.
When the computer restarts one or more new icons will be present on the desktop.
Click on the FUSION icon to run the FUSION client program. The other icons will be present if the operating system is MS Windows Server 2008 / Vista or above. In these operating systems services such as FUSION Server communicate with a special service console which is not visible under normal circumstances.
To view the service console use the ‘Find Service Console’ shortcut once each time that the computer is restarted and then use the ‘View Service Console’ shortcut to view the service console whenever you
3.0 FUSION Client Software Installation
To install FUSION Client run FUSION_Setup.exe on the FUSION Installation disk.
Press the ‘I Agree’ button at the bottom of the License Agreement.
Select FUSION Client installation.
The FUSION Client installer can install SQL Server Express Client if required, although recent versions of Windows already include MS SQL Server Client connectivity as standard. Select MS SQL 2008 R2 unless you wish to use MS SQL 2005 (32 bit operating systems only). Select ‘Do Not Install SQL Server’ if you do not wish to install Windows MS SQL Server Express Client.
Unless there is a need to install FUSION Client elsewhere use the default Destination Folder.
Wait while FUSION Client is installed.
If MS SQL Server Client is included as part of the installation various MS SQL Server Client installation windows and messages will appear as it is installed. User input is not required.
Once FUSION installation is complete, press ‘Finish’ to exit from the installation program.
The following new FUSION icon will be present on the desktop.
Click on the FUSION icon to run the FUSION client program. Unless it has been installed on the computer that hosts the FUSION database FUSION client will not be able to connect to the FUSION database.
Click on the ‘Log In’ button to display the ‘FUSION Database Connections’ window. Press the ‘Manual ADO DB Connection’ button to display the database connection editor.
When providing the ‘MSSQL Server Name’ enter the name of the server that hosts the FUSION database followed by a ‘\’ character followed by the name of the MS SQL Server instance within which the database resides on that server.
Specify a ‘Database Name’ of FUSIONCORE, a ‘Database User Name’ of BORER and an appropriate password. Press the ‘OK’ button.
The FUSION Database Connections window will display the newly-created database connection settings.
FUSION client should now have a successful connection to the FUSION database.
4.0 FUSION NIM Software Installation
To install FUSION NIM software run FUSION_NIM_Setup.exe on the FUSION Installation disk.
Press the ‘I Agree’ button at the bottom of the License Agreement.
Select ‘NIM (FUSION SE)’ installation if the NIM software is to be installed as part of a FUSION SE system (i.e. in the same computer as FUSION Server has already been installed). Only the FUSION NIM database and the NIM program itself will be installed.
Select ‘NIM (Standalone)’ installation if the NIM is to run in a PC without FUSION Server present. This will install MS SQL Server Express, the NIM database, the NIM program and FireDaemon (a program which allows the NIM program to run as a service so that the NIM can be left logged off).
Select the FUSION Default SQL Server Instance name unless this is a FUSION SE installation and MS SQL Server was installed with a different instance name in which case select the ‘Custom’ radio button and enter the required instance name.
Select MS SQL 2008 R2 unless you wish the NIM to use MS SQL 2005. (The FUSION installer only enables the option to use MS SQL 2005 if it detects a 32 bit operating system).
Unless there is a need to install FUSION NIM elsewhere use the default Destination Folder.
Wait while FUSION NIM is installed.
If MS SQL Server is included as part of the installation various MS SQL Server installation windows and messages will appear as it is installed. User input is not required.
Once FUSION NIM installation is complete, press ‘Finish’ to reboot the computer.
When the computer restarts two new icons may be present on the desktop.
These icons will be present if the operating system is MS Windows Server 2008 / Vista or above. In these operating systems services such as the NIM service communicate with a special service console which is not visible under normal circumstances.
To view the service console use the ‘Find Service Console’ shortcut once each time that the computer is restarted and then use the ‘View Service Console’ shortcut to view the service console whenever you require to monitor the NIM service.
In the case of a standalone NIM, the NIM will initially be unable to connect to FUSION Server. To set up the connection it is first necessary to access the NIM program user interface. With versions of the Windows operating system prior to Windows Server 2008 / Vista this is done by double clicking the NIM icon in the icon tray at the bottom of the screen.
With more recent versions of Windows use the desktop ‘Find Service Console’ and ‘View Service Console’
shortcuts to access the user interface.
Press the ‘Server Link’ button to display the server connection configuration window.
Enter the IP address of the FUSION server and press the ‘PING’ button. If a connection is established a list of NIMs defined within the FUSION system will be displayed.
Click on the required NIM and press the ‘OK’ button.
The NIM will connect to FUSION Server.
Appendix A - Configuring MS Windows Server 2008 R2 for FUSION Server
Within Server Manager select ‘Roles’, then click on ‘Add Roles’.
Note the ‘Before You Begin’ information that is displayed.
Select ‘Application Server’.
Press the ‘Add Required Features’ button to confirm that .NET Framework 3.5.1 should be installed.
Select ‘Web Server (IIS)’ to add the web server role to the server.
Note the ‘Application Server’ information that is displayed.
Select ‘Web Server (IIS) Support’.
Press the ‘Add Required Features’ button to confirm that web server support should be installed.
Windows displays the following settings.
Note the ‘Web Server (IIS)’ information that is displayed.
Press the ‘Next’ button to select the default Web Server Roles.
Press the ‘Install’ button to begin the installation of server roles.
The selected roles are installed.
Appendix B - Installing MS SQL Server 2008 R2 for FUSION Server
When installing MS SQL Server 2008 R2 first run the set-up program on the MS SQL Server installation disk. Review the ‘Planning’ option (to the left of the Window) to confirm that your computer meets the required specification etc. and then select the ‘Installation’ option.
Select ‘New installation or add features to an existing installation’.
The installer will then carry out checks for anything within the computer’s environment that might cause a problem during installation.
The installer will prompt for the product key to be typed in.
Press the ‘Install’ button to install Setup Support Files.
The installer then carries out more checks for potential problems.
Select the ‘SQL Server Feature Installation’ radio button.
Press the ‘Select All’ button to select all available features.
The installer carries out more checks.
The installer will display the space requirements of the installation.
Select the service accounts for MS SQL Server to use. One option is to configure all the services to use the same account. To do this press the ‘Use the same account for all SQL Server services’ button.
You will be prompted to enter an account name and password. You can drop down the ‘Account Name’ box to select from the available built-in accounts (e.g. ‘NT AUTHORITY\NETWORK SERVICE’). The password does not have to be entered if a built-in account is selected.
Set the ‘SQL Server Agent’ and the ‘SQL Server Browser’ to start automatically. Leave the ‘Startup Type’
settings of the other services as default.
Select ‘Mixed Mode’ authentication and enter a suitable password for the administrator account. Press the
‘Add Current User’ button to add the current user to the list of SQL Server administrators. Use the ‘Add’
button if you wish to add any other users to the list of SQL Server administrators.
Press the ‘Add Current User’ button to add the current user to the list of Analysis Services administrators.
Select ‘Install the native mode default configuration’ as the required Reporting Services configuration mode.
If required tick the check box to send error reports to Microsoft.
The installer carries out more checks.
The installer is now ready to begin the installation.
The installer displays a Window showing its progress.
The installer displays the following Window on completion.
Press the ‘Start’ button and select ‘Programs’. Select ‘SQL Server Configuration Manager’.
Select ‘Protocols for MSSQLSERVER’ and enable ‘Shared Memory’, ‘Named Pipes’ and ‘TCP/IP’. Leave
‘VIA‘ unselected.
Appendix C - Configuring MS SQL Server Replication for FUSION Server
Primary Server – Configuring Replication Distribution
When installed and running, the MS SQL Server Replication Agents on both the primary and secondary servers will need to use a common domain account. On the primary server this account will be used by the Snapshot Agent to create snapshot files. On the secondary server the account will be used by the Merge Agent to read/write/delete these files. It is advisable to be logged on under this account while configuring Replication as at various points during the configuration the currently-logged-on account can be added to the required access lists, reducing the subsequent work required to get Replication working correctly.
When setting up MS SQL Server Replication the first component that must be configured is Replication Distribution. Configuration of MS SQL Server Replication Distribution is carried out on the primary server using SQL Server Management Studio.
Connect to the MSSQL instance that is used for the FUSION database.
Right click on Replication and select ‘Configure Replication’.
The Distribution Configuration wizard will be displayed.
Select the option to use this server as its own Distributor.
Use the default folder for the snapshot files that will be created by the replication process.
Use the default name and location for the distribution database.
Leave the ‘Publishers’ window with its default setting.
Select ‘Configure distribution’.
Check the choices that you have made are ok then press ‘Finish’.
On completion of the Distribution configuration press the ‘Close’ button.
Primary Server – Configuring a Replication Publication
After setting up Replication Distribution the next component that has to be configured on the primary server is a Publication. This will publish data from the FUSION database to a Subscriber which will be configured on the secondary server.
Using MS SQL Server Management Studio, right click on ‘Local Publications’ and select ‘New Publication’.
The New Publication wizard will be displayed.
Select FUSIONCore as the database to be published.
Select ‘Merge’ as the type of publication to create.
Select ‘SQL Server 2008’ as the SQL Server version that is to be supported.
All tables within the FUSION database except the ‘MQ_’ table are to be replicated. Tick the box to the left of
‘Tables’ to select all tables.
Untick the box to the left of ‘MQ_’.
Windows warns that new ‘Uniqueidentifier’ columns will be added to all tables within the database.
There is no need to set up filters so press ‘Next’.
Configure the Snapshot Agent to create a snapshot immediately and every 14 days.
Press the ‘Security Settings’ button to specify a user account under which the Snapshot Agent will run.
Select a domain account that can be used on both the primary and secondary servers. On the primary server this account will be used by the Snapshot Agent to create snapshot files.
On the secondary server the account will be used by MSSQL Replication to read/write/delete these files.
The selected account is displayed.
Select the ‘Create the publication’ checkbox.
Give the Publication a name and then press the ‘Finish’ button to create the Publication.
When the publication has been created press the ‘Close’ button.
The default MS SQL Server Replication Merge Synchronisation Schedule (the frequency with which the primary and secondary servers are balanced) is 60 seconds.
Typically FUSION systems run with a 10 second Merge Synchronisation Schedule. To change the schedule to 10 seconds right click on ‘Replication’ in the primary server and select ‘Distributor Properties’.
On the ‘General’ page, press the ‘Profile Defaults’ button.
Select ‘Merge Agents’ and press the ‘New’ button.
Select ‘Default Agent Profile’.
Give the new Agent a name and description and alter the ‘PollingInterval’ to 10 seconds.
Tick the checkbox to the left of the newly-created gent and press the ‘Change Existing Agents’ button.
Confirm that you wish to change existing Merge Agents to use the specified profile.
To implement the change reboot the server.
Secondary Server – Configuring a Replication Subscription
After setting up an MS SQL Server Replication Publication of the FUSION database on the primary server the secondary server must be configured. MS SQL Server needs to be installed on the secondary server and then a Replication Subscription can be set up.
A FUSION database will be created and populated from the FUSION database on the primary server as part of the subscription configuration. FUSION server (minus MS SQL Server and the FUSION database) can then be installed into the secondary server.
Configuration of a Replication Subscription is carried out in SQL Server Management Studio.
Right click on ‘Local Subscriptions’.
Select ‘New Subscriptions’.
The ‘New Subscription’ wizard is displayed.
Select ‘Find SQL Server Publisher’.
Connect to the MS SQL instance that hosts the FUSION database on the primary server.
Select to subscribe to the FUSION publication.
Select the ‘Run each agent at its Subscriber’ checkbox.
Select ‘New database’ to have the wizard create a FUSION database on the secondary server.
Specify FUSIONCore as the name of the database to be created.
The details of the subscription database (server name, MS SQL Server Instance name and database name) are displayed.
Windows user accounts under which the Merge Agent will operate must be provided.
The domain account that was specified when configuring the Snapshot Agent on the primary server should be used.
The selected Merge Agent Security settings are displayed.
Specify that synchronisation should run continuously.
Specify that a synchronisation should be carried out immediately to populate the newly-created subscription database with metadata and data from the FUSION database on the primary server.
Specify ‘Client’ as the Subscription type.
Request that the Subscription be created once the wizard is finished.
The Subscription details are displayed. Press the ‘Finish’ button to create the Subscription.
Press the ‘Close’ button when the Subscription has been created.
The secondary server is almost ready to have FUSION Server installed. By default the FUSION Client and Server programs access the FUSION database by using an MS SQL Server User called ‘BORER’.
This user must be added to the list of available users within the MS SQL Server Instance on the secondary server and then to the newly-created FUSION database.
To add the ‘BORER’ user to the MS SQL Server Instance, right click on ‘Logins’ within the MS SQL Server Management Studio and select ‘New Login’.
Set the ‘Login name’ to ‘BORER’, select ‘SQL Server Authentication’ and enter and appropriate password, untick ‘Enforce password expiration’ and ‘User must change password at next login’ and set the ‘Default database’ to ‘FUSIONCore’.
To add the ‘BORER’ user to the FUSION database expand the FUSIONCore database within the MS SQL Server Management Studio, right click on ‘Users’ and select ‘New User’.
Select a ‘User name’ of ‘BORER’, select the ‘BORER’ Login and tick all roles except ‘db_denydatareader’
and ‘db_denydatawriter’. Press the OK button.
It should now be possible to install FUSION Server, remembering to deselect ‘MS SQL Server’ and ‘FUSION Database’ when doing so as these are already present in the secondary server.
