Technology
Development platform
- Development language for the application business logic: Sage X3 4GL
- Development language for mobile applications: TypeScript and GraphQL
- Development language for the web server: JavaScript, HTML5
- Exchange protocol between the client and the web server: pure HTTP/HTTPS (according to HTML 5.x specifications) and web application interface built on a technology like Ajax
- Tool for packaging Sage X3 components: IzPack, open source software built on the Java platform
Technical architecture: global schema
Network and bandwidth requirements
Active Directory (AD)
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, and so on.
Demilitarized Zone (DMZ)
A computer host or small network inserted as a neutral zone between a company’s private network and the outside public network. It prevents outside users from getting direct access to a server that has company data.
Domain Name System (DNS)
Service used to match an IP address with a host and domain name in both ways.
Fully Qualified Domain Name (FQDN)
It indicates the absolute position of a node in the DNS tree, showing all domains up to the top-level (root).
Server-side network requirements
A 10 Gbit/s link is highly recommended between the different process servers and the database server hosting the Sage X3 folders data.
For other components, a Gigabit link is recommended but it can work with lower bandwidth and higher latency.
When Sage X3 server components are installed on a Windows platform, it is highly recommended that there are members of an Active Directory (AD) Domain and belong to the same AD Branch. However, Syracuse web presentation servers can be hosted in DMZ-type sub-networks.
The different servers must also be properly registered in their domain’s DNS, allowing all server involved in a given Sage X3 environment to mutually resolve other servers’ fully qualified domain name (FQDN) in standard and reverse mode.
The servers on which Sage components are installed should not be used as an Active Directory Domain Controller (DC).
Client-side network requirements
| Sage X3 connection method | Front-end server | Bandwidth without printing, requesting BI, or downloading/uploading large documents |
|---|---|---|
| Web browser on user workstation | Syracuse web server (Sage) |
60 Kbit/s per session:
|
| Web browser on remote desktop via RDP protocol | Remote desktop service (Microsoft) | 24 Kbit/s per session |
| Web browser on remote desktop via ICA protocol | XenApp server (Citrix) | 12 Kbit/s per session |
| ADC client (typically hand-held RF terminal) | ADC server (Sage) | 20 Kbit/s per device |
Antivirus
When you install an antivirus protection on Sage X3 servers, Sage highly recommends disabling real-time protection on some parts of the application/main process server and additional process servers for best performance. Perform scheduled scans on real-time scanning excluded areas overnight when there are few or no users logged on.
Exclude the following directories from real-time protection if active:
- The <X3root>\folders directory on the application server(s) and all its subdirectories (objects, temp files, trace files, and so on).
- The <X3root>\runtime directory and its subdirectories (runtime engine, temp files, trace files) on all process servers (including the main one).
- Disable antivirus real-time protection on some parts of the Sage X3 installation to avoid performance issues.
- Run antivirus scans overnight on excluded areas.
- Perform a full backup before applying Windows updates.
- Test Windows Updates in a preproduction environment.