How to…

…know on Architecture and

System Requirements for
Sage X3
Product Update 9.0.0

Version 1a
Contents
Contents ......................................................................................................... 1

Introduction................................................................................................... 3

General overview .................................................................................................... 3

Folders ..................................................................................................................... 3

Components ................................................................................................. 5

Application servers ................................................................................................ 5

Database server ........................................................................................................ 5
Application and Main processing server ............................................................... 5
Additional processing servers ................................................................................. 5

Additional components ......................................................................................... 6

Print server ................................................................................................................. 6
Web server................................................................................................................. 6
Web services and Automated Data Collection (ADC) servers .......................... 7
Java Bridge server .................................................................................................... 7
Business Objects Server .......................................................................................... 7

Configuration console .............................................................................. 8

Mail server or SMTP Gateway .............................................................................. 8

Search Engine......................................................................................................... 8

Client workstations .................................................................................... 9

Desktop or laptop ................................................................................................... 9

Different web browsers are certified with Sage X3: ............................................. 9
Other web browsers or versions are compatible but not certified: ..................... 9

Smartphones and tablets ...................................................................................... 9

Development platform ......................................................................................... 10

Global schema of the technical architecture................................................... 11

Network and bandwidth ...................................................................................... 12

Network requirements ............................................................................................ 12
Network bandwidth between workstation and front- end servers .................... 13

Antivirus ................................................................................................................. 13

Copyright © 2015 Sage Software, Inc. All rights reserved. Page 1 of 10

Microsoft updates ................................................................................................ 13

Virtualization ......................................................................................................... 14

Architecture performance rankings .................................................................. 15

Resource configuration ......................................................................... 16

List of available operating systems .................................................................. 16

List of database versions .................................................................................... 17

Distribution of components in a 2-tier architecture ....................................... 17

Distribution of components in a 3-tier architecture ....................................... 18

Distribution of components up to a 3-tier architecture ................................. 18

Memory size occupied by Sage X3 processes................................................ 18

Other Sage X3 processes distribution.............................................................. 19

List of additional software to be installed ........................................................ 19

Remote connection.................................................................................. 21

Sizing requirements ................................................................................ 22

General prerequisites for databases and applications.................................. 22

Database and application server ....................................................................... 23

Deployment of a single-tier architecture (physical server) ......................... 23

Deployment of a multiple-tier architecture (mixed)........................................ 24

Front-end servers ................................................................................................. 25

Additional processing server ............................................................................. 26

Workstations ......................................................................................................... 26

Copyright © 2015 Sage Software, Inc. All rights reserved. Page 2 of 10

Sage X3

Introduction
This document provides information on system requirements and Definitions
setup for Sage Architecture for the Enterprise (SAFE X3). SAFE X3
is a common technological platform for developing application BATCH SERVER
software. The application software
offers a standard scheduling
function in a “postponed”
General overview mode (batch) to manage a
large number of parameters
The following application software is developed using the technological for the launch of these
platform SAFE X3: processes.

• Sage X3
BATCH TASK

• Sage HR management
Unlike an interactive session,
the batch task is a process
• Sage WMS Geode (pending) launched in batch mode by
the task scheduler (batch
The technical architecture is organized in layers and designed to: server).

• Separate the layers of data management, process execution, and

presentation in a 3-tier architecture,
• Spread the load across one or more servers when the application is
intended for a large number of users for improved scalability,
• Provide implementation options on different technical platforms and
databases,
• Provide access from various user devices including Windows and Mac
computers, tablets, smartphones, and industrial terminals (radio frequency).

Folders
A folder is a repository base that contains management rules, parameters, and
data for one or more companies. It contains a directory tree on the hard disk
and tables stored in the database.

Folders are installed under two resources of the architecture:

• The application server,
• The database server.

When installing Sage X3, four folders are typically created:

• X3 reference or Parent folder – A reference folder that contains the
software programs,
• X3_PUB – A pseudo-folder that contains the publication objects (like
screens, windows, menus, menus profiles) used by the web interface,
• SERVX3 – A pseudo-folder used for managing the batch server,
• SEED – A demonstration folder that may also serve as a model folder from
which new folders can be created by duplication.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 3

Sage X3

Administration tasks include:

• Creating new folders,

• Duplicating folders from a model,
• Removing any unnecessary folders,
• Creating backup folders.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 4

Sage X3

Components
All the resources described herein are logical components. They can all be
installed on the same computer or distributed across several machines
according to the number of users to be connected, the size of the database,
and the number of transactions to be processed. This model of distributed
architecture offers a high level of scalability.

