Kofax MarkView 10.3.0 Fix Pack 5

Build date: January 31, 2024

© 2024 Tungsten Automation. All rights reserved.
Use is subject to license terms.

Introduction

Install Kofax MarkView 10.3.0.5 to resolve the issues listed below.

Note: Install Kofax MarkView 10.3.0.5 only after a full installation of Kofax MarkView 10.3.0 or on top of any previously installed 10.3.0 fix packs.

For a full product installation, see the Kofax MarkView Installation Guide for instructions.

Issues resolved in this fix pack

ID	Issue	Solution
2070605	AUSS sync did not work properly and produced the following error message: "ORA-02291: integrity constraint (MARKVIEW.MV_AUSS_SRC_GRP_MEM_USER_ID_FK) violated - parent key not found."	AUSS code changed to handle the root cause scenario where a user has the "External" person type in Oracle EBS.
2068346	Import Server returned an error while processing specific PDFs.	Upgraded the PDF library.
2067188	Request to upgrade the Log4j library.	The Log4j library was upgraded from version 1 to 2.
2039780	MarkView Import produced error messages, such as "Processing of existing file [file name] failed while trying to upload [file name]" and "Destination file [file name] already exists."	The maximum sequence value and file name length have been increased.
1941430	In MarkView -> Web Inquiry -> AP Invoices, a missing UPPER keyword in the mverp_wda_dflt_ext_pb package body resulted in missing search results.	Added UPPER to the query to make search case-insensitive.

List of issues resolved in previous fix packs

Fix Pack 4

1941368: On Alternate User Assignment page and Support Tools, when entering the lowercase User ID or User ID that does not exist in the system, a 500 error appeared

1936732: Export Requests (Print or Email) from Viewer failed using https with the following exception: Received fatal alert: handshake_failure javax.net.ssl.SSLHandshakeException

1959623: Impossible to email from the MarkView 10.3.0.3 Viewer

1963767: When doing a Get Next from the Oracle EBS Supplier page, the "Request Denied" message appeared

1971821: F5 Load balancer server request response returned incorrect data type in the Content-Type header causing missing menus

Fix Pack 3

1912398: Verification of incoming HTTP request and cookies attribute added to improve security

1908990: In mv_document table and other related MarkView tables, document_id values were too large for the column

1901515: When using the latest version of Google Chrome and Microsoft Edge, the Viewer did not always show Quick Info

1882180: Parameter checking added to improve security

1863724: Verify terminates showed the following error: "...by the JMX call does not have the right format. At least one dot is expected."

1857298: Impossible to send emails through the Viewer using OAuth

1842559: Web application security improved

1842558: SQL security improved

Fix Pack 2

1802415: Encountering an issue when coding an invoice with NON billable project coding

1775797: Need to convert the "mvap_ipa_pkg.RefreshPOTables" dbms job to Scheduler job

1775789: Errors When Approving An Invoice Via MarkView Mobile Link

1775787: Viewer Does Not Display All Layers of Certain PDF Files Ingested via Import Server

1734106: AUSS experiencing major performance issues with synchronization

1734090: After applying Oracle patch for Log4j vulnerability, MarkView is negatively impacting core Oracle functionality

1698724: 500 Internal Server error trying to update or create user record due to 'comor' being added to url in referrer

1679529: KTM Validation Blanket PO Corrected Quantity Not Reflected in Receipt Lines Field

Fix Pack 1

1713746: Mail Gateway: Outbound emails stopped processing when the recipient's address was invalid

1713745: Mail Gateway: Inbound emails stopped processing when the 'To' address was empty

1712543: Mail Gateway closed all windows after clicking OK on the Instance Preferences window

1712540: Mail Gateway created an extra connection for POP protocol that caused the test connection to fail

1712537: When MAPI protocol was selected for Outbound and Inbound services, the Username, Port and Timeout fields had to be disabled

1712534: With MAPI protocol selected, leaving the Port and Timeout fields empty, resulted in incorrect validation

1712531: With SMTP protocol selected, username validation failed for the Outbound service

1712530: With MAPI protocol selected, The 'Enable Authentication' function was unexpectedly available for Inbound and Outbound services

1712529: SMTP connection failed if an SSL port 465 was specified for the Outbound service

1712528: With SMTP, POP or IMAP protocol selected, the SSL connected successfully even with SSL disabled

1712524: With SMTP protocol selected, authentication failed for the Outbound service

