Updating the configuration file

• BDA: Use this value if you're installing on the Oracle Big Data Appliance.
• GENERIC: Use this value if you're installing on general-purpose hardware. This is the default value.
• OPC: Use this value if you're installing on the Oracle Public Cloud.

Note that this document does not cover BDA or Cloud installation. For information on installing on either platform, please contact Oracle Customer Support.

If you're deploying to a single machine, use FALSE. When deploying to a single machine, you should also be sure that the MANAGED_SERVERS, DGRAPH_SERVERS, and DETECTOR_SERVER properties are set to ${ADMIN_SERVER}, or the orchestration script will fail.

Note that this property only accepts UPPERCASE values.

When set to TRUE, the orchestration script removes any previous installations from the ORACLE_HOME directory. Use this value if you're rerunning the script after a failed attempt.

When set to FALSE, the orchestration script does not remove any previous installations. If one exists, the script will fail. This is the default value.

Note that this property only accepts UPPERCASE values.

On the Admin Server and nodes that will host WebLogic Server, this directory must contain at least 6GB of free space. Nodes that will host the Dgraph require 1GB of free space, and those that will host Data Processing require 2GB.

The default value is /localdisk/Oracle/Middleware.

If any other Oracle software products are installed on the machine, this file will already exist. You should update this value to point to that file.

• TRUE: WebLogic (including Studio and the Dgraph Gateway), the Dgraph, and the HDFS Agent will automatically restart after their host servers are rebooted. This is the default value.
• FALSE: WebLogic, the Dgraph, and the HDFS Agent must be restarted manually.

Note that this property only accepts UPPERCASE values.

On the Admin Server and nodes that will host WebLogic Server or the Dgraph, this directory must contain at least 10GB of free space. Nodes that will host Data Processing require 3GB of free space.

If set to prod, the WebLogic Server starts in production mode, which requires a username and password when it starts. This is the default value.

If set to dev, it starts in development mode, which does not require a username or password. The orchestration script will still prompt you for a username and password at runtime, but these will not be required when starting WebLogic Server.

Note that this property only accepts lowercase values.

There is no default value for this property, so you must provide one. Be sure to provide a value for this property, as the installation script will fail if it is not set.

If you're installing on a single machine, this property should be set to ${ADMIN_SERVER}, or the orchestration script will fail.

This property is still required if you are installing on a single server.

This property does not set the number of CPU cores that the WebLogic Server will actually use.

Instead, the orchestration script uses the value for this property at runtime to check whether each of the machines has the minimum number of CPU cores required on each Managed Server.

The value you enter should be less than or equal to the number of CPU cores available on the node. If you are unsure of how many cores a node has, check its node file.

If you enter a value that is greater than the total number of cores available on the node, the script issues a warning but continues to run. If you do not specify a number for this property, the script uses the default value of 4.

This property does not set the RAM size that the WebLogic Server will actually use.

Instead, the orchestration script uses the value for this property at runtime to check whether each of the machines has the minimum amount of RAM available on each Managed Server, in KB.

The value you enter (in KB) should be less than or equal to the total amount of RAM available on the node. If you are unsure of how much RAM a node has, check its node file.

If you enter a value that is greater than the total amount of RAM available on the node, the script issues a warning but continues to run. If you do not specify a value for this property, the script uses the default value of 2048000 KB.

This can be set to TRUE or FALSE. When set to TRUE, the Studio instances on the Admin Server and the Managed Servers listen for requests on the ADMIN_SERVER_SECURE_PORT and MANAGED_SERVER_SECURE_PORT, respectively.

The default value is TRUE. Note that this property does not enable SSL for any other BDD components.

Note that when SSL is enabled, Studio still listens on the un-secure ADMIN_SERVER_PORT for requests from the Dgraph Gateway.

Note that when SSL is enabled, Studio still listens on the un-secure MANAGED_SERVER_PORT for requests from the Dgraph Gateway.

• DEBUG
• INFO
• WARN
• ERROR
• FATAL

The default value is ERROR.

More information on Dgraph Gateway log levels is available in the Oracle Big Data Discovery Administrator's Guide.

