Network Installation Instruction Manual

Network Installation Instruction Manual Version: 1.2.4 Date: 05.12.2012 CD LAB AG, Irisweg 12, CH-3280 Murten, Tel. +41 (0)26 672 37 37, Fax +41 (0)26 672 37 38 www.wincan.com

Table of Contents 1 Introduction... 4 1.1 Server with MS-ACCESS databases... 4 1.2 Server with MSSQL database... 5 1.3 Server with ORACLE database... 5 2 Checking the network environment... 6 3 Network license, prerequisites... 7 3.1 Hardware:... 7 3.2 Software:... 7 4 Network license, installation procedure... 8 4.1 Installation of the hardlock driver... 8 4.2 Installation of the hardlock server... 9 4.3 Installation of the Aladdin Monitor... 11 4.4 Installation of Aladdin DiagnostiX... 13 5 USB Device Server (USB to Network)... 15 6 Activation of the license... 15 6.1 Activation of the license file (VTC file)... 17 7 Installation on the Client-PCs... 20 7.1 Prerequisites... 20 7.2 Installation process... 20 7.2.1 WinCan8 Core installation... 20 7.2.2 WinCan8 main installation... 20 7.2.3 WinCan8 language installation... 21 7.2.4 Environment Variables... 21 7.2.5 Administrator rights for the installation folder... 22 8 MS-SQL server database... 23 8.1 System requirements... 24 8.2 Installing the software for MS-SQL databases... 24 8.3 Set up a WinCan user account... 24 8.4 Creating a new SQL project... 25 8.5 Adding an existing SQL project... 26 9 ORACLE server database... 27 9.1 System requirements... 28 9.2 Installing the software for ORACLE databases... 28 9.3 Set up a WinCan user account... 28 9.4 Adding an existing ORACLE project... 29 10 Result: Structured Workflow... 30 Page 2/42

Table of Contents 11 Appendix... 31 11.1 Windows 7: System Administrator... 31 11.2 Windows Server 2008 R2, 64 bit: Compatibility... 33 11.3 Windows Server 2008 R2, 64 bit: DEP... 34 11.4 Installation of MS-SQL-Server 2008, Express... 35 11.5 Initialisation of databases... 42 Page 3/42

Introduction 1 Introduction The Software WinCan8 has originally been developed for operation in a TV truck. Taking into account certain rules you also may run WinCan8 within a network domain. This documentation addresses to network administrators and resellers of the WinCan8 software. It describes 3 sustainable concepts of embedding PC workstations WinCan8 has been installed on into a network domain. 1.1 Server with MS-ACCESS databases This concept is based on a file server only. Once the survey is finished the WinCan8 projects are copied directly on the server hard drive and called up from the CLIENT computer in the WinCan8 project manager. Data stream fluctuations within the network can have a big influence on the speed when launching or reading your project data. The software module Meta-DB can additionally be installed on every CLIENT-PC and allows searching for inspection data within a larger group of projects (see documentation WinCan8_MetaDB). Page 4/42

Introduction 1.2 Server with MSSQL database This concept is based on a central MSSQL server database AND a file server storage of the media (photos, video clips etc.). Both items can physically be established either on the same or on two different machines. for 1.3 Server with ORACLE database This concept is based on a central ORACLE server database AND a file server media storage (photos, video clips etc.). Both items can physically be established either on the same or on two different machines. for All the 3 concepts mentioned require some tasks to be done prior to the launch of the WinCan8 software. The following chapters are going to describe in detail these tasks: Checking the network environment (IP addresses; firewall settings) Installation of the network dongle (network hardlock) Page 5/42

