Table 2-1 Enterprise Back Office Components
| Component | Description | ||
|---|---|---|---|
|
OBIEE (Oracle Business Intelligence) |
This component is required and installs Oracle WebLogic, Oracle WebLogic Administration Server, and Oracle Business Intelligence. |
||
|
Portal (Reporting and Analytics) |
This component is required and installs Oracle WebLogic and the Reporting and Analytics application. You can configure the component to install Labor Management. |
||
|
Analysis Aggregation |
This service is required and populates the Aggregation Database used for Oracle Business Intelligence and Gift and Loyalty segmentation. |
||
|
Aggregation and Adjustment Service |
This service performs data forecasting, generates trends and projections for InMotion Mobile, and suggests inventory cost adjustments. |
||
|
iCare |
This component installs Oracle WebLogic and the Gift and Loyalty application. |
||
|
Master |
This component is the Remote Transfer Agent posting server that receives incoming sales data from the Point-of-Sale applications and manages all Posting servers. Installation is not required if the Point-of-Sale application uses a different method for posting data to the Enterprise Back Office database. |
||
|
Posting |
Install this component on additional Remote Transfer Agent posting server nodes for load balancing. |
||
|
Admin Server |
This services provides export scheduling and product integration. |
||
|
infoDelivery |
This service interfaces with the mail server to process, schedule, and send reports by mail. |
||
|
Alert Engine |
This services provides push notifications and indicators for mobile applications. |
||
|
Weather |
This service interfaces with a third-party weather provider to retrieve up-to-date information, and stores daily weather condition and forecast information. |
||
|
EMS Batch Service |
This service interfaces with Point-of-Sale applications to process menu item, price, and tax rate updates. |
||
|
Simphony Mobile Aggregation |
This service interfaces with Oracle MICROS Simphony to aggregate and process sales data for InMotion Mobile. |
||
Parent topic: Enterprise Back Office Installation FAQ
Oracle MICROS Enterprise Back Office refers to the whole product suite that contains Reporting and Analytics, Forecasting and Budget, Labor Management, Inventory Management, Gift and Loyalty, and support for mobile applications such as InMotion Mobile. When documentation refers to an Enterprise Back Office entity, it typically refers to an entity that is shared across two or more of these products.
Oracle MICROS Reporting and Analytics refers to the core web application that provides reporting and data management. When documentation refers to Reporting and Analytics, it does not include components such as the Remote Transfer Agent, the Admin Server, and the Analysis Aggregation service.
Parent topic: Enterprise Back Office Installation FAQ
Table 2-2 Reporting and Analytics Deployment Scenarios
| Deployment Scenario | Description | |||
|---|---|---|---|---|
|
Two Servers |
Reporting and Analytics is typically installed in a two-server configuration consisting of:
|
|||
|
Server Cluster |
Reporting and Analytics can be installed in a server cluster for load-balancing and fail-over redundancy. This deployment is typically used by data centers and high-volume customers and consists of:
|
|||
|
Single Server |
Reporting and Analytics offers the option to install all required applications and components on a single server. Oracle MICROS does not recommend this deployment scenario. |
|||
Parent topic: Enterprise Back Office Installation FAQ
If you are upgrading Enterprise Back Office from version 9.0, run the installation wizard for the new version with OBIEE and follow the instructions.
If you are upgrading to Enterprise Back Office 9.0 or later and you want to generate metadata outputs of legacy reports, you must generate metadata for legacy reports before uninstalling Enterprise Back Office. You will not be able to recover the reports after you uninstall the earlier version of Enterprise Back Office.
Remove all components and services of the existing installation. Uninstalling Enterprise Back Office 8.5 or Earlier contains instructions for removing Enterprise Back Office.
Parent topic: Enterprise Back Office Installation FAQ
Oracle MICROS recommends installing the Gift and Loyalty web application on a separate application server for hardware requirement and load purposes.
If the Enterprise Back Office database is installed on Microsoft SQL Server, you can install the Gift and Loyalty database with the Enterprise Back Office database. Review the hardware guidelines in the Oracle MICROS Enterprise Back Office Server Sizing Guide to ensure the database server meets hardware and storage requirements.
Verify that the server specifications comply with compatibility information in the Oracle MICROS Enterprise Back Office Release Notes and hardware guidelines in the Oracle MICROS Enterprise Back Office Server Sizing Guide.
Change the Secure Socket Layer listening port and the listening ports for the network channel in Oracle WebLogic. Changing Gift and Loyalty Ports contains instructions for changing the ports after installation.
Parent topic: Enterprise Back Office Installation FAQ
Oracle MICROS recommends installing the Inventory Management web application and database on a separate server for hardware requirement and load purposes.
You can install the Inventory Management database on the Enterprise Back Office database server if the server specifications adhere to compatibility information in the Oracle MICROS Enterprise Back Office Release Notes and hardware guidelines in the Oracle MICROS Enterprise Back Office Server Sizing Guide.
Install matching release versions of Enterprise Back Office components. For example, to use Inventory Management with Reporting and Analytics 9.1.0, make sure to install Inventory Management 9.1.0. This does not apply to patches because patch release versions may vary by component.
Parent topic: Enterprise Back Office Installation FAQ
Oracle MICROS recommends preparing and using security certificates for all applications that support traffic over public communications methods.
If you do not have a security certificate prepared for one or more servers and must proceed with the installation, you can install Enterprise Back Office without enabling Secure Socket Layer (SSL) security. You can then set up SSL using Oracle WebLogic after acquiring the required certificates.
When performing the installation without enabling SSL, use port 9704 for the Oracle Business Intelligence server published site URL. After enabling SSL in Oracle WebLogic, change the published site URL to use port 443.
Gift and Loyalty
Gift and Loyalty requires a security certificate. You cannot proceed with a Gift and Loyalty installation without acquiring a security certificate.
Parent topic: Enterprise Back Office Installation FAQ
Enterprise Back Office uses Oracle WebLogic Security Assertion Markup Language (SAML) to implement and secure single sign-on authentication across Enterprise Back Office web applications and services. The SAML implementation includes the use of published site URLs to specify the hostname and port at which the server is accessible externally. This hostname and port typically differs from the local address due to a domain name system (DNS) or load balancer.
The Enterprise Back Office installation wizard requests the published site URL information for the server hosting Oracle Business Intelligence Enterprise Edition and for the server hosting the Reporting and Analytics portal web application. To avoid the need to change the published site URLs after the installation, determine what your published site URL will be for both servers before running the installation wizard.
The following table provides a guideline for identifying what you should enter in the published site URL fields.
Table 2-3 Published Site URL Information
| Network Access | Oracle Business Intelligence Server Published Site URL | Reporting and Analytics Application Server Published Site URL | ||
|---|---|---|---|---|
|
Intranet (internal network) |
Use a Domain Name System (DNS) hostname, which must be different from the Reporting and Analytics hostname.
If you are installing Enterprise Back Office without secure socket layer, use port 9704. |
Use a Domain Name System (DNS) hostname, which must be different from the OBI hostname.
|
||
|
Internet (external) |
Set up a Domain Name System (DNS) hostname or a URL redirect for accessing the web application from outside the server network. The OBI URL must be different from the Reporting and Analytics URL. For example, If you use a port other than the default ports, make sure to enter the port. |
Set up a Domain Name System (DNS) hostname or a URL redirect for accessing the web application from outside the server network. The Reporting and Analytics URL must be different from the OBI URL. For example, If you use a port other than the default ports, make sure to enter the port. |
||
You can configure Enterprise Back Office to force users to use the HTTPS protocol. The Enterprise Back Office Security Guide contains more information.