Architecture Guide SafeX3u9 ENG V1a

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
Page 2 of 10
Sage X3
Introduction
This document provides information on system requirements and
setup for Sage Architecture for the Enterprise (SAFE X3). SAFE X3
is a common technological platform for developing application
software.
General overview
The following application software is developed using the technological
platform SAFE X3:
Sage X3
Sage HR management
Sage WMS Geode (pending)

The technical architecture is organized in layers and designed to:
Definitions
BATCH SERVER
The application software
offers a standard scheduling
function in a postponed
mode (batch) to manage a
large number of parameters
for the launch of these
processes.
BATCH TASK
Unlike an interactive session,
the batch task is a process
launched in batch mode by
the task scheduler (batch
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.
Sage X3
Administration tasks include:
Creating new folders,

Duplicating folders from a model,
Removing any unnecessary folders,
Creating backup folders.
this document.
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 (dictionary), and the parameter data.
APPLICATION DATA
SAFE X3 products are developed according to the database editor

recommendations, which guarantee the integrity and the coherence of the data
stored in the database.
There is no limit to the size of the database and it can vary from 30 to 80 GB,
with some databases reaching hundreds of gigabytes. To reduce the size of
the database, you can purge or archive large tables.
Tables and indexes that

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

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:

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
this document.
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
this document.
10
Sage X3
Global schema of the technical architecture
this document.
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.
When these servers are installed on Windows platform, it is highly
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,
Microsoft Terminal Service or Citrix XenApp front-end servers, which can be
part of a DMZ-type sub-network.
In computer networks, a demilitarized zone (DMZ) is a computer
host or small network inserted as a neutral zone between a
companys private network and the outside public network. It
prevents outside users from getting direct access to a server that
has company data.
The different servers must also be registered in a DNS domain, allowing the
different machines to recognize their fully qualified domain name (FQDN)
including that of Unix and/or Linux machines.
The servers on which Sage components are installed should not be used as an
Active Directory Controller (DC) whether Primary or Backup.
SAFE X3 components communicate through sockets. In the case of a timeout
or disconnection due to security components like firewalls, some Sage
components can retrieve the socket connection for other components. The
Sage parameters need to be modified to synchronize the timeout of the users
connection with the firewall rules. If this occurs, confirm that everything is
working properly, otherwise change the firewall rules so that sockets are not
disconnected or closed.
It is strongly recommended to implement the same speed and transfer mode
values between network card(s) installed on the servers and the ports for the
switch(es).
Definitions
ACTIVE DIRECTORY
Centralized system of
identification and authentication
services to a network of
computers using the Windows
operating system. The Active
Directory lists user accounts,
servers, workstations, shared
folders, printers, etc.
DEMILITARIZED ZONE (DMZ)
Subnetwork isolated from the
local network and from the
internet
DOMAIN NAME SYSTEM (DNS)
Service used to match an IP
address with a domain name
FULLY QUALIFIED DOMAIN
NAME (FQDN)
It indicates the absolute
position of a node in the DNS tree,
showing all top-level domains to
the root.
SOCKETS
Interface for communication
between the various Sage
technological components
installed on the network using the
TCP/IP protocol
this document.
12
Sage X3
Network bandwidth between workstation and front- end servers

Workstation
Front-end Server
Web Client
Web Server (Sage)
Bandwidth
without printing and BO requesting
60 KBps per user

-
50 KBps Web server -> Browser

10 KBps Browser -> Web server
Web Client via RDP

protocol
Web Client via ICA
protocol
Terminal Service
(Microsoft)
24 KBps per session
XenApp Server (Citrix)
12 KBps per session
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.
Exclude the following directories from the real-time protection if active:
The directory that is on the application server "... \folders" and all its
subdirectories
The directory "... \runtime" which is on the application server and contains
many trace files
Tips
Disable real-time
virus protection
Run antivirus scan
overnight
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:
Perform a full system backup to easily restore if a serious anomaly is

detected.
Test in a pre-production environment and verify the continuity of Sage
application operations.
If you encounter a problem with Sage applications following the Microsoft

update, we will try to give you all the necessary assistance to identify the
problem and provide a solution as quickly as possible.
Tips
Perform a full backup
before applying
updates
Test updates in a preproduction
environment
this document.
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
this document.
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
General Increased Performance
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 *
Physical
*
Single-tier
Windows x64 & SQL Server *
S
Virtual
Single-tier
Windows x64 & Oracle **
i
Virtual
Single-tier
Windows x64 & SQL Server **
n
Physical
Multi-tier
Windows x64 & Oracle
g
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.
this document.
15
Sage X3
Resource configuration
List of available operating systems
Resources
Database server
Application and Main

processing server
Print server
Web server
Elasticsearch server
Web services and ADC server
Java Bridge server
Operating System versions

Windows Server x64 2012 R2
Red Hat Enterprise Linux AS x64 version 6.2 and later 6.x
Oracle Enterprise Linux x64 version 6.2 and later 6.x
IBM Aix 7.1
IBM Aix 7.1
IBM Aix 7.1
Business Objects server
Web client workstation
Windows 7, 8, 10 (x86, x64)

Windows Server 2012 (R2) x64
Mac OS X
this document.
16
Sage X3
List of database versions

Operating System
Database versions
Requirements for new customers
All Unix and Linux platforms
Oracle Database 12c (12.1.0.1) 64-bit in Standard &

Enterprise
SQL Server 2014 SP1 in Standard & Enterprise
Named instance
Binary sort order
Mixed mode authentication (SQL Server &
Windows)
Enterprise
Allowed for customer doing migration from V7 or PU8
Oracle Database 11g R2 (11.2.0.4) 64-bit or

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

Enterprise
Distribution of components in a 2-tier architecture

Resources
Processes
Process origin
Database &
Application main
runtime
Web server
Search engine
Print server
1 x oracle.exe / instance
1 x sqlserver.exe / instance
1 x adxdsrv.exe / solution
2 x n x adonix.exe
n x sadora.exe / sadoss.exe 1
x node.exe + mongodb.exe 1
x ElastSch.exe
1 x adxsrvimp.exe
engine SGBD Oracle

engine SGBD SQL Server
X3 main engine
Client workstation
iexplore.exe, firefox.exe,
chrome.exe, safari.exe
X3 processes
http Server
Search engine
Sage Print server
Internet browser
this document.
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

Application main runtime
Web server
Search engine
Print server
1 x adxdsrv.exe / solution 2 x
n x adonix.exe
n x sadora.exe / sadoss.exe 1 x
node.exe + mongodb.exe 1 x
ElastSch.exe
1 x adxsrvimp.exe
Client workstation
Distribution
architecture
of
components
up
X3 main engine X3
processes
http Server Search
engine Sage Print
server
Internet browser
to
3-tier
Resources
Processes
Process origin
1 x oracle.exe / instance or
engine SGBD Oracle
Database

1 x adxdsrv.exe / solution n x
sadfsq.exe
X3 main engine X3
process
Additional runtime
1 x adxdsrv.exe / solution 2 x
n x adonix.exe
n x sadora.exe / sadoss.exe
X3 additional engine
X3 process
X3 process
Web server
1 x node.exe + mongodb.exe 1 x
ElastSch.exe
http Server Search

engine
Print server
1 x adxsrvimp.exe
Sage Print server
Client workstation
Internet browser
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
Server
Database
Additional runtime
Processes
1 x oracle.exe / instance
1 x adxdsrv.exe / solution 2
x n x adonix.exe
n x sadora.exe or sadoss.exe
1 x adxdsrv.exe / solution 2
x n x adonix.exe
n x sadora.exe ou sadoss.exe
Physical RAM Memory

4 GB minimum 12%
data+index > 40 GB 10%
data+index > 80 GB 8%
data+index > 150GB
5 MB
60 MB
25 MB
5 MB
30 MB
25 MB
this document.
18
Sage X3
Client workstation
100-200 MB
n = number of concurrent users
Other Sage X3 processes distribution

Resources
Processes
Process origin
ApacheMonitor.exe
Internal X3 pagespublication
ElastSch.exe
Search engine
Node.exe
Mongod.exe
Apache.exe Tomcat.exe
Application Server
Print Server
AdxSrvImp.exe
Web presentation server for users

and web services
HTTP Apache software Web
Services container
HTTP Apache software Java
Bridge container
Safe X3 Print engine
sia.exe
SAP Business Objects
Internet browser
Client Workstation
Web Server
Web Services & ADC
Server
Java Bridge Server
Apache.exe Tomcat.exe
List of additional software to be installed

Software
Version
Resources under which the

software must be installed
JRE (Java Runtime

Environment)
7 minimum, 8 recommended
All Servers
Database engine
Oracle / SQL Server
Database Server
Apache http Server
2.2.25
Application Server
Elastic Search*
1.5
Application Server
JDK (Java Development Kit)
7 minimum, 8 recommended
Server running Elastic Search

engine
Node.js*
12.6
Web Syracuse Server
MongoDB*
2.6
Web Syracuse Server
SAP Business Objects**
4.1 SP3 Patch 1
Apache Tomcat*
6.0.18
Web Services or Java Bridge Server
Apache http Server*
2.2
Web Services or Java Bridge Server
Oracle Client 64-bit
11gR2
12c
Microsoft Office version 32 bits
2010 & 2013, but also

2010 & 2013 shipped
with Office 365
Workstation
Adobe Flash Player
10 or >
Workstation
this document.
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
this document.
20
Sage X3
Remote connection
A remote connections requires a VPN connection through an internet
connection.
The VPN connection can be establish by using any of the standard VPN
applications available like Microsoft VPN Client or Cisco.
To facilitate the remote connection to your site, provide Sage with all the
instructions regarding installation and configuration (list of port tcp/udp #) of
your VPN application.
Definition
VPN
Virtual private
network, a system
that creates a direct
link between remote
computers
this document.
21
Sage X3
Sizing requirements
General prerequisites for databases and applications
Platform
Windows
Processor type
Quad Core Intel Xeon 2.0GHz or
Unix / Linux
Linux X86-64 (Intel Xeon 2.0GHz or
IBM Power System (POWER7 / POWER8 3.6GHz or
Red Hat Enterprise Linux AS x64 version 6.2 &
later 6.x
Oracle Enterprise Linux x64 version 6.2 & later 6.x
IBM Aix 7.1
Operating
System
Windows Server 2012 R2 64 bits
Freeware
Components
Java Runtime Environment 7 or 8, Java Software Development Kit 7 or 8, Apache HTTP Server 2.2.25
RAM memory
2 GB (for the Operating System)

+ 4 GB minimum (per instance of database)
+ 85 MB per user connected under a Windows Server
+ 105 MB per user connected under a Unix or Linux Server
Virtual space
Virtual memory
2 x the size of the RAM memory
Swap disk
1.5 to 2 x the size of the RAM memory
Processor
2 cores minimum for the database

+ 1 core by range of 40 users
2 cores minimum for the database

+ 1 core by range of 40 users
Oracle Database 11g R2 (11.2.0.4) 64-bit

(Update)
Oracle Database 12c (12.1.0.1) 64-bit
Oracle Database 11g R2 (11.2.0.4) 64-bit

(update)
Oracle Database 12c (12.1.0.1) 64-bit
Database
Under
Unix-Linux
platforms
Oracle
installation requires 400 MB of disk space
available in the temporary file-system
SQL Server 2012 SP2

SQL Server 2014 SP1
Disk space
(GB)
RAID
(optional)
Disk
Architecture
Network
Windows
Oracle
SQL Server
X3
Payroll & HR
Database files
RAID 1
RAID 5
RAID 1+0
X3+SEED
PAYE+PAYEDEMO
Mirroring
with parity control
stripping
60
6+
3
12
6
10
= 30
= 6+
Unix
Oracle
X3
Payroll & HR
Database Files
Security
Security at low cost
Security & performance
X3+SEED
PAYE+PAYEDEMO
= 12
=6
>10
>= 2 disks Mirroring

>= 3 disks Mirroring +
>= 4 disks
2 x 72 GB 15k/tpm RAID 1, for the Operating System and the database engine
4 x 140 GB 15k/tpm RAID 10, for the application and the data files
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
Ethernet Card 100 MBps minimum or 1 GBps recommended
User account
User Accounts
=
=
=
=
=
>
Oracle :
SQLserver:
sagex3 :
Group
ORA_DBA
User Accounts
Oracle :
sagex3 :
Group
oinstall, dba
sagex3
Administrators
User Rights Assignment

Log on as a service
this document.
22
Sage X3
Database and application server

Limitations:
Definitions
The server(s) is(are) dedicated to Sage X3.

Only one Sage production environment is present on the machine(s).
Only two database instances are stored on the database server for the
production and the data warehouse.
Only the Sage database and Sage application resources are installed on
the machine(s).
Options for additional machines :
To install other resources: Business Objects engine, Web Server, Print,

Citrix-TSE, etc.
To implement additional environments: development, test, and training.
Deployment of a single-tier architecture

(physical server)
Resources
Sizing recommendations

Linux 6.2 or later 6.x, 7.1 or later 7.x Red
Hat / OEL Server
Single processor Intel Quad Core

2.8GHz RAM Memory 24 GB
(2GB for the OS, 6 GB for 60 X3 users & 5
batch processes + 5 GB production
database instance + 3 GB data warehouse
instance + 8 GB free)
From 30 to 60 users

Hat / OEL Server
From 60 to 120 users

Hat / OEL Server
Single processor Intel 6 Core

(2 GB for the OS, 11 GB for 120 X3 users
& 8 batch processes, 8 GB production
database instance, 4 GB data warehouse
instance + 7 GB free)
Dual processor Intel 6 Core
(2GB for the OS, 21GB for 250 X3 users & 8
batch processes, 12 GB production
database instance, 6 GB data warehouse
instance + 7GB free)
SINGLE-TIER
ARCHITECTURE
Architecture model where all

components are installed on
a single machine
MULTI-TIER
ARCHITECTURE
Logical application
architecture model whose
aim is to:
1) Model an application as a
stack of software layers. The
function of each layer is
clearly defined:
-The presentation layer is
the visible part of the
application and is interactive
with users.
-The business layer reflects
its respective application and
programs.
-The management and data
access layer.
2) Allocate these layers
according to a technical
architecture on physical and/
or virtual machines usually
three, but they can be more.
this document.
23
Sage X3
Deployment of a multiple-tier architecture (mixed)

Resources

Linux 6.2 or later 6.x, 7.1 or later 7.x Red Hat /
OEL Server
Database and application-main processing server:

(physical machine)
Single processor Intel 6 Core 2.8 GHz
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)

Linux 6.2 or later 6.x, 7.1 or later 7.x Red Hat /
OEL Server
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:
(physical machine)
Single processor Intel 6 Core 2.8 GHz
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)

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
this document.
24
Sage X3
Front-end servers
Resources
Sizing recommendations (physical) not

