Communications Configuration Settings

IMPORTANT

Read more about Data Workbench’s End-of-life announcement.

Instructions to configure communications for Insight Server or Repeater.

Complete the parameters in the following file:

Product Name installation directory\Components\Communications.cfg

NOTE

Before modifying any parameters not listed in this table, please contact Adobe.

Parameter Description
Access Control File

Location of the Access Control.cfg file. The default location is the Access Control folder within the Insight Server or Repeater installation directory.

Example: Access Control File = Path: Access Control\\Access Control.cfg

Access Log Directory

Folder to which you want to map the audit logs.

Example: Access Log Directory = string: Audit\\

Note: You can map audit logs to another local drive (example: string: P:\\Audit\\ ), but do not map audit logs to a network drive.

Access Log Verbose This parameter can be set to true or false. It is used to enable and disable audit log filtering. To ensure that every request is logged, set the parameter to True.
IP Interface

IP address to use when two network cards are available for accessing two different networks.

Example: IP Interface = string: < IP Address >

Port

Non-secure (HTTP) port on which the Insight Server or Repeater listens. The default port is 80. Entering a value of 0 disables non-secure connections.

Example: Port = int: 80

SSL Ciphers Some environments require stronger communication security than others. If you want to use a specific SSL cipher suite, you can specify it with this parameter.

Example: SSL Ciphers = string: AES256-SHA256

SSL Port

Secure (via SSL) port on which the Insight Server or Repeater listens. The default port is 443. Entering a value of 0 disables secure connections.

Example:

SSL Port = int: 443
n=LoggingServer: Heading for Logging Server settings.
Customer Name

Customer name to appear for Unspecified customers in administrative alerts, as in the following example:

“No data received from sensor XYZ for customer 'Unspecified' in 15.”

Example: 1 = LoggingServer:    Customer Name = string: CompanyAB

Using the example above, administrative alerts for Unspecified customers would now read as follows:

“No data received from sensor XYZ for customer ‘CompanyAB’ in 15.”

n=FileServer:

Local Path = string: Logs\\

Folder in which you want to store the log files.

Example:

9 = FileServer:    Local Path = string: Logs\\

To be able to access this folder from the Server Files Manager , the location specified in this parameter must match the location that you specify in the Log Paths parameter in the Log Processing.cfg file. For more information about modifying the Logs directory in the Log Processing.cfg file, see Log Processing Configuration File chapter of the Dataset Configuration Guide.

n=FileServer:

Local Path = string: Audit\\

Folder to which you want to map the audit logs.

Example:

5 = FileServer:    Local Path = string: Audit\\

Note:

You can map audit logs to another local drive (example: string: P:\\Audit\\ ), but do not map audit logs to a network drive.

To be able to access this folder from the Server Files Manager , the location specified in this parameter must match the location that you in the Access Log Directory parameter in this file.

n=NormalizeServer:

This parameter applies only to Insight Server .

For more information about specifying the Centralized Normalization Server for your Insight Server cluster, see Log Processing Configuration File chapter of the Dataset Configuration Guide.

n=ReportStatusServer:

URI = string: /ReportStatus.vsp

This parameter applies only to Insight Server .

Enables you to view Report’s status in the Detailed Status interface for Insight Server .

Business.Adobe.com resources

Docs links
Customer Profiles Audience Analytics Mobile Analytics Marketing Attribution Data Ingestion Marketing Analytics

On this page