The following tutorial will demonstrate in detail, the setup of X Dispatch Server on a machine running Windows Server 2012 R2. This is the current recommended setup for on-premise systems by CXT Software. If you have any questions or are in need of assistance at any time, please visit our ServiceDesk Portal to open a ticket.

Terminology

_{Back to top.}

X Dispatch Install Types

_{Back to top.}

Prerequisites

(X Dispatch Server Video Tutorial - Overview)

Hardware/OS Requirements

• 2.5 GHz Intel® or AMD x86-x64 (Quad-core processor)
• 8 GB RAM
• 100 GB available disk space
• Microsoft Windows Server 2012 R2
• Windows Powershell 3.0
• Microsoft SQL Server 2012 R2 (2008R2 will work, however, this will no longer be compatible when v19 releases).

Important Information About Virtualization

CXT Software recommends using a physical server for X Dispatch database server role, however, it is possible to use a Virtual Machine. 

Domain Accounts

You will need to create three domain administrator accounts to handle various back-end processes and roles for X Dispatch. 

1. cxtbll (For running the cxtbll COM+ application)
2. cxtjobs (For running the App Pools in IIS and X Stream)
3. cxtsupport (For RDP access and troubleshooting)

Once these accounts are created you can move on to Step 1 - Configuring DEP (Data Execution Prevention).

Back to top.

Database Server Setup & Configuration

Step 1 - Configuring DEP (Data Execution Prevention)

1. Right click on the Windows start button.
2. Click on System.
3. In the System window click on Advanced system settings. 
4. In the System Properties window click the Advanced tab.

5. Under the Advanced tab click the Settings button under Performance. 

   
6. In the Performance Options window click the Data Execution Prevention tab. 
7. Select the Turn on DEP for essential Windows programs and services only then click OK. 
8. Click OK on the popup to restart the server, then close all active windows and restart. 

Step 2 - Configuring UAC (User Account Control)

1. Click on the Windows start button.
2. Start typing "UAC" in the search box. 
3. Click on Change User Account Control settings. 
4. Drag slider to lowest Never Notify setting. 
5. Click OK. 
6. Click on the Windows start button. 
7. Start typing "Regedit" in the search box.
8. Click on Regedit. 

9. Turn off UAC via registry by changing the DWORD EnableLUA from 1 to 0 in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system". 

   
10. Restart the server.

Step 3 - Configuring COM+ (Component Object Model)

1. Click on the Windows start button.
2. Start typing "Administrative Tools" in the search box.
3. Click on Administrative Tools.
4. In the Administrative Tools window click on Component Services. 
5. In the Component Services window, expand Component Services, then Computer. 

6. Right click on My Computer and select Properties. 

   
7. In the My Computer Properties window click the Options tab. 
8. Change the Transaction Timeout to 1200. 
9. Click on the Default Properties tab. 
10. Check the Enable Distributed COM on this computer and the Enable COM Internet Services on this computer options, if not already. 
11. Click the COM Security tab. 
12. Click the Edit Limits button located in Access Permissions section. 
13. Check that the Everyone and ANONYMOUS LOGON users are listed. If they are not listed, click Add button and add each user.
14. Verify that all the Allow checkboxes are checked for Everyone and ANONYMOUS LOGON users. 

15. Repeat steps 12 - 14 for Edit Limits and Edit Defaults in Access Permissions and Launch and Activation Permissions sections. 

    
16. Click OK.
17. Click OK in the My Computer Properties window.
18. Click Yes on the DCOM Machine Wide settings window.
19. In the Component Services window expand My Computer. 
20. Expand Distributed Transaction Coordinator.
21. Right click on Local DTC and click Properties.
22. In the Local DTC Properties window click on the Security tab.
23. Under the Security tab check the following boxes, Network DTC Access, Allow Remote Clients, Allow Remote Administration, Allow Inbound, Allow Outbound, No Authentication Required, and Enable XA Transactions.
24. Click OK.
25. Click Yes on the MSDTC Service window. 
26. Click OK to the MSDTC restart message. 
27. Close the Component Services window.

Step 4 - Configuring Middle Tier

1. Click the Windows start button. 
2. Start typing "Administrative Tools" in the search box.
3. Click Administrative Tools.
4. In the Administrative Tools window click on Server Manager.
5. In Server Manager click on Local Server in the left menu bar. 
6. After the Local Server management page loads scroll down to Add Roles and Features.

