Skip to main content

MarkView Viewer Express - What are the recommendations and best practices for load balancing the MarkView Express Viewer?



Applies To

  • ERP System: All
  • MarkView Version: 6.x


What are the recommendations and best practices for load balancing the MarkView Express Viewer?

Known Causes

Often customers may want to implement load balancing for MarkView Express. Depending on the number of users on the system, it may be necessary to have more than one MarkView Express server instance.

Note: If users are implementing Document Export or Batch Printing, Kofax recommends partitioning that functionality on a separate MarkView Express and Export Server instance.


  • Preparation and Planning
    • You should review your planned rollout of the MarkView System, and plan for peak number of concurrent users for MarkView Express. In general, system performance degrades and instability can occur when there are more than 20-30 concurrent requests for a MarkView
    • Express instance, but note that your peak may vary, depending on the types of operations taken, the latency in database operations, and the types of customizations in your solution. Note that each action in MarkView Express - each click-through, image zoom, etc. - will send a request to the Express Server.

Note Well: For load balanced MarkView Express Servers, System Administrators must confirm that each instance of MarkView Express meets the minimum requirements per the Installation Guide.

  • Hardware Load Balancing
    • System Administrators may wish to implement a solution using load balancing hardware. Such solutions are acceptable, and generally provide the full-feature of load-balancing, including failover and high-availability. You need only note that Express stores state across requests. Therefore, the load balancing hardware needs to be configured so that all requests for a given user will be routed to the same Application Server instance.
  • Application Load Balancing
    • You can also choose to leverage MarkView Group Preferences to implement load balancing at the Application Level.
  • To configure load balancing in this manner:
    1. Create another J2EE container instance, installing the Oracle Containers for J2EE (OC4J) Standalone distribution per Oracle's instructions.
    2. Create an output of your System Preferences - follow the Answer link below:
    3. Install the MarkView Express and Content Server Modules.
      1. Run the MarkView Application Server installer.
      2. Select Custom install type.
      3. Choose 'Express and Export Server' and 'Content Server'.

        Note: The installer will update the following MarkView preferences
        This change will mean that all of your Express users will be using the new Express OC4J for viewing images after you install.

    4. Set group preferences such that your users are load balanced across the old and new OC4J instances.
      1. Assign some users to the New instance:
        •  Select a user group (for example, AP Entry) and create a group level preference value for the following preferences with a value equal to one of the OC4J instances that you created. (You can review the preference output from Step 2 to see the original value of the preferences. 
      2. Assign some users to the Old instance
        • Take a different user group (for example, Invoice Approvers) and create a group level preference value for the same preferences in step 4(a) above. In the value for this preference, point to a different instance of OC4J than you specified in the previous step.
    5. If you require more than two Express OC4J Instances you can repeat the above steps as necessary, assigning different user groups to different OC4J instances.
  • Best Practices
    • As with all major system changes, you should follow industry-standard best practices for enterprise software, as outlined in the Adminstration Guide.

Keywords: load-balance