Susan Meade and Reuben Chapman (reuben.chapman@uk.ibm.

com)
November 4th, 2015

Presentation schedule to start at :

14.00 IST (Ireland, Britain, Portugal, North Africa)
15.00 CEST (Central Europe, Egypt, South Africa)
16.00 EEST (Eastern Europe, Russia, Middle East)
09.00 EST (East Coast US)
06.00 PST (West Coast US)

Daeja ViewONE Pro and Daeja ViewONE Virtual

and the Integration with FileNet ECM Systems

This session will be recorded and a replay will be available on IBM.COM sites and possibly social media sites such as YouTube. When speaking, do not state any confidential
information, your name, company name or any information that you do not want shared publicly in the replay. By speaking during this presentation, you assume liability for your
comments.
2015 IBM Corporation

Agenda
History
Daeja ViewONE Professional

Overview
High level architecture

Daeja ViewONE ViewONE Virtual

Overview
High level architecture

Customization
Moving from ViewONE Pro to ViewONE Virtual

Java applets and HTML5 technology

The interface
Core code adjustments
Supported HTML parameters and Java Script methodology
Sizing considerations

Daeja Viewer and FileNet Integration

Products
Overview
Integration with Workplace
Integration with Content Navigator

Troubleshooting

General
Java Console
Viewer debug parameters
Server side logging
Summary

Questions
2015 IBM Corporation

History

Daeja ViewONE has existed since 1999

First integrated into FileNet systems in 2001

Sold as a standalone product for integration into any ECM system

The FileNet integrations were main area of business for Daeja Image Systems

Acquired by IBM in 2013

2015 IBM Corporation

Daeja ViewONE Professional

Overview

Takes the form of a simple client side applet requires only a supported browser and Java plug-in to run.

Gets installed on client PC via the Java plug-in, no client-side installation required.

Viewer version is determined by the set of viewer files installed on the server and feature differential is
controlled by a configuration file (lic.v1) generated by the installer.
Installation files are hosted as flat files on a web server (e.g. IIS) or web application server (e.g.
WebSphere).
The <applet> tag on hosting HTML pages points to the hosted install files and the Java plug-in enabled
browser downloads and runs the code.
Content is delivered to client side viewer and all processing work takes place on the client machine and is
then cached in viewer's local working area.

2015 IBM Corporation

Daeja ViewONE Professional

High level architecture

2015 IBM Corporation

Daeja ViewONE Virtual

Overview

Takes the form of a Java servlet rendition engine requires only an HTML5 enabled browser to run.

Gets injected as browser based viewer by JavaScript injection, no client-side installation required.

Viewer version is determined by the Java servlet deployed on the server and feature differential is controlled
by a configuration file (lic-server.v1) generated by the installer.
Installation files are hosted as a Java servlet on a supported web application server (e.g. WebSphere)
The <object> tag on hosting HTML pages points to the deployed java servlet and the HTML5 enabled
browser downloads and runs the code.
Content is processed, rendered and cached on the server and delivered as png tiles to client side browser.

2015 IBM Corporation

Daeja ViewONE Virtual

High level architecture

2015 IBM Corporation

Customization
HTML configuration options allow flexibility without needing to write code:

Enable\Disable functionality

Customize UI layout

Custom annotations

JavaScript API for complete flexibility

Respond to user input

Add custom buttons for custom functionality

Event handling

2015 IBM Corporation

Moving From ViewONE Pro to ViewONE Virtual

Java Applets and HTML5 Technology

Google Chrome has now removed support for NPAPI plug-ins (since September
2015).

Mozilla FireFox is removing support for NPAPI plug-ins by end of 2016.

Microsoft Edge (new browser) will not support NPAPI plug-ins.

Applets are effectively being deprecated.

ViewONE Virtual is best fit for Cloud and Mobile based technology.

2015 IBM Corporation

Moving From ViewONE Pro to ViewONE Virtual

The interface

ViewOne Professional

ViewONE Virtual

2015 IBM Corporation

Moving From ViewONE Pro to ViewONE Virtual

Core code adjustments

ViewONE Virtual

ViewOne Professional

2015 IBM Corporation

Moving From ViewONE Pro to ViewONE Virtual

Supported HTML parameters and JavaScript methodology

Check documentation here:
http://www-01.ibm.com/support/knowledgecenter/SSTPHR_4.1.4/com.ibm.viewone.configuring/dvoco000.htm

Supported in ViewONE Virtual

Not supported in ViewONE Virtual

2015 IBM Corporation

Moving From ViewONE Pro to ViewONE Virtual

Sizing Considerations

With most of the work now being done on the web application server, system sizing becomes much more critical.

It is a how long is a piece of string type question there is no concrete answer and UAT testing is essential.

But there is a tool available to assist; ICCP 4.50.11; which supports Daeja ViewONE Virtual 4.1.4:
http://w3-03.ibm.com/software/spcn/content/C993034C32553R66.html
(Note: this is planned to be updated for 4.1.5 before end of 2015)