Application servers
Database server Definition
The database server stores the application data, the description data for this APPLICATION DATA
application (dictionary), and the parameter data.
Tables and indexes that
SAFE X3 products are developed according to the database editor store information
recorded by application
recommendations, which guarantee the integrity and the coherence of the data users such as suppliers,
stored in the database. customers, products,
inventory, sales,
There is no limit to the size of the database and it can vary from 30 to 80 GB, production, accounting,
with some databases reaching hundreds of gigabytes. To reduce the size of etc.
the database, you can purge or archive large tables.

Application and Main processing server

This server provides access to all the elements that make up Sage X3
including processes, screens, reports, etc. These elements are organized in
directories by folder and are not repeated from parent folder to child folder
except when they truly belong to the child folder. Otherwise, it is the element
from the parent folder that is used. Only three folder levels are managed in this
way.

The Sage X3 Batch Service, which launches and executes batch processes,
runs on the Application and Main processing server.

The application is organized as a hierarchy of folders where the root folder is

the image of the standard delivery and the other folders are the customer
folders, generated from the root folder and each representing an application.

Additional processing servers

These servers manage processes exclusively for everything related to
presentation, which is directly supported by the front-end web server.

The differences between the main processing server and additional processing
servers are as follows:

• The main processing server is mandatory and is located on the same

machine as the application server. The Batch Tasks Supervisor and
programs launched in batch mode via the Supervisor also run on this
server.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 5

Sage X3

• Additional processing servers are optional and are used to balance the load
(CPU and memory). You can select additional servers when configuring the
entry point in the Syracuse Portal.

Additional components
Print server
Definition
This server is hosted on a machine running a Windows Server operating
system. There can be multiple print servers per solution depending on volume JSON
requirements for printing. JavaScript object
notation: a textual data
The print server supports all print requests from interactive sessions as well as format for structuring
batch submissions and sends the files to the appropriate print destination information with tags
(printer, file, PDF, FAX, etc.). MONGO DB
A document-oriented
A Windows service is started on the computer that hosts the Print server. This database classified as a
service is on port number 1890 by default, but it can be customized during NoSQL database
installation. The print service manages an output queue of the requests
submitted, and the execution of these reports can be dispatched on several SADFSQ
editing processes or threads. The number of editing processes can be An internal
customized in the Configuration Console and must be adapted to the size of the communication protocol
machine. executable

The Print server communicates with two other servers in your environment: the
Application server that hosts the printing model and the Database server that
hosts the tables via an ODBC connection.

The report files are transferred using the internal communication protocol
SADFSQ. The Print server has a client SADFSQ able to address and
communicate with a server SADFSQ running on the Application and Main
Processes server.

Reports are designed using Crystal Reports 2008, (version 12.x) or Crystal
Reports 2013 (version 14.1).

Web server
The Web (Syracuse) Server is a front-end server that end users access to
open a Sage X3 session through their internet browsers.

During installation, especially in documents and screens, the Web

server can also be referred to as Syracuse.
It works in asynchronous mode based on the Node.js software platform, which
contains a built-in HTTP server library, making it possible to run a web server
publisher.

Each page has its own URL and sends Java Script feeds (JSON format) that
are SData normalized back to the client.

Operating data, such as Windows customization, dashboard, endpoints,

management roles, user information, and electronic documents that users can

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 6

Sage X3

register via their storage area, are stored locally in a document-oriented

MongoDB database .

Syracuse Web Server also provides management of:

• Workflow links,
• Incoming and outgoing SOAP and REST WebServices (since PU9).

Web services and Automated Data Collection (ADC) servers

A technical server manages communication with:

• The Automated Data Collection devices,

• Incoming SOAP Web services in “legacy mode”.
This component encapsulates Apache HTTP and Apache Tomcat (web servlet
container).

Java Bridge server

The Java Bridge Server provides “legacy” outgoing Web Services (SOAP,
REST) and sends Rich Mail, including pictures, attached documents, etc., from
Sage X3.

Based on the OSGi Equinox framework, it can be used to extend the standard
available functions by developing new OSGi plug-ins.

Java Bridge server encapsulates Apache HTTP and Apache Tomcat (web
servlet container).

Business Objects Server

The Business Objects server hosts Business Objects Enterprise XI. The data
warehouse database can be hosted on this server and updated daily from the
production database.
The Business Object server can be deployed only on Windows 2012
R2.
The data warehouse database can be also stored on another server.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 7

Sage X3

Configuration console
The Configuration Console is a tool used to install and administer SAFE X3
components. The Console configures the components and links them to define
a solution or work environment.

