ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

What Enhancements and Changes are in CA Output Management Web Viewer r12.1 INC00


Article ID: 17967


Updated On:


Output Management Document Viewer Output Management Web Viewer



This is a summary of Enhancements and Changes in Web Viewer r12.1 INC00. NOTE: INC00 is also referred to as Increment 3.


Enhancements and Changes in CA Output Management Web Viewer r12.1 INC00

Separate Installation, Configuration and Deployment

With CA OM Web Viewer r12.1 product configuration is no longer part of the installation. This change lets you perform product installation, product configuration and web server deployment separately and on different machines if needed.

External Configuration Settings

There are now 3 different options for Configuring Web Viewer

  • External, System Level Configuration (Recommended)
    Configuration files are stored in a folder external to the WAR or EAR deployed application, and the location is set by an environment variable.

Chose this option if you want to
  • Configure Web Viewer without re-deploying the WAR or EAR file and/or
  • Update and deploy or undeploy the WAR or EAR files without having to maintain the configuration files.

  • External, Application Level Configuration

Configuration files are stored in a folder external to the WAR or EAR deployed application and are referenced through a setting inside the WAR or EAR deployed application.

Chose this option if you want to deploy multiple instances of Web Viewer to a single web application server.

This allows you to reconfigure Web Viewer without the need to re-deploy the WAR or EAR file unless you also change the location of the configuration folder.

  • Internal, Application Level Configuration

This is the original configuration method introduced in r12 with the configuration files stored in either the WAR or EAR file or with the deployed application.

External Security Exits
Web Viewer r12.1 now includes support for external security exits. There are points in the application where customer-coded Java programming interfaces are called. These exit points allow for full integration of Web Viewer with your existing Single-Sign-On (SSO) or Security Federation systems. A sample Java EXIT is included with the install. You must write your own customized EXIT.

For information about configuring Web Viewer to use your external security EXIT, see the Installation Guide. For information about how to create your EXIT, see the Programmer Guide.

ActiveX Requirement Removed

CA OM Web Viewer r12.1 no longer uses browser add-ons (ActiveX or Plug-in) to perform printing and emailing. These add-ons have been removed due to many restrictions placed on browser add-ons. Web browsers and or computer settings often prevent installation of the add-ons.

New Certifications
Web Viewer is certified for releases 9, 10, and 11 of Internet Explorer, Windows 2012 R2 and Microsoft® SQL Server® 2012.

NOTE: IE8 is still supported.

Simplified Packaging

CA OM Web Viewer r12.1 simplifies the installation to one package with two installation sets, one for Windows (64-bit), and one set for all other supported operating systems.

Simplified Installation

CA OM Web Viewer r12.1 now includes a simpler installer that supports two installation types: Minimal and Full. The Minimal option installs either a WAR or EAR file for deployment Apache Tomcat or IBM WebSphere. The Full option installs Apache Tomcat 7 with CA OM Web Viewer pre-deployed. Installing JRE is now a prerequisite of the product installation.


Release: OUTDRA00200-11.5-Output Management-Distributed Repository Access-System