1708162: When attempted to open Online Help from MarkView 10.3, the Online Help for MarkView 10.2 appeared instead

1697380: After setting the 'MVERP_DFM_DEFAULT_AMOUNT' preference to FALSE, new lines could have no longer been added in the viewer

Applies to

This fix pack is based on Kofax MarkView for Accounts Payable 10.3.0.
Only apply this fix pack to the MarkView 10.3.0 application server; do not run the fix pack installer on a MarkView Oracle Objects installation.

Verify that the version of all installed MarkView components (such as Self-Service Invoices, Document Library, Expenses) is 10.3.0.

For information about system requirements, see the Kofax MarkView 10.3.0 Planning Guide and the Technical Specifications document on the Kofax MarkView Product Documentation website.

Applying this fix pack multiple times on the same system causes no harm. Also, fix packs are cumulative for a release, so you do not need to install previous 10.3.0 fix packs before applying this latest fix pack.

This fix pack includes files that are staged on the application server and that require manual steps, which are included in the sections that follow.

Files included

This fix pack includes the following files:

File name	Version
KofaxMarkView-10.3.0.5.zip	10.3.0.5
ReadMe-KofaxMarkView-10.3.0.5.htm	N/A

Install this fix pack

Use the following procedures to install the fix pack.

MarkView Application Server installation (includes Database Components)

Only apply this fix pack to the MarkView 10.3.0 application server.

Before starting the following procedure, read this entire ReadMe file.

Silent installation preparation

If you used the silent installation method to install MarkView 10.3.0 and you plan to use the same method to install the fix pack, perform the following actions.

1. Go to the distribution > conf folder.

2. Open the preliminary_interview.properties file.

3. Complete the properties file information, but leave the SelectedProducts.selected_products parameter blank.

4. Run the generateInterviewTemplate script to create or update the installer_interview.properties file.

5. Open the installer_interview.properties file.

6. Complete the properties file information according to the Kofax MarkView 10.3.0 Upgrade Guide.

Apply the fix

1. Log in to the application server as the user who installed MarkView 10.3.0.
   Ensure that the environment variables required for installing MarkView 10.3.0 are defined.
   See the Kofax MarkView 10.3.0 Upgrade Guide for information about setting environment variables and other settings required to run the installer.

2. Locate the base MarkView directory where MarkView is installed. Use this path name when prompted for the "Install Directory" during installation.
   The base MarkView install directory includes the following files:

   • target_registry.properties
   • thirdparty.txt

3. Extract the KofaxMarkView-10.3.0.3.zip file into a new directory on the application server where MarkView 10.3.0 is installed.

4. Verify that the system is quiet to ensure that the data remains synchronized.

5. Log in to an SQL*Plus command window as the MarkView schema user.

6. Stop the currently running database user jobs by executing the breakDBJobs.sql script, which is included in the following MarkView 10.3.0 installation distribution directory:
   <MARKVIEW-10.3.0-INSTALLER>/modules/installer-dist-10.3.0/installer-db
   where <MARKVIEW-10.3.0-INSTALLER> is the base directory of the MarkView 10.3.0 installation distribution.

7. To run the installer, invoke the installation script in the bin directory of the fix pack distribution (install.bat|sh or install_silent.bat|sh).
   See the Kofax MarkView 10.3.0 Upgrade Guide for information on running the installer.
   The installer shows a list of all 10.3.0 fixes in the fix pack.

8. Provide answers to any unspecified values in the installer windows.
   Use values that match those provided during version 10.3.0 installation.
   (If available, use the installation worksheet that was completed for MarkView 10.3.0.)
   Note: Install the fix pack in the same target directory specified for the MarkView 10.3.0 installation.
   If you run the installer and see pre-populated information for the wrong environment, such as production URLs when running against a non-production environment, update the fields manually in the installation window.
   If you install this fix pack on WildFly, do one of the following:
   

   • For standalone mode:
     In the Enter App Server information for MarkView applications, leave the Domain field blank.

   • For domain mode:
     In the Enter App Server information for MarkView applications, enter your domain name in the Domain field.

9. When the installation is completed, follow any on-screen instructions that appear in the installation summary window.

10. Restart the application server.

11. To ensure that all database objects are compiled successfully, follow the instructions in the "Check for invalid packages" section of Chapter 5 of the Kofax MarkView 10.3.0 Upgrade Guide.

12. Log in to an SQL*Plus command window as the MarkView schema user.

