The Documentum 5 PLATFORM INTRODUCED the Java method server as a means of improving the performance and scalability of the Documentum method architecture.

The method server runs as a PROCESS distinct from the Content Server and is responsible for the invocation of the individual methods. Each method invocation results in a call to the method server which manages the actual execution of the Java-based method IMPLEMENTATION. As the method server is a continuously running process, there is no overhead INVOLVED in loading and tearing-down a Java virtual machine with each invocation. This yields an enormous benefit in overhead.

The Documentum 5 platform introduced the Java method server as a means of improving the performance and scalability of the Documentum method architecture.

The method server runs as a process distinct from the Content Server and is responsible for the invocation of the individual methods. Each method invocation results in a call to the method server which manages the actual execution of the Java-based method implementation. As the method server is a continuously running process, there is no overhead involved in loading and tearing-down a Java virtual machine with each invocation. This yields an enormous benefit in overhead.