Technical Note. ApplicationXtender Web Access December 28, This technical note contains information on these topics:

Transcription

1 ApplicationXtender Web Access 5.30 Technical Note December 28, 2005 This technical note contains information on these topics: Introduction... 2 ApplicationXtender Web Access Benefits... 3 Understanding ApplicationXtender Web Access... 6 Security Licensing Using ApplicationXtender Web Access Hardware and Software Requirements

2 Introduction Introduction As business expands globally and, as a result, becomes more webcentric, it is clear that the Internet holds the key to effective enterprisewide information access and sharing. Implementing a localized content management system may no longer be adequate to serve your organization's growing needs. Fast, inexpensive, secure, and remote access to your organization's content becomes a necessity in today's business climate. Increasingly Internet-savvy workers are accustomed to "surfing" for the information they need and expect to retrieve it with just a few clicks of a mouse. Companies and employees in today's fast-paced business world do not have the time to be stalled by stationary servers that require direct dial-up access for information retrieval. The ability to open a browser, from any place at any time, and retrieve and exchange information is vitally important to productivity and overall corporate success. However, employers should not have to spend a lot of time, manpower, or money to create and configure company intranets or enterprise - only web sites. ApplicationXtender Web Access (AppXtender Web) addresses all of these needs. AppXtender Web is a component of the ApplicationXtender (AppXtender) content management suite. AppXtender Web works in conjunction with the other modules in the AppXtender system to allow access to AppXtender content via a standard web browser. AppXtender Web allows users to view and manage AppXtender content over intranets or the Internet. With AppXtender Web, users can use web browsers to retrieve, view, and manage content from AppXtender applications. This approach to content access creates an efficient and inexpensive content delivery solution for users both inside and outside your organization. AppXtender Web provides global access to your information wherever and whenever it is needed, allows you to securely share information with employees, customers, suppliers, and partners, and reduces the cost and labor associated with hard-copy distribution of content. This document takes an inside look at the features and functionality of AppXtender Web. The information contained in this document is intended to provide high-level information about the product, including system requirements, architecture, modules, and features. 2

3 ApplicationXtender Web Access Benefits ApplicationXtender Web Access Benefits Secure Access to Data AppXtender Web offers a comprehensive array of features and functions that can be used to efficiently and securely manage content within your business. AppXtender Web provides many layers of security, allowing you to control which users access what data, even down to the document level. You can deploy your AppXtender system with confidence, knowing that your data is secure. Leveraging AppXtender Security AppXtender system administrators can set user profile settings to control access to applications and application functionality in both AppXtender Document Manager and Web. Document level security settings configured in ApplicationXtender Application Generator (AppXtender AppGen) can be set to control access by specific users to specific documents. AppXtender Web supports AppXtender security providers, which allow administrators to choose to manage user credentials through the built-in CM security provider, the built-in Windows security provider, or a directory service security provider. Flexible Configuration of Resource Authentication AppXtender Web allows you to configure your AppXtender Web resource authentication settings in a variety of ways. You can set up impersonation for a resource to cause credentials to be drawn from the specific source you select, and that source can be a dynamic or static source. This flexibility lets you set up a resource authentication model that leverages your existing resource authentication architecture. For example, you can configure your database access security so that access to the database uses credentials from the AppXtender Web user login, letting you audit specific user access through database management tools if needed. Support for HIPAA Compliance Efforts Although the AppXtender system has not been certified as HIPAAcompliant, it provides functionality that you can use in support of your compliance efforts. AppXtender lets administrators create applications that require reason codes to be enabled and comments to be entered when a document is created, opened, printed, exported, or 3

4 ApplicationXtender Web Access Benefits Document Signing ed. The comments are captured in the AppXtender Audit Trails facility. The AppXtender system supports the use of certificates to sign pages of a document. Signed documents cannot be modified without reapplying a signature, ensuring that changes to the document are audited. AppXtender Web allows AppXtender Web clients to sign document pages using certificates installed on the AppXtender Web Server, if the AppXtender Web Server they connect to runs on a.net platform. Extensive Content Management Functionality AppXtender Web provides functionality that lets you manage content through its entire lifecycle. Support for Multiple Web Server Platforms AppXtender Web has two supported deployment models: the ApplicationXtender Web Access.NET (AppXtender Web.NET) deployment model and the ApplicationXtender Web Access J2 (AppXtender WebJ2) deployment model. The AppXtender Web.NET deployment model depends on the Microsoft.NET framework. AppXtender Web.NET is compatible with and requires Microsoft Internet Information Server (IIS) 5.0 for Windows 2000 or IIS 6.0 for Windows The AppXtender WebJ2 deployment model utilizes the Sun Java framework. AppXtender WebJ2 is compatible with and requires the Java 2 Platform, Enterprise Edition (J2EE). AppXtender WebJ2 can run on Apache Jakarta Tomcat 5 standalone, on Tomcat using the Apache web server, or on IBM WebSphere 5.1. AppXtender WebJ2 can be deployed on Windows 2000, Windows 2003, Sun Solaris 10, or SuSE Linux 9.2. The AppXtender WebJ2 deployment model does not support Sybase SQL Anywhere, Microsoft Access, full-text indexing, or digital signatures. Windows-like Interface The client interface for AppXtender Web intentionally mimics the AppXtender Document Manager interface. Toolbars and menus are provided to facilitate access to AppXtender Web functions. Multiple documents and indexes corresponding to those documents can be displayed at the same time, allowing users to arrange the displayed documents in the most convenient layout for their work processes. 4

5 ApplicationXtender Web Access Benefits Client-side Caching When a page of the ApplicationXtender Web Access web site is loaded for the first time, the form for the page is cached at the server. Subsequent access to that cached page occurs much more quickly, even if content within the page changes. Clients using the Interactive Client mode cache document pages when the pages display, speeding repeated access to the same AppXtender document. Diverse Content Capture Methods Robust Search Capabilities Users add content to the AppXtender system through scanning or file import. AppXtender Web allows batch creation to make document capture more efficient. The batches are then indexed through AppXtender Web. Batches created through AppXtender Document Manager or Image Capture can also be indexed in AppXtender Web. Users retrieve documents in AppXtender Web using a wide range of search technologies, ranging from simple index searches to crossapplication queries. Users can search full-text indexes of AppXtender documents if the AppXtender Web Server they connect to runs on a.net platform. Expression and range searches provide the tools for more focused searches of large content repositories. Configurable Document Display AppXtender Web supports a wide variety of options that let the user or administrator control how retrieved content displays in the client browser. Two client modes are available: Thin Client mode, which provides access to most content management functionality through a browser without any additional downloaded components, and Interactive Client mode, for which a downloaded component provides toolbars and other functionality that more closely resembles the functionality of AppXtender Document Manager. Additional downloadable client components also provide extended viewing functionality for PDF files and files that are not natively supported in AppXtender. User profile settings allow users and administrators to toggle use of the expanded functionality on and off as needed. Comprehensive Content Processing Functionality Documents retrieved in AppXtender Web can be ed, exported, printed, or submitted for full-text indexing. Several of these functions can also be performed on individual pages. Multiple documents can be 5

