The following are the system requirements to install and
run Currency Server.
Currency Server was designed to run on any Intel Pentium
(x86 or x64) and compatible system. The software is licensed
per CPU core (4 cores for the Standard Edition, or more if
upgraded, and unlimited cores for the Enterprise Edition).
Currency Server has been tested on systems running
Windows Server 2019, Windows Server 2016, Windows Server
2012 (R2), Windows Server 2008 (R2), Windows Server 2003,
Windows 10, Windows 8, Windows 7, Windows Vista and Windows
XP SP3. It works on both x64 and x86 systems, including "Web
Edition" server products.
Windows Installer (MSI)
Installation of Currency Server requires Windows
Installer (MSI) 2.0 or higher. This component is part of
newer versions of Windows, and is also available as a free
download from Microsoft.
For additional information on
MSI please refer to this support page on the Currency System
Installation of the optional Currency Server Web service
feature requires version 2.0 of the Microsoft .NET
Version 2.0 of the .NET Framework is also
required by the Export() function of the COM
Without version 2.0 of the .NET Framework, the
Web service feature cannot be installed, and the Export()
function, if used, will return an error.
The Windows Azure Storage saving functionality of the
Post-Update Action feature requires version 4.0 of
the Microsoft .NET Framework. Without version 4.0
of the .NET Framework, saving data to Windows Azure Storage
Internet Information Services (IIS)
Installation of the Currency Server Web service feature
(serving .NET and SOAP clients) requires that the Internet
Information Services (IIS) Windows component be installed
and running, and that ASP.NET be installed and enabled.
In an IIS 7 environment, the IIS 6 Metabase Compatibility
feature must be present on the system.
Currency Server supports standard HTTP, WinSock, SOCKS
and TIS FTP proxy servers, with or without authentication
(including Windows NT Challenge/Response). If running older
versions of Currency Server on Windows NT 4.0
the system may need to be upgraded by installing Internet
Explorer 4 or higher in order to support SOCKS proxies. On
Windows NT 4.0 the system may need to be upgraded by
installing Internet Explorer 5 or higher in order to support
Windows NT Challenge/Response authentication.
Terminal Services clients are specifically supported. The
Display on screen notification option causes messages to be
displayed to all Terminal Services users until the first
user acknowledges the notification.
Currency Server includes a built-in SMTP client to
directly send email notifications to an SMTP server. This
functionality is unrelated from Windows Messaging and does
not require special privileges or optional operating system
Currency Server also supports the Windows Messaging
Application Programming Interface (MAPI), which is part of
Windows Messaging. Windows 2000, Windows XP, Windows Server
2003 and higher do not include Windows Messaging. On these
systems, the Microsoft Mail PostOffice and Mail icons are
not listed in Control Panel. MAPI support can be added by
installing a client such as Microsoft Outlook in Corporate
or Workgroup mode. Windows Messaging for Windows 2000 may
also be available from Microsoft Product Support Services.
For additional information on the availability of Windows
Messaging for Windows 2000, Windows XP, Windows Server 2003
and higher please refer to the Microsoft Knowledge Base
(e.g. articles 254458 and 314491).
In order to use the Windows Messaging notification
options, the Currency Server service must be logged on as a
user having access to the desired Windows Messaging Profile
and belonging to the Administrators group on the computer.
By default, Currency Server is installed to log on as System
Account, which does not make available these messaging
features (SMTP notification functionality is however always
available). An option to configure the service to log on as
a different user is available during setup.
Protocols and Ports
Currency Server normally collects currency information
from the internet via HTTP over TCP port 80. Some data
source filters (e.g. Oanda FXP) support connections via
different protocols and ports. The data source filters refer
to the FX servers by host name, therefore requiring DNS
client functionality for name resolution (usually TCP and
UDP port 53 to and from port 53 and random port numbers
greater than 1023). It is possible to manually edit the data
source address or filter configuration to reference the
servers by IP address rather than by host name, so that the
software will run on systems with tighter security settings
(e.g. where only port 80 may be open), however in this case
it is strongly recommended to set up appropriate
Notification options in order to be able to promptly correct
any connection problems (e.g. a change of IP address).
For additional security-related information please refer
to this white paper.
Additional (non-Windows) platforms are supported through
interfaces, and by means of the Custom Action after Update
functionality, which makes it possible to write and upload
data files in any file format (XML, CSV, etc.) and to any
generated by Currency Server is compatible with version 1.2,
and as such works on major "version 4" browsers released
since 1997-1998, and newer versions, including the most
popular widget platforms.