Scale Oracle Analytics Server on Oracle Cloud

If you want to scale Oracle Analytics Server by distributing the processing of requests across multiple virtual machine (VM) instances, add another Oracle Analytics Server instance to your environment on Oracle Cloud.

Pre-requisites for scaling Oracle Analytics Server:

  • Verify that your environment meets system and network requirements. See Networking Overview and Virtual Networking Quickstart.
  • Deploy additional Oracle Analytics Server instance on the same virtual cloud network (VCN) as the primary Oracle Analytics Server instance.
You can use the performance metrics that are provided in Oracle Fusion Middleware Control to monitor process state and to determine when you must increase capacity to improve performance of Oracle Analytics Server on Oracle Cloud.

If you want to use a private subnet, see Configure Public and Private Subnets with a VPN.

  1. Use Oracle Cloud Marketplace to deploy Oracle Analytics Server on Oracle Cloud Infrastructure (node 1).

    For node 1, you must select Create Oracle Analytics Server Domain, and provide the required domain configuration details. See Deploy Oracle Analytics Server Using Oracle Cloud Marketplace.

    Description of oas_create_domain.jpg follows
    Description of the illustration oas_create_domain.jpg
  2. Use Oracle Cloud Marketplace to deploy a secondary Oracle Analytics Server on Oracle Cloud Infrastructure without a domain (node 2).

    For node 2, don't select Create Oracle Analytics Server Domain.

    Description of oas_no_domain.jpg follows
    Description of the illustration oas_no_domain.jpg
  3. Set up shared files and directories between the two nodes.

    The singleton data directory (SDD) stores the metadata. The default location is set to:

    DOMAIN_HOME/bidata

    The SDD path is defined in the file bi-environment.xml, located at

    DOMAIN_HOME/config/fmwconfig/bienv/core/bi-environment.xml.

    1. Use your favorite SSH client to connect to the compute instance for your primary Oracle Analytics Server (node 1). Log in as the opc user, and then switch to the oracle user. 
      ssh -i path_to_private_key opc@oas_public_ip
sudo su oracle
    2. Create a mount point for bidata. For example, run the following command:
      mount DOMAIN_HOME/bidata /sdd/bidata

      This makes /sdd/bidata the mount point for SDD.

    3. Open the bi-environment.xml file for editing, specify the singleton path, and save the file.

      For example:

      <bi:singleton-data-directory>Node1_IP_address:/sdd/bidata/</bi:singleton-data-directory>

      Where:

      • bi:singleton-data-directory is the SDD mount point.
      • Node1_IP_address is the private IP address of node 1.
    4. Log in to node 2 using the SSH utility and ping node 1 to check you can access node 1.
    5. Add the additional ports required for your scaled out environment to a customized firewall configuration file, and then run the script open_oas_firewall_ports.sh to open the ports. See About Managing Firewall Ports.
  4. Set up the global cache. See Set Up the Global Cache.
  5. Add (or remove) instances on Oracle Cloud Infrastructure.
  6. Validate that your system scales correctly. See Validate that Your System Has Been Scaled Correctly.