including OS needs (typically 2 GB)
1 CPU Intel i5, i7, Xeon >= 2.0 GHz
2 GB RAM
Print server
Sizing recommendations (virtual) not

including OS needs (typically 2 GB)
1 to 2 vCPU(s) >= 2.0 GHz
2 GB RAM
Provision a temporary work area on disk 10 GB minimum

Web Syracuse
server
For every 65 concurrent web sessions:

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

o 1 vCPU 2.4 GHz
o 2 GB RAM
o 2 processes node.js
MongoDB server
1 CPU core from Intel Xeon 2.4 GHz

0.5 GB RAM minimum
Minimum disk space: 10GB 10 k/tpm
1 vCPU from Intel Xeon 2.4

GHz
0.5 GB RAM minimum
Minimum disk space: 10 GB 10 k/tpm 10
ElasticSearch server
1 CPU core from Intel Xeon 2.4GHz

1GB RAM minimum /
Minimum disk space: 2GB 10 k/tpm
1 vCPU 2.4GHz
1GB RAM minimum / disk minimum
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
-for 30
connections
-for 60
connections
-for 100
connections
Intel Xeon Quad Core 2.8 GHz / 8 GB RAM

memory / disk 2 x 72 GB 15ktpm in RAID-1
memory / disk 2 x 72 GB 15ktpm in RAID-1
memory / disk 2 x 7 GB 15 k/tpm in RAID-1
1 vCPU 2.8GHz / 8 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
this document.
25
Sage X3

