[/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-Installation Tasks (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Post-Installation Tasks (linktext][/map/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/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying your installation (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying your installation (linktext][/map/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/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Verifying your cluster's health (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Verifying your cluster's health (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use the bdd-admin script to verify the overall health of your cluster. (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 "}) 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 "}) Your BDD installation consists of two main directories: $BDD_HOME and $DOMAIN_HOME. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling Kerberos for the Transform Service (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling Kerberos for the Transform Service (linktext][/map/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/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Studio and the Transform Service require load balancing when installed on multiple nodes. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing for Studio (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing for Studio (linktext][/map/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/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring load balancing for the Transform Service (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring load balancing for the Transform Service (linktext][/map/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/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Updating the DP CLI whitelist and blacklist (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating the DP 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 DP 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 your cluster (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Backing up your cluster (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Oracle recommends that you back up your BDD cluster immediately after deployment. (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][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring Studio database caching (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring Studio database caching (linktext][/map/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/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Customizing Studio database caching (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Customizing Studio database caching (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can customize Studio's database cache configuration, if needed. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Disabling Studio database caching (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Disabling Studio database caching (linktext][/map/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/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Clearing the Studio database cache (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Clearing the Studio database cache (linktext][/map/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/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 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/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Types of reverse proxies (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Types of reverse proxies (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Reverse proxies may be either devices/appliances or specially configured web servers. (shortdesc] (topicmeta] (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]