6 Annotations and Redactions ed, printed, submitted for full-text indexing (if the AppXtender Web Server they connect to runs on a.net platform), or deleted through the AppXtender Web result set, without requiring document display first. Users can annotate PDF files in AppXtender Web, adding text, highlighting, lines, and shapes to enhance the content. Users can annotate and redact COLD, text, and image files. These items can be added to document or batch pages. Understanding ApplicationXtender Web Access AppXtender Web unites the power of AppXtender Document Manager content retrieval with the easy accessibility and portability of the Internet. Using a standard web browser (Microsoft Internet Explorer 6.0 (SP1) or Netscape Navigator 8.0), users can add, delete, view, edit, print, and documents from AppXtender applications. They can submit documents to AppXtender Index Server for OCR and full-text indexing, and index or view batches created in AppXtender Document Manager. In addition, users with administrative privileges can view and manage lists of active user sessions, checked-out documents, locked documents and active full-text or OCR jobs online in real-time, using the AppXtender Web Administrator area of the ApplicationXtender Web Access web site. You can create and manage profiles of AppXtender Web user settings through ApplicationXtender User Profile Administrator (AppXtender User Profile Admin). AppXtender User Profile Admin lets you modify the default user profile that is used as the basis for the user profile of each new AppXtender Web user. You can also use it to modify the profiles of specific users. Using Microsoft Internet Explorer or Netscape Navigator, end users connect to AppXtender Web Server, then search for AppXtender documents to view, index, or annotate. Users can choose to view AppXtender content using either Thin Client or Interactive Client modes. Thin Client mode reuses AppXtender storage and database components but relies on AppXtender Rendering Server to convert thumbnails, AppXtender Reports Mgmt image form overlay, images, and foreign files to formats that can be incorporated into HTML pages. Interactive Client mode uses the IRC Viewer ActiveX control on the client 6

7 The AppXtender System workstation to render AppXtender documents in their native format and allows end users to access advanced AppXtender features such as annotations. Interactive Client mode requires a Win32 platform, as well as the installation of the Interactive Client ActiveX control, which is automatically downloaded when a user attempts to display a document in Interactive Client mode. In AppXtender Web.NET deployments, ApplicationXtender Web Access web pages are implemented using the ASP.NET development framework. You can run the AppXtender Web.NET application on IIS 5.0 or 6.0. ASP.NET is a Microsoft technology that dynamically creates HTML content by incorporating external resources such as web forms and controls into a page. ASP.NET is more secure than previous generations of Microsoft web development technology, as it allows developers to reference source code from a page rather than including the code directly in the HTML source for the page. In AppXtender WebJ2 deployments, ApplicationXtender Web Access web pages utilize JSP technology. JSP is a Java-based technology that delivers dynamic HTML content to the user. You can run the AppXtender Web Java2 application on Tomcat standalone, on Tomcat using the Apache web server, or on IBM WebSphere. The AppXtender system is a content management system that allows your organization to move a large amount of content online in a costeffective manner. AppXtender provides the means to create, enhance, store, retrieve, and output any type of electronic content, optimizing the management and processing of vast amounts of data. AppXtender Web extends the AppXtender content management system to the World Wide Web, offering AppXtender content management capability to clients via the Internet or a corporate intranet. AppXtender Web is inherently tied to AppXtender for document storage and application and user security. Since AppXtender Web exists as a functional extension of the AppXtender product, an understanding of how AppXtender works is useful toward understanding the AppXtender Web architecture and how it functions within the AppXtender system. For more information about other components in the AppXtender system, request copies of the AppXtender, AppXtender Reports Mgmt, and AppXtender Workflow Technical Notes from your sales representative. 7

8 AppXtender Web Components AppXtender Web centralizes document access on the web server while utilizing the same imaging and database components as AppXtender Document Manager. AppXtender Web has two separate deployment models: the AppXtender Web.NET deployment model and the AppXtender WebJ2 deployment model. To support a flexible deployment model, AppXtender Web components are packaged in separate installations to allow you to selectively install components on different machines. The components that make up the AppXtender Web system fall into four categories: AppXtender Web environment components, AppXtender Web Server components, AppXtender Rendering Server components, and client components. For an understanding of which components are used on which computers within the AppXtender Web system, see "AppXtender Web System Architecture" on page 19. AppXtender Web includes the following installation wizards: AppXtender Web.NET Setup Wizard AppXtender WebJ2 Setup Wizard (for AppXtender WebJ2 deployments on Tomcat) A WAR file is available for AppXtender WebJ2 deployments on IBM WebSphere. AppXtender Rendering Server Setup Wizard AppXtender Web configuration is done through three components: ApplicationXtender Administrator (AppXtender Admin) ApplicationXtender User Profile Administrator (AppXtender User Profile Admin) ApplicationXtender Component Registration Wizard (AppXtender Component Registration) In addition, ApplicationXtender Web Access services on AppXtender Web Server and AppXtender Rendering Server, including AppXtender Rendering Server Service, provide the processing service required to respond to requests from AppXtender Web clients and help keep AppXtender Web Server running efficiently. Finally, AppXtender Web clients interact with the ApplicationXtender Web Access web site to use AppXtender Web, and can download a variety of installable client components that provide additional client functionality. 8

9 AppXtender Web Environment Components AppXtender Admin The following components must be in place in the AppXtender Web environment prior to deploying AppXtender Web: The AppXtender system must have a data source group set up, with at least one data source. Applications must be created to allow storage of documents. Users must be configured and assigned AppXtender privileges to allow them access to functionality within AppXtender Document Manager or Web. If you are using an AppXtender Web.NET deployment model, IIS must be installed on the computer to be used as the AppXtender Web Server. If you are using an AppXtender WebJ2 deployment model, Tomcat or IBM WebSphere must be installed on the computer to be used as the AppXtender Web Server. AppXtender Admin must be installed and available for configuration of AppXtender Web settings. AppXtender User Profile Admin, which is installed with AppXtender Admin, must also be installed. AppXtender Admin is the central configuration component in the AppXtender system. AppXtender Admin allows you to create data sources that connect to AppXtender-supported databases and automatically create the database table structure used by the AppXtender system. AppXtender Admin also lets you manage connections to the License Server, DiskXtender (DX) connections, and paths used by AppXtender system resources. AppXtender Admin is also used to configure AppXtender Web settings and monitor remote AppXtender system components. AppXtender Admin, the AppXtender database, and AppXtender applications must be installed and configured before the AppXtender Web components can be deployed. In addition, AppXtender Web settings in AppXtender Admin must be configured before AppXtender Web components are installed. 9

