4 Configuring Oracle Analytics Server

This topic walks you through a step-by-step process to configure Oracle Analytics Server standard topology using the Configuration Assistant.

• About the Configuration Assistant
  The Configuration Assistant is a multi-functional utility that helps you to create database schemas, specify a port range, create system components, and start the application servers in addition to configuring the standard topology. Oracle strongly recommends that you to use the Configuration Assistant to configure the Oracle Analytics Server domain.
• Configuration Assistant Prerequisites
  You must ensure that you meet the criteria listed in this topic for a smooth, error-free domain configuration by using the Configuration Assistant.
• Creating the Database Schemas
  Before you can configure an Oracle Analytics Server domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
• Configuring the Oracle Analytics Server Domain with the Configuration Assistant
  The Configuration Assistant is a .sh (Linux) or .cmd (WINDOWS) file. Start the Configuration Assistant by starting the config executable from the bi/bin directory inside the Oracle home. Follow the procedure in this topic to complete the configuration step-by-step.

About the Configuration Assistant

The Configuration Assistant is a multi-functional utility that helps you to create database schemas, specify a port range, create system components, and start the application servers in addition to configuring the standard topology. Oracle strongly recommends that you to use the Configuration Assistant to configure the Oracle Analytics Server domain.

Oracle recommends that you create the Domain home and Application home directories under /home/oracle/config. But if you use the Configuration Assistant to configure the domain, the Application home is created under /home/oracle/product directory. To achieve the recommended directory structure, configure the domain using the Configuration Wizard.

Use the procedure described in Configuring the Domain in Enterprise Deployment Guide for Oracle Analytics Server.

Configuration Assistant Prerequisites

You must ensure that you meet the criteria listed in this topic for a smooth, error-free domain configuration by using the Configuration Assistant.

To verify whether the required conditions are met, see that:

• You have correctly installed the Oracle Analytics Server binary files.
• You have the latest supported JDK installed on your system.
• You have access to any one of the certified databases. For more information, see Certification - Supported Data Sources in Administering Oracle Analytics Server.
• (Optional) You have connection details of existing RCU schema prefix (STB) and you have already created BIPLATFORM, IAU, OPSS, MDS, STB, and WLS schemas in a single session.

  Note:

  You can, alternatively, generate a schema prefix (STB) and create the BIPLATFORM, IAU, OPSS, MDS, STB, and WLS schemas while you run the Configuration Assistant, provided you have the DBA credentials.

  The database schemas are required to store internal housekeeping information. These schemas are different from any data sources which you plan to analyze by using Oracle Analytics Server .

Creating the Database Schemas

Before you can configure an Oracle Analytics Server domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.

• Installing and Configuring a Certified Database
  Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.
• Starting the Repository Creation Utility
  Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.
• Navigating the Repository Creation Utility Screens to Create Schemas
  Enter required information in the RCU screens to create the database schemas.

Installing and Configuring a Certified Database

Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

See About Database Requirements for an Oracle Fusion Middleware Installation and Certification - Supported Data Sources.

Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.

Note:

You can use this step to create the database schemas when you are configuring Oracle Analytics Server domain for an enterprise deployment.

To start the RCU:

1. Verify that a certified JDK already exists on your system by running java -version from the command line.

   See About JDK Requirements for an Oracle Fusion Middleware Installation.

2. Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK.
   For example:

   • (Linux) setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0

   • (Window) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0

3. Change to the following directory:

   • (Linux) ORACLE_HOME/oracle_common/bin

   • (Windows) ORACLE_HOME\oracle_common\bin

4. Enter the following command:

   • (Linux) ./rcu

   • (WINDOWS) rcu.bat

Navigating the Repository Creation Utility Screens to Create Schemas

Enter required information in the RCU screens to create the database schemas.

• Introducing the RCU
  The Welcome screen is the first screen that appears when you start the RCU.
• Selecting a Method of Schema Creation
  Use the Create Repository screen to select a method to create and load component schemas into the database.
• Providing Database Connection Details
  On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.
• Specifying Schema Passwords
  On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
• Completing Schema Creation
  Navigate through the remaining RCU screens to complete schema creation.
• Configuring the Microsoft SQL Server Database for Oracle Analytics Server
  If you have installed the Oracle Analytics Server schemas on a Microsoft SQL Server database, you must configure Autostart for the SQL Server Agent and ensure that the agent is functioning.

