• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

Debugging Documentum Java Method Server (JMS) Code in Eclipse

You are here: Home / Documentum / Content Server / Debugging Documentum Java Method Server (JMS) Code in Eclipse

March 20, 2012

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.

The ability to remotely debug code using an integrated development environment (IDE), such as Eclipse, is an extremely useful tool to developers because it allow them to step through the code as it’s executing.  Because the Documentum Java Method Server is actually just a Java servlet container behind the scenes, remote debugging with an IDE can be configured just like any other servlet container.

Starting with Content Server version 6.5, the Documentum Java Method Server uses a JBoss servlet container.  This article with give the steps for remotely debugging JMS code using the Eclipse IDE with a JBoss JMS, however, similar steps could be used to configure remote debugging in other IDEs and/or a Documentum 5.x (Tomcat) or Documentum 6.0 (WebLogic) JMS.

Enable Remote Debugging on the Java Method Server

NOTE: Remote debugging should only be enabled in development environments.

To enable remote debugging on the JBoss JMS, you have to modify the JBoss start script.

Windows

Typically the JMS runs on the Documentum Content Server, and the start script can be found at %DOCUMENTUM%jboss4.x.xserverstartMethodServer.cmd in a Windows environment.  Modify the startMethodServer.cmd script, adding the following at the beginning of the script.

set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n %JAVA_OPTS%

Unix/Linux

Typically the JMS runs on the Documentum Content Server and the start script can be found at $DOCUMENTUM/share/jboss4.x.x/server/startMethodServer.sh in a Unix or Linux environment.  Modify the startMethodServer.sh script, adding the following line at the beginning of the script.

JAVA_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n $JAVA_OPTS"

After modifying the start script, restart the JMS.

Configure Remote Debugging in Eclipse

Assuming that the code that is running on the Java Method Server already exists in an Eclipse project, follow these steps to begin debugging JMS code in Eclipse.

  1. In Eclipse, click Run > Debug Configurations.
  2. In the left panel, select Remote Java Application.
  3. Click the icon in the upper left corner to create a new launch configuration.
  4. Provide a Name for the debugging configuration.
  5. Select the eclipse Project that contains the JMS code that you wish to debug.
  6. Select Standard (Socket Attach) as the Connection Type.
  7. Specify the Host and Port in the Connection Properties section.  The host will be the server name or IP address of the server where your JMS is running (typically the Documentum Content Server).  The port is the address that you specified when you edited the JMS start script in the previous step (default 8000).
  8. Click the Apply button to save the changes.
  9. Click the Debug button to begin debugging.

After debugging has started, you can add breakpoints to your JMS code in Eclipse, and the execution of the code will stop when the breakpoints are hit, allowing you to step through your code, view variables, etc. as your code is executing.  Refer to the Eclipse help documentation for more information on using the debugging features of Eclipse.

Filed Under: Content Server, D6.5, D6.7, Documentum, Tech Tip

Reader Interactions

Comments

  1. Ammar Khalid says

    March 21, 2012 at 3:33 am

    Thanks a lot for always sharing knowledge. Really appreciate your input into all the good work in the ECM domain and documentum.

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • Documentum Upgrades – Handling eSignatures in Documentum 6.6+
  • Documentum Upgrade to 6.7 – a simple approach
  • Documentum 6.5 to 6.7 Upgrade Lessons Learned
  • Documentum 6.7 Upgrades and Hardware Changes
  • Documentum – Upgrading to Documentum 7 in Three Weeks
  • Supersized Documentum Migrations and Upgrades Two Billion Documents and Counting
  • Documentum, Mobile and IMAP – A standard and open source approach for email archiving and mobile access
  • EMC World 2012 – May 23rd – What’s Next? ECM Documentum Family Roadmap – Aaron Aubrecht
  • Documentum Webtop 5.3 running on Documentum Content Server 6.x
  • Documentum , Weblogic and DM_DFC_E_BAD_CLASS error

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT