For西安万华PcVue 12SnapVue_Installation guide - 1f

ARC Informatiqueis certifiedISO 9001: 2000 SNAPVUE - INSTALLATION GUIDE Abstract: This document is containing information about the installation process. Its a guide for Referents and Testers.Keywords: Installation, Snapvue, User guide, Last modification: 21/12/2017SNAPVUE - Installation guidePage 25/25Reference: Last modification: 21/12/2017AUTHORIZATIONNameStampDateWritten byLLW16/10/2016Editing byANMI18/10/2016Authorization byREVISION HISTORYRevisionAuthorActionEditingDateDistribution1aLLWCreatedANMI16/10/2016Internal for review1bLLWModifiedANMI,YAMI,NK24/10/2016Internal for review1cLLWModifiedANMI, YAMI,NK,Abdul28/10/2016Internal for review1dLLWModified20/10/2017Internal for review1eLLWModifiedANMI27/11/2017Internal for review1fLLWModifiedANMI21/12/2017Internal for reviewTable of Contents1.Introduction51.1.Object51.2.Document description52.References and terminology62.1.Reference documents62.2.Applicable documents62.3.Definitions63.Installation of SnapVue (V12)73.1.Install Prerequisites73.1.1.Install prerequisites of V11.273.1.2.Install prerequisites of V1274.Configuration of IIS84.1.Configure IIS85.SSL certificates95.1.Create a certificate95.2.Install the certificate96.SnapVue start-up rules14 1. Introduction1.1. ObjectSnapVue is compatible with the Mobility server based on PcVue V12 and on PcVue V12 itself. Since the installation of V12 has not been created yet, we need to describe a procedure to install the current SnapVue version manually. The development of SnapVue is in progress, therefore many things may be changed in the future. This document shall thus be referenced in current period as a technical requirement of a project.1.2. Document descriptionThe document is split into 4 main sections:- Installation of SnapVue (V12)- Configuration of IIS.- Creation of SSL certificate for the Mobility Server- SnapVue start-up rules.The examples given in this document are based on the Windows Server 2012 R2.2. References and terminology2.1. Reference documents2.2. Applicable documents 2.3. Definitions3. Installation of SnapVue (V12)This chapter is dedicated to describe the installation process of the SnapVue infrastructure. SnapVue will be compatible with all operating systems that are suitable for V12. In this document we just focus on Windows Server 2012 R2, the installation process on any other operating system will be similar.Taking an Operating System as Windows Server 2012 R2. Verify that the system is clean and more recently possible, because our objective is not to make a qualification for install of V12, this is just to build one good environment for SnapVue Demo. .1. Install Prerequisites and configuration IISV12 requires installing the same prerequisites as V11.2 as well as some new prerequisites for new features of V12. Here is a procedure of install prerequisite of V12. Downloading the install prerequisite of V12 from intranet file share: lugversionsPcVue12.0_testOnly12.0.00008_Prerequisites_Standalone.zip Or LugversionsDevBuilds12.0Prerequisites (Qualification ftp). it include the following packages:- .NET Framework 4.7- SQL Server 2016 SP1 Feature Pack - Visual C+ Redistributable for Visual Studio 2017Downloading from intranet file share: LugversionsDevBuilds12.012.0.00008_Beta_PcVue.isoLaunching it. If IIS in your OS is not installed properly, the installer will propose you to configure it automatically. Answer yes and wait until it is finished. Dont worry if it takes some time, at the end you will have a message to confirm that it is done correctly.Following the install process till the end. Now, you can see that all web applications were created in IIS, as followsFollowing the step as:1. Take the latest BIN of V12 (ContextVue) from the directory: lugversionsDevBuilds12.012.0.00000.xxxxx_Dev_Redistributable in our ftp server (Qualification login), where xxxx is the build number of the BIN version.2. Copy this BIN into the folder ARC InformatiquePcVue 123. Start the “PcVue 12 Components registration” tool whit his shortcut, which is located in desktop.4. If you are in this step, it means the last version PcVue V12 is ready to launch. 4. SSL certificatesIn theory, the final user needs to buy a certificate from officially trusted Certification Authorities. We have performed the necessary tests to confirm that this approach works. However, for the tests or demo projects, we will use “self-signed” certificates instead of purchasing the valid certificate. 4.1. Create a certificateThere are several tools that can create a “self-signed” certificate. Here, we will use two ways to do it:1) Using IIS method ( Create Self Signed Cerrtificate, see the following detailed information:a) Click on “TEST-WS12R2 (TEST-WS12R2Dev)” and “Server Certificates” see following image.b) Following the previous action, click on the “Cerate Self Signed Certificate” action to open a “Create Self Signed Certificate” dialog box and put the necessaire parameters . See the following image:c)d) Click on “DefaultWebSite” on the left panele) Click on “Bindings” to open the “Site Binding” dialog box.f) Click on the button “Add” to add new site binding. See following image:g) Click on the button “OK”. Your Self Certificate is created. 2) Using the tool “OpenSSL”.First of all you will need to install theOpenSSL software. It allows you to generate private key and the certificate itself. You can download it from the following link: /products/Win32OpenSSL.htmlOn the bottom, you should find the latest normal version for Windows 64bitin the list. Download it and install with the default settings.You can find the file which is named “Create.BAT” and is location in DevBuilds12.0 in our ftp server. Put it in the “C:OpenSSL-Win64Bin” directory, for example, and run it. The program will ask you several questions in order to create a certificate. Here is an example of the answers:Country Name (2 letter code) AU:FRState or Province Name (full name) Some-State:IDFLocality Name (eg, city) :SEVRESOrganization Name (eg, company) Internet Widgits Pty Ltd:ARC INFORMATIQUEOrganizational Unit Name (eg, section) :DEMONote that theCommon Name must be identical to thehostname ofyour server (it can be anIP address)Common Name (e.g. server FQDN or YOUR name) :0 Email Address :After these question you will be asked to create a password for accessing this certificate and the RootCA.PFX file will be created in the “OpenSSL-Win64/BIN” directory.. Install the certificateIn order to install the created PFX file to your IIS server, follow these steps:1. Double click on the rootCA.pfx file2. Select the Local Machine option3. Enter thepassword for the pfx file4. Put a flag to mark the key as exportable: 5. It is important to Place this certificate into the Trusted Root Certification Authorities. This allow your applications to trust this certificateNow, you must associate the HTTPS traffic with your certificate, as follows:1. Click on “TEST-WS12R2 (TEST-WS12R2Dev)”, see following image.2. Select the Server Certificates in the panel and click on the “Open Feature” action. See following image:3. Following the previous action, click on the “Import” action to open a “Import Certificate” dialog box. Select the PFX file created by OpenSSL and select the following parameters:4. Click the “OK” button. Verity that the certificate is imported successfully. See following image:5. Click on “DefaultWebSite” on the left panel6. Click on “Bindings” to open the “Site Binding” dialog box.7. Click on the button “Add” to add new site binding. See following image:8. Choose Https protocol and select your certificate in the combobox, as follows:9. Click “OK”Attention:- If you use the Demo VM from Franois, you must adapt your host network setting and the WiFI access setting. For example: Demo VM address : 4 Host IP address :192.168.92.XX (XX not 34 or 254) with gateway 54. WiFi access address: 54.Because the created certificate is depending the address IP of Demo VM. 5. SnapVue start-up rulesBefore lunching your SnapVue project, you have to do the following:1. You need to create the file “Exprimental.ini” and edit it on notepad including these lines only.2. Copy this file to the directory C:ARC InformatiquePcVue 12ETC.ContextualMobilityEnabled=13. Lunch the service “svMobileServicesHost.exe” and “svInstantMessagingHost.exe” (if you want to use this feature) located in the following directory: C:ARC InformatiquePcVue 12Bin. It is useful to create a shortcut in order to run it easily late.See following image:4. Install the APK (for android) or IPA (for iOS) on your smartphone. The package must be compatible with the version of V12 BIN.Pay attention to: To avoid the confusion, uninstall the previous versions of SnapVue, TouchVue or WebVue NT. You just need to install the com.sv.migelo.apk (SnapVue under Android OS). Dont install another apks, except you need to play TouchVue or WebVue NT. About iOS version, for the moment, you need to ask Anton in order to obtain the version and installation guide.5. Verify that your dongle has the SnapVue license. 6. Before playing SnapVue, you must to do three things as following Click on WebVue&Web Services Toolkit to add Web Server. Once you have finished, you have to restart ContextVue (V12). See following image: Please configure the PropertyServerClient to not use the classic PropertyServer.client.config file. This setting can be enabled by putting the “EnableFileBasedPropertyServerClientConfiguration” flag in the web.config files of the WebServices to False:FalseThis must be done for RealTimeAlarm-, RealTimeData- and HistoricalDataService. If this flag is set to true an automated configuration mechanism by .net remoting is used and in this case we can not take care of the object lifetime by ourselves. Means that the .net remoting connections are only freed if the Application Pool is recycled and this can take up to 20 minutes in the default configuration. Enable WebSocket Protocol in Windows 2012 server. See following image and following step below:Open “Server Manager” Click on “Manage” in the right corner”