Channel settings for a NexJ CRM deployment with Exchange Online
A deployment of NexJ CRM with Exchange Online requires that you add certain channels to the environment file.
Deployments with Exchange Online use a mail channel and a receiver notification channel similar to Exchange Server deployments. For more information, see Channel settings for a typical NexJ CRM deployment with Exchange Server. An Exchange Online specific sender channel also needs to be configured as described below.
Sender channel settings
A deployment of NexJ CRM with Exchange Online requires that you add a sender channel to the environment file.
ExchangeEWSSender channel connection settings
The Value column in the following table contains the recommended settings.
| Attribute | Value | Notes |
|---|---|---|
| Channel | ExchangeEWSSender5 | The name of the channel configured for synchronization. |
| Type | HTTPConnection | The type of channel to use. |
| URL | https://outlook.office365.com/ews/Exchange.asmx | The host must be Exchange Web Services for the target. |
| User | <application_ID>:<service.account@domain.com> | The user has two components separated by a colon. The first component is the application ID of the AAD registered application and the second component is the mailbox address of the service account. |
| Password | text:<client_secret>:<service_account_password> | The password has two components separated by a colon following the "text" prefix. The first component is the client secret created in the AAD registered application and the second component is the password of the service account. |
| Authentication | custom | The type of authentication to use. |
| Use HTTPS Communication | true | Uses HTTPS communication in the receiver. In XML, this attribute is secure. |
| Authentication Component | rpc:System.Authentication.EXO | In XML, this attribute is authComponent, and is used to identify the token URL for AAD. |
| maxSenders | The total number of synchronized users divided by 10. | If you are streaming notifications, you must configure the maxSenders attribute, which provides the maximum number of threads in the connection pool used for an Exchange EWS notification. |
Configuring a proxy server for Exchange Online OAuth
You can use a proxy auto-config file to configure a proxy server for requests made through HTTP channels. To configure a proxy server for Exchange Online OAuth:
- Add the
pacmixin to your environment file. - Add the
pac.url property to the environment file and set the value to the URL of the PAC file. Add the following proxy authentication configuration to the HTTP channel connection, if appropriate:
CODEproxyAuthentication="proactive", or proxyAuthentication="basic" proxyPassword="<proxypass>", proxyUser="<proxyusr>".Optionally, add the following environment properties to control the behavior of pac URL caching:
pac.cacheSize: Maximum cache entry count (defaults to 256)pac.cacheTimeout: Cache timeout in milliseconds (defaults to 604800000 - equivalent to one week)pac.cacheScope: PAC cache scope: host|port|url (defaults to host)