The Console uses different XML configuration files that are generated on each
server when installing the various components.

It can be installed on a workstation, but we recommend that you install it on

one of the Windows servers that make up the Sage X3 hosting infrastructure.

Mail server or SMTP Gateway

A mail server is a computer program or software that forwards electronic
messages from one computer to another. Mail servers move and store mail
over corporate networks via LANs and WANs and across the internet.

Sage X3 users are not directly in contact with the mail server but use a mail
client application, like Microsoft Outlook, to communicate with the mail
server through the SMTP text-based protocol.

A mail server or SMTP Gateway is mandatory for using workflow

functionalities, however, supplying and installing this server does not fall
within the functions of Sage or the details of this architecture.

Search Engine
Elasticsearch®, is a free, open source search engine based on the Lucene
engine 100% Java under the Apache License 2.0. There are no additional
database engines to be installed.

Elasticsearch® provides real-time text-based search on the application data

that has been setup to be indexed.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 8

Sage X3

Client workstations
Desktop or laptop
Users can access Sage X3 applications on the Application server via a web
browser from their workstations.

Different web browsers are certified with Sage X3:

• Windows 7, 8, 10, and Windows Server 2012 workstation:

• Internet Explorer version 11

• Edge (on Windows 10)

• Chrome version 45 or higher

• Firefox version 41 or higher

• Opera version 31 or higher

• Mac OS X workstation:

• Safari version 8 or higher

• Chrome version 45 or higher

• Firefox version 41 or higher

• Opera version 31 or higher

Other web browsers or versions are compatible but not certified:

• Windows 7, 8, 10, and Windows Server 2012 workstation:

• Internet Explorer version 10

• Linux workstation:

• Chrome version 45 or higher

• Firefox version 41 or higher

• Opera version 31 or higher

Smartphones and tablets

Other web-enabled devices can provide access to Sage X3 and Sage HR
Management Applications, subject to certain display conditions.

These devices have been tested for compatibility:

• Smartphones

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 9

Sage X3

• Apple iPhone 4, 5 and 6 running IOS 8 or higher (Safari 8+, Chrome

45+)

• Android OS 4.3 or higher (Chrome 45+, Firefox 41+)

• Windows Phone 7.1 or higher (IE 11)

• Tablets

• Apple iPad (2,3,4, Air, mini, retina) running IOS 8 or higher (Safari 8+,
Chrome 45+)

• Android OS 4.3 or higher (Chrome 45+, Firefox 41+)

• Microsoft Surface running Windows RT 8.1 (IE 11)

Development platform
• Development Workbench: SAFE X3 Framework
• Development language for the application software: Sage X3 4GL
• Development language for the Web Server: JavaScript, HTML5
• Exchange protocol between the Client and the Web Server: pure HTTP
(according to the HTML 5.x specification) and Web application interface is
built on a technology like Ajax.
• Tool for packaging Sage X3 components: IzPack, open source software
built on the Java platform

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 10

Sage X3

Global schema of the technical architecture

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 11

Sage X3

Network and bandwidth

Network requirements
A Gigabit (or better, 10 Gb) link is necessary among the different servers that
host the Sage X3 applications.
Definitions
When these servers are installed on Windows platform, it is highly ACTIVE DIRECTORY
recommended there are members of an Active Directory Domain and belong to
the same branch (same IP address range). The only exception is the Web, Centralized system of
Microsoft Terminal Service or Citrix XenApp front-end servers, which can be identification and authentication
services to a network of
part of a DMZ-type sub-network. computers using the Windows
operating system. The Active
Directory lists user accounts,
In computer networks, a demilitarized zone (DMZ) is a computer servers, workstations, shared
host or small network inserted as a neutral zone between a folders, printers, etc.
company’s private network and the outside public network. It
prevents outside users from getting direct access to a server that DEMILITARIZED ZONE (DMZ)
has company data.
Subnetwork isolated from the
The different servers must also be registered in a DNS domain, allowing the local network and from the
different machines to recognize their fully qualified domain name (FQDN) internet
including that of Unix and/or Linux machines.
DOMAIN NAME SYSTEM (DNS)
The servers on which Sage components are installed should not be used as an Service used to match an IP
Active Directory Controller (DC) whether Primary or Backup. address with a domain name