Checking the network environment 2 Checking the network environment Before you start any installation of a WinCan8 related software item within a network domain the network administrator as a responsible for the server operation will have to check the issues listed below: Defining the IP addresses of the client PCs and the server as a part of the same subnet as shown in the following example: SERVER: 192.168.1.1/255.255.255.0 (subnetmask=255.255.255.0) CLIENT: 192.168.1.5/255.255.255.0 (subnetmask=255.255.255.0) Unblocking of the communication port 3047 in the Windows Firewall. This has to be done on the SERVER as well as on the CLIENT side. 1. Open the Security Center in the Control Panel. 3. Select the item Windows Firewall. 4. Open the tab Exceptions and click on the button AddPort. 5. Unblock the port 3047 for both protocols TCP and UDP. If operating with either a MS SQL or an ORACLE server database you will have to unblock additionally one of the corresponding ports below: MSSQL: port 1433 ORACLE: port 1521 Page 6/42

Network license, prerequisites 3 Network license, prerequisites 3.1 Hardware: SERVER: Server with server operating system (Windows SERVER 2008/2003) Network-Dongle (USB Hardlock) from Aladdin Free USB port on the server CLIENT: See documentation WinCan8_Hardware_Software Requirement USB Device Server (depending upon the server environment): In case the server administrator has defined different virtual machines (e.g. VMWare with MORE than one host) the use of a USB Device Server connected to the real machine via Ethernet is recommended. The network dongle is finally plugged into that device. 3.2 Software: SERVER Windows SERVER 2008/2003 Licence query file (ALF file) that corresponds to the hardlock/dongle CLIENT Windows 7/VISTA or Windows XP, SP3 Oracle client software: version 10G or higher (in case of Oracle databases) Valid license file (VTC file) that corresponds to the hardlock/dongle and contains all the single licenses for WinCan8 modules needed. Hardlock driver: hldrv32.exe Hardlock server software: hlsw32.exe Hardlock monitoring software: aksmon32_setup.exe Hardlock diagnosis software: aksdiag32_setup.exe A VTC file used together with a network dongle contains licenses für 5 work stations per default. An license extension for up to 10, 15 or even 20 work stations is possible. Page 7/42

Network license, installation procedure 4 Network license, installation procedure Copy the files hldrv32.exe, hlsw32.exe, aksmon32_setup.exe and aksdiag32_setup.exe into a separate folder on the server hard drive (C:\HL_Software). Read the instructions on the pages 33 and 34 prior to the installation of these components on the server! 4.1 Installation of the hardlock driver Double click on the file hldrv32.exe to run the installation of the driver for the network dongle. First select the the installation language and follow the further instructions given by the wizard: Page 8/42

Network license, installation procedure Plug the Hardlock into a free USB port on the server. As soon as the hardware is recognized by the system, the red control lamp starts glowing. Copy the ALF file to the hard drive of the server into the folder C:\WINDOWS\system32 (32 bit) or C:\WINDOWS\SysWOW64 (64 bit). The name of this file (e.g. 5990.alf) must always correspond to the number of the Hardlock. 4.2 Installation of the hardlock server Double click on the file hlsw32.exe to run the installation of the hardlock server. First select again the installation language and follow the further instructions given by the wizard: Page 9/42

Network license, installation procedure Click on the button Next to install the hardlock server. For smooth operation the hardlock server needs the latest version of the hardlock driver. Older driver versions are automatically detected and replaced. Confirm with YES: Click on Finish to complete the installation: Page 10/42

Network license, installation procedure 4.3 Installation of the Aladdin Monitor Double click on the file aksmon.exe to run the installation of the Aladdin monitor. First select again the installation language and follow the further instructions given by the wizard: Page 11/42

Network license, installation procedure The files beeing replaced during the installation will be saved with the option Yes. In case of an unintentional uninstallation they can be retrieved: Click on the button Next to run the installation of the Aladdin monitor. Click on Finish to complete the installation: Page 12/42

Network license, installation procedure 4.4 Installation of Aladdin DiagnostiX Double click on the file aksdiag32_setup.exe to run the installation of the Aladdin diagnosis software. First select again the installation language: Click on the button Next: Accept the installation folder as suggested below and click on the button Next: Page 13/42

Network license, installation procedure The files beeing replaced during the installation will be saved with the option Yes. In case of an unintentional uninstallation they can be retrieved: Click on the button Next to run the installation of Aladdin DiagnostiX: Click on the button Finish to complete the installation: Page 14/42

