Cisco Cisco Unified CRM Connector 7.5 Installation Guide

Page of 187
 
100  
configured with the SoapModule.  It is appropriate for web based 
applications such as PeopleSoft.   The SOAP Adapter communicates with 
the application adapter through web services running on an IIS server.   
The IIS server acts as an intermediary between the SOAP Adapter and the 
application adapter.  Its application pools execute the services. 
.Net Remoting is the second communication enabler.  It is more direct and 
streamlined:  there is no intervening web service (IIS).  Instead .Net 
remoting communicates port-to-port between the application adapter and 
the CRM Connector Server.  This is more streamlined and simpler to 
implement.   
.Net remoting is used with application adapters that are run as part of 
another application.  The Salesforce adapter runs within the 
SalesForceCTI.exe application on the agent’s, in the desktop tray. 
Licensing .Net Adapters 
All application adapters use a .Net Adapter.  To simplify licensing, the 
application adapters use the .Net Adapter license rather than requiring a 
separate license key for each application’s adapter.  The .Net Adapter 
license key is:  AA-DOTNET  
Application Adapter Communication Settings 
Each application adapter requires a .Net Adapter sub-component to 
communicate with the CRM Connector Server.  Table 6-1: Application 
Adapter .Net Adapter Type lists the application adapter and the proper 
.Net Adapter Type it uses.  This information is also included in the 
Application Adapter Configuration chapters.  
Table 6-1: Application Adapter .Net Adapter Type 
Application Adapter 
.Net Adapter Type 
Application Adapter for Oracle PeopleSoft 
SOAP Adapter 
Application Adapter for Microsoft CRM 
.Net Remoting 
Application Adapter for Salesforce.com 
.Net Remoting 
CRM Connector Server Administration Tool 
SOAP Adapter 
Configuring .Net Remoting 
The .Net Remoting Adapter runs as a CRM Connector Server module.  It 
is configured in the config.ini file and requires the same Module Manager 
configuration as any other component module:  define the module class 
and then define an instance of the module based on its class.   The 
[RemotingEndpoint] section configures its remote port and other settings. 
Module Manager Keys 
To enable the .Net Remoting Adapter, add the two keys listed in Table 
6-2:  .Net Remoting Module Settings to
 the module manager.  Because this 
is an adapter configuration the settings may be separated from the rest of 
the core modules.