SAFE X3 components communicate through sockets. In the case of a timeout FULLY QUALIFIED DOMAIN
or disconnection due to security components like firewalls, some Sage NAME (FQDN)
components can retrieve the socket connection for other components. The It indicates the absolute
Sage parameters need to be modified to synchronize the timeout of the user’s position of a node in the DNS tree,
connection with the firewall rules. If this occurs, confirm that everything is showing all top-level domains to
working properly, otherwise change the firewall rules so that sockets are not the root.
disconnected or closed. SOCKETS
Interface for communication
It is strongly recommended to implement the same speed and transfer mode between the various Sage
values between network card(s) installed on the servers and the ports for the technological components
switch(es). installed on the network using the
TCP/IP protocol

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 12

Sage X3

Network bandwidth between workstation and front- end servers

Bandwidth
Workstation Front-end Server
without printing and BO requesting
60 KBps per user
Web Client Web Server (Sage) - 50 KBps Web server -> Browser
- 10 KBps Browser -> Web server
Web Client via RDP Terminal Service
24 KBps per session
protocol (Microsoft)
Web Client via ICA
XenApp Server (Citrix) 12 KBps per session
protocol
ADC client Web Server (Sage) 20 KBps per device

Antivirus
If you install antivirus protection, we recommend disabling real-time protection
and instead, review files overnight when there are few or no users logged in for
best performance. Tips
Exclude the following directories from the real-time protection if active: Disable real-time

• The directory that is on the application server "... \folders" and all its
virus protection

subdirectories Run antivirus scan

• The directory "... \runtime" which is on the application server and contains overnight
many trace files

Microsoft updates
We recommend taking all necessary precautions when installing Microsoft
updates because there is always a risk that they could alter how the system
environment functions.

Before installing Microsoft updates in the production environment: Tips

• Perform a full system backup to easily restore if a serious anomaly is Perform a full backup
detected. before applying
• Test in a pre-production environment and verify the continuity of Sage updates
application operations.
Test updates in a pre-
If you encounter a problem with Sage applications following the Microsoft production
update, we will try to give you all the necessary assistance to identify the environment
problem and provide a solution as quickly as possible.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 13

Sage X3

Sage installs many of the global Windows patches on our own

network and qualification environments. An update that worked
well at Sage does not guarantee it will work in all environments.

Virtualization
The information in this document is intended for physical hardware. However,
you can deploy the solution in a virtual environment like VMware vSphere,
Hyper-V, RedHat KVM, Citrix XenServer or Oracle VM.

Most Sage X3 components below can be deployed on virtual machines.

• Application and Main processing server

• Additional processing server
• Print server
• Web Syracuse server
• Elastic Search server
• Web Services & RF server
• Java Bridge server
If you decide to virtualize your architecture, you must acquire and
develop a physical infrastructure adapted to a virtual environment
for optimum performance. We recommend dedicated resources
assigned to your environment, rather than sharing resources.

A production virtualization architecture should be built with

multiple physical hosts and rely on a shared storage system
(SAN) providing high availability and adequate performance to
cope with the I/O and throughput need of all hosted VMs and
applications.

Plan to acquire adequate backup tools so that you can save online
virtual machines and consider a redundancy of the bay and
physical blades.

For project environments (like development, training, recovery, etc.), deploying

the database within a virtual infrastructure is possible because performance is
not a major issue.

Except for the production environment, we strongly recommend installing the

Database and the Application and Main processing components on a physical
server for getting the lowest possible latency between database and business
logic execution in order to achieve the best performance.

However, if you opt for a virtual infrastructure, Sage cannot predict the
performance of its software applications. Therefore, we suggest a sufficiently
large virtual machine so that it can serve as a potential production server and
use the design phase of the project to determine the performance of the virtual
infrastructure before going live. In this way, you can improve the virtual

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 14

Sage X3

infrastructure if necessary to make it more efficient or switch to a physical,

dedicated server.

To help determine the quality of an infrastructure regardless of its nature

(physical or virtual, mono or multi-tier, Oracle or SQL Server, Unix-Linux or
Windows, etc.), Sage can provide a test program to measure the performance
of its software application that carries out seven actions in the database of the
reference folder (read, write, delete).

The results of this program can help you identify and determine how
performance compares to previously measured criteria based on benchmarks
and feedback from other customers’ production infrastructures.

Architecture performance rankings

Although there are many types of possible architectures for Sage X3, the most
common are listed below.

Physical Single-tier IBM Aix & Oracle *

Physical Single-tier Linux & Oracle *
Physical Single-tier Windows x64 & Oracle *
General Increased Performance

