Installing Reporting and Analytics and Components on Server 1

This chapter describes the instructions and verification steps for installing Reporting and Analytics on Server 1:

Installing the Reporting and Analytics Components for Oracle MICROS Simphony

  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.

    /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.
    3. For Will iCare be used with this installation?, select No.
    4. For Will Simphony be used with this installation?, select Yes.
    5. For Will myInventory be used with this installation?, select No.
    6. For Will myLabor be used with this installation?, select Yes.
    7. For Will the weather service be used with this installation?, select No.
  5. On the Use existing Portal configuration page, make your selection based on your installation:
    1. If you are performing a new installation or 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, Aggregation and Adjustment Service, infoDelivery, Admin Server, , and Simphony Mobile Aggregation.
  7. On the Check if Cluster Environment page, select No.
  8. On the WebLogic Info page, configure the application server settings:

    Table 4-9 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 be eight to 20 characters, must not contain special characters, and must include at least one number.

    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.

    Node Manager port

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

  9. On the Published URL page, enter the published site URL. What are Published Site URLs? contains more information..
  10. On the Map Drive page:
    1. Create a mapped network drive to the drive containing the myMicros folder on the OBI server. For example, if you installed OBI on the E: drive, you can create the mapped drive Z:\ and enter the path as shown in the following image:

      Figure 4-3 Mapped Network Drive to OBI Server

      This image is a screenshot from the Map Network Drive dialog box mapping the E: drive on the OBI server to the Z: drive on the Reporting and Analytics server.
    2. Enter the mapped drive root and the path to the myMicros installation folder. For example, Z:\myMicros\
  11. On the SSL page, select Yes to enable SSL/Transport Layer Security, and then click Next
    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.
    2. Click Choose and select the certificate file, and then click Next.

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

    3. Verify the certificate information, and then click Next.
  12. On the Database Information page, configure the connection to the Reporting and Analytics database:

    Table 4-10 Database Information

    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):

    Table 4-11 Repository Database Information

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

    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.

    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 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.

    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 InfoDelivery Configuration page, enter the CEDB user credentials.
  15. On the Posting/Admin Database Information page, enter the hostname of the Admin Server.
  16. On the InfoDelivery Mail Server page, enter the hostname of the IceWarp Mail Server or enter the hostname for the separate InfoDelivery server, and then enter the SMTP port.
  17. On the Simphony Configuration for Portal page:
    1. Select the type of database used by Simphony, and then enter the database SID and port.
    2. Enter the name or IP of the Simphony database server, and then enter any additional connection strings.
  18. On the Portal/InfoDelivery Settings - Font page, configure the Report Mail font settings as described in the following table:

    Table 4-12 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.

  19. On the Admin Server Configuration page:
    1. Enter the credentials for the Admin Server to access the database server.
    2. Enter the CEDB user credentials.
  20. On the InfoDelivery Configuration page, enter the infoDelivery email login credentials for sending and receiving emails.
  21. On the InfoDelivery page, leave the Pentaho Solutions Directory blank.
  22. On the Admin Server Configuration page, configure the Admin Server as described in the following table:

    Table 4-13 Admin Server Configurations

    Field Description

    Trailer to send in alerts from Admin Server

    Enter trailer text in the four fields provided.

    Email account to send alerts from

    Enter the email name, without the domain, that the Admin Server uses to send alerts.

    Number of hours before a location is considered out of contact

    Enter the maximum number of hours before the Admin Server flags an unresponsive location.

    Email addresses to send long alert messages to

    Enter the email name, without the domain, to which the Admin Server sends long alert messages. You can separate multiple addresses with a comma.

    Email addresses to send short alert messages to

    Enter the email name, without the domain, to which the Admin Server sends short alert messages. You can separate multiple addresses with a comma.

    Email addresses to send copies of org alerts to

    Enter the email name, without the domain, to which the Admin Server sends a copy of all alerts.

    Folder containing custom packages for Admin Server

    Enter a folder path containing custom packages.

  23. On the Simphony Mobile Aggregation page:
    1. Enter the number of Aggregation Threads.
    2. Enter the credentials for the Portal DB user, the Core DB user, the Location Activity DB user, and the RTA DB user.
  24. On the Aggregation and Adjustment Configuration page, configure the database connection to the Aggregation and Adjustment service as described in the following table:

    Table 4-14 Aggregation and Adjustment Service Login

    Field Description

    Core database login and Core database password

    Enter the core database login credentials.

    RTA database login and RTA database password

    Enter the RTA database login credentials.

    Portal database login and Portal database password

    Enter the Enterprise Back Office database login credentials.

    Location Activity database login and Location Activity database password

    Enter the location activity database login credentials.

    Name for Analysis/Aggregation Instance

    Enter a unique name for this instance of the analysis/aggregation service. The service inserts the name into the database to denote which service processed a job.

    Connection Cache Type

    Select a connection cache type from the drop-down list.

  25. 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.

  26. Review the Pre-Installation Summary, and then click Install.

Verifying the Reporting and Analytics Application 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. 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 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 the portal component is 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.
  3. Verify the following Microsoft Windows services are running:
    • beasvc bifoundation_domain_appServ1

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