2015 IBM Corporation

Daeja Viewer and FileNet Integration

Products
Embedded in FileNet systems since 2001:
ViewONE Standard Embedded in:
FileNet Image Services (Open Client and ISRA)
FileNet Workplace (P8, XT)
ViewONE Pro embedded in:
IBM Production Imaging Edition
IBM Content Navigator
ViewONE Virtual embedded in:
IBM Content Navigator (therefore embedded in other FileNet systems which use Navigator)
Integrated to fit with the existing FileNet ECM system using FileNet server side components to handle
documents and annotation data
The integration is effectively enabled with parameters:
Filenet=true
FileNet system=0 (Image Services)
FileNet system=1 (Workplace)
FileNet system=3 (PIE)
FileNet system=4 (ICN)
2015 IBM Corporation

Daeja Viewer and FileNet Integration

Overview

Server side code that interfaces between document repository and viewer.
Server side components that handle saving and loading of annotation data.
Additional components included that handle FileNet annotation security.
Custom buttons and bespoke HTML parameters for each individual FileNet system.
Main difference between a FileNet integrated viewer and a non-FileNet viewer is annotation data handling:

2015 IBM Corporation

Daeja Viewer and FileNet Integration

Integration with Workplace

Viewer files are stored in \FNJavaV1Files folder

Code integration is contained in a single file WcmJavaViewer.jsp.

Code that determines which file formats are rendered in the viewer is content_redir.properties.

(show)

Note that the formal integration of ViewONE Pro is only available with use of Production Imaging Edition or Content
Navigator but many IBM customers have switched to using ViewONE Pro themselves by purchasing ViewONE Pro
directly from Daeja Image Systems (prior to acquisition) and using a Workplace\Pro\Streamer integration guide.

2015 IBM Corporation

Daeja Viewer and FileNet Integration

Integration with IBM Content Navigator

Up until version 2.0.2, parameters were enabled using a flat binary file.

Since version 2.0.3, all parameters and server side properties can be added via the interface.

Since version 2.0.3 both ViewONE Pro Applet and ViewONE Virtual are fully integrated.

All modules are now included free of charge, except Office module and Redaction module, which are available as chargeable
add-ons.
(Demonstration)

2015 IBM Corporation

Troubleshooting
General

Typical Must Gather applies screenshots, scope of the problem, what changed, etc.

For Pro applet, Java console log is primary source of logging.

For Virtual and Pro server components, logging to a named file (or <stnd out>) is primary source of logging.

On-line demos at http://daejaviewonedemo.demos.ibm.com/ is a very useful cross-check tool.

Always gather <shift> and <t> detail this provides version and module details, breakdown of processed HTML parameters
and debugging options.

2015 IBM Corporation

Troubleshooting

Java Console
Enabled via the Advanced options under control panel, Java plug-in:

Turn on all logging options and show console ->

Full Java logging can be enabled by pressing 5 in the console itself.

There are further shortcut keys in the console itself (for example m for current memory consumption) but these should only
be used when directed by IBM engineering.
In the event of the console not being available, files are stored under the Java deployment cache area:
C:\Users\IBM_ADMIN\AppData\LocalLow\Sun\Java\Deployment\log

2015 IBM Corporation

Troubleshooting

Viewer debugging parameters

Trace parameters can be added to code that runs up the viewer, for example:
<param name=traceNet value=true>
or
writeParam('traceNet', 'true');
Can also be added dynamically from within the viewer itself press <shift> and <t> and then tick the relevant options:

2015 IBM Corporation

Troubleshooting

Server side logging

Same trace parameters are used for both Virtual and Applet
Parameters are added to a properties file that controls the servlet
tracenet=true
logfile=c:\logs\streamer

Can also be directed to <std out> but known file is recommended

2015 IBM Corporation

Troubleshooting

Summary
Always Required:

Scope of the problem what changed, how many users affected, etc.

Screenshot(s) showing problem.

All detail from <shift> <t> screenshot .

Java console output and\or server log file with relevant logging enabled
(note: traceNet and traceException are useful defaults for initial logging).
Possibly Required:

All detail from Image Properties screenshot.

Replicated in on-line demo?

Server side http logs.

Additional logging as specified by L2\L3.

2015 IBM Corporation

Questions

2015 IBM Corporation

Contact details

Reuben Chapman: reuben.chapman@uk.ibm.com

Do not hesitate to send me your comments or any further questions.

Any suggestions for further presentations would be welcome.

2015 IBM Corporation

Legal

THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION
CONTAINED IN THIS PRESENTATION, IT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBMS CURRENT PLANS AND STRATEGY, WHICH ARE
SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING
OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION,
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO NOR SHALL HAVE THE EFFECT OF CREATING ANY
WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS
AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCT OR SOFTWARE.
Copyright and Trademark Information
IBM, The IBM Logo and IBM.COM are trademarks of International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks and others are available on the web under Copyright and Trademark Information located at
www.ibm.com/legal/copytrade.shtml.

2015 IBM Corporation