10 If you are implementing an AppXtender Web.NET server, you can either configure these settings in the AppXtender Web.NET Configuration Wizard or configure these settings (and other settings) in the AppXtender Admin tree. For details, see the following sections: "AppXtender Web Configuration in AppXtender Admin" on page 10 "AppXtender Web.NET Configuration Wizard" on page 11 AppXtender Admin depends on the Microsoft.NET framework, so the AppXtender Desktop installation wizard detects whether the framework already exists on the AppXtender Admin computer, then installs the framework if needed. AppXtender Web Configuration in AppXtender Admin AppXtender Admin has an AppXtender Web node that allows you to configure settings that apply to AppXtender Web.NET, AppXtender WebJ2, and AppXtender Web Services as shown in the following table: Table 1 Shared AppXtender Admin Settings AppXtender Admin Setting AppXtender Web.NET AppXtender WebJ2 AppXtender Web Services Global credentials for authentication AppXtender Web.NET session cache location AppXtender Web.NET security settings AppXtender Web settings AppXtender Web file types AppXtender Web logging facilities Security settings and logging settings for AppXtender WebJ2 deployments are configured by modifying files on the AppXtender WebJ2 Server. You can configure AppXtender Rendering Server settings under the Services node, including AppXtender Rendering Server service account credentials and AppXtender Rendering Server cache location and data source. 10

11 Figure 1 AppXtender Web Settings in AppXtender Admin AppXtender Web.NET Configuration Wizard The AppXtender Web.NET Configuration Wizard has three aspects, as described in the following table: Table 2 Wizard ApplicationXtender Wizard Aspect Desktop Web Access Web Access with Workflow integration Aspects of the AppXtender Web.NET Configuration Description This aspect of the wizard allows you to configure License Server connections and data sources. This aspect of the wizard allows you to configure the above settings plus all settings required for AppXtender Web.NET configuration: Global credentials, Session management, IIS security, , AppXtender Rendering Server, and Logging. This aspect of the wizard allows you to configure all of the above settings, plus settings for AppXtender Workflow integration. 11

12 AppXtender AppGen This wizard allows you to configure AppXtender Web.NET step by step. At the end of the wizard, a list of errors appears, indicating which settings remain to be configured before the AppXtender Web Server can be used. You can also display this list directly, without having to run the configuration wizard first. This wizard can be run at any time to configure and reconfigure AppXtender Web.NET. This wizard also allows you to quickly configure a default event logger for logging application errors. AppXtender Admin allows users to launch the wizard at startup via a command line switch. AppXtender AppGen plays an essential role in the AppXtender system, allowing you to create AppXtender applications and manage AppXtender user identities and privileges. Applications must be created and users configured in AppXtender AppGen before your users can start using AppXtender Web. AppXtender User Profile Admin AppXtender User Profile Admin can be used to manage AppXtender Web user profiles from a central location. A default user profile can be modified and each new AppXtender Web user adopts that profile as a default profile. Individual user profiles can also be modified through AppXtender User Profile Admin. You can load a profile from a file, modify it, and choose whether to save those changes to the AppXtender database or to a file. You can also copy profiles from one user to another. AppXtender User Profile Admin is installed on the AppXtender Admin computer when AppXtender Admin is installed. 12

13 Installation of AppXtender Web Components AppXtender Web components for AppXtender Web Server and Rendering Server are installed separately, so that you can install them on separate computers: For the AppXtender Web Server, installation varies depending on your deployment: To install AppXtender Web.NET, you run AppXtender Web.NET Setup Wizard. To install AppXtender WebJ2 on Tomcat, you run AppXtender WebJ2 Setup Wizard. To install AppXtender WebJ2 on IBM WebSphere, you use WebSphere and a WAR file to install a new application. For the AppXtender Rendering Server, you run AppXtender Rendering Server Setup Wizard. For information on the components these setup modules install, see the following sections: "AppXtender Web Server" on page 14 "AppXtender Component Registration" on page 14 "ApplicationXtender Web Access Web Site" on page 16 "AppXtender Rendering Server Service" on page 15. AppXtender Web Server Components The components required on the AppXtender Web Server depend on which deployment model you use: the AppXtender Web.NET deployment model or the AppXtender WebJ2 deployment model. AppXtender Web.NET Server Components When you set up an AppXtender Web.NET Server, you install AppXtender Web Server and Component Registration. Like AppXtender Admin, these components require the Microsoft.NET framework. Microsoft Internet Information Server (IIS) Microsoft Internet Information Server (IIS) is a standards-based, transactional web server that is fully integrated with Windows 2000 Server and Windows 2003 Server. AppXtender Web runs as an application on Microsoft IIS 5.0 on Windows 2000 and Microsoft IIS 6.0 on Windows When you install AppXtender Web on your IIS Server, AppXtender Web places the ApplicationXtender Web Access web site files on the site you select. AppXtender Web uses ASP.NET technology in conjunction with information from your AppXtender database to retrieve and display 13

14 requested documents. Without any custom development on your part, you can allow clients to add, delete, view, edit, annotate, and print AppXtender documents using Microsoft Internet Explorer or Netscape Navigator. AppXtender Web Server AppXtender Web Server installation installs the ApplicationXtender Web Access web site on your Internet Information Server. The ApplicationXtender Web Access web site contains the ASP.NET files that are used to create the HTML pages and other components received by AppXtender Web browser clients as they navigate through the ApplicationXtender Web Access web site. AppXtender Component Registration Running AppXtender Component Registration on the AppXtender Web Server computer registers the server with the AppXtender data source group. After installing AppXtender Web Server, run AppXtender Component Registration to add AppXtender Web Server to the data source group. AppXtender Component Registration must be run once for each component to be registered. Running AppXtender Component Registration after making changes to data source or global account credential settings registers those changes. AppXtender WebJ2 Server Components The AppXtender WebJ2 deployment model uses the Sun Java framework. AppXtender WebJ2 is compatible with and requires the Java 2 platform, Enterprise Edition (J2EE). AppXtender WebJ2 can run on Tomcat standalone, on Tomcat using the Apache web server, or on IBM WebSphere. AppXtender WebJ2 can be deployed on Windows 2000, Windows 2003, Sun Solaris 10, or SuSE Linux 9.2. Web Application Container AppXtender WebJ2 is compatible with and requires Jakarta Tomcat 5. AppXtender WebJ2 can run on Tomcat standalone. However, an application server can also be used. The AppXtender WebJ2 deployment model uses Jakarta Tomcat as a web application container on the Java 2 platform. Application Server AppXtender WebJ2 supports the following application servers: Apache web server IBM WebSphere

