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 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
Network and bandwidth requirements
Network requirements
- A Gigabit (or better, 10 Gbit/s) link is necessary among the different process servers and the database server hosting the Sage X3 folders’ data. For other X3 components, a Gigabit link is recommended but it can work with lower bandwidth and higher latency.
- When X3 server components are installed on a Windows platform, it is highly recommended that they 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 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).
Network bandwidth between front-end servers and workstations
| X3 connection method | Front-end server | Bandwidth without printing or BO requesting |
|---|---|---|
| Web browser on user workstation | Syracuse Web Server (Sage) | 60 Kbit/s per session 50 Kbit/s Web server > Browser 10 Kbit/s Browser > Web server |
| 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
If you install an antivirus protection on Sage X3 servers, Sage 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 (X3 objects, temp files, trace files, etc.);
- The <X3root>\runtime directory and its subdirectories (runtime engine, temp files, trace files) on all Process servers (including Main one).
Windows Updates
If you encounter a problem with Sage applications after a Microsoft Windows Update is applied, Sage will try to give you all the needed assistance to identify the problem and provide a solution as quickly as possible.
Important: Sage notes that it installs most of the global Windows patches on its own servers and qualification environments. However, Sage advises that a Windows Update that worked well on Sage’s environments is not guaranteed to work in all environments.
Tips and Tricks
- Disable antivirus real-time protection on some parts of 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 pre-production environment.
-
Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.
-