USB Device Server (USB to Network) 5 USB Device Server (USB to Network) An additional hardware element like the USB Device Server allows you to run the network dongle independently from the Aladdin hardlock server. This is especially useful if the hardlock server has been installed within a virtual environment (e.g. VMWare). So the commands sent from the USB device can pass through the LAN via TCP/IP to the PC/Server. The use of the device type Silex SX-3000GB is recommended: Installation hints: The USB Device Server and its corresponding driver software must be installed on the server machine which the Aladdin hardlock server has already been installed on. The device must be configured as a service. So the network dongle will be available without any login. The corresponding software SX-Virtual Link as Service can be downloaded from the website of the manufacturer: http://www.silexeurope.com/de/home/support/produktgruppen/commondownloads/device-server-and-virtual-link.html. 6 Activation of the license This chapter is describing the licensing procedure step by step to get the license of WinCan8 activated for the whole network domain. Run the the Aladdin monitor on the server as shown below: Check whether the Hardlock Server Service has been activated: Page 15/42

Activation of the license The address of the corresponding software module must be added now. For WinCan you will need the module address 6428: Type this module address into the corresponding value field and click on the button Add to save the value. The new address appears in the left part of the window as a new item in the folder tree: Page 16/42

Activation of the license The module address 6428 appears as an additional icon linked to the current server. Click on the symbol to get the button Update displayed in the center of the window: If this button is NOT displayed the ALF-file either is corrupt or it has been copied into a wrong directory! 6.1 Activation of the license file (VTC file) The license file (VTC-file) contains all the information about the WinCan modules licensed for your dongle and must be activated first in order to make full use of the WinCan application from any of the CLIENT-PCs: Make sure that the VTC-file has been copied into a separate folder on the server hard drive (e.g. C:\WinCan8_License) and click on the the button Update in the Aladdin monitor window: Page 17/42

Activation of the license Delete the predefined entries (e.g. "0000167f.ctv") in the dialogue box that follows: Browse for the VTC file in the lower part of the dialogue (Write License Update (VTC) to Hardlock) and activate the option from file. Click on the button been put into: to search the folder on the server hard drive the license file has Select the VTC-file, click on the button Open and the path of the license file is displayed: C:\WinCan8_License\5990.vtc Click on the button Write Licence Update to continue with license update. Page 18/42

Activation of the license The information provided by the VTC-file are now sent to the server. Finally click on the button Done to complete the activation of the license file. C:\WinCan8_License\5990.vtc All the license information are now listet in the Aladdin monitor window: All the installation and settings required from the part of the server are completed now. Page 19/42

Installation on the Client-PCs 7 Installation on the Client-PCs 7.1 Prerequisites Check the following issues before installing WinCan8: The user on the target PC must be logged in as system administrator. When operating with Windows 7/VISTA this account has to be activated first (p. 31-32)! Download and installation of all the updates for your Windows operating system Installation of the latest driver version of the graphics board used Installation of the encoding card driver (VITEC card, MobileCap124 or other encoding cards supported as listed in the documentation WinCan Entry, page4) Installation of Microsoft.NET Framework 2.0, SP2 (already built-in in Windows 7/VISTA) Installationof Microsoft.NET Framework 4.0 Installation of Microsoft DirectX 9c or higher Installation of Windows MediaPlayer 11: (already integrated in Windows VISTA und Windows 7) 7.2 Installation process The WinCan8 installation files are present as so called setup packages that you will have to install one after the other. The installation must absolutely be performed in the correct order as described below: 7.2.1 WinCan8 Core installation Make sure that any local WinCan8 dongle is unplugged before starting the installation. Network dongles can be plugged in during the installation. Log in as system administrator, double click on the file icon shown above and confirm every step given by the wizard hitting the button NEXT until the dialogue with the button FINISH is popping up. RESTART your PC. 7.2.2 WinCan8 main installation Log in as system administrator and double click on the file WinCan8Setup that will launch the installation of the basical components of WinCan8. Page 20/42

