2 Oracle Linux for MICROS Platform
Oracle Linux for MICROS was introduced in Simphony 19.1. Some features useful for Integrators were added in Simphony 19.2, notably the HTML5 Custom Dialogs.
Why Linux?
Several factors drove the move to Linux for Simphony:
- Simple platform in comparison to the multiple Microsoft Windows platforms currently supported.
- Lower hardware resource requirements enable Oracle Restaurants to support older, and/or more cost-effective hardware, such as the Workstation 5A.
- Lower licensing cost.
- Alignment with industry and company direction.
- Provides an upgrade path for RES 3700 and e7 customers using existing workstations.
- Enhanced security posture.
- A complete solution (including hardware, software, and operating system) designed, maintained, and supported by Oracle.
- Oracle manages and delivers platform updates through the Client Application Loader (CAL).
- Linux reduces computing resources, improving point-of-sale application performance.
- Appliance-like environment creates a more user-friendly, secure, and dedicated point-of-sale experience. This eliminates the potential for users to run other applications on the point-of-sale hardware.
- Reduced cost and time for implementation.
- Supports conversion path for the Workstation 5A, providing customers which use the most popular legacy MICROS workstations with a pathway to Simphony, without having to upgrade hardware.
The Oracle Linux for MICROS platform was designed with the goal of an operating platform that acts and performs as an appliance, with every device manufactured and provisioned identically, including the base OS image and installed Simphony software. Customization is allowed only in strict circumstances, with defined constraints for specific intended use cases.
Appliance Model vs Custom Model
The following paragraphs contain an overview of two different models for the Linux based workstation, explaining the constraints of the appliance model, and the flexibility offered by the custom model.
The appliance versus custom model distinction is an unenforced concept subject to change. Oracle suggests that Integrators and customers decide which model they wish to adhere to maintain compatibility moving forward.
In the appliance model, the device is an appliance, signifying no changes and no customization beyond the Oracle signed software. The simplicity is one of the motivations for the Linux platform. To be considered an appliance or to exhibit appliance-like behavior and benefits requires only core Simphony software on the device, and Oracle approved and certified components.
The appliance model will only run:
- Core Simphony software installed by the CAL software.
- Oracle signed extensibility software installed by the Oracle CAL software (for example, Fiscal extensibility apps).
The appliance model is a locked down security model.
The custom model includes the following capabilities and characteristics:
- Download and use custom CAL packages, all extensibility apps, and SIM scripts.
- EMC controls authorizing and signing extensibility apps and SIM scripts. In other words, responsibility and control for authorizing and signing custom software is expanded to include not only Oracle, but also a high privilege EMC user.
- Hashing verification of custom software package downloads.
- Ability to revert to appliance model with a re-image.
Genesis of Oracle Linux for MICROS
The OS image used for Simphony on the Linux workstations is a custom image of Oracle Enterprise Linux. Much of the customization involves hardening the security posture and slimming it down, which results in removing unnecessary components and allowing a more compact OS image to preserve RAM for the Simphony application, database, and associated components.
The outcome is a custom image known as Oracle Linux for MICROS. This section covers the principles, guidelines, and constraints imposed by the choices made for the custom image. The OS image is the same across all workstations.
Principles and Constraints
The following is a list of principles and constraints for Oracle Linux for MICROS in a production environment.
- No desktop installed. The Linux workstation does not use a desktop; the POS display runs in a single dedicated X session. Standard Microsoft Windows practices, such as minimizing the application to access the OS or run a file explorer, are unavailable. Linux integrators must use the Linux shell to troubleshoot issues. Furthermore, integrators cannot install their own GUI applications on the Linux appliance.
- No on-screen keyboard available.
- No interactive root login available.
- All software run under unprivileged “osuser” account with the following exception: COM port enabled (including USB virtualized COM port).
- No direct access to the database. Data access is protected by security policy. Data access for integrators is provided solely through published Simphony APIs.
- User interface is in HTML5. No XAML/WPF is available within Mono.
- Certificate handling on Linux with Mono is different. This is relevant for Integrators connecting to external TLS endpoints. See Certificate Handling for more information.
- Unmanaged Microsoft Windows code does not work under Mono or Linux.
- Microsoft Windows specific .NET assemblies do not load on Mono.
- Unmanaged code is possible outside of Mono (e.g. for extensibility). Micosoft Windows extensibility application can call into native MicrosoftWindows DLLs. Linux extensibility applications can call into native Linux DLLs. Documentation exists on the internet outlining how to use the Mono Interop facility (search term "linux mono call native dll").
- Simphony 19.2 HTML5 dialog enhancements. See Runtime Environment for more information.
- The Oracle Simphony CAL (Client Application Loader) must install everything.