7. Click the Tasks drop-down and select Add Roles and Features. 

   
8. In the Add Roles and Features Wizard click Next on the Before you Begin Screen.
9. On the Installation Type screen select Role-based or feature-based installation and click Next. 
10. Select the correct server in the Server Selection screen and click Next.
11. On the Select Server Roles screen check Application Server, then click Next.
12. On the Select Features window check the .NET Framework 3.5 options, then click Next. 

13. On the Select Role services window check the COM+ Network Access, Distributed Transactions (all sub boxes checked) then click Next. 

    
14. In the Choose a Server Authentication Certificate for SSL encryption click the Create self-signed certificate then click Next.
15. Verify installation choices then click Install.
16. Once the Roles and Features are installed close Server Manager.
17. Restart the server.

Step 5 - SQL Server Installation & Configuration

1. Download Microsoft SQL server here. (SQL Server Express is Free to use but is limited to a Database of 10 GB)
2. Follow Microsoft instructions to register and download Microsoft SQL Server 2012 Express with Mgmt Tools. (64 Bit ENU\x64\SQLEXPRWT_x64_ENU.exe, 32 Bit ENU\x86\SQLEXPRWT_x86_ENU.exe)
3. Right click on the downloaded SQL Server installer and click Run as Administrator.
4. In the SQL Server Installation Center window click on New SQL Server stand-alone installation or add feature to an existing installation.
5. Check the box I accept the license terms and click Next.
6. On the Products Updates page check the box to Include SQL Server product updates, then click Next.

7. On the Feature Selection page check the boxes Database Engine Services, SQL Server Replication, Management Tools - Basic, SQL Client Connectivity SDK, then click Next. 

   

8. On the Instance Configuration page select Named Instance and name it "MSSQLSERVER", then click Next. 
9. On the Server Configuration window ensure the SQL Server Database Engine is configured to use the NT AUTHORITY\SYSTEM account.
10. On the Database Engine Configuration page set Authentication Mode to Mixed Mode in the Server Configuration tab.
11. Set the Password and confirm.
12. Click Add... and add the 3 users created at the start (cxtbll,cxtjobs,cxtsupport) click Next. 
13. Click Next to start the installation.
14. Once the installation is complete click Close then Close again.
15. Click on the Windows start button.
16. Start typing "SQL Server Configuration Manager" in the search box.
17. Click on SQL Server Configuration Manager.
18. In the SQL Server Configuration Manager window expand SQL Server Network Configuration so that Protocols for MSSQLSERVER is visible. 
19. Click on Protocols for MSSQLSERVER.
20. Right click on Shared Memory and select Disable.
21. Click OK.
22. Right click on TCP/IP and select Enable.
23. Click OK.
24. Click on SQL Server Services.
25. Right click on SQL Server Browser and select Properties. 
26. Select the Service tab. 
27. Click Disabled on Start Mode to show options, then select Automatic.
28. Click OK.
29. Right click on SQL Server (MSSQLSERVER).
30. Click Restart.
31. Right click on SQL Server Browser. 
32. Click Start.
33. Close all windows.

Step 5.5 - Attaching a database

1. Create a full backup of both CxtData and CxtArchiveData databases.
2. Move backup files to a new server if necessary.
3. Click on the Window start button.
4. Start typing "SQL Server Management Studio" in the search box.
5. Click on SQL Server Management Studio.
6. In the Connect to Server window ensure the Server Type is set to Database Engine.
7. Enter a period (.) in Server name since the SQL instance has previously been named MSSQLSERVER.
8. Under Authentication, you should set it to be Windows Authentication.
9. Click Connect.
10. Expand Databases in the tree on the left to view all Databases. Note cxtData and cxtArchiveData are not there. 
11. If you did a backup and are restoring to the new SQL server, right click on Databases and click New Database.
12. In the New Database window enter cxtData as the Database name and click OK.
13. Repeat steps 11-12 for cxtArchiveData database.
14. Right click on cxtData and select Tasks > Restore > Database...
    

15. Select Device.

16. Click the ... button.

17. Click the Add button, navigate to the location of the backup file and select the file.

18. Press OK then OK.

19. Verify that the information is correct and click OK. 

    Quick Tip

    To attach a baseline Right click on Databases and choose Attach. Follow the on-screen instructions to navigate to the location of the DB files, choose the files and click OK to complete. Must be in a location that the accounts have read write access to.

Step 6 - Installing X Dispatch Server

