|String||The path to your java environment.|
The local path to the data written and used by the Developer Console. The user executing it must have all rights to this path.
If you choose to store your console data inside an S3 bucket, this parameter is the base object in which the data will be stored
E.g: If I want to store my data at this path : s3://mybucket/path/to/dev/console, my VISUALDOOP_DATA parameter will be path/to/dev/console
Developer Console data are not the data you use with Indexima and your business intelligence tools. It is only data used by the Developer Console such as projects, users, saved queries,...
|Integer||The number of the port used to connect to the Developer Console via your internet browser.|
The authentication mode you want:
LDAP (Deprecated: replaced by Visualdoop/ldap.properties)
Set this variable to true if you connect to Indexima through a Knox gateway
Set this variable to "true" if you want to connect to the web console thru an HTTPS encrypted connection
|Integer||Set this variable to the port number you want to use for HTTPS connection to the web console. Used only if VISUALDOOP_SSL is true|
|String||Absolute path to the java Keystore used for TLS/SSL encryption. Used only if VISUALDOOP_SSL is true|
|String||Passphrase of the Keystore used for TLS/SSL encryption. Used only if VISUALDOOP_SSL is true|
VisualDoop Data storage on s3
If you want to store your dev console data on Amazon S3, Google Cloud Storage, or Azure Data Lake Storage, set this parameter to the desired value.
Possibles values are: S3, GS, ADLS respectively
The name of the bucket you want to use to store your Visualdoop data.
E.g: s3://mybucket/path/to/dev/console, VISUALDOOP_BUCKET will be mybucket
This parameter is used only if VISUALDOOP_STORE is set to S3 or GS
The AWS access key you want to use to access your data on S3. The account associated with this access key must have read and write rights on the bucket previously configured.
|The AWS secret key you want to use to access your data on S3. The account associated with this secret key must have read and write rights on the bucket previously configured.|
Define the admin users (comma separated)
could be LDAP users
|String||The host to which Developer Console must connect to run. Unless you use a very unusual and specific infrastructure, this value must stay be 0.0.0.0 if Developer Console is not installed on your personal computer.|