Windows Oracle

This document describes the minimum configuration requirements to install the application and/or data servers on a Microsoft Windows server with an Oracle 19c or 12c database.

Please note that any fresh installation should be performed with Oracle 19c as support for Oracle 12c could be removed in the future (from Oracle and Sage).

On installations where Oracle RDBMS and Sage X3 runtime components are in the same host, Oracle 19c is the only version where the connection from Sage X3 runtime and database can leverage the BEQ protocol.

If using Oracle RDBMS 12c, the connection must be done through embedded Oracle Instant Client 19 and listener even in a single-server configuration.

Category Configuration requirements
Operating system
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2019
    Warning:
    • On Windows 2019 and later, only Oracle 19c (19.3.0.0 or later) is certified.
    • Oracle Corporation does not certify Oracle 12c R1 or R2 with Windows 2019 or later.
  • Microsoft Windows Server 2016
    Warning:
    • On Windows 2016, Oracle 19c (19.3.0.0 or later) or 12cR2 (12.2.0.1) should be used.
    • Oracle Corporation does not certify Oracle 12cR1 12.1.0.2 with Windows 2016.

    • Note: Windows Server 2012 R2 should not be used for new installations, as:
    • Its End of Life is planned for October 10, 2023.
    • Sage stopped supporting Windows Server 2012 R2 in 2022.
    • If you are currently using Windows Server 2012 R2, you need to upgrade to Windows Server 2016, 2019, or 2022.
Server
  • Industry-standard server or virtual machine in a certified virtualization platform/operating system configuration.
  • Processors:
    • Intel® CPUs:
      • Minimal models: Intel® Xeon® E5 v4, E7 v4
      • Recommended: Latest (third generation) or previous generation (second and first) Intel® Xeon® Scalable Processors, Gold or Platinum variants
    • AMD™ CPUs:
      • Opteron™ family is very slow on integer computation and should not be used at all.
      • EPYC™ gen.1 (7001 series) are behind equivalent Intel® Xeon® CPUs of the same generation. Their use is discouraged.
      • EPYC™ gen.2 (7002 series) can be used. Its performance is similar to equivalent Intel® Xeon® Scalable processors.
    • Processor clock frequency:
      • Avoid low energy processors with low clock frequency. This will give poor results.
      • The base clock frequency should be ≥ 2.4 GHz.
      • For heavy single-threaded loads, consider using a processor with a 2.8 GHz or higher base clock speed.
  • Standard needs for the Sage X3 runtime (no database, and no Syracuse in the same VM), with 2.4 GHz Intel® Xeon®:
    • 2 logical cores for the first 40 Sage X3 sessions.
    • 1 additional logical core for each additional 40 Sage X3 sessions.
  • Add at least two logical cores for Oracle RDBMS if it is on the same host as Sage X3 application or runtime components.
RAM
  • 2 GB minimum for Windows operating system, 4 GB minimum (more is better) per Oracle database instance if hosted in the same server as Sage X3 application or runtime components.
  • Generally, the RAM usage per X3 session is under 100 MB, but it can be higher in the case of non-standard settings of maxmem.
Disk space
  • For Oracle 19c RDBMS software (binaries):
    • 8 GB for 19.3.0.0. SE2
    • Can be more for Enterprise Edition
    • Add free space for installing updates/patches
  • For Oracle 12c RDBMS software (binaries):
    • 5 GB for 12.1.0.2 SE2
    • Can be more for 12.2.0.1 and/or Enterprise Edition
    • Add free space for installing updates/patches
  • For Sage X3 (reference folder and software): 10 GB.
  • For the SEED demonstration folder (SEED): 10 GB.
  • For the production folder:
    • Depends on the amount of data in the folder. It will never be less than 10 or 20 GB.
    • A sizing tool is available in Sage X3 to estimate the size requirements.
Database software
  • Oracle 19c (19.3.0.0 or later):
    • Should be the version used for any new installation or in upgrade projects.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • Oracle 12cR2(12.2.0.1):
    • Is End of Life or near and should not be used for new installations.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • Oracle 12cR1(12.1.0.2):
    • Is End of Life and should absolutely not be used for new installations.
    • Editions: SE2 (Standard Edition 2) or EE (Enterprise Edition).
  • It is necessary to set up an Oracle TNS listener (for Print Server connectivity at least).
  • During X3 Solution initial configuration, you should ensure that in Oracle's sqlnet.ora file:
    • The SQLNET.AUTHENTICATION_SERVICES parameter value is set to NONE. The NTS value is not supported during the initial configuration, but it may be set back to NTS after this step.
  • Since recent Sage X3 Print Server versions embed Oracle 19c ODBC, there is no need to deprecate security in sqlnet.ora to allow legacy DataDirect ODBC drivers connection.
Software prerequisites for Sage X3 components
  • A Java Runtime Environment or JDK 8 (minimum 8u201) must be installed before any Sage X3 component installation.
  • The SAFE X3 Adxadmin administration engine component must be installed before installing Sage X3 application and runtime components.
  • The latest SAFE X3 management console should be used to configure the Sage X3 solution. Use at least the version provided in the ISO of the installed release.
  • For more details regarding Powershell, consult the pre-requisites documentation.

Note: From version 2022 R2 onwards, the use of Apache server is deprecated. It should only be installed in case your Sage X3 install requires one of the following applications:

  • JavaWeb (VT) Server

  • JavaBridge

  • SAP Business Objects

  • Sage X3 HR version 9 User Portal
Mail server
  • The workflow engine used in classic mode requires an SMTP server or gateway accessible from all Sage X3 runtime servers.
Windows user accounts
  • Oracle RDBMS installation and service accounts:
    • If you want to be able to create the Oracle database for the Sage X3 solution through the Sage X3 console in managed database mode, you must:
      • Install Oracle on Windows in a legacy mode where services run as a localsystem and not as a standard Windows user account.
      • If Oracle RDBMS is not on the same host as the Sage X3 application or runtime, you must install a SAFE X3 AdxAdmin administration engine on the Oracle RDBMS host.
      • You must install the Sage X3 Oracle component on the host where Oracle RDMBS is installed.
    • In other cases, you will have to use the manual configuration to configure a Sage X3 solution database from the Sage X3 console.
  • Sage X3 runtime service account:
    • Installing Oracle requires a user account with local administrator rights.
      If Oracle RDBMS is hosted on the same machine as the Sage X3 application or runtime. You can also use this account to run the Sage X3 runtime service if it is on the same virtual machine. Sage does not recommend doing this.
    • It is recommended to use an Active Directory account for running the Sage X3 runtime service when possible rather than a server’s local account.
      Permissions for this account:
      • It must have the Log on as a service privilege.
      • In case Oracle RDBMS is on the same host as the Sage X3 application or runtime, it must have read/write access to the solution’s Oracle database directories to use the Oracle tracing and debugging capability.
  • It is easier to set up Sage X3 if the account for running the runtime service belongs to the server's local administrators group. You can avoid this if the X3 folders directory tree is given full access to this account before performing the final configuration from the Sage X3 console.
  • For the actual software users, it is recommended to define a user group and assign access to the different software folders after installing the software components.