jdbc:mysql://<database hostname>:<port number>/<database name>?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false

jdbc:oracle:thin:@<database hostname>:<port number>:<database SID>

The third template is for Hypersonic databases, which use the org.hsqldb.jdbcDriver driver. Hypersonic is not supported for production environments, so you should only use this instance if you are deploying to a demo environment. If you want the orchestration script to create a Hypersonic database for you, uncomment this template and comment out the other two. The orchestration script will create the database for you in the location defined by the URL.

This list cannot contain duplicate values. Additionally, as Oracle does not recommend cohosting the Dgraph with Spark, this list should not contain hostnames of Spark nodes.

If you're installing on a single machine, this property should be set to ${ADMIN_SERVER}, or the orchestration script will fail.

This property does not set the number of cores that the Dgraph will actually use.

Instead, the orchestration script uses the value for this property at runtime to check whether each of the machines has the minimum number of CPU cores required for hosting the Dgraph and the HDFS Agent.

The value you enter should be less than or equal to the number of cores available on the machine.

If you enter a value that is greater than the total number of cores available on the Dgraph nodes, the script issues a warning but continues to run.

If you do not specify a number for this property, the orchestration script uses the default value of 2 cores.

This property does not set the RAM size that the Dgraph will actually use.

Instead, the orchestration script uses the value for this property (in KB) at runtime to check whether each of the machines has the minimum amount of RAM required on nodes hosting the Dgraph and the HDFS Agent.

The value you enter should be less than or equal to the total amount of RAM available on the node.

If you enter a value that is greater than the total amount of RAM available on the Dgraph nodes, the script issues a warning but continues to run.

If you do not specify a number for this property, the orchestration script uses the default value of 2048000 KB.

If you are installing with an existing index, move the index to the directory defined by DGRAPH_INDEX_DIR and change the value of this property to the name of the index you are using. If the index does not exist in the DGRAPH_INDEX_DIR location, the orchestration script will fail.

Do not include _indexes in the index's name. For example, if you have an index named product_indexes, you should only specify product.

• For machines running only the Dgraph, the number of threads should be equal to the number of CPU cores on the machine.
• For machines running the Dgraph and other BDD components, the number of threads should be the number of CPU cores minus 2. For example, a machine with 4 cores should have 2 threads.

Be sure that the number you use is in compliance with the licensing agreement.

You only need to specify the number of MB to allocate to the cache. For example, a value of 50 sets the cache size to 50MB.

For enhanced performance, Oracle recommends allocating at least 50% of the node's available RAM to the Dgraph cache. If you later find that queries are getting cancelled because there is not enough available memory to process them, experiment with gradually decreasing this amount.

Note that this property is not related to the Dgraph index.

The default value is bdd.

If you are installing on a single machine, this property should be set to ${ADMIN_SERVER}, or the orchestration script will fail.

The default value is default. This is the same as the default value of HIVE_DATABASE_NAME, which is used by Studio and the CLI. It is possible to use different databases for these properties, but it is recommended that you start with one for a first time installation.

When set to true, all of the data enrichments run, and when set to false, none of them run. The default value is true.

For more information on data enrichments, see the Data Processing Guide.

Note that this property is not the same as JAVA_HOME.

Note that the actual number of records in each data set will sometimes be slightly more than or slightly less than the value of MAX_RECORDS.

The default value is 1000000.

The value of this property must be equal to or less than the value of Spark's Total Java Heap Sizes of Worker's Executors in Bytes (executor_total_max_heapsize) property. To access the executor_total_max_heapsize property, open Cloudera Manager and select Clusters > Spark (Standalone), click the Configuration tab, and select the Worker Default Group category.

A language code requires more processing but produces better processing and indexing results by using OLT libraries for the specified language. If the value is unknown, the processing time is faster but the processing and indexing results are more generic and OLT is not invoked.

The default value is unknown.

The default value is default. This is the same as the default value of DETECTOR_HIVE_DATABASE, which is used by the Hive Table Detector. It is possible to use different databases for these properties, but it is recommended that you start with one for a first time installation.