EMC ® ApplicationXtender ®

Web Access .NET

6.5

Administrator’s Guide
P/N 300-010-571 A01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 1994-2010 EMC Corporation. All rights reserved.
Published March 2010
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
 Table of Contents

Preface ................................................................................................................................ 13
Chapter 1 Planning AppXtender Web Access Deployment .......................................... 15
AppXtender Web Access Deployment Overview ................................................ 15
Preparing the AppXtender Content Management Environment ....................... 16
Displaying AppXtender Web Access Settings in AppXtender
Admin ..................................................................................................... 17
Starting AppXtender Administrator ....................................................... 18
Selecting Data Sources .......................................................................... 18
Specifying a Default Data Source ....................................................... 18
Specifying Multiple Data Sources ...................................................... 19
Showing the AppXtender Web Node ..................................................... 19
Licensing AppXtender Web Access ............................................................ 19
License Server ...................................................................................... 19
License Groups..................................................................................... 20
Types of Licenses .................................................................................. 20
AppXtender Public Access Licensing ..................................................... 20
AppXtender Web Services Standalone vs. Integrated Mode ..................... 20
Testing the AppXtender Content Management Environment ....................... 21
Configuring Authentication Accounts ............................................................ 21
Testing Authentication Account Access to Paths ......................................... 22
Preparing the AppXtender Rendering Server.................................................. 22
AppXtender Rendering Server Requirements ............................................. 22
AppXtender Rendering Server Computer Preparation Checklist .................. 22
Preparing the AppXtender Web.NET Server ................................................... 23
IIS, .NET, and ASP.NET User Preparation for AppXtender
Web.NET ................................................................................................. 23
Directory Permissions for the ASPNET/Network Service
Account ............................................................................................... 24
Installing ASPNET Scriptmaps to the Default Web Site ........................... 25
Installing ASPNET Scriptmaps to a Web Site Other than the
Default ................................................................................................ 26
AppXtender Web.NET Server Preparation Checklist ................................... 26
Configuring the Default SMTP Virtual Server for Use with
AppXtender Web.NET .......................................................................... 28
Upgrading AppXtender Web Access .................................................................. 29
Planning an AppXtender Web Upgrade ......................................................... 29
Upgrading Other System Components ....................................................... 29
Upgrading AppXtender Web Components ................................................. 29
Connectivity between Releases .................................................................. 30
AppXtender Web System Architecture Upgrade Considerations .................. 30
Supported Platform Upgrade Considerations ............................................. 30
Operating System Upgrade Considerations ............................................ 30
Upgrading AppXtender Web Server .............................................................. 31

Chapter 2 Configuring AppXtender Rendering Server ................................................. 33

Required AppXtender Rendering Server Configuration ...................................... 33

ApplicationXtender Web Access .NET Administrator’s Guide 3

Table of Contents

Configuring an AppXtender Rendering Server Login Account......................... 33

Configuring AppXtender Rendering Server Cache Settings ............................. 35
Optional AppXtender Rendering Server Configuration ....................................... 37
Configuring AppXtender Rendering Server Rendering Settings ....................... 37
Setting the Maximum Number of Concurrent Conversions ......................... 37
Configuring Image Conversion Settings ..................................................... 38
Configuring Image Conversion Format .................................................. 38
Configuring the Maximum Wait Time for Image Conversion
Completion .......................................................................................... 38
Configuring Foreign File Conversion Settings ............................................. 38
Enabling Foreign File HTML Conversion ............................................... 39
Configuring the Maximum Wait Time for Foreign File
Conversion Completion ........................................................................ 39
Configuring COLD/ERM Form Overlay Font Settings ................................. 39
Configuring AppXtender Rendering Server Cleanup Settings .......................... 40

Chapter 3 Using the AppXtender Web.NET Configuration Wizard ............................... 41

Introduction ..................................................................................................... 41
Starting the Wizard ........................................................................................... 42
Specifying Global Credentials............................................................................ 43
Configuring License Server Connections ............................................................ 44
Adding a License Server Connection .............................................................. 45
Managing the License Server List................................................................... 45
Configuring Data Sources ................................................................................. 46
Specifying Data Source Identification ............................................................. 48
Connecting to the Database ........................................................................... 48
Specifying Data Source Authentication .......................................................... 50
Specifying a License Server for the Data Source .............................................. 51
Selecting a Security Provider for the Data Source ............................................ 51
Managing the Data Source List ...................................................................... 52
Configuring Session Management ..................................................................... 53
Configuring Session Management Settings ..................................................... 54
Configuring IIS Security .................................................................................... 57
Configuring User Access ............................................................................... 57
Configuring Automatic Login ....................................................................... 58
Configuring E-mail ........................................................................................... 59
Configuring E-mail Settings .......................................................................... 60
Configuring AppXtender Rendering Server ........................................................ 62
Configuring AppXtender Rendering Server Authentication Account ............... 62
Selecting an AppXtender Rendering Server Data Source ................................. 64
Connecting to the AppXtender Rendering Server Database ............................. 65
Specifying the AppXtender Rendering Server Cache Path ............................... 66
Viewing the Configuration Summary ................................................................. 68
Validating Configurations ................................................................................. 69

Chapter 4 Configuring AppXtender Web Access Settings ........................................... 75

Understanding Required vs. Optional Settings ................................................... 75
Required AppXtender Web Access Server Configuration................................. 76
Optional AppXtender Web Access Server Configuration ................................. 76
Configuring AppXtender Web Access Setup Settings .......................................... 77
Configuring AppXtender Web Server Session Cache ....................................... 77
Configuring Session Data Management.......................................................... 78

4 ApplicationXtender Web Access .NET Administrator’s Guide

 Table of Contents

Configuring the AppXtender Web Server Global Authentication

Account ....................................................................................................... 79
Configuring AppXtender Web Access Security Settings....................................... 80
Configuring AppXtender Web File Type Map Settings ........................................ 81
Adding File Types ........................................................................................ 83
Modifying a File Type ................................................................................... 84
Deleting a File Type ...................................................................................... 85
Configuring E-Mail for AppXtender Web Access ................................................ 85
Designating an SMTP Server for E-Mail ......................................................... 86
Setting AppXtender Web Administrator E-Mail Information ........................... 87
Managing E-Mail Addresses ......................................................................... 88
Adding an E-mail Address ........................................................................ 89
Modifying an Existing E-Mail Address....................................................... 90
Deleting E-Mail Addresses ........................................................................ 91
Deleting an Individual E-Mail Address .................................................. 91
Deleting All Listed E-Mail Addresses..................................................... 92
Importing Addresses from a File ............................................................... 93
Exporting E-mail Addresses to a File.......................................................... 95
Sorting E-Mail Addresses .......................................................................... 95
Monitoring Configuration Updates .................................................................... 96
Types and Effect of Configuration Updates .................................................... 97
Configuring Client Download of JRE ................................................................. 98
Configuring Thumbnails ................................................................................... 99
Resizing Thumbnail Views ............................................................................ 99
Changing the Default Viewer for Document Thumbnails .............................. 100
Configuring AppXtender Web Logging ............................................................ 102

Chapter 5 Installing and Registering AppXtender Web Access Components ............ 103
Before Running Setup ..................................................................................... 103
Installing AppXtender Web Access Components .............................................. 104
Installing AppXtender Rendering Server ...................................................... 104
Installing AppXtender Web.NET Access Server ............................................ 109
Additional Web Server Configuration for Macintosh Clients...................... 115
Installing Client Components .......................................................................... 117
Preparing AppXtender Web Component Servers as Database Clients ................. 117
Preparing AppXtender Component Servers as IBM DB2
Database Clients ..................................................................................... 118
Installing IBM DB2 8.2 Client............................................................... 118
Configuring IBM DB2 8.2 Client .......................................................... 119
Preparing AppXtender Component Servers as Oracle Database
Clients ................................................................................................... 122
Installing Oracle Client ....................................................................... 122
Configuring Oracle Client ................................................................... 122
Configuring Net Manager ............................................................... 122
Configuring Net Configuration Assistant ......................................... 123
Preparing AppXtender Component Servers as Sybase SQL
Anywhere Database Clients .................................................................... 123
Installing Sybase Clients ..................................................................... 124
Creating an ODBC Data Source for Sybase SQL Anywhere ................... 124
Preparing AppXtender Component Servers as MySQL Database
Clients ................................................................................................... 127
Create an ODBC Data Source for MySQL ............................................. 128
Starting Registration of AppXtender Web Access Components .......................... 130
Starting Registration of other AppXtender Components ................................ 130

ApplicationXtender Web Access .NET Administrator’s Guide 5

Table of Contents

Locating a Data Source.................................................................................... 131

Locating a Microsoft SQL Server Data Source ........................................... 132
Locating an Oracle Data Source ............................................................... 134
Locating an IBM DB2 Data Source ........................................................... 136
Locating a MySQL Data Source ............................................................... 137
Locating a Sybase SQL Anywhere Data Source ......................................... 139
Completing Registration of AppXtender Web Access Components .................... 140
Completing Registration of Other AppXtender Components ......................... 140
Selecting a Component Type ................................................................... 141
Reviewing Permissions ........................................................................... 141
Entering Component Information ............................................................ 142
Specifying Web Service Settings ............................................................... 143
Configuring Database Access .................................................................. 145
Completing Registration ......................................................................... 146
Testing the AppXtender Components .............................................................. 147
Testing the AppXtender Web.NET Server ..................................................... 147
Testing the AppXtender Rendering Server.................................................... 147

Appendix A Managing AppXtender Web Access .......................................................... 149

Working with AppXtender Web Access Administrator...................................... 149
Accessing the AppXtender Web Access Administrator .................................. 150
Navigating the AppXtender Web Access Administrator ................................ 151
Managing Sessions ..................................................................................... 152
Viewing the Logged On Session List ........................................................ 152
Terminating Sessions .............................................................................. 153
Viewing License Server Information ........................................................ 153
Managing Job Queues ................................................................................. 154
Viewing Jobs .......................................................................................... 155
Cancelling Jobs ....................................................................................... 155
Managing Checked Out Documents............................................................. 156
Viewing Checked Out Documents ........................................................... 156
Releasing Checked Out Documents ......................................................... 156
Managing Locked Documents ..................................................................... 157
Viewing Locked Documents .................................................................... 158
Releasing Locked Documents .................................................................. 158
Managing Retention Hold Documents ......................................................... 158
Managing Annotation Security in AppXtender Web Access ............................... 159
Configuring Rubber Stamp Security............................................................. 159

Appendix B Managing User Profiles ............................................................................. 163

Introduction ................................................................................................... 163
Starting AppXtender User Profile Administrator .............................................. 164
AppXtender User Profile Administrator Toolbar Buttons .................................. 166
Editing User Profiles ....................................................................................... 167
Editing User Profile Settings ........................................................................ 167
Configuring Automatic E-mail Registration .................................................. 181
Exporting a Profile ...................................................................................... 182
Loading a User Profile for Editing................................................................ 183
Merging User Profiles ................................................................................. 184
Restoring Default Values ................................................................................. 185
Restoring Individual Profiles to Match the Default User Profile ..................... 186
Restoring All Profiles to Match the Default User Profile ................................ 186
Restoring All Profiles to Factory Defaults ..................................................... 186
Saving User Profile Setting Changes ................................................................ 186
Undoing User Profile Setting Changes ............................................................. 187

6 ApplicationXtender Web Access .NET Administrator’s Guide

 Table of Contents

Copying a Profile from One User to Other Users............................................... 187

Copying Profiles Using the Right-click Menus .............................................. 187
Copying Profiles Using the Copy Profile Dialog Box ..................................... 188

Appendix C Maintaining AppXtender Web Access Installations ................................... 191

Maintaining AppXtender Web Access .NET Server ........................................... 191
Repairing AppXtender Web.NET ................................................................. 191
Uninstalling AppXtender Web.NET ............................................................. 192
Maintaining AppXtender Rendering Server...................................................... 192
Repairing AppXtender Rendering Server ..................................................... 192
Uninstalling AppXtender Rendering Server ................................................. 193

Glossary ............................................................................................................................ 195

ApplicationXtender Web Access .NET Administrator’s Guide 7

Table of Contents

List of Figures

Figure 1. AppXtender Admin - Servers > Rendering Server Node .......................................... 34

Figure 2. AppXtender Admin Enter User Credentials Dialog Box .......................................... 34
Figure 3. AppXtender Rendering Server Cache Settings ........................................................ 36
Figure 4. AppXtender Admin Browse For Folder Dialog Box ................................................. 36
Figure 5. AppXtender Web.NET Configuration Wizard - Global Credentials
Configuration Page ........................................................................................... 43
Figure 6. AppXtender Web.NET Configuration Wizard - License Server
Configuration Page ........................................................................................... 44
Figure 7. AppXtender Web.NET Configuration Wizard - License Server
Connection Page ............................................................................................... 45
Figure 8. AppXtender Web.NET Configuration Wizard - License Server List Page .................. 46
Figure 9. AppXtender Web.NET Configuration Wizard - Data Source
Configuration Page ........................................................................................... 47
Figure 10. AppXtender Web.NET Configuration Wizard - Data Source Identification
Page ................................................................................................................ 48
Figure 11. AppXtender Web.NET Configuration Wizard - Data Source Link Page..................... 49
Figure 12. AppXtender Web.NET Configuration Wizard - Data Source
Authentication Page ......................................................................................... 50
Figure 13. AppXtender Web.NET Configuration Wizard - Data Source Licensing Page ............. 51
Figure 14. AppXtender Web.NET Configuration Wizard - Data Source Security
Provider Page ................................................................................................... 52
Figure 15. AppXtender Web.NET Configuration Wizard - Data Source List Page ...................... 53
Figure 16. AppXtender Web.NET Configuration Wizard - Session Management Page ............... 54
Figure 17. AppXtender Web.NET Configuration Wizard - Session Management
Path Page ......................................................................................................... 55
Figure 18. AppXtender Web.NET Configuration Wizard - Local Path Setup Dialog Box ............ 55
Figure 19. AppXtender Web.NET Configuration Wizard - Browse For Folder Dialog
Box .................................................................................................................. 56
Figure 20. AppXtender Web.NET Configuration Wizard - IIS Security Page ............................. 57
Figure 21. AppXtender Web.NET Configuration Wizard - User Access Page ............................ 58
Figure 22. AppXtender Web.NET Configuration Wizard - Automatic Login Page ..................... 59
Figure 23. AppXtender Web.NET Configuration Wizard - E-mail Configuration Page ............... 60
Figure 24. AppXtender Web.NET Configuration Wizard - E-mail Settings Page ........................ 61
Figure 25. AppXtender Web.NET Configuration Wizard - E-Mail Address Dialog Box .............. 61
Figure 26. AppXtender Web.NET Configuration Wizard - AppXtender Rendering
Server Configuration Page................................................................................. 62
Figure 27. AppXtender Web.NET Configuration Wizard - AppXtender Rendering
Server Authentication Account Page .................................................................. 63
Figure 28. AppXtender Web.NET Configuration Wizard - AppXtender Rendering
Server Data Source Page.................................................................................... 64

8 ApplicationXtender Web Access .NET Administrator’s Guide

 Table of Contents

Figure 29. AppXtender Web.NET Configuration Wizard - AppXtender Rendering

Server Data Link Page ....................................................................................... 65
Figure 30. AppXtender Web.NET Configuration Wizard - AppXtender Rendering
Server Cache Path Page ..................................................................................... 66
Figure 31. AppXtender Web.NET Configuration Wizard - UNC Path Setup Dialog Box ............ 67
Figure 32. AppXtender Web.NET Configuration Wizard - Browse For Folder Dialog
Box .................................................................................................................. 67
Figure 33. AppXtender Web.NET Configuration Wizard - Summary Page................................ 68
Figure 34. AppXtender Admin Validate Configurations Dialog Box ......................................... 69
Figure 35. AppXtender Admin - AppXtender Web > Setup Node ............................................ 77
Figure 36. AppXtender Admin - Local Path Setup Dialog Box ................................................. 78
Figure 37. AppXtender Admin - AppXtender Web Session Management ................................. 79
Figure 38. AppXtender Admin - AppXtender Web Global Credentials Account........................ 80
Figure 39. AppXtender Admin - Enter User Credentials Dialog Box ........................................ 80
Figure 40. AppXtender Admin - AppXtender Web > Security Node ......................................... 81
Figure 41. AppXtender Admin - AppXtender Web > File Type Map Node ................................ 83
Figure 42. AppXtender Admin - File Types Dialog Box ........................................................... 84
Figure 43. AppXtender Admin - AppXtender Web > File Type Map Node ................................ 84
Figure 44. AppXtender Admin - File Types Dialog Box ........................................................... 85
Figure 45. AppXtender Admin - AppXtender Web > Email > Setup Node ................................ 86
Figure 46. AppXtender Admin - AppXtender Web Email SMTP Server .................................... 86
Figure 47. AppXtender Admin - AppXtender Web > Email > Setup Node ................................ 87
Figure 48. AppXtender Admin - AppXtender Web Administrator Email .................................. 87
Figure 49. AppXtender Admin - AppXtender Web> Email> Setup Node .................................. 88
Figure 50. AppXtender Admin - Email Address Dialog Box .................................................... 88
Figure 51. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 89
Figure 52. AppXtender Admin - Email Address Dialog Box .................................................... 90
Figure 53. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 90
Figure 54. AppXtender Admin - Email Address Dialog Box .................................................... 91
Figure 55. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 92
Figure 56. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 93
Figure 57. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 94
Figure 58. AppXtender Admin - Import Address Book Dialog Box .......................................... 94
Figure 59. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 95
Figure 60. AppXtender Admin - AppXtender Web > Email > Addresses Node ......................... 96
Figure 61. Thumbnails Contact Sheet: Reordering and Resizing Document Pages..................... 99
Figure 62. Document Display View with Thumbnails View of Document Pages:
Silverlight viewer ........................................................................................... 101
Figure 63. Document Display View with Thumbnails View of Document Pages:
Java viewer .................................................................................................... 101
Figure 64. AppXtender Rendering Server Setup - Welcome Page ........................................... 105
Figure 65. AppXtender Rendering Server Setup - License Agreement Page ............................ 106
Figure 66. AppXtender Rendering Server Setup - Customer Information Page........................ 106
Figure 67. AppXtender Rendering Server Setup - Destination Folder Page ............................. 107
Figure 68. AppXtender Rendering Server Setup - Garbage Collection Page ............................ 107

ApplicationXtender Web Access .NET Administrator’s Guide 9

Table of Contents

Figure 69. AppXtender Rendering Server Setup - Ready to Install Page.................................. 108
Figure 70. AppXtender Rendering Server Setup - Installing Page ........................................... 108
Figure 71. AppXtender Rendering Server Setup - Installation Complete Page ......................... 109
Figure 72. AppXtender Web.NET Access Setup - Welcome Page ............................................ 110
Figure 73. AppXtender Web.NET Access Setup - License Agreement Page ............................. 111
Figure 74. AppXtender Web.NET Access Setup - Customer Information Page ........................ 111
Figure 75. AppXtender Web.NET Access Setup - Select Target Web Site Page ......................... 112
Figure 76. AppXtender Web.NET Access Setup - Destination Folder Page .............................. 113
Figure 77. AppXtender Web.NET Access Setup - Ready to Install Page .................................. 113
Figure 78. AppXtender Web.NET Access Setup - Installing System Page ................................ 114
Figure 79. AppXtender Web.NET Access Setup - Installation Complete Page ......................... 114
Figure 80. Server Properties dialog box ................................................................................ 115
Figure 81. MIME Types dialog box ...................................................................................... 116
Figure 82. MIME Type dialog box........................................................................................ 116
Figure 83. IBM DB2 Administrative Client - Configuration Assistant ..................................... 119
Figure 84. IBM DB2 Add Database Wizard - Select How You Want to Set Up a
Connection Page ............................................................................................. 120
Figure 85. IBM DB2 Add Database Wizard - Select a Database from the Network
Search Result Page .......................................................................................... 120
Figure 86. IBM DB2 Add Database Wizard - Specify a Nickname for the Database
Page .............................................................................................................. 121
Figure 87. IBM DB2 Add Database Wizard - Register This Database as a Data
Source Page .................................................................................................... 121
Figure 88. SQL Anywhere Studio 9 Install Wizard ................................................................ 124
Figure 89. Create New Data Source Dialog Box .................................................................... 125
Figure 90. ODBC Configuration Dialog Box - ODBC Tab ....................................................... 125
Figure 91. ODBC Configuration Dialog Box - Login Tab ........................................................ 126
Figure 92. ODBC Configuration Dialog Box - Database Tab ................................................... 126
Figure 93. ODBC Configuration Dialog Box - Network Tab ................................................... 127
Figure 94. Create New Data Source Dialog Box .................................................................... 128
Figure 95. Connector/ODBC Window - Login Tab ................................................................ 129
Figure 96. Connector/ODBC Window - Advanced Tab .......................................................... 129
Figure 97. AppXtender Component Registration - Data Source Configuration Page ................ 131
Figure 98. AppXtender Component Registration - Login Dialog Box ..................................... 132
Figure 99. Data Link Properties Dialog Box - Provider Tab .................................................... 133
Figure 100. Data Link Properties Dialog Box - Connection Tab ................................................ 134
Figure 101. Data Link Properties Dialog Box - Provider Tab .................................................... 135
Figure 102. Data Link Properties Dialog Box - Connection Tab ................................................ 135
Figure 103. Data Link Properties Dialog Box - Provider Tab .................................................... 136
Figure 104. Data Link Properties Dialog Box - Connection Tab ................................................ 137
Figure 105. Data Link Properties Dialog Box - Provider Tab .................................................... 138
Figure 106. Data Link Properties Dialog Box - Connection Tab ................................................ 138
Figure 107. Data Link Properties Dialog Box - Provider Tab .................................................... 139
Figure 108. Data Link Properties Dialog Box - Connection Tab ................................................ 140

10 ApplicationXtender Web Access .NET Administrator’s Guide

 Table of Contents

Figure 109. AppXtender Component Registration - Component Type Page .............................. 141
Figure 110. AppXtender Component Registration - Review Permissions Dialog Box................. 142
Figure 111. AppXtender Component Registration - Component Information Page ................... 143
Figure 112. AppXtender Component Registration - Web Service Configuration Page ................ 144
Figure 113. AppXtender Component Registration - Configure Database Page .......................... 146
Figure 114. AppXtender Web Login Page .............................................................................. 150
Figure 115. AppXtender Web Access Administrator Toolbar ................................................... 151
Figure 116. Session List Page - Logged On Session List ........................................................... 152
Figure 117. Session List Page - License Server Information ...................................................... 154
Figure 118. Job Queue List .................................................................................................... 154
Figure 119. Job Queue and Job Element Lists ......................................................................... 155
Figure 120. Checked Out Document List Page........................................................................ 156
Figure 121. Locked Document List ........................................................................................ 157
Figure 122. Data Source Selection Dialog Box......................................................................... 165
Figure 123. AppXtender User Profile Administrator Window ................................................. 166
Figure 124. AppXtender User Profile Administrator Toolbar ................................................... 166
Figure 125. Email Auto Registration Dialog Box ..................................................................... 182
Figure 126. Export User Profile Dialog Box ............................................................................ 183
Figure 127. Load User Profile Dialog Box............................................................................... 184
Figure 128. Merge Profile Data Dialog Box ............................................................................ 185
Figure 129. Copy Profile Dialog Box ...................................................................................... 188

ApplicationXtender Web Access .NET Administrator’s Guide 11

Table of Contents

List of Tables

Table 1. Required Directory Permissions for ASPNET/Network Service Accounts

on AppXtender Web.NET Server ....................................................................... 25
Table 2. Cleanup Options .................................................................................................. 40
Table 3. Aspects of the AppXtender Web.NET Configuration Wizard ................................... 42
Table 4. Suggestions for Each Possible Warning .................................................................. 70
Table 5. Configuration Monitor Restart Modes .................................................................... 97
Table 6. Types and Effect of Configuration Updates ............................................................ 97
Table 7. Web Access Client Component MSI File Names .................................................... 117
Table 8. Web Service Configuration Properties .................................................................. 144
Table 9. Web Access Administrator Toolbar Options ......................................................... 151
Table 10. Basic Session Information .................................................................................... 153
Table 11. Rubber Stamp Application Editable Index Fields .................................................. 160
Table 12. Setting Difference Indicators ............................................................................... 166
Table 13. AppXtender User Profile Administrator Toolbar Buttons ...................................... 167
Table 14. User Profile Settings ........................................................................................... 168

12 ApplicationXtender Web Access .NET Administrator’s Guide

 Preface

This document provides instructions on how to install, configure, and administer the
ApplicationXtender (AppXtender) Web Access .NET™ (Web.NET) software. For detailed instructions
on how to use AppXtender Web, refer to the ApplicationXtender Web Access User’s Guide and the
program’s Online Help.
As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC
periodically releases revisions of its hardware and software. Therefore, some functions described in this
document may not be supported by all versions of the software or hardware currently in use. For the most
up-to-date information on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this document, please contact
your EMC representative.

Audience
The information in this document is intended for system administrators who are responsible for
installing software and maintaining the servers and clients on a network. Operators who monitor the
daily backups may also find this manual useful.

Related Documentation
Post-release information is contained in the Release Notes for this product. This document is available
at http://Powerlink.EMC.com. Refer to the web site periodically to view the latest Release Notes.
Related documents include:
• ApplicationXtender Web Access User’s Guide
• ApplicationXtender Web Access Administrator’s Quick Reference
• ApplicationXtender Web Access User’s Quick Reference
AppXtender Web is one module in the AppXtender Content Management suite. The following is a
list of documentation for related products that may be useful when working with AppXtender Web:
• ApplicationXtender Core Components Administrator’s Guide
• ApplicationXtender Administrator’s Quick Reference
All documents are in Adobe Acrobat Portable Document Format (PDF), and can be viewed by
downloading and installing the Adobe Acrobat Reader. The Reader is available from Adobe at

ApplicationXtender Web Access .NET Administrator’s Guide 13

Preface

www.adobe.com. To install and use the Reader on the preferred platform, refer to the instructions on
the Adobe web site.

Where to get help

EMC support, product, and licensing information can be obtained as follows.
Product information — For documentation, release notes, software updates, or for information about
EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at
http://Powerlink.EMC.com.
Technical support — For technical support, go to EMC Customer Service on Powerlink. To open
a service request through Powerlink, you must have a valid support agreement. Please contact
your EMC sales representative for details about obtaining a valid support agreement or to answer
any questions about your account.

14 ApplicationXtender Web Access .NET Administrator’s Guide

 Chapter 1
Planning AppXtender Web Access
Deployment

To make the AppXtender Web Access deployment process more efficient, you can use the information
in this section to plan your AppXtender Web system architecture before you install and configure
AppXtender Web software. The topics in this section address areas of the deployment to consider
when planning the installation of your system. For more information, see the following topics:
Note: For information on AppXtender components, features, architecture, best practices, and system
planning, refer to the ApplicationXtender Concepts Guide.
• AppXtender Web Access Deployment Overview, page 15
• Upgrading AppXtender Web Access, page 29

AppXtender Web Access Deployment Overview

AppXtender Web is closely integrated with other components of the AppXtender system, and
depends on those components in several ways. For this reason, prior to installing the AppXtender
Web Server and Rendering Server software, you must install ApplicationXtender Administrator
(AppXtender Admin) and configure AppXtender Web Server and Rendering Server settings within
AppXtender Admin. You also need to install AppXtender components and configure settings
in those components.
There should be only one AppXtender Admin per data source group. However, you can install
multiple AppXtender Rendering Servers to perform file rendering services for your AppXtender
Web Server.
AppXtender Web supports multiple operating system and web server platforms through the
ApplicationXtender Web Access .NET (AppXtender Web.NET) deployment model.
AppXtender Web is also supported with Secure Socket Layer (SSL). For information on configuring
SSL with IIS (for AppXtender Web.NET), refer to Windows documentation. Prior to using SSL
with an AppXtender Web website, you must connect to the web server using SSL to confirm that
SSL is correctly configured.
The Windows operating system uses an ASP.NET application, which runs on Microsoft Internet
Information Server (IIS), to support AppXtender Web.NET.

ApplicationXtender Web Access .NET Administrator’s Guide 15

Planning AppXtender Web Access Deployment

To set up your AppXtender Web.NET system:

1. Prepare the ApplicationXtender content management environment. For more information, see
Preparing the AppXtender Content Management Environment, page 16.
Test the AppXtender content management environment. For instructions, see Testing the
AppXtender Content Management Environment, page 21.
2. Create an authentication account on the AppXtender Web.NET Server computer and the
Rendering Server computer. For details, see Configuring Authentication Accounts, page 21.
Test each authentication account’s access to paths. For instructions, see Testing Authentication
Account Access to Paths, page 22.
3. If you need to support AppXtender Web Thin Client, thumbnail, or email rendering, prepare the
AppXtender Rendering Server computer. For more information, see Preparing the AppXtender
Rendering Server, page 22.
4. Prepare the AppXtender Web.NET Server computer. For more information, see Preparing the
AppXtender Web.NET Server, page 23.
5. Install AppXtender Rendering Server components on the AppXtender Rendering Server
computer(s). For more information, see Installing AppXtender Rendering Server, page 104.
6. Install AppXtender Web.NET Server components on the AppXtender Web.NET Server computer.
For more information, see Installing AppXtender Web.NET Access Server, page 109.
7. Run the AppXtender Component Registration wizard on each AppXtender Rendering Server
computer to register the AppXtender Rendering Server with the database. For more information,
see Starting Registration of other AppXtender Components, page 130.
8. Run the AppXtender Component Registration wizard on the AppXtender Web.NET Server
computer to register the AppXtender Web.NET Server with the database. For more information,
see Starting Registration of other AppXtender Components, page 130.
9. Test AppXtender Web.NET Server login to verify that AppXtender Web.NET has been correctly
installed, configured, and registered. For more information, see Testing the AppXtender
Components, page 147.

Preparing the AppXtender Content Management

Environment
Before running the AppXtender Web.NET Server setup wizard or running the AppXtender Rendering
Server setup wizard, be sure that the items listed in this section are in place within your network.
The following must be in place:
• A License Server that is network-accessible to the AppXtender Web Server and contains
appropriate licenses for anticipated usage on your system.
For more information on License Server installation and configuration, refer to the "Licensing
AppXtender Products" chapter of the ApplicationXtender Core Components Administrator’s Guide.

16 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

For a summary of available licensing modes for AppXtender Web, refer to Licensing AppXtender
Web Access, page 19.
• A fully configured AppXtender Admin 6.5 installation.
For more information on installing AppXtender Admin and configuring environment settings
for the entire content management system, refer to the ApplicationXtender Core Components
Administrator’s Guide.
Note: For each data source that will be used with AppXtender Web, check the network transport
setting of each License Server and DiskXtender connection. If any of these connections are using
Named Pipes, change that connection to another network transport setting. Named Pipes is
not supported for AppXtender Web.
• A fully configured ApplicationXtender Application Generator (AppXtender AppGen) 6.5
installation. AppXtender 6.5 applications and security settings must be configured through
AppXtender AppGen in the database or databases for the data source group for which you want
to provide AppXtender Web functionality.
For more information, refer to the ApplicationXtender Core Components Administrator’s Guide.
• AppXtender Web Access settings revealed in AppXtender Admin. For instructions, see Displaying
AppXtender Web Access Settings in AppXtender Admin, page 17.
• At least one supported database that is network-accessible to the AppXtender Web Server,
configured as a data source through AppXtender Admin.
For more information on supported databases and database configuration, refer to the
AppXtender Data Sources chapter of the ApplicationXtender Core Components Administrator’s Guide.
• A storage location for AppXtender documents.
If DiskXtender (DX) or Centera will be used for document storage, connectivity must be
configured in AppXtender Admin. For more information on configuring document storage,
refer to the Using a Document Storage Server chapter of theApplicationXtender Core Components
Administrator’s Guide.
• If you are using dual write paths with your AppXtender Web deployment, refer to the Dual
Write Paths section of the ApplicationXtender Concepts Guide for a discussion of considerations
in setting up dual write paths. Verify that your write path configuration complies with the
recommendations provided there for systems that include AppXtender Web Access.

