DataFlowProbe.properties Parameters

long

string

HTTP or HTTPS (SSL)

Default: HTTPS

long

appilog.agent.Probe.BasicAuth.User

appilog.agent.Probe.BasicAuth.Pwd

string

All keys must be used to indicate usage of this feature. Values can be empty to represent non-values.

Password has to be encrypted. Encrypt password using the Probe JMX (that is, the getEncryptedKeyPassword operation in the MainProbe MBean).

string

Password has to be encrypted. Encrypt password using the Probe JMX (that is, the getEncryptedKeyPassword operation in the MainProbe MBean).

string

Default: ${DefaultDomain}

string

customer (default); external

The Probe Gateway name used for identification by the UCMDB server

The server uses this name to pass tasks to the appropriate Probe Gateway.

string

Uses the value defined during installation.

The default value is the machine name.

Specifies whether to enable support of UD Agent driven flow by Data Flow Probe.

Password has to be encrypted. Encrypt password using the Probe JMX (that is, the getEncryptedKeyPassword operation in the MainProbe MBean).

Default: 1977;
1979 for the second probe (if installed)

Enables using the default https server.

Starting with version 10.31, the default value for this setting is true for fresh installed probes of version 10.31 (or later). The HTTPS port 8453 is enabled for the Probe by default, and the HTTP port 1977 disabled. For details, see Using HTTPS Port 8453 as Default for Data Flow Probe.

Default: true

string

string

int

int

appilog.agent.
callhome.port

appilog.agent.local.jdbc.user

To change the DB password:

1. The out-of-the-box script set_dbuser_password.cmd can be used in order to change the password of the default PostgreSQL user.

2. The password value in the properties file should be encrypted. Encrypt the password using the Probe JMX (that is, getEncryptedKeyPassword operation in MainProbe MBean).

Default: org.postgresql.Driver

Default: jdbc:postgresql://localhost
/dataflowprobe

jdbc:postgresql://localhost:
5433/dataflowprobe for the second probe (if installed)

Default: jdbc:postgresql://localhost
/dataflowprobe

jdbc:postgresql://localhost:
5433/dataflowprobe for the second probe (if installed)

Default: jdbc:postgresql://localhost
/dataflowprobe

jdbc:postgresql://localhost:
5433/dataflowprobe for the second probe (if installed)

Default: jdbc:postgresql://localhost
/dataflowprobe

jdbc:postgresql://localhost:
5433/dataflowprobe for the second probe (if installed)

true - Probe GW process should also run a Probe Manager on same JVM.

false - Probe manager runs separately

Default: 1742;
1744 for the second probe (if installed)

Default: 1741;
1743 for the second probe (if installed)

true - Encrypted DomainScope document is stored on file system and internal DB.

false - Encrypted DomainScope document is retrieved from server each startup and stored only in memory.

probe.fips.status

Indicates which stage the probe is on in FIPS mode:
0 = NON-FIPS
1 = JCE is ready
2 = FIPS

resetObjectForSameCmdbIDOsh

When you import vector XML file by using a custom Jython job, if there are multiple CI objects having the same ID with different memory locations, setting resetObjectForSameCmdbIDOsh to true enables merging these CI objects into one CI object.

true - Results sent to the Server are stored in the database in a backup table.

false - Results are not stored in a backup table.

Default: 180000 msec (3 minutes)

The maximum objects of the touch results to be sent to the server each time.

probe.master.key

Specifies probe master key for password encryption purpose.

Default:
appilog.common.
system.types.vect
ors.ObjectStateHo
lderVector

Maximal number of worker threads which can be considered as stuck at the same time. When the number is reached, the Probe schedules a restart to release these threads.

true - The Probe Manager should detect stuck threads.

false - Otherwise.

The maximum number of remote processes allowed to be created during discovery. Remote processes are used to separate specific discovery from Probe process to prevent the Probe from possible memory issues.

Used, for example, in J2EE Discovery.

true - Send auto-delete notification to Server for aged objects, not discovered by the Probe.

false - Do not send.

true - Validate links are legal.

false - Do not validate links.

true - Filter results be predefined rules (CI types).

false - Otherwise.

true - Filter results which have been already sent to server.

false - Disable filter.

true - If CIs were ignored by reconciliation on a discovery cycle, as long as they have not undergone any changes, they are filtered by the Probe on subsequent discovery cycles, and a warning is displayed on the trigger CI level. To resend these objects, you must clear the results cache.

false - Even if CIs that were ignored by reconciliation, they are still sent to the UCMDB on each discovery cycle, together with new and updated CIs.

true - Fix direction of illegal links.

false - Otherwise.

true - Reports multiple update warnings to the UCMDB server.

true - DiscoveryAnalyzer is executed from Eclipse.

false - DiscoveryAnalyzer is not executed from Eclipse.

Default: 20000

appilog.collectors.
probemgr.DefaultResult
GroupMinTime

appilog.collectors.
probemgr.DefaultResult
GroupMaxObjs

Default min: 5000

Default max: 30000 (in ms.)

Relation between two keys: OR

Format: HH:MM

Values: 00:00-23:59

Default: 00:00

Format: HH:MM

Values: 00:00-23:59

Default: 00:00

Syntax: chcpCodeTo
CharasetName.
<code>=<encoding_name>

Example: chcpCodeTo
CharasetName.
932=MS932

Default: English Options: get=German

rus=Russian