13. Start database user jobs by executing the startDBJobs.sql script found in the following MarkView 10.3.0 installation distribution directory:
    <MARKVIEW-10.3.0-INSTALLER>/modules/installer-dist-10.3.0/installer-db
    where <MARKVIEW-10.3.0-INSTALLER> is the base directory of the MarkView 10.3.0 installation distribution.
    In a clustered environment, point to one server, then propagate to other nodes in the cluster using the appropriate process for your application server.

14. If you plan to install Import Server or you have Import Server 10.3, verify that you clear the Verify Upload option on the Import tab of the MarkView Import Server Preferences window.

Capture and Output components for MarkView 10.3.0

The following Capture and Output components for MarkView were updated as part of the 10.3.0 Fix Pack 1:

• The MarkView Mail Gateway was updated as part of the 10.3.0 Fix Pack 1.

To install or upgrade the MarkView Mail Gateway, run the msi file from:
<MARKVIEW-INSTALL-DIR>/misc/10.3.0/FIX16526/sfMailService.Installer.msi

Configure MarkView Mail Gateway on a machine with KTM installed.

MarkView post-installation steps (WildFly and FileNet only)

If you are installing this fix pack on a WebLogic Application Server, or if you do not use the FileNet server, skip this section.
If you are installing this fix pack on a WildFly Application Server and you use the FileNet server, perform the following post-installation steps:

1. Back up $JBOSS_HOME/standalone/configuration/standalone.xml.

2. Open $JBOSS_HOME/standalone/configuration/standalone.xml and locate the following tag:
   <subsystem xmlns="urn:jboss:domain:security:1.2">

3. Within <subsystem xmlns="urn:jboss:domain:security:1.2">, locate the <security-domains> tag and add the following strings:
   

   <security-domain name="FileNetP8WSI" cache-type="default">
    <authentication>
     <login-module code="com.filenet.api.util.WSILoginModule" flag="required"/>
    </authentication>
   </security-domain>

4. Save the file and restart the WildFly Application Server.

Oracle Forms Integration

Apply FIX18102

Starting from version 10.3.0.3, the fix pack contains FIX18102 for the folowing bug:
Bug 1908990: In mv_document table and other related MarkView tables, document_id values are too large for the column.

If you already applied this fix, skip the steps.

To apply FIX18102:

1. Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.

2. Copy the MVOAUTIL.pll file from:
   <MARKVIEW-INSTALL-DIR>/misc/10.3.0/FIX18102
   To:
   $c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

3. Back up the previous version of $c_MARKVIEW_TOP/MVOA/<version_number>/libraries/MVOAUTIL.plx.

4. Compile MVOAUTIL.pll into MVOAUTIL.plx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/<version_number>/libraries/MVOAUTIL.pll module_type=LIBRARY compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

5. Back up the previous version of $AU_TOP/resource/MVOAUTIL.plx.

6. Copy the MVOAUTIL.plx file from:
   $c_MARKVIEW_TOP/MVOA/<version_number>/libraries
   To:
   $AU_TOP/resource

Apply FIX16695

Starting from version 10.3.0.2 the fix pack contains FIX16695 for the following bug:
Bug 1734090: After applying Oracle patch for Log4j vulnerability, MarkView is negatively impacting core Oracle functionality
If you already applied this fix, skip the steps.

To apply FIX16695:

1. Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.

2. Change directory to <MARKVIEW-INSTALL-DIR>/misc/10.3.0/FIX16695:
   

   cd <MARKVIEW-INSTALL-DIR>/misc/10.3.0/FIX16695

   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

3. Extract files from mvoa_patch.zip archive into $JAVA_TOP directory:
   

   unzip -o -d $JAVA_TOP mvoa_patch.zip

4. Change directory to $JAVA_TOP:
   

   cd $JAVA_TOP

5. Remove log4j classes from $JAVA_TOP if they exist:
   

   rm -f log4j.jar log4j.properties
   rm -rf org/apache/log4j
   rmdir --ignore-fail-on-non-empty org/apache org

6. For Oracle EBS 12.2.x only:

   • Back up the previous version of $JAVA_TOP/customall.jar file.
   • Run adcgnjar utility to recreate and sign $JAVA_TOP/customall.jar file:
     

     adcgnjar

     (Enter APPS schema name and password when prompted.)

7. Restart the Oracle ERP system.

Issues resolved in previous fix packs

Issues Resolved in Fix Pack 4

Issues Resolved in Fix Pack 3

Issues Resolved in Fix Pack 1