run_universal_connector

Enables the Guardium universal connector on the local or specified collectors.

This API is available in Guardium V11.3 and later.

REST API syntax

This API is available as a REST service with the GET method. Call this API as follows: 
GET https://[Guardium hostname or IP address]:8443/restAPI/runUniversalConnector

GuardAPI syntax

run_universal_connector parameter=value

Parameters

Parameter Value type Description
overwrite_old_instance Boolean Determines whether to overwrite the container (erase all saved data and restart the Guardium universal connector).Valid values:
  • 0 (false)
  • 1 (true)

Default = 0 (false)
uc_debug_level String Valid values:
  • all
  • debug
  • info
  • warn
  • error
  • fatal
  • off
  • trace
api_target_host String

Specifies the target hosts where the API executes. Valid values:
  • all_managed: execute on all managed units but not the central manager
  • all: execute on all managed units and the central manager
  • group:<group name>: execute on all managed units identified by <group name>
  • host name or IP address of a managed unit: specified from the central manager to execute on a managed unit.  For example, api_target_host=10.0.1.123.
  • host name or IP address of the central manager: specified from a managed unit to execute on the central manager. For example, api_target_host=10.0.1.123.

IP addresses must conform to the IP mode of your network. For dual IP mode, use the same IP protocol with which the managed unit is registered with the central manager. For example, if the registration uses IPv6, specify an IPv6 address. The hostname is independent of IP mode and can be used with any mode.

Examples

To start the Guardium universal connector on your local Guardium system:
grdapi run_universal_connector
ID=0
Universal-Connector container was started
ok