Overview
The Trifork T4 Enterprise Application Server is a fully featured and J2EE compatible application server built to handle enterprise level demands. It provides high-speed Web, JSP, Web services, and EJB services, by keeping resource usage low and allows more users and transactions on the same physical hardware.

The amazingly low memory footprint of the Trifork T4 Application Server allows developers to easily run the application server, database and other development tools directly on the computer used for development.

The simple fact that both the installation and runtime sizes for Trifork T4 are significantly below the competition makes Trifork T4 an ideal candidate for embedding into other systems. Trifork T4 is particularly suited for repackaging and redistribution, as part of third party solutions and software providers’ offerings. One example is the installation procedure for Trifork T4, which can seamlessly integrate into third party product installations. Further, all management operations for Trifork T4 are accessible by programmable APIs through Java Management Extensions and other J2EE™ interfaces; thus the application that embeds Trifork T4 can control all aspects of the live server without the end-user ever knowing the application server is even there.

Features
Trifork T4 Application Server provides a complete solution for your application infrastructure; with a number of features increasing usability:

  • Servlet 2.4 and Java ServerPages 2.0
  • Enterprise JavaBeans™ 2.1
  • Java Message Service 1.0.1
  • JAX RPC 1.0, JAXR and SAAJ
  • Full support for SOAP 1.1, WSDL 1.1, and WS-I Basic Profile 1.0
  • Includes UDDI Registry
  • Basic authentication, Digest authentication and SSL/certificated based login.
  • CORBA interoperability with CSIv2 wire-level security.
  • JCA and LDAP integration.
  • Multi-operating system support Linux™, Solaris™, Windows™, AIX™, Mac OS X™ and others.
  • Pure Java implementation lets you leverage your existing hardware investment.
  • Extremely low memory foot print.
  • Web based server management and configuration.
  • Command line based server management and configuration.
  • Complete ANT integration.
  • Client management: Allows you to centrally manage and monitor thick clients.
  • Pluggable security realms.
  • Hot deployment: With the Trifork Server, Hot Deployment is the combination of several features. Combining mapped archives with system container auto restart and inplace deployment you obtain a very high degree of flexibility. Only your IDE defines your setup: Just let the Trifork T4 run in the background and keep on using your IDE’s normal structure. The moment you hit the save button in your IDE, the server grabs your code changes and automatically rereads everything reducing turn-around time to typically around 1 sec
  • Never restart the server! Applications, WARs, JARs, etc. are deployed to a live application server by simply storing it in the running server’s repository.
  • With in-place deployment, what is deployed is not an archive, but a reference to a directory. Whenever the server needs a file (for instance to serve a JSP file) it will be read out of the directory specified at “deployment time”. Simple changes to JSPs and static content, images and html documents can thus be updated on the fly. To have the application server re-load compiled classes, the system container that owns the application is simply restarted.
  • Mapped Archives: With the Trifork T4, your application (.ear/.jar/.war/.rar) may be described through an xml descriptor in place of the actual archive file/directory. This descriptor maps directories and files into one logical archive and becomes a deployable abstraction of an archive. Both absolute and relative file system paths may be used for identifying files and directories. You may even specify jar files recursively in the mapping descriptor, e.g., to describe a .war file nested inside an ear file.
  • Persistent web sessions: Continue a web session across redeployment or server restart.

More information: