VE-based applications can easily be deployed on any J2EE server with the VE/Server libraries. Accordingly, the same VE application can be deployed in different configurations and on various platform stacks. For example, one can deploy a Human Resource (HR) application built with VE for a small department on a single instance of a Sun ONE server, running BEA's Java VM, on MS-Windows 2000 server running on an Intel box. And, you can take this same application and deploy it as an enterprise-wide HR system running on BEA WebLogic web server and application server cluster running on Sun's Java VM deployed on Sun Fire server farm with Sun Solaris.

Aside from the ability to choose what vendor implementation to use for each layer in the architecture stack, VE/Server can be deployed on top of a web server (e.g. Tomcat or BEA WebLogic Express) running as pure Servlet, or on a full J2EE implementation supporting both Servlets and EJBs (e.g. JBoss, IBM WebSphere Server or BEA WebLogic Server) while taking full advantage of the scalability, fault-tolerance, distributed transactions support, and security features offered by EJB containers. The very same VE applications can run in either deployment configuration without any change.

Running on strictly a web server (Servlet engine), the VE/Server executes VE applications immediately in the same Virtual Machine (VM). It uses the JNDI API to load the application logic from the object repository (e.g. file system, LDAP server), and the JDBC API to interact with the database of choice for storing and retrieving the application data. VE supports and has been tested against a variety of relational databases (RDBMS) including Oracle, DB2, MS-SQL, and PervasiveSQL.