IFS Applications is built using standard tools and technologies. IFS supports most platforms, including Microsoft Windows, major UNIX® variants, and Linux®. Because each physical tier in the architecture is separated through standard protocols, it is possible to "mix and match" platforms in a deployment. IFS Applications can be deployed on anything from a single laptop running all components for demo purposes, to multi-server production installations with both database and application servers running in cluster configurations - supporting tens of thousands of concurrent users.
The two principal deployment components are the database and the J2EE application server.
Clients communicate through Http(s) to the web and application servers that in turn access the database instance through JDBC.
The database runs both the storage tier and the application core business logic objects. The J2EE application server called IFS Middleware Server runs the services layer business logic objects, the web/portal presentation tier, and integration services. Both the database and the application server can be run in clustered configurations for extreme reliability and scalability.
Clients access the business logic predominantly by using Http (or Https using SSL) protocol. This allows easy passage through firewalls, proxies, and other network infrastructure. Port numbers can be configured. Integrations and customer interfaces access the business logic through the same access providers as used by IFS Applications clients, and thus use the same protocols.
IFS' ongoing goal is to offer customers a choice of hardware, operating systems, application servers, or integration technology platforms on which to run IFS Applications. Instead of trying to lock customers into a particular technology stack, IFS works actively to enable customers to choose and change over time.
Whereas some enterprises predominantly use Windows platforms, others rely on UNIX or Linux. Consequently, IFS actively works to integrate IFS Applications into both Windows and UNIX/Linux environments. This includes the ability not only to run server-side components on either platform but also to provide plug-and-play support for important infrastructure on the respective platform. For example, IFS Applications can use either Microsoft Active Directory, or any LDAP directory for authentication. Add-on and integration development can be done using Java/J2EE, or .NET.
Similarly, IFS sees no need to choose between J2EE and .NET - companies can use both. Packaged applications in combination with continuously changing IT environments mean that most organizations will find themselves operating both J2EE and .NET-based applications. Interoperability between the two is both possible and available. IFS respects these facts, and although the server-tier of IFS Applications is implemented according to J2EE architecture, IFS Applications fits well into either environment. This is why IFS Applications supports J2EE technologies such as JSP, JMS, and EJB as well as .NET technologies such as ASP.NET, WinForms, WPF etc.