If users are implementing Document Export or Batch Printing, Kofax recommends partitioning that functionality on a separate MarkView Express and Export Server instance.
Note Well: System Administrators must confirm that each instance of MarkView Export Server meets the minimum requirements per the Chapter 5, 'Middle Tier Requirements' in the 'Planning To Install the MarkView System' guide. A link to the MarkView 5.5 Planning Guide is provided below:
Note: For instructions on load balancing MarkView Express for end users, refer to the Answer for .
To partition the MarkView Document Export functionality from MarkView Express, you need to install and configure a separate Mark?View Express and Export Server instance. The steps below will install a new MarkView Express and Content Server instance for all end users, and will make the existing MarkView Express server the default for MarkView Document Export and batch printing.
This configuration requires updating relevant MarkView Preferences.
- Create another J2EE container instance, installing the Oracle Containers for J2EE (OC4J) Standalone distribution per Oracle's instructions.
- Create an output of your System Preferences - follow the Answer link below:
- Install the MarkView Express and Content Server Modules.
- Run the MarkView Application Server installer.
- Select Custom install type.
- Choose the 'Express and Export Server', and the '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.
- Shutdown the original Content Server instance by running stop-mvas-content.sh.
- Remove start-mvas-content.sh from the start-all.sh script in the original OC4J install.
- Set MVAS_EXPORT_BASE_URL to the original URL (for the original Export Server OC4J instance).
- If you have installed any patches, including the MarkView 5.10.x Patchsets, you will need to reapply the relevant updates (.ear file changes) to the Express and Content servers within your new OC4J home in order to keep your versions consistent.
- If you have modified the startup parameters for the Express and Content servers (e.g. start-mvas- content.sh or start-mvas-vue.sh), you should ensure those parameter changes are also applied to the other instances.
As with all major system changes, you should follow industry-standard best practices for enterprise software, as outlined in the Answer below: