5 Enterprise Back Office on One Server

This section provides instructions for installing and configuring Oracle MICROS Reporting and Analytics on one server.

Important:

Review all the information in this section before starting the software installation.
If you are installing Simphony on the same server, install these components in one operation with the installer:

  • Portal WebLogic AdminServer and Reporting and Analytics

  • Admin Server (optional if needed)

  • Aggregation and Adjustment Service

  • InfoDelivery Service

  • Alert Engine Service

  • Simphony Mobile Aggregation

Single-Server Prerequisites

Before installing Portal WebLogic AdminServer and Reporting and Analytics 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. Review Enterprise Back Office 9.1 Release Variations to determine which one is right for your environment and requirements. Then download the appropriate general release installation media.
  3. Review the System Requirements, Supported Systems, and Compatibility section of the Oracle MICROS Enterprise Back Office Release Notes for the latest operating system, database server, and software requirements.
  4. Review the Oracle MICROS Enterprise Back Office Security Guide and, if you are installing Inventory Management, review the Oracle MICROS Inventory Management Security Guide for detailed explanations regarding securing your system during and after installation.
  5. Make sure the operating system accepts file names and file paths longer than 260 characters.
  6. Verify that ports 7001 and 9556 are not being used.
  7. Obtain separate Secure Socket Layer (SSL) certificates for the Reporting and Analytics hostname and create a Java keystore. See Appendix D of the Oracle MICROS Enterprise Back Office Security Guide for instructions. Confirm that the SSL certificate password as well as the keystore password only contain alphanumeric characters. Special characters, symbols, or spaces are not allowed for the password.
  8. Make sure that at least 65 GB of storage is free in addition to the server hardware requirements for the installation files and for temporary files created by the installation wizard.
  9. If you are performing an upgrade instead of a brand-new installation, How Do I Upgrade? contains a summary of upgrade information and instructions.

Parent topic: Enterprise Back Office on One Server

Enterprise Back Office Database Configurations

Oracle MICROS recommends setting the following Oracle Database configurations when creating the database instance and before running an Enterprise Back Office product installer. While some configurations can be changed after the installation, preparing the database instance prior to schema installation can prevent unexpected errors and problems.

Oracle Database Configuration for Enterprise Back Office Database

Use the following table for a set of guidelines for setting up the Oracle Database instance for Enterprise Back Office:
Parameter Recommended Value

db_block_size

16384

open_cursors

20000

db_recovery_file_dest_size

Set as the amount of storage allocated to FRA and DATA.

job_queue_processes

64

aq_tm_processes

1

session_cached_cursors

100

optimizer_mode

first_rows_10

optimizer_index_caching

20

optimizer_index_cost_adj

20

cusrsor_sharing

exact

processes

1024

sga_max_size

Set as 50% of database RAM, to be tuned by the DBA during the life of the environment.

sga_target

Set as the same value as sga_max_size.

pga_target

Set as 25% of sga_target.

Oracle Database Tablespaces for Enterprise Back Office Database

Make sure to create the following tablespaces in the Enterprise Back Office database. Each tablespace requires Transparent Data Encryption (TDE) encryption.

  • COREDB

  • PORTALDB

  • LOCDB

  • LOC_INDX

  • RTA

  • PENTAHO or SMALLFILE

    • Not applicable for 9.1 New Tech Stack

  • CEDB

  • TEMP

Parent topic: Enterprise Back Office on One Server

Starting the Installation

  1. Extract the following from the installation file archive. 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 to use more than one IP or database service name 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. If your environment uses Labor Management, select Yes for Will myLabor be used with this installation?
  6. To install Simphony on the same server, select Yes for Will Simphony be used with this installation?
  7. Select the features to install.
    If you are installing Simphony on the same server, make sure to select these services.

    • Portal WebLogic AdminServer

    • Portal Managed Server

    • Alert Engine

    • Aggregation and Adjustment Service

    • infoDelivery

    • Admin Server (optional)

    • Simphony Mobile Aggregation

Parent topic: Enterprise Back Office on One Server

Installing Portal WebLogic AdminServer and Reporting and Analytics

  1. On the WebLogic Info - Single Box page, configure the application server settings:

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

    WebLogic Admin Server Host Name and WebLogic Admin Server Port

    Enter the hostname of the server that hosts Portal WebLogic AdminServer.

    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.
  2. If you are completing a 9.1 release installation, on the SSL page select Yes to enable SSL/Transport Layer Security.
  3. If you are completing a 9.1 New Tech Stack installation or completed Step 2, on the Certificate Configuration - Portal page fill out the form to install the signed certificate:
    1. 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.

      Note:

      Both passwords can only contain alphanumeric characters. Special characters, symbols, or spaces are not allowed.
    2. Click Choose, select the keystore file, and then click Next. See the Oracle MICROS Enterprise Back Office Security Guide for instructions on how to select the keystore file.

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

    3. Verify the certificate information, and then click Next.
  4. 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 Service Name.

    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.
  5. If you are completing a 9.1, 9.1 with OBIEE, or 9.1 New Tech Stack with Pentaho installation, 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 Service Name.

    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 customer-facing, Internet 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 customer-facing, Internet URL for Reporting and Analytics.
  6. If you are completing a 9.1, 9.1 with OBIEE, or 9.1 New Tech Stack with Pentaho installation, on the Is this an OLAP Portal Instance page, select DUAL.
  7. If you are completing a 9.1, 9.1 with OBIEE, or 9.1 New Tech Stack with Pentaho installation, on the OLAP Database Type Database Information page, configure the OLAP database connection as described in the following table:

    Table 5-2 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/database service name for the OLAP database.
  8. 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.
  9. 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.
  10. Configure Reporting and Analytics:
    1. On the Portal Specific Settings page, configure Reporting and Analytics as described in the following table:

      Table 5-3 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. This must be enabled if you are completing 9.1 New Tech Stack release installations.

      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.
  11. 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 5-4 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.
  12. On the Confirm Datasource Name page, enter the OLAP database name in the OLAPDS database name field. By default, this field uses AGGREGATE_DB.
  13. On the InfoDelivery Configuration page, enter the Info Delivery email username for sending and receiving emails, and the Info Delivery administrator email account.

Parent topic: Enterprise Back Office on One Server

Installing Admin Server

  1. On the Posting/Admin Database Information page, enter the address of the aggregation database server.
  2. On the Posting/Admin Mail Server page, enter the mail server information to be used by the Admin Server, and then set the port to 25.
  3. On the Admin Server Configuration page, enter the credentials for the database user and the CEDB user.
  4. On the Admin Server Configuration page, configure the Admin Server as described in the following table:

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

Parent topic: Enterprise Back Office on One Server

Connecting Reporting and Analytics to the Admin Server

  1. Follow the instructions for the installation wizard. You do not need to change values from the Reporting and Analytics installation.
  2. On the Posting/Admin Database Information page, enter the hostname of the Admin Server.
  3. On the Posting/Admin Mail Server page, enter the hostname, SMTP port, and POP3 port of the mail server to be used by the Admin Server.

Parent topic: Installing Admin Server

Installing Aggregation and Adjustment

  1. On the Aggregation Database connection Information page, configure the connection to the Enterprise Back Office, Gift and Loyalty, and Aggregate_DB databases:
    1. Select Enable Monitor.
    2. Select Oracle or Sql Server depending on the Enterprise Back Office database type.
    3. Enter the database SID and server port for the Core database and the Aggregate_DB database.
    4. Enter the hostname for the Core database and the Aggregate_DB database.
    5. Enter the hostname, additional connection properties, and the server port for the Gift and Loyalty database.
    6. Enter login credentials to the Core and Aggregate_DB databases, typically the AGG user created during database install.
    7. Enter login credentials to the Gift and Loyalty database, typically the MMSQL user created during database install.
  2. On the Aggregation and Adjustment Configuration page, configure the database connection to the Aggregation and Adjustment service as described in the following table:

    Table 5-6 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.

Parent topic: Enterprise Back Office on One Server

Connecting Reporting and Analytics to the Aggregation and Adjustment Service

  1. Follow the instructions for the installation wizard. You do not need to change values from the Reporting and Analytics installation.
  2. On the Portal Specific Settings - Aggregation and Adjustment Service page, enter the hostname and port of the server with the Aggregation and Analysis service installation.
  3. Review the log files for errors. The installation wizard writes logs to the C:\temp\ folder during installation, and to the installation path after completing installation.
  4. Set the Aggregation Service memory configurations for your environment.

Parent topic: Installing Aggregation and Adjustment

Installing the InfoDelivery Service

  1. On the InfoDelivery Configuration page, enter the credentials to the CE database.
  2. On the InfoDelivery Mail Server page, enter the address of the mail server, and then set the port to 25.
  3. On the Portal/InfoDelivery Settings - Font page, configure the Report Mail font settings as described in the following table:

    Table 5-7 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.
  4. On the InfoDelivery Configuration page, enter the infoDelivery email login credentials for sending and receiving emails.
  5. If you are completing a 9.1, 9.1 with OBIEE, or 9.1 New Tech Stack with Pentaho installation, on the InfoDelivery page, leave the Pentaho Solutions Directory blank.

Parent topic: Enterprise Back Office on One Server

Installing the Alert Engine Service

  1. On the Alert Engine Configuration page, configure the Alert Engine as described in the following table:

    Table 5-8 Alert Engine Configurations

    Field Description

    Push alert service username and Push alert service password

    Enter the login credentials for the push alert service.

    Number of alert threads

    Enter the number of alert threads.

    Portal DB User and Portal DB Password

    Enter the Enterprise Back Office database login credentials.

    Core DB User and Core DB Password

    Enter the core database login credentials.

    Location Activity DB User and Location Activity DB Password

    Enter the location activity database login credentials.

    RTA DB User and RTA DB Password

    Enter the RTA database login credentials.

    CE DB User and CE DB Password

    Enter the CE database login credentials.

Parent topic: Enterprise Back Office on One Server

Installing the Simphony Mobile Aggregation

  1. On the Simphony Mobile Aggregation page, 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.

Parent topic: Enterprise Back Office on One Server

Completing the Installation

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

  2. Review the Pre-Installation Summary, and then click Install.
  3. Verify the installation as described in Verifying the Installation.
  4. Apply Patch 9.1.35 or higher.
  5. For 9.1, 9.1 with OBIEE, and 9.1 New Tech Stack with Pentaho release installations and if Pentaho Interactive Reports are in use, install Pentaho Patch Package.
  6. For 9.1 New Tech Stack and 9.1 New Tech Stack with Pentaho release installation details, see WebLogic Configuration for Enterprise Back Office.

Parent topic: Enterprise Back Office on One Server

Verifying the 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, go to PortalWebLogicAdminServerHOSTNAME:7001/console and log in using the WebLogic administrator account credentials created during the installation.
      Port 7001 is the default port. If your environment uses a different port, replace 7001 with that port value in the URL.
    2. Click Environment from the menu, and then click Servers. Verify that the AdminServer (admin) service is running.
    3. Start the HOSTNAME_appServ1 service, where:

      • HOSTNAME is the name of the host server.

      • appServ1 is the default name of the Reporting and Analytics application server instance. If you changed the default name when you installed Reporting and Analytics, that name appears instead of the default.

    4. 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.
  3. Verify the following Microsoft Windows services are running:
    For the 9.1 or 9.1 with OBIEE release:

    • beasvc bifoundation_domain_AdminServer

    • beasvc bifoundation_domain_<HOSTNAME>_appServ1

    • Oracle WebLogic NodeManager (<Path to Oracle Middleware wlserver installation>)

    For the 9.1 New Tech Stack or 9.1 New Tech Stack with Pentaho release:

    • wlsvc bifoundation_domain_AdminServer

    • wlsvc bifoundation_domain_<HOSTNAME>_appServ1

    • Oracle Weblogic bifoundation_domain NodeManager

Parent topic: Enterprise Back Office on One Server