Installation on the Client-PCs 7.2.3 WinCan8 language installation Double click on the LanguageSetup for your country. This will install all the specific items for pipe inspections used in your country (language files, damage catalogues, export interfaces ). for the United States of America for Great Britain for Australia for Singapore 7.2.4 Environment Variables The following hardlock related variables must be defined by a professional server administrator in the System Properties (tab Advanced) of each Client-PC or server (e.g. CIT- RIX) with a WinCan8 installation and a network license: Variable HL_SEARCH HLS_IPADDR Value IP IP address of the Aladdin hardlock server (p.16) Please refer to the Hardlock End Users Manual (p. 37-43) that can be downloaded from the website of the company ALADDIN (www.safenet-inc.com) to get more details about this issue. RESTART your PC; the installation of WinCan8 is finished now. Page 21/42

Installation on the Client-PCs 7.2.5 Administrator rights for the installation folder Always verify if the user has got administrator rights on ALL the subfolders and files of the installation folder C:\Program Files\WinCan v8 before launching the application. Right click on that folder, select the menu command Properties and check the settings as shown in the dialogue box below: The current user must have Full Control over the WinCan v8 installation folder! Double click on the WinCan8 desktop icon and open a project that has been copied on the server hard drive before. To run the application from a CLIENT-PC the license for WinCan Entry MS-Access must be activated in any case. The access to a MS-SQL or an Oracle database requires at least one additional license: Page 22/42

MS-SQL server database 8 MS-SQL server database This chapter is describing the installation procedure of WinCan8 in combination with a MS-SQL database. In the figure below you can see an overview of all the hard- and software items therefore needed: MS-SQL server database AND file server can be installed either on the same or on two separate machines. The MS-SQL server database is used to save the records of the WinCan8 database. The most important tables are listed here: P_T: Project table (i.e contractor, client ) S_T: Section table (i.e pipe shape, material, street, location, diameter ) SI_T: Inspection table (i.e operator, weather, date, time ) SO_T: Observation table (i.e OP code, observation text ) N_T: Node table (i. e. manhole data) NI_T: Node inspection table (i.e. manhole inspection data) NO_T: Node observation table (i.e. manhole observation data) NE_T: Pipes (i.e. Inlets and Outlets) linked to the manhole Please use the script create_wincan.sql saved in the WinCan8 installation folder C:\Program Files\WinCan v8\wincan\scripts to initialize the MS-SQL database (p. 42) The file server is used to save the files linked to the WinCan8 database. The most important file types are listed below: Subfolder Picture: contains picture files (*.jpg, *.gif, *.bmp) Subfolder Video: contains video files (*.mpeg, *.avi) Subfolder Template: contains the template files (*.wtp) Subfolder Inclination: contains inclination files (*.inc) Subfolder ScanExplorer: contains the folders and files created by the different pipe scanning systems Page 23/42

MS-SQL server database 8.1 System requirements SERVER: Windows Server 2008/2003 Microsoft SQL Server 2008/2005/2003/2000 (Professional version) OR Microsoft SQL Server 2005, Express (Freeware) CLIENT: Windows 7/VISTA, SP1; Windows XP, SP3 No special CLIENT-Software WinCan8; version 8.25.0.XXXX or higher 8.2 Installing the software for MS-SQL databases The MS-SQL Server software must be installed by a professional server administrator. In case of any troubles please refer to the Microsoft SQL installation help document. 8.3 Set up a WinCan user account To use the SQL database with WinCan8 at least 1 user account with administrator rights on the SQL server is needed: Create new database Add records Delete records Change records If you don t want ALL the users to have full control on the database you can set up different accounts on the server as shown in the following example: User 1: WinCan8_Admin Create new database Add new record Delete record Change record User 2: WinCan8_User Create new database Add new record Delete record Change record IMPORTANT: When creating user accounts always add the UNC path of the server hard drive containing the data (e.g. "\\server\projects") in order the users will be able to access them. Page 24/42

