Configuring Connect:Direct for UNIX for Server and Upgrade Management

Control Center Director upgrades and applies maintenance to Connect:Direct through a Connect:Direct Agent instance. You need a required level of maintenance in Connect:Direct software for Agent inclusion.

To successfully move to a Connect:Direct version that supports a Control Center Director deployment, there are a few scenarios to consider. Review the actions below in order to optimize your update experience:
  • Download the required maintenance version of Connect:Direct software. For more information go to Fix Central.
  • Certificate-based authentication is enabled when you install and configure Connect:Direct Secure Plus for UNIX.
  1. Configure the Agent listening port that Control Center Director will use to communicate with the Agent. 
    agent.port=<port> [Default:1365]
    The Agent is now set to automatically listen for incoming connections from Control Center Director.
    Attention: With multiple Connect:Direct instances on the same system you’re likely to run into port conflict issues unless you allocate a unique Agent listening port per instance.

    It is also recommended that having upgraded an instance, its unique port number must be applied before upgrading the next instance. This prevents potential errors that you could encounter during an upgrade process due to port conflict.

  2. Configure the Control Center Director Open Server Architecture (OSA) URL, the target location where Agent posts all the events to Control Center Director. 
    osa.rest.url=https;//<ip/hostname;port>/osa/events/post:
[Default:<blank>]
    Note: Ensure that you insert a ';' and not a ':' between hostname and port and after https.
  3. Set the following property to enable Agent to post all events to Control Center Director except when set to Y. 
    osa.disable=N
  4. Invoke the following script for changes to take effect. This script is available atcdinstallation_location/install/agent/bin. 
    startAgent.sh