Displaying AppXtender Web Access Settings in AppXtender Admin

The following sections describe how to reveal AppXtender Web Access settings in AppXtender
Admin:
• Starting AppXtender Administrator, page 18
• Selecting Data Sources, page 18
• Showing the AppXtender Web Node, page 19

ApplicationXtender Web Access .NET Administrator’s Guide 17

Planning AppXtender Web Access Deployment

Starting AppXtender Administrator

AppXtender Web settings are configured through the AppXtender Web subnodes in AppXtender
Admin.

To start AppXtender Admin:

1. From the Windows Start menu, select Programs -> ApplicationXtender -> Administrator. A
login dialog box appears.
2. In the User Name text box, type an administrative user name.
3. In the Password text box, type the password for the user name you entered.
Note: The first time you log into AppXtender Admin, the password for the user name sysop is
xscm. Once you have logged in for the first time, using the user name sysop and the password
xscm, you can (and should) use AppXtender AppGen to change the password to something
more secure.
4. Click Login. AppXtenderAdmin appears.

Selecting Data Sources

AppXtender Admin allows you to set a data source as default. This setting determines which data
source is selected by default in the AppXtender Web login page.
If you have multiple data sources configured in AppXtender Admin, you can also designate multiple
data sources to be viewed within AppXtender Web. This allows users to view applications from all
applicable data sources during a single AppXtender Web session. In this way, users can access
applications located on many different data sources during a single AppXtender Web session,
provided they have security rights to access those data sources.
For more information, refer to:
• Specifying a Default Data Source, page 18
• Specifying Multiple Data Sources, page 19
For information on data source creation and configuration, refer to your AppXtender system
administrator or refer to the AppXtender Data Sources chapter of the ApplicationXtender Core
Components Administrator’s Guide.
Users can log into only those data sources for which they have a user account. For more information
on creating a user account in a data source, consult your system administrator or refer to the
"Implementing Security" chapter of the ApplicationXtender Core Components Administrator’s Guide.

Specifying a Default Data Source

AppXtender Admin allows you to set a data source as default. This setting determines which data
source is selected by default in the AppXtender Web login page.

To set a data source as default:

1. In the AppXtender Admin tree, expand the Environment node and select Data Sources.

18 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

2. Select the data source that you want to set as default.

3. Click Default. A white check mark within a black background ( ) should appear next to it.
4. From the AppXtender Admin File menu, select Save Changes.

Specifying Multiple Data Sources

If you have multiple data sources configured in AppXtender Admin, you can designate multiple
data sources to be viewed within AppXtender Web. This allows users to view applications from all
applicable data sources during a single AppXtender Web session.

To configure multiple data sources to be viewed in AppXtender Web:

1. In the AppXtender Admin tree, expand the Environment node and select Data Sources.
2. Select the data source that you want to appear within AppXtender Web (in addition to the default
data source) and click Show. A black check mark with no background ( ) should appear next
to it.
3. Repeat the previous step for each data source you want to be accessible within AppXtender Web.
4. From the AppXtender Admin File menu, select Save Changes.

Showing the AppXtender Web Node

By default, AppXtender Admin displays configuration interfaces for both AppXtender Desktop and
AppXtender Web Access. If the AppXtender Web node has been hidden, you can show it.

To show the AppXtender Web node:

1. In AppXtender Admin, from the Tools menu, select Options. The Options dialog box appears.
2. Under Applications Installed, select AppXtender Web NET.
3. Click OK. The AppXtender Admin tree reappears with the AppXtender Web node.

Licensing AppXtender Web Access

The AppXtender content management products use the License Server to monitor software license
compliance.
Before AppXtender Web Access can be used, a license key for the software must be registered with
the License Server. License information can be updated using the License Server Administrator.

License Server

The License Server is used by workstations to validate AppXtender content management product
licensing options and to monitor users on the system.

ApplicationXtender Web Access .NET Administrator’s Guide 19

Planning AppXtender Web Access Deployment

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 AppGen. However, you must be sure that the AppXtender Web serial number has
been entered into the License Server.
For more information about the License Server, refer to the Licensing AppXtender Products chapter
of the ApplicationXtender Core Components Administrator’s Guide.

License Groups

License groups can be configured for AppXtender Desktop, Web Access, and Reports Management.
The creation of license groups allows licenses to be applied to a group or groups of users as opposed
to being applied on an individual basis. License groups are created in AppXtender Admin. For more
information about configuring license groups, refer to the Adding a License Group section of the
ApplicationXtender Core Components Administrator’s Guide.

Types of Licenses

You can purchase the following types of AppXtender 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 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 Desktop Full-Text Licenses: When a user enables the Enable FTS check box on the
login page, they are using an AppXtender Desktop Full-text license. This license is actually drawn
from the AppXtender Desktop license pool. Verity for AppXtender full-text search licenses are
included in AppXtender Desktop licensing.

AppXtender Public Access Licensing

AppXtender Public Access Licensing allows a larger number of clients to connect to the AppXtender
Web server at a lower cost than full licensing. This is useful if you have many remote users who are
connecting to the AppXtender Web system to retrieve information. Users or groups who have this
designation (the AppXtender Web PAL User security privilege assigned from AppXtender AppGen)
can use AppXtender Web only in read-only, Thin Client mode with minimal privileges. Users with
the AppXtender Web PAL privilege can access AppXtender applications using AppXtender Web only
– they cannot log into AppXtender Document Manager.

AppXtender Web Services Standalone vs. Integrated Mode

AppXtender Web Services is available in standalone or integrated mode:

• In standalone mode, AppXtender Web Services is installed as a separate application, provides
only SOAP/XML interface functionality, and has no document display functionality. In this mode,

20 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

AppXtender Web Services can be configured to use an AppXtender Web Services license or an
AppXtender Desktop license. Upon user login, the specified license type is decremented.
• In integrated mode, the client application can use the AppXtender Web.NET document view page
for document display based on the proper URL to the document view page obtained through the
AppXtender Web Services API call. In this case, AppXtender Web.NET is sharing the same session
that was established during login to AppXtender Web Services.
Upon user login, the AppXtender Web Services software checks for the availability of at least one
AppXtender Web Services license and an AppXtender Web (or Desktop) license is decremented. To
implement this mode, you must use the AppXtender Web.NET installation wizard (rather than the
AppXtender Web Services installation wizard) to install AppXtender Web Services.

Testing the AppXtender Content Management Environment

Test the AppXtender content management environment by creating and retrieving documents from
an AppXtender Desktop workstation, with the SYSOP user and with other users. If you have any
difficulty logging in or performing tasks on the AppXtender Desktop workstation, check each element
of the AppXtender content management environment again (as listed in Preparing the AppXtender
Content Management Environment, page 16) and resolve any problems before continuing with
AppXtender Web configuration. For detailed instructions, refer to the following guides:
• ApplicationXtender Concepts Guide
• ApplicationXtender Core Components Administrator’s Guide
• ApplicationXtender Desktop Installation Guide
• ApplicationXtender Document Manager User’s Guide

Configuring Authentication Accounts

On each of the computers intended for the AppXtender Web Server, Rendering Server, or Web
Services, you must create an authentication account. If any of the system resources are on computers
remote to these computers, create appropriate authentication accounts configured as Domain users
for access to those resources.

To configure authentication accounts:

1. Create one or more user accounts to be used as authentication accounts. For information on the
advanced rights required, refer to the Accounts and Rights Required for Resource Authentication
Accounts section of the ApplicationXtender Concepts Guide.
2. Specify each authentication account in AppXtender Admin. For information about the credential
settings in AppXtender Admin, refer to the About Configuring Resource Authentication
Credentials section of the ApplicationXtender Concepts Guide.
3. Test each authentication account. For instructions, see Testing Authentication Account Access to
Paths, page 22.

ApplicationXtender Web Access .NET Administrator’s Guide 21

Planning AppXtender Web Access Deployment

Testing Authentication Account Access to Paths

To test an account’s access to paths before installation, repeat the following steps on each of the
computers intended for the AppXtender Web Server, Rendering Server, and AppXtender Web
Services.

To test an account’s access to paths:

1. Log in using the account that you want to test.
2. Create a test file and a folder on the path that you want to test, such as a cache path or write path.
3. Delete the test file and folder.
The account that you are testing should be able to perform all of these steps. If the account that you
are using fails this test, make sure that the account has been properly configured. For details, see
Configuring Authentication Accounts, page 21.

Preparing the AppXtender Rendering Server

Refer to the following topics for information on preparing the AppXtender Rendering Server:
• AppXtender Rendering Server Requirements, page 22
• AppXtender Rendering Server Computer Preparation Checklist, page 22

AppXtender Rendering Server Requirements

The AppXtender Rendering Server must meet the hardware and software requirements listed in the
ApplicationXtender Web Access Release Notes. Each AppXtender Admin data source group can have
multiple AppXtender Rendering Server(s), but only one AppXtender Rendering Server can perform
garbage collection for the rendering cache for the data source group.

AppXtender Rendering Server Computer Preparation Checklist

Before running the AppXtender Rendering Server setup wizard and running AppXtender Component
Registration wizard to register the AppXtender Rendering Server with AppXtender Admin, be
sure that the following are in place on the computer or computers to be used as the AppXtender
Rendering Server or Rendering Servers:
• The server is running a supported operating system, as listed in the ApplicationXtender Web
Access Release Notes.

Caution: If you plan to install Windows Server 2008 on the AppXtender Rendering Server
computer, you must install the Web Server (IIS) role including the IIS 6.0 Scripting Tools role

22 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

service using the Windows 2008 Server Manager. Otherwise, the AppXtender Rendering
Server setup program will fail.

• The volume area that contains the AppXtender Rendering Server cache should not be compressed.
• The account used to install AppXtender Rendering Server must be a member of the local
Administrators group on the computer where the install is performed.
• The account configured for use by the AppXtender Rendering Server must have the appropriate
permissions detailed in the Accounts and Rights Required for Resource Authentication Accounts
section of the ApplicationXtender Concepts Guide.
• If an earlier release of AppXtender Rendering Server is installed, uninstall that release. For more
details, see Planning an AppXtender Web Upgrade, page 29.
• Preparatory steps may need to be taken to install and configure client access components to allow
each AppXtender Rendering Server access to a database within the data source group. For more
information, see Preparing AppXtender Web Component Servers as Database Clients, page 117.
• Prior to installing and registering AppXtender Rendering Server, configure AppXtender
Rendering Server settings in AppXtender Admin as described in Configuring AppXtender
Rendering Server Rendering Settings, page 37.

Preparing the AppXtender Web.NET Server

Refer to the ApplicationXtender Web Access Release Notes for specific AppXtender Web.NET Server
hardware and software requirements. The AppXtender Web Server must also meet the requirements
discussed in the following topics:
• IIS, .NET, and ASP.NET User Preparation for AppXtender Web.NET, page 23
• AppXtender Web.NET Server Preparation Checklist, page 26
Note: Each AppXtender Admin data source group can have only one AppXtender Web server.
Note: EMC recommends configuring the AppXtender Web server to support the overflow of events
in the operating system event log. Refer to the server operating system Help for information on
configuring event logs.

IIS, .NET, and ASP.NET User Preparation for AppXtender Web.NET

Prepare IIS, the .NET Framework, and the ASP.NET user for AppXtender Web.NET.
• If you are using Windows, IIS is required. Make sure that IIS is selected during the Windows
installation process. The server operating system must support the version of IIS installed on
the server.

Caution: If you plan to install Windows Server 2008 on the AppXtender Web.NET Server
computer, you must install the Web Server (IIS) role including the IIS 6.0 Scripting Tools role

ApplicationXtender Web Access .NET Administrator’s Guide 23

Planning AppXtender Web Access Deployment

service using the Windows 2008 Server Manager. Otherwise, the AppXtender Web.NET
setup program will be unable to detect the default web site and installation will fail.

• The .NET framework must be installed on the AppXtender Web.NET Server computer. Make sure
that the .NET framework is selected during the Windows installation process.
• If you have already installed the Windows operating system on the AppXtender Web.NET Server,
update the installation with IIS, the .NET framework, and the ASPNET user at the same time.
— If you update the installation with the .NET framework before installing IIS or the ASPNET
user, you must delete the ASPNET user, then run aspnet_regiis -i through the command
line on the AppXtender AppXtender Web.NET Server once you install IIS and the ASPNET
user. For more information, see Installing ASPNET Scriptmaps to the Default Web Site, page 25.
If the ASPNET scriptmaps are not installed on the web site where your AppXtender Web
content is installed (typically the default web site), users will not be able to log into your
AppXtender Web Access web site.
— If you have already updated the installation with IIS but not .NET framework, you must delete
ASPNET user account before installing .NET framework. Installing the .NET framework
automatically creates an ASPNET user, so you do not need to run aspnet_regiis in this situation.
— If you plan to use AppXtender Web.NET on a web site other than the Default Web
Site, you need to install ASPNET scriptmaps to that web site. You do this by running
aspnet_regiis -i path (where path refers to the root path of the web site application,
such as W3SVC/2/ROOT, where W3SVC is a constant referring to the IIS web service, 2 is
the Web Site Number, and ROOT is the root directory designation) through the command
line on the AppXtender Web.NET Server. You can use the findweb.vbs script in your
inetpub\AdminScripts directory to identify the Web Site Number. The aspnet_regiis
-i path command should be run once you install IIS and the ASPNET user. For more
information, see Installing ASPNET Scriptmaps to a Web Site Other than the Default, page 26.
If the ASPNET scriptmaps are not installed on the web site where your AppXtender Web
content is installed, users will not be able to log into your AppXtender Web Access web site.
• The Network Service account must have access to certain .NET Framework operating directories
and temporary directories. For more information on verifying that access, see Directory
Permissions for the ASPNET/Network Service Account, page 24.
• You should be able to connect to the default IIS web site to verify that your IIS server is running
correctly prior to installing AppXtender Web.NET. (For example, try entering the following URL
in your browser Address text box: http://localhost/iisstart.htm. A message may appear indicating
that the site is currently under construction, but this message verifies that your IIS server is
running on the local computer.) For instructions, refer to your IIS documentation.

Directory Permissions for the ASPNET/Network Service Account

When a AppXtender Web.NET client loads a page for the first time, ASP .NET invokes a just-in-time
compiler to compile that page and store it in the cache. From there, all subsequent hits to that page
are retrieved from a cache located in the following directory:
%windir%\Microsoft.NET\Framework\vx.x\Temporary ASP.NET Files

24 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

where vx.x is the version of Framework installed on the machine. If the Network Service account
does not have appropriate permissions to directories used during the compilation and caching
process, the compilation process fails.
If you encounter either of the following errors when connecting to the AppXtender Web.NET server,
check directory permissions:
• Access to the path "C:\WINDOWS\Microsoft.NET Framework\vx.x\Temporary
ASP.NET Files\sitecontent\...." is denied
• CS0016: Could not write to output file "c:\WINDOWS\Microsoft.NET
Framework\vx.x\Temporary ASP.NET Files\sitecontent\...." -- "Access is
denied."
To check permissions for compilation and caching directories on the AppXtender Web.NET server:
• Make sure the Network Service account has the following permissions for the following
directories:

Table 1. Required Directory Permissions for ASPNET/Network Service Accounts on AppXtender

Web.NET Server

Directory Required Permission

%windir%\Microsoft.NET\Frame- Read
work\vx.x\
%windir%\Microsoft.NET\Frame- Read\Write
work\vx.x\ Temporary ASP.NET Files
%tmp% and/or %temp% directories as set in the Read\Write
computer System Variables

Installing ASPNET Scriptmaps to the Default Web Site

Microsoft Internet Information Services (IIS) are installed by default when you install Windows.
However, since the option to install IIS can be disabled during Windows installation, you may need
to install IIS separately prior to using AppXtender Web.NET.
If you install IIS after installing the Microsoft .NET framework, you need to run the aspnet_regiis
utility to install ASPNET scriptmaps to the default IIS web site.

Caution: If the ASPNET scriptmaps are not installed on the web site where your AppXtender
Web content is installed (typically the default web site), users will not be able to log into your
AppXtender Web Access web site.

To install ASPNET scriptmaps to the default web site using aspnet_regiis:

1. Select Start> Run and type cmd to open the Command Prompt.
2. Change directories to the directory where the Microsoft .NET Framework is installed. For
example, if the .NET Framework is installed in C:\WINNT\Microsoft.NET\Framework\vx.x,
enter the command
cd C:\WINNT\Microsoft.NET\Framework\vx.x.

ApplicationXtender Web Access .NET Administrator’s Guide 25

Planning AppXtender Web Access Deployment

3. At the command prompt, type aspnet_regiis -i -enable to install ASPNET scriptmaps to

the default web site and enable the scriptmaps.

Installing ASPNET Scriptmaps to a Web Site Other than the Default

When you install the Microsoft .NET Framework to a computer where Internet Information Services
(IIS) are installed, the ASPNET scriptmaps are installed to the IIS default web site. However, if you
plan to install AppXtender Web.NET on a web site other than the default web site, you need to
make sure that the ASPNET scriptmaps are installed on that web site as well. In this scenario, you
need to run the aspnet_regiis utility to install the ASPNET scriptmaps to the IIS web site you plan
to use with AppXtender Web.NET.

Caution: If ASPNET scriptmaps are not installed on the web site where your AppXtender Web
content is installed, users will not be able to log into your AppXtender Web Access web site.

To install ASPNET scriptmaps to a specific web site using aspnet_regiis:

1. Select Start> Run and type cmd to open the Command Prompt.
2. Change directories to the inetpub subdirectory where IIS administrative scripts are located. For
example, if the administrative scripts are located in C:\Inetpub\AdminScripts, enter the
command cd C:\Inetpub\AdminScripts.
3. At the command prompt, enter findweb -computername "Web Site Description"
(where computername is the name of the computer where IIS is installed and "Web Site
Description" is the Web Site Description from the Web Site tab of the web site’s properties
in IIS).
4. Click OK to close each message box that appears providing information about that web site’s
properties, noting the Web Site Number displayed in the first message box.
5. Change directories to the directory where the Microsoft .NET Framework is installed. For example,
if the .NET Framework is installed in C:\WINNT\Microsoft.NET\Framework\vx.x, enter
the command cd\, then the command cd C:\WINNT\Microsoft.NET\Framework\vx.x.
6. At the command prompt, enter aspnet_regiis -i path (where path is the root application
path for the web site) to install ASPNET files to the default web site.
Note: For more information on use of the aspnet_regiis utility, refer to the Microsoft
documentation for IIS.

AppXtender Web.NET Server Preparation Checklist

Before running the AppXtender Web.NET Server setup wizard and running AppXtender Component
Registration wizard to register the AppXtender Web.NET Server with AppXtender Admin, use this
checklist be sure that the necessary components are in place on your AppXtender Web.NET Server
computer:
• The server is running a supported operating system, as listed in the ApplicationXtender Web
Access Release Notes.

26 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

Caution: If you plan to install Windows Server 2008 on the AppXtender Web.NET Server
computer, you must install the Web Server (IIS) role including the IIS 6.0 Scripting Tools role
service using the Windows 2008 Server Manager. Otherwise, the AppXtender Web.NET
setup program will be unable to detect the default web site and installation will fail.

— Prepare IIS, the .NET Framework, and the ASP.NET user. For details, see IIS, .NET, and
ASP.NET User Preparation for AppXtender Web.NET, page 23.
— A Default SMTP Virtual Server should be installed and running if you intend to use
AppXtender Web electronic mail functionality, and the Default SMTP Virtual Server must be
configured to relay messages for the AppXtender Web.NET Server. For more information, see
Configuring the Default SMTP Virtual Server for Use with AppXtender Web.NET, page 28.
— You may also choose to install the Windows Indexing Service, which allows for client-side
full-text searches of your web site, and the Windows Script Debugger, which assists in
troubleshooting and debugging.
• To provide a more secure environment, the volume that will contain AppXtender Web Access
content should be formatted using NTFS (rather than the FAT or FAT-32 file system). In addition,
the volume area that contains the AppXtender Web application content (typically C:\INETPUB)
should not be compressed.
• If you wish to install AppXtender Web.NET to a web site other than the default, it must be
configured through IIS prior to running setup. Refer to IIS Help for information on how to
perform this function.
— You must install ASPNET scriptmaps on the web site you plan to use. For more information on
installing ASPNET scriptmaps on a non-default web site, see Installing ASPNET Scriptmaps to
a Web Site Other than the Default, page 26.
— The use of headers that map the non-default website to appear as a default port 80 site is
not supported.
• If using Microsoft FrontPage, disable the personal Web server.
• The account used to install AppXtender Web.NET must be a member of the local Administrators
group on the computer where the install is performed.
• The ASPNET user and any authentication accounts used by AppXtender Web resources must
have the appropriate permissions detailed in the Accounts and Rights Required for Resource
Authentication Accounts section of the ApplicationXtender Concepts Guide.
• Resource authentication credentials configured in AppXtender Administrator. Refer to the
ApplicationXtender Concepts Guide for more information.
• AppXtender Web Access settings in the AppXtender database or databases, configured through
AppXtender Admin.
These settings must be configured before you install AppXtender Web.NET on the AppXtender
Web Server computer and register it as a system component. For more information on configuring
AppXtender Web settings, see Chapter 4, Configuring AppXtender Web Access Settings.
• If you plan to use digital signatures with AppXtender Web.NET, install the certificate you want to
use to sign documents in the local computer certificate repository on the AppXtender Web Server.

ApplicationXtender Web Access .NET Administrator’s Guide 27

Planning AppXtender Web Access Deployment

This certificate should match the certificate installed on any AppXtender computer that signs
documents also available to AppXtender Web clients.
• If an earlier release of AppXtender Web Access is installed, uninstall that release. For more details,
see Planning an AppXtender Web Upgrade, page 29.
• Prior to installing and registering AppXtender Web.NET Server, configure AppXtender Web
settings in AppXtender Admin as described in Chapter 4, Configuring AppXtender Web Access
Settings.
• Preparatory steps may need to be taken to install and configure client access components to allow
the AppXtender Web.NET Server access to a database within the data source group. For more
information, see Preparing AppXtender Web Component Servers as Database Clients, page 117.

Configuring the Default SMTP Virtual Server for Use with AppXtender Web.NET

If you will be using email features in AppXtender Web.NET, you need to permit the AppXtender
Web Server to relay through an SMTP server. For AppXtender Web.NET deployments, the Default
SMTP Virtual Server in Internet Information Services can be set to relay for the AppXtender Web.NET
Server. By default, the Only the List Below option is enabled in the Relay Restrictions settings and the
list of servers which can relay through the Virtual Server is blank. By default, therefore, no computers
are allowed to relay through the Virtual Server. To use email features through AppXtender Web,
you must change that setting to enable AppXtender Web Server relay through the Default SMTP
Virtual Server.

To configure the default SMTP Virtual Server for use with AppXtender Web.NET:
1. Open Internet Information Services on the AppXtender Web.NET Server.
2. Right-click the Default SMTP Virtual Server and select Properties. The Default Virtual Server
Properties dialog box appears.
3. Select the Access tab.
4. Select the Relay button under Relay Restrictions. The Relay Restrictions dialog box appears.
5. To enable relay for your AppXtender Web server, you have two choices:
• Leave the default of Only the List Below in place and add the AppXtender Web Server IP
address to the list to relay messages for the AppXtender Web Server only.
• Select All except the list below and do not add the AppXtender Web Server IP address to
the list.
6. Select OK in the Relay Restrictions dialog box.
7. Select Apply in the Default Virtual Server Properties dialog box, then select OK to close the
dialog box.
Note: If you do not apply the changes prior to selecting OK you will need to restart the Default
SMTP Virtual Server.
8. Reload the page.
Note: For more information on configuration of the Default SMTP Virtual Server, refer to the
Microsoft documentation for IIS.

28 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

Upgrading AppXtender Web Access

The following topics explain how to upgrade to the current version of AppXtender Web Access:
• Planning an AppXtender Web Upgrade, page 29
• Upgrading AppXtender Web Server, page 31

Planning an AppXtender Web Upgrade

After upgrading the AppXtender database, do not connect to the database with an older version
of AppXtender.
For more information, refer to the following topics:
• Upgrading Other System Components, page 29
• Upgrading AppXtender Web Components, page 29
• Connectivity between Releases, page 30
• AppXtender Web System Architecture Upgrade Considerations, page 30
• Supported Platform Upgrade Considerations, page 30

Upgrading Other System Components

Because AppXtender Web shares a database and document repository with AppXtender Document
Manager and other AppXtender content management components, you need to uninstall AppXtender
Web prior to upgrading AppXtender and then upgrade AppXtender prior to reinstalling AppXtender
Web. For more information on upgrading your AppXtender system, refer to the ApplicationXtender
Desktop Installation Guide.

Upgrading AppXtender Web Components

If you are upgrading to the current release of AppXtender Web, uninstall the AppXtender Web
software prior to upgrading the components in the AppXtender content management system. For
more information, see Upgrading AppXtender Web Server, page 31.
After preparing the AppXtender Web server as described in AppXtender Web.NET Server
Preparation Checklist, page 26 and Chapter 4, Configuring AppXtender Web Access Settings, install
the current version of AppXtender Web.

Caution: Make sure you prepare the AppXtender Web Server by configuring the necessary
settings under the AppXtender Web node in AppXtender Admin prior to installing and
registering AppXtender Web components. For more information, see Required AppXtender
Web Access Server Configuration, page 76 and Required AppXtender Rendering Server
Configuration, page 33.

ApplicationXtender Web Access .NET Administrator’s Guide 29

Planning AppXtender Web Access Deployment

Connectivity between Releases

When you upgrade your AppXtender database, EMC recommendeds upgrading all AppXtender
Desktop and AppXtender Web workstations at the same time. If you must delay upgrading some
workstations, do not use any new features until the entire system has been upgraded. Also, do
not use any administrative components (such as AppXtender AppGen) from previous releases.
Server components from any previous release of AppXtender Content Management, such as
AppXtender Web, Reports Management, and Index Server, must be uninstalled prior to upgrading
the AppXtender system.

Caution: Uninstall any previous release of AppXtender Web.NET on the AppXtender Web
Server prior to upgrading AppXtender Desktop.

Workstations using the AppXtender Document Manager module can connect to an AppXtender
database from a previous release of AppXtender. (New features might not be available in this case.)
Note: Connecting from the workstation in this section means logging into the data source from
the AppXtender Document Manager component of AppXtender or the AppXtender Web Access
component of AppXtender. If you log into the data source from AppXtender Admin or AppGen,
a message appears asking if you want to upgrade the database.

AppXtender Web System Architecture Upgrade Considerations

You can install AppXtender Web Server and AppXtender Rendering Server on separate computers.
This allows you to deploy AppXtender Web components in a way that improves processor efficiency.
For more information on optimizing your AppXtender Web system, refer to the Install Each Server
Component on a Dedicated Computer and Increase Concurrent Conversion Capacity by Installing
Multiple AppXtender Rendering Servers sections of the ApplicationXtender Concepts Guide.

Supported Platform Upgrade Considerations

If you are upgrading from a previous release of AppXtender Web, make sure the operating systems
on your servers are still supported.
• Operating System Upgrade Considerations, page 30

Caution: If you upgrade from one type of deployment to another, you should completely
uninstall all AppXtender Web components and redeploy the system as described in AppXtender
Web Access Deployment Overview, page 15.

Operating System Upgrade Considerations

With each release of AppXtender Web, the list of operating systems supported for the AppXtender
Web Server computer may change for a variety of reasons. If operating system support does change,
and if you plan to use the same hardware for your AppXtender Web system, you may need to

30 ApplicationXtender Web Access .NET Administrator’s Guide

 Planning AppXtender Web Access Deployment

upgrade the operating system prior to installing the current version of AppXtender Web. Other
minimum hardware and software requirements may have increased for AppXtender Web. Refer to
the ApplicationXtender Web Access Release Notes for specific hardware and software requirements for
the computers you plan to use for AppXtender Web.

Upgrading AppXtender Web Server

To upgrade AppXtender Web:
1. Plan your upgrade carefully. For information, see Planning an AppXtender Web Upgrade, page
29.
The upgrade should be performed only on the AppXtender Web Access Server; AppXtender Web
Access Interactive Client (AppXtender Web IRC) users will be automatically upgraded when they
connect to the server that hosts the current release of the AppXtender Web IRC.
2. Uninstall the previous release of AppXtender Web as described in the WebXtender System Guide,
WebXtender Administrator’s Guide, or ApplicationXtender Web Access Administrator’s Guide for
that release.
If you attempt to install the current release of AppXtender Web when a previous release is still
installed, a Windows Installer message box appears that states Another version of this product is
already installed. Installation of this version cannot continue.
3. If AppXtender Desktop and AppXtender Web are installed on the same computer, perform
the following steps:
a. Uninstall AppXtender Desktop from the computer where AppXtender Web is installed.
b. Install the current version of AppXtender Desktop (including the AppXtender Admin
component) and upgrade the database. This step may be performed on the same computer
or a different computer.
For a more complete discussion of database upgrade considerations and procedures, refer to the
ApplicationXtender Desktop Installation Guide.
4. Continue with AppXtender Web deployment as if for a new installation. For instructions, see
AppXtender Web Access Deployment Overview, page 15.

ApplicationXtender Web Access .NET Administrator’s Guide 31

Planning AppXtender Web Access Deployment

32 ApplicationXtender Web Access .NET Administrator’s Guide

 Chapter 2
Configuring AppXtender Rendering
Server

Prior to installing and registering the AppXtender Rendering Server, you must configure any
mandatory AppXtender Rendering Server settings in AppXtender Admin.
This chapter provides configuration procedures for both required and optional AppXtender
Rendering Server settings. For more information on configuring AppXtender Rendering Server
settings, see the following sections:
• Required AppXtender Rendering Server Configuration, page 33
• Optional AppXtender Rendering Server Configuration, page 37

Required AppXtender Rendering Server

Configuration
Prior to installing the AppXtender Rendering Server and registering it with AppXtender Admin,
you must set up a login account and configure the cache location and database to be used by the
AppXtender Rendering Server. AppXtender Rendering Server settings are configured in AppXtender
Admin. For more information on configuring mandatory AppXtender Rendering Server settings,
see the following sections:
• Configuring an AppXtender Rendering Server Login Account, page 33
• Configuring AppXtender Rendering Server Cache Settings, page 35

Configuring an AppXtender Rendering Server Login

Account
The AppXtender Rendering Server Login Account setting is used whenever the AppXtender
Rendering Server requires a security context to access a resource. The user name you enter here
must have access to any resources the AppXtender Rendering Server needs to access to fulfill
rendering requests. For example, the account you configure must have appropriate access rights to
the rendering cache location.

ApplicationXtender Web Access .NET Administrator’s Guide 33

Configuring AppXtender Rendering Server

To set the AppXtender Rendering Server user credentials:

1. In AppXtender Admin, expand the Servers node.
2. Select Rendering Server. AppXtender Rendering Server options appear in the right pane of the
window.

Figure 1. AppXtender Admin - Servers > Rendering Server Node

3. In the Login section, click the Setup button to the right of the Account text box.
4. The Enter user credentials dialog box appears. In the User Name text box, enter the full name for
the user account that should be used as the global authentication account for the rendering cache
path, using the following syntax: domain_name\username.

Figure 2. AppXtender Admin Enter User Credentials Dialog Box

5. In the Password text box, enter the password for the account.
6. In the Confirm Password text box, re-enter the same password to confirm the spelling.

34 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Rendering Server

7. Click OK.
A message may appear indicating that the credentials could not be verified. This message may
appear for a variety of reasons, including the following:
• The domain name, user name, or password may have been mistyped. Try reentering the
account information.
• The credentials may be local to the server or do not have permission to log on locally.
Although this message appears on the local computer, it does not reflect a problem with
access to the remote server. Test the user account on the remote server by using that account
to log in on that server.
8. Select File > Save Changes to save changes.

