Communication with Aurea CRM.Web

CRM.launcher communication with Aurea CRM.Web.

The CRM.launcher performs the following tasks to mediate communication between the browser running in a shared environment and Aurea CRM.Web application:

• It maintains different unique identifiers to distinguish between user’s web browser login sessions.
• It allows the user to activate the CRM.launcher session from the web browser.
• If the user closes the web browser and re-opens the browser again, the CRM.launcher gets the unique identifier for the user’s previous session.
• The CRM.launcher is independent of the Windows service. In case the CRM.launcher is not launched as a windows service, a user can still launch the CRM.launcher server for this session.
  Note: The user has to be a part of the administrator group, in order to be able to start the service.
• CRM.launcher service for multiple users is not activated for the standard version of Aurea CRM.Web application. This is only allowed for the Enterprise version of Aurea CRM web application.
  Note: If multiple users try to activate CRM.launcher session from the Standard version of Aurea CRM, the following message is displayed: Multiple login sessions for CRM.launcher is an enterprise feature only. To use this funcationality, please upgrade your system to an enterprise edition.

CRM.launcher and Aurea CRM.Web communicate over a secure Web Socket sub-protocol named WAMP. For further details, see http://wamp.ws. The communication only accepts a secure connection. Therefore the user has to install a certificate when CRM.launcher is first started.

For more information, see the article “CRM.Launcher and Security” at https://support.aurea.com.

To enable the communication between CRM.launcher and Aurea CRM.Web, both products need to know which port to use (default: 18188).

For Aurea CRM.Web the port is configured via the System.LauncherPort Web Configuration parameter. For further details, see System.LauncherPort in the Web Administrator's Guide. This port needs to match the port configured for CRM.launcher:

• Users can configure the port in CRM.launcher's Settings dialog (Connectivity tab). The configured port is saved in the user.config file that is used for CRM.launcher. The user.config file is located in in the root directory of the installation, i.e. the same location as update.Launcher.exe (default: %localappdata%/update.CRM).
• If you don't want users to be able to change this setting, specify the port in the update.launcher.exe.config file as follows:

  <update.launcher>
  	[...]
  <!-- The list of plug-ins to be loaded by CRM.launcher -->
  	<PlugIns>
  		<!--
  		<PlugIn type="update.Launcher.Offline.PlugIn,update.Launcher.Offline" required="true" />
  		-->
  		<PlugIn type="update.Launcher.WebBrowser.PlugIn,update.Launcher.WebBrowser" required="false" />
  			<Url>wss://localhost:11771</Url>
  		<PlugIn type="update.Launcher.RemoteControl.PlugIn,update.Launcher.RemoteControl" required="false" />
  		<PlugIn type="update.Launcher.Documents.PlugIn,update.Launcher.Documents" required="false" />
  		<PlugIn type="update.Launcher.Phone.PlugIn,update.Launcher.Phone" required="false" />
  	</PlugIns>
  </update.launcher>