15 AppXtender WebJ2 Server AppXtender WebJ2 Server installation installs the ApplicationXtender Web Access web site on Tomcat or on IBM WebSphere. The AppXtender WebJ2 web site contains the JSP files that are used to create the HTML pages received by AppXtender Web browser clients as they navigate through the ApplicationXtender Web Access web site. AppXtender Component Registration Running AppXtender Component Registration on the AppXtender Web Server computer registers the server with the AppXtender data source group. After installing AppXtender Web Server, run AppXtender Component Registration to add AppXtender Web Server to the data source group. AppXtender Component Registration must be run once for each component to be registered. Running AppXtender Component Registration after making changes to data source or global account credential settings registers those changes. AppXtender Rendering Server Components The AppXtender Rendering Server Setup Wizard installs the AppXtender Rendering Server Service and Component Registration. You configure AppXtender Rendering Server Service settings through AppXtender Admin when you configure other AppXtender Web settings. You use AppXtender Component Registration to register AppXtender Rendering Server with the data source group. AppXtender Rendering Server Service When a user requests an image through AppXtender Web, that request is handled by an.aspx page, which passes the request to a worker process. If the request requires rendering of images for thin client viewing, thumbnails, AppXtender Reports Mgmt image form overlay, or , the worker process first searches the AppXtender Rendering Server database to find out if the file is in the rendering cache. If the file has been cached, the AppXtender Rendering Server Service retrieves it from the rendering cache. It then returns the JPEG or GIF (depending on which conversion type is chosen in AppXtender Admin) to the requesting.aspx page, which incorporates the image in the HTML page it returns to the browser. This causes performance to improve when multiple users access the same image since the image does not have to be converted multiple times. If the requested image has not been rendered, the worker process passes the request to AppXtender Rendering Server Service. AppXtender Rendering Server Service renders the image and delivers it back to the worker process, which inserts it in the HTML page that is delivered to 15

16 the client. As images fill up the cache, AppXtender Rendering Server Service discards older images according to Cleanup parameters set in the AppXtender Rendering Server settings in AppXtender Admin. AppXtender Component Registration AppXtender Component Registration on the AppXtender Rendering Server computer registers the AppXtender Rendering Server location with the AppXtender data source group. Once AppXtender Rendering Server has been installed, AppXtender Component Registration must be run to add that computer to the data source group. AppXtender Component Registration must be run once for each component to be registered. After making changes to data source or AppXtender Rendering Server account credential settings, run AppXtender Component Registration again to register those changes with the data source group. AppXtender Web Client Interface When a user logs into AppXtender Web, the user does so by connecting to the ApplicationXtender Web Access web site. The ApplicationXtender Web Access web site provides the client interface for AppXtender Web. Two different client modes, Thin Client mode and Interactive Client mode, provide different document display options. ApplicationXtender Web Access Web Site The ApplicationXtender Web Access web site contains the ASP.NET or JSP files that are used to create the HTML pages and other components received by AppXtender Web browser clients as they navigate through the ApplicationXtender Web Access web site. 16

17 Figure 2 ApplicationXtender Web Access Web Site AppXtender Web IRC Viewer Component The IRC Viewer component is used to provide the same document display available in AppXtender Document Manager. The same toolbars and functionality provided in the Document Display View in AppXtender Document Manager are offered through the IRC Viewer component. This component is automatically installed and used in Interactive Client mode. AppXtender Web IRC Result Set Component The IRC Result Set component enables multi-document processing from the AppXtender Web Result Set. For example, if users have their AppXtender Web client setting set to Interactive Client mode, they can download this component to print multiple documents from the AppXtender Web result set. This component is automatically installed and used in either client mode. AppXtender Web Adobe Component An Adobe PDF component can also be downloaded and installed to allow viewing of Adobe PDF files in native format. Downloading and installing the Adobe component provides access to the Adobe Acrobat Reader toolbar and allows users to manipulate annotations on PDF files in Interactive Client mode. 17

18 AppXtender Web Scan Component Downloading the AppXtender Web Scan component allows users to scan documents to the AppXtender repository through AppXtender Web. The AppXtender Web Scan component installs TWAIN, ISIS, and Kofax scan drivers for use by the AppXtender Web client. This component can be installed and used in Interactive Client mode. AppXtender Web Verity KeyView Viewer Component If the Verity KeyView Viewer component is downloaded and installed and KeyView viewing technology is enabled in the AppXtender Web user settings profile for a user, the Verity KeyView component allows rendering of foreign files in Interactive Client mode. If the KeyView component is not used, foreign files are presented as a link. This component can be installed and used in Interactive Client mode. Installer for AppXtender Web Interactive Client Components AppXtender Web provides an installer that can install AppXtender Web IRC components for normal operation of AppXtender Web clients. The installer has the following features: Performs seamless installation of web components onto a target workstation without interfering with the normal operations of components installed via the download approach. Is executed via command line from a remote location. [silent mode] Installs components that co-exist with other versions of the same component. Uninstalls components without interfering with the normal operations of different versions of the same component. Upgrades components to a higher major version, or higher minor version according to upgrading rules. Generates an installation log. The AppXtender Web IRC Installer is limited to ActiveX IRC components and does not install Java applets. 18

19 Configuring Client Download of JRE By default, when an AppXtender Web user attempts to use thumbnails or cross-application queries, if Java 2 Runtime Environment (JRE) has not already been downloaded, the user is prompted to download JRE If necessary, you can configure AppXtender Web so that users can use JRE 1.3, 1.5, or Oracle JInitiator instead of JRE If your client computers already have JRE 1.4.2, no configuration is necessary. You can perform this configuration by modifying an XML file and restarting the application server (IIS, Tomcat, Apache, or WebSphere). The next time a user attempts to launch thumbnail or cross-applicationquery applets, the applets will load JVM based on your configuration. To change JRE download configuration, you should understand how applets work with Java Virtual Machine (JVM) on clients. AppXtender Web System Architecture A typical AppXtender Web deployment usually consists of: One AppXtender Web Server computer One or more AppXtender Rendering Server computer One computer with AppXtender Admin installed and the additional servers required to support the AppXtender system (such as the AppXtender database server, the License Server, and AppXtender Index Server and full-text database server) The content storage repository (typically DX) A connection through the Internet or an intranet to a number of clients using a web browser The diagram in Figure 3 illustrates a possible deployment model for an AppXtender system. The callouts within the diagram indicate what components are installed on the main components of the system (from an AppXtender Web perspective). 19

20 Figure 3 AppXtender Network Architecture with AppXtender Web.NET Components AppXtender Admin allows you to create data source groups where all components and modules connecting to the data source group share the same pool of data sources, License Server settings, and document storage configuration settings. The illustration in Figure 3 shows a data source group with one AppXtender Web.NET Server, one AppXtender Rendering Server, an AppXtender Index Server, a full text database server, a database server supported by AppXtender, storage servers for content storage, and a licensing server. The illustration in Figure 4 shows a data source group with one AppXtender WebJ2 Server, one AppXtender Rendering Server, a database server supported by AppXtender, storage servers for content storage, and a licensing server. 20

21 Figure 4 AppXtender Network Architecture with AppXtender WebJ2 Components All AppXtender Web components within a data source group share processing responsibilities. For example, multiple AppXtender Rendering Servers might be registered for a particular data source group. The AppXtender Rendering Server settings configured in the AppXtender Admin console for that data source group apply to all AppXtender Rendering Server, and the AppXtender Rendering Servers work in tandem to process rendering requests from the AppXtender Rendering Server request queue. In each AppXtender data source group, you must have one AppXtender Web Server to enable browser-based access to AppXtender documents. If Thin Client mode HTML rendering, thumbnail rendering, AppXtender Reports Mgmt image overlay rendering, or rendering are required by browser clients accessing your AppXtender system, or if you are using an AppXtender WebJ2 deployment model, at least one AppXtender Rendering Server is required. You can choose to install 21

