[/map
{"- map/map "})
[/map/title
{"- topic/title "}) After You Install (title][/map/topicref
{"- map/topicref "}) [/map/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Post-Deployment Tasks (navtitle][/map/topicref/topicmeta/linktext
{"- map/linktext "}) Post-Deployment Tasks (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Navigating the BDD directory structure (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Navigating the BDD directory structure (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Verifying your deployment (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Verifying your deployment (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Verifying the deployed services (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Verifying the deployed services (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Verifying Data Processing (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Verifying Data Processing (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Updating the CLI whitelist and blacklist (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Updating the CLI whitelist and blacklist (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Signing in to Studio as an administrator (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Signing in to Studio as an administrator (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Backing up BDD (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Backing up BDD (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Replacing certificates (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Replacing certificates (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Increasing Linux file descriptors (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Increasing Linux file descriptors (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) You should increase the number of file descriptors from the 1024 default. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Customizing the WebLogic JVM heap size (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Customizing the WebLogic JVM heap size (linktext][/map/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/topicref
{"- map/topicref "}) [/map/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Creating Multiple Studio Instances (navtitle][/map/topicref/topicmeta/linktext
{"- map/linktext "}) Creating Multiple Studio Instances (linktext][/map/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) For a larger production environment, you may want to configure a number of Studio instances. (shortdesc] (topicmeta][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) About multiple Studio instances (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) About multiple Studio instances (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Setting up multiple Studio instances (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Setting up multiple Studio instances (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Installing the Studio instances (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Installing the Studio instances (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Configuring synchronized caching for the Studio instances (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Configuring synchronized caching for the Studio instances (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Studio instances in a multiple node environment must use synchronized caching. (shortdesc] (topicmeta][/map/topicref/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) About synchronized caching (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) About synchronized caching (linktext][/map/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/topicref/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Updating portal-ext.properties to synchronize caching for Studio instances (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Updating portal-ext.properties to synchronize caching for Studio instances (linktext][/map/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/topicref/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Customizing the shared cache configuration files (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Customizing the shared cache configuration files (linktext][/map/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/topicref/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Clearing the cache for multiple Studio instances (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Clearing the cache for multiple Studio instances (linktext][/map/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/topicref
{"- map/topicref "}) [/map/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Using Studio with a Reverse Proxy (navtitle][/map/topicref/topicmeta/linktext
{"- map/linktext "}) Using Studio with a Reverse Proxy (linktext][/map/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Studio can be configured to use a reverse proxy. (shortdesc] (topicmeta][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) About reverse proxies (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) About reverse proxies (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) What is a reverse proxy? (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) What is a reverse proxy? (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Types of reverse proxies (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Types of reverse proxies (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Reverse proxies may be either devices/appliances or specially configured web servers. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Example sequence for a reverse proxy request (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Example sequence for a reverse proxy request (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Recommendations for reverse proxy configuration (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Recommendations for reverse proxy configuration (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Here are some general configuration recommendations for setting up a reverse proxy. (shortdesc] (topicmeta][/map/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Preserving HTTP 1.1 Host: headers (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Preserving HTTP 1.1 Host: headers (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Enabling the Apache ProxyPreserveHost directive (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Enabling the Apache ProxyPreserveHost directive (linktext][/map/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/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Reverse proxy configuration options for Studio (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Reverse proxy configuration options for Studio (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Here are some options for configuring reverse proxy for Studio. (shortdesc] (topicmeta][/map/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Simple Studio reverse proxy configuration (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Simple Studio reverse proxy configuration (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Studio reverse proxy configuration without preserving Host: headers (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Studio reverse proxy configuration without preserving Host: headers (linktext][/map/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/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Configuring Studio to support an SSL-enabled reverse-proxy (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Configuring Studio to support an SSL-enabled reverse-proxy (linktext][/map/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] (map]