Skip to main content
Kofax

MarkView for SAP Gateway - What diagnostic steps should I follow and what information should I gather when there is an issue with MarkView Gateway?

  1. Last updated
  2. Save as PDF

Summary 

5116

Applies To

  • ERP System: SAP
  • MarkView Versions: All MarkView for SAP versions

Overview

MarkView does not have direct access to SAP backend tables. As such, MarkView uses BAPIs (Business APIs) to expose the ERP data it needs to retrieve from SAP. All communication from MarkView to SAP is handled through our BAPIs which get created in the SAP environment during installation of MarkView. A Java middle tier component, the MarkView Gateway for SAP, facilitates all of the communication between MarkView and SAP.

Troubleshooting Steps

If you encounter an issue with the MarkView Gateway Component, please perform the following steps:

Verify the mvsap-gw is up

  • For OAS
    Log into Oracle Enterprise Manager and ensure that the "mvsap-gw" component is started in the OC4J Instance. This is designated by the green arrow pointing up in the Status column.
  • For WebLogic
    Log into WebLogic Administration console and ensure that the "mvsap-gw" component is started in the markview deployments. This is designated by the "Active" status in the Status column.

Review log files for errors

  • If Markview Gateway is not functioning correctly then you will want to review the log files for any error messages. See the "Logging" section below for logging information.

Logging

Enable Debug Logging

  • Set the MVERP_GATEWAY_LOGGING_LEVEL preference to DEBUG at the System level
  • For MarkView versions up to and including 8.0, restart the MarkView Gateway component mvsap-gw on the Application Server
  • For Markview versions 8.1 and higher, no restart is required although it may take a few minutes before the new logging level is established

Disable Debug Logging

  • Delete the preference row set at System level for the preference MVERP_GATEWAY_LOGGING_LEVEL
  • For MarkView versions up to and including 8.0, restart the MarkView Gateway component mvsap-gw on the Application Server
  • For Markview versions 8.1 and higher, no restart is required although it may take a few minutes before the new logging level is established

Log File Location   

  • File location: All MarkView Components - Log File Locations
  • File name: mvsap-gw.log

Impact of Debug Logging

  • The Gateway log file will grow to 5000KB and will keep 3 backup copies of the log file before automatically overwriting them. In this case the maximum hard drive space taken up by the Gateway is 15000KB. If the log file exceeds the maximum size it will automatically overwrite the oldest information
  • The Gateway log file does log a significant amount of data with debug logging enabled. Because of this the log files often rollover quickly in a Production environment. As such it is often best to reproduce issues in a non-production environment when Debug logging is needed on the MarkView Gateway.

Keywords: diag, info