Skip to main content
Kofax

MarkView Process Monitor - What diagnostic steps should I follow and what information should I gather when there is an issue with Process Monitor?

Summary

3983

Applies To

  • ERP System : Oracle, Peoplesoft, SAP
  • MarkView Version: All Versions

Behavior

  • The MarkView Process Monitor is a real-time management tool that monitors business processes. MarkView Process Monitor provides a graphical view of the current status of business processes, as well as spreadsheet views of the history and results of work performed to date.

Known Causes

n/a

Resolution

  • If you encounter an issue with the MarkView Process Monitor, please perform the following steps:

Troubleshooting Steps

Verify the OC4J is up

  • Verify that the MarkView Process Monitor has properly started, by starting a browser and navigating to a URL of the following form which should load Process Monitor.
    http://server:port/sfasmm/
    For customers running MarkView Version 5.10 or earlier http_port will be the http port of the Process Monitor OC4J (sfasmm) as specified in the Oracle Containers for J2EE (OC4J)_HOME\config-sfas- mm\http-web-site.xml file. (If you are running https in your environment you will need to check the secure-web-site.xml file) For MarkView Versions 6.0 and higher the http port will be the HTTP1 port listed in Oracle Enterprise Manager.
  • If Process Monitor is up when going to the URL directly but is failing when clicking on the link from MarkView Home you will need to check the menu item for the correct machine name and port information. This can be done by logging into MarkView Home and navigating to Administration -> Module Admin -> Menu Item. You can then find the menu item for Process Monitor and make sure that the port information is correct.

Review log files for errors

  • If Process Monitor 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.
    • For All MarkView versions
      • If the log file shows a java.lang.OutofMemoryError restart the OC4J and review the following Suppor Web Answer:
    • For MarkView versions 4.x to 5.10.x
      • If the errors point to a port issue you can check the http-web-site.xml, jms.xml, and rmi.xml files located in the Oracle Containers for J2EE (OC4J)_HOME\config-sfas-mm directory. By checking these port values and using the netstat command you can determine if any ports are being used by another application. (If you are running https in your environment you will need to check the secure-web-site.xml file)
      • If the errors point to a database connection issue you can check the Oracle Containers for J2EE (OC4J)_HOME\config-sfas-mm\data-sources.xml file. Using the connection information in the file you should be able to connect directly to the database using SQL*Plus.

Check pre-requisite software

To check the versions of pre-requisite software please review the following Support Web Answer:

Logging

Enable debug logging

  • For MarkView Version prior to 8.1
    • In Process Admin -->Preferences, set the MONITOR_WEB_LOGGING_LEVEL preference to a value of 3 to enable full debug logging.
    • Bounce the process monitor application.
  • For MarkView Versions 8.1 and above
    • Navigate to MarkView Administration -->Preferences
    • Select the PROCESS_MONITOR_LOGGING_LEVEL preference
    • Create a new system level preference with a value of "Debug"
Please note that with MarkView 8.1 and above the logging changes will take place automatically within a few minutes, there is no restart of the Application Server needed

 Disable debug logging

  • For MarkView Version prior to 8.1
    • In Process Admin -->Preferences, set the MONITOR_WEB_LOGGING_LEVEL preference to a value of 0 to disable debug logging.
    • Bounce the process monitor application.
  • For MarkView Versions 8.1 and above
    • Navigate to MarkView Administration -->Preferences
    • Select the PROCESS_MONITOR_LOGGING_LEVEL preference
    • Set the system level preference to a value of "warn"
Please note that with MarkView 8.1 and above the logging changes will take place automatically within a few minutes, there is no restart of the Application Server needed

 Log file names

Log file Locations:

File location: All MarkView Log Locations 

Impact of debug logging

  • Enabling full debug logging for Process Monitor will cause the log file to grow rapidly and is not recommended for Production environments under normal circumstances.

Keywords: troubleshoot SQL*Flow Monitor Web Edition, troubleshooting, problem, general, minimum, information,sqlflow