Resources :
Additional process
server
Windows
- for 150 users
- for 300 users
Linux
- for 150 users
Sizing recommendations (physical)
Sizing recommendations (virtual)
Single processor Quad Core Intel

Xeon 2.66 GHz / 14 GBRAM
4 vCPU 2.66 GHz / 14 GB RAM
Dual processor Quad Core Intel Xeon

2.66 GHz / 28 GBRAM
Single processor Quad Core Intel

Xeon 2.66 GHz / 16GB RAM

- for 300 users
Dual processor Quad Core Intel Xeon

2.66 GHz / 32GB RAM
IBM-Aix
- for 300 users
IBM POWER 7/8 4 cores

3.6GHz 32GB RAM
IBM POWER 7 8 LCPUs

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

3.6GHz 64GB RAM
IBM POWER 7 8 LCPUs

3.6GHz 64GB RAM
Workstations
Resources
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
this document.
26

Architecture Guide SafeX3u9 ENG V1a

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Architecture Guide SafeX3u9 ENG V1a

Uploaded by

Copyright:

Available Formats

How to

know on Architecture and

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

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

Copyright 2015 Sage Software, Inc. All rights reserved.

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

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

Copyright 2015 Sage Software, Inc. All rights reserved.

Sage WMS Geode (pending)

