4. Minimal Configuration

The minimal DCC configuration is pretty close to the default one, included in the sample configuration file. It assumes DCC will be running on the same host as Promptar Server and that Promptar Server itself will launch and terminate DCC along with its own initialization and finalization stages.

To obtain that, all that is needed is to copy the sample configuration file, under the platform specific configuration directory, to the actual configuration file. In other words, copying prptDCC.conf.sample to prptDCC.conf. Then, proceed to adjusting the logging and data configuration.

Open the prptDCC.conf file and scroll down to the [log] section. You should find the following:

[log]

; Recommended configuration
; -------------------------
; type  = file
; file  = /var/log/promptar/prptDCC.log
; file  = C:/Program Files/Promptar Desktop Client Connector/Log/prptDCC.log
; file  = C:/Program Files (x86)/Promptar Desktop Client Connector/Log/prptDCC.log
; file.rotate.when      = 1 midnight
; file.rotate.count     = 7
; level                 = warning

Uncomment the lines starting with type, file and level, depending on whether you’re on a Linux or Windows host, paying particular attention the the lines starting with file, pointing to the path of the log file. The recommended configuration ensures daily log file rotation while keeping 7 days worth of history. If you want to change these settings, please check the comments preceding these lines in the sample configuration file.

Then scroll down to the [data] section where you will find:

[data]

; Recommended configuration
; -------------------------
; location = /var/lib/promptar/prptDCC
; location = C:/Program Files/Promptar Desktop Client Connector/data
; location = C:/Program Files (x86)/Promptar Desktop Client Connector/data

Again, uncomment the location line appropriate to your environment and finish up by saving the file.

If you are in the process of initial Promptar Server setup, this is all that is needed.

Enabling TLS

 

For full backwards compatibility, Transport Layer Security is not enabled by default.

To do that, please refer to the next section’s Enabling TLS chapter.