1. Download the latest version of X Dispatch Server here.
2. Extract the downloaded file. 
3. Right click Run as Administrator.
4. Agree to the terms. 
5. Click Next.
6. Click Install.
7. Accept the ASP.NET MVC Install. 
8. Click Finish ASP.NET MVC.
9. Click the Windows start button.
10. Start typing "Services" in the search box.
11. Click on Services.
12. Scroll down to X Stream.
13. Double click and open the X Stream service.
14. Click the Log On tab.

15. Change from Local System account to the domain account cxtjobs. 

    
16. Click OK.
17. Click OK on the account has been granted permissions pop up. 
18. Click OK to the restart pop up.
19. Right click On X Stream and click Restart.

Step 6.1 - Updating the database

1. Click the Windows start button.
2. Start typing "Powershell" in the search bar.
3. Right click Powershell and select to Run as Administrator.
4. In the Powershell window, type the following command and press Enter: set-executionPolicy RemoteSigned
5. In the Powershell window, type the following command and press Enter: cd "\Program Files (x86)\Connexion"
6. In the Powershell window, type the following command and press Enter: .\update.ps1
7. Close Powershell.
8. In File Explorer, navigate to "C:\Program Files (x86)\Connexion".
9. Review the Update.txt file.

Enter a support ticket if any errors are listed.

Step 6.5 - CXTBLL Configuration

1. Click the Windows start button. 
2. Start typing "Component Services" in the search box.
3. Click Component Services.
4. Expand Component Services, Computers, My Computer, COM+ Applications.
5. Right click on cxtbll and click Properties.
6. Click the Identity tab.
7. Click on This User
8. Enter the cxtbll account created in Step 1 - Configuring DEP (Data Execution Prevention), click OK.
9. Close Component Services.
10. Open X Dispatch.

_{Back to top.}

Web Server Set Up & Configuration

1. Click on the Windows start button.
2. Start typing "IIS" in the search box.
3. Click on Internet Information Services (IIS) Manager.
4. Expand the server in the tree on the left.
5. Right click on Application Pools, click on Add Application Pool...
6. In the Add Application Pool window, set the Name to .NET 2.0 and the .NET CLR Version to .NET CLR Version v2.0.50727. 
7. Click OK.
8. Right click on Application Pools, click on Add Application Pool... 
9. In the Add Application Pool window, set the Name to .NET 4.0 and the .NET CLR Version to .NET CLR Version v4.0.30319. 
10. Click OK.
11. Right click on the .NET 2.0 application pool, then click on Advanced Settings... 

12. In the Advanced Settings window, click on ... under Identity. 

    
13. Select Custom account and press the Set... button.  
14. Enter cxtjobs domain account information for the server, then click OK.
15. In the Advanced Settings window set the Enable 32 Bit Applications to True, then click OK.
16. Repeat steps 11 - 15 for the .NET 4.0 application pool.
17. Unzip X internet. Download here.
18. Copy the second XInternet folder (there is a XInternet folder inside the XInternet folder), to C:\Inetpub\wwwroot so all the content is in C:\Inetpub\wwwroot\XInternet. These are the web files.
19. Expand the Sites folder in the tree on the left. 
20. Right click on Sites, then click Add New Site.
21. Name the new site "XInternet".
22. Press the Select... button.
23. Select .Net 2.0 as Application pool.

24. Click OK. 

    Quick Tip

    

    • If "Duplicate..." message appears, press "OK" to continue.  
    • If "Default" website exists and is not used, right click on it and select "Remove." 
    • Click on "Sites" and check "Status" of "XInternet" site.  If the status is "Stopped" then click on XInternet and select "Start" from the right pane.
25. Set the physical path to where you saved the web files.
26. Open a web browser and navigate to 127.0.0.1 to verify the site is running.
27. In IIS, click on the Server then click Server Certificates.

28.  Check for existence of current license under Name.If the license doesn't exist, select Create Self-Signed Certificate. 

    
29. Specify a friendly name for certificate and press OK. 
30. Select XInternet website.
31. Select Bindings. 

32. Set Type to https.

33. Set SSL certificate to the one created.

34. Click OK,  

    
35. Close the Bindings window.
36. Right click on XInternet site and select Add Application...
37. Set the Alias to "CxtWebService".
38. Click Select... to set Application pool to .Net 4.0. 
39. Set the Physical path to "C:\Program Files (x86)\Connexion\XInternet\CxtWebService". 

40. Press OK. 

    
41. Right click on XInternet site and select Add Application... 
42. Set Alias to "XInternetMVC". 
43. Click Select... to set Application Pool to ".Net 4.0". 
44. Set the Physical path to "C:\Program Files (x86)Connexion\XInternet\V2".

