Skip to main content

Markview Filenet Integration - What diagnostic steps should I follow and what information should I gather when there is an issue related to Markview Filenet Integration

Article # 304240 - Page views: 108



Applies To

  • ERP System: SAP, Oracle
  • MarkView Version: and Greater


  • FileNet Content Manager provides document management and a ready-to-use workflow that helps to capture, manage and share content. Communication between FileNet Content Engine and MarkView is established by means of the MarkView Document Transport Module (DTM), a part of the MarkView Document Server, via HTTP Web Services to the Content Engine. FileNet Web Services return FileNet objects which can be used to process documents.

Troubleshooting Steps

Troubleshooting the Markview Connection to FileNet

  • If the Connection between FileNet is not working, check the following preferences for the correct values. Also check to ensure that there are not extra white spaces in any of these values.
    1. MVAS_DTM_FILENET_URL_TRANSPORT - This preference contains the url for FileNet integration. It should be set as follows:
      http://: /wsi/FNCEWS40DIME (5.0 or earlier)
      http://: /wsi/FNCEWS40MTOM (5.1 or later)
    2. MVAS_DTM_FILENET_FOLDERS - This preference should contain a single name or a comma-separated list of folders used by FileNet.
  • If the preferences are correct please check that all steps in Chapter 3 - Integrating with FileNet Content Manager from the document KofaxMarkViewIntegrationGuideforContentManagementSystems_EN have been completed.
  • If all steps have been completed and the preferences are correct, enable debug logging per the steps in the logging section and review the log for errors.

Troubleshooting Items and PO Number properties are not populated in FileNet metadata

  • This will happen if Distribution lines are not created at the time of metadata synchronization. In this case the properties will be updated when invoice gets to Pending Payment queue


Enable Filenet Logging

  • The preference controlling the logging level for FileNet is CMSYNC_LOGGING_LEVEL. This is a system level preference. Along with enabling FileNet logging, when troubleshooting FileNet issues the Document Transport Module (DTM) logging should also be enabled as FileNet works with the DTM. DTM logging is controlled by the system level preference MVAS_DTM_LOGGING_LEVEL. To enable FileNet and DTM logging, set the preference CMSYNC_LOGGING_LEVEL and MVAS_DTM_LOGGING_LEVEL preferences to "All" to log at the most granular level.

Disable PL/SQL Servlet Logging

  • FileNet and DTM logging can be disabled by setting the preferences CMSYNC_LOGGING_LEVEL and MVAS_DTM_LOGGING_LEVEL to Off.

Log File name and Location

  • When FileNet logging is enabled it creates (or appends to) the file cmsync.log.
  • When DTM logging is enabled it creates (or appends to) the file mvdtm.log
  • The FileNet and DTM log file can be found in a MarkView log location which is dependent upon MarkView release and middle tier type. Please see the following article for the location:

Keywords: filenet

  • Was this article helpful?