Skip to main content
Skip table of contents

Channel settings for a typical NexJ CRM deployment with Exchange Server

A typical deployment of NexJ CRM requires that you add certain channels to the environment file.

All deployments with Exchange Server require a mail channel, one or more sender channels, and a receiver notification channel.

Mail channel settings for a typical NexJ CRM deployment

You must set up a mail channel if you want to enable the synchronization of meeting notifications.

Mail channel connection settings for a typical NexJ CRM deployment

AttributeValueNotes
ChannelMail
TypeMailConnection
Email Account<user.name>@<example.com><user.name> is used to connect to the mail server. In the XML, this attribute is named user.
Password<Email_Password>The password corresponding to the Email Account.
FolderINBOXThe incoming messages folder. In XML, this folder is named inFolder.
Receiver Protocolpop3The protocol to use for incoming messages. In XML, this attribute is named inProtocol.
Receiver Host<mailserver.example.com>The mail server host for incoming messages. In XML, this attribute is named inHost.
Receiver EncryptionSSLThe type of channel encryption to use. In XML, this attribute is named inEncryption
Sender Email<outmail@example.com>The default email address for the sender. In XML, this attribute is named from.
Sender ProtocolsmtpThe protocol to use for outgoing messages. In XML, this attribute is named outProtocol.
Sender Host<outmailserver.example.com>The mail server host for outgoing messages. In XML, this attribute is named outHost.

Channel settings for a typical NexJ CRM deployment with Exchange Server

A typical deployment of NexJ CRM with Exchange Server requires that you add certain channels to the environment file.

ExchangeEWSSender channel connection settings for a typical NexJ CRM deployment

The Value column in the following table contains the recommended settings.

AttributeValueNotes
ChannelExchangeEWSSender
TypeHTTPConnectionThe type of channel encryption to use.
URLhttp://<host>/ews/Exchange.asmxThe host must be that of the Exchange Web Service for the target server.
User<HTTP_User_ID>The user name used to connect to remote HTTP servers.
Password<HTTP_User_Password>The password corresponding to the HTTP User ID.
Trust<certificatefile>The certificate file.
AuthenticationbasicThe type of authentication to use.
readTimeout180000Timeout (in milliseconds) for outbound HTTP requests.
Use HTTPS CommunicationtrueUses HTTPS communication in the receiver. In XML this attribute is secure.
maxSendersThe total number of synchronized users divided by 10.If you are using Exchange Server 2013 or 2016 with 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. 

Info

ExchangeEWSSender2 and ExchangeEWSSender3 channels are duplicates of ExchangeEWSSender and are also optional channel connections when there is only one entry point for Exchange EWS communication; just one ExchangeEWSSender channel is sufficient in that event.

ExchangeEWSNotificationReceiver channel connection settings for a typical NexJ CRM deployment

AttributeValueNotes
ChannelExchangeEWSNotificationReceiver
TypeHTTPConnectionThe type of channel encryption to use.
AuthenticationnoneThe type of authentication to use.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.