ADP ES configuration parameters
This article describes the parameters that can be configured for ADP ES services via ADCM. To read about the configuring process, refer to the relevant article Configure services.
|
NOTE
Some of the parameters become visible in the ADCM UI after the Show advanced flag being set.
|
AD Eureka
| Parameter | Description | Default value |
|---|---|---|
port |
AD Eureka listening port. It can only be set during installation. The AD Eureka web interface is available on this port |
8761 |
Xmx ram parameter |
Defines the maximum Java heap size for the service in gigabytes |
1 |
Log level |
A logging level of messages written to log files. Possible values: |
INFO |
ADВМ
| Parameter | Description | Default value |
|---|---|---|
Xmx ram parameter |
Defines the maximum Java heap size for the service in gigabytes |
1 |
Log level |
A logging level of messages written to log files. Possible values: |
INFO |
ADP Control
| Parameter | Description | Default value |
|---|---|---|
Username |
The database username |
adpgc |
Password |
The database password. It is specified during installation |
— |
| Parameter | Description | Default value |
|---|---|---|
Admin’s password |
The ADP Control administrator password. It is specified during installation. The administrator is the automatically created user — |
— |
| Parameter | Description | Default value |
|---|---|---|
Listening WEB UI port |
The port on which the ADP Control web UI is available. It is specified during installation |
8090 |
Xmx ram parameter |
Defines the maximum Java heap size for the service in gigabytes |
1 |
Log level |
A logging level of messages written to log files. Possible values: |
INFO |
Database
| Parameter | Description | Default value |
|---|---|---|
Data directory |
The directory that is used to store PostgreSQL data. It can be changed only during installation |
/pg_data1 |
Chrony
| Parameter | Description | Default value |
|---|---|---|
NTP servers |
Addresses of valid NTP servers. For example, |
— |