MS-SQL server database 8.4 Creating a new SQL project Open WinCan8 and create a new SQL project from the project manager that is displayed automatically: After you have started WinCan8 click on this button. Change the database type to Microsoft SQL Server. The names of the server and its instance must be entered in this way. Please ask your administrator. Define the path where the project data (i.e. templates, pictures, videos) will be saved. IMPORTANT: This drive must be a network drive where the WinCan8 users have full rights! Log in with the SQL user account having the permission to create the database on the server. Once you have filled in all required data click here. Page 25/42

MS-SQL server database 8.5 Adding an existing SQL project Open WinCan8 and add a new SQL project from the project manager that is displayed automatically: After you have started WinCan8 click on this button. SQLServername\Instance Type the name of the SQL server. Unless you are using the default instance type "/" followed by the name of the instance Log in with the user account that has got the right to access the SQL-database. When you have entered all the required data click here to confirm. Page 26/42

ORACLE server database 9 ORACLE server database This chapter is describing the installation procedure of WinCan8 in combination with an ORACLE database. In the figure below you can see an overview of all the hard- and software items therefore needed: ORACLE server AND file server can be installed either on the same or on two separate machines. The ORACLE server database is used to save the records in the WinCan8 database. The most important tables are listed here: P_T: Project table (i.e contractor, client ) S_T: Section table (i.e pipe shape, material, street, location, diameter ) SI_T: Inspection table (i.e operator, weather, date, time ) SO_T: Observation table (i.e OP code, observation text ) N_T: Node table (i. e. manhole data) NI_T: Node inspection table (i.e. manhole inspection data) NO_T: Node observation table (i.e. manhole observation data) NE_T: Pipes (i.e. Inlets and Outlets) linked to the manhole Please use the script create_wincan_oracle.sql saved in the WinCan8 installation folder C:\Program Files\WinCan v8\wincan\scripts to initialize the ORACLE database (p. 42) The file server is used to save the files linked to the WinCan8 database. The most important file types are listed below: Picture: Contains picture files (*.jpg, *.gif, *.bmp) Video: Contains video files (*.mpeg, *.avi) Template: Contains the template files (*.wtp) Inclination: Contains inclination files (*.inc) ScanExplorer: Contains the files created by pipe scanning systems Page 27/42

ORACLE server database 9.1 System requirements SERVER Windows Server 2008/2003 ORACLE Server CLIENT Windows 7/VISTA, SP1; Windows XP, SP3 ORACLE Client, version 10G or higher WinCan8, version 8.25.0.XXXX or higher 9.2 Installing the software for ORACLE databases The ORACLE Server software must be installed by a professional server administrator. In case of any troubles please refer to the ORACLE Server installation documentation. Download the software package Oracle XE Express Client (version 10g) from the website www.oracle.com. Install the package OracleXEClient.exe on the PC which you want to access the oracle database from. 9.3 Set up a WinCan user account To use the ORACLE database with WinCan8 you need at least 1 user account with administrator rights on the oracle server: Create new database Add records Delete records Change records If you don t want ALL users to have full control on the database you can set up different accounts on the server as shown in the following example: User 1: WinCan8_Admin Create new database Add new record Delete record Change record User 2: WinCan8_User Create new database Add new record Delete record Change record IMPORTANT: When creating user accounts always add the UNC path of the server hard drive containing the data (e.g. "\\server\projects") in order the users will be able to access them. Page 28/42

ORACLE server database 9.4 Adding an existing ORACLE project In an ORACLE database environment the professional database administrator is usually the ONLY one that creates NEW databases. The users connect directly to these databases to add them to the project list of the WinCan8 Project Manager: After you have started WinCan8 click on this button. Type = ORACLE Server SID = TNS string USERNAME = Database name PASSWORD = Database name IMPORTANT: Always write the whole Oracle TNS string into the field SID. The string can be found in the file tnsnames.ora located in the ORACLE installation folder. The example below is giving you an idea how such a TNS string may look like: (DESCRIPTION= (_LIST=((PROTOCOL=TCP)(HOST=)(PORT=1521))) (CONNECT_DATA=(SID=)(SERVER=DEDICATED)))) Page 29/42

