[/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, install, and deploy the Oracle Big Data Discovery product. 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/topicmeta {"- map/topicmeta "}) [/map/topichead/topicmeta/navtitle {"- topic/navtitle "}) Before You Install (navtitle] (topicmeta][/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 deployment 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 is comprised of a number of separate components, which are installed and deployed simultaneously. These components are described below. (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 of Big Data Discovery with Cloudera Distribution for Hadoop (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Integration of Big Data Discovery with Cloudera Distribution for Hadoop (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Cloudera Distribution for Hadoop (CDH) provides a number of Hadoop-related components and tools that BDD requires to process and manage data. CDH 5.3.0 must be installed on your system before you install BDD. (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 of Big Data Discovery with WebLogic (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Integration of Big Data Discovery with WebLogic (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The WebLogic Server provides a J2EE container for hosting and managing the Studio and Dgraph Gateway J2EE applications. Additionally, WebLogic's Admin Server plays an important role in the installation process, as well as BDD administration 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 "}) Deployment configurations and diagrams (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Deployment configurations and diagrams (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Big Data Discovery supports many different deployment configurations. Before installing, you can configure your deployment to have one that best supports your needs. This topic describes three types of deployments suitable for demonstration purposes, development, and production. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Big Data Discovery administration (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Big Data Discovery administration (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After deployment, you have two options for administering Big Data Discovery: the bdd-admin script and Oracle Enterprise Manager. (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 in Big Data Discovery (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Security in Big Data Discovery (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD does not currently support SSL for the inward-facing ports between its components. Oracle therefore recommends that you deploy Big Data Discovery behind a firewall. (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 or the Hadoop Exporter. These are legacy names for the Dgraph Gateway and HDFS Agent, respectively. This document refers to the components by their official names, and will make a note of 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 system 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 "}) CDH requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) CDH requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) CDH 5.3.0 must be installed on your system before you install BDD. The table below describes the specific CDH components BDD requires. (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 specific BDD deployment 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 "}) User access requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) User access requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following must be configured for the user who will perform 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 "}) Physical memory and disk space requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Physical memory and disk space requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Each type of node has different physical memory and 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 "}) Software requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Software requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD has a number of software requirements. Many of these requirements must be met by all nodes in the cluster, while others only need to be met by node of a specific type. If you are installing on a single node, that node must meet all 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 "}) 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] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Database requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) 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. All Studio instances must be able to connect and write 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 a production database (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Sample commands for a production database (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections contain 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 database—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 "}) Index requirements (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Index requirements (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Dgraph requires an index to store the contents of the data sets it can query. All Dgraph nodes in the cluster must be able to connect to the index. (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 browsers (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Supported browsers (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD supports the following browsers: (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicmeta {"- map/topicmeta "}) [/map/topichead/topicmeta/navtitle {"- topic/navtitle "}) Installation and Deployment (navtitle] (topicmeta][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Overview (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Overview (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe the BDD installer and its behavior, as well as the high-level steps involved in the installation and deployment process. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The orchestration script (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The orchestration script (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) BDD uses a single script, called the orchestration 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] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installation and deployment workflow (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installation and deployment workflow (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you have verified that your cluster satisfies all of BDD's pre-installation requirements, you can begin installing the software. At a high level, this involves the following steps: (shortdesc] (topicmeta] (topicref] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Installing and Deploying Big Data Discovery (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Installing and Deploying Big Data Discovery (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe the full installation and deployment process, from selecting the Admin Server to running the installer. They also provide tips for troubleshooting a failed installation and instructions on rerunning the installer. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Selecting the Admin Server (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Selecting the Admin Server (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The first step in the installation and deployment process is to select a machine to be the Admin Server and verify that it meets all requirements specific to the Admin 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 "}) 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 "}) Once you have selected the Admin Server, 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 "}) Creating the installation source directory (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating the installation source directory (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you have downloaded the BDD media pack, you need to create the installation source directory. This is the location from which you will run the orchestration script, as well as the uninstallation script should you choose to uninstall 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 "}) Updating the configuration file (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating the configuration file (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you have created the installation source directory, you must configure your deployment by updating the bdd.conf file, which is located in the /BDD_deployer/installer directory. (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 orchestration script (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Running the orchestration script (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you have updated bdd.conf, you can install and deploy BDD by running the orchestration script from the Admin 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 "}) Troubleshooting orchestration script problems (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Troubleshooting orchestration script problems (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If the orchestration script fails, use its console output and log files to determine the cause of the failure. (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 orchestration script (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Rerunning the orchestration script (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you have fixed the errors that caused the orchestration script to fail, you can reinstall BDD. To do this, you must first run the uninstallation script, set the FORCE property in bdd.conf to TRUE, and rerun the orchestration script. (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topichead {"+ map/topicref mapgroup-d/topichead "}) [/map/topichead/topicmeta {"- map/topicmeta "}) [/map/topichead/topicmeta/navtitle {"- topic/navtitle "}) After You Install (navtitle] (topicmeta][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Post-Deployment Tasks (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Post-Deployment Tasks (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe tasks you can perform after you install and deploy 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 "}) 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 "}) The BDD installation and deployment process adds a number of new directories to your system. The following sections describe these directories and their contents. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying your deployment (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying your deployment (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once the orchestration script 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 the deployed services (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying the deployed services (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use the bdd-admin script to verify the statuses of the Dgraph, HDFS Agent, Studio, and Dgraph Gateway services. (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 "}) Updating the CLI whitelist and blacklist (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating the 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 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 BDD (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Backing up BDD (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Oracle recommends that you back up BDD after deployment. This procedure must be performed manually. (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] (topicref][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating Multiple Studio Instances (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Creating Multiple Studio Instances (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) For a larger production environment, you may want to configure a number of Studio instances. (shortdesc] (topicmeta][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About multiple Studio instances (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About multiple Studio instances (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio allows you to create multiple Studio instances. In a cluster of Studio instances, changes made to one instance are automatically made to the other instances. For a large production environment, using clustering provides redundancy and support for higher throughput, allowing for more concurrent users. (shortdesc] (topicmeta] (topicref][/map/topichead/topicref/topicref {"- map/topicref "}) [/map/topichead/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Setting up multiple Studio instances (navtitle][/map/topichead/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Setting up multiple Studio instances (linktext][/map/topichead/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) To configure multiple Studio instances, you connect each instance to the same application database, and then configure a shared cache for those instances. (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 Studio instances (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Installing the Studio instances (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Each instance in the cluster of Studio nodes is first installed as a standalone instance and then modified to share certain configuration. (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 synchronized caching for the Studio instances (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring synchronized caching for the Studio instances (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio instances in a multiple node environment must use synchronized caching. (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 "}) About synchronized caching (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About synchronized caching (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Synchronized caching ensures that the information cached by one Studio instance is available to all of the Studio instances in the environment. (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 "}) Updating portal-ext.properties to synchronize caching for Studio instances (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating portal-ext.properties to synchronize caching for Studio instances (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The portal-ext.properties file for each instance includes commented-out settings for synchronizing the caches for Studio instances. (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 "}) Customizing the shared cache configuration files (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Customizing the shared cache configuration files (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The default versions of the shared cache configuration files should work in most cases. However, you can if needed create and deploy customized versions. (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 "}) Clearing the cache for multiple Studio instances (navtitle][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Clearing the cache for multiple Studio instances (linktext][/map/topichead/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) As part of troubleshooting issues with a multi-instance Studio implementation, you can clear the cache for Studio instances. From the Studio Control Panel, you can clear the cache for either the current instance or for the entire Studio cluster. (shortdesc] (topicmeta] (topicref] (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. (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 "}) What is a reverse proxy? (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) What is a reverse proxy? (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) A reverse proxy retrieves resources on behalf of a client from one or more servers, and then returns these resources to the client as though they came from the server itself. (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 "}) Types of reverse proxies (navtitle][/map/topichead/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Types of reverse proxies (linktext][/map/topichead/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Reverse proxies may be either devices/appliances or specially configured web servers. (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 "}) 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/topicmeta {"- map/topicmeta "}) [/map/topichead/topicmeta/navtitle {"- topic/navtitle "}) Uninstalling Big Data Discovery (navtitle] (topicmeta][/map/topichead/topicref {"- map/topicref "}) [/map/topichead/topicref/topicmeta {"- map/topicmeta "}) [/map/topichead/topicref/topicmeta/navtitle {"- topic/navtitle "}) Uninstalling Big Data Discovery (navtitle][/map/topichead/topicref/topicmeta/linktext {"- map/linktext "}) Uninstalling Big Data Discovery (linktext][/map/topichead/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following sections describe how to uninstall BDD using the uninstallation script. (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 can uninstall BDD by running the uninstall.sh script. This script deletes all BDD components, including all services, the Data Processing libraries, and the contents of the $ORACLE_HOME directory. (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 can uninstall BDD by running the uninstall.sh from the Admin Server. (shortdesc] (topicmeta] (topicref] (topicref] (topichead] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Conventions used in this document (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Conventions used in this document (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]