45. Press OK. 

    
46. Click on CxtWebService. 
47. Click on Authentication.
48. Right click on Anonymous Authentication and select Enable. 
49. Right click on Anonymous Authentication and select Edit. 
50. Select Application pool identity and press OK.
51. Verify that the status is enabled.
52. Repeat steps 48 - 51 for XIntenetMVC.
53. Click on CXTWebService and open Application Settings.
54. Select Add from the pane on right.  

55. Enter "RemoteServer" as Name. and Data Source=127.0.0.1;Initial Catalog=cxtdata;Integrated Security=SSPI into Value field.  The IP address (127.0.0.1 is used as this is a single server replace with IP address of Database server for multi server setup..) 

    
56. Right click on XInternet site and select Add Application.
57. Enter "ROWS" for Alias.
58. Select ".Net 2.0" for Application pool.
59. Set Physical path to "C:\Program Files(x86)\Connexion\ROWS".

60. Press OK. 

    
61. Close IIS.

_{Back to top.}

X Tracking Set Up & Configuration

X Tracking allows the plotting of orders, routes and delivery personnel on a web-based map in real time. This means that delivery personnel can be tracked to their last GPS fix, or if GPS devices are not used, to their last pickup or delivery. Unassigned and assigned orders are shown in additional to route stops that are plotted in sequential order for a true graphical representation of a single or multiple routes. Several reports can be created, such as the "Driving Distance" report which shows true GPS driving distance the delivery personnel. All of these features add up to an easy and intuitive tool that can be used to more effectively manage the fleet.

XT IIS Configuration

1. Open IIS Manager, expand Sites. 
2. Right click on X Internet, select Add Application...
3. Set Alias to XInternet.
4. Set Physical Path to C:\Program Files(x86)\Connexion\XInternet.
5. Set Application Pool to .NET 2.0.
6. Press OK.
7. On the Connect As screen set Specific user to cxtbll.
8. Click Test Settings... to verify path and user account are accurate. 
9. Select the XInternet application and open Application Settings section.
10. Set Name to "AspAddress" and Value to the URL location of ASP site. " / " can be entered if a virtual directory is created under ASP website and ASP website is the default website in IIS.
11. Select Add under Actions to add new Application Setting 
12. Set Name to "RemoteServer"  and enter the IP address of X Dispatch Server under Value.
13. Click OK.
14. Add (for new installations) or modify (for upgrades) the following settings below. 
         - Name: XTrackingWebserviceURL
         - Value: http://127.0.0.1/XInternet/CxtMappingWebService.svc?wsdl
15. Click OK.
16. Close IIS.

_{Back to top.}

Remote Desktop Setup & Configuration

Detailed instructions for installing Remote Desktop is beyond the scope of this documentation, however, brief notes are provided below.  Remote desktop is a standard remote connectivity platform from Microsoft and your IT team should have the ability to install this Microsoft product.

RDS Setup

1. Open Server Manager.
2. Click on Local server.
3. Scroll to Roles and Features.

4. Click the Task dropdown and select Add Roles and Features. 

   
5. If you receive the "Before you begin" page click Next. 
6. Select Role-based or feature-based installation, then click Next.
7. Select the server and click Next.
8. Check Remote Desktop Services under the Select Server Roles screen, then click Next.
9. Add required features, then click Next.
10. Click Install.

_{Back to top.}

Installation Troubleshooting Tips & Tricks

When launching X Dispatch, if it gets stuck at X%

• 32% Cannot connect to Remote Server (Database) or it is blank opens server select utility
• 35% cxtbll COM+ Application  may not be  configured correctly
• 36% Fails here may mean SQL is not running
• 94% Check the DEP settings

Multi-Server Setup - on-premise: X Internet will not log in

Review the Global.asa file located in the c:\inetpub\wwwroot\XInternet directory.

• RemoteServer - Default "127.0.0.1"    - This should be pointed at the DB Server 
• XInternetURL - Default "/XInternet/" 
• XInternetMvcURL - Default "/XInternetMVC/" 

Multi-Server Setup - on-premise: X Mobile will not work

Review the gps.asp file located in the c:\inetpub\wwwroot\XInternet directory.

• The default should be Application("RemoteSever") but it can be a fixed address pointing at the DB Server
  • ogps.Process(Application("RemoteServer"))
  • ogps.Process("192.168.100.100")

_{Back to top.}