22 AppXtender Rendering Server components on the same server as the AppXtender Web Server, or you can set up a separate AppXtender Rendering Server or Servers. AppXtender Web clients can connect to the AppXtender Web Server in either Thin Client or Interactive Client mode. Clients can also download and install PDF and foreign file viewing and scan components to make additional functionality accessible within either of those modes. A detailed discussion of AppXtender Web system architecture follows for both deployment models of AppXtender Web Server, AppXtender Rendering Server, and AppXtender Web Thin Client and Interactive Client modes. The AppXtender Web components of the AppXtender system are designed to allow flexibility in the deployment of those components. The AppXtender Web.NET Server Deployment Model The AppXtender Web.NET deployment model depends on the Microsoft.NET framework. AppXtender Web.NET is compatible with and requires IIS 5.0 for Windows 2000 or IIS 6.0 for Windows AppXtender Web places the ApplicationXtender Web Access web pages in an AppXtender Web directory associated with the selected web site. After you configure AppXtender Web, the default ApplicationXtender Web Access web pages are used in conjunction with information from your AppXtender database to retrieve and display requested documents. Without any custom development on your part, you can allow remote users to view, edit, print, add, and delete AppXtender documents using Microsoft Internet Explorer or Netscape Navigator. AppXtender Web.NET has been tightly integrated with Microsoft's.NET framework, allowing AppXtender Web to use the latest and most innovative technologies from IIS. The web pages are implemented using ASP.NET technology a Microsoft technology that is built upon a scalable and flexible platform that uses Just-In-Time compilation to significantly improve performance. In addition, XML and advanced caching techniques are used to further optimize performance and scalability. AppXtender Web.NET Server is installed on an IIS computer that hosts the ApplicationXtender Web Access web site. The ApplicationXtender Web Access web site content is installed on the server through AppXtender Web Setup Wizard. AppXtender Web Server hosts the ASP.NET resources that combine to supply the interface for clients logging into AppXtender Web. AppXtender Web.NET Server uses a session cache to manage AppXtender Web browser session data. That cache can be located on the 22

23 AppXtender Web.NET Server computer for most efficient processing. User session data for active user sessions is stored in the session cache. For more detailed information about the specific components installed on the AppXtender Web Server computer, see "AppXtender Web Server Components" on page 13. Although AppXtender Web.NET is designed for use with Internet Explorer and Netscape, Internet Explorer is recommended for an optimal user experience. The AppXtender WebJ2 Server Deployment Model The AppXtender WebJ2 deployment model utilizes the Sun Java framework. AppXtender WebJ2 is compatible with and requires the Java 2 Platform, Enterprise Edition (J2EE). AppXtender WebJ2 can run on Tomcat standalone, on Tomcat using the Apache web server, or on IBM WebSphere. AppXtender WebJ2 can be deployed on Windows 2000, Windows 2003, Sun Solaris 10, or SuSE Linux 9.2. AppXtender WebJ2 Server is installed on the Tomcat or IBM WebSphere computer that hosts the ApplicationXtender Web Access web site. The ApplicationXtender Web Access web site content is installed on the server through a setup wizard (when installing on Tomcat) or a WAR file (when installing on WebSphere). AppXtender WebJ2 Server hosts the JSP files that supply the interface for clients logging into AppXtender Web. AppXtender WebJ2 Server uses a session cache to manage AppXtender Web browser session data. That cache can be located on AppXtender Web Server for most efficient processing. User session data for active user sessions is stored in the session cache. The AppXtender WebJ2 deployment model does not support Sybase SQL Anywhere, Microsoft Access, full-text indexing, or digital signatures. For more detailed information about the specific components installed on the AppXtender Web Server computer, see "AppXtender Web Server Components" on page 13. AppXtender Rendering Server AppXtender Rendering Server renders AppXtender Web content for Thin Client mode browser clients, thumbnail viewing, AppXtender Reports Mgmt form overlay viewing, or AppXtender Web features. For small systems, you can choose to install AppXtender Rendering Server on the same computer as AppXtender Web Server. If you are deploying an enterprise system, you can also choose to install one or more AppXtender Rendering Servers on separate computers to 23

24 provide more efficient processing of client requests. If installed separately from AppXtender Web Server, AppXtender Rendering Server offloads processing tasks from AppXtender Web Server. This enhances AppXtender Web Server performance, especially when many users access the server simultaneously. This flexible deployment model is designed to offer the greatest level of scalability and performance as the number of concurrent users grows. AppXtender Rendering Server uses both a rendering cache and rendering database to manage the rendering request queue. Once a file is rendered, it is cached in the rendering cache location. Information relating to cached files and the current rendering request queue is stored in the rendering database. The rendering server database tables can be added to the AppXtender database, or you can create a separate database on any of the AppXtender Web supported database platforms. For more detailed information about the specific components installed on the AppXtender Rendering Server computer, see "AppXtender Rendering Server Components" on page 15. AppXtender Web Client Architecture AppXtender Web has two client modes: Thin Client mode and Interactive Client mode. The AppXtender Web system administrator can decide to allow users to choose whether to use the Thin Client or Interactive Client mode, or can control the mode setting by setting the mode in the default user profile and then disabling user access to the setting. For more detailed information about the ApplicationXtender Web Access web site that acts as the AppXtender Web client interface and about downloadable components that can be installed on AppXtender Web clients, see "AppXtender Web Client Interface" on page 16. Dual-Mode Client Functionality There are differences between AppXtender Web Thin Client mode and AppXtender Web Interactive Client mode, primarily in the functionality available when a document displays and in the options for processing documents from the result set. However, several aspects of client functionality are common to both client modes, including search functionality, thumbnail display, and index display and modification. If increased content management functionality is necessary (including the magnifier, multiple page upload, enhanced zoom control, document properties view, and annotations), Interactive Client mode should be used. In addition, Interactive Client mode presents images in their native 24

25 format, allowing for the highest quality. Thin Client mode, by comparison, requires AppXtender Rendering Server conversion of images to GIF or JPEG format for online viewing. The following common functionality is available in either client mode: Users can retrieve documents using a variety of search methods including cross-application queries, index term searches, document property searches, full-text searches (in AppXtender Web.NET deployments), ad-hoc text searches, wildcard searches, list of values searches, and expression searches. Dialog boxes similar to those provided in AppXtender Document Manager aid the user in creating the necessary syntax to perform list of values and expression searches. When a query is executed, the list of results appears in the AppXtender Web Result Set. From here, in addition to opening documents, users can choose to sort results, toggle through results pages, and enable/disable document thumbnails. If the IRC Result Set component is downloaded, multiple documents can be printed, ed, exported, or deleted from the result set. Thumbnails representing the pages of the currently viewed document can be displayed on the Document View page. Once a document is opened from the Result Set, users can view document indexes using the Document Index view and can (with appropriate privileges set in AppXtender AppGen) modify indexes as needed. When modifying indexes, a user can employ dual data entry, multiple indexes referencing a single document, Auto Indexing, and Key Reference indexing in applications configured with those functions. Version control is provided using the AppXtender Web Check In/Check Out feature. Users can check documents out after retrieving them. When a user checks out a document, other users view the document in read-only mode, preventing simultaneous revisions and loss of work. Documents can be submitted to AppXtender Index Server for fulltext indexing from the Document View page. Digital signatures can be applied to AppXtender documents hosted on an AppXtender Web.NET server. Reason codes can be used to track what users access a document, when, and for what reasons. 25