Result: Structured Workflow 10 Result: Structured Workflow Once a central server database (MS-SQL or ORACLE) has been established by the server administrator all the CLIENT PC within the same network domain will be able to access it via WinCan8. Thus data integrity is guaranteed: Each record updated during a pipe inspection job must be merged into the central database and is ready for further data processing done by other users. The model below is showing the most important jobs that are running in a centralized way: Filtering: Pipe data can be filtered in WinCan, exported as separate WinCan projects and distributed to the operators in the TV-trucks. Merging: Once the pipe sections have been (re)inspected from the TV-truck the data are transmitted to the staff in the office where they will have to be merged with the WinCan replicator into the central database. Printing: In case of immediate use of certain pipe data you may search them in the central database and print the data directly via the WinCan Docu-Center or send them as a PDF file via e-mail. Exporting: As an alternative to printing the data provided by the central database can also be distributed and burnt directly on DVD or exported in a special file format (TXT, XML, MDB). Page 30/42

Appendix 11 Appendix 11.1 Windows 7: System Administrator During the first installation of Windows 7/VISTA you will have to assign yourself an administrator account to finish the installation procedure properly. However this administrator is NOT the system administrator. Only the latter one has got all the rights to access certain system components used during software installation. Proceed as follows to activate this system administrator: Right click on the desktop icon Computer and select the menu command Manage: Open the subfolder USERS in the category Local Users and Groups. Right click on the User named as Administrator (system administrator) and select the command Properties: DEACTIVATE the option Account is disabled in this panel (so the account will be enabled!) Page 31/42

Appendix Set a password for further LOGIN as system administrator and confirm this one. Remove the default user that had to be defined during the installation of Windows from the group of administrators. Close all the dialogue boxes and restart your PC. It is possible from now to log in as system administrator. You must log in as system administrator to install WinCan8 as well as all the other additional software modules! After the activation of the system administrator on a CLIENT-PC you must remove this computer temporarily from the domain before installing WinCan8. Otherwise the system administrator might in some cases be affected by restrictions defined by the domain controller and WinCan8 will NOT be installed properly! If WinCan8 has NOT been installed as system administrator Windows 7/VISTA will block certain events in the WinCan8 application when launching/using the software for the first time. Proceed as follows to repair this: Activate the system administrator Browse to the folder C:\Users\[Current User]\AppData\Local\VirtualStore. Look for a program folder named as \WinCan v8 or for WinCan related files that are automatically put in this VirtualStore subfolder after a first launch of WinCan8. Delete any WinCan8 related entry in the subfolder VirtualStore OR rename it (e.g. WinCan v8_old). Finally restart your PC. Log in as system administrator and install WinCan8 again. Device drivers must first be completely uninstalled and then reinstalled. Page 32/42

Appendix 11.2 Windows Server 2008 R2, 64 bit: Compatibility If the server is operating with the system Windows Server 2008 R2, 64 bit you will have to change the properties of the installation file hlsw32.exe before you install the hardlock server: Right click on the installation file hlsw32.exe and select the command Properties in the context menu. Open the tab Compatibility in the dialogue box and check the corresponding options as shown below: Activate the compatibility mode for Windows XP, SP3. Activate this privilege level. Confirm with the button OK and run the installation of the hardlock server (Source: www.logiboard.at/blogs/support-ecke/item/39-hardlock-server-unter-windows-server-2008-r2-verwenden) Page 33/42

Appendix 11.3 Windows Server 2008 R2, 64 bit: DEP If the Data Execution Prevention (DEP) has been activated for all programs and services under Windows Server 2008 R2, 64 bit you will have to set the hardlock server service as an exception. Open the Control Panel, click on the System icon and continue as illustrated below: C:\windows\system32\hls32svc.exe C:\windows\system32\hls32.exe C:\...\HL-Server\HLS32SVC.exe C:\...\HL-Server\Hls32.exe 32 bit 64 bit (Source: www.logiboard.at/blogs/support-ecke/item/39-hardlock-server-unter-windows-server-2008-r2-verwenden) Page 34/42

