{"id":8733,"date":"2016-11-02T06:00:50","date_gmt":"2016-11-02T05:00:50","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/"},"modified":"2016-11-02T06:00:50","modified_gmt":"2016-11-02T05:00:50","slug":"documentum-story-documentum-jms-log-configuration","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/","title":{"rendered":"Documentum story &#8211; Documentum JMS Log Configuration"},"content":{"rendered":"<p>The aim of this blog is to provide you a way to configure the JMS Logs in order to align all applications logging with date information, log rotation and retention. Some changes have to be done on the jboss container as well as on the log4j utility for each deployed JMS applications (acs.ear, serverapps.ear and bpm.ear).<\/p>\n<h3>General configuration<\/h3>\n<p>First, go to the JMS configuration at $DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/configuration\/<br \/>\nThe jboss version may vary depending on your Content Server version.<br \/>\nDo a backup of the standalone file like follow:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">cp standalone.xml standalone.xml_$(date +%Y%m%d).log<\/pre>\n<p>Then edit the file standalone.xml by replacing each pattern-formatter with the following configuration:<\/p>\n<pre class=\"brush: xml; gutter: true; first-line: 1\">&lt;pattern-formatter pattern=\"%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %s%E%n\"\/&gt;<\/pre>\n<p>Note that you can change this setting which will change the way the log file will look like, but try to be consistent with other environments and components.<br \/>\nNow go to application deployments: $DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/deployments<br \/>\nOnce again, depending your Content Server version you could have to go into deploy instead of deployments.<\/p>\n<h3>For ServerApps.ear<\/h3>\n<p>Backup the current log4j.properties file:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">cp .\/ServerApps.ear\/APP-INF\/classes\/log4j.properties .\/ServerApps.ear\/APP-INF\/classes\/log4j.properties_$(date +%Y%m%d).log<\/pre>\n<p>Then edit .\/ServerApps.ear\/APP-INF\/classes\/log4j.properties and set it like this:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">log4j.rootCategory=WARN, A1, F1\n log4j.category.MUTE=OFF\n log4j.additivity.tracing=false\n log4j.category.tracing=DEBUG, FILE_TRACE\n#------------------- CONSOLE --------------------------\n log4j.appender.A1=org.apache.log4j.ConsoleAppender\n log4j.appender.A1.threshold=ERROR\n log4j.appender.A1.layout=org.apache.log4j.PatternLayout\n log4j.appender.A1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE --------------------------\n log4j.appender.F1=org.apache.log4j.RollingFileAppender\n log4j.appender.F1.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/ServerApps.log\n log4j.appender.F1.MaxFileSize=10MB\n log4j.appender.F1.layout=org.apache.log4j.PatternLayout\n log4j.appender.F1.MaxBackupIndex=10\n log4j.appender.F1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- ACS --------------------------\n log4j.category.acs=WARN, ACS_LOG\n log4j.appender.ACS_LOG=org.apache.log4j.RollingFileAppender\n log4j.appender.ACS_LOG.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/AcsServer.log\n log4j.appender.ACS_LOG.MaxFileSize=100KB\n log4j.appender.ACS_LOG.layout=org.apache.log4j.PatternLayout\n log4j.appender.ACS_LOG.MaxBackupIndex=10\n log4j.appender.ACS_LOG.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE_TRACE --------------------------\n log4j.appender.FILE_TRACE=org.apache.log4j.RollingFileAppender\n log4j.appender.FILE_TRACE.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/ServerApps_trace.log\n log4j.appender.FILE_TRACE.MaxFileSize=100MB\n log4j.appender.FILE_TRACE.layout=org.apache.log4j.PatternLayout\n log4j.appender.FILE_TRACE.MaxBackupIndex=10\n log4j.appender.FILE_TRACE.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n<\/pre>\n<p>We changed the conversion pattern in order to add more info when logging. For example, here we added &#8220;z&#8221; in order to show the TimeZone. With such configuration it is easier to compare several logs which can be generated from different servers in different time zones.<\/p>\n<p>We also added the MaxFileSize and MaxBackupIndex in order to manage the retention. In the code above the logs will be generated in maximum 10 files of 100MB, hence it will never exceed 1GB on the file system. The drawback is that if you have a lot of logs generated it will grow fast and the older files will be replaced by the new ones.<\/p>\n<h3>For acs.log<\/h3>\n<p>You can do the same as before, first backup the configuration file:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">cp .\/acs.ear\/lib\/configs.jar\/log4j.properties .\/acs.ear\/lib\/configs.jar\/log4j.properties_$(date +%Y%m%d).log<\/pre>\n<p>Then edit .\/acs.ear\/lib\/configs.jar\/log4j.properties and set it like this:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">log4j.rootCategory=WARN, A1, F1\n log4j.category.MUTE=OFF\n log4j.additivity.tracing=false\n log4j.category.tracing=DEBUG, FILE_TRACE\n#------------------- CONSOLE --------------------------\n log4j.appender.A1=org.apache.log4j.ConsoleAppender\n log4j.appender.A1.threshold=ERROR\n log4j.appender.A1.layout=org.apache.log4j.PatternLayout\n log4j.appender.A1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE --------------------------\n log4j.appender.F1=org.apache.log4j.RollingFileAppender\n log4j.appender.F1.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/acs.log\n log4j.appender.F1.MaxFileSize=10MB\n log4j.appender.F1.layout=org.apache.log4j.PatternLayout\n log4j.appender.F1.MaxBackupIndex=10\n log4j.appender.F1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- ACS --------------------------\n log4j.category.acs=WARN, ACS_LOG\n log4j.appender.ACS_LOG=org.apache.log4j.RollingFileAppender\n log4j.appender.ACS_LOG.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/AcsServer.log\n log4j.appender.ACS_LOG.MaxFileSize=100KB\n log4j.appender.ACS_LOG.layout=org.apache.log4j.PatternLayout\n log4j.appender.ACS_LOG.MaxBackupIndex=10\n log4j.appender.ACS_LOG.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE_TRACE --------------------------\n log4j.appender.FILE_TRACE=org.apache.log4j.RollingFileAppender\n log4j.appender.FILE_TRACE.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/acs_trace.log\n log4j.appender.FILE_TRACE.MaxFileSize=100MB\n log4j.appender.FILE_TRACE.layout=org.apache.log4j.PatternLayout\n log4j.appender.FILE_TRACE.MaxBackupIndex=10\n log4j.appender.FILE_TRACE.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#-------------------- ATMOS LOGGING ---------------------\n log4j.logger.com.documentum.content.store.plugin.atmos=DEBUG,ACS_LOG\n log4j.logger.com.emc.esu=WARN,ACS_LOG<\/pre>\n<p>&nbsp;<\/p>\n<h3>For bpm.ear<\/h3>\n<p>You can do the same as before, first backup the configuration file:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">cp .\/bpm.ear\/APP-INF\/classes\/log4j.properties .\/bpm.ear\/APP-INF\/classes\/log4j.properties_$(date +%Y%m%d).log<\/pre>\n<p>Then edit .\/bpm.ear\/APP-INF\/classes\/log4j.properties and set it like this:<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1\">log4j.rootCategory=WARN, A1, F1\n log4j.category.MUTE=OFF\n log4j.additivity.tracing=false\n log4j.category.tracing=DEBUG, FILE_TRACE\n#------------------- CONSOLE --------------------------\n log4j.appender.A1=org.apache.log4j.ConsoleAppender\n log4j.appender.A1.threshold=ERROR\n log4j.appender.A1.layout=org.apache.log4j.PatternLayout\n log4j.appender.A1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE --------------------------\n log4j.appender.F1=org.apache.log4j.RollingFileAppender\n log4j.appender.F1.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/bpm.log\n log4j.appender.F1.MaxFileSize=10MB\n log4j.appender.F1.layout=org.apache.log4j.PatternLayout\n log4j.appender.F1.MaxBackupIndex=10\n log4j.appender.F1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- BPM --------------------------\n log4j.logger.com.documentum.bpm=WARN, bpmappender\n log4j.logger.com.documentum.bps=WARN, bpmappender\n log4j.additivity.com.documentum.bpm=false\n log4j.additivity.com.documentum.bps=false\n log4j.appender.bpmappender=org.apache.log4j.RollingFileAppender\n log4j.appender.bpmappender.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/bpm-runtime.log\n log4j.appender.bpmappender.MaxFileSize=1MB\n log4j.appender.bpmappender.layout=org.apache.log4j.PatternLayout\n log4j.appender.bpmappender.MaxBackupIndex=10\n log4j.appender.bpmappender.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n\n#------------------- FILE_TRACE --------------------------\n log4j.appender.FILE_TRACE=org.apache.log4j.RollingFileAppender\n log4j.appender.FILE_TRACE.File=$DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs\/bpm_trace.log\n log4j.appender.FILE_TRACE.MaxFileSize=100MB\n log4j.appender.FILE_TRACE.layout=org.apache.log4j.PatternLayout\n log4j.appender.FILE_TRACE.MaxBackupIndex=10\n log4j.appender.FILE_TRACE.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS z} %-5p [%c] (%t) %m%n<\/pre>\n<p>&nbsp;<\/p>\n<p>When everything is setup you can restart the JMS and verify that all logs are properly written in $DOCUMENTUM_SHARED\/jboss7.1.1\/server\/DctmServer_MethodServer\/logs<\/p>\n<p>Now you have your JMS log system setup consistently.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The aim of this blog is to provide you a way to configure the JMS Logs in order to align all applications logging with date information, log rotation and retention. Some changes have to be done on the jboss container as well as on the log4j utility for each deployed JMS applications (acs.ear, serverapps.ear and&hellip;&nbsp;<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4135,4179],"tags":[475,901,902,903,890],"class_list":["post-8733","post","type-post","status-publish","format-standard","category-digitalization","category-documentum","tag-acs","tag-bpm","tag-configuration","tag-jms","tag-log"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.9) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum story - Documentum JMS Log Configuration - dbi services Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum story - Documentum JMS Log Configuration\" \/>\n<meta property=\"og:description\" content=\"The aim of this blog is to provide you a way to configure the JMS Logs in order to align all applications logging with date information, log rotation and retention. Some changes have to be done on the jboss container as well as on the log4j utility for each deployed JMS applications (acs.ear, serverapps.ear and&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2016-11-02T05:00:50+00:00\" \/>\n<meta name=\"author\" content=\"Middleware Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Middleware Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/\"},\"author\":{\"name\":\"Middleware Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8a0bfec3c3bd1f27d3d452eaa592bfb8\"},\"headline\":\"Documentum story &#8211; Documentum JMS Log Configuration\",\"datePublished\":\"2016-11-02T05:00:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/\"},\"wordCount\":403,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"keywords\":[\"ACS\",\"bpm\",\"configuration\",\"jms\",\"log\"],\"articleSection\":[\"Digitalization\",\"Documentum\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/\",\"name\":\"Documentum story - Documentum JMS Log Configuration - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2016-11-02T05:00:50+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-documentum-jms-log-configuration\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum story &#8211; Documentum JMS Log Configuration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8a0bfec3c3bd1f27d3d452eaa592bfb8\",\"name\":\"Middleware Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"caption\":\"Middleware Team\"},\"description\":\"Posts published under the Middleware Team account are collective contributions by the dbi services middleware and enterprise content management consultants. The practice covers ECM platforms such as OpenText Documentum, Alfresco, and M-Files, as well as application servers and integration technologies including WebLogic, JBoss, Tomcat, and the Elastic Stack, from architecture and deployment to operations under service level agreements.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/middleware-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum story - Documentum JMS Log Configuration - dbi services Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/","og_locale":"en_US","og_type":"article","og_title":"Documentum story - Documentum JMS Log Configuration","og_description":"The aim of this blog is to provide you a way to configure the JMS Logs in order to align all applications logging with date information, log rotation and retention. Some changes have to be done on the jboss container as well as on the log4j utility for each deployed JMS applications (acs.ear, serverapps.ear and&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2016-11-02T05:00:50+00:00","author":"Middleware Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Middleware Team","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/"},"author":{"name":"Middleware Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8a0bfec3c3bd1f27d3d452eaa592bfb8"},"headline":"Documentum story &#8211; Documentum JMS Log Configuration","datePublished":"2016-11-02T05:00:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/"},"wordCount":403,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"keywords":["ACS","bpm","configuration","jms","log"],"articleSection":["Digitalization","Documentum"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/","name":"Documentum story - Documentum JMS Log Configuration - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-11-02T05:00:50+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-documentum-jms-log-configuration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum story &#8211; Documentum JMS Log Configuration"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8a0bfec3c3bd1f27d3d452eaa592bfb8","name":"Middleware Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","caption":"Middleware Team"},"description":"Posts published under the Middleware Team account are collective contributions by the dbi services middleware and enterprise content management consultants. The practice covers ECM platforms such as OpenText Documentum, Alfresco, and M-Files, as well as application servers and integration technologies including WebLogic, JBoss, Tomcat, and the Elastic Stack, from architecture and deployment to operations under service level agreements.","url":"https:\/\/www.dbi-services.com\/blog\/author\/middleware-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8733","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8733"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8733\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8733"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8733"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8733"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}