[/map {"- map/map "}) [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) About this guide (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) About this guide (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This guide describes how to configure and install Oracle Big Data Discovery. It also provides information on tasks you can perform after deployment and instructions for uninstalling the product. (shortdesc] (topicmeta] (topicref] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Introduction (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Introduction (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe Oracle Big Data Discovery and how it integrates with other software products. They also describe some of the different cluster configurations Big Data Discovery supports. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The Big Data Discovery software package (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The Big Data Discovery software package (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Oracle Big Data Discovery has a number of distinct components, which are installed simultaneously. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Integration with Hadoop (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Integration with Hadoop (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD runs on top of an existing Hadoop cluster, which provides a number of components and tools that BDD requires to process and manage data. For example, the Hadoop Distributed File System (HDFS) stores your source data and Hadoop Spark on YARN runs all Data Processing jobs. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Integration with WebLogic (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Integration with WebLogic (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) WebLogic Server provides a J2EE container for hosting and managing Studio and the Dgraph Gateway, which are J2EE applications. Additionally, WebLogic's Admin Server plays an important role in the installation process and administering BDD after installing. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Integration with Jetty (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Integration with Jetty (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Jetty provides an open-source javax.servlet container for hosting the Transform Service. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Cluster configurations and diagrams (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Cluster configurations and diagrams (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD supports many different cluster configurations. You should determine the one that best suits your needs before installing. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) A note about component names (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) A note about component names (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Some of the installation files and scripts may contain references to the Endeca Server, which is a legacy name for the Dgraph Gateway. This document refers to the component as the Dgraph Gateway, and notes any discrepancies to avoid confusion. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Prerequisites (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Prerequisites (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe the hardware and software requirements your environment must meet before you can install BDD. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Supported platforms (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Supported platforms (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following tables list the platforms and versions supported in each BDD release. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Hardware requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Hardware requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The hardware requirements for your BDD installation depend on the amount of data you will process. Oracle recommends the following minimum requirements: (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Memory requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Memory requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The amount of RAM your system requires depends on the amount of data you plan on processing. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Disk space requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Disk space requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Each type of BDD node has specific disk space requirements. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Network requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Network requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The hostname of each BDD machine must be externally-resolvable and accessible using the machine's IP address. Oracle recommends using only Fully Qualified Domain Names (FQDNs). (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Supported operating systems (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Supported operating systems (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD supports the following operating systems: (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Required Linux utilities (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Required Linux utilities (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The BDD installer requires several Linux utilities. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing the required Perl modules (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing the required Perl modules (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Three Perl modules are required on the install machine. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) OS user requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) OS user requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The entire installation must be performed by a single OS user, called the bdd user. After installing, this user will run all BDD processes. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling passwordless SSH (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling passwordless SSH (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You must enable passwordless SSH on all nodes in the cluster for the bdd user. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Hadoop requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Hadoop requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) One of the following Hadoop distributions must be running on your cluster before you install BDD: (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) YARN setting changes (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) YARN setting changes (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) To ensure that each YARN worker node has access to sufficient resources during processing, you need to update the following YARN-specific Hadoop properties. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Required Hadoop client libraries (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Required Hadoop client libraries (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD requires a number of client libraries to interact with Hadoop. When the installer runs, it adds these libraries to a single JAR, called the Hadoop fat JAR, which it then distributes to all BDD nodes. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Required HDP JARs (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Required HDP JARs (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have HDP, make sure that the following JAR files are present on all of your Hadoop nodes. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) MapR-specific requirements (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) MapR-specific requirements (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have MapR, your system must meet a few additional requirements. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Updating the YARN ResourceManager configuration (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating the YARN ResourceManager configuration (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have MapR, you must set the yarn.resourcemanager.hostname property in yarn-site.xml to the fully-qualified domain name (FQDN) of your YARN ResourceManager. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Applying the MapR patches (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Applying the MapR patches (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have MapR, you must apply three sets of patches to your Hadoop cluster before installing BDD. (shortdesc] (topicmeta] (topicref] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) JDK requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) JDK requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD requires one of the following JDK versions: (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Security options (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Security options (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe methods for securing your BDD cluster. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Kerberos (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Kerberos (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Kerberos network authentication protocol enables client/server applications to identify one another in a secure manner, even when communicating over an unsecured network. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Sentry (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Sentry (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Sentry provides role-based authorization in Hadoop clusters. Among other things, it can be used to restrict access to Hive data at a granular level. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) TLS/SSL (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) TLS/SSL (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD can be installed on Hadoop clusters secured with TLS/SSL. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) HDFS data at rest encryption (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) HDFS data at rest encryption (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) HDFS data at rest encryption allows data to be stored in encrypted HDFS directories called encryption zones. All files within an encryption zone are transparently encrypted and decrypted on the client side, meaning decrypted data is never stored in HDFS. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Other security options (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Other security options (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can further protect BDD by installing it behind a firewall and enabling TLS/SSL on Studio's outward-facing ports. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Dgraph database requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Dgraph database requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The data sets the Dgraph queries are stored in databases. For high availability, these can be stored on HDFS/MapR-FS or a shared NFS. They can also be stored on the local disk for a non-HA option. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) HDFS (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) HDFS (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Storing your databases on HDFS provides increased high availability for the Dgraph—the contents of the databases are distributed across multiple nodes, so the Dgraph can continue to process queries if a node goes down. It also increases the amount of data your databases can contain. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Setting up cgroups (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Setting up cgroups (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Control groups, or cgroups, are a Linux kernel feature that enable you to allocate resources like CPU time and system memory to specific processes or groups of processes. If you need to host the Dgraph on nodes running Spark, you should use cgroups to ensure sufficient resources are available to it. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing the HDFS NFS Gateway service (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing the HDFS NFS Gateway service (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have MapR, CDH 5.7.1, or HDFS data at rest encryption, and you want to store your Dgraph databases on HDFS, you must install the HDFS NFS Gateway service (called the MapR NFS service in MapR). (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing FUSE (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing FUSE (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Filesystem in Userspace (FUSE) enables unprivileged users to access filesystems without having to make changes to the kernel. In the context of BDD, it enables the Dgraph to read and write data to HDFS by making HDFS behave like a mountable local disk. The Dgraph supports FUSE 2.8+. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) NFS (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) NFS (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you don't want to store your databases on HDFS, you can keep them on a shared NFS. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Increasing the number of open file descriptors (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Increasing the number of open file descriptors (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Regardless of where you put your Dgraph databases, you must set the hard and soft limits on the number of open file descriptors to 65536, at a minimum. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Studio database requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Studio database requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio requires a relational database to store configuration and state, including component configuration, user permissions, and system settings. If you install with multiple Studio instances, all of them must be connected to the same database. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Sample commands for production databases (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Sample commands for production databases (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Below are sample commands you can use to create users and schemas for Oracle and MySQL databases. You are not required to use these exact commands when setting up your component databases—these are just examples to help get you started. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Supported Web browsers (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Supported Web browsers (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio supports the following Web browsers: (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Screen resolution requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Screen resolution requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD has the following screen resolution requirements: (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Studio support for iPad (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Studio support for iPad (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can use the Safari Web browser on an iPad running iOS 7+ to sign in to Studio and view projects. You cannot use an iPad to create, configure, or export projects. (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Prerequisite checklist (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Prerequisite checklist (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Before installing, run through the following checklist to verify you've satisfied all prerequisites. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) QuickStart Installation (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) QuickStart Installation (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The BDD installer includes a quickstart option, which installs the software on a single machine with default configuration suitable for a demo environment. You can use quickstart to install BDD quickly and easily, without having to worry about setting it up yourself. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing BDD with quickstart (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing BDD with quickstart (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you've satisfied all of BDD's prerequisites, you can download and install the software. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Single-Node Installation (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Single-Node Installation (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you want to demo BDD before committing to a full-cluster installation, you can install it on a single node. This gives you the chance to learn more about the software and see how it performs on a smaller scale. The following sections describe how to get BDD running on your machine quickly and easily. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing BDD on a single node (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing BDD on a single node (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you've satisfied all of BDD's prerequisites, you can download and install the software. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring a single-node installation (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring a single-node installation (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The table below describes the properties you should set for a single-node installation. You can modify bdd.conf in any text editor. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Cluster Installation (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Cluster Installation (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe how to install BDD on multiple nodes, and provide tips on troubleshooting a failed installation. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The BDD installer (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The BDD installer (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD uses a single script to install and deploy its components all at once. When the script finishes, BDD will be completely installed, and your cluster will be up and running. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Silent installation (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Silent installation (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can optionally run the installer in silent mode. This means that instead of prompting you for information it requires at runtime, it obtains that information from environment variables you set beforehand. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installer behavior (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installer behavior (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The diagram below illustrates the behavior of the installer. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Setting up the install machine (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Setting up the install machine (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The first step in the installation process is to set up the install machine. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Downloading the BDD media pack (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Downloading the BDD media pack (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you set up the install machine, you can download the BDD media pack from the Oracle Software Delivery Cloud. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Downloading a WebLogic Server patch (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Downloading a WebLogic Server patch (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can optionally download a WebLogic Server patch for the installer to apply when it runs. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring BDD (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring BDD (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you download the required Hadoop client libraries, you must configure your installation by updating the bdd.conf file, which is located in the /<installation_src_dir>/installer directory. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Required settings (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Required settings (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The first part of bdd.conf contains required settings. You must update these with information specific to your system, or the installer could fail. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Running the prerequisite checker (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Running the prerequisite checker (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Before installing, you should run the prerequisite checker script to determine whether all requirements have been satisfied. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing BDD on a cluster (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing BDD on a cluster (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you update bdd.conf and verify that you satisfied all prerequisites, you can install BDD. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Troubleshooting a Failed Installation (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Troubleshooting a Failed Installation (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If the installer fails, you can use its console output and log files to determine why. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Failed ZooKeeper check (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Failed ZooKeeper check (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The installer will fail if it can't connect to the ZooKeeper. This can occur if the ZooKeeper crashes during the installation. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Failure to download the Hadoop client libraries (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Failure to download the Hadoop client libraries (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have CDH, the installer will fail if it can't download the required Hadoop client libraries. This can occur if you don't have an internet connection, or if some of the libraries are missing or incomplete. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Failure to generate the Hadoop fat JAR (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Failure to generate the Hadoop fat JAR (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have HDP, the installer will fail if it's unable to generate the Hadoop fat JAR. This can occur if it can't find the ojdbc6.jar file. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Rerunning the installer (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Rerunning the installer (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you have fixed the errors that caused the installer to fail, you can reinstall BDD. (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Post-Installation Tasks (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Post-Installation Tasks (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe tasks you can perform after you install BDD, such as verifying your installation and increasing Linux file descriptors. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying your installation (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying your installation (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once the installer completes, you can verify that each of the major BDD components were installed properly and are running. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying your cluster's health (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying your cluster's health (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use the bdd-admin script to verify the overall health of your cluster. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying Data Processing (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying Data Processing (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) To verify that Data Processing is running, you must launch a Data Processing workflow. You can do this in two ways: (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Navigating the BDD directory structure (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Navigating the BDD directory structure (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Your BDD installation consists of two main directories: $BDD_HOME and $DOMAIN_HOME. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling Kerberos for the Transform Service (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling Kerberos for the Transform Service (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you have Kerberos, you need to manually enable it for the Transform Service after installing. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio and the Transform Service require load balancing when installed on multiple nodes. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing for Studio (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing for Studio (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you installed Studio on multiple nodes, you need to set up a load balancer in front of them to ensure that user requests are always routed to available nodes. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing for the Transform Service (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing for the Transform Service (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you installed the Transform Service on multiple nodes, you need to set up a load balancer in front of them. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Updating the DP CLI whitelist and blacklist (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating the DP CLI whitelist and blacklist (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) In order to create data sets from existing Hive tables, you must update the DP CLI white- and blacklists that define which tables are processed by Data Processing. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Signing in to Studio as an administrator (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Signing in to Studio as an administrator (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you complete the BDD installation and deployment, you can sign in to Studio as an administrator, begin to create new users, explore data sets, re-configure Studio settings as necessary, and so on. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Backing up your cluster (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Backing up your cluster (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Oracle recommends that you back up your BDD cluster immediately after deployment. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Replacing certificates (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Replacing certificates (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Enabling SSL for Studio activates WebLogic Server's default Demo Identity and Demo Trust Keystores. As their names suggest, these keystores are untrusted and meant for demo purposes only. After deployment, you should replace them with your own certificates. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Increasing Linux file descriptors (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Increasing Linux file descriptors (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You should increase the number of file descriptors from the 1024 default. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Customizing the WebLogic JVM heap size (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Customizing the WebLogic JVM heap size (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can change the default JVM heap size to fit the needs of your deployment. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring Studio database caching (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring Studio database caching (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) All Studio instances are automatically configured to use synchronized database caching, so that information cached on one instance is available to the others. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Customizing Studio database caching (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Customizing Studio database caching (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can customize Studio's database cache configuration, if needed. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Disabling Studio database caching (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Disabling Studio database caching (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Database caching is enabled for Studio by default. This provides better network efficiency for most clusters, but can in some cases cause issues in Studio. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Clearing the Studio database cache (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Clearing the Studio database cache (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) As part of troubleshooting issues with Studio, you can clear the cache for either a single Studio instance or the entire Studio cluster. (shortdesc] (topicmeta] (topicref] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Using Studio with a Reverse Proxy (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Using Studio with a Reverse Proxy (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio can be configured to use a reverse proxy. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About reverse proxies (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About reverse proxies (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) A reverse proxy provides a more secure way for users to get access to application servers by retrieving resources on behalf of a client from one or more servers and returning them to the client as though they came from the server itself. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Types of reverse proxies (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Types of reverse proxies (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Reverse proxies may be either devices/appliances or specially configured web servers. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Example sequence for a reverse proxy request (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Example sequence for a reverse proxy request (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Here is an example of the typical sequence for a request processed using a reverse proxy server. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Recommendations for reverse proxy configuration (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Recommendations for reverse proxy configuration (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Here are some general configuration recommendations for setting up a reverse proxy. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Preserving HTTP 1.1 Host: headers (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Preserving HTTP 1.1 Host: headers (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) HTTP 1.1 requests often include a Host: header, which contains the hostname from the client request. This is because a server may use a single IP address or interface to accept requests for multiple DNS hostnames. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling the Apache ProxyPreserveHost directive (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling the Apache ProxyPreserveHost directive (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The ProxyPreserveHost directive is used to instruct Apache mod_proxy, when acting as a reverse proxy, to preserve and retain the original Host: header from the client browser when constructing the proxied request to send to the target server. (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Reverse proxy configuration options for Studio (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Reverse proxy configuration options for Studio (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Here are some options for configuring reverse proxy for Studio. (shortdesc] (topicmeta][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Simple Studio reverse proxy configuration (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Simple Studio reverse proxy configuration (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Here is a brief overview of a simple reverse proxy configuration for Studio. The configuration preserves the Host: header, and does not use SSL or path remapping. Studio only supports matching context paths. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Studio reverse proxy configuration without preserving Host: headers (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Studio reverse proxy configuration without preserving Host: headers (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If a reverse proxy used by Studio does not preserve the Host: header, and instead makes a request with a Host: header referring to the target application server, Studio and the application server receive an incorrect hostname. This causes Studio to generate absolute URLs that refer to the proxied application server instead of to the reverse proxy server. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring Studio to support an SSL-enabled reverse proxy (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring Studio to support an SSL-enabled reverse proxy (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If Studio is installed behind a reverse proxy that has SSL capabilities, and the client SSL is terminated on the reverse proxy, you must configure Studio to set the preferred protocol to HTTPS, and provide the host and port for the reverse proxy server. (shortdesc] (topicmeta] (topicref] (topicref] (topicref] (topichead] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Uninstallation (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Uninstallation (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes how to uninstall BDD. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The uninstallation script (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The uninstallation script (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You uninstall BDD by running the uninstall.sh script, which is located in $BDD_HOME/uninstall. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Running the uninstallation script (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Running the uninstallation script (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You uninstall BDD by running uninstall.sh from the Admin Server. (shortdesc] (topicmeta] (topicref] (topicref] (topichead][/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicmeta {"- map/topicmeta "}) [/map/topichead/topicmeta/navtitle {"- topic/navtitle "}) (navtitle] (topicmeta][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Optional and Internal BDD Properties (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Optional and Internal BDD Properties (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe the optional and internal properties in bdd.conf. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Optional settings (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Optional settings (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The second part of bdd.conf contains optional properties. You can update these if you want, but the default values will work for most installations. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Internal settings (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Internal settings (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The third part of bdd.conf contains internal settings either required by the installer or intended for use by Oracle Support. Note that the installer will automatically add properties to this section when it runs. (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Conventions (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Conventions (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following conventions are used in this document. (shortdesc] (topicmeta] (topicref] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Copyright and disclaimer (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Copyright and disclaimer (linktext] (topicmeta] (topicref] (map]