Appendix 11.4 Installation of MS-SQL-Server 2008, Express This chapter is describing the installation of the software SQL Server 2008, Express. Please download the package SQL Server 2008 Express with Advanced Services, SP2 (256 MByte) that also contains the Management Studio Express as well as some additional tools. Double click on the file SQLEXPR_ADV.EXE to launch the installation. Follow the installation wizard until you see the dialogue shown below. Make sure that the option Hide advanced configuration options is activated: Click on the button Next and select the 4 items highlighted in the dialogue that follows: Click on Next to continue Page 35/42

Appendix Select the option Mixed Mode (Windows Authentication and SQL Server Authentication). The SQL Server Authentication is required to connect to the server from WinCan8. Click on Next Activate both options Select the preferred Error and Usage Report Settings. Page 36/42

Appendix Configuring SQL Server 2005 Express Edition Next, we will make some configurations in the SQL Server 2005 Express Edition. We will make all these settings in the SQL Server Configuration Manager which can be launched as follows. Make sure that there is a remote connection to SQL Server 2005: 1. Select the category Protocols for SQLExpress on the left. 2. Right click on TCP/IP and select Enable: SQL Server 2005 Express Edition is using dynamic ports per default. To prevent blocking of these ports during a restart of the PC we have to reconfigure the SQL Server in order to use static ports in the future. 1. Select SQL Server 2005 Network Configuration Protocols for SQLExpress 2. Doubleclick on TCP/IP 3. In the tab Protocol make sure that Listen All is set to Yes. Select the tab IP Addresses go to the type category IPAll and type a free port number into the field TCP Port. If this is the only instance of SQL Server on the current PC use the standard SQL port 1433. If you use another port please mind that you will need to replace the value at other places accordingly. Page 37/42

Appendix Restart SQL Server 2005 Select the category SQL Server 2005 Services in the left column Right click on the item SQL Server (SQLEXPRESS) and select Restart Configure firewall The port that SQL Server listens to needs to be open. In this guide, we are using the standard SQL port 1433. Under Windows XP (SP3) the firewall can be configured as follows: 1. Open the Security Center in the Control Panel. 3. Select the item Windows Firewall. 4. Open the tab Exceptions and click on the button AddPort. 5. Unblock the port 1433 for both protocols TCP and UDP. Page 38/42

Appendix Configurations in SQL Server Management Studio Express In following steps are describing how to set a user account and how to configure the SQL Server Management Studio Express: In this dialog first select the server you just have installed and click on Connect. Create a user account to use with WinCan v8 Right click on [PCName]\SQLExpress\Security\Logins and select New login. Page 39/42

Appendix Select the category General and enter the data as described below: Create a Login name (e.g. "wincan8") Select the option SQL Server authentication and set a password (e.g. "wincan8") Uncheck these three options Default database = master Select the category Server Roles and activate ALL the items listed on the right part: Page 40/42

Appendix Select the category User Mapping and activate the options shown below for the master database: Connecting to SQL Server 2005 from WinCan8 Launch WinCan8 and create a new project using the following data: Project name: Source Server: [any] [IP of Server PC],[SQL Port]\SQLExpress Example: 192.168.254.71,1433\SQLExpress Database name: [same as project name by default] User: Password: "wincan8" "wincan8" Page 41/42

Appendix 11.5 Initialisation of databases When creating projects directly from the WinCan8 application that are based on MS AC- CESS the corresponding tables are created and saved automatically in the project database whereas MS-SQL or ORACLE databases are empty at the beginning. In order the users are able to access a database structure based on MS-SQL or ORACLE this one must be initialised first by a professional server administrator. 1. Import the initialisation scripts listed below into the server database: For MS-SQL: C:\Program Files\WinCan v8\wincan\scripts\create_wincan.sql For ORACLE: C:\Program Files\WinCan v8\wincan\scripts\create_wincan_oracle.sql These scripts will create all the tables that WinCan8 needs for data entry 2. Open the project table P_T in the server database and add the fields listed below: P_Path P_Name P_Language P_DefTemplateSection P_DefCatalogSection P_DefTemplateSat P_DefCatalogSat P_DefTemplateMH P_DefCatalogMH Page 42/42