Set a specific IP address for a Groundplex node

Set the cc_secure_uri JVM option to specify a static advertised URL for a JCC node, enabling nodes in a Groundplex to discover each other using custom IP addresses or DNS hostnames.

Overview

On nodes with multiple IP addresses, the JCC service might autoselect the wrong interface for intra-node communication. Use cc_secure_uri to pin the advertised URI to a specific IP address or DNS hostname, ensuring that other nodes in the Groundplex always reach this node via the correct interface.

A common symptom of the wrong interface being selected is Unable to communicate alerts in the Dashboard, even when pipeline executions are unaffected.

JVM options chain

cc_secure_uri is a JCC process property. It must be nested inside the -Djvm_options parameter, which passes JCC-specific options through the Monitor process:

EXTRA_JVM_OPTIONS="$MONITOR_JVM_OPTIONS -Djvm_options=\"$EXTRA_JCC_JVM_OPTIONS\""

Where EXTRA_JCC_JVM_OPTIONS contains your JCC-specific settings, for example -Dcc_secure_uri=https://10.0.1.100:8081.

Important: cc_secure_uri must be configured per-node. Setting it via global.properties or any server-side global mechanism does not work.

Important: The port in cc_secure_uri must match the configured JCC secure port. The default JCC service port is 8081; the FeedMaster port is 8084.

Configure for VMs (RPM installation)

Set the environment variables in /etc/sysconfig/jcc (or the appropriate sysconfig file for your installation):

EXTRA_JCC_JVM_OPTIONS="-Dcc_secure_uri=https://10.0.1.100:8081"
EXTRA_JVM_OPTIONS="-Djvm_options=\"$EXTRA_JCC_JVM_OPTIONS\""

Note: Restart the node after changing this configuration.

Configure for Kubernetes

Set the environment variables in your pod specification:

env:
  - name: EXTRA_JVM_OPTIONS
    value: "-Djvm_options=\"-Dcc_secure_uri=https://jcc-node-1.example.com:8081\""

Or using separate variables for clarity:

env:
  - name: EXTRA_JCC_JVM_OPTIONS
    value: "-Dcc_secure_uri=https://jcc-node-1.example.com:8081"
  - name: EXTRA_JVM_OPTIONS
    value: "-Djvm_options=\"$(EXTRA_JCC_JVM_OPTIONS)\""

Configure for Docker Compose

environment:
  EXTRA_JVM_OPTIONS: "-Djvm_options=\"-Dcc_secure_uri=https://jcc-node-1.example.com:8081\""

Considerations

Per-node configuration: Each JCC node or pod must have a unique cc_secure_uri value corresponding to its own reachable address. The value must be configured independently for each instance.
DNS hostnames: Both IP addresses and DNS hostnames are supported. When using DNS, the hostname must resolve consistently to the same node — this value is used for node-to-node communication within the cluster. For autoscaling deployments, register the pod's DNS name dynamically at startup before the JCC process initializes.
Network reachability: The advertised URL must be reachable from all other nodes in the Groundplex cluster via HTTPS.
Port reachability on all interfaces: If JCC nodes are not reachable on the expected port, review the HTTP Interface setting in Node properties to control which network interfaces the JCC service node listens on.
Failover and backup interfaces: When switching from a primary to a backup network interface, update cc_secure_uri to the backup IP address or hostname, then restart the node for the change to take effect.