Physical
* Single-tier Windows x64 & SQL Server *
S
Virtual Single-tier Windows x64 & Oracle **
i
Virtual Single-tier Windows x64 & SQL Server **
n
Physical
g Multi-tier Windows x64 & Oracle
lPhysical Multi-tier Windows x64 & SQL Server
e
Virtual
- Multi-tier Windows x64 & Oracle **
t
Virtual Multi-tier Windows x64 & SQL Server **
i
er environments generally have reduced high availability,
scalability, and security compared to multi-tier architecture

**Virtual environments are not recommended for production

systems due to reduced performance.

If performance is the primary objective, a physical, single-tier architecture is

best.

If high availability, scalability, and security for larger implementations are of

primary concern, a multi-tier architecture is more appropriate.

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 15

Sage X3

Resource configuration
List of available operating systems
Resources Operating System versions
Windows Server x64 2012 R2
Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Database server
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
IBM Aix 7.1
Windows Server x64 2012 R2
Application and Main Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
processing server Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
IBM Aix 7.1
Windows Server x64 2012 R2
Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Additional processing server
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
IBM Aix 7.1

Print server Windows Server x64 2012 R2

Windows Server x64 2012 R2

Web server Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
Windows Server x64 2012 R2
Elasticsearch server Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
Windows Server x64 2012 R2
Web services and ADC server Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x
Windows Server x64 2012 R2
Java Bridge server Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Oracle Enterprise Linux x64 version 6.2 and later 6.x
Red Hat Enterprise Linux AS x64 version 7.1 and later 7.x
Oracle Enterprise Linux x64 version 7.1 and later 7.x

Business Objects server Windows Server x64 2012 R2

Windows 7, 8, 10 (x86, x64)
Web client workstation Windows Server 2012 (R2) x64
Mac OS X

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 16

Sage X3

List of database versions

Operating System Database versions

Requirements for new customers

Oracle Database 12c (12.1.0.1) 64-bit in Standard &

Enterprise
SQL Server 2014 SP1 in Standard & Enterprise
Windows Server x64 2012 R2 Named instance
Binary sort order
Mixed mode authentication (SQL Server &
Windows)

Oracle Database 12c (12.1.0.1) 64-bit in Standard &

All Unix and Linux platforms Enterprise

Allowed for customer doing migration from V7 or PU8

Oracle Database 11g R2 (11.2.0.4) 64-bit or
Oracle Database 12c (12.1.0.1) 64-bit in Standard &
Enterprise
SQL Server 2012 SP2 or SQL Server 2014 SP1 in
Windows Server x64 2012 R2 Standard & Enterprise
Named instance
Binary sort order
Mixed mode authentication (SQL Server
& Windows)
Oracle Database 11g R2 (11.2.0.4) 64-bit or
All Unix and Linux platforms Oracle Database 12c (12.1.0.1) 64-bit in Standard &
Enterprise

Distribution of components in a 2-tier architecture

Resources Processes Process origin

1 x oracle.exe / instance engine SGBD Oracle

Database & 1 x sqlserver.exe / instance engine SGBD SQL Server
Application main 1 x adxdsrv.exe / solution X3 main engine
runtime 2 x n x adonix.exe
X3 processes
Web server n x sadora.exe / sadoss.exe 1
Search engine x node.exe + mongodb.exe 1 http Server
Print server x ElastSch.exe Search engine
1 x adxsrvimp.exe Sage Print server

iexplore.exe, firefox.exe,
Client workstation Internet browser
chrome.exe, safari.exe

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 17

Sage X3

Distribution of components in a 3-tier architecture

Resources Processes Process origin
1 x oracle.exe / instance or engine SGBD Oracle
Database 1 x sqlserver.exe / instance
engine SGBD SQL Server
1 x adxdsrv.exe / solution 2 x X3 main engine X3
Application main runtime n x adonix.exe
processes
Web server n x sadora.exe / sadoss.exe 1 x
Search engine node.exe + mongodb.exe 1 x http Server Search
Print server ElastSch.exe engine Sage Print
1 x adxsrvimp.exe server
iexplore.exe, firefox.exe,
Client workstation Internet browser
chrome.exe, safari.exe

Distribution of components up to a 3-tier

architecture
Resources Processes Process origin
1 x oracle.exe / instance or engine SGBD Oracle
Database 1 x sqlserver.exe / instance
engine SGBD SQL Server
1 x adxdsrv.exe / solution n x X3 main engine X3
Application main runtime
sadfsq.exe process
1 x adxdsrv.exe / solution 2 x X3 additional engine
Additional runtime n x adonix.exe X3 process
n x sadora.exe / sadoss.exe X3 process
1 x node.exe + mongodb.exe 1 x http Server Search
Web server
ElastSch.exe engine

Print server 1 x adxsrvimp.exe Sage Print server