26 AppXtender Web Client/Server Data Flow In the pages prior to the Document Display page, the flow of data between client and server is the same for both client modes. When users log into AppXtender Web and run queries, HTTP requests are sent to the appropriate ASP.NET.aspx page that resides on the IIS server. The.aspx page hands off the processing request to a worker process, outside of the IIS web server process. This worker process processes the ASP.NET.aspx page, creating the requested HTML page and delivering it to the client. When a page is displayed for the first time, JavaScript is downloaded to the client to allow for more efficient client-side processing of the page when it is loaded in the future. When a HTTP request is a request for document display, the worker process passes requests for rendered content to AppXtender Rendering Server. AppXtender Web uses AppXtender Rendering Server to render data in a web-viewable format in several instances: If the client is in Thin Client mode If thumbnails are requested If the document is an AppXtender Reports Mgmt document with image overlay AppXtender Rendering Server returns the rendered content to the worker process, which includes it in the HTML page returned to the client. When a client attempts to display a document in AppXtender Web, the server response depends on whether the client is in Thin Client mode or Interactive Client mode. In Thin Client mode, document pages must be converted to a web-viewable format before they are transmitted to the client. When a client in Interactive Client mode requests a document, the document is delivered directly to the client and cached on the client. It is then displayed in the IRC Viewer. The sections that follow provide detailed information on the flow during document retrieval for each client mode. Thin Client Mode AppXtender Web Thin Client mode allows users to view, edit, and print AppXtender documents using a web browser, without any additional software or plug-in installation. Thin Client mode provides a basic client and requires only that a supported web browser be installed. Interactive Client mode supplies extensive functionality, but Thin Client mode may be a more appropriate choice if you are retrieving documents for viewing or index editing only. 26

27 In Thin Client mode, users can scale documents using preset zoom functions. Users can generate printer-friendly views to facilitate document printing. In addition, the Verity KeyView Viewer allows Thin Client users to view foreign files natively, if foreign file export has been enabled in the AppXtender Web settings in AppXtender Admin. When a client operates in Thin Client mode, no additional downloaded components are needed to access most AppXtender Web functionality. AppXtender Rendering Server renders images and thumbnails for inclusion in the HTML pages that display in Thin Client mode. AppXtender Web Thin Client mode can also be configured to open a document in its native application within the Document View frame, as long as the file type association is configured in AppXtender Admin and the client computer has the associated application installed. Supported Document Types for Thin Clients The following table lists supported AppXtender Web document types and describes how those document types are treated in Thin Client mode in AppXtender Web. Table 3 Document Type Image AppXtender Reports Mgmt AppXtender Reports Mgmt with Text Form Overlay AppXtender Reports Mgmt with Image Form Overlay Foreign File OLE Object PDF File Supported Document Types for Thin Clients Comments Preset zoom ratios are provided. Annotation viewing is supported. Zoom ratios are not supported, unless an image form overlay is in use. No color bars. Text form overlays cannot be turned on and off by the client. Image form overlays can be turned on and off by the client from the Options page. Zoom and custom fonts are allowed with image form overlay. Presented as a link, which the user can click to download the file. If a file association is configured in AppXtender Admin and the application associated with the file type exists on the client computer, the document opens with the native application in the AppXtender Web Document window. If you enable foreign file rendering in AppXtender Admin, foreign files are converted to HTML format, and included graphics are rendered as GIF or JPEG. AppXtender Web does not support embedded OLE objects. To add file types not supported by AppXtender, add the files as foreign files in AppXtender Web or Document Manager rather than using OLE embedding in AppXtender Document Manager. PDF files, like foreign files, are presented as links, which the user can click to download the file (if Acrobat Reader is installed, clicking the link opens the PDF file in the browser). If a user has downloaded the optional Adobe component, PDF files display in their native format in the AppXtender Web Document window. 27

28 Interactive Client Mode When a client operates in Interactive Client mode, two components are automatically downloaded to enable additional functionality: the IRC Viewer component and the IRC Result Set component. The IRC Viewer component allows users to access an interface very similar to the AppXtender Document Manager user interface over the Internet. The IRC Result Set lets users process multiple documents from the result set. The AppXtender Web Interactive Client mode has all the functionality available in Thin Client mode, but allows users to view documents using the IRC Viewer and to process multiple documents from the result set using the IRC Result Set component. The IRC Viewer provides access to the image and annotation toolbars, which include access to annotations, enhanced zoom options, page rotation, magnification, printing, client workstation configuration, and image information. The presence of the IRC Viewer also enables users to import multi-page batches and to scan pages into AppXtender Web. (Scanning also requires download and installation of the AppXtender Web Scan Component on the client station.) Clients operating in Interactive Client mode can download components to add functionality that would not otherwise be available. The Check Installed Components dialog box on the AppXtender Web client lists the downloadable components, which include the Adobe component, the AppXtender Web Scan component, and the Verity KeyView Viewer component. For more information on each of these components, see the following sections: "AppXtender Web Adobe Component" on page 17 "AppXtender Web Scan Component" on page 18 "AppXtender Web Verity KeyView Viewer Component" on page 18 Interactive Client mode requires a Win32 platform. AppXtender Web currently supports Microsoft Internet Explorer and Netscape Navigator browsers. Internet Explorer is highly recommended, as it provides native XML support, allowing for a faster AppXtender Web experience with less strain on the AppXtender Web Server. Netscape requires the Interactive Client Viewer Plug-In. The plug-in interprets and implements ActiveX controls within Netscape Navigator. AppXtender Web.NET supports use of Netscape Navigator 8.0 but not other versions of Netscape. AppXtender Web Interactive Client Data Flow Interactive Client mode actively loads a document into the Interactive Client Viewer ActiveX control for dynamic viewing and update. The 28

