Connection Manager Server

Top  Previous  Next

What is the Connection Manager Server (CMS)?

The Connection Management Server (CMS) is the heart of the mSuite system.  It is responsible for the secure VPN tunnel that is maintained to the client devices.  It is also responsible for routing client requests to the appropriate service providers which include:

 

Authentication Server
Client Agent Proxy (& Device Management Server)
mNotes / mForms Server
File Replication Server
Chat Server

 

       Configuring the Connection Manager Server

1.Expand the configuration node in the navigation tree and select Servers and Groups.  The action pane will display the configured servers
2.Right mouse click the server and select Properties from the pop-up menu.
3.Select the Connection Management tab.  It will highlight the currently-active template, which is normally the default template that we recommend not be altered (Default CMS Template).  Click the Configuration Wizard button - with the magic wand icon.
4.On the Welcome screen, make sure that the box Run the Connection Manager Service is checked and then click the Next button.
5.The General Settings page allows you to configure the TCP ports that the CMS will use.  The default is to listen on all interfaces on the current machine "*" on port 605.
6.Also on the General Settings page, you can change the x.509 certificate used by the system.  This will be defaulted to mSuite CA - this is the unique self signed certificate created by the installation process.  Only change this if you have a certificate issued by your organization's Certificate Authority or by a public Certificate Authority.  The characteristics of the certificate are described here .  To change the certificate, it must be installed on the machine running the CMS and appear in the list of available certificates.  If this is not the case use the Add certificate button to include your certificate and then select it from the list.
7.Lastly you can change the session idle timeout value.  The default is 5 minutes and this is the recommended value.
8.Press Next to continue.
9.The next screen display the proxy settings.  This provides the information that the CMS needs to be able to make an outbound connection to the Proxy.  The Proxy can be local, in the DMZ or on the internet (the CommonTime Switching Center or CSC).
10.Check the Use proxy box to make the CMS direct all traffic via a Proxy.
 
To use the CommonTime Switching Center (CSC), the proxy settings are:
IP Address: csc.commontime.com
Port: 443 (if necessary, you can use either port 80 or port 1650 instead)
Use SSL: checked

 
You may also need to configure the Web Proxy settings to allow the CMS to make an outbound internet connection to the CSC.
 
For a Local or DMZ Proxy, the settings depend on the proxy location.  The IP address and Host must specify the machine address where the Proxy is running and the port that the Proxy is listening on for CMS connections.

 

11.Click Next when this screen is complete.
12.The Authentication Servers screen allows you to select the authentication servers that should be used by the CMS to respond to authentication requests.  If you configure multiple servers, they will be used in a round robin fashion to respond to authentication requests.  Click Next to continue.
13.The Client Agent Proxy Servers screen allows you to select the CAP that should be used by the CMS to respond to CAP requests.  If you configure multiple servers, they will be used in a round robin fashion.  Click Next to continue.
14.The mNotes Servers screen allows you to select the mNotes Server that should be used by the CMS to respond to mNotes and mForms requests.  If you configure multiple servers they will be used in a round robin fashion.  Click Next to continue.
15.The Chat Servers screen allows you to select the Chat Server that should be used by the CMS to respond to Sametime requests.  If you configure multiple servers they will be used in a round robin fashion.  Click Next to continue.
16.The Notification Servers screen allows you to select the Notification Servers that this CMS  should use to send notifications to devices.  If you configure multiple servers they will be used in a round robin fashion.  Click Next to continue.
17.The HTTP Proxy Servers screen allows you to select the internal web proxies that this CMS will redirect client HTTP traffic to.  Use the New button to add a web proxy - enter the IP address and port that the web proxy listens on.  If you configure multiple servers they will be used in a round robin fashion.  Click Next to continue.
18.On the completion page, you have the choice of saving the settings as a new template or updating the existing properties.  You will normally update the existing properties - the default settings.  Templates are advanced configuration and you should only use them if instructed by CommonTime support.
19.Click Finish to complete the wizard.

Page url: http://msuitehelp.commontime.com/index.html?ct_adv_services_connection_manager_server.htm