iexplore.exe, firefox.exe,
Client workstation Internet browser
chrome.exe, safari.exe
n = number of concurrent users
1 Adonix in Syracuse mode that is shared between landing pages and navigation
Syrapedia
1 Adonix convergence mode that is created when you open a convergence function and
is retained for reuse later

Memory size occupied by Sage X3 processes

Resources Processes Physical RAM Memory
4 GB minimum 12%
1 x oracle.exe / instance data+index > 40 GB 10%
Database
1 x sqlserver.exe / instance data+index > 80 GB 8%
data+index > 150GB
Server

1 x adxdsrv.exe / solution 2 5 MB
Application main runtime x n x adonix.exe 60 MB
n x sadora.exe or sadoss.exe 25 MB
1 x adxdsrv.exe / solution 2 5 MB
Additional runtime x n x adonix.exe 30 MB
n x sadora.exe ou sadoss.exe 25 MB

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 18

Sage X3

iexplore.exe, firefox.exe,
Client workstation 100-200 MB
chrome.exe, safari.exe
n = number of concurrent users

Other Sage X3 processes distribution

Resources Processes Process origin
ApacheMonitor.exe Internal X3 pagespublication
Application Server
ElastSch.exe Search engine
Node.exe Web presentation server for users
Web Server
Mongod.exe and web services
Web Services & ADC Apache.exe Tomcat.exe HTTP Apache software Web
Server Services container
Apache.exe Tomcat.exe HTTP Apache software Java
Java Bridge Server
Bridge container
Print Server AdxSrvImp.exe Safe X3 Print engine

Business Objects Server sia.exe SAP Business Objects

iexplore.exe, firefox.exe, Internet browser

Client Workstation chrome.exe, safari.exe

List of additional software to be installed

Resources under which the
Software Version
software must be installed
JRE (Java Runtime
7 minimum, 8 recommended All Servers
Environment)
Database engine Oracle / SQL Server Database Server

Apache http Server 2.2.25 Application Server

Elastic Search* 1.5 Application Server

Server running Elastic Search
JDK (Java Development Kit) 7 minimum, 8 recommended
engine
Node.js* 12.6 Web Syracuse Server

MongoDB* 2.6 Web Syracuse Server

SAP Business Objects** 4.1 SP3 Patch 1 Business Objects Server

Apache Tomcat* 6.0.18 Web Services or Java Bridge Server

Apache http Server* 2.2 Web Services or Java Bridge Server

Business Objects Server
11gR2
Oracle Client 64-bit
12c

2010 & 2013, but also

Microsoft Office version 32 bits 2010 & 2013 shipped Workstation
with Office 365
Adobe Flash Player 10 or > Workstation

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 19

Sage X3

Adobe Reader (230MB) XI or > Workstation

* component delivered on the Sage X3 Installation DVD-ROM
** component delivered on the Sage X3 Installation DVD-ROM for Windows

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 20

Sage X3