29 client then uses the ActiveX control whenever AppXtender Web displays a document. When new pages are viewed within a document, they are retrieved directly from the document storage location. AppXtender Rendering Server does not intercept requests for or cache Interactive Client documents, even if the documents are images. However, AppXtender Rendering Server does intercept requests for thumbnail images and foreign file exports, and caches them. It follows the same procedure to convert and display thumbnail images as is used for the conversion and display of Thin Client documents. Web site content and/or AppXtender documents are copied to and cached in the browser cache until the space used in the browser cache exceeds the browser's configured cache limits and the user's browser cache is purged. Supported Document Types for Interactive Clients The following table lists supported AppXtender Web document types and describes how those document types are treated in Interactive Client mode in AppXtender Web. Document Type Image Table 4 AppXtender Reports Mgmt AppXtender Reports Mgmt with Text Form Overlay AppXtender Reports Mgmt with Image Form Overlay Foreign File OLE Object Supported Document Types for Interactive Clients Comments Preset zoom ratios are provided. Viewing and editing of annotations is supported. Zoom ratios and color bars are supported. Color bars are supported. Font sizes can be modified in the Interactive Client Configuration Properties dialog box. Form overlay can be turned on and off on the client from the Interactive Client Configuration Properties dialog box. Image form overlays can be turned on and off on the client from the Interactive Client Configuration Properties dialog box. Zoom is allowed with image form overlay. Custom fonts can also be used with this overlay. Presented as a link, which the user can click to download or save the file. If the Verity KeyView component is downloaded and installed, and use of KeyView to display foreign files is enabled within the user's profile, foreign files with recognized extensions are converted to HTML format are rendered using the KeyView technology, within the IRC Viewer. The AppXtender Web Interactive Client supports embedded OLE objects, but AppXtender Web Thin Client does not support embedded OLE objects. To add file types not supported by AppXtender, add the files as foreign files in AppXtender Web or Document Manager rather than using OLE embedding in AppXtender Document Manager. 29

30 PDF File If the Adobe Acrobat plug-in is installed on the client computer, and the AppXtender Web Adobe component has not been downloaded and installed, the Adobe plug-in displays PDF pages with the IRC Viewer. If the AppXtender Web Adobe component is downloaded and installed, the component is used to display PDF files within the Interactive Client Viewer. Using the Acrobat plug-in, all Acrobat Reader navigation and viewing functions are supported. Using the AppXtender Web Adobe component, all Acrobat Reader navigation and viewing functions are supported and annotations are supported. Monitoring Configuration Updates AppXtender web applications (AppXtender Web.NET, Utility Services, and Web Services) load configurations (such as data source and License Server connections) at startup and cache them for the duration of their lifetime. Some configuration updates take effect immediately, but some take effect only when the web application is restarted. By default, AppXtender web applications automatically restart under certain conditions. This is intended as a compromise between implementation of configuration updates and user access to the web application. However, you can configure this feature to optimize either implementation of configuration updates or user access to the web application. The AppXtender WebJ2 deployment model does not use these configuration monitoring settings. The default configuration monitoring settings are the recommended settings and will suffice in most cases. The following table describes how configuration updates will be handled by the web application as it monitors for configuration updates. Realtime updates occur only if the application is configured to poll for configuration updates. The following table lists each of the settings, or group of settings, in AppXtender Admin that apply to AppXtender web applications. For each of these settings, the table indicates how the update is applied: Table 5 Types and Effect of Configuration Updates Configuration Update Effect of the Update Global Impersonation Account Real-time License Servers Real-time update when change is detected. Re-login required to detect change. Data Sources (without dropping any existing data sources) Real-time update when change is detected. Re-login required to detect change. 30

31 Configuration Update Data Sources (Data source is deleted or becomes hidden) Dual Write Paths DiskXtender Servers Document Signing AppXtender Web (Session path does not change) AppXtender Web (Session path change) File Type Map Address book Authentication Service Authorization Service AppXtender Rendering Server Settings AppXtender RM Service Logging Effect of the Update Application Restart Real-time update when change is detected Real-time update when change is detected Real-time update when change is detected Real-time Application Restart Scheduled Real-time update when change is detected Real-time update when change is detected Requires restart Requires restart Real-time update when change is detected Application Restart Application Restart If there are any changes in AppXtender AppGen, you must restart IIS manually. Error Log Default Software Integrations The error log default feature is intended to encourage the use of error logs in AppXtender Web configuration, which should improve the resolution time of technical support calls. This feature is supported for both deployment models of AppXtender Web (AppXtender Web.NET and WebJ2), but implementation is slightly different in the two deployment models: In AppXtender Web.NET, this feature is implemented via the new AppXtender Web.NET configuration wizard in AppXtender Admin. In AppXtender WebJ2, this feature is implemented via the Apache Log4J logging facility. The following software can be integrated with AppXtender and viewed in AppXtender Web: Operating systems supported by AppXtender or AppXtender Web might not be supported by these third-party components. 31

32 Security Software Records Manager (RM) SP1 Table 6 AppXtender Integrations Description of Integration Records Manager for ApplicationXtender (RM for AppXtender) is a Department of Defense (DoD) compliant and certified records management module of AppXtender. It allows AppXtender users to classify and submit documents into RM from either AppXtender Document Manager or Web. RM for AppXtender allows users to create, review, revise, approve, and distribute content within an audited environment, letting users enforce, model, and track approvals and change management on regulated content. For more information, refer to the Records Manager for ApplicationXtender Integration Guide. Records Manager full-text searches are available only when the AppXtender Web server is running on an AppXtender Web.NET Web server rather than an AppXtender WebJ2 Web server. ecopy ShareScan 8.3 and ShareScan OP 3.0 ESRI ArcGIS 9.0 eroom ShareScan for AppXtender allows users to scan documents directly into AppXtender from the ecopy ShareScan user interface. Documents may be scanned in individually or in batches. In the case of individual documents, the indexing procedure for AppXtender is performed through the ShareScan user interface. When indexing documents through ShareScan, AppXtender Key Reference as well as Date and Time Stamp fields are also supported. Batches are indexed through AppXtender using the standard batch indexing procedure. Up to four separate connections to AppXtender may be configured. For more information, refer to the ShareScan Connector for ApplicationXtender Integration Guide and the ShareScan OP Connector for ApplicationXtender Integration Guide. The ArcGIS for ApplicationXtender is the interface between the AppXtender and ESRI ArcGIS systems. The ApplicationXtender Interface for ArcGIS provides ArcGIS users with the ability to seamlessly retrieve and view documents associated with spatial data items. For more information, refer to the ArcGIS for ApplicationXtender Quick Reference. The eroom product provides a robust collaboration environment for knowledge workers. eroom allows for ad-hoc and template-based collaboration. Using the AppXtender Web CDK, AppXtender Web.NET can be extended to provide ad-hoc collaboration features by leveraging the eroom SDK to create document links within the eroom environment. This greatly increases the ease at which discussions can occur around AppXtender content. Security AppXtender Web relies on AppXtender for security profiles (including annotation groups) and Document Level Security. When users log into AppXtender Web using their AppXtender user names and passwords, they are given the same access privileges as would be assigned during AppXtender Document Manager sessions. Both AppXtender application level security and document level security apply to users logging into AppXtender Web. In addition, AppXtender Document Level Security (DLS) stays in effect for those applications that have DLS active. DLS allows you to deny or grant user access to selected documents, without restricting access to all documents in an application. 32

