6 Reporting and Analytics on One Server

This section provides instructions for installing and configuring the Oracle Business Intelligence Enterprise Edition and Oracle MICROS Reporting and Analytics on one server.
  1. Reporting and Analytics Single Server Prerequisites

  2. Installing Oracle Business Intelligence and Reporting and Analytics on One Server

  3. Verifying the Single Server Installation

Reporting and Analytics Single Server Prerequisites

Before installing the Oracle Business Intelligence Enterprise Edition and the Reporting and Analytics application on the same server:

  1. Verify that your server meets the system requirements. The Application Server Compatibility and Requirements section in the Oracle MICROS Enterprise Back Office Release Notes contains compatibility and requirement information.
  2. Install the required Java Development Kit version in a folder path that does not contain spaces. For example, do not install Java in the default Program Files path.
  3. Set up a static IP address for the Oracle Business Intelligence server.
  4. Verify that the 7001, 9704, and 9556 ports are not being used.
  5. Obtain separate Secure Socket Layer (SSL) certificates for the OBI hostname and the Reporting and Analytics hostname.
  6. Install Oracle Business Intelligence and Reporting and Analytics.

Installing Oracle Business Intelligence and Reporting and Analytics on One Server

  1. Extract the following from the installation file archive in the same file structure to the Reporting and Analytics application server. Do not extract the files to a folder structure that contains spaces.

    /OBIEE/

    /OBIEEPatch/

    /Weblogic/

    Install_version.exe

  2. Double-click Install_version.exe to launch the installation wizard.
  3. On the Choose Install Folder page, enter the installation path or click Choose to select the installation path.
  4. On the Before We Begin page, select Yes or No for the questions shown to help the installation wizard understand your installation environment. The selections do not affect whether or not the wizard installs the selected modules, but the selections allow you to enter database connection information for the selected modules.
    1. For Would you like to install or upgrade a database with this installation for either myMicros or iCare?, select No.
    2. For Will different features connect to the myMicros Database using different database IP Addresses, select Yes if you expect to use more than one IP/SID to connect to the Enterprise Back Office database. For example, select Yes in an Oracle Real Application Cluster (RAC) environment that does not use a virtual IP and when features such as Remote Transfer Agent connect to a different node. If you select No, you can still modify the connection strings, but you cannot view individual database information screens by feature.
  5. On the Use existing Portal configuration page, make your selection based on your installation:
    1. If you want to install with a clean set of configurations, select No to install and configure a new installation set.
    2. If you are performing an upgrade and want to keep old settings, select Yes to use existing configurations. You can then select whether to configure the feature set on the Additional Features page.
  6. On the Choose Install Set page, select Portal and OBIEE.
  7. On the WebLogic Info - Single Box page, configure the application server settings:

    Table 6-1 Oracle WebLogic Application Server Information

    Field Description

    WebLogic User Name and WebLogic Password

    Create the login credentials for an administrator account on the WebLogic application server. The password must contain a number, no special characters, and consist of eight to 20 characters.

    Local JVM Path

    Verify the folder path to the local Java Development Kit installation. This install path must not contain spaces.

    WebLogic Admin Server Host Name and WebLogic Admin Server Port

    Enter the hostname and port of the Oracle Business Intelligence server, typically 7001.

    App Server Host Name

    Enter the hostname of the Reporting and Analytics WebLogic application server.

    BI Server Port

    Enter the port used by Oracle Business Intelligence, typically 9704.

    Node Manager port

    Enter the port used by the Node Manager, typically 9556.

  8. On the OBIEE Installation page, configure the connection to the OBIEE database and Repository Creation Utility (RCU) schemas:

    Table 6-2 Oracle Business Intelligence Enterprise Edition Database Information

    Field Description

    RCU Database Location

    Enter the hostname of the Enterprise Back Office database containing the RCU schema installation.

    SQL Server or Oracle

    Select the database type.

    Port and Database Service Name

    Enter the port used by the database, and any additional connection parameters as necessary.

    BIPLATFORM Schema Password

    Enter the schema password you created for the Repository Creation Utility (RCU) during database installation.

    MDS Schema Password

    Enter the schema password you created for the Repository Creation Utility (RCU) during database installation.

  9. On the Published URLs page, enter the published site URLs. Use port 9443 instead of port 443 for the OBI server. What are Published Site URLs? contains more information.
  10. On the OBIEE Repository page, create the password for the Oracle Business Intelligence Enterprise Edition (OBIEE) repository. The password must contain a number, no special characters, and consist of eight to 20 characters.
  11. On the SSL page, select Yes to enable SSL/Transport Layer Security.
    1. On the Certificate Configuration - Portal page, enter the Keystore Password, the Private Key Password, and the Alias that was used when generating the Certificate Signing Request for the Reporting and Analytics application.
    2. Click Choose, selected the signed certificate file, click Next, verify the certificate information, and then click Next.

      Make sure the filepath includes the following components: folder_path/file_name.extension

    3. On the Certificate Configuration - Obiee page, enter the Keystore Password, the Private Key Password, and the Alias that was used when generating the Certificate Signing Request for the Oracle Business Intelligence Enterprise Edition server.
    4. Click Choose, selected the signed certificate file, click Next, verify the certificate information, and then click Next.

      Make sure the filepath includes the following components: folder_path/file_name.extension

  12. On the Database Information page, configure the connection to the Reporting and Analytics database:
    Oracle Database Microsoft SQL Server
    1. In the Database Type section, select Oracle, and then enter the database network port and SID.

    2. Enter the database login credentials.

    3. Enter the hostname of the database server.

    4. In the Preferred Cache Type drop-down list, select Oracle.

    1. In the Database Type section, select SQL Server, and then enter the database network port.

    2. In the Additional Connection Parameters field, enter any required connection strings.

    3. Enter the database login credentials.

    4. Enter the hostname of the database server.

    5. In the Preferred Cache Type drop-down list, select Generic.

  13. On the Repository Database Information page, configure the connection to the Business Intelligence Repository database (BiRepos):
    Oracle Database Microsoft SQL Server
    1. In the Database Type section, select Oracle, and then enter the database network port and SID.

    2. Enter the login credentials to the Business Intelligence Repository database.

    3. Enter the login credentials to the Quartz Job Scheduler database.

    4. Enter the hostname of the Business Intelligence Repository database server. The information is typically filled by the installation wizard.

    5. Enter the externally-facing address for access to Enterprise Back Office. This is typically the published URL for Reporting and Analytics.

    1. In the Database Type section, select SQL Server, and then enter the database network port.

    2. Enter the login credentials to the Business Intelligence Repository database.

    3. Enter the login credentials to the Quartz Job Scheduler database.

    4. Enter the hostname of the Business Intelligence Repository database server. The information is typically filled by the installation wizard.

    5. Enter the externally-facing address for access to Enterprise Back Office. This is typically the published URL for Reporting and Analytics.

  14. On the OBI Database Information page, enter the password to the Oracle Business Intelligence (OBI) database.
  15. On the Aggregation DB information for Obiee Repository page, configure the aggregation server to use with the Oracle Business Intelligence Enterprise Edition (OBIEE) repository:
    Oracle Database Microsoft SQL Server
    1. Enter the hostname and port for the database server hosting the OBIEE aggregate database.

    2. Enter the database service name in Aggregate_DB Service name.

    The installation wizard does not show this configuration screen when upgrading from 9.0 using a Microsoft SQL Server database.
    1. Enter the hostname for the database server hosting the OBIEE aggregate database.

    2. Enter additional connection parameters.

  16. On the Is this an OLAP Portal Instance page, select DUAL.
  17. On the OLAP Database Type Database Information page, configure the OLAP database connection as described in the following table:

    Table 6-3 Online Analytical Processing Database Connection

    Field Description

    OLAP Login and OLAP Password

    Enter the login credentials for the OLAP database.

    OLAP Server name or IP

    Enter the hostname of the OLAP database.

    OLAP DatabasePort

    Enter the OLAP database server port.

    OLAP DB SID

    Enter the SID for the OLAP database.

  18. Set up the following connections:
    Connection Page Information

    IceWarp Mail Server

    Portal Mail Server

    Enter the Simple Mail Transfer Protocol (SMTP) hostname and port of the server that will host the IceWarp Mail Server, and then enter the mail domain, such as example.com.

    InfoDelivery Service

    InfoDelivery Mail Server

    Enter the hostname of the IceWarp Mail Server, or enter the hostname for the separate InfoDelivery server. Enter the SMTP port.

    RTA Master Server

    Location of Master Server

    Enter the hostname of the RTA Master Server.

  19. On the Mail Users page, configure the accounts used by Enterprise Back Office:
    1. In the Mail account jobs will be sent to by the client stores field, enter the email account that the Master Server uses to receive resultSets data and deploy jobs.
    2. In the Email account that will receive errors field, enter the email account to which the Point-of-Sales stores forward error messages.
  20. Configure Reporting and Analytics:
    1. On the Portal Specific Settings page, configure Reporting and Analytics as described in the following table:

      Table 6-4 Reporting and Analytics Configurations

      Field Description

      Names of all Portal Application Servers

      Enter the hostnames of all Reporting and Analytics web application servers in a comma-separated list.

      Administrator e-mail address

      Enter the email address, without the domain, of the administrator account.

      What email user will the Portal use to send mail?

      Enter the email address, without the domain, that the Portal uses to send mail.

      What is the password for the email user?

      Enter the password for the portal email user.

      Use HTTPS protocol for portal?

      Select whether the web application uses the HTTPS protocol. This option requires a Secure Socket Layer (SSL) connection and should typically only be selected when the installation environment has an SSL accelerator.

      Password for Messaging Queue

      Enter the login credentials for the messaging queue. This field does not show when performing an upgrade.

      Username and Password for utility user

      Enter the login credentials for the UTIL account created during database installation.

      Username and Password for CE user

      Create login credentials for accessing the Microsoft Windows Compact Edition database (CEDB).

      New Line Style for Portal CSV display

      Select whether to use Windows, Unicode, or HTML line styling when using the CSV export while viewing a report.

    2. On the Portal Specific Settings - Purge page, select whether Reporting and Analytics uses thread pooling to purge threads, and then configure the purge parameters.
    3. On the Portal Specific Settings - Aggregation and Adjustment Service page, enter the hostname of the server that will host the Adjustment and Aggregation Service in the Adjustment Server Name field.
  21. Configure Info Delivery:
    1. On the InfoDelivery Configuration page, enter the infoDelivery email login credentials for sending and receiving emails.
    2. On the Portal/InfoDelivery Settings - Font page, configure the Report Mail font settings as described in the following table:

      Table 6-5 Report Mail Font Configurations

      Field Description

      Enable User Font

      Select whether to allow using custom fonts when rendering PDFs.

      Path to user font

      Enter the path to a font, or click Choose and navigate to a font, to set the font used when rendering PDFs.

      Limit detail query days

      Enter a date limit for executing audit/analysis detail queries. The Organization configuration can override this setting.

      Limit summary query days

      Enter a date limit for executing audit/analysis summary queries. The Organization configuration can override this setting.

      New Line Style for InfoDelivery CSV format

      Select whether to use Windows, Unicode, or HTML line styling when formatting Report Mail items in CSV.

      Load reports by market segment

      Select whether to load reports dynamically by appending the organization or role market segment to the template name.

  22. On the Confirm Datasource Name page, enter the OLAP database name in the OLAPDS database name field. By default, this field uses AGGREGATE_DB.
  23. On the InfoDelivery Configuration page, enter the Info Delivery email username for sending and receiving emails, and the Info Delivery administrator email account.
  24. On the Review page, select your preferred review type:
    • Normal: Review the install folder, features, and disk space requirements.

    • Advanced: Review and edit individual variables in the installation files, then review the install folder, features, and disk space requirements.

  25. Review the Pre-Installation Summary, and then click Install.
  26. If you are performing a fresh installation on the 64-bit version of Microsoft Windows Server 2012, the installation wizard shows the Oracle Business Intelligence has stopped working error while the Oracle Universal Installer is copying files. This error is caused by a known issue with the Oracle Business Intelligence installation. Click Close the program to ignore the message and continue installation.
  27. To set up Report Mail for OBIEE:
    1. Log in to Enterprise Manager and expand the WebLogic Domain folder.
    2. Right-click bifoundation_domain, select Security, and then select Credentials.

      This image is a screenshot of the steps listed in step 52b with the bifoundation_domain folder circled, security circled, and credentials circled.
    3. Expand the oracle.bi.enterprise folder, select mail.server, and then click Delete.

      This image is a screenshot of step 52c with the mail.server option circled and the delete button circled.
    4. Click Deployment and then click Mail. Confirm that the Username and Password fields are blank.
    5. Restart the services.

Verifying the Single Server Installation

  1. Check the installation wizard logs for error, exception, and fail:
    • root\temp\MM_Log.log

    • root\temp\MMInstaller.log

    • root\myMicros\Uninstall_myMicros\Logs\myMicros_Install_datetime.log

  2. Check the Oracle Business Intelligence log in root\Program Files\Oracle\Inventory\logs\ for error messages.
  3. Perform the following checks in the Oracle WebLogic console:
    1. In a web browser, navigate to OBI server hostname:7001/console and log in using the WebLogic administrator account credentials created during the installation.
    2. Click Environment from the menu, and then click Servers. Verify that you see AdminServer (admin), Bi_server1, and appServ1 as Running.

      The status may be set to Starting if you check the WebLogic console immediately after completing installation. Verify that the status changes to Running.

    3. Click Deployments from the menu, click Customize this table, and then select Exclude libraries when displaying deployments. Verify that all components are set to Active.
    4. In the Domain Structure, click bifoundation_domain, click Security Realms, and then in the menu, click myrealm, click Providers, click Credential Mapping, click saml2CMP, and then click Management. Verify that obiee is listed.
  4. Verify the following Microsoft Windows services are running:
    • beasvc bifoundation_domain_AdminServer

    • beasvc bifoundation_domain_bi_server1

    • beasvc bifoundation_domain_appServ1

    • Oracle Process Manager (ORCLRNA)

    • Oracle WebLogic NodeManager(path to Oracle Middleware wlserver installation)

  5. Use opmnctl to verify that all components are set as Alive:
    1. In a command prompt, navigate to root\myMicros\Oracle\Middleware\instances\hostname_ORCLRNA\bin\
    2. Enter opmnctl status
    3. Verify that the components are set as Alive.

      Figure 6-1 Single Server opmnctl Status

      This image is a screenshot of the output of opmnctl status after installing the Primary OBIEE server, with the five service components set to the Alive state.