Remote connection
A remote connections requires a VPN connection through an internet
connection. Definition
VPN
The VPN connection can be establish by using any of the standard VPN
applications available like Microsoft VPN Client or Cisco. Virtual private
network, a system
To facilitate the remote connection to your site, provide Sage with all the that creates a direct
instructions regarding installation and configuration (list of port tcp/udp #) of link between remote
your VPN application. computers

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 21

Sage X3

Sizing requirements
General prerequisites for databases and applications
Platform Windows Unix / Linux
Linux X86-64 (Intel Xeon 2.0GHz or
Processor type Quad Core Intel Xeon 2.0GHz or
IBM Power System (POWER7 / POWER8 3.6GHz or

Red Hat Enterprise Linux AS x64 version 6.2 &

Operating later 6.x
Windows Server 2012 R2 64 bits
System Oracle Enterprise Linux x64 version 6.2 & later 6.x
IBM Aix 7.1
Freeware
Java Runtime Environment 7 or 8, Java Software Development Kit 7 or 8, Apache HTTP Server 2.2.25
Components
2 GB (for the Operating System)
+ 4 GB minimum (per instance of database)
RAM memory
+ 85 MB per user connected under a Windows Server
+ 105 MB per user connected under a Unix or Linux Server
Virtual memory Swap disk
Virtual space
2 x the size of the RAM memory 1.5 to 2 x the size of the RAM memory
2 cores minimum for the database 2 cores minimum for the database
Processor
+ 1 core by range of 40 users + 1 core by range of 40 users
Oracle Database 11g R2 (11.2.0.4) 64-bit Oracle Database 11g R2 (11.2.0.4) 64-bit
(Update) (update)
Database Oracle Database 12c (12.1.0.1) 64-bit Oracle Database 12c (12.1.0.1) 64-bit
Standard & Enterprise Standard & Enterprise
Under Unix-Linux platforms Oracle
SQL Server 2012 SP2 installation requires 400 MB of disk space
SQL Server 2014 SP1 available in the temporary file-system

Windows = 60 Unix = 30
Oracle = 6+ Oracle = 6+
Disk space SQL Server = 3
(GB) X3 X3+SEED = 12 X3 X3+SEED = 12
Payroll & HR PAYE+PAYEDEMO = 6 Payroll & HR PAYE+PAYEDEMO =6
Database files > 10 Database Files >10
RAID 1 Mirroring Security >= 2 disks Mirroring
RAID RAID 5 with parity control Security at low cost >= 3 disks Mirroring +
(optional)
RAID 1+0 stripping Security & performance >= 4 disks
2 x 72 GB 15k/tpm RAID 1, for the Operating System and the database engine
Disk 4 x 140 GB 15k/tpm RAID 10, for the application and the data files
Architecture 2 x 140 GB 15k/tpm RAID 1, for Oracle Archive Log Files or the SQL Server Transactions logs
under Windows Operating System the disk must be formatted with NTFS File System
Network Ethernet Card 100 MBps minimum or 1 GBps recommended
User account Group User Accounts Group
Oracle : ORA_DBA Oracle : oinstall, dba
SQLserver: sagex3 : sagex3
User Accounts sagex3 : Administrators
User Rights Assignment
Log on as a service

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 22

Sage X3

Database and application server

Limitations: Definitions
• The server(s) is(are) dedicated to Sage X3. SINGLE-TIER
• Only one Sage production environment is present on the machine(s).
ARCHITECTURE

• Only two database instances are stored on the database server for the Architecture model where all
components are installed on
production and the data warehouse.
•
a single machine
Only the Sage database and Sage application resources are installed on
the machine(s).
•
MULTI-TIER
Options for additional machines : ARCHITECTURE

• To install other resources: Business Objects engine, Web Server, Print,

Logical application
architecture model whose
Citrix-TSE, etc. aim is to:
• To implement additional environments: development, test, and training.
1) Model an application as a
stack of software layers. The
function of each layer is
Deployment of a single-tier architecture clearly defined:
(physical server) -The presentation layer is
Resources Sizing recommendations the visible part of the
application and is interactive
Single processor Intel Quad Core
2.8GHz RAM Memory 24 GB
with users.
Windows Server x64 2012 R2
Linux 6.2 or later 6.x, 7.1 or later 7.x Red (2GB for the OS, 6 GB for 60 X3 users & 5 -The business layer reflects
Hat / OEL Server batch processes + 5 GB production its respective application and
database instance + 3 GB data warehouse programs.
From 30 to 60 users instance + 8 GB free)
-The management and data
Single processor Intel 6 Core access layer.
Windows Server x64 2012 R2 2.8GHz RAM Memory 32 GB
Linux 6.2 or later 6.x, 7.1 or later 7.x Red (2 GB for the OS, 11 GB for 120 X3 users 2) Allocate these layers
Hat / OEL Server & 8 batch processes, 8 GB production
according to a technical
database instance, 4 GB data warehouse
instance + 7 GB free) architecture on physical and/
From 60 to 120 users
or virtual machines – usually
Dual processor Intel 6 Core three, but they can be more.
Windows Server x64 2012 R2 2.8GHz RAM Memory 48 GB
Linux 6.2 or later 6.x, 7.1 or later 7.x Red (2GB for the OS, 21GB for 250 X3 users & 8
Hat / OEL Server batch processes, 12 GB production
database instance, 6 GB data warehouse
From 120 to 250 users instance + 7GB free)

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 23

Sage X3

Deployment of a multiple-tier architecture (mixed)

Resources Sizing recommendations
Database and application-main processing server:
Windows Server x64 2012 R2 (physical machine)
Linux 6.2 or later 6.x, 7.1 or later 7.x Red Hat / Single processor Intel 6 Core 2.8 GHz
OEL Server RAM Memory 32 GB
(2GB for the OS, 12 GB production database instance, 6 GB data
warehouse instance + 6 GB Sage software + 6 GB free)
From 100 to 250 users
Additional processing server:
(physical or virtual machine)
Single processor Intel 6 Core 2.8GHz or 6 vCPU
RAM Memory 24 GB
Database and application-main processing server:
Windows Server x64 2012 R2 (physical machine)
Linux 6.2 or later 6.x, 7.1 or later 7.x Red Hat / Single processor Intel 6 Core 2.8 GHz
OEL Server RAM Memory 48 GB
(2GB for the OS, 16 GB production database instance, 8 GB data
warehouse instance + 10 GB Sage software + 12 GB free)
From 250 to 500 users
2 x additional processing servers:
(physical or virtual machine)
Single processor Intel 6 Core (X5660) 2.8 GHz or 6 vCPU
RAM Memory 24 GB

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 24

Sage X3

Front-end servers
Resources Sizing recommendations (physical) not Sizing recommendations (virtual) not
including OS needs (typically 2 GB) including OS needs (typically 2 GB)
1 CPU Intel i5, i7, Xeon >= 2.0 GHz
1 to 2 vCPU(s) >= 2.0 GHz
2 GB RAM
Print server 2 GB RAM

Provision a temporary work area on disk 10 GB minimum

Web Syracuse For every 65 concurrent web sessions: For every 65 concurrent web sessions:
server o 1 CPU core from Intel Xeon 2.4 GHz o 1 vCPU 2.4 GHz
o 2 GB RAM o 2 GB RAM
o 2 processes node.js o 2 processes node.js

MongoDB server 1 CPU core from Intel Xeon 2.4 GHz 1 vCPU from Intel Xeon 2.4
0.5 GB RAM minimum GHz
Minimum disk space: 10GB 10 k/tpm 0.5 GB RAM minimum
Minimum disk space: 10 GB 10 k/tpm 10
ElasticSearch server 1 CPU core from Intel Xeon 2.4GHz 1 vCPU 2.4GHz
1GB RAM minimum / 1GB RAM minimum / disk minimum
Minimum disk space: 2GB 10 k/tpm 2GB 10 k/tpm
(recommended 10% of the X3 folder size per language) (recommended 10% of the X3 folder size per
language)

Front-end server
Citrix XenApp
Microsoft TS
Intel Xeon Quad Core 2.8 GHz / 8 GB RAM 1 vCPU 2.8GHz / 8 GB RAM
-for 30 memory / disk 2 x 72 GB 15ktpm in RAID-1 / disk 72 GB 15 k/tpm
connections
Intel Xeon Quad Core 2.8 GHz / 16 GB RAM
-for 60 memory / disk 2 x 72 GB 15ktpm in RAID-1 2 vCPU 2.8GHz / 16 GB RAM
connections / disk 72 GB 15 k/tpm
Intel Xeon Quad Core 2.8 GHz / 22 GB RAM
-for 100 memory / disk 2 x 7 GB 15 k/tpm in RAID-1
connections 4 vCPU 2.8GHz / 22 GB RAM
/ disk 72 GB 15 k/tpm

Provision a working area of 250 MB per user

To increase security: we recommend to implement several machines configured
in Load Balancing

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 25

Sage X3

Additional processing server

Resources :
Additional process Sizing recommendations (physical) Sizing recommendations (virtual)
server
Windows
- for 150 users Single processor Quad Core Intel 4 vCPU 2.66 GHz / 14 GB RAM
Xeon 2.66 GHz / 14 GBRAM

- for 300 users Dual processor Quad Core Intel Xeon 8 vCPU 2.66 GHz / 28 GB RAM
2.66 GHz / 28 GBRAM

Linux
- for 150 users Single processor Quad Core Intel 4 vCPU 2.66 GHz / 16 GB RAM
Xeon 2.66 GHz / 16GB RAM
8 vCPU 2.66 GHz / 32 GB RAM
- for 300 users Dual processor Quad Core Intel Xeon
2.66 GHz / 32GB RAM

IBM-Aix IBM POWER 7/8 4 cores IBM POWER 7 8 LCPUs

- for 300 users 3.6GHz 32GB RAM 3.6GHz 32GB RAM

- for 600 users IBM POWER 7/8 8 cores IBM POWER 7 8 LCPUs
3.6GHz 64GB RAM 3.6GHz 64GB RAM

Workstations
Resources Sizing recommendations
Intel Core i3, i5, i7 or equivalent in AMD

2 GB RAM memory minimum (4 GB recommended)

Web workstation
Display 1280 x 768 pixels color 32-bits
Internet Explorer 10 minimum is required on the workstation to
the Excel add-in

The information contained herein is confidential and may be changed without notice. Although Sage makes
every effort to provide accurate information, no implicit or explicit warranty is given regarding the content of
this document.

Copyright © 2015 Sage Software, Inc. All rights reserved. 26