33 Licensing Licensing AppXtender Web relies on AppXtender for licensing. As with other AppXtender products, AppXtender Web uses License Server to store and validate AppXtender Web licenses. The License Server is used by workstations to validate AppXtender content management product licensing options and to monitor users on the system. AppXtender Web should automatically detect the License Server upon installation, as AppXtender Web reads the necessary licensing information from the data sources that are configured using AppXtender Admin. However, you must be sure that the AppXtender Web serial number has been entered into the License Server. While AppXtender Web user licenses may be separate from AppXtender Document Manager licenses, Full-Text Search licenses are currently shared with AppXtender Document Manager. You can purchase three types of AppXtender Web licenses: Full Licenses: Full licenses are per-seat licenses that allow users to access all features of AppXtender Web. Public Access Licenses: Public Access Licenses (PAL) can be used for a large number of users using AppXtender Web to access AppXtender documents in read-only mode using the AppXtender Web Thin Client. AppXtender Full-Text Licenses: When a user enables the Request Full Text Search Support check box on the login page, the user is using an AppXtender Full-text license. This license is actually drawn from the AppXtender license pool. Verity K2 full-text search licenses are included in AppXtender licensing. By default, when AppXtender Web licenses are unavailable, AppXtender Desktop licenses are used instead. If necessary, you can disable this feature. Using ApplicationXtender Web Access The ApplicationXtender Web Access web site offers both AppXtender Web administrative tools and content management functionality for end users. This section highlights some of the functionality available, and provides examples of some of the pages on the ApplicationXtender Web Access web site. Online AppXtender Web Administration The AppXtender Web Administrator section of the ApplicationXtender 33

34 Using ApplicationXtender Web Access Web Access web site allows you to manage user sessions, checked-out documents, locked documents, and full-text/ocr jobs in real-time. Figure 5 AppXtender Web Administrator Session List You can also view AppXtender Web Server, Rendering Server, and Index Server properties and statistics using the AppXtender Web Administrator monitoring pages. Figure 6 AppXtender Web Administrator AppXtender Web Monitor 34

35 Using ApplicationXtender Web Access AppXtender Web Administrator is secure and appears as an option from the AppXtender Web Edit menu, visible only to users assigned the Administrator privilege. Managing Content through AppXtender Web AppXtender allows you to manage content through its entire lifecycle. AppXtender Web provides the AppXtender web interface for adding, retrieving, and processing content. Accessing AppXtender Applications The AppXtender Web window appears after the AppXtender user logs into AppXtender Web. From the AppXtender Web window, users can add content to an application or search an application or applications to retrieve existing content. They can also access the settings for their user profiles from this window. Figure 7 AppXtender Web Window Applications List Managing User Settings AppXtender Web clients can manage the specific user settings for their client profiles through the AppXtender Web client interface. If the Configure WS privilege is enabled for a user in AppXtender AppGen, the user can configure search and result set settings, full-text settings, document view options, Interactive Client viewer behavior, AppXtender Reports Mgmt document display options, Result Set Print settings, e- mail options, and print options. 35

36 Using ApplicationXtender Web Access Figure 8 Settings Dialog Box Adding Content to AppXtender Web Users can add content to AppXtender Web by scanning or importing batches through AppXtender Web, adding the batches to the AppXtender batch queue. 36

37 Using ApplicationXtender Web Access Figure 9 Import New Page Dialog Box Users can index batches created in AppXtender Web, Document Manager, or Image Capture. Figure 10 Batch List Window Batches Available for Indexing The user separates the batch into individual pages or documents as needed during indexing. 37

38 Using ApplicationXtender Web Access Figure 11 AppXtender Web Batch Index Document Window Indexing a New Document Once a document has been indexed, a user can retrieve it by running a query from the AppXtender Web window. Figure 12 AppXtender Web Window Applications List Shortcut Menu Options Retrieving AppXtender Documents AppXtender Web supports a wide variety of search options, including simple keyword search, wildcard search, expression search, range or list of values search, full-text search (for AppXtender Web.NET Server deployments), and cross-application queries. Users can also perform adhoc text searches on a set of search results to narrow the results. Users can start a query from the AppXtender Web window. 38

39 Using ApplicationXtender Web Access Figure 13 AppXtender Web Window Query Criteria Page Once the query is executed, documents matching the search criteria are listed in the Query Results page. 39

40 Using ApplicationXtender Web Access Figure 14 AppXtender Web Window Query Results Page Displaying Content AppXtender Web displays content in specific ways based on the configured AppXtender Web client mode, the user profile settings, and the presence of downloaded components. For more information on the client modes and the downloaded components, see "AppXtender Web Client Interface" on page 16 and "AppXtender Web Client Architecture" on page 24. See examples of how an imported Word file displays in the different client modes in Figure 15 on page 41 and Figure 16 on page

41 Using ApplicationXtender Web Access Figure 15 AppXtender Web Document Window Thin Client Mode with Server-Side Rendering Option Enabled Figure 15 shows how document display options would be presented for a Word file when the browser is in Thin Client mode. Even if the KeyView component were installed on this client and the KeyView option enabled in the user profile settings, the display options would still be those shown while the browser is in Thin Client mode. Figure 16 shows how the same Word file displays when the browser is in Interactive Client mode, the KeyView component is installed on this client, and the KeyView option is enabled in the user profile settings. 41

42 Using ApplicationXtender Web Access Figure 16 AppXtender Web Document Window Interactive Client Mode with KeyView Component Installed and KeyView Viewer Option Enabled AppXtender Web can be configured so that documents are displayed within the main browser window or in a separate window. Also, if AppXtender Web has been configured so that documents are displayed within the main browser window, AppXtender Web users can navigate to the previous or next document (as listed in the query results) from the document view. In AppXtender Desktop, when the result set contains only one document, the document is automatically opened. AppXtender Web result set functionality can be configured to match that of AppXtender Desktop in this respect. This feature improves performance by reducing the number of round trips to the server and eliminates the need for the result set rendering. For the user, this feature allows viewing the document using fewer clicks and less time. This feature can be configured via the AppXtender Web Settings page or AppXtender User Profile Admin. When this feature is enabled, and when AppXtender Web has been configured so that documents are displayed within the main browser window, and the query yields only a single document, the document is automatically displayed. When an image is being viewed in AppXtender Web Thin Client mode, the image can be flipped horizontally and vertically and can be rotated. The state of the image will always revert to its original state if the web page is refreshed. This feature is not available with Netscape or in AppXtender Web IRC mode. 42

43 Using ApplicationXtender Web Access Processing Documents AppXtender Web provides many options for processing documents and pages stored in AppXtender Web. Documents and pages can be e- mailed, printed, exported, annotated, submitted for full-text indexing, and deleted. In addition, revision histories and properties can be viewed for documents. Figure 17 AppXtender Web Document Window Document Processing Options Some of the processing options for pages are similar to those for documents, but users can also apply a digital signature to a page and view the signature history for a page when connecting to an AppXtender Web.NET Server. Figure 18 AppXtender Web Document Window Page Processing Options Several document processing functions can be performed for multiple documents from the Query Results page. 43