Configuring AppXtender Rendering Server Cache

Settings
The AppXtender Rendering Server Cache Location settings dictate the path where rendered files are
cached for repeated access. If the AppXtender Web Server and Rendering Server are on the same
computer, the AppXtender Rendering Server Cache Location can be either a UNC or local drive
letter path. If the AppXtender Web Server and Rendering Server are not on the same computer, the
AppXtender Rendering Server Cache Location must be a UNC path, because the Cache Location
must be available to all AppXtender Rendering Server computers.
The data source for the AppXtender Rendering Server database points to a database containing
tables used to manage the rendering queue for the AppXtender Rendering Server. To simplify your
configuration process, you can set up a data source pointing to an existing AppXtender content
management database and add the AppXtender Rendering Server queue tables to that database. If
you anticipate heavy rendering queue traffic, however, you may want to set up a database specifically
for rendering queue management. The same databases and database versions supported for the
AppXtender content management database can be used for the AppXtender Rendering Server
database. You can also use a schema user with the database if needed. For more information on
supported databases, creating a database, or using a schema with your data source, refer to the
AppXtender Data Sources chapter of the ApplicationXtender Core Components Administrator’s Guide.

To configure AppXtender Rendering Server cache settings:

1. In AppXtender Admin, expand the Servers node.
2. Select Rendering Server. AppXtender Rendering Server Setup options appear in the right pane
of the window.
3. To configure the location of the AppXtender Rendering Server cache, click the Browse button to
the right of the Location text box in the Cache section.

ApplicationXtender Web Access .NET Administrator’s Guide 35

Configuring AppXtender Rendering Server

Figure 3. AppXtender Rendering Server Cache Settings

The Browse For Folder dialog box appears.

Figure 4. AppXtender Admin Browse For Folder Dialog Box

4. You have the following choices:

• To use an existing directory for the AppXtender Rendering Server cache, browse for and
select that directory, and click OK.
• To create a new directory for the AppXtender Rendering Server cache, browse to the folder
below which the directory should be located and select that directory, then click New Folder.
Rename the new folder as appropriate, verifying that the name is reflected in the Folder text
box, then click OK.
Note: If the AppXtender Web Server and Rendering Server are on the same computer, the
AppXtender Rendering Server Cache Location can be either a UNC or local drive letter
path. If the AppXtender Web Server and Rendering Server are not on the same computer,
the AppXtender Rendering Server Cache Location must be a UNC path, because the Cache
Location must be available to all AppXtender Rendering Server computers.
A message appears prompting you to configure the new path under the Paths section
in AppXtender Admin. For more information on configuring paths, refer to the
ApplicationXtender Core Components Administrator’s Guide.
5. To configure a data source to be used to hold the AppXtender Rendering Server rendering job
queue information, click the Select button to the right of the Database text box in the Cache
section. You can either select an existing database or create a new database specifically for this
purpose. When you connect to the data source for the first time from this settings page, the
AppXtender Rendering Server tables are created in the database. For more information on
creating databases and configuring data sources, refer to the AppXtender Data Sources chapter of

36 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Rendering Server

the ApplicationXtender Core Components Administrator’s Guide. For information on locating existing
data sources, see Locating a Data Source, page 131.
6. From the AppXtender Admin File menu, select Save Changes.

Optional AppXtender Rendering Server

Configuration
After configuring mandatory AppXtender Rendering Server settings, you can also adjust file
rendering and garbage collection settings for AppXtender Rendering Server through AppXtender
Admin. For more information about optional adjustments to AppXtender Rendering Server settings,
see the following sections:
• Configuring AppXtender Rendering Server Rendering Settings, page 37
• Configuring AppXtender Rendering Server Cleanup Settings, page 40

Configuring AppXtender Rendering Server Rendering

Settings
For more information, see the following sections:
• Setting the Maximum Number of Concurrent Conversions, page 37
• Configuring Image Conversion Settings, page 38
• Configuring Foreign File Conversion Settings, page 38
• Configuring COLD/ERM Form Overlay Font Settings, page 39

Setting the Maximum Number of Concurrent Conversions

The Max number of concurrent connections option helps to avoid bottlenecks at the AppXtender
Rendering Server by limiting the total number of AppXtender Web Thin Client image conversions
or AppXtender Web Thin Client foreign file HTML rendering conversions at any particular time.
All converted files are affected by these options, including thumbnails, fully rendered JPEG/GIF
representations of graphical (non-text) documents, rendering of documents for email, and foreign file
rendering.
By default, five (5) concurrent conversions can occur across the AppXtender Rendering Server in a
data source group. If you have a single AppXtender Rendering Server with a single-processor,
this setting is appropriate.
If your AppXtender Rendering Server has dual or quad processors, or if you have multiple
AppXtender Rendering Servers, you can increase the number of concurrent conversions. Adding five
(5) concurrent conversions per processor per server is a good rule of thumb.

ApplicationXtender Web Access .NET Administrator’s Guide 37

Configuring AppXtender Rendering Server

To change the maximum number of concurrent conversions:

• In the Generation section under the Servers > Rendering Server> Setup node in AppXtender
Admin, use the spin box next to the Max number of concurrent connections option to increase
or decrease the total maximum number of concurrent conversions allowed for AppXtender
Rendering Servers in the data source group.

Configuring Image Conversion Settings

You can configure options to manage the conversion of images by the AppXtender Rendering Server.
See the following sections:
• Configuring Image Conversion Format, page 38
• Configuring the Maximum Wait Time for Image Conversion Completion, page 38

Configuring Image Conversion Format

The Image type to generate option allows you to choose whether the AppXtender Rendering Server
creates GIF or JPEG files when it converts AppXtender Web Thin Client images, COLD/ERM
documents with image form overlay, and thumbnails. JPEG images are best for photographs, scanned
photographs, and complex color images. They have a higher quality than GIF images and will more
closely resemble the original document. However, the higher quality is reflected in larger file sizes,
which are slower to load on a web page. GIF images are best for images that contain solid colors, text,
and line art. GIF images have a lower quality and file size than JPEG files, and as such, will load faster.
You may decide to use GIF files if resolution and document quality are less important than page load
times (for instance, for black and white scanned images). The JPEG image type is enabled by default.

To change the image type:

1. Enable the JPEG radio button or enable the GIF radio button.
2. Select File > Save Changes to apply changes.

Configuring the Maximum Wait Time for Image Conversion Completion

You can configure the delay interval (in seconds) between image conversion attempt retries.

To change the maximum wait time between image conversion attempts:

1. Use the spin box for the Max time to wait for a conversion to complete (seconds) option to select
the number of seconds you want to configure between conversion retries.
2. Select File > Save Changes to apply changes.

Configuring Foreign File Conversion Settings

You can set parameters to manage the conversion of foreign files on the AppXtender Rendering Server.

38 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Rendering Server

For more information, see the following sections:

• Enabling Foreign File HTML Conversion, page 39
• Configuring the Maximum Wait Time for Foreign File Conversion Completion, page 39

Enabling Foreign File HTML Conversion

AppXtender Web can be configured to use KeyView viewing technology to render foreign files
as HTML documents.

To enable HTML rendering of foreign files:

1. Enable the Render foreign files as HTML option.
2. Select File > Save Changes to apply changes.

Configuring the Maximum Wait Time for Foreign File Conversion Completion

You can configure the delay interval (in seconds) between foreign file conversion attempt retries.

To change the maximum wait time between foreign file conversion attempts:
1. Enter the number of seconds you want in the spin box for the Max time to wait for a conversion to
complete (seconds) option.
2. Select File > Save Changes to apply changes.

Configuring COLD/ERM Form Overlay Font Settings

The Image Form Overlay Font for AppXtender Web Thin Client option allows you to select a custom
font for AppXtender Web Thin Client image form overlay. Various font types, font styles, and font
sizes can be configured for form overlays. It is recommended that only fixed width fonts be used for
Form Overlay.

To select a font installed on the computer:

1. Click the Select button to the right of the Image Form Overlay Font for AppXtender Web Thin
Client text box.
2. Select a font from the Font list.
3. Click OK.
4. Select File > Save Changes to apply changes.
Note: You can change the body text font of text pages by adjusting your local browser font
settings.

ApplicationXtender Web Access .NET Administrator’s Guide 39

Configuring AppXtender Rendering Server

Configuring AppXtender Rendering Server Cleanup

Settings
All Cleanup options are applied when the garbage collection operation is attempted. The following
table describes the controls in the Cleanup section.

Table 2. Cleanup Options

Control Description
Check the cache every The delay (in seconds) between each garbage collection
(minutes) attempt.
Limits - Max File Maximum number of files allowed in cache before
Garbage Collection takes place.
Limits - Max Space Used Maximum megabytes allowed for all files in cache.
(MB) This number should be larger than the largest possible
file to be retrieved from AppXtender AppXtender, or
the file may not be rendered.
When limit is reached, The percentage of used space that must be reclaimed
decrease by (%) through garbage collection before a garbage collection
attempt will stop once it has started.

40 ApplicationXtender Web Access .NET Administrator’s Guide

 Chapter 3
Using the AppXtender Web.NET
Configuration Wizard

This chapter describes how to configure any mandatory AppXtender Web Access .NET Server
settings in AppXtender Administrator.
• Introduction, page 41
• Starting the Wizard, page 42
• Specifying Global Credentials, page 43
• Configuring License Server Connections, page 44
• Configuring Data Sources, page 46
• Configuring Session Management, page 53
•
• Configuring IIS Security, page 57
• Configuring E-mail, page 59
• Configuring AppXtender Rendering Server, page 62
• Viewing the Configuration Summary, page 68
• Validating Configurations, page 69

Introduction
Prior to installing and registering AppXtender Web Access Server, you must configure any mandatory
AppXtender Web Access Server settings in AppXtender Admin.
If you are implementing a 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. This chapter describes how to use the AppXtender Web.NET Configuration
Wizard to set up AppXtender Web.NET in your AppXtender system. For instructions on configuring
these (and other) settings in the AppXtender Admin tree, see Chapter 4, Configuring AppXtender
Web Access Settings
The AppXtender Web.NET Configuration Wizard has two aspects, as described in the following table:

ApplicationXtender Web Access .NET Administrator’s Guide 41

Using the AppXtender Web.NET Configuration Wizard

Table 3. Aspects of the AppXtender Web.NET Configuration Wizard

AppXtender Wizard
Aspect Description
Desktop This aspect of the wizard allows you to configure
License Server connections and data sources.
Web Access This aspect of the wizard allows you to configure
the above settings plus all settings required for
AppXtender Web Access .NET configuration:
• Global credentials

• Session management

• IIS security

• E-mail

• AppXtender Rendering Server

To use the AppXtender Web.NET Configuration Wizard:

1. Configure License Server connections and data sources by running the AppXtender Desktop
aspect of the wizard. For instructions, see Starting the Wizard, page 42.
2. In AppXtender AppGen, create applications and finish implementing security for each data
source. For instructions, refer to the "Creating an Application" and "Implementing Security"
sections of the ApplicationXtender Core Components Administrator’s Guide.
3. Complete the AppXtender Web Access configuration by running the AppXtender Web Access
aspect of the wizard. For instructions, see Starting the Wizard, page 42.

Starting the Wizard

To start the AppXtender Web.NET Configuration Wizard:
1. Start AppXtender Admin. For instructions, see Starting AppXtender Administrator, page 18.
2. From the Tools menu, select AppXtender Web.NET Wizard. The AppXtender Web.NET
Configuration Wizard appears, starting with the welcome page.
3. Select which aspect of this wizard you want to run.
4. Click Next. The page that appears next depends on which aspect of the wizard you selected:
• If you selected AppXtender Web Access, the Global Credentials Configuration page appears.
For instructions, see Specifying Global Credentials, page 43.
• If you selected AppXtender Desktop, the License Server Configuration page appears. For
instructions, see Configuring License Server Connections, page 44.

42 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Specifying Global Credentials

The Global Credentials Configuration page of the wizard allows you to specify the AppXtender Web
global authentication account. The AppXtender Web global authentication account grants security
privileges to AppXtender Web Access in instances where an authentication context is required to
access a resource and the global credentials option is selected for that resource. Because an actively
logged-on account is not required for AppXtender Web to be running, some security context must be
established – this context is established through the use of an authentication account.
You can configure specific resource authentication methods for many of the resources that
AppXtender Web accesses in the course of processing client requests. The credentials specified for a
resource are used whenever AppXtender Web needs to provide authentication account information
in order to access a resource.
Whenever global credentials are configured for a resource, AppXtender Web Access uses the global
credentials that you specify to access the resource. Resources for which you can configure credentials
include remote and server resources on Windows, such as the AppXtender Web Session Cache,
the data sources through which AppXtender Web connects to databases, and DiskXtender (DX)
document servers. The global account is also used for authentication if needed when accessing
the registry or the License Server. The ASPNET user and any authentication accounts used by
AppXtender Web resources, including the global account, must have the appropriate permissions
detailed in the Accounts and Rights Required for Resource Authentication Accounts section of
the ApplicationXtender Concepts Guide.
You can configure credentials settings elsewhere in AppXtender Admin to override the use of the
global account for authentication. However, any accounts that are used to provide credentials
as an authentication context for AppXtender Web resources must have the rights to access to
those resources. To make sure you have access to all resources, the easiest approach is to use the
AppXtender Web global account to impersonate for all AppXtender Web resources, and make sure
that this account has access to all resources and appropriate rights.

Figure 5. AppXtender Web.NET Configuration Wizard - Global Credentials Configuration Page

ApplicationXtender Web Access .NET Administrator’s Guide 43

Using the AppXtender Web.NET Configuration Wizard

To specify global credentials:

1. In the User Name text box, enter the full name for the user account that should be used as the
global authentication account, using the following syntax: domain_name\username.
2. In the Password text box, enter the password for the account.
3. In the Confirm Password text box, re-enter the same password to confirm the spelling.
4. Click Verify. A message appears indicating whether the wizard was able to verify the account.
(For information, see the table in Validating Configurations, page 69.) Click OK.
5. Click Next. (If the wizard was unable to verify the specified account, a message appears asking
whether you want to continue. Click Yes.)
The License Server Configuration page appears. For instructions, see Configuring License Server
Connections, page 44.

Configuring License Server Connections

The License Server Configuration part of the wizard allows you to add, view, modify, and remove
License Server connections. The option to view or modify License Server connections is available only
when a License Server connection already exists.

Figure 6. AppXtender Web.NET Configuration Wizard - License Server Configuration Page

To continue using the wizard:

You have the following choices:
• If you want to add a new License Server connection, select Add New License Server Connection
and click Next. The License Server Connection page appears. For instructions, see Adding a
License Server Connection, page 45.
• If you have existing License Server connections, and you want to view or modify them, select
View/Modify License Server Connections and click Next. The License Server List page appears.
For instructions, see Managing the License Server List, page 45.
• Otherwise, select Use Evaluation License or Skip License Server Connections Configuration
and click Next. If an evaluation license is in use, a message appears asking you whether you

44 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

want to continue. Click Yes. The Data Source Configuration page appears. For instructions, see
Configuring Data Sources, page 46.

Adding a License Server Connection

The License Server Connection page of the wizard allows you to add a connection to a License Server.

Figure 7. AppXtender Web.NET Configuration Wizard - License Server Connection Page

To add a connection to a License Server:

1. Type the license server address (server name or IP address) in the Network Address text box.
2. To limit access to the license server to a specific group of users, type a license group in the License
Group text box. Refer to the ApplicationXtender Core Components Administrator’s Guide for more
information on license groups.
3. Click Verify. A message appears indicating whether the License Server was successfully
contacted. (You can expand the message to view licensing details.) Click Close.
4. Click Next. The License Server Configuration page reappears. For instructions, see Configuring
License Server Connections, page 44.

Managing the License Server List

The License Server List page of the wizard displays a list of existing License Server connections and
allows you to view the properties of, verify, or remove each connection. (The License Group column
is provided only for backwards compatibility.)

ApplicationXtender Web Access .NET Administrator’s Guide 45

Using the AppXtender Web.NET Configuration Wizard

Figure 8. AppXtender Web.NET Configuration Wizard - License Server List Page

To manage the License Server list:

1. Select a License Server connection from the list.
2. You have the following choices:
• If you want to verify the connection, click Verify. A message appears indicating whether the
License Server was successfully contacted. (You can expand the message to view licensing
details.) Click Close.
• If you want to modify the connection, click Properties. The License Server dialog box appears.
You can change the network transport or network address. (The License Group text box is
provided only for backwards compatibility.) Click OK.
• If you want to remove the connection, click Remove. A message appears requesting
confirmation of the removal. Click Yes. The connection is removed.
Note: To remove a License Server connection, you must first remove any references to that
connection. If, for example, a data source points to the connection to be deleted, you must
reassign that data source to another connection prior to removing the connection.
3. Click Next. The Data Source Configuration page appears. For instructions, see Configuring
Data Sources, page 46.

Configuring Data Sources

The Data Source Configuration part of the wizard allows you to add, view, modify, and remove
AppXtender data sources.

46 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 9. AppXtender Web.NET Configuration Wizard - Data Source Configuration Page

To continue using the wizard:

1. You have the following choices:
• If you want to add a new data source, select Add New Data Source.
• If you want to set an existing data source as default, show or hide a data source, or delete a
data source, select Manage Visibility of Data Sources.
• If you want to change the description, data link, schema, authentication, licensing, or security
provider of an existing data source, select Manage the Properties of a Data Source.
• Otherwise, select Skip Data Sources Configuration.
2. Click Next. The page that appears next depends on your selections:
• If you selected Add New Data Source, the Data Source Identification page appears. For
instructions, see Specifying Data Source Identification, page 48.
• If you selected Manage Visibility of Data Sources, the Data Source List page appears. For
instructions, see Managing the Data Source List, page 52.
• If you selected Manage the Properties of a Data Source, the Data Source Identification page
appears. For instructions, see Specifying Data Source Identification, page 48.
• If you selected Skip Data Sources Configuration and you are using the AppXtender Web
Access aspect of the wizard, the Session Management page appears. For instructions, see
Configuring Session Management, page 53.
• If you selected Skip Data Sources Configuration and you are using the AppXtender Desktop
aspect of the wizard, the Summary page appears. For instructions, see Viewing the
Configuration Summary, page 68.

ApplicationXtender Web Access .NET Administrator’s Guide 47

Using the AppXtender Web.NET Configuration Wizard

Specifying Data Source Identification

For a new data source, the Data Source Identification page of the wizard allows you to provide a
name and description. For an existing data source, the Data Source Identification page of the wizard
displays the name and allows you to modify the description. The name and description are used only
for identifying the data source; they do not have any effect on using the data source.

Figure 10. AppXtender Web.NET Configuration Wizard - Data Source Identification Page

To specify data source identification:

1. In the Name text box, type a name for the data source.
2. In the Description text box, type a description for the data source.
3. Click Next. The Data Source Link page appears. For instructions, see Connecting to the Database,
page 48.

Connecting to the Database

The Data Source Link page of the wizard allows you to create a connection to the AppXtender
database.

48 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 11. AppXtender Web.NET Configuration Wizard - Data Source Link Page

To connect to the database:

1. Click Data Link. The Data Link Properties dialog box appears.
2. On the Provider tab, select the appropriate data provider for the data source. On the Connection
tab, enter appropriate server and database information. (For more information on creating
databases and configuring data sources, refer to the AppXtender Data Sources chapter of the
ApplicationXtender Core Components Administrator’s Guide. For information on locating existing
data sources, see Locating a Data Source, page 131.) Click OK.
3. If a schema has been set up in the database, enter the name in the Schema text box. The schema
name will be used to begin all database table names created for this data source and thus the
name entered should be in a valid format for the database. Avoid using any spaces, using
any keywords, or beginning the name with a numeral. (You can use an underscore in place
of a space.) For information on database schema, refer to the Database Schema section of the
ApplicationXtender Concepts Guide.
4. Click Next.
The wizard compares the password for the administrative user for the existing data source group
to the password for the same user in the new database. If it does not match, a message appears
asking if you want to change the password. If you click Yes, a Password Confirmation dialog
box appears. For instructions, refer to the Information about Logging into AppXtender Admin
section of the ApplicationXtender Core Components Administrator’s Guide.
If the specified database is new to the AppXtender system, a message appears asking if you
want to create the required tables. Click Yes. The AppXtender Table Create dialog box appears,
indicating the progress of the table creation. When table creation is complete, click Close.

ApplicationXtender Web Access .NET Administrator’s Guide 49

Using the AppXtender Web.NET Configuration Wizard

The page that appears next depends on your configuration:

• If the database is Microsoft SQL Server (and if the SQL Server setting, Windows NT Integrated
Security, is not being used), the Data Source Licensing page appears. For instructions, see
Specifying a License Server for the Data Source, page 51.
• Otherwise, the Data Source Authentication page appears. For instructions, see Specifying
Data Source Authentication, page 50.

Specifying Data Source Authentication

The Data Source Authentication page of the wizard allows you to specify an authentication method
for the data source.

Figure 12. AppXtender Web.NET Configuration Wizard - Data Source Authentication Page

To specify data source authentication:

1. Under Authentication Method, you have the following choices:
• To use the application credentials entered when the user logged into AppXtender Desktop or
Web, select Application.
• To use the global impersonation account credentials configured in the Global Credentials
Configuration page of the wizard, select Global. EMC recommends this setting in most cases.
• To enter a specific username and password to be used when authenticating requests for
access to this database, select Supplied. Click Select. The Enter User Credentials dialog box
appears. Enter the domain, username, and password, then confirm the password and click
OK. (If the wizard was unable to verify the specified account, a message appears asking
whether you want to continue. Click Yes.)
For more information, refer to the About Configuring Data Source Credentials section of the
ApplicationXtender Concepts Guide.

50 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

2. Click Next. The Data Source Licensing page appears. For instructions, see Specifying a License
Server for the Data Source, page 51.

Specifying a License Server for the Data Source

The Data Source Licensing page of the wizard allows you to configure licensing for the data source.

Figure 13. AppXtender Web.NET Configuration Wizard - Data Source Licensing Page

To configure licensing for the data source:

1. From the License Server drop-down list, select the License Server connection that you want to
use. You can choose Evaluation or any existing License Server connection. If you choose an
existing License Server connection, the License Group text box becomes available.
2. If you want users to use licenses from a particular license group, enter the name of the license
group in the License Group text box. For information on the interaction of license group
settings, refer to the License Groups section of the ApplicationXtender Concepts Guide. For more
information on configuring license groups, refer to the Adding a License Group section of the
ApplicationXtender Core Components Administrator’s Guide.
3. Click Next. The Data Source Security Provider page appears. For instructions, see Selecting a
Security Provider for the Data Source, page 51.

Selecting a Security Provider for the Data Source

The Data Source Security Provider page of the wizard allows you to select a security provider for
the data source.

ApplicationXtender Web Access .NET Administrator’s Guide 51

Using the AppXtender Web.NET Configuration Wizard

Figure 14. AppXtender Web.NET Configuration Wizard - Data Source Security Provider Page

To select a security provider for the data source:

1. From the Security Provider drop-down list, select the security provider that you want to use.
If you want to use a directory service security provider and if it is not available in the list, you
must create it before using this wizard. For instructions, refer to the Creating a Directory Service
Security Provider section of the ApplicationXtender Core Components Administrator’s Guide.
Note: The next time that you open AppXtender AppGen with this data source set as default,
a message appears indicating that you need to change the security provider in AppXtender
AppGen to match AppXtender Admin. For instructions, refer to the Variations on Login
Procedures section of the ApplicationXtender Core Components Administrator’s Guide.
2. Click Next. The Data Source List page appears. For instructions, see Managing the Data Source
List, page 52.

Managing the Data Source List

The Data Source List page of the wizard displays a list of existing data sources and allows you
to set a data source as default, show or hide data sources from AppXtender Web.NET users, and
remove data sources.

52 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 15. AppXtender Web.NET Configuration Wizard - Data Source List Page

To manage the data source list:

1. Select a non-default data source from the list. (To perform an action on the default data source,
you must first set another data source as default.)
2. You have the following choices:
• If you want to set the data source as default, click Default. A white check mark within a black
background ( ) appears next to the data source name.

• If you want to show the data source, click Show. A check mark ( ) appears next to the
data source name.
• If you want to hide the data source, click Hide. The check mark next to the data source name
disappears.
• If you want to remove the data source, click Remove. A message appears requesting
confirmation of the removal. Click Yes. The data source is removed.
3. Click Next. A message appears asking whether you would like to add another data source. The
page that appears next depends on whether you click Yes or No:
• If you click Yes, the Data Source Identification page appears. For instructions, see Specifying
Data Source Identification, page 48.
• If you click No, the Session Management page appears. For instructions, see Configuring
Session Management, page 53.

Configuring Session Management

The Session Management part of the wizard allows you to specify the AppXtender Web Server
session cache path, the authentication method for that path, and settings for session ending.

ApplicationXtender Web Access .NET Administrator’s Guide 53

Using the AppXtender Web.NET Configuration Wizard

Figure 16. AppXtender Web.NET Configuration Wizard - Session Management Page

To continue using the wizard:

1. You have the following choices:
• If you want to configure session management, select Configure Session Management.
• Otherwise, select Skip Session Management.
2. Click Next. The page that appears next depends on your selections:
• If you selected Configure Session Management, the Session Management Path page appears.
For instructions, see Configuring Session Management, page 53.
• If you selected Skip Session Management and you are using the AppXtender Web Access
aspect of the wizard, the IIS Security page appears. For instructions, see Configuring IIS
Security, page 57.

Configuring Session Management Settings

The Session Management Path page of the wizard allows you to specify the AppXtender Web Server
session cache path, the authentication method for that path, and settings for session ending.
The AppXtender Web Server session cache stores AppXtender Web user session data for active
AppXtender Web sessions. Session data includes authorization and authentication data for user
sessions and user session context for operations a user is engaged in. EMC recommends using a local
path for the session cache.
The AppXtender Web Session Time-Out (Minutes) setting controls the management of session data.
This setting sets the duration of session idle time that AppXtender Web allows to elapse before
closing inactive user sessions. For example, if AppXtender Web Session Time-Out (Minutes) is set
to 30, user sessions will terminate after 30 minutes of user inactivity. The default Session Time-Out
setting is 20 minutes.

54 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 17. AppXtender Web.NET Configuration Wizard - Session Management Path Page

To configure session management:

1. Select the Browse button to the right of the Session Cache Path text box. The Local Path Setup
dialog box appears.

Figure 18. AppXtender Web.NET Configuration Wizard - Local Path Setup Dialog Box

2. From the Path list, select the appropriate path for the cache used by AppXtender Web Server,
or click Browse to browse for a new path. If you click Browse, the Browse For Folder dialog
box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 55

Using the AppXtender Web.NET Configuration Wizard

Figure 19. AppXtender Web.NET Configuration Wizard - Browse For Folder Dialog Box

In the Browse For Folder dialog box, you have the following choices:
• To use an existing directory for the cache, browse for and select that directory, and click OK.
• To create a new directory for the cache, browse to and select the directory in which the new
directory should be created. Click New Folder. Rename the new folder as appropriate,
verifying that the name is reflected in the Folder text box, then click OK.
3. If the correct credentials are not already selected, select the appropriate credentials option for
the authentication account that is used when accessing the selected path. By default, global
credentials are set for a path.
Note: The Application authentication method is available only when all data sources in the data
source group are using the Application authentication method.
Note: If the selected path already exists in the AppXtender Admin Paths table, a credentials
option may already have been selected. If you change the credentials for a path here, the change
affects the credentials used for that path in any location where it is used, and the change is
reflected in the record for that path in the AppXtender Admin Paths table.
4. Click OK.
If the specified path does not exist, a message appears asking whether you want to create it.
Click Yes.
A message appears indicating that the specified path was added to the Paths configuration. Click
OK. The specified path appears in the Session Cache Path text box.
5. In the AppXtender Web Session Time-Out text box, specify the duration of session idle time
that you want to allow (in minutes) before AppXtender Web automatically closes inactive user
sessions.
6. Specify whether you want AppXtender Web to automatically logout the user when the user
closes the main browser window.
7. Click Test Connection. A message appears indicating whether the path could be verified. (For
information, see the table in Validating Configurations, page 69.) Click OK.
8. Click Next. (If the wizard was unable to verify the cache path, a message appears asking whether
you want to continue. Click Yes.)
The IIS Security page appears. For instructions, see Configuring IIS Security, page 57.

56 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Configuring IIS Security

The IIS Security part of the wizard allows you to configure settings that control the authentication
methods used by browser clients when accessing the AppXtender Web.NET Server. The settings that
you should choose depend on the credentials you select for AppXtender Web.NET system resources.
For more information, refer to the Configuring Authentication Accounts and Security Settings for
AppXtender Web and Web Services sections of the ApplicationXtender Concepts Guide.

Figure 20. AppXtender Web.NET Configuration Wizard - IIS Security Page

To continue using the wizard:

You have the following choices:
• If you want to configure IIS security settings that determine how users are authenticated, select
Configure IIS Security and click Next. The User Access page appears. For instructions, see
Configuring User Access, page 57.
• Otherwise, select Skip IIS Security and click Next. The E-mail Configuration page appears. For
instructions, see Configuring E-mail, page 59.

Configuring User Access

The User Access page of the wizard allows you to specify how users may access AppXtender
Web.NET Server.

ApplicationXtender Web Access .NET Administrator’s Guide 57

Using the AppXtender Web.NET Configuration Wizard

Figure 21. AppXtender Web.NET Configuration Wizard - User Access Page

To configure user access:

1. To cause users logging into the AppXtender Web.NET Server to be authenticated first through
Windows security, enable the Using NTLM Authentication option. Windows authentication
occurs if the user is connecting from a Windows computer that belongs to the same domain as the
AppXtender Web.NET Server or a trusted domain, and if the Users may access the server via
Anonymous user account option is disabled.
2. To allow users accessing the AppXtender Web.NET Server to be authenticated anonymously,
enable the Via Anonymous User Account option. Anonymous authentication occurs through
the Network Service.
3. Click Next. The page that appears next depends on your selections:
• If any data source in the data source group is using the Windows security provider and if you
have selected the Using NTLM Authentication option, the Automatic Login page appears.
For instructions, see Configuring Automatic Login, page 58.
• Otherwise, the E-mail Configuration page appears. For instructions, see Configuring E-mail,
page 59.

Configuring Automatic Login

The Automatic Login page of the wizard allows you to specify whether users can login to AppXtender
Web.NET automatically, and if so, whether a full-text license should be requested automatically.
Note: This page of the wizard appears if the default data source is using the Windows security
provider and if you have selected the Using NTLM Authentication option on the User Access page.

58 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 22. AppXtender Web.NET Configuration Wizard - Automatic Login Page

To configure automatic login:

1. To cause AppXtender Web.NET to attempt to automatically log a user authenticated through
NTLM when the default data source is using the Windows security provider, enable the
Automatic login option.
When the auto-login option is selected, the Request Full-text License option becomes available.
2. To automatically request full-text capabilities when a user is automatically logged in through
the setting configured in Step 1, enable the Request Full-Text License option in the Automatic
Login Options section.
3. Click Next. The E-mail Configuration page appears. For instructions, see Configuring E-mail,
page 59.

Configuring E-mail
The E-mail Configuration part of the wizard allows you to configure settings so that users can e-mail
documents and pages, or references to documents and pages using AppXtender Web.

ApplicationXtender Web Access .NET Administrator’s Guide 59

Using the AppXtender Web.NET Configuration Wizard

Figure 23. AppXtender Web.NET Configuration Wizard - E-mail Configuration Page

To continue using the wizard:

You have the following choices:
• If you want to allow users to send documents by e-mail from AppXtender Web, select Configure
E-mail Settings and click Next. The E-mail Settings page appears. For instructions, see
Configuring E-mail Settings, page 60.
• Otherwise, select Skip E-mail Configuration and click Next. If e-mail settings are not fully
configured, a message appears asking whether you want to continue. Click Yes. The AppXtender
Rendering Server Configuration page appears. For instructions, see Chapter 2, Configuring
AppXtender Rendering Server.

Configuring E-mail Settings

The E-mail Settings page of the wizard allows you to enable e-mail features for AppXtender Web by
designating an SMTP server and adding an administrator’s e-mail address.

60 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 24. AppXtender Web.NET Configuration Wizard - E-mail Settings Page

To configure e-mail settings:

1. In the E-mail SMTP Server section, in the Server Name text box, enter the server name or IP
address of an active SMTP server that can be used to relay AppXtender Web messages.
2. In the Administrator E-mail section, click the Add or Modify button. The E-Mail Address
dialog box appears.

Figure 25. AppXtender Web.NET Configuration Wizard - E-Mail Address Dialog Box

3. In the Display Name text box, enter the name you wish to display in the From field of the email.
The default value is AppXtender Web Administrator.
4. In the E-mail Address text box, enter the administrator’s e-mail address, in SMTP format
([email protected]).
5. Click the Save & Close button to apply your changes.
6. Click Next. The AppXtender Rendering Server Configuration page appears. For instructions, see
Chapter 2, Configuring AppXtender Rendering Server.

ApplicationXtender Web Access .NET Administrator’s Guide 61

Using the AppXtender Web.NET Configuration Wizard

Configuring AppXtender Rendering Server

The AppXtender Rendering Server Configuration part of the wizard allows you to specify a
AppXtender Rendering Server authentication account, data source, and cache path. AppXtender
Web.NET requires these AppXtender Rendering Server settings to support AppXtender Web Thin
Client, thumbnail, or e-mail rendering.

Figure 26. AppXtender Web.NET Configuration Wizard - AppXtender Rendering Server Configuration
Page

To continue using the wizard:

You have the following choices:
• If you want to support AppXtender Web Thin Client, thumbnail, or e-mail rendering, select
Configure AppXtender Rendering Server Settings and click Next. The AppXtender Rendering
Server Authentication Account page appears. For instructions, see Configuring AppXtender
Rendering Server Authentication Account, page 62.
• Otherwise, select Skip AppXtender Rendering Server Configuration and click Next. If AppXtender
Rendering Server settings are not fully configured, a message appears asking whether you want to
continue. Click Yes.

Configuring AppXtender Rendering Server

Authentication Account
The AppXtender Rendering Server Authentication Account page of the wizard allows you to specify
an authentication account for the AppXtender Rendering Server.
The AppXtender Rendering Server authentication account is used whenever the AppXtender
Rendering Server requires a security context to access a resource. The account must have access to
any resources the AppXtender Rendering Server needs to access in order to fulfill rendering requests.

62 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

For example, the account must have appropriate access rights to the AppXtender Rendering Server
cache path.

Figure 27. AppXtender Web.NET Configuration Wizard - AppXtender Rendering Server Authentication
Account Page

To specify the AppXtender Rendering Server authentication account:

1. You have the following choices:
• If you want to copy the global credentials and use that account information as your
AppXtender Rendering Server authentication account, select Copy the global credentials and
skip to Step 5. (If the global credentials are later changed, the AppXtender Rendering Server
credentials are not automatically updated.)
• If you want to use a different account information as your AppXtender Rendering Server
authentication account, select Supply credentials.
2. In the Domain\User text box, enter the full name for the user account that should be used as
the global authentication account for the rendering cache path, using the following syntax:
domain_name\username.
3. In the Password text box, enter the password for the account.
4. In the Confirm Password text box, re-enter the same password to confirm the spelling.
5. Click Verify. A message appears indicating whether the wizard could verify the credentials. (For
information, see the table in Validating Configurations, page 69.) Click OK.
6. Click Next. (If the wizard was unable to verify the specified account, a message appears asking
whether you want to continue. Click Yes.)

ApplicationXtender Web Access .NET Administrator’s Guide 63

Using the AppXtender Web.NET Configuration Wizard

The page of the wizard that appears next depends on your configuration:
• If a data source has not already been specified for the AppXtender Rendering Server, the
AppXtender Rendering Server Data Source page appears. For instructions, see Selecting an
AppXtender Rendering Server Data Source, page 64.
• If a data source has already been specified for the AppXtender Rendering Server, the
AppXtender Rendering Server Data Link page appears. For instructions, see Connecting to
the AppXtender Rendering Server Database, page 65.
Note: If a data source has already been specified for the AppXtender Rendering Server and you
want to switch to a different data source for the AppXtender Rendering Server, you must do so
via AppXtender Admin. For instructions, see Configuring AppXtender Rendering Server Cache
Settings, page 35.

Selecting an AppXtender Rendering Server Data Source

The AppXtender Rendering Server Data Source page of the wizard allows you to specify a data
source for the AppXtender Rendering Server.
The AppXtender Rendering Server data source holds the AppXtender Rendering Server rendering
job queue information. You can either select an existing database or create a new database specifically
for this purpose. When you connect to the data source for the first time, the AppXtender Rendering
Server tables are created in the database.

Figure 28. AppXtender Web.NET Configuration Wizard - AppXtender Rendering Server Data Source Page

To select a data source for the AppXtender Rendering Server:

• You have the following choices:
— If you want to add a new data source for the AppXtender Rendering Server, select Add New
AppXtender Rendering Server Data Source and click Next. The AppXtender Rendering Server

64 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Data Link page appears. For instructions, see Connecting to the AppXtender Rendering Server
Database, page 65.
— If you want to use an existing data source, select Use Existing Data Source. Select the data
source from the drop-down list and click Next. The AppXtender Rendering Server Cache
Path page appears. For instructions, see Specifying the AppXtender Rendering Server Cache
Path, page 66.

Connecting to the AppXtender Rendering Server

Database
The AppXtender Rendering Server Data Link page of the wizard allows you to create a connection
to the AppXtender Rendering Server database.

Figure 29. AppXtender Web.NET Configuration Wizard - AppXtender Rendering Server Data Link Page

To connect to a database for the AppXtender Rendering Server:

1. Click Data Link. The Data Link Properties dialog box appears.
2. On the Provider tab, select the appropriate data provider for the data source. On the Connection
tab, enter appropriate server and database information. (For more information on creating
databases and configuring data sources,refer to the AppXtender Data Sources chapter of the
ApplicationXtender Core Components Administrator’s Guide. For information on locating existing
data sources, see Locating a Data Source, page 131.)
3. Click Next. The AppXtender Rendering Server Cache Path page appears. For instructions, see
Specifying the AppXtender Rendering Server Cache Path, page 66.

ApplicationXtender Web Access .NET Administrator’s Guide 65

Using the AppXtender Web.NET Configuration Wizard

Specifying the AppXtender Rendering Server Cache

Path
The AppXtender Rendering Server Cache Path page of the wizard allows you to specify the path
where rendered files are cached for repeated access. If the AppXtender Web Server and Rendering
Server are on the same computer, the AppXtender Rendering Server cache path can be either a UNC
or local drive letter path. If the AppXtender Web Server and Rendering Server are not on the same
computer, the AppXtender Rendering Server cache path must be a UNC path, because the cache path
must be available to all AppXtender Rendering Server computers.

Figure 30. AppXtender Web.NET Configuration Wizard - AppXtender Rendering Server Cache Path Page

To specify the AppXtender Rendering Server cache path:

1. Click Browse. The UNC Path Setup dialog box appears.

66 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Figure 31. AppXtender Web.NET Configuration Wizard - UNC Path Setup Dialog Box

2. From the Path list, select the appropriate path for the cache used by the AppXtender Rendering
Server, or click Browse to browse for a new path. If you click Browse, the Browse For Folder
dialog box appears.

Figure 32. AppXtender Web.NET Configuration Wizard - Browse For Folder Dialog Box

In the Browse For Folder dialog box, you have the following choices:
• To use an existing directory for the cache, browse for and select that directory, and click OK.
• To create a new directory for the cache, browse to and select the directory in which the new
directory should be created. Click New Folder. Rename the new folder as appropriate,
verifying that the name is reflected in the Folder text box, then click OK.
Note: If you browse for a new path, that path is automatically added to the Paths list. If it
is a locally mapped drive on the AppXtender Admin server, remember that you need to
configure drive mapping to map the local path to a universally accessible UNC path under
the Storage > Paths node in AppXtender Admin. UNC paths, rather than mapped paths, are
recommended. For details on mapping drives for paths, refer to the Configuring Paths section
of the ApplicationXtender Core Components Administrator’s Guide.

ApplicationXtender Web Access .NET Administrator’s Guide 67

Using the AppXtender Web.NET Configuration Wizard

3. If the correct credentials are not already selected, select the appropriate credentials option for
the authentication account that is used when accessing the selected path. By default, global
credentials are set for a path.
Note: The Application authentication method is available only when all data sources in the data
source group are using the Application authentication method.
Note: If the selected path already exists in the AppXtender Admin Paths table, a credentials
option may already have been selected. If you change the credentials for a path here, the change
affects the credentials used for that path in any location where it is used, and the change is
reflected in the record for that path in the AppXtender Admin Paths table.
4. Click OK. (If the specified directory does not already exist, a message appears asking if you want
to create it. Click Yes. A message appears indicating that the new path was added to the Paths
configuration. Click OK.) The specified path appears in the Session Cache Path text box.
5. Click Test Connection. A message appears indicating whether the path could be verified. (For
information, see the table in Validating Configurations, page 69.) Click OK.
6. Click Next. (If the wizard was unable to verify the cache path, a message appears asking whether
you want to continue. Click Yes.)

Viewing the Configuration Summary

The Summary page of the wizard displays a list of the warnings generated as you advanced through
the wizard. For example, if you skipped parts of the wizard, a warning appears in the summary to
remind you which settings still remain to be configured.

Figure 33. AppXtender Web.NET Configuration Wizard - Summary Page

68 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

To complete the wizard:

1. Take note of any warnings listed on the Summary page. For information on each warning, see the
table in Validating Configurations, page 69.
2. Click Finish. A message appears asking whether you would like to save changes made by the
wizard.
3. Click Yes. The changes you have made within the wizard are reflected in AppXtender Admin.
After you have resolved the issues that caused the warnings, you can start the wizard again and
change the appropriate settings. For instructions, see Starting the Wizard, page 42.
You can also determine whether the warnings have been resolved without having to page through the
entire AppXtender Web.NET Configuration Wizard. For instructions, see Validating Configurations,
page 69.

Validating Configurations
You can check whether settings in AppXtender Admin are configured appropriately for AppXtender
Web.NET without having to page through the entire AppXtender Web.NET Configuration Wizard.

To validate configurations:
1. Start AppXtender Admin. For instructions, refer to .
2. From the Tools menu, select Validate Configurations. The Validate Configurations dialog box
appears.

Figure 34. AppXtender Admin Validate Configurations Dialog Box

3. Take note of any warnings listed. The following table lists possible warnings and provides
suggestions for resolving each one:

ApplicationXtender Web Access .NET Administrator’s Guide 69

Using the AppXtender Web.NET Configuration Wizard

Table 4. Suggestions for Each Possible Warning

Possible
Category Warnings Suggestion
Global Global Supply account information for the global
Credentials Credentials are authentication account. This account grants
not supplied security privileges to AppXtender Web in
instances where an authentication context
is required to access a resource and the
global credentials option is selected for that
resource. For instructions, see Configuring the
AppXtender Web Server Global Authentication
Account, page 79.
Unable to verify Check each of the following:
user name and • The domain name, user name, or password
password. may have been mistyped. Try reentering the
account information.

• The credentials may be local to the server

or do not have permission to log on locally.
Although this message appears on the local
computer, it does not reflect a problem with
access to the remote server. Test the user
account on the remote server by using that
account to log in on that server.

For instructions, see Configuring the

AppXtender Web Server Global Authentication
Account, page 79.
License The license server Check each of the following:
Server <License Server> • License Server has been installed on a
could not be computer that is network accessible.
contacted
• The License Server computer is running.

• The License Server service is running.

For instructions, refer to the Licensing

AppXtender Products chapter of the
ApplicationXtender Core Components
Administrator’s Guide.
The license group Associate the license group with a data
<license group> source instead. For instructions, refer to the
is associated with Modifying an Existing Data Source section
license server of the ApplicationXtender Core Components
<License Server>. Administrator’s Guide.