Separate the layers of data management, process execution, and

The database server.

When installing Sage X3, four folders are typically created:

X3_PUB A pseudo-folder that contains the publication objects (like

Administration tasks include:

Creating new folders,

SAFE X3 products are developed according to the database editor

Tables and indexes that

Application and Main processing server

Additional processing servers

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

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

Incoming and outgoing SOAP and REST WebServices (since PU9).

Web services and Automated Data Collection (ADC) servers

The Automated Data Collection devices,

Incoming SOAP Web services in legacy mode.

Java Bridge server

Business Objects Server

Mail server or SMTP Gateway

Different web browsers are certified with Sage X3:

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

Internet Explorer version 11

Safari version 8 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

Chrome version 45 or higher

Smartphones and tablets

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

Windows Phone 7.1 or higher (IE 11)

Development Workbench: SAFE X3 Framework

Global schema of the technical architecture

Network and bandwidth

Network bandwidth between workstation and front- end servers

Web Server (Sage)

60 KBps per user

50 KBps Web server -> Browser

Web Client via RDP

24 KBps per session

XenApp Server (Citrix)

12 KBps per session

Web Server (Sage)

20 KBps per device

Perform a full system backup to easily restore if a serious anomaly is

If you encounter a problem with Sage applications following the Microsoft

Sage installs many of the global Windows patches on our own

Application and Main processing server

A production virtualization architecture should be built with

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

Architecture performance rankings

General Increased Performance

IBM Aix & Oracle *

Linux & Oracle *

Windows x64 & Oracle *