Introducing the RCU

The Welcome screen is the first screen that appears when you start the RCU.

Click Next.

Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

• If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.

• If you do not have the necessary permissions or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.

• If the DBA has already run the SQL script for System Load, select Perform Product Load.

Providing Database Connection Details

On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

For Oracle databases, if you are unsure of the service name for your database, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database.

For Oracle databases, if the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

To provide the database connection details:

1. On the Database Connection Details screen, for a selected database type, provide the database connection details.

   • For Oracle Database, use the following example:

     • Connect String: examplehost.exampledomain.com:1521:Orcl.exampledomain.com

       Note:

       To specify the connect string, you must select the Connection String option.

     • Host name: examplehost.exampledomain.com

     • Port: 1521

     • Service Name: Orcl.exampledomain.com

     • User Name: sys

     • Password: ******

     • Role: SYSDBA

   • For Microsoft SQL Server, use the following example:

     • Connect String: examplehost.exampledomain.com:1433:dbname

       Note:

       To specify the connect string, you must select the Connection String option.

     • Server name: examplehost.exampledomain.com

     • Port: 1433

     • Database Name: dbname

     • User Name: sa

     • Password: ******

     If the middle tier database is Microsoft SQL Server, you must enable the SQL Server Agent. For more information, see Configuring the Microsoft SQL Server Database for Oracle Analytics Server.

2. Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.

Specifying Schema Passwords

On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

Click Next.

Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the Oracle database when you start the RCU.

To complete schema creation:

1. On the Map Tablespaces screen, select Encrypt Tablespace if you want to encrypt all new tablespaces that the RCU creates.
2. In the Completion Summary screen, click Close to dismiss the RCU.

Configuring the Microsoft SQL Server Database for Oracle Analytics Server

If you have installed the Oracle Analytics Server schemas on a Microsoft SQL Server database, you must configure Autostart for the SQL Server Agent and ensure that the agent is functioning.

Perform the following steps to enable the SQL Server Agent on Windows operating systems:

1. On the Start menu, navigate to Programs, SQL Server 2019, Configuration Tools, and then click SQL Server Configuration Manager.

2. Click + to expand the SQL Server that you want to manage the services.

3. Right-click SQL Server Agent and then click Properties.

   For default instances, the SQL Server Agent service is displayed as SQL Server Agent and for named instances, the SQL Server Agent service is displayed as SQL Server Agent (Instance name).

4. In the SQL Server Agent dialog box, on the Service tab, select Automatic from the Start Mode list, and then click OK to close the window.

   This setting automatically starts the SQL Server Agent when the system restarts.

5. Right-click SQL Server Agent and click Start.

6. In the User Account Control dialog box, click Yes to confirm.

Run the following commands to enable the SQL Server Agent and restart the SQL Server service on Linux operating systems:

1. sudo /opt/mssql/bin/mssql-conf set sqlagent.enabled true

2. sudo systemctl restart mssql-server

   Alternatively, you can use the command restart mssql docker to restart the SQL Server service.

Configuring the Oracle Analytics Server Domain with the Configuration Assistant

The Configuration Assistant is a .sh (Linux) or .cmd (WINDOWS) file. Start the Configuration Assistant by starting the config executable from the bi/bin directory inside the Oracle home. Follow the procedure in this topic to complete the configuration step-by-step.

If you are extending the WebLogic domain with Oracle Analytics Server by using the Configuration Assistant, make sure that the Administration Server for the domain is named AdminServer. Other names for the Administration Server are not supported.

To configure the Oracle Analytics Server standard topology:

1. Change to the following directory:

   • (Linux)ORACLE_HOME/bi/bin

   • (WINDOWS)ORACLE_HOME\bi\bin

2. Start the Configuration Assistant by entering the following command:

   • (Linux) ./config.sh

   • (WINDOWS) config.cmd

3. Select the components to install and click Next.
   To ensure that a consistent set of suites are deployed, the Configuration Assistant automatically adjusts your selection.
   • Oracle Analytics Server: Includes components such as data visualization, analyses, dashboards and agents, and installs Oracle Analytics Server without Publisher.
   • Oracle Analytics Publisher: Includes Publisher for pixel-perfect reports.

     You can use this option to install standalone Publisher.

   Select the Oracle Analytics Server and Oracle Analytics Publisher components to install Oracle Analytics Server with Publisher.

4. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.
   If any of the prerequisite checks fail, then a short error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or warning messages and continue with the installation, click Skip, although this approach is not recommended.

   Note:

   The configuration might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.
5. On the Define New Domain screen, specify the following:
   1. Enter the location where you want to set up the domain directory.
      The new domain is stored in a sub-directory with the same name as the domain.
   2. Enter a name for the domain.
      You can use alphanumeric characters, underscores or hyphens.
   3. Enter a username for the default system administrator.
      The username must not be blank and not exceed 30 characters.

      Note:

      This user is created in the embedded LDAP and is granted WebLogic Administrator permissions.

   4. Enter a password for the system administrator.

      It must begin with a letter, include at least one number, and can contain alphanumeric, underscore, dollar sign, and pound sign characters.

   5. Reenter the password to confirm.

      Domain Home is a read-only field derived from 'Domains Directory' and 'Domain Name'.

6. Click Next to proceed to the Database Schema screen. On this screen, click the appropriate option either to create a new schema or use an existing schema.
   • If you select to create a new schema, specify the following:

     Note:

     In this case, the Configuration Assistant creates a schema for you.

     1. Enter a unique schema prefix.

     2. Enter a password for your schema.

     3. Reenter the password to confirm.

     4. Select the type of database to use from the list.

        For the list of databases supported by Oracle Analytics Server, see Certification - Supported Data Sources in Administering Oracle Analytics Server.

        For Oracle ATPs Database, use the following example:

        • Schema prefix: BI1722428737

        • Schema password: ******

        • Confirm schema password: ******

        • Database type: Oracle Database

        • Username: admin

        • Password: ******

        • Simple Connect String: jdbc:oracle:thin:@(description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1521)(host=examplehost.exampledomain.com))(connect_data=(service_name=Orcl.exampledomain.com))(security=(ssl_server_dn_match=yes)))

        • Role: NORMAL

     5. Enter the username of the account that has privileges to create new schemas.

     6. Enter the password for the username.

     7. Enter the connect string based on the type of database you are using.

        For the list of databases supported by Oracle Analytics Server, see Certification - Supported Data Sources in Administering Oracle Analytics Server.

     8. Select the type of role to use.

        You must select NORMAL for Oracle Autonomous Database and SYSDBA for Oracle Database.

   • If you select to use an existing schema, specify the following::

     Note:

     In this case, you must create STB, BIPLATFORM, IAU, MDS, OPSS, and WLS schemas using the RCU.

     1. Select the type of database to use from the list.

        For the list of databases supported by Oracle Analytics Server, see Certification - Supported Data Sources in Administering Oracle Analytics Server.

     2. Enter the connect string based on the type of database you are using.

        For the list of databases supported by Oracle Analytics Server, see Certification - Supported Data Sources in Administering Oracle Analytics Server.

     3. Enter a unique schema prefix.

     4. Enter a password for your schema.

7. On the Port Management screen, specify the port range and click Next.

   Note:

   The default, allocated port range is from 9500 to 9999, both inclusive. You can keep the default values or specify different values within this range.
8. On the Initial Content screen, select one of the following options, and click Next:
   • Existing export archive (.jar file) from a previous installation

     Note:

     This option is applicable if you are migrating from Oracle BI 11g to Oracle Analytics Server.

     See Upgrading Oracle Analytics Server from 12c (Out-of-Place Migration) in Migrating and Upgrading Oracle Analytics Server.

   • Clean Installation (default).
9. On the Summary screen, verify the values that you specified on each screen.
   1. Click Save to generate a response file used for silent installation (optional).
   2. Click Configure.
      The configuration process starts and the Configuration Progress screen is displayed.
10. After the configuration concludes without any errors, click Next to go to the Configuration Complete screen.
11. On the Configuration Complete screen, review the configuration summary.
    1. Click Save to save the information displayed on this screen in a file.
    2. Click Finish to close the Configuration Assistant.
       The Oracle Analytics Server Application opens in the browser. Use the login credentials that you specified while configuring to sign in to the Home page of Oracle Analytics Server.

You have configured the standard Oracle Analytics Server topology. The Configuration Assistant automatically starts the newly configured Oracle Analytics Server instance after successful completion. However, if you want to restart a domain that has been shut down manually, start servers and processes.