70 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Possible
Category Warnings Suggestion
Your License For each License Server connection that
Server connection is using Named Pipes, change to another
<server name> network transport.
is using Named
Pipes, which is
not supported
with AppXtender
Web.
Data Source The data source Make sure that the following characters are
<data source> not used in the data source name: backslash
does not have a (\), slash (/), colon (:), asterisk (*), question
valid data source mark (?), double quote ("), angle brackets
name (<>), or pipe (|). For instructions, refer
to the AppXtender Data Sources section
of the ApplicationXtender Core Components
Administrator’s Guide.
A schema must To use integrated security, you must specify the
be specified to data source schema. For instructions, refer to
use Integrated the Modifying an Existing Data Source section
Security of the ApplicationXtender Core Components
Administrator’s Guide.
You chose to use Create a connection to a License Server and
an Evaluation select that License Server connection for the
license server. It data source. If necessary, obtain a valid license
will expire in 30 and register it on the License Server. For
days. instructions, refer to the Licensing AppXtender
Products chapter of the ApplicationXtender Core
Components Administrator’s Guide.
Session Session Cache Specify a path to be used to store AppXtender
Management path is not Web user session data for active AppXtender
defined Web sessions. For instructions, see Configuring
AppXtender Web Server Session Cache, page
77.
<Specified session Select an authentication method (Application,
cache path>: Global, or Supplied) for the session cache path.
Credentials user If you select Supplied, you must specify user
name is not account information. For instructions, see
specified. Configuring AppXtender Web Server Session
Cache, page 77.
<Specified session Make sure that the specified path exists
cache path>: and the relevant authentication account has
Credentials test appropriate rights. For instructions, see
failed Configuring AppXtender Web Server Session
Cache, page 77.

ApplicationXtender Web Access .NET Administrator’s Guide 71

Using the AppXtender Web.NET Configuration Wizard

Possible
Category Warnings Suggestion
IIS Security IIS Security is not Specify how users may access AppXtender
configured. Web.NET Server. For instructions, see
Configuring AppXtender Web Access Security
Settings, page 80.
E-mail SMTP Server is Specify the server name or IP address of an
Settings not configured active SMTP server that can be used to relay
AppXtender Web messages. For instructions,
see Configuring E-Mail for AppXtender Web
Access, page 85.
E-mail address is Specify an e-mail address so that AppXtender
not configured Web.NET can send error messages to users.
For instructions, see Configuring E-Mail for
AppXtender Web Access, page 85.
AppXtender Rendering Service Specify a path where you want rendered
Rendering Cache is not files to be cached for repeated access. For
Server configured. instructions, see Configuring AppXtender
Rendering Server Cache Settings, page 35.
Credentials user Supply account information for the
name is not AppXtender Rendering Server authentication
configured. account. This account is used whenever the
AppXtender Rendering Server requires a
security context to access a resource. For
instructions, see Configuring an AppXtender
Rendering Server Login Account, page 33.
Unable to verify Check each of the following:
user name and • The domain name, user name, or password
password. may have been mistyped. Try reentering the
account information.

• The credentials may be local to the server

or do not have permission to log on locally.
Although this message appears on the local
computer, it does not reflect a problem with
access to the remote server. Test the user
account on the remote server by using that
account to log in on that server.

For instructions, see Configuring an

AppXtender Rendering Server Login Account,
page 33.
The AppXtender Make sure that the specified path exists
Rendering Server and the relevant authentication account has
cache path could appropriate rights. For instructions, see
not be verified. Configuring AppXtender Rendering Server
Cache Settings, page 35.

72 ApplicationXtender Web Access .NET Administrator’s Guide

 Using the AppXtender Web.NET Configuration Wizard

Possible
Category Warnings Suggestion
Paths <Specified path> Make sure that the specified path exists
path could not be and the relevant authentication account has
verified. appropriate rights. For instructions,refer
to the Configuring Paths section of
the ApplicationXtender Core Components
Administrator’s Guide.
<Path> is the root Make sure that the session cache path is not
of <path> being used as the render cache path and vice
versa.
Storage Your DiskXtender For each DiskXtender connection that is using
connection Named Pipes, change to another network
<server name> transport.
is using Named
Pipes, which is
not supported
with AppXtender
Web.

4. Click Close.

ApplicationXtender Web Access .NET Administrator’s Guide 73

Using the AppXtender Web.NET Configuration Wizard

74 ApplicationXtender Web Access .NET Administrator’s Guide

 Chapter 4
Configuring AppXtender Web Access
Settings

Prior to installing and registering AppXtender Web Access Server, you must configure any mandatory
AppXtender Web Access Server settings in AppXtender Admin.
Note: If you are implementing a 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. This chapter describes how to use the AppXtender Admin tree to
set up AppXtender Web.NET in your AppXtender system. For instructions on configuring these
settings in the AppXtender Web.NET Configuration Wizard, see Chapter 3, Using the AppXtender
Web.NET Configuration Wizard.
This chapter provides configuration procedures for both required and optional AppXtender Web
Server settings. For information on configuring AppXtender Web Server settings, see the following
sections:
• Understanding Required vs. Optional Settings, page 75
• Configuring AppXtender Web Access Setup Settings, page 77
• Configuring AppXtender Web Access Security Settings, page 80
• Configuring AppXtender Web File Type Map Settings, page 81
• Configuring E-Mail for AppXtender Web Access, page 85
•
• Monitoring Configuration Updates, page 96
• Configuring Client Download of JRE, page 98
• Configuring Thumbnails, page 99
• Configuring AppXtender Web Logging, page 102

Understanding Required vs. Optional Settings

You must configure a subset of the configuration options for AppXtender Web before installing and
registering the AppXtender Web Server. Other optional settings can be modified, but the AppXtender
Web Server can run if those settings remain in the default configuration.

ApplicationXtender Web Access .NET Administrator’s Guide 75

Configuring AppXtender Web Access Settings

The following sections list the required settings and the optional settings.
• Required AppXtender Web Access Server Configuration, page 76
• Optional AppXtender Web Access Server Configuration, page 76

Required AppXtender Web Access Server Configuration

For AppXtender Web.NET, you must configure the User Account and Session Cache Path settings
under the AppXtender Web > Setup node before you install and register the AppXtender Web.NET
Server. If users will be using email options in AppXtender Web, you must also configure an
administrative email address for the server. The following sections provide details on configuration
procedures for each of these required settings:
• Configuring AppXtender Web Server Session Cache, page 77
• Configuring the AppXtender Web Server Global Authentication Account, page 79
• Setting AppXtender Web Administrator E-Mail Information, page 87

Optional AppXtender Web Access Server Configuration

There are additional AppXtender Web settings you can configure to manage the behavior of
AppXtender Web functionality. You can configure file types to force AppXtender Web to treat a
file with a particular extension as a specific file type. You can also control the length of time a
AppXtender Web session remains available before timing out from inactivity. To use the email
features in AppXtender Web, you need to configure an email address for the AppXtender Web
administrator. You also need to configure an SMTP server.
You can also prevent Web Access users from running application queries with no criteria, which
improves search performance and helps to prevent potential timeouts. This capability is available
using the ApplicationXtender Data Source Features wizard. Refer to the “Managing Existing
Applications” appendix of the ApplicationXtender Core Components Administrator’s Guide.
For AppXtender Web.NET deployments, AppXtender Web Security settings control what user
authentication methods are used when clients connect to the AppXtender Web.NET Server.
For AppXtender Web.NET installations, see the following sections for information on optional
settings you may want to configure for your deployment:
• Configuring Session Data Management, page 78
• Configuring AppXtender Web Access Security Settings, page 80
• Configuring AppXtender Web File Type Map Settings, page 81
• Configuring E-Mail for AppXtender Web Access, page 85
• Monitoring Configuration Updates, page 96
• Configuring Client Download of JRE, page 98
• Configuring Thumbnails, page 99
• Configuring AppXtender Web Logging, page 102

76 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Configuring AppXtender Web Access Setup

Settings
The configuration options available under the AppXtender Web > Setup node allow you to designate
the path for the AppXtender Web session cache, adjust the length of time sessions remain active
before timing out, and set the AppXtender Web global authentication account.
See the following sections for more information:
• Configuring AppXtender Web Server Session Cache, page 77
• Configuring Session Data Management, page 78
• Configuring the AppXtender Web Server Global Authentication Account, page 79

Configuring AppXtender Web Server Session Cache

The AppXtender Web Server session cache stores AppXtender Web user session data for active
AppXtender Web sessions. Session data includes authorization and authentication data for user
sessions and user session context for operations a user is engaged in.

To set the Session Cache Path for AppXtender Web:

1. In AppXtender Admin, expand the AppXtender Web node.
2. Select Setup. AppXtender Web Setup options appear in the right pane of the window.

Figure 35. AppXtender Admin - AppXtender Web > Setup Node

3. In the Session Cache Path section, select the Browse button to the right of the text box. The
Local Path Setup dialog box appears.
4. From the Path list, select the appropriate path for the cache used by AppXtender Web Server, or
click Browse to browse for a new path.

ApplicationXtender Web Access .NET Administrator’s Guide 77

Configuring AppXtender Web Access Settings

Figure 36. AppXtender Admin - Local Path Setup Dialog Box

5. If the correct credentials are not already selected, select the appropriate credentials option for
the authentication account that is used when accessing the selected path. By default, global
credentials are set for a path.
Note: If the selected path already exists in the AppXtender Admin Paths table, a credentials
option may already have been selected. If you change the credentials for a path here, the change
affects the credentials used for that path in any location where it is used, and the change is
reflected in the record for that path in the AppXtender Admin Paths table.
6. Click OK.
7. If you chose to add the path, it appears in the Session Cache Path text box.
A message appears prompting you to configure the new path under the Paths section in
AppXtender Admin. For more information on configuring paths, refer to the Configuring Paths
section of the ApplicationXtender Core Components Administrator’s Guide.
8. Specify whether you want AppXtender Web to automatically logout the user when the user
closes the main browser window.
9. Select File> Save Changes to save all changes since the last save.

Configuring Session Data Management

The AppXtender Web Session Time-Out (Minutes) setting controls the management of session data.
This setting sets the duration of session idle time that AppXtender Web allows to elapse before
closing inactive user sessions. For example, if AppXtender Web Session Time-Out (Minutes) is set
to 30, user sessions will terminate after 30 minutes of user inactivity. The default Session Time-Out
setting is 20 minutes.

To change the Session Time-Out amount:

1. In the Session Management section under AppXtender Web> Setup, enter the number of minutes
you want in the spin box next to AppXtender Web Session Time-Out (Minutes).

78 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 37. AppXtender Admin - AppXtender Web Session Management

2. Select File> Save Changes to save all changes since the last save.

Configuring the AppXtender Web Server Global

Authentication Account
The AppXtender Web global authentication account grants security privileges to AppXtender
Web in instances where an authentication context is required to access a resource and the global
credentials option is selected for that resource. Because an actively logged on account is not required
for AppXtender Web to be running, some security context must be established – this context is
established through the use of an authentication account.
You can configure specific resource authentication methods for many of the resources that
AppXtender Web accesses in the course of processing client requests. The credentials specified for a
resource are used whenever AppXtender Web needs to provide authentication account information
in order to access a resource.
Whenever global credentials are configured for a resource, AppXtender Web uses the global
credentials that you specify to access the resource. Resources for which you can configure credentials
include remote and server resources on Windows, such as the AppXtender Web Session Cache,
the data sources through which AppXtender Web connects to databases, and DiskXtender (DX)
document servers. The global account is also used for authentication if needed when accessing
the registry or the License Server. The ASPNET user and any authentication accounts used by
AppXtender Web resources, including the global account, must have the appropriate permissions
detailed in the Accounts and Rights Required for Resource Authentication Accounts section of
the ApplicationXtender Concepts Guide.
Note: AppXtender Rendering Server uses the account configured under the Services> AppXtender
Rendering Server settings to access the image repository.
You can configure credentials settings elsewhere in AppXtender Admin to override the use of the
global account for authentication. However, any accounts that are used to provide credentials
as an authentication context for AppXtender Web resources must have the rights to access to
those resources. To make sure you have access to all resources, the easiest approach is to use the
AppXtender Web global account to impersonate for all AppXtender Web resources, and make sure
that this account has access to all resources and appropriate rights.

To configure the global AppXtender Web authentication account:

1. Expand the AppXtender Web node in AppXtender Admin and then select Setup.
2. In the Global Credentials Account section, click Setup.

ApplicationXtender Web Access .NET Administrator’s Guide 79

Configuring AppXtender Web Access Settings

Figure 38. AppXtender Admin - AppXtender Web Global Credentials Account

The Enter user credentials dialog box appears.

Figure 39. AppXtender Admin - Enter User Credentials Dialog Box

3. In the User Name text box, enter the full name for the user account that should be used as the
global authentication account, using the following syntax: domain_name\username.
4. In the Password text box, enter the password for the account.
5. In the Confirm Password text box, re-enter the same password to confirm the spelling.
6. Click OK.
A message may appear indicating that the credentials could not be verified. This message may
appear for a variety of reasons, including the following:
• The domain name, user name, or password may have been mistyped. Try reentering the
account information.
• The credentials may be local to the server or do not have permission to log on locally.
Although this message appears on the local computer, it does not reflect a problem with
access to the remote server. Test the user account on the remote server by using that account
to log in on that server.
7. Select File> Save Changes to save changes.

Configuring AppXtender Web Access Security

Settings
The AppXtender Web Security section allows you to configure settings that control the authentication
methods used by browser clients when accessing the AppXtender Web.NET Server. The settings that
you should choose depend on the credentials you select for AppXtender Web.NET system resources.
For more information on credentials and security settings, refer to the Planning AppXtender Security
chapter of the ApplicationXtender Concepts Guide.

To configure AppXtender Web.NET Security settings:

1. Expand the AppXtender Web node in AppXtender Admin and then select Security.

80 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 40. AppXtender Admin - AppXtender Web > Security Node

2. To cause users logging into the AppXtender Web.NET Server to be authenticated first through
Windows security, enable the Users may access the server using NTLM Authentication option.
Windows authentication occurs if the user is connecting from a Windows computer that belongs
to the same domain as the AppXtender Web.NET Server or a trusted domain, and if the Users
may access the server via Anonymous user account option is disabled.
3. To allow users accessing the AppXtender Web.NET Server to be authenticated anonymously,
enable the Users may access the server via Anonymous user account option. Anonymous
authentication occurs through the Network Service.
4. To cause AppXtender Web.NET to attempt to automatically log a user authenticated through
NTLM when the default data source is using the Windows security provider, enable the
Automatic Login option under the Windows Security Login Options section.
5. To automatically request full-text capabilities when a user is automatically logged in through
the setting configured in Step 4, enable the Request Full-Text License option in the Automatic
Login Options section.

Configuring AppXtender Web File Type Map

Settings
The File Type Map node provides options for importing files into AppXtender Web.
AppXtender Web natively supports many file types such as TIFF, Windows bitmaps, TGA, RTF, JPEG,
GIF, PCX, and DCX. By default, files not natively supported by AppXtender Web are imported as
foreign files. Depending on the AppXtender Web configuration, pages that have been imported as

ApplicationXtender Web Access .NET Administrator’s Guide 81

Configuring AppXtender Web Access Settings

foreign files can be displayed in the AppXtender Web Document Display window in the following
ways:
• As an icon.
• In their native applications.
• Through the AppXtender KeyView component (available only with AppXtender Web IRC). For
details, refer to the ApplicationXtender Web Access User’s Guide.
• In an embedded Office Viewer (available only with AppXtender Web IRC for supported Microsoft
Office 2003 and 2007 documents). Microsoft Office must be installed on the client machine and
the KeyView setting must be enabled. For details, refer to the ApplicationXtender Web Access
User’s Guide.
Note: The KeyView Viewer component does not need to be installed on the client machine to
use the embedded Office Viewer.
• Using the Render foreign files as HTML option (available only with AppXtender Web Thin Client).
For details, see Enabling Foreign File HTML Conversion, page 39.
For example, if a user adds a Microsoft Word document to AppXtender Web as a new document, a
Word icon would appear as the AppXtender Web page. Users would then double-click the icon to
launch Microsoft Word and to view the document. The File Type page provides options for importing
file types or extensions.
PDF support is available with AppXtender Web, but users must download the AppXtender Adobe
Component to view PDF documents in their native format. For instructions, refer to the Customizing
Your AppXtender Web Workstation chapter of the ApplicationXtender Web Access User’s Guide.
Note: If you are having trouble viewing a document using Acrobat, try opening Acrobat manually
once before retrieving the document using AppXtender Web.
By default, most text pages are imported as plain text, but some may be imported as foreign files. If
you want to import all files with a TXT extension as plain text, add this file type in the File Types tab.
Note: Because text files saved as ANSI format (MBCS) do not contain locale information, AppXtender
and AppXtender Web auto-recognize them as text only if the content in the file is pure US ASCII
characters. To force AppXtender to import a text file as text, you must set up file type mapping in
AppXtender Admin before importing the text files. For example, map the TXT extension to the
text file type.
Note: When users import text files, AppXtender and AppXtender Web use the following procedure
to identify the code page for the text file:
• Determine whether the file name contains a language specifier. For example, if the file name
for a Chinese text file is xxx.[zh-CN].txt, the language specifier [zh-CN] denotes the Simplified
Chinese code page. AppXtender supports common Western European languages, Chinese (both
simplified and traditional), Japanese, and Korean.
• If the file name does not contain a language specifier, AppXtender uses the current operating
system ANSI code page and AppXtender Web uses the current thread culture for its text codepage.
Once imported, all text files are stored internally as UTF-8 and can be displayed in any operating
system correctly.
Note: Microsoft Word documents can be brought into AppXtender as OLE Objects, in which case
the File Types settings do not matter. File Types settings only apply when a document or page is
uploaded to AppXtender Web or imported into AppXtender using the Import File command.

82 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Note: AppXtender Web does not support progressive JPEGs. Importing a progressive JPEG into
AppXtender Web will result in the file being imported as a foreign file.

Figure 41. AppXtender Admin - AppXtender Web > File Type Map Node

For more information about the options available through the File Type Map node, see the following
sections:
• Adding File Types, page 83
• Modifying a File Type, page 84
• Deleting a File Type, page 85

Adding File Types

You can add a file type mapping to AppXtender Web so that file type can be displayed in its native
format.

To map a new file type:

1. In the AppXtender Admin tree, expand the AppXtender Web node and then select File Type Map.
2. In the File Type Map pane, click Add. The File Types dialog box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 83

Configuring AppXtender Web Access Settings

Figure 42. AppXtender Admin - File Types Dialog Box

3. In the Extension text box, enter the extension for the type of file that you want to map.
4. From the File Type list, select the file type that you want to associate with the extension that
you entered.
5. Click OK. The file type association is added to the File Type Map list.

Figure 43. AppXtender Admin - AppXtender Web > File Type Map Node

6. Select File> Save Changes to save all changes since the last save.

Modifying a File Type

You can view or modify properties for an existing file type mapping.

To view or modify properties for a file type mapping:

1. In the AppXtender Admin tree, expand the AppXtender Web node and then select File Type Map.
2. In the File Type Map list, select the file type mapping that you want to modify.
3. Click Properties. The File Types dialog box appears.

84 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 44. AppXtender Admin - File Types Dialog Box

4. To modify the mapping, select a new file type from the File Type list.
5. Click OK.
6. Select File> Save Changes to save all changes since the last save.

Deleting a File Type

You can remove any previously added file type.

To remove a file type mapping:

1. In the AppXtender Admin tree, expand the AppXtender Web node and then select File Type Map.
2. In the File Type Map list, select the file type mapping that you want to delete.
3. Click Remove. A confirmation message appears, asking you to confirm the deletion.
4. Click Yes.
5. Select File> Save Changes to save all changes since the last save.

Configuring E-Mail for AppXtender Web Access

The E-Mail node allows you to configure settings so that users can e-mail documents and pages, or
references to documents and pages using AppXtender Web.
To use e-mail features for AppXtender Web, you need to designate an SMTP server and add an
administrator’s e-mail address.

Caution: You must have an active mail server available to relay SMTP messages, such as the
SMTP service on your local AppXtender Web IIS server or your corporate mail server, for the
AppXtender Web e-mail function to work.

ApplicationXtender Web Access .NET Administrator’s Guide 85

Configuring AppXtender Web Access Settings

Figure 45. AppXtender Admin - AppXtender Web > Email > Setup Node

For more information about configuring the E-Mail page, see the following sections:
• Designating an SMTP Server for E-Mail, page 86
• Setting AppXtender Web Administrator E-Mail Information, page 87
• Managing E-Mail Addresses, page 88

Designating an SMTP Server for E-Mail

The E-Mail SMTP Server section of the AppXtender Web > E-Mail> Setup pane allows you to
designate the SMTP Server that will be used to relay messages for the AppXtender Web Server,
enabling use of e-mail features.

Figure 46. AppXtender Admin - AppXtender Web Email SMTP Server

Caution: The SMTP server you select must be installed and running. Also, for AppXtender
Web.NET, the SMTP server you select must allow relay of messages for the AppXtender Web
Server. For more information on enabling relay of messages, see Configuring the Default SMTP
Virtual Server for Use with AppXtender Web.NET, page 28.

To select an SMTP Server to relay messages for AppXtender Web:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail node. When the E-Mail
node is expanded, the Setup subnode is automatically selected and the E-Mail Setup pane appears.

86 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 47. AppXtender Admin - AppXtender Web > Email > Setup Node

2. In the E-Mail SMTP Server section, enter the server name or IP address of an active SMTP server
that can be used to relay AppXtender Web messages in the Server Name text box.
3. Select File > Save Changes to save the changes.

Setting AppXtender Web Administrator E-Mail

Information
The AppXtender Web Administrator E-Mail Information section of the E-Mail Setup page allows you
to designate the AppXtender Web administrator display name and the administrator’s e-mail address.
This information is used as the “from:” line in messages sent from the system to users for registration,
and is the default e-mail address used for any mail-related error messages.

Figure 48. AppXtender Admin - AppXtender Web Administrator Email

To edit AppXtender Web administrator e-mail Information:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail node. When the E-Mail
node is expanded, the Setup subnode is automatically selected and the E-Mail Setup pane appears.

ApplicationXtender Web Access .NET Administrator’s Guide 87

Configuring AppXtender Web Access Settings

Figure 49. AppXtender Admin - AppXtender Web> Email> Setup Node

2. Click the Modify button. The E-Mail Address dialog box appears.

Figure 50. AppXtender Admin - Email Address Dialog Box

3. Enter the name you wish to display in the From field of the email in the Display Name text box.
4. Enter the administrator’s e-mail address, in SMTP format ([email protected]), in the E-Mail
Address text box.
5. Click Save And Close to apply your changes.
6. Select File > Save Changes to save the changes.

Managing E-Mail Addresses

Global e-mail addresses can be added through the AppXtender Web > E-Mail > Addresses node. All
AppXtender Web users can then use these e-mail addresses.
The AppXtender Web E-Mail Addresses list also allows you to import e-mail addresses that have
been exported in comma-delimited or tab-delimited format from other e-mail clients (such as
Microsoft Outlook). Addresses that have been added globally to AppXtender Web can be exported to
comma-delimited or tab-delimited files as well.

88 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

For more information, see the following sections:

• Adding an E-mail Address, page 89
• Modifying an Existing E-Mail Address, page 90
• Deleting E-Mail Addresses, page 91
• Importing Addresses from a File, page 93
• Exporting E-mail Addresses to a File, page 95
• Sorting E-Mail Addresses, page 95

Adding an E-mail Address

When you add an email address to the list, you make that address available to all AppXtender
Web users.

To add a new global e-mail address:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

Figure 51. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Click Add to add a new email address. The Email Address dialog box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 89

Configuring AppXtender Web Access Settings

Figure 52. AppXtender Admin - Email Address Dialog Box

3. In the Display Name text box, enter the “friendly” name that corresponds to the e-mail address
(such as Alice Anderson).
4. In the E-Mail Address text box, enter the e-mail address in SMTP format (such as
[email protected]).
5. Click Save and New to add the e-mail address. The address appears in the Addresses list. Repeat
these steps for each e-mail address you want to add.
6. Click Save and Close to add the last e-mail address and close the dialog box.
7. Select File > Save Changes to save the changes.

Modifying an Existing E-Mail Address

You can make changes to an e-mail address that has already been added.

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

Figure 53. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Select the e-mail address you want to modify and click Edit.

90 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 54. AppXtender Admin - Email Address Dialog Box

3. In the Display Name text box, make changes to the “friendly” name that corresponds to the
e-mail address (such as Alice Anderson) as needed.
4. In the E-Mail Address text box, make changes to the e-mail address in SMTP format (such as
[email protected]) as needed.
5. Click Save and Close to save the changes to the e-mail address. The modified address re-appears
in the Addresses list. Repeat these steps for each e-mail address you want to modify.
6. Select File > Save Changes to save the changes.

Deleting E-Mail Addresses

You can delete an individual e-mail address from the list or delete all listed addresses at once.
For more information, see the following sections:
• Deleting an Individual E-Mail Address, page 91
• Deleting All Listed E-Mail Addresses, page 92

Deleting an Individual E-Mail Address

When you delete a specific address, only the selected address is deleted.

To delete a specific address:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

ApplicationXtender Web Access .NET Administrator’s Guide 91

Configuring AppXtender Web Access Settings

Figure 55. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Select the e-mail address you want to delete and click Delete. The selected address is deleted
from the Addresses list. Repeat this step for each e-mail address you want to delete.
3. Select File > Save Changes to save the changes.

Deleting All Listed E-Mail Addresses

When you select the Delete All option, all addresses in the list are deleted, regardless of the current
selection.
When you delete all addresses in the list, you force each user to re-register their email address the
next time they use a AppXtender Web email feature.

To delete all addresses:

1. In the AppXtender Admin tree, expand the AppXtender Web> E-Mail> Addresses node. The
Addresses list appears in the pane on the right.

92 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 56. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Select the e-mail address you want to delete and click Delete All. All addresses in the Addresses
list are deleted.
3. Select File > Save Changes to save the changes.

Importing Addresses from a File

You can save time by importing a list of e-mail addresses in Outlook format. You can import an
address book in comma-delimited (Outlook CSV) or tab-delimited (Outlook CSV) format that has
been exported from Outlook. For more information on exporting an address book from Outlook,
refer to the Microsoft Outlook documentation.

To import addresses from an Outlook address book:

1. Export contacts from your Outlook address book into a file using either comma-delimited
(Outlook CSV) or tab-delimited (Outlook CSV) format.
2. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

ApplicationXtender Web Access .NET Administrator’s Guide 93

Configuring AppXtender Web Access Settings

Figure 57. AppXtender Admin - AppXtender Web > Email > Addresses Node

3. Click Import. The Import Address Book dialog box appears.

Figure 58. AppXtender Admin - Import Address Book Dialog Box

4. In the Format drop-down list, select Comma-Delimited or Tab-Delimited format (depending on

what format you chose to export addresses from your e-mail client).
5. To overwrite all existing global addresses, enable the Overwrite Existing check box.
6. To have AppXtender Web verify whether the address syntax is correct, enable the Verify Address
Syntax check box.
Note: If Verify Address Syntax is enabled, you will be prompted to accept or reject any e-mail
addresses with syntax that AppXtender Web discovers to be incorrect. From the dialog box that
appears when AppXtender Web encounters an address with incorrect syntax, you can click Yes to
accept the address, No to reject the address, or Cancel to cancel the import.
7. Select the Browse button next to the File text box to locate the import file you created. The Open
dialog box appears.
8. Browse to the file that you want to use and click Open.
9. Click OK. The addresses are imported and appear in the Addresses list.

94 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

10. Select File > Save Changes.

11. Optionally, sort the email address list using the procedures in Sorting E-Mail Addresses, page 95.

Exporting E-mail Addresses to a File

You can export the listed addresses to a file for use with other e-mail clients.

To export AppXtender Web global addresses to a file:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

Figure 59. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Click Export. The listed email addresses are exported to a file in a comma-delimited (CSV) format.

Sorting E-Mail Addresses

When you import email addresses into the global address book, the email address list is not sorted by
default. Sorting the email address list after importing it into the global address book makes it easier
for Web Access users to locate an email address. The email address list can be sorted by name or by
email address, in either ascending or descending order.

To sort email addresses:

1. In the AppXtender Admin tree, expand the AppXtender Web > E-Mail > Addresses node. The
Addresses list appears in the pane on the right.

ApplicationXtender Web Access .NET Administrator’s Guide 95

Configuring AppXtender Web Access Settings

Figure 60. AppXtender Admin - AppXtender Web > Email > Addresses Node

2. Click either the Name or Email Address column header, as desired, to sort the list of addresses.
3. To reverse the sort order, click the header again.
4. Select File > Save Changes to save the changes.
ApplicationXtender Web Access users can also sort addresses in the email address book when they
choose to email documents from the query results set page or from Document Display view. Refer to
Sending an E-Mail in the EMC ApplicationXtender Web Access User’s Guide for more information.

Monitoring Configuration Updates

AppXtender web applications (AppXtender Web Access, 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. For details, see Types and Effect of Configuration
Updates, page 97.
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.
Note: The default configuration monitoring settings are the recommended settings and will suffice in
most cases.

To change configuration monitoring settings:

1. Back up the existing web.config file, which is located in C:\Inetpub\wwwroot\AppXtender
by default.
2. In a text editor, open the web.config file.
3. Specify how often the web site should poll the configuration database to detect any configuration
updates, by editing nnnnn in the following line of text:
<add key="ConfigMonitorPollFrequency" value="nnnnn" />

96 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

By default, the nnnnn value is set to 60 seconds. (Values are entered in milliseconds). To turn off
this feature, set this value to 0. The minimum acceptable value for this key is 10000. Polling more
frequently than once every 10 seconds may degrade performance.
4. Specify the behavior of the web application when a configuration update is detected that requires
a web application restart, by editing ModeValue in the following line of text:
<add key="ConfigMonitorRestartMode" value="ModeValue" />
By default, the ModeValue value is set to PendingSession. The following table describes
each of the possible values that you can enter:

Table 5. Configuration Monitor Restart Modes

Restart Mode Description

Immediate Immediately restarts the web application. This mode
has the same effect as the Configuration Monitor service
available in releases of AppXtender web applications
previous to 5.30.
PendingSession Recycles the process when one of the following two
conditions occurs:
• When all the users have logged out.

• When the session time-out period has elapsed since the

configuration update was detected.

With this mode, web pages indicate that an application

restart is pending.
Never Does not restart the web application. This mode allows
administrators to manually perform the restart at their
own convenience.

5. Save the changes.

Types and Effect of Configuration Updates

The following table describes how configuration updates will be handled by the web application as it
monitors for configuration updates. Real-time 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 6. 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.

ApplicationXtender Web Access .NET Administrator’s Guide 97

Configuring AppXtender Web Access Settings

Configuration Update Effect of the Update

Data Sources (without dropping Real-time update when change is detected.
any existing data sources) Re-login required to detect change.
Data Sources (Data source is Application Restart
deleted or becomes hidden)
Dual Write Paths Real-time update when change is detected
DiskXtender Servers Real-time update when change is detected
Document Signing Real-time update when change is detected
AppXtender Web (Session path Real-time
does not change)
AppXtender Web (Session path Application Restart Scheduled
change)
File Type Map Real-time update when change is detected
Email Address book Real-time update when change is detected
Authentication Service Requires restart
Authorization Service Requires restart
AppXtender Rendering Server Real-time update when change is detected
Settings
AppXtender RM Service Application Restart

Note: If there are any changes in AppXtender AppGen, you must restart IIS manually.

Configuring Client Download of JRE

By default, when an AppXtender Web user attempts to use thumbnails or cross-application queries, if
JRE has not already been downloaded, the user is prompted to download JRE.

Caution: If you change JRE download configuration, you must already understand how applets
work with Java Virtual Machine (JVM) on clients.

To configure client download of JRE for AppXtender Web.NET:

1. Navigate to C:\Inetpub\wwwroot\AppXtender\client and open the version.xml file
for editing.
2. Enter plugin class ID and plugin CAB file values that correspond to the version of JRE that
you want the AppXtender Web.NET users to use. For details, refer to technical sections for the
applets on the java.sun.com and oracle.com sites.
3. Restart IIS.
The next time a user attempts to launch thumbnail or cross-application-query applets, the applets will
load JVM based on your configuration.

98 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Configuring Thumbnails
AppXtender Web users can choose to display thumbnails of retrieved document pages so that they
can browse the contents of documents without having to download each page. The thumbnails
contact sheet allows users to reorder page(s) within a document. Users can also resize document
thumbnails from 50 to 300 percent of the original thumbnail size. Zoom settings are retained for
the remainder of the user’s Web Access session. The following screen capture illustrates a sample
thumbnails contact sheet.

Figure 61. Thumbnails Contact Sheet: Reordering and Resizing Document Pages

In addition to user-controlled settings for thumbnails, you can modify the default size of the
Thumbnails view and thumbnails contact sheet. You can also change the default viewer that is used
to display document thumbnails in AppXtender Web Access. These settings apply to all Web Access
users. The following sections describe how to perform these tasks.

Resizing Thumbnail Views

Both the Thumbnails view (which displays next to Document Display view in Web Access) and the
thumbnails contact sheet are 100 pixels wide by default. You can change the width of these views
by modifying the DocViewThumbnailViewSize key in the web.config file. For example, if you
change the default value of 100 to 150, the width of both the Thumbnails view and the thumbnails

ApplicationXtender Web Access .NET Administrator’s Guide 99

Configuring AppXtender Web Access Settings

contact sheet is changed to 150 pixels. Web Access adjusts the height of these views automatically
based on the width you specify. Alternatively, you can specify a fixed value for the height of these
views by adding a height value to the key using the format width, height. For example, a value of
100,60 specifies a width of 100 pixels and a height of 60 pixels for these views.
You can also set the Thumbnails view and thumbnails contact sheet to two different sizes, if desired,
by adding a second set of values to the DocViewThumbnailViewSize key and separating the
settings using a semi-colon. In this case, the first set of values controls the size of the Thumbnails view
and the second set controls the thumbnails contact sheet. For example, 100;120 specifies that the
Thumbnails view should be 100 pixels wide and the thumbnails contact sheet should be 120 pixels
wide. The height of the views adjusts automatically. If desired, you can specify a fixed value for the
height for each view. For example, 100,150;90,120 specifies that the Thumbnails view is 100
pixels wide by 150 pixels high and the thumbnails contact sheet is 90 pixels wide by 120 pixels high.
To change the default size of thumbnail views, use a text editor to edit the web.config file on the Web
Access server. This file is located in C:\Inetpub\wwwroot\AppXtender by default.
The following excerpt from the web.config file illustrates the default width of 100 pixels for the
Thumbnails view and thumbnails contact sheet. In the file, the term thumbnail bar represents the
Thumbnails view.
<!-- Document View Thumbnail Size "width" or "width, height"
Use semicolon to set different sizes for Thumnail Bar and Contact Sheet
e.g. "thumbnail bar width, thumbnail bar height; contactsheet width,
contactsheet height" -->
<add key="DocViewThumbnailViewSize" value="100" />

Note: Modified web.config file settings apply to all Web Access users.

Changing the Default Viewer for Document Thumbnails

The default viewer that is used to display document thumbnails in AppXtender Web Access is
Microsoft Silverlight. You can change the viewer to Java, if desired, by changing the value for the
ViewThumbnailApp key from Silverlight to Applet in the web.config file. This file is located in
C:\Inetpub\wwwroot\AppXtender on the Web Access server by default.
The following excerpt from the web.config file illustrates the default viewer setting of Silverlight.
<!-- Thumbnail Viewer application type, options are "Silverlight" or "Applet" -->
<add key="ViewThumbnailApp" value="Silverlight" />

The following figure shows an example of the Thumbnails view and its associated Document Display
view using the Silverlight viewer.

100 ApplicationXtender Web Access .NET Administrator’s Guide

 Configuring AppXtender Web Access Settings

Figure 62. Document Display View with Thumbnails View of Document Pages: Silverlight viewer

The following figure shows an example of the Thumbnails view and its associated Document Display
view using the Java viewer.

Figure 63. Document Display View with Thumbnails View of Document Pages: Java viewer

Note: Modified web.config file settings apply to all Web Access users.

ApplicationXtender Web Access .NET Administrator’s Guide 101

Configuring AppXtender Web Access Settings

Configuring AppXtender Web Logging

The Microsoft .NET Framework component allows you to configure trace logs for the AppXtender
Web.NET system. To change the default trace log settings, use a text editor to edit the web.config
file on the Web Access server. The Web Access installation wizard installs the web.config file in the
following directory:
\Inetpub\wwwroot\AppXtender
Refer to the Microsoft Developer Network Web site at msdn.microsoft.com for more information
on how to configure trace logs.

102 ApplicationXtender Web Access .NET Administrator’s Guide

 Chapter 5
Installing and Registering AppXtender
Web Access Components

An AppXtender Web Access (AppXtender Web) system has several components that can be installed
on a single computer or deployed on several computers to take advantage of distributed processing
by multiple computers. Each of those components is installed using a setup wizard. The wizard takes
you step-by-step through the installation process.
After installing each of these components, you need to register each component with a database for
the data source. Registering each component creates a connection between AppXtender Admin and
the component, so the component’s settings (which are configured through AppXtender Admin) are
conveyed to the component.
For more information about AppXtender Web component installation, see the following sections:
• Before Running Setup, page 103
• Installing AppXtender Web Access Components, page 104
• Installing Client Components, page 117
• Preparing AppXtender Web Component Servers as Database Clients, page 117
• Starting Registration of AppXtender Web Access Components, page 130
• Locating a Data Source, page 131
• Completing Registration of AppXtender Web Access Components, page 140
• Testing the AppXtender Components, page 147

Before Running Setup

There are several steps you must take prior to installing and registering AppXtender Web.NET
Server and AppXtender Rendering Server, including installing AppXtender Admin and AppXtender

ApplicationXtender Web Access .NET Administrator’s Guide 103

Installing and Registering AppXtender Web Access Components

AppGen, creating a centralized database, and using AppXtender Admin to configure environment
settings and AppXtender Web Server and AppXtender Rendering Server settings, among other tasks.
• For a checklist of items that must be installed and configured prior to AppXtender Web Server and
AppXtender Rendering Server installation, see AppXtender Web Access Deployment Overview,
page 15.
• For information on AppXtender Web Server settings that should be configured prior to running
AppXtender Web Server setup, see Understanding Required vs. Optional Settings, page 75.
• For information on AppXtender Rendering Server settings that should be configured prior to
running AppXtender Rendering Server setup, see Chapter 2, Configuring AppXtender Rendering
Server.

Installing AppXtender Web Access

Components
After performing the preparatory steps outlined in Before Running Setup, page 103, you can install
AppXtender Web components. For instructions, see the following sections:
• Installing AppXtender Rendering Server, page 104
• Installing AppXtender Web.NET Access Server, page 109

Installing AppXtender Rendering Server

After performing the preparatory steps outlined in Preparing the AppXtender Rendering Server,
page 22 and in Chapter 2, Configuring AppXtender Rendering Server, you can set up rendering
services for your data source group. To do so, install the AppXtender Rendering Server on the
computer you want to use as the AppXtender Rendering Server. After installing the AppXtender
Rendering Server, you need to register the server with the data source group using the AppXtender
Component Registration wizard.
AppXtender Rendering Server setup installs the AppXtender Rendering Server service on the
AppXtender Rendering Server computer. You can install multiple AppXtender Rendering Servers
for a single data source group to improve rendering efficiency.
Note: On most screens in the setup wizard, you can click Back to return to the previous step, Next to
advance to the next page or Cancel to abort the installation. There are no files copied and no registry
or system changes made until the initial steps of the setup wizard are complete.

To install AppXtender Rendering Server:

1. Log in as a user with administrative rights on the AppXtender Rendering Server computer.
2. Close all open applications.
3. Obtain the installation files for AppXtender Rendering Server. You can either:
• Download the RenderingServer_6.5.xxx.zip file from the EMC download center at
http://Powerlink.EMC.com to a temporary directory on your computer. Extract the installer

104 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

zip file to the temporary directory. If you download multiple products, download all of them
to the same temporary directory.
• Insert the disc containing the AppXtender Desktop/Web setup files into your media drive.
4. In the temporary directory or media drive, navigate to the AppXtender Rendering Server
directory and double-click the AppXtender Render Server.msi file.
If a previous release of AppXtender Rendering Server (or any AppXtender product) is already
installed, a message appears indicating that the AppXtender Rendering Server cannot be installed
until the previous release is uninstalled.
The InstallShield Wizard appears and begins the setup process. If any required components are
missing, the InstallShield Wizard prompts you to confirm the installation and then continues the
setup process. When all required components have been installed, the AppXtender Rendering
Server Setup wizard appears, starting with the Welcome page.

Figure 64. AppXtender Rendering Server Setup - Welcome Page

5. Click Next. The License Agreement page appears.

ApplicationXtender Web Access .NET Administrator’s Guide 105

Installing and Registering AppXtender Web Access Components

Figure 65. AppXtender Rendering Server Setup - License Agreement Page

6. Read the agreement, select I accept the terms in the license agreement, and click Next. The
Customer Information page appears.

Figure 66. AppXtender Rendering Server Setup - Customer Information Page

The User Name and Organization fields are self-populated, but you are able to make changes
to that information on this screen.
7. Specify who may use the application on the computer:
• To allow open access to the application, select Anyone who uses this computer (all users).
• To restrict access to the application, select Only for me. Only the user listed in the User Name
field on the Customer Information page may use the application.
8. Click Next. The Destination Folder page appears.

106 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 67. AppXtender Rendering Server Setup - Destination Folder Page

The default installation directory is C:\Program Files\XtenderSolutions\Content Management.

9. Click Next. The Garbage Collection page appears.

Figure 68. AppXtender Rendering Server Setup - Garbage Collection Page

10. To make sure the Render Server removes cached images for users who log off Web Access, select
Enable Garbage Collection on this Rendering Server.
11. Click Next. A Ready to Install page appears.

ApplicationXtender Web Access .NET Administrator’s Guide 107

Installing and Registering AppXtender Web Access Components

Figure 69. AppXtender Rendering Server Setup - Ready to Install Page

12. Click Install. The setup wizard installs the application files.

Figure 70. AppXtender Rendering Server Setup - Installing Page

After the setup wizard installs the application files, a confirmation page appears.

108 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 71. AppXtender Rendering Server Setup - Installation Complete Page

13. Click Finish to exit the setup wizard.

Installing AppXtender Web.NET Access Server

Once you have completed the preparations for installing AppXtender Web.NET Access components
described in AppXtender Web Access Deployment Overview, page 15, and Chapter 4, Configuring
AppXtender Web Access Settings, you can proceed with AppXtender Web.NET Access component
installation and setup.
AppXtender Web.NET Access Server setup installs the AppXtender Web.NET Access website, IE Web
Controls, and AppXtender Component Registration wizard on the Internet Information Server. In
addition, the setup installs the following wizards:
• AppXtender Administration wizard. This wizard lets you delete batches of documents from
AppXtender applications. Refer to the “Managing Existing Applications” appendix of the
ApplicationXtender Core Components Administrator’s Guide.
Provided you have the optional Centera retention license or AppXtender software retention
license, the AppXtender Administration wizard also lets you perform retention administration
tasks for Centera-enabled or AppXtender software retention-enabled applications. Refer to the
Retention Manager Integration Guide.
• ApplicationXtender Data Source Features wizard. This wizard provides options that apply to all
applications in an ApplicationXtender data source. Refer to the “Managing Existing Applications”
appendix of the ApplicationXtender Core Components Administrator’s Guide.
Note: These installation instructions apply only to the English release of AppXtender Web.NET
Access. For instructions on installing releases of AppXtender Web.NET Access for other languages,
refer to the ApplicationXtender Web Access Release Notes for that language.

ApplicationXtender Web Access .NET Administrator’s Guide 109

Installing and Registering AppXtender Web Access Components

To install AppXtender Web.NET Access:

1. Log in as a user with administrative rights on the computer where you want to install
AppXtender Web.NET Access.
2. Obtain the installation files for AppXtender Web.NET Access. You can either:
• Download the WebAccessNET_6.5.xxx.zip file from the EMC download center at
http://Powerlink.EMC.com to a temporary directory on your computer. Extract the installer
zip file to the temporary directory. If you download multiple products, download all of them
to the same temporary directory.
• Insert the disc containing the AppXtender Desktop/Web setup files into your media drive.
3. In the temporary directory or media drive, navigate to the AppXtender Web.NET Accessdirectory
and double-click the Setup.exe file.
The AppXtender Web.NET Access setup wizard appears, starting with the welcome page.

Figure 72. AppXtender Web.NET Access Setup - Welcome Page

4. Click Next. The License Agreement page appears.

110 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 73. AppXtender Web.NET Access Setup - License Agreement Page

5. Read the agreement, select I accept the terms in the license agreement, and click Next. The
Customer Information page appears.

Figure 74. AppXtender Web.NET Access Setup - Customer Information Page

The User Name and Organization fields are self-populated, but you are able to make changes
to that information on this screen.
6. Specify who may use the application on the computer:
• To allow open access to the application, select Anyone who uses this computer (all users).
• To restrict access to the application, select Only for me. Only the user listed in the User Name
field on the Customer Information page may use the application.
7. Click Next. The Select Web Application page appears.

ApplicationXtender Web Access .NET Administrator’s Guide 111

Installing and Registering AppXtender Web Access Components

Figure 75. AppXtender Web.NET Access Setup - Select Target Web Site Page

The Internet Information Services (IIS) service displays a list of your available web sites, for
example, Default Web Site.
Note: The Web sites that appear in Figure 123, page 166 are examples only.
8. Select the target Web site from the Site List. This is the Web site that will host the AppXtender
Web.NET Access application.

Caution: Do not install AppXtender Web.NET Access on the Administration (root) web site.
9. To change the default application name, type a new name in the Application name field.
Note: If you do not change the application name, the setup wizard installs the Web Content files
to the Web site currently selected in the Site List. Make a note of this location because it will be
a part of the AppXtender Web.NET Access Web site address.
10. Click Next. The Destination Folder page appears.

112 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 76. AppXtender Web.NET Access Setup - Destination Folder Page

11. Click Next. The Ready to Install page appears.

Figure 77. AppXtender Web.NET Access Setup - Ready to Install Page

12. Click Install. The setup wizard installs the application files.

ApplicationXtender Web Access .NET Administrator’s Guide 113

Installing and Registering AppXtender Web Access Components

Figure 78. AppXtender Web.NET Access Setup - Installing System Page

Note: If your system is missing any third party components, such as MDAC (Microsoft Data
Access Components), Active Directory Services Interfaces (ADSI), Windows HTML Help,
Windows Script, or the Microsoft XML Parser, they are installed at this time.
After the setup wizard installs the application files, a confirmation page appears.

Figure 79. AppXtender Web.NET Access Setup - Installation Complete Page

13. Click Finish to exit the setup wizard.

Note: An Installer Information dialog box may appear recommending that you restart your
computer. If you receive this message, click Yes to restart your computer. If you do not restart
your computer when prompted, AppXtender Web.NET Access may not run properly.
Note: Make sure that Everyone has read access to the C:\Program Files\Common
Files\XtenderSolutions directory and all subdirectories.

114 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Additional Web Server Configuration for Macintosh Clients

ApplicationXtender Web Access allows users to display document thumbnails in a contact sheet
using the Microsoft® Silverlight™ component. Web Access users are prompted to install Silverlight if
they attempt to display thumbnails in a contact sheet. The Silverlight executable for Windows installs
successfully on Windows client machines. However, in an environment that uses Macintosh clients
to connect to the ApplicationXtender Web server, IIS does not recognize the MIME type (.dmg file
extension) for the Macintosh version of Silverlight. In this case, you must register the .dmg MIME
type in IIS on the Web server to allow users on Macintosh clients to display thumbnails in a contact
sheet. Otherwise, Web Access displays the message “The Request is not Supported” when users click
the link to install the Macintosh version of Silverlight.

To register the MIME type for the Macintosh version of Silverlight:

1. On the server where ApplicationXtender Web Access is installed, select Start > Programs >
Administrative Tools > Internet Information Services (IIS) Manager to launch the IIS Manager.
The Internet Information Services (IIS) Manager dialog box appears.
2. Right-click on the ApplicationXtender Web server, then select Properties. The <server_name>
Properties dialog box appears.

Figure 80. Server Properties dialog box

3. Click the MIME Types button. The MIME Types dialog box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 115

Installing and Registering AppXtender Web Access Components

Figure 81. MIME Types dialog box

4. Click New. The MIME Type dialog box appears.

Figure 82. MIME Type dialog box

5. Do the following:
a. In the Extension field, type dmg.
b. In the MIME type field, type application/octet-stream.
c. Click OK. The file extension .dmg is added to the list of registered MIME types.
6. Click OK on the MIME Types dialog box.
7. Click OK on the Server Properties dialog box.
8. Restart IIS.

116 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Installing Client Components

You can install the following client components directly from Web Access or you can run an
executable to install all the client components or a Microsoft Installer (MSI) file to install the
components individually:
• AppXtender Web Access Adobe Component – Integrates the PDF library with AppXtender
• AppXtender Web Access Scan Component – Supports client-side scanning using ISIS, TWAIN,
WIA, and Kofax Image Controls
• AppXtender KeyView Component – Supports HTML rendering; Content is rendered in XML and
HTML formats for viewing
• AppXtender Spellchecker Component – Supports ability to spellcheck annotations
To install all or selected client components directly from Web Access, select Help > Check Installed
Components. Refer to the ApplicationXtender Web Access User’s Guide for the complete set of
procedures.
If, for example, the client workstation does not have access rights for installations, you run an
executable file or MSI file to push out and install the client components.
To install all client components, navigate to the Inetpub directory where AppXtender is installed
and run the WxClientInstaller.exe.
Note: If you chose the default site to install Web Access .NET, the client folder path is
C:\Inetpub\wwwroot\AppXtender\client.
To install individual client components, navigate to the Inetpub directory where AppXtender is
installed and click the MSI file listed in the following table:

Table 7. Web Access Client Component MSI File Names

Client component MSI file name

AppXtender Web Access Adobe XSAdobeComponent91.msi
Component
AppXtender Web Access Scan Component XSScanningComponent.msi
AppXtender KeyView Component KeyViewComponent80.msi
AppXtender Spellchecker Component SpellCheckComponent.msi

Note: The Windows Installer prompts you to uninstall any previous version before displaying the
Welcome page.

Preparing AppXtender Web Component

Servers as Database Clients
If your AppXtender database is an IBM DB2, Sybase SQL Anywhere, Oracle, or MySQL database, you
must install and configure the appropriate client software on each AppXtender component computer
where you need to locate the AppXtender database.

ApplicationXtender Web Access .NET Administrator’s Guide 117

Installing and Registering AppXtender Web Access Components

For more information, see the following sections:

• Preparing AppXtender Component Servers as IBM DB2 Database Clients, page 118
• Preparing AppXtender Component Servers as Oracle Database Clients, page 122
• Preparing AppXtender Component Servers as Sybase SQL Anywhere Database Clients, page 123
• Preparing AppXtender Component Servers as MySQL Database Clients, page 127
Note: If your AppXtender database is a Microsoft SQL Server database, no client configuration
is required.
For information on supported databases and database configuration, refer to the AppXtender Data
Sources chapter of the ApplicationXtender Core Components Administrator’s Guide.
These sections outline the steps necessary to install and configure database software for use with
AppXtender components. For complete information, refer to the database software documentation.
When configuring database licensing, keep in mind that each AppXtender Desktop user in the
AppXtender system requires a corresponding license in the database software. However, an
additional database license is needed for the Global authentication account. For example, if your
AppXtender system has 20 AppXtender Desktop user licenses, you should obtain 21 database licenses
(20 for AppXtender Desktop and 1 for the AppXtender Web Global authentication account).

Preparing AppXtender Component Servers as IBM DB2 Database

Clients

On each AppXtender component computer where you need to locate the AppXtender database,
perform the following steps:

To prepare AppXtender components as IBM DB2 database clients:

1. Install IBM DB2 Client 8.2.
2. Configure IBM DB2 Client 8.2.

Caution: DB FixPack 3 is required to connect to an IBM DB2 v.8.2 database.

For instructions, see:

• Installing IBM DB2 8.2 Client, page 118
• Configuring IBM DB2 8.2 Client, page 119

Installing IBM DB2 8.2 Client

You must install the IBM DB2 8.2 Client on each AppXtender component computer where you need
to locate the AppXtender database. When installing IBM DB2 8.2 Client, perform the following steps:

118 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

To install IBM DB2 8.2 Client:

• On the client workstation where you plan to locate an IBM DB2 data source, install the IBM
DB2 8.2 Administrative Client according to the instructions provided in the IBM DB2 8.2
documentation. The default installation settings are sufficient for use with AppXtender.

Caution: If you install your IBM DB2 client files outside the program files directory, you must
use global credentials for your data source resource authentication credentials in AppXtender
Admin.

Configuring IBM DB2 8.2 Client

On each AppXtender computer where you need to locate an IBM DB2 AppXtender database, you
must first use the IBM DB2 8.2 Administrative Client you installed to create a connection to the IBM
DB2 database on the IBM DB2 server.

To configure a connection to the IBM DB2 database:

1. On the client workstation where you plan to locate an IBM DB2 data source, select Start>
Programs> IBM DB2> Set-up Tools> Configuration Assistant to start the IBM DB2 Configuration
assistant. The Configuration Assistant dialog box appears.

Figure 83. IBM DB2 Administrative Client - Configuration Assistant

2. From the Selected menu, choose Add Database Using Wizard. The Add Database Wizard
appears, starting with the Select how you want to set up a connection page.

ApplicationXtender Web Access .NET Administrator’s Guide 119

Installing and Registering AppXtender Web Access Components

Figure 84. IBM DB2 Add Database Wizard - Select How You Want to Set Up a Connection Page

3. Enable the Search the network option and click Next. The Select a database from the network
search result page appears.

Figure 85. IBM DB2 Add Database Wizard - Select a Database from the Network Search Result Page

4. Under the appropriate folder, expand the node for the IBM DB2 Server where the AppXtender
database is located. Expand the DB2 node for that server (where DB2 is the instance under which
the database was created), then expand the Local databases node under the DB2 node. Select the
appropriate database and click Next. The Specify a nickname for the database page appears.

120 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 86. IBM DB2 Add Database Wizard - Specify a Nickname for the Database Page

5. Click Next to accept the default as the Database alias for the database. The Register this database
as a data source page appears.

Figure 87. IBM DB2 Add Database Wizard - Register This Database as a Data Source Page

6. Enable the Register this database for ODBC check box. Verify that As system data source is
enabled and that the correct database name is displayed in the Data Source Name text box. Click
Finish. An ODBC data source is created for IBM DB2 on the client workstation.

ApplicationXtender Web Access .NET Administrator’s Guide 121

Installing and Registering AppXtender Web Access Components

Preparing AppXtender Component Servers as Oracle Database

Clients

On each AppXtender component computer where you need to locate the AppXtender database,
perform the following steps:

To prepare AppXtender components as Oracle database clients:

1. Install Oracle Client.
2. Configure Oracle Client.
For instructions, see:
• Installing Oracle Client, page 122
• Configuring Oracle Client, page 122

Installing Oracle Client

You must install the Oracle Client on all AppXtender component computers where you need to locate
the AppXtender database. When installing Oracle Client, perform the following steps:

To install Oracle Client on each AppXtender component computer:

1. Specify Oracle Home. Oracle Home is the physical location where Oracle files will be installed.
2. Specify whether an application user or a database administrator will use the workstation.
3. When applicable for your version of Oracle, select SQL *Net protocol adapters.

Caution: If you install your Oracle client files outside the program files directory, you must use
global credentials for your data source resource authentication credentials in AppXtender
Admin.

Configuring Oracle Client

Each version of Oracle has two network interfaces that allow Oracle tools running on network
workstations and servers to access, modify, share, and store data on other servers. Both components
guide you through the configuration of the network environment.
To set up AppXtender data sources for Oracle databases, you must install one of these components on
each client workstation (such as the AppXtender component computer) and use it to configure the
client workstation. For more information, see the following sections:
• Configuring Net Manager, page 122
• Configuring Net Configuration Assistant, page 123

Configuring Net Manager

When using Net Manager to configure the client workstation, perform the following steps:

122 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

To configure a connection to the Oracle database:

1. Create a Net Service Name. (This is the server name that you will specify when you create an
AppXtender data source.)
2. Choose the network protocol to be used when connecting to a remote database.
3. Specify the name of the computer where the server (host) database is located.
4. Type a service name. This is used to request a connection to a remote database.
5. Test the connection.
Note: The default user name and password provided by Oracle for this test may need to be
replaced with account information for a valid AppXtender user.

Configuring Net Configuration Assistant

When using Net Configuration Assistant to configure the client workstation, use the following
procedure:

To configure a connection to the Oracle database:

1. Indicate that you want to perform a local net service name configuration.
2. Indicate that you want to add a new service.
3. Specify the service name. (A database’s service name is always the same as its global database
name.)
4. Choose the network protocol to be used when connecting to a remote database.
5. Specify a host name. (This is the computer where the Oracle database resides.)
6. Test the connection.
Note: The default user name and password provided by Oracle for this test may need to be
replaced with account information for a valid AppXtender user.
7. Type a service name. (This is the server name that you will specify when you create an
AppXtender data source.)

Preparing AppXtender Component Servers as Sybase SQL

Anywhere Database Clients

On each AppXtender component computer where you need to locate the AppXtender database,
perform the following steps:

To prepare AppXtender components as Sybase SQL Anywhere database clients:

1. Install a Sybase SQL Anywhere 9.0 client.
2. Create an ODBC data source.

ApplicationXtender Web Access .NET Administrator’s Guide 123

Installing and Registering AppXtender Web Access Components

For instructions, see:

• Installing Sybase Clients, page 124
• Creating an ODBC Data Source for Sybase SQL Anywhere, page 124

Installing Sybase Clients

For all AppXtender component computers where you need to locate the AppXtender database, the
Sybase Network Client software must be installed. This comes with the Sybase SQL Anywhere
product CD; ensure the Network Database Client is selected during installation.

Figure 88. SQL Anywhere Studio 9 Install Wizard

After installation, the client computer must be restarted before using the program. A message
prompting you to restart the computer appears at the end of the installation program.

Creating an ODBC Data Source for Sybase SQL Anywhere

Once the client software is installed, you can connect the AppXtender component to the network
database server using Microsoft OLE DB Provider for ODBC Drivers through a Sybase Adaptive
Server ODBC data source.

To create an ODBC data source:

1. Start the ODBC Data Source Administrator: From the Windows Start menu, select Settings
and then Control Panel. From the Control Panel, open Administrative Tools and double-click
Data Sources (ODBC).
2. On the System DSN tab or the User DSN tab, click Add. The Create New Data Source dialog
box appears.

124 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 89. Create New Data Source Dialog Box

3. From the list of drivers, select Adaptive Server Anywhere 9.0. Click Finish. The ODBC
Configuration for Adaptive Server Anywhere dialog box appears.

Figure 90. ODBC Configuration Dialog Box - ODBC Tab

4. On the ODBC tab, enter a data source name. You can also enter a description. Click the Login tab.

ApplicationXtender Web Access .NET Administrator’s Guide 125

Installing and Registering AppXtender Web Access Components

Figure 91. ODBC Configuration Dialog Box - Login Tab

5. On the Login tab, select the Supply user ID and password option. In the User ID and Password
text boxes, type the sysop user name and password. (This is the user account that you created in
Sybase Central for the AppXtender database. The first time you start an AppXtender component,
the password for the user name sysop is xscm.)
6. Click the Database tab.

Figure 92. ODBC Configuration Dialog Box - Database Tab

7. In the Server name text box, type the server name you specified when you started your Sybase
network database server (the server name that you specified using the –n option).

126 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

8. In the Database name text box, specify the database name (the database name that you specified
using the –n option).
Note: If you have only one database started in your server, you can leave the Database name
field empty. If you have more than one database started in the database server, you must specify
the database name.
9. Click the Network tab. On the Network tab, choose the network protocols that are supported
by your Sybase network database server (the network protocols that you specified using the
-x option).

Figure 93. ODBC Configuration Dialog Box - Network Tab

Note: For a Sybase database server that supports TCP/IP protocol, if the port number is the
default 2638, then nothing needs to be entered in the TCP/IP text box. If the port number is not
the default 2638, enter the number in the field next to the TCP/IP check box. For example, if your
Sybase network database server supports TCP/IP communication link on port number 2639, you
should type ServerPort=2639 in the TCP/IP text box.
10. Click the ODBC tab. On the ODBC tab, you can perform a test connection by clicking Test
Connection. Click OK. The data source is created. In the ODBC Data Source Administrator,
click OK.

Preparing AppXtender Component Servers as MySQL Database

Clients

On each AppXtender component computer where you need to locate the AppXtender database,
perform the following steps:

ApplicationXtender Web Access .NET Administrator’s Guide 127

Installing and Registering AppXtender Web Access Components

To prepare AppXtender components as MySQL database clients:

1. Install the MySQL Connector/ODBC 3.51 (MyODBC) client driver. For instructions, refer to
the MySQL documentation.
2. Create an ODBC data source.
For instructions, see Create an ODBC Data Source for MySQL, page 128.

Create an ODBC Data Source for MySQL

You can connect AppXtender to the network database server using Microsoft OLE DB Provider for
ODBC Drivers through a MySQL ODBC data source.

To create an ODBC data source:

1. Start the ODBC Data Source Administrator: From the Windows Start menu, select Settings
and then Control Panel. From the Control Panel, open Administrative Tools and double-click
Data Sources (ODBC).
2. On the System DSN tab or the User DSN tab, click Add. The Create New Data Source dialog
box appears.

Figure 94. Create New Data Source Dialog Box

3. From the list of drivers, select MySQL ODBC 3.51 Driver. Click Finish. The Connector/ODBC
window appears.

128 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 95. Connector/ODBC Window - Login Tab

4. On the Login tab, specify the following information:

• A name for the ODBC data source
• The server name
• The sysop user name and password (These are the administrator login values that you
created for the AppXtender table space. The first time you start an AppXtender component,
the password for the user name sysop is xscm.)
• The database created for AppXtender
5. On the Connect Options tab, either leave the Port text box blank (so that 3306 will be used)
or specify 3306.

Figure 96. Connector/ODBC Window - Advanced Tab

ApplicationXtender Web Access .NET Administrator’s Guide 129

Installing and Registering AppXtender Web Access Components

6. On the Advanced tab, enable the following options:

• Don’t Optimize Column Width
• Return Matching Rows
7. Click OK.

Starting Registration of AppXtender Web

Access Components
After AppXtender Web component installation and database client preparation, you can begin to
register each of the AppXtender Web components:
• AppXtender Web.NET
• AppXtender Rendering Server (optional for AppXtender Web.NET)
You do this by running the AppXtender Component Registration wizard. For instructions, see
the following sections:
• Starting Registration of other AppXtender Components, page 130
The AppXtender Component Registration wizard must be re-run in the following circumstances:
• Deletion of the default data source.
• Selection of a different data source as default.
• Modification of the user name or password in the data link properties for a data source.
• Modification of resource authentication credentials in AppXtender Admin.
• Application of a software update

Starting Registration of other AppXtender Components

After component configuration through AppXtender Admin, component installation, and database
client preparation, you can begin to register components. You do this by running the AppXtender
Component Registration wizard.

To register AppXtender components:

1. If AppXtender Admin is open, close it. (From the File menu, select Exit.)
2. From the Start menu, select Programs> ApplicationXtender Desktop> AppXtender Component
Registration. The ApplicationXtender Component Registration Wizard appears, starting with the
welcome page.
3. Click Next. The page of the wizard that appears next depends on your configuration:
• If the AppXtender data source has not been located on this computer before, the Data Source
Configuration page appears.
• If the AppXtender data source has been located on this computer before, the Component
Type page appears.

130 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

For instructions on configuring the Data Source Configuration page, see Locating a Data Source,
page 131. For instructions on configuring the Component Type page, see Completing Registration
of Other AppXtender Components, page 140.

Locating a Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard
prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
The Data Source Configuration page allows you to locate a data source that has been configured
through AppXtender Admin.

Figure 97. AppXtender Component Registration - Data Source Configuration Page

To configure the Data Source Configuration page:

1. For a SQL Server or Oracle database, if a schema has been set up in the database, enter the name
in the Schema text box. The schema name will be used to begin all database table names created
for this data source and thus the name entered should be in a valid format for a SQL Server or
Oracle database. Avoid using any spaces, using any keywords, or beginning the name with a
numeral. (You can use an underscore in place of a space.)
Note: Schema is not supported for IBM DB2, Sybase, or MySQL databases.
2. Click Data Link. The Data Link Properties dialog box appears. In this dialog box, enter location
information for a database within the data source group where you want to register the
AppXtender component. The instructions for locating a data source within this dialog box vary
depending on the database software.

ApplicationXtender Web Access .NET Administrator’s Guide 131

Installing and Registering AppXtender Web Access Components

For details, see the following sections:

• Locating a Microsoft SQL Server Data Source, page 132
• Locating an Oracle Data Source, page 134
• Locating an IBM DB2 Data Source, page 136
• Locating a MySQL Data Source, page 137
• Locating a Sybase SQL Anywhere Data Source, page 139
For information on supported databases and database configuration, refer to the AppXtender
Data Sources chapter of the ApplicationXtender Core Components Administrator’s Guide. For
instructions on installing and configuring database client software on the AppXtender component
servers, see Preparing AppXtender Web Component Servers as Database Clients, page 117.
3. Once you have entered data source location information in Data Link Properties dialog box,
click OK.
If a user account has not been saved with the database connection information (in the Data Link
Properties dialog box), the Login dialog box appears.

Figure 98. AppXtender Component Registration - Login Dialog Box

4. In the User Name text box, type an administrative user name. In the Password text box, type the
password for the user name you entered. Click Login.
5. In the AppXtender Component Registration wizard, click Next to continue. The Component
Type page appears.
For instructions on using the Component Type page, see Completing Registration of Other
AppXtender Components, page 140.

Locating a Microsoft SQL Server Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard

prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
AppXtender components have been tested with the Microsoft OLE DB Provider for SQL Server that
is installed with Microsoft Data Access Components (MDAC). If MDAC is not installed on your
workstation, the AppXtender setup wizards install it.

132 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

The Provider tab of the Data Link Properties dialog box allows you to locate a SQL Server data source.

Figure 99. Data Link Properties Dialog Box - Provider Tab

To locate a SQL Server data source:

1. Select Microsoft OLE DB Provider for SQL Server and click Next. The Connection tab appears.
2. From the Server Name list, select the server on which you placed your SQL Server database. In
the User Name and Password text boxes, type the sysop user name and password. (These are
the administrator login values that you created in SQL Server for the AppXtender database. The
first time you start an AppXtender component, the password for the user name sysop is xscm.)
Select the AppXtender database name from the Select Database list.

ApplicationXtender Web Access .NET Administrator’s Guide 133

Installing and Registering AppXtender Web Access Components

Figure 100. Data Link Properties Dialog Box - Connection Tab

Note: If you do not check the Allow saving password option, you must use a database schema.
3. You can test the connection between the AppXtender component and the database by clicking
Test Connection. Click OK.
The AppXtender Component Registration wizard continues. For instructions, see Completing
Registration of Other AppXtender Components, page 140.

Locating an Oracle Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard

prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
AppXtender components have been tested with the Microsoft OLE DB Provider for Oracle that
is installed with Microsoft Data Access Components (MDAC). If MDAC is not installed on your
workstation, the AppXtender setup wizards install it.
The Provider tab of the Data Link Properties dialog box allows you to locate an Oracle data source.

134 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 101. Data Link Properties Dialog Box - Provider Tab

To locate an Oracle data source:

1. Select Microsoft OLE DB Provider for Oracle.
Note: When locating an AppXtender data source with an Oracle database, do not use the Oracle
Provider for OLE DB or the Microsoft OLE DB Provider for ODBC Drivers.
2. Click Next. The Connection tab appears.

Figure 102. Data Link Properties Dialog Box - Connection Tab

Note: If you do not check the Allow saving password option, you must use a database schema.

ApplicationXtender Web Access .NET Administrator’s Guide 135

Installing and Registering AppXtender Web Access Components

3. In the Server Name text box, enter the Net Service Name that you configured in Net Manager
or Net Configuration Assistant. In the User Name and Password text boxes, type the sysop
user name and password. (These are the administrator login values that you created for the
AppXtender table space. The first time you start an AppXtender component, the password
for the user name sysop is xscm.)
4. You can test the connection between the AppXtender component and the database by clicking
Test Connection. Click OK.
The AppXtender Component Registration wizard continues. For instructions, see Completing
Registration of Other AppXtender Components, page 140.

Locating an IBM DB2 Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard

prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
AppXtender components have been tested with the IBM OLE DB Provider for DB2 that is installed
with the IBM DB2 server or client.

Caution: DB FixPack 3 is required to connect to an IBM DB2 8.2 database.

The Provider tab of the Data Link Properties dialog box allows you to locate an IBM DB2 data source.

Figure 103. Data Link Properties Dialog Box - Provider Tab

136 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

To locate an IBM DB2 data source:

1. Select IBM OLE DB Provider for DB2 and click Next. The Connection tab appears.
2. From the Existing data source list, select the AppXtender database.
3. In the User Name and Password text boxes, type the user name and password for the
administrative user that was used during IBM DB2 Enterprise Server installation on the database
server.

Figure 104. Data Link Properties Dialog Box - Connection Tab

4. Check the Allow saving password option.

5. You can test the connection between the AppXtender component and the database by clicking
Test Connection. Click OK.
The AppXtender Component Registration wizard continues. For instructions, see Completing
Registration of Other AppXtender Components, page 140.

Locating a MySQL Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard

prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
AppXtender components have been tested with the Microsoft OLE DB Provider for ODBC Drivers
provider that is installed with Microsoft Data Access Components (MDAC). If MDAC is not installed
on your workstation, the AppXtender setup wizards install it.
The Provider tab of the Data Link Properties dialog box allows you to locate a MySQL data source.

ApplicationXtender Web Access .NET Administrator’s Guide 137

Installing and Registering AppXtender Web Access Components

Figure 105. Data Link Properties Dialog Box - Provider Tab

To locate a MySQL data source:

1. Select Microsoft OLE DB Provider for ODBC Drivers, and click Next. The Connection tab appears.

Figure 106. Data Link Properties Dialog Box - Connection Tab

2. From the Use data source name list, select the MySQL data source that you created in ODBC
Administrator.
3. In the User Name and Password text boxes, type the sysop user name and password. (These are
the administrator login values that you created for the AppXtender table space. The first time you
start an AppXtender component, the password for the user name sysop is xscm.)

138 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

4. Check the Allow saving password option.

5. You can test the connection between the AppXtender component and the database by clicking
Test Connection. Click OK.
The AppXtender Component Registration wizard continues. For instructions, see Completing
Registration of Other AppXtender Components, page 140.

Locating a Sybase SQL Anywhere Data Source

When registering an AppXtender component, the AppXtender Component Registration wizard

prompts you to locate a data source, so that you can register the AppXtender Web.NET Server or
AppXtender Rendering Server in the data source group you want to use. You are also prompted to
locate a data source when you specify a database for the AppXtender Rendering Server, so that
rendering queue tables can be created in the database.
AppXtender components have been tested with the Microsoft OLE DB Provider for ODBC Drivers
provider that is installed with Microsoft Data Access Components (MDAC). If MDAC is not installed
on your workstation, the AppXtender setup wizards install it.
The Provider tab of the Data Link Properties dialog box allows you to locate a Sybase data source.

Figure 107. Data Link Properties Dialog Box - Provider Tab

To locate a Sybase data source:

1. Select Microsoft OLE DB Provider for ODBC Drivers, and click Next. The Connection tab appears.

ApplicationXtender Web Access .NET Administrator’s Guide 139

Installing and Registering AppXtender Web Access Components

Figure 108. Data Link Properties Dialog Box - Connection Tab

2. Check the Allow saving password option.

3. From the Use data source name list, select the Sybase data source that you created in ODBC
Administrator. In the User Name and Password text boxes, type the sysop user name and
password. (The first time you start an AppXtender component, the password for the user name
sysop is xscm.)
4. You can test the connection between the AppXtender component and the database by clicking
Test Connection. Click OK.
The AppXtender Component Registration wizard continues. For instructions, see Completing
Registration of Other AppXtender Components, page 140.

Completing Registration of AppXtender Web

Access Components
If your Web Access deployment required you to locate a data source, you can now complete the
registration of AppXtender components. For instructions, refer to:
• Completing Registration of Other AppXtender Components, page 140

Completing Registration of Other AppXtender

Components
The AppXtender Component Registration wizard allows you to register the AppXtender Web
Services and AppXtender Rendering Server components.

140 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Selecting a Component Type

The Component Type page allows you to select which component to register.

Figure 109. AppXtender Component Registration - Component Type Page

To continue with registration:

1. Select the option for the AppXtender component that you want to register.
2. Click Next.
AppXtender Component Registration runs a diagnostic utility to detect whether all security
settings are correctly configured and all accounts used for resource authentication credentials
have the correct advanced rights applied.
What happens next depends on whether the diagnostic utility detects any discrepancies:
• If the diagnostic utility detects any discrepancies in permissions for AppXtender accounts,
the Review Permissions dialog box appears.
• If you have already correctly configured all security settings and assigned rights to the
required accounts, the Component Information page appears.
For instructions, see:
• Reviewing Permissions, page 141
• Entering Component Information, page 142

Reviewing Permissions

AppXtender Component Registration runs a diagnostic utility to detect whether all security settings
are correctly configured and all accounts used for resource authentication credentials have the correct
advanced rights applied. If the diagnostic utility detects any discrepancies in permissions for
AppXtender accounts, the Review Permissions dialog box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 141

Installing and Registering AppXtender Web Access Components

Figure 110. AppXtender Component Registration - Review Permissions Dialog Box

To continue with registration:

1. If the Review Permissions dialog box appears, select the Save option to save the list of issues to an
XML file, or select OK to close the dialog box.
2. If you need to adjust settings in AppXtender Admin, exit the AppXtender Component
Registration wizard before doing so. Apply any missing privileges to the appropriate accounts.
(You may need to restart the computer after applying permissions.) Then restart the AppXtender
Component Registration wizard and repeat previous steps.
The Component Information page appears.
For instructions, see Entering Component Information, page 142.

Entering Component Information

The Component Information page allows you to enter a description to identify the component, and
if necessary, specify an IP address.

142 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Figure 111. AppXtender Component Registration - Component Information Page

To continue with registration:

1. Enter a description in the Description text box. This description will be displayed in the registered
components listing in AppXtender Admin.
2. Confirm that the correct IP address appears in the IP Address text box or enter the correct one.
3. Click Next to continue. The page that appears next depends on your configuration:
• If you are registering AppXtender RM Service, Web Services, or RM Service, the Web Service
Configuration page appears.
• If this computer has never connected to an application data source, the Configure Database
page appears.
• Otherwise, the final page of the AppXtender Component Registration wizard appears.
For instructions, see:
• Specifying Web Service Settings, page 143
• Configuring Database Access, page 145
• Completing Registration, page 146

Specifying Web Service Settings

The Web Service Configuration page allows you to specify settings specific to AppXtender RM
Service, Web Services, or RM Service.

ApplicationXtender Web Access .NET Administrator’s Guide 143

Installing and Registering AppXtender Web Access Components

Figure 112. AppXtender Component Registration - Web Service Configuration Page

To continue with registration:

1. Take note of information as described in the following table:

Table 8. Web Service Configuration Properties

Property Description
Host Type Take note of the host type that the AppXtender component
resides on. The Host Type setting on this page reflects the
deployment choice made during AppXtender component
installation.
Port The Port setting reflects the selections made during AppXtender
component installation as follows:
• If IIS deployment was selected, this setting automatically
reflects the port number associated with the selected web
site.

• If AppXtender Web Host deployment was selected, this

setting automatically reflects the port number associated
with the AppXtender component.

If you want to change the web site later, you can run
AppXtender Component Registration again to change the port
number.
Site URL Take note of the site URL (Universal Resource Locator) for
the web site where the AppXtender component is installed.
The site URL is automatically provided, depending on the IP
address entered on the Component Information page of the
AppXtender Component Registration wizard.

144 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Property Description
Virtual Root Take note of the virtual root that will be used for the
AppXtender component web site. You can use this setting to
include a company name or create a hierarchy. The method
to modify this setting depends on the deployment selection
as follows:
• If IIS deployment was selected, the virtual root can be
specified only in the Windows utility, Internet Information
Services.

• If AppXtender Web Host deployment was selected, you

can modify the virtual root in the AppXtender Component
Registration wizard.
Physical Path Take note of the physical path to the AppXtender component
files. (The Physical Path text box is available only for
AppXtender Web Host.)

2. Click Next to continue. The page that appears next depends on your configuration:
• If the Allow Saving Password option is off in AppXtender Admin for the default data source,
the Configure Database page appears.
• Otherwise, the final page of the AppXtender Component Registration wizard appears.
For instructions, see:
• Configuring Database Access, page 145
• Completing Registration, page 146

Configuring Database Access

If the Allow Saving Password option is off in AppXtender Admin for the default data source, the
Configure Database page appears.

ApplicationXtender Web Access .NET Administrator’s Guide 145

Installing and Registering AppXtender Web Access Components

Figure 113. AppXtender Component Registration - Configure Database Page

To continue with registration:

1. Under Data Sources, select a data source. In the text boxes, specify the user name and password
for a user account that has access to the database. This step is necessary so that the component
you are registering can access the database later.
2. Click Next to continue. The final page of the AppXtender Component Registration wizard
appears.
For instructions, see Completing Registration, page 146.

Completing Registration

The final page of the AppXtender Component Registration wizard allows you to complete the
registration of the selected component and optionally begin the registration of another component.

To continue with registration:

1. To run the wizard again to register another component, enable the Would you like to run the
AppXtender Component Registration wizard again? option.
2. Click Finish.
After you have configured, installed, and registered each of the AppXtender Web.NET components,
you can test their deployment. For more information, see Testing the AppXtender Components,
page 147.

146 ApplicationXtender Web Access .NET Administrator’s Guide

 Installing and Registering AppXtender Web Access Components

Testing the AppXtender Components

After you have configured, installed, and registered each of the AppXtender components, you can
test their deployment. For information, see the following topics:
• Testing the AppXtender Web.NET Server, page 147
• Testing the AppXtender Rendering Server, page 147

Testing the AppXtender Web.NET Server

To verify that AppXtender Web.NET has been correctly installed, configured, and
registered:
1. Enter the website address for AppXtender Web.NET in your browser Address text box. The
format for the website URL for a AppXtender Web.NET server is as follows:
http://<Server>/<alias>/login.aspx
• The placeholder <Server> represents the IP address or domain of the IIS server.
• The placeholder <alias> represents the AppXtender Web.NET server alias you specified
when installing AppXtender Web.NET. By default the alias is AppXtender.
The Login page appears.
2. Test the ability to log into the AppXtender Web.NET Server by entering credentials and clicking
Login.
3. Test the user ability to create or display documents.
For more information on use of AppXtender Web, see the ApplicationXtender Web Access User’s Guide.
If you are unable to login (or if you can login but are unable to create or display documents), check
each item described in the following sections:
• Testing the AppXtender Content Management Environment, page 21
• Configuring Authentication Accounts, page 21
• AppXtender Rendering Server Computer Preparation Checklist, page 22
• AppXtender Web.NET Server Preparation Checklist, page 26
• Preparing AppXtender Web Component Servers as Database Clients, page 117

Testing the AppXtender Rendering Server

To verify that AppXtender Rendering Server has been correctly installed, configured,
and registered:
1. Verify that the AppXtender Rendering Server service is running.
2. Log into AppXtender Web as described in Testing the AppXtender Web.NET Server, page 147
3. In thin client mode, test the user ability to create or display a document that would need to be
rendered, such as a Microsoft Word document.

ApplicationXtender Web Access .NET Administrator’s Guide 147

Installing and Registering AppXtender Web Access Components

A Loading Requested Image page should appear.

4. Verify that JPG files have been created in the AppXtender Rendering Server cache directory.
For more information on use of AppXtender Web, see the ApplicationXtender Web Access User’s Guide.
If you are unable to perform these steps, check each item described in the following sections:
• Configuring Authentication Accounts, page 21
• AppXtender Rendering Server Computer Preparation Checklist, page 22

148 ApplicationXtender Web Access .NET Administrator’s Guide

 Appendix A
Managing AppXtender Web Access

AppXtender Web Access provides an online administration component, AppXtender Web Access
Administrator, that allows you to manage document locks, checked-out documents, full-text queues,
and sessions in real-time. AppXtender Web Access Administrator is secure and appears as a link
from the AppXtender Web Access View menu, visible only to those users granted Administrator
privilege within the AppXtender Application Generator module.
See the following sections to learn more about managing AppXtender Web Access:
• Working with AppXtender Web Access Administrator, page 149
• Managing Annotation Security in AppXtender Web Access, page 159
Note: For instructions on monitoring servers using the AppXtender Web Access Administrator, refer
to the ApplicationXtender Server Monitoring Guide.

Working with AppXtender Web Access

Administrator
Each AppXtender Web Access Administrator page contains a toolbar that allows you to easily
navigate within the AppXtender Web Access Administrator pages and refresh the pages to see
the most current information.
See the following sections to learn more about AppXtender Web Access Administrator:
• Accessing the AppXtender Web Access Administrator, page 150
• Navigating the AppXtender Web Access Administrator, page 151
• Managing Sessions, page 152
• Managing Job Queues, page 154
• Managing Checked Out Documents, page 156
• Managing Locked Documents, page 157
• Managing Retention Hold Documents, page 158

ApplicationXtender Web Access .NET Administrator’s Guide 149

Managing AppXtender Web Access

Accessing the AppXtender Web Access Administrator

You can access AppXtender Web administrative functions through the AppXtender Web client
browser interface if you have Administrator privilege in AppXtender AppGen.

To access the AppXtender Web Access Administrator through a browser:

1. Enter the website address for AppXtender Web in your browser Address text box. The format for
the website URL for an AppXtender Web.NET server is as follows: http://<Server>/<alias>
(where <Server> is the IP address or the server name and <alias> is the AppXtender Web.NET
server alias). When logging into an AppXtender Web.NET Server, the Welcome page appears.
Note: If you do not know the name of the AppXtender Web Access server, contact your
AppXtender Web administrator for assistance.
The Login page appears.

Figure 114. AppXtender Web Login Page

2. To use a data source other than the default data source, on the AppXtender Web Access Login
dialog box, select the desired data source from the Data Source drop-down list. The selected data
source is considered the active data source for the session.
All of the data sources available to you appear in the Data Source drop-down list. If you choose
Default, you are logged into either the data source that your AppXtender Web administrator set
as default or the data source that you set as default in a previous session.
3. Type your AppXtender login user name and password in the corresponding text boxes.
4. Click Login. The AppXtender Web Access Applications window opens.
5. Select Edit > Administration.

150 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

Navigating the AppXtender Web Access Administrator

The AppXtender Web Access Administrator toolbar allows you to navigate within the AppXtender
Web Access Administrator pages and refresh the pages to see the most current information. The
toolbar appears at the top of each AppXtender Web Access Administrator page.
In addition, you can navigate through AppXtender Web Access Administrator pages using the
Administration options located in the AppXtender Web View menu.

Figure 115. AppXtender Web Access Administrator Toolbar

The following table describes each button on the Web Access Administrator toolbar.

Table 9. Web Access Administrator Toolbar Options

Button Description
Closes the window.

Opens the session list. For details, refer to Managing Sessions, page
152.
Opens the Job Queue List (for full-text and OCR job queues). For
details, refer to Managing Job Queues, page 154.
Opens the Locked Documents List. For details, refer to Managing
Locked Documents, page 157.
Opens the Checked Out Document List. For details, refer to
Managing Checked Out Documents, page 156.
Opens the Retention Holds Admin page. For details, refer to
Managing Retention Hold Documents, page 158.
Depending on the context, terminates sessions, cancels jobs,
releases checked out documents, or releases locked documents.
For details, refer to:
• Terminating Sessions, page 153

• Cancelling Jobs, page 155

• Releasing Checked Out Documents, page 156

• Releasing Locked Documents, page 158

Refreshes the current list.

ApplicationXtender Web Access .NET Administrator’s Guide 151

Managing AppXtender Web Access

To navigate to a different AppXtender Web Access Administrator page using the toolbar:
• Click the appropriate toolbar button to select the page you want to view. The page appears
in AppXtender Web Access’s main window.
To refresh the current AppXtender Web Access Administrator page manually:
• Click the Refresh List button. The current AppXtender Web Access Administrator page refreshes.
For more information, see:
• Managing Sessions, page 152
• Managing Job Queues, page 154

Managing Sessions
You can manage current AppXtender Web sessions and view detailed session information using
the Session List page.
To view current AppXtender Web sessions:
• In the Administrator window, select View> Session Management.
The Session List page appears, listing all currently active AppXtender Web client sessions for the
data source group and indicating the user name for each session.
For more information, see:
• Viewing the Logged On Session List, page 152
• Terminating Sessions, page 153
• Viewing License Server Information, page 153

Viewing the Logged On Session List

The Logged On Session List shows AppXtender Web session information and allows you to terminate
sessions.

Figure 116. Session List Page - Logged On Session List

The following table describes each column of the Logged On Session List:

152 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

Table 10. Basic Session Information

Column Description
Session ID Unique session identifier.
Create Time The day and time the session was created.
Last Access The day and time the session was last accessed.
Time
Data Source The data source to which the session’s user is currently logged in
and that user’s user name.

Terminating Sessions

You can terminate selected user sessions or all user sessions from the Session Management page.
However, you cannot terminate the session that you are currently using to manage sessions.

To terminate selected user sessions:

1. Select the check boxes that correspond to the session(s) you want to terminate.
2. Click the Terminate Selected Sessions button on the toolbar.
3. Exit the Session Management page.

To terminate all sessions:

1. Select the check box in the heading row to select the check boxes for all active sessions.
2. Click the Terminate Selected Sessions button on the toolbar. All sessions (with the exception of
the session you are currently using to administrate AppXtender Web Access) are terminated.
3. Exit the Session Management page.

Viewing License Server Information

You can display License Server information from the Session Management page. To do so, click the
View License Info hyperlink.
The License Server information shown includes the maximum and current license usage for
AppXtender products and features.
Note: Figure 117, page 154 shows a sample License Server Information page. The information
displayed on this page depends on the licensed AppXtender features installed in your AppXtender
system.

ApplicationXtender Web Access .NET Administrator’s Guide 153

Managing AppXtender Web Access

Figure 117. Session List Page - License Server Information

Managing Job Queues

The Job Queue List page allows you to view and manage AppXtender Web Access full text and
OCR jobs.

To view current AppXtender Web job queues for the active data source:
1. In the AppXtender Web Access Administrator window, select View> Queues.
The Job Queue List page appears.

Figure 118. Job Queue List

2. From the Select Queue list, select a job queue to view.

154 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

Basic information about the current jobs in the selected queue appears. For each job, information
is provided including a JobID number, a UserID number, a priority number, a date and time
submitted, a date and time started, a date and time finished, and a job status.
For more information, see:
• Viewing Jobs, page 155
• Cancelling Jobs, page 155

Viewing Jobs

The Job Queue List page allows you to view full text or OCR job information.
To refresh jobs:
• Click the Refresh List button.
To view detailed job information:
• Double-click the job for which you want to view information.

Figure 119. Job Queue and Job Element Lists

Information about the elements of the selected job appears. For each job element, information is
provided including the index number, application ID number, document ID number, page number,
page version, status, and description.

Cancelling Jobs
To delete selected full text jobs:
1. Select the check box that corresponds to the job or jobs you want to delete.
2. Click Delete Selected Jobs.

To delete selected full text jobs:

1. Select the check box that corresponds to the job or jobs you want to delete.
2. Click the Terminate Selected Full Text Job button on the toolbar.

ApplicationXtender Web Access .NET Administrator’s Guide 155

 Managing AppXtender Web Access

Managing Checked Out Documents

The Checked Out Document List page allows you to view and manage checked out documents.
To view currently checked out documents:
• In the AppXtender Web Access Administrator window, select View> Checked Out Documents.
The Checked Out Document List page appears.

Figure 120. Checked Out Document List Page

Detailed information about the currently checked out documents in the active data source appears.
For each document, information is provided including the application ID number, the application
name, the document ID number, the revision number, the ID and name of the user who checked
out the document, the workstation name, the date and time the document was checked out, and
comments the user entered when checking out the document.
For more information, see:
• Viewing Checked Out Documents, page 156
• Releasing Checked Out Documents, page 156

Viewing Checked Out Documents

The Checked Out Document List page allows you to view all checked out documents for the active
data source.
To refresh the list of documents:
• Click the Refresh List button.

Releasing Checked Out Documents

You can release checked out documents. You can cancel check out of a single document or of multiple
documents at once. When you cancel check out on a document, any changes that may have been
made since the document was checked out are discarded.

156 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

To release multiple checked out documents:

1. Select the check boxes that correspond to the documents you want to release from check out.
2. Click the Unlock Selected Documents button on the toolbar. As long as the document is not
locked, check out is cancelled.
To cancel check out for a single document:
• Double-click the document you want to release from check out. As long as the document is
not locked, check out is cancelled.
For instructions on releasing locked documents, see Releasing Locked Documents, page 158.

Managing Locked Documents

Under the following circumstances, documents that are open on a client’s computer are locked:
• The user opened the document in AppXtender Web IRC mode.
• The user displayed the index for the document and clicked Modify.
The Locked Document List page allows you to view and manage locked documents.
To view currently locked documents:
• In the Administrator window, select View> Locked Documents.
The Locked Document List page appears.

Figure 121. Locked Document List

Detailed information about the currently locked out documents in the active data source appears. For
each document, information is provided including the user ID number, the session ID number, and
the date and time the document was locked.
For more information, see:
• Viewing Locked Documents, page 158
• Releasing Locked Documents, page 158

ApplicationXtender Web Access .NET Administrator’s Guide 157

Managing AppXtender Web Access

Viewing Locked Documents

The Locked Document List page allows you to view all locked documents for the active data source.
To refresh the list of documents:
• Click the Refresh List button.

Releasing Locked Documents

If necessary, you can release locked documents. For example, you can release locked documents to
allow cancellation of check out for the documents. You can unlock a single document or multiple
documents at once.

To unlock multiple selected documents:

1. Select the check boxes that correspond to the documents you want to release from check out.
2. Click the Cancel Check Out for Selected Documents button on the toolbar.
To unlock a single document:
• Double-click the document you want to release from check out.

Managing Retention Hold Documents

The Retention Holds page of the AppXtender Web Access Administrator allows you to remove the
retention hold setting from a set of documents under Centera retention or AppXtender software
retention.

To remove the retention hold setting:

1. Select View > Retention Hold Documents from the Administrator menu bar, or click on the
Administrator toolbar. Web Access displays the Retention Holds dialog box.
2. Select the data source from the Data Source list box.
3. Select the AppXtender application from the Select Application list box.
4. Select the retention hold label from the Select Label list box.
5. Click Display Docs to display the documents.
6. Click Remove Holds.

158 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

Managing Annotation Security in AppXtender

Web Access
You can manage security for AppXtender rubber stamps using AppXtender Web Access or Document
Manager. All other annotation security functions are performed using AppXtender AppGen and
Document Manager.
• For more information about how AppXtender Web uses AppXtender security, refer to the
Planning AppXtender Security chapter of the ApplicationXtender Concepts Guide.
• For more information about creating the _RSTAMP application, refer to the "The _RSTAMP
Application" section of the ApplicationXtender Core Components Administrator’s Guide.
• For more information about configuring rubber stamp security in AppXtender Web, see
Configuring Rubber Stamp Security, page 159.
• For more information about configuring rubber stamp security in AppXtender Document
Manager, refer to the "Rubber Stamp Annotations" section of the ApplicationXtender Document
Manager User’s Guide.

Configuring Rubber Stamp Security

If you are an AppXtender Web administrator and have access to the _RSTAMP application, you can
edit the Rubber Stamp name, application, user or group access, and description.
Note: Access to the _RSTAMP application requires that users have the Administrator privilege in
their AppXtender security profile. Alternatively, the AppXtender administrator can grant access to all
users using the ApplicationXtender Data Source Features wizard. Refer to the “Managing Existing
Applications” appendix of the ApplicationXtender Core Components Administrator’s Guide or contact
your AppXtender administrator if you have questions.

To configure rubber stamp security:

1. Query the _RSTAMP application:
• To search for a particular rubber stamp, add search criteria to the index fields.
• To view all available rubber stamps, leave the search criteria fields blank.
2. Select the rubber stamp you want to configure by clicking its icon in the Result Set. The Document
View page appears.
3. Click the Document Index button. The document index appears.
4. Click Modify. Change the index fields as needed. The following table describes each index field
and its effect on AppXtender Web rubber stamp annotations.

ApplicationXtender Web Access .NET Administrator’s Guide 159

Managing AppXtender Web Access

Table 11. Rubber Stamp Application Editable Index Fields

Index
Field Description Usage
NAME Name of the Enter the name, as it should appear in the Name
rubber stamp. column of the Select a rubber stamp from the
list dialog box (this appears after choosing More
rubber stamps from the Annotation toolbar). The
actual content of placed rubber stamps must be
changed from within AppXtender Document
Manager. For information about modifying rubber
stamps from within AppXtender Document
Manager, refer to the ApplicationXtender Document
Manager User’s Guide.
DESC Description Enter the description, as it should appear in the
of the rubber Description column of the Select a rubber stamp
stamp. from the list dialog box (this appears after choosing
More rubber stamps from the Annotation toolbar).
APP Application Enter the name of the specific application the
in which the rubber stamp should be used with. Leave this
rubber stamp field blank to allow the rubber stamp to be used
will be used. in all applications (in order to do this, the APP
field should be configured as non-required within
the _RSTAMP application). For information
about modifying applications, refer to "Modifying
an Application" in the ApplicationXtender Core
Components Administrator’s Guide.
USER User or group You can enter either individual users or groups
that will have in this box to restrict usage of the rubber stamp
access to the to an individual user or group. To allow all
rubber stamp. users to access the rubber stamp, leave this
field blank (in order to do this, the USER field
should be configured as non-required within the
_RSTAMP application). For information about
modifying applications, refer to "Modifying
an Application" in the ApplicationXtender Core
Components Administrator’s Guide.
DOMAIN Domain will If the underlying AppXtender system uses the
have access Windows security provider, this is where a domain
to the rubber associated with this rubber stamp can be specified.
stamp. If this field is empty, this rubber stamp is available
to all domains. If the AppXtender system uses the
CM security provider, leave this field blank. For
more information about security providers, refer
to the Planning AppXtender Security chapter of
the ApplicationXtender Concepts Guide.

160 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing AppXtender Web Access

5. When you have finished changing the index fields to match your requirements, click Save.

ApplicationXtender Web Access .NET Administrator’s Guide 161

Managing AppXtender Web Access

162 ApplicationXtender Web Access .NET Administrator’s Guide

 Appendix B
Managing User Profiles

This appendix explains how to manage user profiles. A user profile is a set of default properties
assigned to a AppXtender Web Access user, and is created when a user logs into AppXtender Web
for the first time.
• Introduction, page 163
• Starting AppXtender User Profile Administrator, page 164
• AppXtender User Profile Administrator Toolbar Buttons, page 166
• Editing User Profiles, page 167
• Restoring Default Values, page 185
• Saving User Profile Setting Changes, page 186
• Undoing User Profile Setting Changes, page 187
• Copying a Profile from One User to Other Users, page 187

Introduction
A user profile is a set of default properties assigned to a AppXtender Web Access user, and is created
when a user logs into AppXtender Web for the first time.
Note: If the current data source is using the Windows security provider or a directory service
security provider, user profiles are not created for users until they have logged into Windows or
the directory service.
You can edit user profiles through AppXtender User Profile Administrator (which is installed with
AppXtender Admin). You can customize profiles on a per-user basis, edit the default user profile for
all AppXtender Web users, or combine the two strategies.
AppXtender User Profile Admin provides a greater amount of control over what users can or cannot
configure on their own. If users are not given the Configure WS privilege in AppXtender, they
cannot alter the settings that you have configured in their user profile. This allows you to uniformly
configure functionality across clients if needed. For example, if you leave the Enable IRC setting set to
a value of False (disabled) for all users, users cannot download the AppXtender Web IRC module and
must use AppXtender Web in AppXtender Web Thin Client mode.
You can make changes to user profile setting values and then choose whether to export those changes
to a file without modifying the database values, or save the changes to the database. You can also

ApplicationXtender Web Access .NET Administrator’s Guide 163

Managing User Profiles

undo changes that you have made, copy the default profile to a specific user, or restore default values
to reinitialize the database values to their original defaults.
Note: Users can be created and deleted only in AppXtender Application Generator (AppXtender
AppGen). When users are created or deleted in AppXtender AppGen, these changes are reflected in
AppXtender User Profile Admin the next time you start it.

Caution: Changes made to the user profile settings can accidentally disable AppXtender
Web functionality. Settings should be changed only if necessary. If your AppXtender Web
installation functions incorrectly after you make a change, use the procedure in Restoring
Default Values, page 185 to return the settings to the default values.

For more information, see the following sections:

• Starting AppXtender User Profile Administrator, page 164
• AppXtender User Profile Administrator Toolbar Buttons, page 166
• Editing User Profiles, page 167
• Restoring Default Values, page 185
• Saving User Profile Setting Changes, page 186
• Undoing User Profile Setting Changes, page 187
• Copying a Profile from One User to Other Users, page 187

Starting AppXtender User Profile Administrator

The AppXtender User Profile Administrator is a separate module that is installed when the
AppXtender Admin is installed.

To start AppXtender User Profile Administrator:

1. Select Start > Programs> AppXtender> User Profile Administrator. If you have multiple data
sources in your data source group, the Data Source Selection dialog box appears.

164 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Figure 122. Data Source Selection Dialog Box

2. Select the appropriate data source from the list and click OK. The Login dialog box appears.
3. In the User Name text box, enter the user name for an AppXtender user with the Administrator
privilege.
4. In the Password text box, enter the corresponding password.
5. Click OK to login.
Note: If this is the first time AppXtender User Profile Administrator is being started after a database
upgrade and the administrator chose to delay upgrading the user profile schema during database
upgrade, a message appears that prompts you to upgrade the user profile schema. If you click
Cancel, AppXtender User Profile Administrator does not open. If you click OK, the default user
profile is reset to factory defaults, which overwrites any customized user profile setting values you
may have configured for that profile.
The AppXtender User Profile Administrator window appears.

ApplicationXtender Web Access .NET Administrator’s Guide 165

Managing User Profiles

Figure 123. AppXtender User Profile Administrator Window

The settings listed in the AppXtender User Profile Administrator window reflect the settings in the
User Profile table in the database. The following table explains how the AppXtender User Profile
Administrator window indicates differences between profiles:

Table 12. Setting Difference Indicators

Indicator Meaning
A bold value listed for the Default A difference between the Default User
User Profile Profile and the factory-default
A bold value listed for other user A difference between the selected user
profiles profile and the Default User Profile
A blank setting when you select A difference between the selected profiles
multiple user profiles

Note: The AppXtender User Profile Administrator can also be started from AppXtender Admin.
(From the Tools menu, select AppXtender User Profile Admin.)

AppXtender User Profile Administrator Toolbar

Buttons
The AppXtender User Profile Administrator window has a toolbar with buttons for frequently
used user profile modification tasks.

Figure 124. AppXtender User Profile Administrator Toolbar

166 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

See the following table for details on the use of each toolbar button.

Table 13. AppXtender User Profile Administrator Toolbar Buttons

Button Description Related Topic

Restore Defaults Restoring Default Values, page 185

Save Changes Saving User Profile Setting Changes, page 186

Undo Changes Undoing User Profile Setting Changes, page

187

Editing User Profiles

You can make changes to a user profile and then choose whether to export those changes to a file
without modifying the database values, or save the changes to the database. You can also merge user
profile information into the profiles currently listed in AppXtender User Profile Administrator.
For more information, see the following sections:
• Editing User Profile Settings, page 167
• Configuring Automatic E-mail Registration, page 181
• Exporting a Profile, page 182
• Loading a User Profile for Editing, page 183
• Merging User Profiles, page 184

Editing User Profile Settings

You can modify the value for a user profile setting. You can choose to change a value for each default
setting that is used by any new user that is created. You can change the defaults for a specific
application or for all applications at once.
You can also change the value of any setting for a specific user, either for all AppXtender applications
or for a specific AppXtender application.
When you restore user profiles, you reset the values in the User Profile table in the database to the
defaults. If you or any users have modified any user profiles, those modifications are overwritten.

To edit user profile settings:

1. In the AppXtender User Profile Administrator window, from the list of users on the left, select the
user profile or profiles that you want to edit. The list includes the Default User Profile and all
users that have been created in AppXtender AppGen.

ApplicationXtender Web Access .NET Administrator’s Guide 167

Managing User Profiles

2. From the Application drop-down list on the right, select the application in which you want your
changes to take effect. You can choose all applications (Global) or for a specific application:
• To modify the value for all applications, select Global (Not Application Specific).
• To modify the value for a specific application, select the application name.
3. In the tree view of settings, expand the node for the category of settings that you want to modify
and select a setting.
4. Change the value for the selected setting by selecting a different value from a drop-down list or
by typing a value. The following table describes each setting and its available options:

Table 14. User Profile Settings

Available
Category Setting Name Description Options
COLD Allow Zoom Indicates whether zoom • True
is allowed for COLD
document display. • False
COLD Box Drawing Indicates that the • True
Data Text Enable Enable Box Drawing for
Form Data Text option • False
is enabled. (Disable
this option to display
text written in foreign
languages using the
ASCII values from 176
to 223.)
COLD Box Drawing Indicates that the • True
Overlay Text Enable Box Drawing
Enable for Form Overlay Text • False
option is enabled.
(Disable this option to
display form overlays
written in foreign
languages using the
ASCII values from 176
to 223.)
COLD Color Bar Indicates the color to be Custom, web, or
Options: Color used for color bars. system colors
Bar Color
COLD Color Bar Indicates the number 1-100
Options: Color of lines to be used for
Bar Lines color bars.

168 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
COLD Color Bar Indicates whether • True - User-
Options: Use user-specific or specific color
Default application-specific bar settings
color bar settings should be used
should be used.
• False -
Application-
specific color
bar settings
should be used
COLD Default Print Indicates the type of • None
Overlay overlay to be used for
COLD documents that • Text
are printed or e-mailed.
• Image
COLD Default View Indicates the type of • None
Overlay overlay to be used for
COLD documents that • Text
are viewed.
• Image
COLD Show Color Bars Indicates whether color • True
bars will display with
COLD documents. • False
COLD Text Font: Name Specifies the name of Depends on
the font to use for text. the fonts
available on the
computer where
AppXtender
User Profile
Administrator
is installed.
COLD Text Font: Size Specifies the size to use 6-24
for the selected font.
COLD Text Font: Unit Specifies the unit for the • World
font size.
• Pixel

• Point

• Inch

• Document

• Millimeter

ApplicationXtender Web Access .NET Administrator’s Guide 169

Managing User Profiles

Available
Category Setting Name Description Options
COLD Text Font: Bold Displays text in bold • True
typeface.
• False
COLD Text Font:
GdiCharSet
COLD Text Font: • True
GdiVerticalFont
• False
COLD Text Font: Italic Displays text in Italic • True
typeface.
• False
COLD Text Font: Displays text with • True
Strikeout strikeout formatting.
• False
COLD Text Font: Displays text with • True
Underline underline formatting.
• False
COLD Text Font for Text Specifies the name Depends on
Overlay: Name of the font to use for the fonts
overlay text. available on the
computer where
AppXtender
User Profile
Administrator
is installed.
COLD Text Font for Text Specifies the size to use 6-24
Overlay: Size for the selected font.
COLD Text Font for Text Specifies the unit for the • World
Overlay: Unit font size.
• Pixel

• Point

• Inch

• Document

• Millimeter
COLD Text Font for Text Displays overlay text in • True
Overlay: Bold bold typeface.
• False
COLD Text Font for
Text Overlay:
GdiCharSet

170 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
COLD Text Font for • True
Text Overlay:
GdiVerticalFont • False
COLD Text Font for Text Displays overlay text in • True
Overlay: Italic Italic typeface.
• False
COLD Text Font for Displays overlay • True
Text Overlay: text with strikeout
Strikeout formatting. • False
COLD Text Font for Displays overlay • True
Text Overlay: text with underline
Underline formatting. • False
Display Automatically Indicates whether • True
Resume the users can resume
Checkout checkout of a document • False
that they have closed,
but neglected to check
in.
Display Default Image Indicates the default 25%, 50%, 75%,
Size image viewing size. 100%, 150%, 200%
(In AppXtender Web
IRC mode, this setting
is used only when
the Interactive Viewer
Default Image Size
setting is set to User
Settings.)
Display Display Shows thumbnails in • True
Document Document Window.
Thumbnails • False
Display Enable HTML Indicates whether • True
Rendering HTML export of foreign
files is enabled for the • False
AppXtender Web IRC.
Display Printer Friendly For printer-friendly 75, 100, 150, 200,
View Options: display of document 300, 400, or 600
DPI pages, indicates the DPI DPI
(dots per inch).

ApplicationXtender Web Access .NET Administrator’s Guide 171

Managing User Profiles

Available
Category Setting Name Description Options
Display Printer Friendly For printer-friendly • True
View Options: display of document
Fit to Height pages, indicates • False
whether the image
should be scaled to fit
the height of the page.
Display Printer Friendly For printer-friendly Integer
View Options: display of document
Margins: Left pages, indicates the
and Right width of the left and
right margins, in inches
Display Printer Friendly For printer-friendly Integer
View Options: display of document
Margins: Top pages, indicates the
and Bottom height of top and
bottom margins in
inches
Display Printer Friendly For printer-friendly Integer
View Options: display of document
Page Height pages, indicates the
height of the page in
inches
Display Printer Friendly For printer-friendly Integer
View Options: display of document
Page Width pages, indicates the
width of the page in
inches
Display Prompt For Enables display of • True
Checkout dialog box prompting
the user to check • False
out document when
document is first
displayed.
Email Use PDF format Sets the format for text
if possible and images in e-mail
messages to PDF.
Email Use XPS format Sets the format for text
if possible and images in e-mail
messages to XPS.

172 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
Email 4 or 8 Bit Color Indicates the type of • Windows
Images image to be used for Bitmap
4 or 8 bit color image
attachments. • Compressed
Windows
Bitmap

• GIF

• TIFF

• Compressed
TIFF
Email Black and White Indicates the type of • Windows
Images image to be used for Bitmap
black and white image
attachments. • TIFF

• Compressed
TIFF
Email Cold Form Indicates the type of • None
Overlay overlay to be used for
COLD documents that • Text
are printed or e-mailed.
• Image
Email Email Address User e-mail origination • (auto)
address. For
information on • E-mail address
automatic e-mail
registration, see
Configuring Automatic
E-mail Registration,
page 181.
Email Email JPEG Indicates the JPEG Integer (1-100,
Quality Factor compression for e-mail where 1 is lowest
attachments in JPEG and 100 is highest)
format.
Email Email Text Indicates whether • Text
Format text attachments are
included as text or • Image
images.
Email Message Format Indicates the format of • Text
e-mail messages.
• HTML

ApplicationXtender Web Access .NET Administrator’s Guide 173

Managing User Profiles

Available
Category Setting Name Description Options
Email Send As Indicates whether a • Hyperlink -
Hyperlink document or page is True
sent as a hyperlink
referencing the • Attachment -
document or page False
or as an attachment
Email True Color Indicates the type • Compressed
Images of image to be used Windows
for true color image Bitmap
attachments.
• GIF

• JPEG

• TIFF

• Compressed
TIFF
Email Use Archive File Indicates whether or • True
Format not the archive format
configured for export is • False
used
Email Use Multi-Page Indicates whether • True
Files attachments in a
multi-page format can • False
be sent as multi-page
files.
Full Text Automatically Enables automatic • True
Index New Doc submittal of new
documents for full • False
text indexing.
Full Text Convert To Text Enables automatic text • True
conversion.
• False
Full Text Default OCR Specifies the language You can choose
Language used for the OCR from 29 different
full-text indexing languages.
engine.
Full Text Enable Full Text Indicates whether full • True
text search functionality
is available for the user • False
profile.

174 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
Full Text Enable Indicates whether • True
Thesaurus the Thesaurus file is
located on the server • False
while performing
full-text queries.
Only applicable if the
Verity for AppXtender
full-text engine is
installed.
Indexing Enable Dual Data Enables Dual Data • True
Entry Entry for index terms.
• False
Indexing Ignore Indicates whether • True
Datestamp Date Stamps should
be ignored while • False
displaying documents.
Indexing Max Document Indicates the maximum Integer
Indexes number of indexes
that reference a single
document.
Interactive Default Image Indicates the default • Original
Viewer Size image viewing size for
AppXtender Web IRC • Page Width
viewing.
• Page Height

• Fit to Window

• User Settings
Interactive Display Indicates whether the • True
Viewer Annotation Annotation toolbar
Toolbar will appear within the • False
AppXtender Web IRC.
Interactive Display Scan Indicates whether the • True
Viewer Toolbar Scan toolbar will appear
within the AppXtender • False
Web IRC.
Interactive Enable IRC Enables the • True
Viewer AppXtender Web IRC.
• False

ApplicationXtender Web Access .NET Administrator’s Guide 175

Managing User Profiles

Available
Category Setting Name Description Options
Interactive Enable KeyView If KeyView is installed, • True
Viewer uses KeyView to
render foreign files • False
on the client side in
the AppXtender Web
IRC. If MS Office is
installed, this setting
allows supported MS
Office documents to
display in an embedded
Office Viewer.
Interactive Export Format: Sets the export format
Viewer Use PDF format for document images
if possible and text to PDF.
Interactive Export Format: Indicates the type of • Windows
Viewer 4 or 8 Bit Color image to be used for Bitmap
Images export of 4 or 8 bit color
images. • Compressed
Windows
Bitmap

• GIF

• TIFF

• Compressed
TIFF
Interactive Export Format: Indicates the type of • Windows
Viewer Black and White image format to be used Bitmap
Images for export of black and
white images. • TIFF

• Compressed
TIFF

• JPEG
Interactive Export Format: Indicates whether the • True
Viewer Export in configured archive file
Archived Format format is used when • False
documents and pages
are exported by the
user.
Interactive Export Format: Indicates whether text • Text
Viewer Export Text files are exported as text
Format or as images. • Image

176 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
Interactive Export Format: Indicates the JPEG Integer (1-100,
Viewer JPEG Quality compression. where 1 is lowest
Factor and 100 is highest)
Interactive Export Format: Indicates the type of • Compressed
Viewer True Color image to be used for Windows
Images export of true color Bitmap
images.
• GIF

• JPEG

• TIFF

• Compressed
TIFF
Interactive Export Format: Indicates whether file • True
Viewer Use Multi-Page types that support
Files multi-page formats are • False
exported as multi-page
files.
Interactive Import Format: Indicates the type of • Default
Viewer 4 or 8 Bit Color image to be used for
Images import of 4 or 8 bit color • TIFF
images.
• Windows
Bitmap
Interactive Import Format: Indicates the type of • Default
Viewer Black and White image format to be used
Images for import of black and • TIFF
white images.
• Windows
Bitmap
Interactive Import Format: Indicates the JPEG Integer (1-100,
Viewer JPEG Quality compression for import where 1 is lowest
Factor of images stored in and 100 is highest)
JPEG format.
Interactive Import Format: Indicates whether • True
Viewer Separate Multi multi-page TIFF files
Page Tiffs are separated into • False
multiple documents
when imported into
AppXtender Web.

ApplicationXtender Web Access .NET Administrator’s Guide 177

Managing User Profiles

Available
Category Setting Name Description Options
Interactive Import Format: Indicates the type of • Default
Viewer True Color image to be used for
Images import of true color • TIFF
images.
• Windows
Bitmap

• JPEG
Interactive Print Indicates that • True
Viewer Endorsement documents should be
Options: endorsed when printed. • False
Endorse Printed
Pages
Interactive Print Indicates the text Text
Viewer Endorsement to be used as the
Options: endorsement.
Endorsement
Text
Interactive Print Indicates that the • True - allow
Viewer Endorsement endorsement should overlap
Options: overlap images.
Overlap • False - scale the
Endorsement image to avoid
on Image overlap
Interactive Print Indicates the • Lower Right
Viewer Endorsement endorsement position.
Options: Text • Lower Left
Position
• Upper Right

• Upper Left
Interactive Print Options: Indicates which mode • None
Viewer Acceleration of expedited printing
Mode should be used. • XipPrint

• Talaris

• Quick PCL
Interactive Print Options: Indicates whether to • True
Viewer Enable expedite printing.
Acceleration • False
Interactive Print Options: Indicates whether to • True
Viewer Enable Dithering create the illusion of
varying shades of gray. • False

178 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
Interactive Print Indicates whether to • True
Viewer Options: Print print the image with
Annotations annotations (depending • False
on privileges).
Interactive Print Options: Indicates whether to • True
Viewer Print Original print the image at the
Size original size. • False
Interactive Print Options: Indicates whether to • True
Viewer Print Text Notes print the image with the
text of text annotations. • False
Interactive Print Options: Indicates whether the • True
Viewer Show Print Print Options dialog
Options box should appear • False
before printing.
Interactive Result Set Print Indicates whether to • True
Viewer Options: Cancel cancel the print job on
on First Print the first print failure. • False
Failure
Interactive Result Set Print If an error occurs • True
Viewer Options: Enable when AppXtender Web
Page Fetch Retry attempts to retrieve • False
a page, AppXtender
Web continues trying
as many times as
designated by the
Page Fetch Retry Count
setting.
Interactive Result Set Print Indicates how many Integer
Viewer Options: Page times AppXtender Web
Fetch Retry attempts to retrieve a
Count page when an error
occurs.
Interactive Result Set Indicates that each • True
Viewer Print Options: document should be
Separate Jobs per printed as a separate • False
Document print job.
Interactive Scale To Gray Indicates whether Scale • True
Viewer to Gray is enabled for
AppXtender Web IRC • False
images.

ApplicationXtender Web Access .NET Administrator’s Guide 179

Managing User Profiles

Available
Category Setting Name Description Options
Query and Automatically Automatically opens • True
Result Set Open Single document if query
Display Document yields only one result. • False
Options
Query and Display Shows document ID in • True
Result Set Document ID Result Set.
Display • False
Options
Query and Document ID Determines the order • Ascending -
Result Set Sort Order documents are sorted Sorts Result Set
Display in Result Set. in ascending
Options order, lowest
to highest
document ID

• Descending -
Sorts Result Set
in descending
order, highest
to lowest
document ID

• Disable -
Documents are
not sorted by
document ID
Query and Enable MDI When a document is • True - Displays
Result Set View displayed from the documents
Display result set, this setting in a separate
Options determines whether browser
it is displayed in the window
same browser window
or a separate browser • False - Displays
window. documents
in the same
browser
window as the
result set.
Query and Enable ODMA Enables ODMA • True
Result Set Search attribute searching.
Display • False
Options

180 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Available
Category Setting Name Description Options
Query and Limit Query Controls the number of Integer (1-25, and
Result Set Results Page Size results that appear on must be less than
Display each page of the Result or equal to the
Options Set. Limit Search Size
value)
Query and Limit Search Size Controls the number Integer
Result Set of results AppXtender
Display Web will retrieve.
Options
Query and Show Document Shows document • True
Result Set Revisions revisions in Result
Display Set. • False
Options
Query and Text Search Indicates whether the • True
Result Set Enabled text search from result
Display set feature is enabled • False
Options
Query and Text Search Max Limits the maximum Integer (1-1000)
Result Set Hits number of text search
Display hits to be displayed.
Options

Note: For information on setting difference indicators, see Starting AppXtender User Profile
Administrator, page 164.
5. From the File menu, select Save Changes.

Configuring Automatic E-mail Registration

By default, before users can send documents by e-mail in AppXtender Web, they must register their
e-mail addresses in the system. (For instructions, refer to the "Registering Your E-Mail Address"
section of the ApplicationXtender Web Access User’s Guide.)
However, if the user names in your AppXtender system match the user names in your domain, you
can configure automatic e-mail registration by specifying a domain name.

To specify a domain:
1. From the Tools menu, select Email Auto Registration. The Email Auto Registration dialog box
appears.

ApplicationXtender Web Access .NET Administrator’s Guide 181

Managing User Profiles

Figure 125. Email Auto Registration Dialog Box

2. In the Domain Name text box, enter the name of the domain that you want to use for
automatically completing user e-mail addresses. For example, if you enter documentum.com,
the user name john.smith would be completed as [email protected].
3. Click OK.
4. From the File menu, select Save Changes.
The domain name you entered is used to construct the e-mail addresses for all users whose profiles
have an Email Address setting of (auto).

Exporting a Profile
You can export profile values listed in AppXtender User Profile Administrator to a file. When you
use the Export Profile command to save settings, you save the settings only to a file. Settings are not
saved to the User Profile table unless you save changes in the AppXtender User Profile Administrator
window. For more information on saving changes in the AppXtender User Profile Administrator
window, see Saving User Profile Setting Changes, page 186.

To export profile values to a file:

1. In the AppXtender User Profile Administrator window, the method to begin the export depends
on whether you want to export profile values for all users or for an individual user:
• If you want to export profile values for all users, select Tools> Export Profile.
• If you want to export profile values for an individual user, right-click the user whose profile
you want to export and select Export Profile.
The Export User Profile dialog box appears.

182 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Figure 126. Export User Profile Dialog Box

2. Browse to the location where you want to export the file.

3. Enter a file name in the File name text box.
4. Click Save to export the file.

Loading a User Profile for Editing

You can load an exported user profile file to edit the values in the file.

To load an exported profile:

1. In the AppXtender User Profile Administrator window, select Tools> Load Profile. The Load User
Profile dialog box appears.

ApplicationXtender Web Access .NET Administrator’s Guide 183

Managing User Profiles

Figure 127. Load User Profile Dialog Box

2. Browse to locate the user profile file that you want to load and click Open to load the file. A
message appears asking you to confirm replacement of existing profile data with the data from
the selected import file.
3. Click Yes.
The values specified in the file appear in the AppXtender User Profile Administrator window.
Note: For information on setting difference indicators, see Starting AppXtender User Profile
Administrator, page 164.

Merging User Profiles

You can append additional information from an exported profile to the information currently listed in
AppXtender User Profile Administrator.

To merge an exported profile with the currently listed information:

1. In the AppXtender User Profile Administrator window, select Tools> Merge Profile. The Merge
Profile Data dialog box appears.

184 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

Figure 128. Merge Profile Data Dialog Box

2. Browse to locate the user profile file that you want to merge and click Open to merge the file.
The values specified in the file appear in the AppXtender User Profile Administrator window.
For each setting, a non-default value overrides the default value. Otherwise, values in the file
override existing values. If the merge file does not contain a value for a particular setting, then
the existing setting does not change.
Note: For information on setting difference indicators, see Starting AppXtender User Profile
Administrator, page 164.

Restoring Default Values

If necessary, you restore default values in a variety of ways:
• You can reset one or more individual user profiles to match the Default User Profile. For
instructions, see Restoring Individual Profiles to Match the Default User Profile, page 186.
• You can reset all user profiles to match the Default User Profile. For instructions, see Restoring All
Profiles to Match the Default User Profile, page 186.
• You can reset all user profiles, including the Default User Profile, to the original set of user profile
values (the factory-default). For instructions, see Restoring All Profiles to Factory Defaults,
page 186.

Caution: When you restore defaults, you overwrite any customized user profile setting values
you may have configured. Restoring defaults also overwrites any changes to profile settings
that users may have done on their individual profiles.

ApplicationXtender Web Access .NET Administrator’s Guide 185

Managing User Profiles

Restoring Individual Profiles to Match the Default User

Profile
To restore individual profiles to match the Default User Profile:
1. In the AppXtender User Profile Administrator window, from the list of users on the left, select the
user profile or profiles that you want to restore.
2. Right-click the selection and select Reset to Default. The selected user profiles are reset to match
the Default User Profile.

Restoring All Profiles to Match the Default User Profile

To restore all profiles to match the Default User Profile:
1. In the AppXtender User Profile Administrator window, from Edit menu, select Reset All Profiles.
A message appears asking you to confirm the restoration of values to all profiles.
2. Click Yes. All user profiles are reset to match the Default User Profile.

Restoring All Profiles to Factory Defaults

You can reset all user profiles, including the Default User Profile, to the original set of user profile
values (the factory-default).

To restore default values to the database:

1. In the AppXtender User Profile Administrator window, select File> Restore Defaults. A message
appears asking you to confirm the restoration of all values in the utility to factory-default.
2. Select Yes. All user profiles are reset to the factory-default.

Saving User Profile Setting Changes

You can save the modifications you make to user profiles to the User Profile table in the database.

Caution: When you save changes to the user profiles, you are saving those changes to the User
Profile table in the database. When you save a modification for a setting, you overwrite any
customized user profile setting values for that setting that users may have configured.

186 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

To save changes:
• In the AppXtender User Profile Administrator window, select File> Save Changes. Any changes
that have not been saved are saved to the User Profile table in the database.

Undoing User Profile Setting Changes

You can undo changes without causing them to be written to the database, as long as those changes
have not been saved. For example, if you made changes to a loaded profile solely to save that
modified profile to a file, you may want to undo those changes and then make a different set of
changes to the actual User Profile table. You can use the Undo Changes function to undo the initial set
of changes. Undoing changes reverses all changes since the AppXtender User Profile Administrator
was last opened or changes were last saved, whichever was more recent. If no changes are available
to be undone, the option is dimmed.
To undo changes:
• In the AppXtender User Profile Administrator window, select File> Undo Changes. Any changes
that have not been saved are undone.

Copying a Profile from One User to Other Users

You can copy any user profile to any other user profile or profiles, using right-click menus or the
Copy Profile dialog box:
• When you need to copy to 250 profiles or fewer, the right-click menu method may be used. This
method copies all profile information. For instructions, see Copying Profiles Using the Right-click
Menus, page 187.
• When you need to copy to more than 250 profiles, the Copy Profile dialog box method is
most appropriate because it copies only settings that vary from the Default User Profile. For
instructions, see Copying Profiles Using the Copy Profile Dialog Box, page 188.

Caution: When you copy a profile to a user, you are saving that profile for that user to the User
Profile table in the database. This action may overwrite any customized user profile setting
values that the user may have configured.

Copying Profiles Using the Right-click Menus

When you need to copy to 250 profiles or fewer, the right-click menu method may be used. This
method copies all profile information.

Caution: If you use the right-click menus to copy profiles, performance decreases with the
number of profiles to which you are copying. When you need to copy to more than 250 profiles,
consider using the Copy Profile dialog box instead. For instructions, see Copying Profiles
Using the Copy Profile Dialog Box, page 188.

ApplicationXtender Web Access .NET Administrator’s Guide 187

Managing User Profiles

To copy profiles using the right-click menus:

1. In the AppXtender User Profile Administrator window, from the list of users on the left, select the
user profile that you want to copy.
2. Right-click the selection and select Copy.
3. Select the user profile or profiles to which you want to paste the copied profile.
4. Right-click the selection and select Paste.
5. From the File menu, select Save Changes.

Copying Profiles Using the Copy Profile Dialog Box

When you need to copy to more than 250 profiles, the Copy Profile dialog box method is most
appropriate because it copies only settings that vary from the Default User Profile.

To copy profiles using the Copy Profile dialog box:

1. Select the user profile that you want to copy.
2. Right-click the selection and select Copy To. The Copy Profile dialog box appears. The Source
User Profile text box indicates the user profile that you selected to copy from.

Figure 129. Copy Profile Dialog Box

3. In the Available Users list, select the user profiles to which you want to paste the source user
profile.
4. Click the>> button. The selected user profiles move to the Selected Users list.
5. Click OK.

188 ApplicationXtender Web Access .NET Administrator’s Guide

 Managing User Profiles

6. From the File menu, select Save Changes.

ApplicationXtender Web Access .NET Administrator’s Guide 189

Managing User Profiles

190 ApplicationXtender Web Access .NET Administrator’s Guide

 Appendix C
Maintaining AppXtender Web Access
Installations

The following sections describe how to repair or remove AppXtender Web Access or Rendering
Server:
• Maintaining AppXtender Web Access .NET Server, page 191
• Maintaining AppXtender Rendering Server, page 192

Maintaining AppXtender Web Access .NET

Server
For information about repairing or removing AppXtender Web Access .NET, see the following
sections:
• Repairing AppXtender Web.NET, page 191
• Uninstalling AppXtender Web.NET, page 192

Repairing AppXtender Web.NET

You can choose to repair your AppXtender Web Access installation using the AppXtender Web
Access Setup Repair utility. Repair reinstalls missing or corrupt files, registry keys, and shortcuts.

Caution: Repairing AppXtender Web may reset AppXtender Web preferences stored in the
registry to their default values.

To repair your AppXtender Web Access installation:

1. From the Start menu, select Settings, then Control Panel. From the Control Panel, double-click
Add/Remove Programs. Select AppXtender Web Access from the list of programs, then click
Change or Change/Remove.
The AppXtender Web Access Setup Application Maintenance page appears.
2. Select Repair and click Next. Ready to Repair the Application page appears.

ApplicationXtender Web Access .NET Administrator’s Guide 191

Maintaining AppXtender Web Access Installations

3. Click Next. The Updating System page appears. The AppXtender Web installation repair begins.
When the repair is complete, a window appears confirming a successful installation.
4. Click Finish to complete the AppXtender Web repair.
5. An Installer Information dialog box may appear recommending that you restart your computer. If
you receive this message, click Yes to restart your computer. If you do not restart your computer,
AppXtender Web Access may not run properly.

Uninstalling AppXtender Web.NET

You can uninstall AppXtender Web Access .NET using the Windows Add/Remove Programs utility.

To uninstall AppXtender Web Access:

1. From the Start menu, select Settings, then Control Panel. From the Control Panel, double-click
Add/Remove Programs. Select AppXtender Web Access .NET from the list of programs, then
click Change or Change/Remove. The AppXtender Web Access Setup Application Maintenance
page appears.
2. Select Remove and click Next. The AppXtender Web Access .NET Uninstall page appears.
3. Click Next to continue with the uninstall process. The Updating System page appears while
AppXtender Web Access files are being removed.
4. When the uninstall process is complete, a window appears confirming a successful uninstall.
Click Finish to complete the AppXtender Web uninstall.
5. An Installer Information dialog box may appear recommending that you restart your computer.
If you receive this message, click Yes to restart your computer.

Maintaining AppXtender Rendering Server

For information about repairing or removing AppXtender Rendering Server, see the following
sections:
• Repairing AppXtender Rendering Server, page 192
• Uninstalling AppXtender Rendering Server, page 193

Repairing AppXtender Rendering Server

You can choose to repair your AppXtender Rendering Server installation using the AppXtender
Rendering Server Setup Repair utility. Repair reinstalls missing or corrupt files, registry keys, and
shortcuts.

192 ApplicationXtender Web Access .NET Administrator’s Guide

 Maintaining AppXtender Web Access Installations

To repair your AppXtender Rendering Server installation:

1. From the Start menu, select Settings, then Control Panel. From the Control Panel, double-click
Add/Remove Programs. From the list of programs, select AppXtender Rendering Server, and
then click Change or Change/Remove.
The AppXtender Rendering Server Setup Application Maintenance page appears.
2. Select Repair and click Next. Ready to Repair the Application page appears.
3. Click Next to begin repairing AppXtender Rendering Server. The Updating System page appears
while the AppXtender Rendering Server installation is being repaired. When the repair is
complete, a window appears confirming a successful installation.
4. Click Finish to complete the AppXtender Rendering Server repair.
5. An Installer Information dialog box may appear recommending that you restart your computer.
If you receive this message, click Yes to restart your computer. If you do not restart your
computer, AppXtender Rendering Server may not run properly.

Uninstalling AppXtender Rendering Server

You can uninstall AppXtender Rendering Server using the Windows Add/Remove Programs utility.

To uninstall AppXtender Rendering Server:

1. From the Start menu, select Settings, then Control Panel. From the Control Panel, double-click
Add/Remove Programs. From the list of programs, select AppXtender Rendering Server, and
then click Change. The Welcome to AppXtender Rendering Server Repair, Remove page appears.
2. Select Next. The Program Maintenance page appears.
3. Enable the Remove option and click Next. The Ready to Remove the Program page appears.
4. Click Remove. The removal process begins. When removal is complete, the application does not
appear in the Windows Add/Remove Programs list.
Note: Restart your computer before installing the latest release of the component.

ApplicationXtender Web Access .NET Administrator’s Guide 193

Maintaining AppXtender Web Access Installations

194 ApplicationXtender Web Access .NET Administrator’s Guide

 Glossary

This glossary contains terms related to ApplicationXtender (AppXtender) components. Many of

these terms are used in this manual.

accessible security
Accessible security grants access to the users in the group for only documents with index
field values matching the secured value list. (See also Document Level Security.)

annotation
An annotation is a note or a shape added to a document or batch page, typically to focus
attention on a particular part of the page. Users can use annotations to comment on the
contents of a page, block areas of the page from view, or highlight important information.
When a user creates an annotation, it is associated with the AppXtender page on which he
or she created it. Annotations are edited and stored separately from the image, but they
are displayed along with the image in AppXtender Document Manager and Web Access.
The types of annotations available include text, highlighting, lines, arrows, shapes, and
rubber stamps.

annotation group
Annotation groups allow you to create associations between users, groups, and specific
annotations. You can specify which users and groups can view or modify specific
annotations, and which users and groups can hide or modify specific redactions.

appender
An appender allows you to select the specific AppXtender Web Access .NET or Rendering
Server information you want to log and to publish that information to a specific reporting
venue.

application
An AppXtender application is an index-driven data storage structure where documents can
be stored and retrieved. An AppXtender application is based on an index that is composed
of one or many fields. AppXtender applications are created in AppXtender Application
Generator (AppXtender AppGen).

application security profile

Application security profiles, like global security profiles, allow you to grant a particular set
of privileges to a user or group of users. You can define different privileges for a user or
group of users in each application.
When a profile is application-specific, however, the privilege settings are not carried over to
a new application when it is created. If a group of users has an application-specific profile
for a certain application, but no global profile, then when a new application is created, the

ApplicationXtender Web Access .NET Administrator’s Guide 195

Glossary

members of the group will not be able to access the new application. Application-specific
security settings override global security settings.

ApplicationXtender Auto Index Import

AppXtender Auto Index Import allows use of the <F7> key to import index values from a text
file, so users adding documents can automatically populate indexes using the imported data.
Auto Index is ideal for the import of index records that are applicable to only one document.
In an Auto Index Import table, once a record (or a group of index values) has been used
to index a document, the record is deleted.

ApplicationXtender Index Image Import

AppXtender Index Image Import allows you to import index data and document files in a
single step. A text file is required which contains a line of text for each document to be
imported, with a value for each index field and a reference to the location of the file to be
imported. No manual document indexing is required.

ApplicationXtender Index Server

ApplicationXtender Index Server is an optional module that adds full-text indexing and
OCR functionality to AppXtender systems.

ApplicationXtender Key Reference Import

AppXtender Key Reference Import allows use of the <Tab> key to import index values from a
text file. Key Reference is most effectively used in situations where each imported record
may describe several documents. Key Reference Import maintains the index records in the
Key Reference table even after records have been used to index documents. Any change
made to a record in the Key Reference table is reflected in the indexes of all documents
described by that record.

audit trail
The Audit Trails feature allows you to track user activity within the AppXtender system.
System-wide activities such as the creation, modification, and deletion of applications, users,
and groups can be tracked. You can also track user activity in applications by tracking items
such as the creation and deletion of documents, the addition of pages, and the modification
of index information for documents. By default, AppXtender logs audit trail events to a
table in the AppXtender database. You can configure audit trails to log to this table, to a log
file, or to both locations.

authentication
Authentication requires all users to enter a valid user name and password to access software
modules. Authentication ensures that each user is who he or she claims to be.

authorization
Authorization is the granting of specific access privileges according to the user name.
Security profiles contain information pertaining to a user’s specific privileges within the
AppXtender system.

check in/check out mode

When an AppXtender application or an AppXtender Document Manager workstation is in
check in/check out mode, use of revision control with AppXtender documents is mandatory.

196 ApplicationXtender Web Access .NET Administrator’s Guide

 Glossary

Users must check out a document in order to modify it. If they do not check the document
out, it is opened in read-only mode and it cannot be modified.

COLD
COLD (computer output to laser disk) data is report data generated for existing applications.
COLD data can be added to AppXtender as documents through the use of AppXtender
Reports Management (AppXtender Reports Mgmt).

collection
A collection is a K2 full-text database.

data source
A data source is the means by which AppXtender accesses data from a database. When a
data source is defined, an OLE DB data provider is configured to access the database. All of
these characteristics in combination – where the data is stored, the format of the data stored,
and the data provider used to access the data – comprise the data source.

data source group

A data source group in ApplicationXtender Administrator (AppXtender Admin) associates a
list of data sources with everything that has been configured in AppXtender Admin, such
as ApplicationXtender Web Access (AppXtender Web) settings and connections to License
Server computers. This feature provides convenience in that the work of configuration does
not have to be repeated every time you create a data source.

database
A database is a collection of data tables of a particular database format (such as Oracle or
Microsoft SQL Server). AppXtender uses databases to store application information. When
an application is created, details such as the field definitions and security information are
stored in database tables. Once documents are added to an application, index information is
stored in a table, as are the pointers to the location of the documents.

document
A document is a page or group of pages stored in an application and identified by index
information. Each page of a document is comprised of a single object such as a scanned
image file or a word processing document. To create a new document, users add an object
to an application and attach index information to it. Subsequent objects can be added as
additional pages of the same document.

Document Level Security

Document Level Security (DLS) pinpoints user access within an AppXtender application.
With DLS, you can deny a group of users access to any classified or sensitive document(s),
without restricting access to other documents in the application. DLS can also be configured
to grant a group of users access to only a specific set of documents in an application.

ERM
ERM (enterprise report management) data is report data generated for existing applications.
ERM data can be added to AppXtender as documents through the use of ApplicationXtender
Reports Management (AppXtender Reports Mgmt).

ApplicationXtender Web Access .NET Administrator’s Guide 197

Glossary

extended applications
Extended applications are AppXtender applications that can be called from within other
software applications, adding document storage and processing functions.

full-text
Users can index documents for full-text searching by submitting them to the AppXtender
Index Server. With a full-text search, users can find documents even if they do not know any
of the index values. Users can also use full-text searching to refine an index value search.

global security profile

Global security profiles can be established to automatically assign a uniform set of access
privileges for a user or group of users every time a new application is created. When a
global profile exists for a user or group of users, the privileges assigned in that profile are
automatically assigned for every application created. If a user or group of users does not
have a global profile, an application-specific profile must be created for that user or group
before they can access an application.

grab bar
An AppXtender Document Manager docked view has a grab bar. A grab bar is similar to a
title bar except that it does not contain a title.

impersonation account
The AppXtender Index Server impersonation account grants security privileges to
AppXtender Index Server and is essential for the AppXtender Index Server to operate
properly. AppXtender Index Server uses the AppXtender Index Server impersonation
account to access remote and server resources, including AppXtender document paths,
the License Server, the registry, and the image repository (in some cases, the DiskXtender
Document Server).

import specification
A specification is a set of rules that AppXtender follows when importing data from an
import file using the AppXtender Auto Index Import, Index Image Import, or Key Reference
Import wizard.

inaccessible security
Inaccessible security denies access to the users in the group for documents with index field
values matching the secured value list. (See also Document Level Security.)

index
An AppXtender index contains a group of fields where descriptive information pertaining
to documents can be stored. This group of field definitions is used by AppXtender when
storing index information within an application.

node
A node is an element of a tree structure such as in AppXtender Admin, AppGen, Document
Manager, or Reports Mgmt. A node can be expanded to reveal subnodes or can be collapsed.

198 ApplicationXtender Web Access .NET Administrator’s Guide

 Glossary

OCR
Users can process bi-tonal images using optical character recognition (OCR). This process
converts an image of text into text. After a user processes an image using OCR, it can then be
submitted to the AppXtender Index Server for full-text searching.

ODMA
Open Document Management API (ODMA) support allows users to work with AppXtender
documents within other ODMA-compliant applications.

OLE DB
OLE DB is a programming interface for accessing data, and is a fundamental building block
for storing and retrieving data using Microsoft’s Data Access Components (MDAC). OLE DB
provides flexible data architecture that offers applications like AppXtender efficient access to
databases. Data is accessed through OLE DB data providers

page
The word “Page” typically implies a single entity. Since AppXtender supports multiple
object types, the term “page” is redefined within AppXtender to mean a single object. A very
long word processing file is considered a page to AppXtender. A page could also be, for
example, a single scanned image, a 30-minute video clip, or an audio recording. Each page of
a document has the same index record attached.

privileges
Privileges govern the ability of a user or group of users to access functions in AppXtender.

redaction
A redaction is a filled and opaque annotation shape that can be used to secure or hide
portions of image and text pages. Users can apply redaction to all available annotations.
When applied, the area of the page behind the redaction is not visible.

security
Security is the combination of authentication and authorization.

security mapping
When AppXtender Migration is used to migrate documents and security information,
the administrator has the option to map users and groups in the source database to users
and groups in the destination database. Similarly, when the ApplicationXtender Media
Distribution (AppXtender Distribution) Extraction Wizard is used to extract AppXtender
documents and security information before the creation of an AppXtender Distribution
CD-ROM, the administrator has the option to map users and groups in the source database to
users and groups in the database on the CD-ROM (or in the database where the CD-ROM
will be reintegrated).

security provider
Security providers implement authentication, which requires all users to enter a valid user
name and password to access most modules. AppXtender Admin offers two pre-packaged
security providers (CM and Windows) to ensure that each user is who he or she claims to be.
You can also create a directory service security provider, if necessary.

ApplicationXtender Web Access .NET Administrator’s Guide 199

Glossary

write paths
Write paths are used to instruct AppXtender where to store documents, annotations, OCR
output, and the ProIndex full-text database for a particular AppXtender application.

200 ApplicationXtender Web Access .NET Administrator’s Guide

 Index

A cached page
appending user profile info, 184 cached image type, 38
application credentials garbage collection, 40
data source, 50 changing the default viewer for
ApplicationXtender Data Source Features thumbnails, 100
wizard, 76, 109, 159 checked out documents, 156
AppXtender Component Registration, 130 managing, 156
AppXtender Rendering Server viewing, 156
cache configuration, 35, 66 client download of JDK, configuring, 98
configuration, 33 clients
database configuration, 36, 64 IBM DB2, configuring, 119
login account, 33, 62 IBM DB2, installing, 118
repairing installation, 192 Oracle, configuring, 122
uninstalling, 193 Oracle, installing, 122
AppXtender Web Access Sybase SQL Anywhere, installing, 124
Administrator e-mail information, 87 COLD settings, 168
automatic restart after config color bar settings, 168
updates, 96 component registration, 130
global authentication account, 43, 79 configuration wizard, AppXtender
node, showing/hiding, 19 Web.NET, 41
repairing installation, 191 configuring
uninstalling, 192 client download of JDK, 98
AppXtender Web Services database clients, IBM DB2, 119
standalone vs. integrated mode, 20 database clients, Oracle, 122
AppXtender Web.NET Configuration logging, 102
Wizard, 41 thumbnails, 99
authentication account, 21 uniform functionality, 163
automatic features conversion settings
e-mail registration, 181 foreign files, 38
restart after config updates, 96 images, 38
copying user profile, 187
creating an ODBC data source
B MySQL, 128
blank settings in AppXtender User Profile Sybase SQL Anywhere, 124
Admin, 166
bold values in AppXtender User Profile
Admin, 166
D
data source
locating for AppXtender Rendering
C Server, 131
cached image type, 38 locating for AppXtender Web.NET, 131

ApplicationXtender Web Access .NET Administrator’s Guide 201

Index

locating, IBM DB2, 136 FrontPage, installation considerations, 27

locating, MySQL, 137 full text jobs, 154
locating, Oracle, 134 managing, 155
locating, SQL Server, 132 viewing, 155
locating, Sybase, 139 full text settings, 174
locating, Sybase SQL Anywhere, 139
selecting on login, 150
data sources
G
multiple, 19 garbage collection, 40
specifying default, 18 GIF vs. JPEG, 38
data sources, selecting, 18 global credentials, 43, 79
default data source, 50
data sources, specifying, 18 global e-mail addresses
display settings, 171 adding, 90 to 91
download of JDK, configuring client, 98 importing, 93
sorting, 95

E
e-mail
H
address book, 88 hiding
enabling, 59, 85 AppXtender Web Access node, 19
registration, automatic, 181 HTML rendering
settings, 172 enabling, 39
e-mail page wait time, 39
adding global addresses, 90 to 91
address book, 88 I
AppXtender Web Administrator e-mail IBM DB2
information, 87 configuring clients, 119
global addresses, 88 installing clients, 118
importing global addresses, 93 locating a data source, 136
sorting global addresses, 95 IIS
embedded Office Viewer, 82, 176 installation considerations, 23
enabling e-mail, 59, 85 Image conversion, 38
export format settings, 176 format, 38
exporting user profiles to XML, 182 max wait time, 38
image form overlay options, 39
F impersonation account
file types See authentication account, 21
adding, 83 import format settings, 177
configuring, 81 indexing settings, 175
deleting, 85 installing
modifying, 84 AppXtender Rendering Server, 104
file types page, 81 AppXtender Web.NET, 109
adding file types, 83 IBM DB2 Client, 118
deleting a file type, 85 IIS, 23
Foreign File conversion, 38 Oracle Client, 122
enabling, 39 preparing AppXtender Admin
max wait time, 39 environment, 16
form overlay font, 39 preparing AppXtender Web.NET
Server, 26

202 ApplicationXtender Web Access .NET Administrator’s Guide

 Index

Sybase SQL Anywhere clients, 124 Microsoft

to non-default web site, 27 FrontPage, installation
integrated mode, AppXtender Web considerations, 27
Services, 21 multiple
interactive viewer settings, 175 data sources, 19
Internet Information Server. <em MySQL
Emphasis, 23 creating an ODBC data source, 128
locating a data source, 137
J
JDK, configuring client download of, 98 N
JPEG vs. GIF, 38 Net Configuration Assistant, Oracle client
configuration, 123
Net Manager, Oracle client
L configuration, 122
license agreement page, 106, 111
license groups, 20
License Server, 19 O
licensing AppXtender Web Access OCR jobs, 154
information, 19 ODBC data source, creating for
loading user profiles, 183 MySQL, 128
locating a data source Sybase SQL Anywhere, 124
for AppXtender Rendering Server, 131 online administration, 149
for AppXtender Web.NET, 131 navigation, 151
IBM DB2, 136 session management, 152
MySQL, 137 Oracle
Oracle, 134 configuring clients, 122
SQL Server, 132 installing clients, 122
Sybase, 139 locating a data source, 134
Sybase SQL Anywhere, 139
locked documents, 157
managing, 158
P
viewing, 158 preparing AppXtender components as
logging, 102 database clients, 117
IBM DB2, 118
MySQL, 127
M Oracle, 122
maintaining Sybase SQL Anywhere, 123
AppXtender Rendering Server print endorsement settings, 178
installation, 192 print settings, 178
maintaining AppXtender Web printer friendly view settings, 171
installation, 191 profiles
managing user in AppXtender User Profile
AppXtender Web online, 149 Admin, 163
sessions, 152 public access licensing, 20
user profiles in AppXtender User
Profile Admin, 163
margin settings, 172
Q
max. entries, 40 query settings, 180
merging user profiles, 184

ApplicationXtender Web Access .NET Administrator’s Guide 203

Index

R SQL Server, locating a data source, 132

registering standalone mode, AppXtender Web
AppXtender components, 130 Services, 20
e-mail addresses automatically, 181 starting AppXtender User Profile
when to register again, 130 Admin, 164
reinstalling supplied credentials
AppXtender Rendering Server, 192 data source, 50
reinstalling AppXtender Web, 191 Sybase
repairing AppXtender Rendering locating a data source, 139
Server, 192 Sybase SQL Anywhere
repairing AppXtender Web Access, 191 creating an ODBC data source, 124
resizing installing clients, 124
thumbnail views, 99 locating a data source, 139
restoring defaults in AppXtender User
Profile Admin, 167, 185 T
restoring profiles terminating sessions, 153
to default profile, 186 Thin Client, image form overlay font
to factory-default, 186 for, 39
result set display settings, 180 thumbnail views, resizing, 99
result set print settings, 179 thumbnails
rights changing the default viewer for, 100
needed to install AppXtender thumbnails, configuring, 99
Rendering Server, 23
needed to install AppXtender
Web.NET, 27 U
rubber stamp, configuring security, 159 undoing changes in AppXtender User
Profile Admin, 167, 187
uninstalling
S AppXtender Rendering Server, 193
saving changes in AppXtender User Profile AppXtender Web.NET, 192
Admin, 167, 186 upgrading AppXtender Web Access
security Server, 31
configuring for AppXtender URL
Web.NET, 57, 80 for AppXtender Web.NET Server, 147
configuring rubber stamp, 159 user profile
security provider managing in AppXtender User Profile
selecting for data source, 52 Admin, 163
selecting a data source on AppXtender Web
login, 150
session W
cache, configuring, 54, 77 web applications, automatic restart after
managing, 152 updates, 96
terminating, 153 web site
time-out, configuring for AppXtender installing to non-default, 27
Web.NET Server, 78 web.config file, settings
showing default thumbnail viewer, 100
AppXtender Web Access node, 19 monitoring configuration updates, 96
sorting global e-mail addresses, 95 resizing thumbnail views, 99
SQL Server trace logs, 102
locating a data source, 132 WebXtender

204 ApplicationXtender Web Access .NET Administrator’s Guide

 Index

upgrading, 31 ApplicationXtender Data Source

Windows Server 2008 Features, 76, 109, 159
installation considerations, 22 to 23, 27 AppXtender Web.NET
wizards configuration, 41

ApplicationXtender Web Access .NET Administrator’s Guide 205