Dell Wyse Management Suite Version 1.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................4 High availability overview.................................................................................................................................................. 4 2 High availability architecture..........................................................................................................................
1 Introduction Wyse Management Suite version 1.3 is the next generation management solution and enables you to configure, monitor, manage, and optimize your Dell Wyse thin clients. This helps you to deploy and manage thin clients on a high availability set-up with improved performance. It offers advanced feature options such as cloud versus on-premises deployment, manage-from-anywhere by using a mobile application, and enhanced security such as BIOS configuration and port lockdown.
2 High availability architecture The Dell Wyse Management Suite architecture consists of Windows Server 2012 with failover cluster enabled. The Windows cluster contains a main computer that supports other applications and ensures minimum downtime by harnessing the redundant. This is used for application failover for Tomcat, Memcache, MQTT services. MongoDB database cluster helps in the event of primary database failure the secondary database will take over.
The hardware and software requirements to set up high availability for Wyse Management Suite version 1.3 are: Table 1. System requirements Product Port Protocol Description Microsoft Windows Server 2012 R2 • • Minimum disk space—40 GB • Minimum number of systems—2 Server where Wyse Management Suite is hosted.
3 High availability on Windows Server 2012 A failover cluster is a group of independent systems that increases the availability and scalability of clustered roles. This feature supports multiple workloads running clusters on hardware or on virtual machines. A failover cluster is a group of systems that are independent and increases the availability and scalability of clustered roles. The clustered servers are the nodes that are connected to one another as a network.
3 Right-click Roles and then select Configure Role to display the High Availability Wizard screen. Figure 3. High availability wizard 4 Select Generic Service and then click Next to view the Select Service screen. Figure 4. Select service 5 Select Dell WMS: Tomcat Service and then click Next. NOTE: You can add the Wyse Management Suite version 1.3 related services to the cluster only after you install Wyse Management Suite version 1.3.
Figure 5. Confirmation 7 Click Next to complete the process. 8 To add other Wyse Management Suite services as part of the cluster, launch Failover Cluster Manager, and then go to ActionsRoles to display the network name that you have created. 9 Click on the network name, and go to Add ResourceGeneric Service.
4 Achieve high availability on Windows Server 2012 The following are the steps to achieve high availability on Windows Server 2012: 1 Add failover cluster feature on Windows Server 2012—see Adding failover cluster feature on Windows Server 2012. 2 Create file share witness—see Create file share witness. 3 Configure cluster Quorum—see Configure cluster Quorum. 4 Create clustered roles—see Create cluster roles.
Figure 7. Select server destination 4 Select the server where you want to enable the failover cluster feature and then click Next. 5 Select Failover Clustering on the Features screen, and then click Next. After you enable the failover cluster on the servers, open the Failover Cluster Manager on the server at Node 1. 6 Click Yes to confirm installation, and enable the failover cluster feature on the selected server.
Figure 8. Failover cluster manager 8 Click Select servers or cluster and then click Browse to configure the servers. 9 ClickNext and select Run all tests from the Testing Options screen.
Figure 9. Testing options 10 Click Next. The Confirmation screen is displayed with the list of selected servers.
Figure 10. Confirmation 11 Click Next. The Summary screen is displayed with the failover cluster validation report.
Figure 11. Test summary details 12 Click View Report to check the report. If the status is Passed, you can proceed with the next step. If the status is Failed, you must fix the errors before you proceed with the next step. NOTE: The Create Cluster Wizard screen is displayed if there are no validation errors. 13 Click Next and type a name for the cluster in the Cluster Name field and then select the IP address of the system. 14 Click Next and the Confirmation screen is displayed.
9 Click Close to exit. Configure cluster quorum settings The cluster configuration database, also called the quorum, contains details as to which server should be active at any given time in a cluster set-up. To configure the cluster quorum settings, do the following: 1 In Microsoft Windows Server 2012, click Start to open the Start screen and then click Server Manager to launch the Server Manager dashboard.
Figure 13. Select voting configuration 6 Click Next . Select Configure a file share witness from the Select Quorum Witness screen. 7 Click Next and then type the share path in the File Share Path field from the Configure a file share witness screen. Figure 14. Configure file share witness 8 Click Next . TheSummary screen is displayed with the configured quorum settings.
Figure 15. Summary of the quorum settings 9 Click Finish to complete the quorum settings. Creating clustered roles After you create the failover cluster, you can create clustered roles to host cluster workloads. Ensure that Wyse Management Suite is installed on the servers and point to the remote database before you create clustered roles.
Figure 16. High availability wizard 4 Select Generic Service and then click Next to view the Select Service screen. Figure 17. Select service 5 Select Dell WMS: Tomcat Service and then click Next. NOTE: You can add the Wyse Management Suite version 1.3 related services to the cluster only after you install Wyse Management Suite version 1.3.
Figure 18. Confirmation 7 Click Next to complete the process. 8 To add other Wyse Management Suite services as part of the cluster, launch Failover Cluster Manager, and then go to ActionsRoles to display the network name that you have created. 9 Click on the network name, and go to Add ResourceGeneric Service.
5 Achieve high availability for MySQL InnoDB The following steps explain how to achieve high availability for MySQL InnoDB: 1 Check MySQL InnoDB server instance—see Create MySQL InnoDB cluster. 2 Add server or node to MySQL InnoDB—see Adding server or node to MySQL InnoDB cluster. 3 Create MySQL Router—see Creating MySQL Router High availability with MySQL InnoDB The MySQL InnoDB cluster provides a complete high availability solution for MySQL.
Figure 19. MySQL command prompt • • • To check that the MySQL InnoDB is created on all the three cluster nodes, run the following commands at the command prompt: mysql-js> dba.checkInstanceConfiguration('root@IPAddress1:3306') mysql-js> dba.checkInstanceConfiguration('root@IPAddress2:3306') mysql-js> dba.checkInstanceConfiguration('root@IPAddress3:3306') Create a cluster instance for MySQL InnoDB After you have installed MySQL InnoDB instance on the servers, create a cluster instance.
Figure 21. Confirmation screen Add server instance to MySQL InnoDB cluster You must add server instance to the MySQL InnoDB cluster as primary or secondary. Do the following to add a server instance to the MySQL InnoDB cluster: 1 Login as DB Admin user from the command prompt. 2 Run the following command to add a server instance to the MySQL InnoDB cluster: cluster.addInstance('root@IPAddress2:3306') cluster.
Figure 22. Cluster status Configure MySQL Router MySQL Router establishes communication network between Wyse Management Suite and MySQL InnoDB. To install MySQL Router, do the following: 1 Login to the Windows Server 2012 to install MySQL Router. For more information, see MySQL Router Installation 2 Select MySQL Router from the Select Products and Features screen and then clck Next until the Installation Complete screen is displayed. 3 Browse to \ProgramData\MySQL\MySQL Router directory, and open the
Figure 23. Bootstrap server address Create database and users on MySQL InnoDB server You must create the database and user accounts with administrator privileges on MySQL InnoDB server.
6 Achieve high availability on MongoDB The following steps explain how to achieve high availability on MongoDB: 1 Install MongoDB—see Installing MongoDB. 2 Create replica servers—see Creating Replica servers. 3 Create Stratus users—see Creating Stratus user account. 4 Create root user—see Creating root user for MongoDB. 5 Edit MongoDB configuration file—see Editing MongoDB configuration file.
Figure 25. mongod.cfg file 4 Open the mongod.cfg file in a text editor, and add the following entries: a b c SystemLog:destination: file path: c:\data\log\mongod.log Storage: dbpath: c:\data\db 5 Save the file. 6 Login to MongoDB server. 7 Run the following command to start the MongoDB service: a b C:\MongoDB\bin>.\mongod.exe --config c:\Mongodb\mongod.cfg --install C:\MongoDB\bin>net start mongodb The message MongoDB service is starting is displayed. 8 Change the working directory to \MongoDB\bi
Create DBadmin user for MongoDB Login to the MongoDB using the user account created in the previous section. The DBadmin user is created with the administrative privileges. Run the following command to create the DBadmin user: mongo -uDBUser -pPassword admin use admin db.createUser( { user: "DBadmin", pwd: , roles: [ { role: "DBadmin", db: "admin" } ] }) Edit mongod.cfg file You must edit the mongod.cfg file to enable the security for the MongoDB database.
2 Go to \data\bin\mongod.cfg directory, and open mongod.cfg file in a text editor. 3 Add the following three lines in the mongod.cfg file: keyFile: c:\data\log\mongod.key.txt replication: replSetName: wms Figure 27. Enabling security 4 Create mongod.key.txt file and copy on all the three servers. Figure 28.
Figure 29. Replication status 8 Start mongod service and add the secondary nodes to the second and third nodes in the MongoDB cluster: rs.add("IPAddress2:27017") rs.add("IPAddress3:27017") NOTE: The port numbers will differ based on the systems at your network and systems. 9 After you add the nodes in the MongoDB cluster, check the replication status by running the following commands for the primary and secondary nodes: rs.
Figure 30. Status in primary server Figure 31.
7 Achieve high availability for Teradici devices Wyse Management Suite uses the HAProxy hosted on the Ubuntu server 16.04.1 LTS to perform load balancing between the EMSDK servers. HAProxy is a load balancer proxy that can also provide high availability based on how it is configured. It is a popular open source software for TCP/HTTP Load Balancer, and proxy solution which runs on Linux operating system.
NOTE: Administrator must add additional back end servers beyond the total number of client’s capacity to have seamless failover. 5 Save the changes to the haproxy.cfg file by typing CTRL+O.
Install Wyse Management Suite server Ensure that the following components are configured before you install Wyse Management Suite server: • Windows Failover Cluster on two Nodes • MongoDB Server is running with replica set • MySQL InnoDB Cluster set-up is running • MySQL Router isinstalled on the two Nodes Do the following to install Wyse Management Suite server: 1 Launch the Wyse Management Suite v1.3 installer screen. 2 Select Custom Type and Teradici EMSDK and then click Next.
8 Install Wyse Management Suite on Windows Server 2012 To install the Wyse Management Suite on a private cloud, do the following: 1 Double-click the installer package. 2 On the Welcome screen, read the license agreement, and click Next. 3 Select the Setup Type you want to install, and click Next. The available options are: 4 • Typical—Requires minimum user interaction and installs embedded databases. • Custom—Requires maximum user interactions and is recommended for advanced users.
9 Post installation checks Do the following to check the high availability for Wyse Management Suite version 1.3: • Launch the Wyse Management Suite admin portal and check whether you are able to login using the web interface. • Edit the bootstrap.propertiesfile in the Tomcat sever in under the \Dell\WMS\Tomcat-8\webapps\ccm-web\WEB-INF\classes folder for MongoDB as follows: mongodb.seedList = MongoDBServer1_IP:27017, MongoDBServer2_IP:27017, MongoDBServer3_IP:27017 Figure 32.
NOTE: Ensure that there is only one record in serversInCluster table and if there are more than one record, delete the excess records.
10 Troubleshooting This section provides troubleshooting information for Wyse Management Suite version 1.3 for the cluster set up. • Problem: Where is the Wyse Management Suite log file located to check server installation issues. Workaround: The log file is in the %temp% WMSInstall.logfolder. • Problem: Where is the Tomcat service related log file located to check the application related issues. Workaround: The log file is in the \Program Files\DELL\WMS\Tomcat-8\stratus.log folder.
