One of the big challenges with working with Documentum is debugging code that is deployed to the Content Server’s Java Method Server (JMS). Deploying code updates to the JMS can be tedious because it the JMS is typically on a remote server for developers, and it usually takes a long time to restart when code changes are deployed. The Java Method Server is also shared by all repositories on the content server, so continuously restarting the server for debugging can impact other repositories. Logging for the JMS can also be tricky to configure, and log files can be difficult to locate.
This article will describe how to set up remote debugging in Eclipse for code that runs on the Documentum Java Method Server.