Document Exchange Server 2.5

Transcription

1 KOFAX Document Exchange Server 2.5 Installation Guide for WebLogic

2 Kofax, Inc., Laguna Canyon Road, Irvine, California 92618, U.S.A. All rights reserved. Use is subject to license terms. Third-party software is copyrighted and licensed from Kofax s suppliers. For information on third-party software included in this product, see DESTHIRDPARTYLICENSEREADME.txt. This product is protected by U.S. Patent No. 6,370,277. THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF KOFAX, INC. USE, DISCLOSURE OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF KOFAX, INC. Kofax, the Kofax logo, VirtualReScan, the VRS VirtualReScan logo, and VRS are trademarks or registered trademarks of Kofax, Inc. in the U.S. and other countries. All other trademarks are the trademarks or registered trademarks of their respective owners. U.S. Government Rights Commercial software. Government users are subject to the Kofax, Inc. standard license agreement and applicable provisions of the FAR and its supplements. You agree that you do not intend to and will not, directly or indirectly, export or transmit the Software or related documentation and technical data to any country to which such export or transmission is restricted by any applicable U.S. regulation or statute, without the prior written consent, if required, of the Bureau of Export Administration of the U.S. Department of Commerce, or such other governmental entity as may have jurisdiction over such export or transmission. You represent and warrant that you are not located in, under the control of, or a national or resident of any such country. DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

3 Contents Introduction...1 Related Documentation...1 Administrator s Guide...1 Kofax Document Exchange Server Installation Guide...2 Software Installed with Kofax Document Exchange Server...2 Supported System Configurations...2 System Requirements...3 Managed Server Requirements...3 Operating System...3 Minimum Hardware Requirements...3 Certified VMWare Configurations...3 Certified VMWare Configurations...4 Open Ports...4 Client Requirements...4 Certified Web Browsers...5 Adobe Reader Requirement...5 Monitor Display Resolution...5 Pre-Installation Planning...5 Network Configuration Requirements...5 Cluster Planning...5 Installing on a Local Drive...5 Requirement for Free Hard Drive Space...5 Dedicated Server Requirement...6 Registry Access...6 Restarting the Server...6 Invalid Drive Path...6 Using Kofax Document Exchange Server on a Virtual Machine (VM)...6 Security Settings for Browsers...6 Text Resizing in Browsers...7 Migrating from a Previous Version of Kofax Document Exchange Server on WebLogic...7 Installation Notes for 64-Bit Computers...7 Installing Kofax Document Exchange Server...7 Setting Environment Variables...7 Getting Oracle Connection Information...8 Creating Shared Folders...8 Sharing the Configuration Files...8 Installing the Kofax Document Exchange Server Components...9 Kofax, Inc. iii

4 Contents Installing on One Machine...9 Installing on Separate Machines (one or more managed servers on the same domain as the administration and proxy server)...10 Preparing an Oracle Database...12 Recovering from a SQL Failure...13 Configuring the install.properties File...13 Mandatory Settings...14 Java configuration...14 OS Configuration...14 Initial admin user to deploy license and workflow...15 Information about the WebLogic installation...15 Domain configuration...15 Cluster configuration...16 Managed servers configuration...17 Cluster URL configuration...20 Proxy server configuration...20 Server Java VM startup options...21 Oracle DB Configuration...21 Optional Custom Settings...22 About the Installation Scripts...23 Running the Installation Scripts...24 Install Managed Servers...25 Install a Proxy Server...25 Deploy the Proxy Server...26 Deploy Document Exchange Server...26 Special Instructions for Installing on Non-English Operating Systems...27 Recovering from Install Script Failure...27 Starting the Cluster...27 Viewing the Installation Log Files...28 Uninstalling Kofax Document Exchange Server...28 Adding New Managed Servers to a Cluster...29 install.properties: An Example...30 What s in Weblogic Administration Console?...34 What Needs to be Done After Installation?...34 Configuring for Oracle RAC...35 Create the XA Data Sources...35 Create the XA Multi Data Source...37 Create the Non-XA Data Sources...38 Create the Non-XA Multi Data Source...40 Reset the Persistent Stores Data Source...40 Configuring Destination Types...41 Deploying Connectors for Additional Destinations...42 Installing MFP Front Panel Software...45 iv Kofax, Inc.

5 Contents Other Configuration Tasks...45 What if Port 7001 is in Use: Changing the Admnistration Server Port...45 Changing the WebLogic Administrator Credentials...46 Stopping and Restarting Kofax Document Exchange Server...46 Troubleshooting...46 Technical Support...47 Kofax, Inc. v

6 Contents vi Kofax, Inc.

7 Introduction This guide includes instructions on installing Kofax Document Exchange Server with a WebLogic 9.2 MP3 (maintenance pack 3) application server. Read this guide completely before using the software. This guide was written with the assumption that you have a thorough understanding of Microsoft Windows and network configuration. Related Documentation In addition to this guide, Kofax Document Exchange Server includes the following documentation. Except for the Help and release notes, you can select to view any of the documentation by opening guides.html on the installation media root or \Documentation\DESguides.html after installation (if you select to install Documentation). Figure 1. Guides Page Administrator s Guide The Kofax Document Exchange Server Administrator s Guide shows how to change the configuration by modifying properties files and performing other administration tasks to keep Kofax Document Exchange Server working properly. If you select to install Documentation during the setup process, the guide is installed with Kofax Document Exchange in the \Documentation folder. Multifunction Peripheral (MFP) Administrator Guides These guides show how to make Kofax Document Exchange Server features available on MFP front panels. The MFP administrator guides are in the setup\guides folder on the Kofax Document Exchange Server installation media. If you select to install Documentation during the setup process, they are installed with the software in the \Documentation\Guides folder. Destination Configuration Guides These guides show how to enable Kofax Document Exchange Server to send documents to destinations, such as content management and systems. The destination configuration guides are in the \setup\guides folder on the Kofax Document Exchange Server installation Kofax, Inc. 1

8 media. If you choose to install documentation, they are installed with the software in the Documentation\Guides folder. Kofax Document Exchange Server Installation Guide These guides show how to install Kofax Document Exchange Server as a standalone or as a cluster. Kofax Fax Connector Installation Guide The Kofax Fax Connector Installation Guide provides installation and configuration instructions for the Kofax Fax Connector. If you select to install Documentation during the setup process, the guide is installed with Kofax Document Exchange in the \OtherResources\FaxConnector folder. Help for Kofax Document Exchange Server Applications Kofax Document Exchange and Kofax Administration Console have Help that describes how to use the application. Each Help system has a table of contents, index, and full-text search to assist you in finding information. To view the Help from the application, click the Help button. The Help appears in a separate browser window. You can also view the Help when you are at the server by selecting Start Programs Kofax Documentation and then the Help system. Release Notes Late-breaking product information is available from the release notes. Read the release notes carefully, because they contain information that may not be included in other Kofax Document Exchange Server documentation. The release notes are available for viewing or downloading from the Kofax Web site. Software Installed with Kofax Document Exchange Server The following software is installed with Kofax Document Exchange Server: To ensure the installation ant scripts can run as documented, a version of Ant is installed and added to the System path. Java Runtime Environment (JRE): A version of the JRE is installed in the Kofax Document Exchange Server folders. This JRE is used by Kofax Document Exchange Server and does not replace any versions of the JRE installed on your system. Bonjour: Software that discovers devices on a network. VirtualReScan (VRS): Kofax product for improving image quality. Supported System Configurations The following system configurations are supported. WebLogic 9.2 MP3 administration server and managed server installed on one machine Oracle 10g Release 2 database or Oracle RAC Shared network storage or Microsoft Cluster Server shared storage WebLogic 9.2 MP3 administration server and proxy server on one or two machines and one or more managed servers on separate machines. All machines must be in the same domain. Oracle 10g Release 2 database or Oracle RAC 2 Kofax, Inc.

9 Shared network storage or Microsoft Cluster Server shared storage Important There can be no spaces in the JRockit installation path (see Setting Environment Variables on page 7 for more information). Also, if you will be using a proxy server, the System path environment variable cannot contain any quotation marks. System Requirements The administration, proxy, and managed servers used for Kofax Document Exchange Server must meet the system requirements described in this section. These requirements will be updated as new configurations are supported. Refer to the Kofax Web site for the latest information. Managed Server Requirements This section contains requirements for each managed server in the cluster, as well as the administration and proxy server machines. Important The Kofax Document Exchange Server installation for WebLogic does not support computer names with the underscore _ character in the name. Use only computer names that have letters, numbers, dashes, or periods. Or, if your computer name has underscores but can have a fixed IP address, you can use the IP address. Operating System Kofax Document Exchange Server requires either of the following versions of Microsoft Windows Server for production use: Windows Server 2003 Enterprise x64 Edition with Service Pack 2 Windows Server 2003 Enterprise x86 Edition with Service Pack 2 Windows Server 2003 Standard x64 Edition with Service Pack 2 Windows Server 2003 Standard x86 Edition with Service Pack 2 Minimum Hardware Requirements The cluster machines must meet the following minimum hardware requirements. 2 GHz Pentium 4 or compatible microprocessor 4 GB RAM 100/1000 Mbps network card (10 Mbps not supported) Certified VMWare Configurations Kofax Document Exchange Server supports the following host operating systems. For a list of the supported hardware for running VMWare, please refer to the VMWare installation guide available from the manufacturer's website. Kofax, Inc. 3

10 ESX Server version 3.5 Windows Server 2003 Enterprise x64 Edition with Service Pack 2 Windows Server 2003 Enterprise x86 Edition with Service Pack 2 Windows Server 2003 Standard x64 Edition with Service Pack 2 Windows Server 2003 Standard x86 Edition with Service Pack 2 VMWare Server and 2.0 Windows Server 2003 Enterprise x86 Edition with Service Pack 2 Windows Server 2003 Standard x86 Edition with Service Pack 2 Certified VMWare Configurations The following VMWare configurations have been certified for Kofax Document Exchange Server. ESX Server version 3.5 Host Hardware: HP ProLiant DL360 G4 Dual Intel Xeon CPU 3.0 GHz with HT 6 GB RAM Internal Hard drives 100 MB NIC Operating System: Windows 2003 Server, Standard SP2 VMWare Server and 2.0 Windows 2003 Server, Enterprise SP2 32 bit Open Ports Ports 80 and 8080 must be available for use by Kofax Document Exchange Server. If Internet Information Services (IIS), a Web server, or another application uses these ports, reconfigure it to use different ports. If IIS, a Web server, or an application cannot be reconfigured, disable or uninstall it or install Kofax Document Exchange Server on another computer. Port 7001 must be available during the installation, but can be released after installation is complete. If you have an application that uses that port and the application can be temporarily configured to use another port, follow the instructions in What if Port 7001 is in Use: Changing the Admnistration Server Port on page 45. Some MFPs also need port 8888 open in the network connection between Kofax Document Exchange Server and the device. Refer to the MFP administrator guide for information. Client Requirements This version of Kofax Document Exchange Server provides browser-based applications, Kofax Document Exchange and Kofax Administration Console, which require the following: 4 Kofax, Inc.

11 Certified Web Browsers Kofax Document Exchange Server requires a Web browser to run thin clients and view the Help. The following browsers have been tested with Kofax Document Exchange Server: Microsoft Internet Explorer 6.0 and 7.0 Mozilla Firefox 1.5 and 2.0 Adobe Reader Requirement To view PDF files on Kofax Document Exchange Server client workstations, you need the current version of Adobe Reader. Note For information on additional requirements if you want to scan directly from the Kofax Document Exchange (using the feature called WebScan), see the Kofax Document Exchange Server Administrator s Guide. Monitor Display Resolution To view client software correctly in a browser, the monitor display resolution must be at least 1024 x 768 with 16-bit color and Normal fonts. Pre-Installation Planning This section contains information and options you should read, understand, and verify before starting the installation. Network Configuration Requirements Destination types and Kofax Document Scan Server devices need to be on the same network as Kofax Document Exchange Server with routable addresses from the server. Kofax Document Exchange Server uses the IP address of the first network connection listed in the connection order. If there are multiple network cards in the server, you may need to change the order of network connections so that the connection used by MFPs and destination types is first. Refer to the Microsoft Windows Server 2003 documentation for instructions on changing the connection order. Cluster Planning The WebLogic cluster must have a unique IP address and listen port combination for each of its managed servers. Installing on a Local Drive The Kofax Document Exchange Server must be installed on a local drive, which can be any drive letter. Do not install the Kofax Document Exchange Server on a network drive, including a mapped drive. Requirement for Free Hard Drive Space Make sure that there is sufficient space on the hard drive for the database. A minimum of 25 GB is recommended as an initial amount of free hard drive space for the database. Additional space will Kofax, Inc. 5

12 be needed as the database grows. You can manage the database size by periodically purging old records. Kofax Documentation Exchange Server can also block database requests if the free drive space reaches a specified threshold. For information about freeing hard drive space, refer to the Kofax Document Exchange Server Administrator s Guide. Dedicated Server Requirement Kofax Document Exchange Server should not be installed on a domain controller or a system with Active Directory. Registry Access Kofax Document Exchange Server needs to modify the Registry during installation. If you are using software that restricts changes to the Registry, turn it off while installing Kofax Document Exchange Server. Restarting the Server Do not restart a machine manually while the installation program is running. Restarting the server will cause the installation to fail. Invalid Drive Path If you change the default path during installation, you must select an install path that includes a valid local drive letter. The following error appears if you select a drive letter that does not exist. You do not have write permissions to the chosen installation destination. Using Kofax Document Exchange Server on a Virtual Machine (VM) Kofax Document Exchange Server may not run properly on a VMware Virtual Machine when the host computer has multiple processors, multiple cores, or hyper threading enabled. The following problems may occur: When users attempt to download a PDF file, the following error appears. The text in italics varies depending on your system and the files affected. KDE Cannot download the document. Verify that document is not locked by another process. If the document cannot be downloaded, have the system administrator verify that the VRS component has been installed with the Kofax Document Exchange Server. If PDF is selected as the format for a destination file, scanned documents will not be sent to that destination. This setting also affects documents scanned from Kofax Document Scan Server. These documents may appear in Kofax Document Exchange without pages and preview images. Workaround: Configure the VM as a dual virtual processor system. If the problem continues, set the BIOS of the host computer to turn off hyper threading. Security Settings for Browsers If a browser is set to the highest security setting, Kofax Administration Console and Kofax Document Exchange may not work correctly. These applications depend on JavaScript, and they must be able to communicate with the server. Therefore, make Kofax Administration Console, Kofax Document Exchange, and their Help systems trusted sites and enable JavaScript and cookies. 6 Kofax, Inc.

13 Text Resizing in Browsers Panels and scroll bars are not resized automatically when the text size changes. This can cause enlarged text to appear outside the borders of a panel. It can affect automatic scrolling, such as when you drag a document to the bottom of a Destination panel to scroll down the list of destinations. To cause resizing, use the browser s Refresh command so the panels and scroll bars are resized to fit the text. Migrating from a Previous Version of Kofax Document Exchange Server on WebLogic If you are using a previous version of Kofax Document Exchange Server, you must uninstall it before installing this version of Kofax Document Exchange Server. Tell users to release all of their documents in their Kofax Document Exchange Inbox before you migrate to the Kofax Document Exchange Server. There is no way to migrate Inbox documents after you have uninstalled the old version. If you use a directory service, this version of Kofax Document Exchange Server uses the samaccount name for authentication. The common name is no longer used, and there is no way to configure authentication using common name. Refer to the Kofax Document Exchange Server Administrator s Guide for information about connecting to directory services. Installation Notes for 64-Bit Computers If you are installing Kofax Document Exchange Server on a 64-bit computer, note the following additional requirements. Kofax Document Exchange Server supports the AMD64 instruction set and architecture on the Windows operating system. Intel Itanium processors are not supported. The C:\Program Files (x86) folder is still required for some components of Kofax Document Exchange Server. To support these components, the Installer does the following: Bonjour is installed in both C:\Program Files and C:\Program Files (x86). A Bonjour subfolder is created in each folder. VRS is installed in C:\Program Files (x86). All other files are installed in the installation path you specified. Installing Kofax Document Exchange Server This section provides the steps to install Document Exchange Server in a WebLogic cluster using an Oracle database or an Oracle RAC. You will create an administration server, an optional proxy server, and one or more managed servers. Follow the instructions in the exact order they are presented. You must log on to each machine as a user with Administrator rights to install Kofax Document Exchange Server Setting Environment Variables WebLogic 9.2 MP3 and JRockit should be installed on the administration server and all machines that will be in the cluster. You must manually set the correct System path environment variables on each machine in the cluster, including the administration and proxy servers, because the variables are not set automatically during the installation procedure. Kofax, Inc. 7

14 Important For 64-bit WebLogic installations, install JRockit first and to a path that does not have spaces, such as C:\bea. Kofax Document Exchange Server installation does not support spaces in the installation path, so the default WebLogic installation path of C:\Program Files cannot be used. On each machine, set the JAVA_HOME System path environment variable to the JRockit path: For 32-bit WebLogic systems, the default is C:\bea\jrockit_150_12 For 64-bit WebLogic systems, <installfolder>\jrockit-r jdk1.5.0_14 (note that if you have two JRockit folders, the variable is to the jdk not the jre). Then, add %JAVA_HOME%\bin to the System path environment variable. Getting Oracle Connection Information An Oracle 10g database or Oracle Real Application Cluster (RAC) is required. You can leverage Oracle RAC to improve both the scalability and availability of Kofax Document Exchange Server. Warning There is a known issue that the JMS server will require a restart if the database is shut down for a significant amount of time. For a single Oracle database, this might be approximately 2 minutes. With Oracle RAC, the problem is less severe because WebLogic will issue a connection retry in 15 seconds (the WebLogic default is 1 second, but Kofax Document Exchange Server installation configures this to 15 seconds), but the problem may still occur. Tip Oracle database and RAC configuration and tuning is critical for achieving optimal performance. We recommend you take advantage of the many diagnostic and tuning tools and resources that are available. Create an Oracle user account that will own the Kofax Document Exchange Server information. The user must also have privileges to create objects in the schema, as well as a quota on a default tablespace. You will provide this username and password later in the install.properties file. You will also provide the host name of the database server, the Oracle SID, and the Oracle port. Creating Shared Folders You need to create shared file storage locations for scanjobs and inbox content. The shared storage must be accessible to all the other machines in the cluster. There is no particular naming convention you must follow, as you will supply the UNC paths when you configure the install.properties file in a later step. In addition, the account that will be used to run the cluster must have read/write access to the shared storage locations. Note If you have clustered storage in a highly available environment, you can use Microsoft Cluster Server to create file shares accessible through a UNC path and then specify that path in the install.properties file. Sharing the Configuration Files There are many configuration files that are installed to the \conf folder in the root of the WebLogic domain. The Kofax Document Exchange Server Administrator s Guide has instructions on 8 Kofax, Inc.

15 how to use these files to customize your implementation. In a clustered environment, all managed servers in the cluster should use the same configuration settings. The recommended way to accomplish this is to maintain each managed server s local \conf folder and manage the files either manually or by using a centralized management tool. Another alternative is to create a network share, place the configuration files in that share, and specify the share location in a property in the install.properties file. When you create the share, the final location in the path must be a folder named \conf. Then, modify the avalin.domain.conf.path property in the install.properties file with a value of the full UNC path to the share, or UNC path to clustered shared storage location. After installation, if you need to change the location of the shared domain configuration folder, you can create the new share ending with \conf, copy the configuration files to the new location, and then edit the WeblogicDomainConf property in the \conf\des.properties file. Once the cluster is restarted, the new share will be used. Important If you use this method to share the configuration files and the network share fails, all of the servers in the cluster will be affected. Installing the Kofax Document Exchange Server Components This section provides instructions for installing Kofax Document Exchange Server, related components, and installation scripts. You will be running an installation program from the installation media. Follow the instructions that apply to your planned implementation: If you will be installing the administration server and a managed server on the same machine, see Installing on One Machine. If your administration server and managed servers are on separate machines, see Installing on Separate Machines (one or more managed servers on the same domain as the administration and proxy server) Installing on One Machine 1 Insert the Kofax Document Exchange Server installation media into your drive. 2 Browse to the \setup folder, and run setupweblogic.exe. 3 Review the Kofax Document Exchange Server license agreement and select I accept the terms of the License Agreement to continue with the installation. Click Next to continue. 4 You will be prompted to select features to install. Select all features (however, selecting to install Documentation is optional) and click Next to continue. Figure 2. Custom Installation Set: All Features Selected Kofax, Inc. 9

16 5 Type the user name and password for the initial Kofax Document Exchange Server administrator. Use this user account to log on to Kofax Administration Console for the first time. The user name and password must meet the following rules: User names must be unique on the server. User names are case-insensitive, cannot include spaces, and the following characters are not permitted: ~ # % * \ ; / : &?. ', " ` $ < + > Passwords are case-sensitive and can include spaces, but not at the beginning or end. There can be no repeating spaces. The password for the initial administrator cannot include the following characters that are prohibited by the database: & $ < ' > \ * / " You can create additional administrators by assigning the Administrator role to other users in Kofax Administration Console. Click Next to continue. 6 Accept the default installation path, or choose another location. Click Next to continue. 7 Review the installation parameters and click Install to begin the installation. Note If you are installing on 64-bit OS, the installation of Bonjour is not a silent installation: you will be prompted to complete the Bonjour installation screens. Installing on Separate Machines (one or more managed servers on the same domain as the administration and proxy server) On the machine that will host the administration server Note If you will not have the administration server and proxy server on this same machine, you must repeat these installation steps on the proxy server machine. 1 Insert the Kofax Document Exchange Server installation media into your drive. 2 Browse to the \setup folder, and run setupweblogic.exe. The Introduction screen appears (Figure 3). Click Next. Figure 3. Kofax Document Exchange Server Installer Introduction Screen 10 Kofax, Inc.

17 3 On the License Agreement screen, review the license agreement and select I accept the terms of the License Agreement. Click Next to continue. 4 On the Choose Features screen, select all features except DES Prerequisites (however, selecting to install Documentation is optional) and click Next to continue. Tip The DES Prerequisites installation would install VRS, Bonjour, and other software that is not needed on the administration server. Figure 4. Custom Installation Set: DES Prerequisites Unselected 5 On the Initial Administrator screen, type the user name and password for the initial Kofax Document Exchange Server administrator. Use this user account to log on to Kofax Administration Console for the first time. The user name and password must meet the following rules: User names must be unique on the server. User names are case-insensitive, cannot include spaces, and the following characters are not permitted: ~ # % * \ ; / : &?. ', " ` $ < + > Passwords are case-sensitive and can include spaces, but not at the beginning or end. There can be no repeating spaces. The password for the initial administrator cannot include the following characters that are prohibited by the database: & $ < ' > \ * / " You can create additional administrators by assigning the Administrator role to other users in Kofax Administration Console. Click Next to continue. 6 On the Choose Installation folder screen, accept the default installation path, or choose another location. Click Next to continue. 7 On the Pre-Installation Summary screen, review the installation parameters and click Install to begin the installation. Important Do not close the Installer window until the installation is complete. Interrupting the installation can leave the system in an unrecoverable state. 8 A screen indicates when the installation is done. Click Done to close the Installer. 9 Continue to the next step: installing the managed servers. Important You must perform the following installation steps on every managed server in the cluster. On each machine that will host a managed server 1 Insert the Kofax Document Exchange Server installation media into your drive. Browse to the \setup folder, and run setupweblogic.exe. Kofax, Inc. 11

18 2 On the License Agreement screen, review the Kofax Document Exchange Server license agreement and select I accept the terms of the License Agreement. Click Next to continue. 3 On the Choose Features screen, select all features except Administration Server Prerequisites (however, selecting to install Documentation is optional) and click Next to continue. Figure 5. Custom Installation Set: Administration Server Prerequisites Unselected 4 On the Choose Installation Location screen, accept the default installation path, or choose another location. Click Next to continue. 5 On the Pre-Installation Summary screen, review the installation parameters and click Install to begin the installation. Note the following while the Installer is running: Do not close the Installer window until the installation is complete. Interrupting the installation can leave the system in an unrecoverable state. If you are installing on the 64-bit version of Windows, the installation of Bonjour is not a silent installation. You will be prompted to complete the Bonjour installation screens. 6 A screen indicates when the installation is done. Click Done to close the Installer. 7 Repeat the installation on any additional managed servers. Preparing an Oracle Database Before configuring install.properties, the database administrator must run SQL scripts to create Kofax Document Exchange Server users in the Oracle database. Have the database administrator perform the procedure in this section. When the database administrator is finished, obtain the credential for the new user schema to use in configuring the install.properties file. To prepare an Oracle database 1 On the administration server, browse to the folder \AppServer\install\SQLScripts\oracle where Kofax Document Exchange Server was installed. 2 Edit the weblogic_oracle_jdbc.sql and drop_weblogic_oracle_jdbc.sql files according to the instructions in the files. Save and close the files. 3 Create an Oracle user that Kofax Document Exchange Server will use to access the database. 4 Run the scripts in the user schema you created in the following order: a create_oracle.sql b create_doctracking_oracle.sql c create_documents_oracle.sql 12 Kofax, Inc.

19 d e f weblogic_oracle_jdbc.sql create_des_users_oracle.sql create_des_oracle.sql Recovering from a SQL Failure To recover from SQL failure, the database administrator runs the drop scripts in the following order: 1 drop_weblogic_oracle_jdbc.sql 2 drop_documents_oracle.sql 3 drop_doctracking_oracle.sql 4 drop_oracle.sql The database administrator may reduce the new user privileges after running the scripts. Configuring the install.properties File You must modify some properties in the file install.properties before creating the Kofax Document Exchange Server WebLogic Server domain. Tip There are many properties in the file that do not need to be changed if your installation of WebLogic is in the default location, and you want to accept the default domain installation name, location, and other values. To see what lines you might need to modify, you can examine an example install.properties file in install.properties: An Example on page 30. On a managed server (it does not matter which one), browse to the folder \AppServer\install where Kofax Document Exchange Server was installed, and edit install.properties as directed in the following instructions. After you have finished editing the install.properties file, copy it to the same location (\AppServer\install) on every machine in the cluster, overwriting the existing file. Important In all Document Exchange Server configuration and properties files, file paths should always use forward-slashes. There are two areas in this section where the properties in this file are described: Mandatory Settings You must set these for a successful installation. Note that not all of the properties in a set are listed in this section, as some default values (such as the WebLogic installation path) are already included to make configuration easier. Java configuration Scanjob share location Inbox share location Initial admin user to deploy DES license and workflows WebLogic information home admin user name admin password Domain configuration administration server host name Kofax, Inc. 13

20 shared configuration path nodemanager user name nodemanager password Cluster information number of physical machines in the cluster (less admin or proxy) number of managed servers in the cluster Managed server configuration host names of each managed server Cluster configuration list of all managed servers in the cluster Proxy server configuration proxy server host name list of managed servers Java startup options use defaults for 32-bit: modify for 64-bit Oracle DB configuration host name user name password Optional Custom Settings Specific settings you can use to customize your domain, or if Weblogic is not installed on the default location. There are some properties in the file that are used for internal purposes only and should not be altered. These include some properties with values and also some that should be left blank. Do not alter any property unless directed to do so in the Mandatory or Optional Custom Settings sections. Important Passwords are encrypted in install.properties when you run the installation script or use the script to start or stop the cluster. If you need to change a password, type the new password in place of the encrypted one. The new password is encrypted the next time the cluster is started. After the new password has been encrypted in install.properties, copy the file to each of your managed servers. This ensures that all servers have the same install.properties file that contains the encrypted new password. Mandatory Settings This section explains the properties you must set for a successful implementation. Properties are listed under their commented grouping title in the file. Java configuration avalin.java.home Set this property to the location of your JRockit Java Virtual Machine. Remember to use forward slashes when entering file paths. OS Configuration des.scanjobsdir Set this property to the full UNC path of an available folder for use by Kofax Document Exchange Server to store temporary files. It is recommended that this be a network shared folder, as this folder must be accessible to all machines that will host servers that are part of 14 Kofax, Inc.

21 the Kofax Document Exchange Server WebLogic Server cluster. This folder must grant read/ write access to the account that will be used to run the cluster. If you are using a clustered storage in a highly available environment, you can use Microsoft Cluster Server to create the file shares and specify the UNC to the clustered storage. des.inboxdir Set this property to the full UNC path of an available folder for use by Kofax Document Exchange Server to store files for each user s inbox. It is recommended that this be a network shared folder as this folder must be accessible to all machines that will host servers that are part of the Kofax Document Exchange Server WebLogic Server cluster. This folder must grant read/write access to the account that will be used to run the cluster. If you are using a clustered storage in a highly available environment, you can use Microsoft Cluster Server to create the file shares and specify the UNC to the clustered storage. Initial admin user to deploy license and workflow startup.deployer.username Set this property to the user name previously provided to the Installer as the initial Kofax Document Exchange Server administrator. startup.deployer.password Set this property to the password previously provided to the Installer for the initial Kofax Document Exchange Server administrator. Information about the WebLogic installation bea.home Set this property to the location of your WebLogic installation folder. avalin.weblogic.admin.name Used to set the WebLogic administrator account name: this is the user name you will use to log on to the WebLogic Administration Console. The default value is weblogic. Note that the WebLogic administration name and password must be at least eight characters. avalin.weblogic.admin.password Used to set the WebLogic administrator account password. This is the password you will use to log on to the WebLogic Administration Console. The default value is weblogic. Domain configuration avalin.domain.host Set this property to the name of the machine that will run the administration server. If the computer name is bound to more than one IP Address, set this to the appropriate fixed IP Address instead of the computer name. Important The installation for WebLogic does not support computer names with the underscore _ character in the name. Use only computer names that have letters, numbers, dashes, or periods. Or, if your computer name has underscores but can have a fixed IP address, you can use the IP address. avalin.domain.conf.path Kofax, Inc. 15

22 Set this property to the location of the WebLogic domain \conf folder that contains the configuration files. By default, the value is the \conf folder in the des domain on each managed server. You can have all the managed servers in the cluster share a single configuration folder by creating a network or cluster share ending with a \conf folder and using the UNC path as the value for this property. See Sharing the Configuration Files for more information. avalin.nodemgr.logon.user Set this property to the user name of the Windows account to use to start the servers in the Kofax Document Exchange Server WebLogic Server cluster. The avalin.nodemgr.logon.user account must have all of the following: Be an account with Administrator rights on each machine in the cluster. A domain account is preferred. Important You cannot enter a domain account in the install.properties file (slashes are not supported). To use a domain account for the NodeManager service, follow the steps below. Log on as service rights on each machine in the cluster. To provide service rights, go to the Control Panel Administrative Tools Local Security Policy. Expand Local Policies, select User Rights Assignment, and then in the right panel select Log on as a service and add the user to the list. Read/write access to the WebLogic Document Exchange Server domain folder. Read/write access to the des.scanjobsdir and des.inboxdir folders specified in the OS Configuration section. If a shared configuration folder is used, read/write access to the \conf folder wherever it is located. To set a domain user account for NodeManager service 1 Set this property to a local user account that has the rights in the list above. Each machine in the cluster must have the same local account. 2 On the administration server after running the ant script install-admin-server, and on each managed server after running the ant script install-managed-server, do the following: a Go to the Services panel and manually change the login account for the des NodeManager service to a domain account that meets the criteria listed in the bullet list above. b Restart the service and resume the next step in the installation instructions. avalin.nodemgr.logon.password Set this property to the password of the user account specified in avalin.nodemgr.logon.user. Cluster configuration The following two properties are both required, and should have identical values. avalin.machines and avalin.managed.servers Set these properties to the number of managed servers in the Kofax Document Exchange Server WebLogic Server cluster. For each of the managed servers, there needs to be a set of properties in the next section Managed servers configuration. 16 Kofax, Inc.

23 Managed servers configuration avalin.managed.server.1 Set this property to the computer name of a machine that will be a managed server. Important If a computer name is bound to more than one IP Address, set avalin.managed.server.<number> to the IP Address that is accessed first by network services instead of the computer name. By default, this section of the install.properties file is set up to use three managed servers, so there is one set of properties for each server. Each set of properties begins with the line avalin.managed.server.n=myservern and ends with avalin.managed.server.1.channel1.client.certificate.enforced=false as shown here: avalin.managed.server.1=myserver1 avalin.machine.1.addresses=${avalin.managed.server.1} avalin.machine.1.nodemgr.host=${avalin.managed.server.1} avalin.machine.1.nodemgr.port=5556 avalin.managed.server.1.host= avalin.managed.server.1.port=8080 avalin.managed.server.1.ssl.port=8443 avalin.managed.server.1.cluster=1 avalin.managed.server.1.machine=1 avalin.managed.server.1.replicationgroup=group1 avalin.managed.server.1.domain.home=${avalin.domain.dir} avalin.managed.server.1.java.home=${avalin.java.home} avalin.managed.server.1.bea.home=${bea.home} avalin.managed.server.1.channel1.name=channel-http-80 avalin.managed.server.1.channel1.protocol=http avalin.managed.server.1.channel1.listen.port=80 avalin.managed.server.1.channel1.external.listen.port=80 avalin.managed.server.1.channel1.enabled=true avalin.managed.server.1.channel1.client.certificate.enforced=false avalin.managed.server.n.< lines two through the end of a set> Set the number values n in all the lines in a set to the same number, which must be unique to the managed server. For example, you could set the first managed server s number values to 1, the second managed server number values to 2, etc. as in the following examples. avalin.managed.server.1.cluster=1 Do not change this value: you will be installing only one cluster, so this value needs to be 1. avalin.managed.server.1.channel1.protocol=http Do not change any of the six channel values in each section: this value needs to be 1 for all managed servers in the cluster. Examples One managed server: avalin.managed.server.1=myserver1 avalin.machine.1.addresses=${avalin.managed.server.1} avalin.machine.1.nodemgr.host=${avalin.managed.server.1} avalin.machine.1.nodemgr.port=5556 avalin.managed.server.1.host= Kofax, Inc. 17

24 avalin.managed.server.1.port=8080 avalin.managed.server.1.ssl.port=8443 avalin.managed.server.1.cluster=1 avalin.managed.server.1.machine=1 avalin.managed.server.1.replicationgroup=group1 avalin.managed.server.1.multicastinterfaceaddress= avalin.managed.server.1.domain.home=${avalin.domain.dir} avalin.managed.server.1.java.home=${avalin.java.home} avalin.managed.server.1.bea.home=${bea.home} avalin.managed.server.1.channel1.name=channel-http-80 avalin.managed.server.1.channel1.protocol=http avalin.managed.server.1.channel1.listen.port=80 avalin.managed.server.1.channel1.external.listen.port=80 avalin.managed.server.1.channel1.enabled=true avalin.managed.server.1.channel1.client.certificate.enforced=false Two managed servers: avalin.managed.server.1=myserver1 avalin.machine.1.addresses=${avalin.managed.server.1} avalin.machine.1.nodemgr.host=${avalin.managed.server.1} avalin.machine.1.nodemgr.port=5556 avalin.managed.server.1.host= avalin.managed.server.1.port=8080 avalin.managed.server.1.ssl.port=8443 avalin.managed.server.1.cluster=1 avalin.managed.server.1.machine=1 avalin.managed.server.1.replicationgroup=group1 avalin.managed.server.1.multicastinterfaceaddress= avalin.managed.server.1.domain.home=${avalin.domain.dir} avalin.managed.server.1.java.home=${avalin.java.home} avalin.managed.server.1.bea.home=${bea.home} avalin.managed.server.1.channel1.name=channel-http-80 avalin.managed.server.1.channel1.protocol=http avalin.managed.server.1.channel1.listen.port=80 avalin.managed.server.1.channel1.external.listen.port=80 avalin.managed.server.1.channel1.enabled=true avalin.managed.server.1.channel1.client.certificate.enforced=false avalin.managed.server.2=myserver2 avalin.machine.2.addresses=${avalin.managed.server.2} avalin.machine.2.nodemgr.host=${avalin.managed.server.2} avalin.machine.2.nodemgr.port=5556 avalin.managed.server.2.host= avalin.managed.server.2.port=8080 avalin.managed.server.2.ssl.port=8443 avalin.managed.server.2.cluster=1 avalin.managed.server.2.machine=2 avalin.managed.server.2.replicationgroup=group1 avalin.managed.server.2.multicastinterfaceaddress= avalin.managed.server.2.domain.home=${avalin.domain.dir} avalin.managed.server.2.java.home=${avalin.java.home} avalin.managed.server.2.bea.home=${bea.home} avalin.managed.server.2.channel1.name=channel-http-80 avalin.managed.server.2.channel1.protocol=http 18 Kofax, Inc.

25 avalin.managed.server.2.channel1.listen.port=80 avalin.managed.server.2.channel1.external.listen.port=80 avalin.managed.server.2.channel1.enabled=true avalin.managed.server.2.channel1.client.certificate.enforced=false Three managed servers: avalin.managed.server.1=myserver1 avalin.machine.1.addresses=${avalin.managed.server.1} avalin.machine.1.nodemgr.host=${avalin.managed.server.1} avalin.machine.1.nodemgr.port=5556 avalin.managed.server.1.host= avalin.managed.server.1.port=8080 avalin.managed.server.1.ssl.port=8443 avalin.managed.server.1.cluster=1 avalin.managed.server.1.machine=1 avalin.managed.server.1.replicationgroup=group1 avalin.managed.server.1.multicastinterfaceaddress= avalin.managed.server.1.domain.home=${avalin.domain.dir} avalin.managed.server.1.java.home=${avalin.java.home} avalin.managed.server.1.bea.home=${bea.home} avalin.managed.server.1.channel1.name=channel-http-80 avalin.managed.server.1.channel1.protocol=http avalin.managed.server.1.channel1.listen.port=80 avalin.managed.server.1.channel1.external.listen.port=80 avalin.managed.server.1.channel1.enabled=true avalin.managed.server.1.channel1.client.certificate.enforced=false avalin.managed.server.2=myserver2 avalin.machine.2.addresses=${avalin.managed.server.2} avalin.machine.2.nodemgr.host=${avalin.managed.server.2} avalin.machine.2.nodemgr.port=5556 avalin.managed.server.2.host= avalin.managed.server.2.port=8080 avalin.managed.server.2.ssl.port=8443 avalin.managed.server.2.cluster=1 avalin.managed.server.2.machine=2 avalin.managed.server.2.replicationgroup=group1 avalin.managed.server.2.multicastinterfaceaddress= avalin.managed.server.2.domain.home=${avalin.domain.dir} avalin.managed.server.2.java.home=${avalin.java.home} avalin.managed.server.2.bea.home=${bea.home} avalin.managed.server.2.channel1.name=channel-http-80 avalin.managed.server.2.channel1.protocol=http avalin.managed.server.2.channel1.listen.port=80 avalin.managed.server.2.channel1.external.listen.port=80 avalin.managed.server.2.channel1.enabled=true avalin.managed.server.2.channel1.client.certificate.enforced=false avalin.managed.server.3=myserver3 avalin.machine.3.addresses=${avalin.managed.server.3} avalin.machine.3.nodemgr.host=${avalin.managed.server.3} avalin.machine.3.nodemgr.port=5556 avalin.managed.server.3.host= avalin.managed.server.3.port=8080 Kofax, Inc. 19

26 avalin.managed.server.3.ssl.port=8443 avalin.managed.server.3.cluster=1 avalin.managed.server.3.machine=3 avalin.managed.server.3.replicationgroup=group1 avalin.managed.server.3.multicastinterfaceaddress= avalin.managed.server.3.domain.home=${avalin.domain.dir} avalin.managed.server.3.java.home=${avalin.java.home} avalin.managed.server.3.bea.home=${bea.home} avalin.managed.server.3.channel1.name=channel-http-80 avalin.managed.server.3.channel1.protocol=http avalin.managed.server.3.channel1.listen.port=80 avalin.managed.server.3.channel1.external.listen.port=80 avalin.managed.server.3.channel1.enabled=true avalin.managed.server.3.channel1.client.certificate.enforced=false If you have fewer than three managed servers, delete extra sets accordingly. If you have more than three managed servers, copy a set, paste below the last existing set, and change the values. Cluster URL configuration wls.cluster.url Set this property as a comma-delimited list of all the managed servers in the cluster. The list will have one entry ${avalin.managed.server.1}:${avalin.managed.server.1.port} for each managed server, as shown in the following examples. Example One managed server: ${avalin.managed.server.1}:${avalin.managed.server.1.port} Two managed servers: ${avalin.managed.server.1}:${avalin.managed.server.1.port},${avalin.manag ed.server.2}:${avalin.managed.server.2.port} Three managed servers: ${avalin.managed.server.1}:${avalin.managed.server.1.port},${avalin.manag ed.server.2}:${avalin.managed.server.2.port},${avalin.managed.server.3}:$ {avalin.managed.server.3.port} Proxy server configuration avalin.machine.proxyserver.addresses Set this property to the name of the machine that will run the WebLogic Server cluster proxy server. If the computer name is bound to more than one IP address, set this to the appropriate IP address instead of the computer name. avalin.machine.proxyserver.ip If you are using a proxy server, set this property to the IP address of the proxy server. If you are not using a proxy server, you must leave this property blank. avalin.machine.proxyserver.nodemgr.host Set this property to the same value as avalin.machine.proxyserver.addresses. avalin.managed.servers.list 20 Kofax, Inc.

27 Set this property as a pipe (the keyboard character)-delimited list of the avalin.managed.server.n: avalin.machine.n.nodemgr.port properties of each of the managed servers configured above. Examples One managed server: ${avalin.managed.server.1}:${avalin.managed.server.1.port} Two managed servers: ${avalin.managed.server.1}:${avalin.managed.server.1.port} ${avalin.managed. server.2}:${avalin.managed.server.2.port} Three managed servers: ${avalin.managed.server.1}:${avalin.managed.server.1.port} ${avalin.managed. server.2}:${avalin.managed.server.2.port} ${avalin.managed.server.3}:${avali n.managed.server.3.port} Server Java VM startup options This group contains an active section ready to use for a 32-bit WebLogic installation, and also a commented out section for 64-bit WebLogic. Before using for a 64-bit WebLogic installation, uncomment the four lines from the 64-bit section and either comment out or delete the 32-bit section. ###### Server Java VM startup options 32-bit Weblogic avalin.java.options=- Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl - Djava.security.auth.login.config=${avalin.domain.security.login.config} - Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFac toryimpl avalin.managed.servers.vmargs=-dweblogic.store.jdbc.ioretrydelaymillis= Xnohup avalin.admin.server.vmargs= avalin.proxy.server.vmargs= ###### Server Java VM startup options 64-bit Weblogic #avalin.java.options=- Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl - Djava.security.auth.login.config=${avalin.domain.security.login.config} - Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFac toryimpl -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 #avalin.managed.servers.vmargs=- Dweblogic.store.jdbc.IORetryDelayMillis= Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xnohup #avalin.admin.server.vmargs=- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 #avalin.proxy.server.vmargs=- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 Oracle DB Configuration When the installation is finished, a JDBC data source for your Oracle database will be created. If you will be using Oracle RAC, set the values of these properties to match one of your RAC instances so that the database can be initialized. After installation, complete the steps in Configuring for Oracle RAC on page 35. Kofax, Inc. 21

28 db.avalin.ora.host Set this property to the host name of the Oracle database server hosting the Kofax Document Exchange Server Oracle database instance or Oracle RAC node. db.avalin.ora.port Set this property to the port number to use to connect to the Kofax Document Exchange Server Oracle database instance or Oracle RAC node. Note By default, Oracle may use port That port must be reserved for Kofax Document Exchange Server, so be sure to change the Oracle port to one other than db.avalin.ora.sid Set this property to the SID for the Kofax Document Exchange Server Oracle database instance or Oracle RAC node. db.avalin.ora.user Set this property to the user name used to connect to the Kofax Document Exchange Server Oracle database instance or Oracle RAC node. db.avalin.ora.password Set this property to the password used to connect to the Kofax Document Exchange Server Oracle database instance or Oracle RAC node. Optional Custom Settings The following properties may optionally be modified to customize your Kofax Document Exchange Server WebLogic Server cluster. You would change some of these settings, for example, if you had changed the WebLogic administrator account or if you want to use a name other than des for your domain. avalin.weblogic.admin.name Used to set the WebLogic administrator account name. The default value is weblogic. Note that the WebLogic administration name and password must be at least eight characters. avalin.weblogic.admin.password Used to set the WebLogic administrator account password. The default value is weblogic. avalin.domain.name Used to set the name of the WebLogic domain in which the Kofax Document Exchange Server WebLogic Server cluster will run. The default value is des. avalin.domain.port Used to set the listen port for the administration server. The default value is avalin.domain.sslport Used to set the SSL listen port for the administration server. The default value is avalin.nodemgr.port Used to set the port for the administration server NodeManager service. The default value is avalin.cluster.1.multicast.ip 22 Kofax, Inc.

29 Used to set the IP multicast address used by the Kofax Document Exchange Server WebLogic Cluster domain. The default value is avalin.managed.server.proxyserver.ssl.port Used to set the SSL listen port for the proxy server. The default value is avalin.managed.server.1.multicastinterfaceaddress Used to specify which IP address will be used to broadcast or listen to the cluster multicast traffic in multi-homed managed servers. For example, you may have a server that has two network cards and IP addresses to LAN1 and LAN2 separately. If each managed server has one IP address only, leave this property blank; otherwise, set the value it to the IP address that listens to the cluster multicast traffic. If not set properly, the proxy server would drop some managed servers intermittently in run time. avalin.cluster.1.multicast.port Used to set the IP multicast port used by the Kofax Document Exchange Server WebLogic Cluster domain. The default value is avalin.machine.#.nodemgr.port Used to set the port for the managed server NodeManager service. The default value is avalin.managed.server.#.port Used to set the listen port for the managed server. The default value is avalin.managed.server.#.ssl.port Used to set the SSL listen port for the managed server. The default value is avalin.managed.server.#.channel1.listen.port Used to set an additional port on which managed servers listen. The default value is 80. avalin.machine.proxyserver.nodemgr.port Used to set the port for the proxy server NodeManager service. The default value is avalin.managed.servers.vmargs Used to pass arguments to the Java Virtual Machine when starting the managed servers. avalin.admin.servers.vmargs Used to pass arguments to the Java Virtual Machine when starting the administration server. avalin.proxy.servers.vmargs Used to pass arguments to the Java Virtual Machine when starting the proxy server. About the Installation Scripts This section lists the actions performed by the various installation scripts. Instructions for running the scripts are presented in the next section, Running the Installation Scripts. install-admin-server Imports Kofax Document Exchange Server SSL certificate file into the local Java VM. Connects to Oracle, creates the database tables, and initializes data. Creates the Kofax Document Exchange Server domain directory inside of the WebLogic programs folder. Kofax, Inc. 23

30 Installs and starts the NodeManager Windows service. install-managed-server Imports Kofax Document Exchange Server SSL certificate file into the local Java VM. Creates the Kofax Document Exchange Server domain directory under the WebLogic programs folder. Connects to the running administration server and registers it with the Kofax Document Exchange Server domain. Adds the Kofax Document Exchange Server domain VRS files to the System path environment variable. Installs and starts the NodeManager Windows service. Copies configuration files to the domain \conf folder. prepare-managed-server Replaces install-managed-server for standalone (single-machine) WebLogic deployment. Not used in clusters with multiple machines. Performs basically the same steps as install-managed-server, but slightly differently because it shares a machine with the administration server. deploy-proxy Configures the local Kofax Document Exchange Server domain folder to host a proxy server. Builds the proxy Web application and installs it to the Kofax Document Exchange Server WebLogic domain. deploy-des Copies application files to the Kofax Document Exchange Server WebLogic domain. Connects the managed servers to the Oracle database. Starts the managed servers and installs the new files. Running the Installation Scripts This section provides the instructions to run the installation scripts described in the previous section About the Installation Scripts. As you follow the instructions, pay attention to which machine you are performing the steps on. Also, be sure to wait for each step to be completed (result=build Successful) before moving to the next step. Important Before starting to run the scripts, be sure that the completed install.properties file has been copied to the same location (AppServer\install) on every machine in the cluster. Also, if the avalin.nodemgr.logon.user account is not the same on all machines that will be in the cluster be sure to edit the install.properties file on each machine with the appropriate account. Install the Administration Server There may be some non-fatal error messages logged to the administration server while the scripts run. An example are some process not found errors for omninames and NativeModules. This is expected and can be ignored, as long as you get the Build Successful message at the end. 24 Kofax, Inc.

31 On the machine that will be the administration server 1 Open a Command Prompt window, browse to the folder \AppServer\install where Kofax Document Exchange Server was installed, and type: ant install-admin-server 2 As the build progresses, another Command Prompt window (running startweblogic.cmd) will open close as activity between the two windows continues. Wait for the build to complete successfully (approximately 5 minutes). You will see the original Command Prompt window and the administration server output window. Important Do not close the administration server output window or the managed servers will not be able to register. 3 Check the Services console and verify that the des NodeManager service is running. Warning If you want to use a domain account to run the NodeManager service, you must follow the instructions in avalin.nodemgr.logon.user on page 16 before proceeding. Install Managed Servers On each machine that will be a managed server 1 Open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. 2 Do one of the following: If the machine is not the same machine as the administration server, type: ant install-managed-server If the machine is the same machine as the administration server, type: ant prepare-managed-server This build should take approximately 3 minutes. The following environment variables are added automatically to the System path environment variable during the installation: C:\bea\jrockit_150_12\jre\bin c:/bea/user_projects/domains/des/bin; c:/bea/user_projects/domains/des/bin/libtiff Warning If you want to use a domain account to run the NodeManager service, you must follow the instructions in avalin.nodemgr.logon.user on page 16 before installing the next managed server, and follow them again after installation on each managed server. Install a Proxy Server Skip this step if either of the following are true and go to the next task Deploy the Proxy Server : You are not going to use a proxy server. Your administration server and single managed server are on the same machine. Kofax, Inc. 25

32 Note Do not install a proxy server on a machine that is a managed server. Important Before installing a proxy server, be sure that the des NodeManager service is running on all machines in the cluster. Also, the System path environment variable cannot contain any quotation marks. On the machine that will be the proxy server (that is not the administration server). 1 Open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. 2 Type: ant install-proxy-server As the build progresses, another Command Prompt window (running startweblogic.cmd) will open close as activity between the two windows continues. This build should take approximately 3 minutes. Deploy the Proxy Server Skip this step if you are not going to use a proxy server. On the administration server 1 Open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. 2 Type: ant deploy-proxy As the build progresses, another Command Prompt window (running startweblogic.cmd) will open close as activity between the two windows continues. Note that there will appear to be no activity towards the end of the build until the properties begin loading. This build should take approximately 5 minutes. Deploy Document Exchange Server If you are installing on a non-english operating system, see Special Instructions for Installing on Non-English Operating Systems before proceeding. On the administration server 1 Open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. 2 Type: ant deploy-des As the build progresses, another Command Prompt window (running startweblogic.cmd) will open close as activity between the two windows continues. At the end of the build, the administration server window will close when the server is shut down.this is the longest build, and may take up to 10 minutes. 26 Kofax, Inc.

33 Special Instructions for Installing on Non-English Operating Systems If you are installing on a non-english operating system, before you deploy Kofax Document Exchange Server you must verify that the java-home path in the domain s configuration is correct. You must do this on each machine in the cluster (not just the managed servers, but the administration and proxy server machines as well), following the instructions below. To verify the java-home setting 1 Using a plain text editor, open the config.xml file in the domain s \config folder. 2 Find or search for the text java-home, which will take you to the first instance of javahome in the server-start element: <server-start> <name>avalinmanaged_1</name> <java-home>c:/bea/jrockit_150_12</java-home> 3 If the <java-home> value is not correct, change it. 4 Repeat from step 2 until each instance is verified correct. The number of instances equals the number of managed servers in the cluster. 5 Save and close the file. 6 Repeat on each machine in the cluster. When done, go to the administration server and deploy Document Exchange Server. Recovering from Install Script Failure If the installation scripts fail for any reason, you will need to debug the problem and may need to restart the installation. The most common reason for failure is a misconfiguration of the install.properties file. To delete an incomplete installation, do the following: 1 Stop the cluster. From any machine in the cluster: If you are using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type: ant stop-avalin-cluster-with-proxy If you are not using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type: ant stop-avalin-cluster 2 On each machine in the cluster, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type: ant stop-nodemanager 3 Then, to delete the WebLogic nodemanager service, type: ant delete-nodemanager 4 On each machine in the cluster, manually delete the domain folder (for example: C:\bea\user_projects\domains\des). 5 Drop and recreate the database. Refer to Preparing an Oracle Database for instructions. Starting the Cluster Now you can start the cluster. Kofax, Inc. 27

34 Important Before starting the cluster, be sure that the des NodeManager service is running on all machines in the cluster. To start the cluster from the command line: If you are using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type: ant start-avalin-cluster-with-proxy If you are not using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type: ant start-avalin-cluster This build should take approximately 5 to 10 minutes, depending on the number of managed servers in the cluster. When the Build Successful message appears, you should be able to log on to Kofax Administration Console or Kofax Document Exchange. You can use the WebLogic Administration console to perform start and stop activities, or you can do so from the command line. In a Command Prompt window, go to $BEA_HOME/ user_projects/domains/<domain_name>/bin. To start or stop the administration server, type the appropriate command: startweblogic.cmd stopweblogic.cmd To start or stop a managed server, type the appropriate command: startmanagedweblogic.cmd <managed_server_name> <admin_url> stopmanagedweblogic.cmd <managed_server_name> <admin_url> Viewing the Installation Log Files If you need to resolve a problem with the installation, you can view the installation log files on each machine for detailed information in Document Exchange Server\Install Logs\ and Document Exchange Server\AppServer\install\. Important The following installation log files include passwords in plain text. After you are finished with the installation and no longer need the files, delete them or save them in a secure location. On the administration server: Document Exchange Server\Install Logs\install_debug_Kofax Document Exchange Server.log On each managed server: Document Exchange Server\Install Logs\install_debug_Kofax Document Exchange Server.log Document Exchange Server\AppServer\install\install.log Uninstalling Kofax Document Exchange Server Here are the instructions for uninstalling Kofax Document Exchange Server. Perform the steps on each managed server in the cluster, and also the administration and proxy servers. To uninstall Kofax Document Exchange Server 1 Stop the entire WebLogic cluster. 28 Kofax, Inc.

35 2 In the Services console, verify that the <domain> NodeManager service is stopped. 3 Browse to C:\bea\user_projects\domains and delete the folder of your Kofax Document Exchange Server domain. 4 Open Control Panel Add or Remove programs. Select Kofax Document Exchange Server and click Change/Remove. Select the Complete Uninstall option. 5 The installer will prompt you to restart when finished. Select to restart. Adding New Managed Servers to a Cluster You can add more managed servers to an existing cluster. This section provides instructions. To add managed servers to a cluster 1 Make sure the Kofax Document Exchange Server cluster is up and running. 2 Insert the Kofax Document Exchange Server installation media into the drive of machine that will host a new managed server. 3 Browse to the \setup folder, and run setupweblogic.exe. The Introduction screen appears. 4 Click Next. The License Agreement screen appears. 5 On the License Agreement screen, review the license agreement and select I accept the terms of the License Agreement. Click Next to continue. 6 On the Choose Features screen, select all features except Administration Server Prerequisites (however, selecting to install Documentation is optional) and click Next to continue. 7 Update the install.properties file according to the instructions in Configuring the install.properties File. Configure it as if you were installing a completely new cluster that contains the additional managed servers you want to add. For example, if your cluster currently has two managed servers and you want to add a third and a fourth, you need to edit install.properties as if you were about to install a new cluster with all four managed servers. Once you are done editing install.properties, copy it to the \AppServer\install directory of all machines in the cluster, including the ones you are adding. Tip If you begin with an install.properties file from a previous installation, be sure to double-check values for any names or passwords that might have changed, for example your WebLogic Administration Console or database administrator. 8 On each machine you are adding to the cluster, open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. Type: install-managed-server Wait for the build to be successfully completed. 9 On the administration server, open a Command Prompt window and browse to the folder \AppServer\install where Kofax Document Exchange Server was installed. Type: update-managed-servers Wait for the build to be successfully completed. Kofax, Inc. 29

36 Note There will be some non-fatal error messages logged to the administration server during the step above. This is expected and can be ignored, as long as you get the Build Successful message at the end. Then type: redeploy-proxy Wait for the build to be successfully completed. 10 If the cluster is not sharing configuration files, copy any modified configuration files (for example, destination configuration files) from the domain s \conf folder of an existing managed server to the \conf folder of each of the new managed servers. 11 To bring up the new managed servers, do one of the following: If you are only adding one new managed server, on the administration server type: start-avalin-wls-managed-server If you are adding multiple managed servers, log on to the WebLogic Administration Console and start the new managed servers. install.properties: An Example To help visualize what you might need to modify in the install.properties file, here is a sample scenario, the file modified for that scenario, and what the installation produces in the WebLogic Administration Console. Also included in the example are the additional steps that need to be done the console for the Oracle RAC. Scenario: a company already has an Oracle RAC with three nodes, and wants to install Kofax Document Exchange Server in a cluster of three managed servers. The administration server and the proxy server will be installed together on a non-managed machine. Here are the company specific values that will be modified. All other install.properties default values will be used. Scanjob share: //SDadmin1/DESshares/scanjobs Inbox share: //SDadmin1/DESshares/inbox Name of administration and proxy server machine: SDadmin1 Nodemanager logon account user: nodemanager Nodemanager logon account password: Node13! Name of managed server 1 machine: SDman1 Name of managed server 1 machine: SDman2 Name of managed server 1 machine: SDman3 Oracle RAC node host name: SDOracle Oracle RAC node user name: myoracleuser Oracle RAC node password: myoraclepassword Here is the install.properties file: the only modifications needed are indicated in bold, larger font. ########################################### # General Configuration Properties ########################################### ###### Java configuration avalin.java.home=c:/bea/jrockit_150_12 ###### OS Configuration os.version= Kofax, Inc.

37 des.scanjobsdir=//sdadmin1/desshares/scanjobs des.inboxdir=//sdadmin1/desshares/inbox ###### Initial admin user to deploy license and workflow startup.deployer.username=admin startup.deployer.password=admin ########################################### # Weblogic Configuration Properties # Modify if server.type=wls ########################################### ###### Information about the Weblogic installation bea.home=c:/bea weblogic.home=${bea.home}/weblogic92 avalin.weblogic.admin.name=weblogic avalin.weblogic.admin.password=weblogic ###### Domain configuration avalin.domain.name=des avalin.domain.host=sdadmin1 avalin.domain.port=7001 avalin.domain.sslport=8444 avalin.domain.dir=${bea.home}/user_projects/domains/${avalin.domain.name} avalin.domain.conf.path=${avalin.domain.dir}/conf avalin.domain.security.login.config=file://${avalin.domain.conf.path}/ login.config avalin.nodemgr.home=${avalin.domain.dir}/nodemanager avalin.nodemgr.port=5556 avalin.nodemgr.logon.user=nodemanager avalin.nodemgr.logon.password=node13! ###### Cluster configuration avalin.cluster.1.multicast.ip= avalin.cluster.1.multicast.port=17123 avalin.machines=3 avalin.managed.servers=3 ###### Managed servers configuration avalin.managed.server.1=sdman1 avalin.machine.1.addresses=${avalin.managed.server.1} avalin.machine.1.nodemgr.host=${avalin.managed.server.1} avalin.machine.1.nodemgr.port=5556 avalin.managed.server.1.host= avalin.managed.server.1.port=8080 avalin.managed.server.1.ssl.port=8443 avalin.managed.server.1.cluster=1 avalin.managed.server.1.machine=1 avalin.managed.server.1.replicationgroup=group1 avalin.managed.server.1.multicastinterfaceaddress= avalin.managed.server.1.domain.home=${avalin.domain.dir} avalin.managed.server.1.java.home=${avalin.java.home} avalin.managed.server.1.bea.home=${bea.home} avalin.managed.server.1.channel1.name=channel-http-80 Kofax, Inc. 31

38 avalin.managed.server.1.channel1.protocol=http avalin.managed.server.1.channel1.listen.port=80 avalin.managed.server.1.channel1.external.listen.port=80 avalin.managed.server.1.channel1.enabled=true avalin.managed.server.1.channel1.client.certificate.enforced=false avalin.managed.server.2=sdman2 avalin.machine.2.addresses=${avalin.managed.server.2} avalin.machine.2.nodemgr.host=${avalin.managed.server.2} avalin.machine.2.nodemgr.port=5556 avalin.managed.server.2.host= avalin.managed.server.2.port=8080 avalin.managed.server.2.ssl.port=8443 avalin.managed.server.2.cluster=1 avalin.managed.server.2.machine=2 avalin.managed.server.2.replicationgroup=group1 avalin.managed.server.2.multicastinterfaceaddress= avalin.managed.server.2.domain.home=${avalin.domain.dir} avalin.managed.server.2.java.home=${avalin.java.home} avalin.managed.server.2.bea.home=${bea.home} avalin.managed.server.2.channel1.name=channel-http-80 avalin.managed.server.2.channel1.protocol=http avalin.managed.server.2.channel1.listen.port=80 avalin.managed.server.2.channel1.external.listen.port=80 avalin.managed.server.2.channel1.enabled=true avalin.managed.server.2.channel1.client.certificate.enforced=false avalin.managed.server.3=sdman3 avalin.machine.3.addresses=${avalin.managed.server.3} avalin.machine.3.nodemgr.host=${avalin.managed.server.3} avalin.machine.3.nodemgr.port=5556 avalin.managed.server.3.host= avalin.managed.server.3.port=8080 avalin.managed.server.3.ssl.port=8443 avalin.managed.server.3.cluster=1 avalin.managed.server.3.machine=3 avalin.managed.server.3.replicationgroup=group1 avalin.managed.server.3.multicastinterfaceaddress= avalin.managed.server.3.domain.home=${avalin.domain.dir} avalin.managed.server.3.java.home=${avalin.java.home} avalin.managed.server.3.bea.home=${bea.home} avalin.managed.server.3.channel1.name=channel-http-80 avalin.managed.server.3.channel1.protocol=http avalin.managed.server.3.channel1.listen.port=80 avalin.managed.server.3.channel1.external.listen.port=80 avalin.managed.server.3.channel1.enabled=true avalin.managed.server.3.channel1.client.certificate.enforced=false ###### Administration server configuration avalin.domain.admin.host=${avalin.domain.host} ###### Cluster URL configuration 32 Kofax, Inc.

39 wls.cluster.url=${avalin.managed.server.1}:${avalin.managed.server.1.port},$ {avalin.managed.server.2}:${avalin.managed.server.2.port},${avalin.managed.s erver.3}:${avalin.managed.server.3.port} ###### Proxy server configuration avalin.machine.proxyserver.addresses=sdadmin1 avalin.machine.proxyserver.ip= avalin.machine.proxyserver.nodemgr.host=sdadmin1 avalin.machine.proxyserver.nodemgr.port=5556 avalin.managed.servers.list=${avalin.managed.server.1}:${avalin.managed.serv er.1.port} ${avalin.managed.server.2}:${avalin.managed.server.2.port} ${aval in.managed.server.3}:${avalin.managed.server.3.port} avalin.managed.server.number=${avalin.managed.servers} avalin.managed.server.proxyserver.host= avalin.managed.server.proxyserver.port=8080 avalin.managed.server.proxyserver.ssl.port=8443 ###### Server Java VM startup options 32-bit Weblogic avalin.java.options=- Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl - Djava.security.auth.login.config=${avalin.domain.security.login.config} - Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFac toryimpl avalin.managed.servers.vmargs=-dweblogic.store.jdbc.ioretrydelaymillis= Xnohup avalin.admin.server.vmargs= avalin.proxy.server.vmargs= ###### Server Java VM startup options 64-bit Weblogic #avalin.java.options=- Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl - Djava.security.auth.login.config=${avalin.domain.security.login.config} - Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFac toryimpl -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 #avalin.managed.servers.vmargs=- Dweblogic.store.jdbc.IORetryDelayMillis= Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xnohup #avalin.admin.server.vmargs=- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 #avalin.proxy.server.vmargs=- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 ###### Oracle DB Configuration db.avalin.ora.host=sdoracle db.avalin.ora.port=1521 db.avalin.ora.sid=orcl db.avalin.ora.user=myoracleuser db.avalin.ora.password=myoraclepassword Kofax, Inc. 33

40 What s in Weblogic Administration Console? After installation and starting the cluster, log on to the WebLogic Administration Console and see that the following items have been created (as shown in Figure 6): A cluster of three managed servers A JMS server for each managed server A persistent store for each JMS server An XA data source and a non-xa data source Cluster JMS Servers Persistent Stores Data Sources avalincluster_1 avalinmanaged_1 AvalinJMSServer_1 JDBCStore-1 OraDS OracleNonXA avalinmanaged_2 AvalinJMSServer_2 JDBCStore-2 avalinmanaged_3 AvalinJMSServer_3 JDBCStore-3 Figure 6. Example: Items In WebLogic Administration Console After Installation What Needs to be Done After Installation? After installation, the following tasks need to be performed (as illustrated in Figure 7 and described in Configuring for Oracle RAC): For each node in the Oracle RAC, create an XA and a non-xa data source. Create an XA and a non-xa multi data source. Reset all persistent stores to use the non-xa multi data source. 34 Kofax, Inc.

41 JDBCStore-1 JDBCStore-2 DESOracleNonXA Multi Data Sources OraDS JDBCStore-3 temp Data Sources OracleNonXA_1 RAC_1 OraDS_1 OracleNonXA_2 RAC_2 OraDS_2 OracleNonXA_3 RAC_3 OraDS_3 Figure 7. Example: Items you Create or Reset in WebLogic Administration Console Configuring for Oracle RAC If your planned installation includes using an Oracle RAC, you edited the Oracle section of the install.properties file with specifics of one of the nodes in your Oracle RAC cluster. During the installation process, an XA data source (OraDS) and a non-xa data source (OracleNonXA) were created. To complete the configuration to connect to your Oracle RAC, you need to perform the following tasks in the WebLogic Administration Console: Create an XA data source for each node in the Oracle RAC. Create one multi data source that links all the nodes in the Oracle RAC. Create a non-xa data source for each node in the Oracle RAC. Create one non-xa multi data source that links all the nodes in the Oracle RAC. Reset all the persistent stores to use the non-xa multi data source. The remainder of this section provides the instructions for each of the tasks. Create the XA Data Sources During installation, one JDBC XA data source named OraDS is created based on the values in the install.properties file. However, since you need to create a multi data source named OraDS and because you cannot have a duplicate named in a data source and a multi-data source you will begin the connection tasks by deleting the OraDS data source. To create the XA data sources 1 In the WebLogic Administration Console under Domain Structure, expand Services expand JDBC, and select Data Sources. The Summary of JDBC Data Sources screen (Figure 8) appears. Kofax, Inc. 35

42 Figure 8. Summary of JDBC Data Sources Screen 2 Under the Change Center, click the Lock & Edit button, select the check box for the OraDS data source, and click Delete. Click Yes when prompted to confirm the delete. 3 Click New. The JDBC Data Source Properties screen appears. Complete the fields as follows: Name: A name of your choosing, for example OraDA_1. This is to identify the data source: it is not the information about your RAC node, which comes later. JNDI name: A name of your choosing, which can be same as Name above. Database Type: Oracle Database Driver: Oracle s Driver (Thin XA) 4 Click Next. The Transaction Options screen appears, notifying you about XA driver details. 5 Click Next. The Connection Properties screen appears, where you define connection properties for a node in your Oracle RAC. Complete the fields as follows: Database Name: The SID of a RAC node. Host Name: The host name of the RAC node above. Port: 1521 Database User Name: The user name specified in the install.properties for db.avalin.ora.user=. Password and Confirm Password: The password for the database user above. 6 Click Next. The Test Your Connection screen appears where you can test your connection and then click Next. The Select Targets screen appears. 7 In the Clusters group, select the check box of your cluster (for example, avalincluster_1 as shown in Figure 9) as the target and click Finish. You are returned to the Summary of JDBC Data Sources screen. 36 Kofax, Inc.

43 Figure 9. Selecting the Cluster as Target 8 In the Name column of the Data Sources table, click the data source name. The Settings screen appears. 9 Click the Connection Pool tab. At the bottom of the screen (you may have to scroll down), expand Advanced. Select Test Connections On Reserve, then click Save. 10 Click the Transaction tab, select every check box, and complete the following fields: XA Transaction Timeout: 120 XA Retry Duration: Click Save. 12 Under Change Center, click the Activate Changes button. 13 For an additional node in the cluster, under Domain Structure, expand Services, expand JDBC, and select Data Sources. The Summary of JDBC Data Sources screen appears Repeat the process for each node in the RAC cluster. Repeat from step 3 above. When all nodes have a data source, create the multi data source. Create the XA Multi Data Source To create the XA Multi Data Source 1 Under Domain Structure, expand Services, JDBC, and select Multi Data Sources. The Configure the Multi Data Source screen appears. 2 Click Lock & Edit, then click New. The Configure the Multi Data Source screen appears. Complete the fields as follows: Name: OraDS JNDI Name: OraDS Algorithm Type: select the option you prefer, either Failover or Load-Balancing. 3 Click Next. The Select Targets screen appears. 4 In the Clusters group, select the check box of your cluster (for example, avalincluster_1 as shown in Figure 9) as the target and click Next. The Select Data Source Type screen appears. 5 Select XA Driver and click Next. The Add Data Sources screen appears. Kofax, Inc. 37

44 Figure 10. Add Data Sources Screen 6 Move all the nodes to the Chosen column and click Finish. 7 Under Change Center, click the Activate Changes button. 8 If Document Exchange Server was running on any managed server in the cluster during these data source and multi data source changes, then stop and restart the managed server. If Document Exchange Server was not running on a managed server, it should be started. When you are done, create the non-xa data sources. Create the Non-XA Data Sources JMS messages need to be persistent, so you need to create a non-xa data source for each node in the Oracle RAC and also a persistent store for each managed server in the Weblogic cluster so a table will be added to the database to contain this information. To create the non-xa data sources 1 In the WebLogic Administration Console under Domain Structure, expand Services expand JDBC, and select Data Sources. The Summary of JDBC Data Sources screen (Figure 11) appears. 38 Kofax, Inc.

45 Figure 11. Summary of JDBC Data Sources Screen 2 Under the Change Center, click the Lock & Edit button. 3 Click New. The JDBC Data Source Properties screen appears. Complete the fields as follows: Name: A name of your choosing, for example OracleNonXA_1. This is to identify the data source: it is not the information about your RAC node, which comes later. JNDI name: A name of your choosing, which can be same as Name above. Database Type: Oracle Database Driver: Oracle s Driver (Thin) 4 Click Next. The Transaction Options screen appears. Unselect Supports Global Transactions. 5 Click Next. The Create a New JDBC Data Source screen appears. Complete the fields as follows: Database Name: The SID of a RAC node. Host Name: The host name of the RAC node above. Port: 1521 Database User Name: The user name specified in the install.properties for db.avalin.ora.user=. Password and Confirm Password: The password for the database user above. 6 Click Next. The Test Your Connection screen appears where you can test your connection and then click Next. The Select Targets screen appears. 7 In the Clusters group, select the check box of your cluster as the target and click Finish. You are returned to the Summary of JDBC Data Sources screen. 8 In the Name column of the Data Sources table, click the data source name. The Settings screen appears. 9 Click the Connection Pool tab. At the bottom of the screen (you may have to scroll down), expand Advanced. Select Test Connections On Reserve, then click Save. 10 Click Save. 11 Under Change Center, click the Activate Changes button. Kofax, Inc. 39

46 12 For an additional node in the cluster, under Domain Structure, expand Services, expand JDBC, and select Data Sources. The Summary of JDBC Data Sources screen appears. 13 Repeat the process from step 3 to create a non-xa data source for each node in the RAC cluster. When all nodes have a non-xa data source, create the non-xa multi data source. Create the Non-XA Multi Data Source During installation, one non-xa JDBC data source named OracleNonXA is created based on the values in the install.properties file. This data source is assigned to each of the persistent stores, so you will create a Non-XA multi data source so you can assign it to your persistent stores. To create the non-xa Multi Data Source 1 Under Domain Structure, expand Services, JDBC, and select Multi Data Sources. The Configure the Multi Data Source screen appears. 2 Click Lock & Edit, then click New. The Configure the Multi Data Source screen appears. Complete the fields as follows: Name: A name of your choosing, for example DESOracleNonXA (you cannot use the name OracleNonXA) JNDI Name: A name of your choosing, which can be same as Name above Algorithm Type: you must select Failover 3 Click Next. The Select Targets screen appears. 4 In the Clusters group, select the check box of your cluster as the target and click Next. The Select Data Source Type screen appears. 5 Select Non-XA Driver and click Next. The Add Data Sources screen appears. 6 Move the non-xa data sources you created to the Chosen column and click Finish. Note Do not move OracleNonXA: you will delete it after you reset the persistent stores data source in the next section. 7 Under Change Center, click the Activate Changes button. Reset the Persistent Stores Data Source You need to reset the temporary data source selection to the new non-xa multi data source you just created. To reset the data source 1 In the WebLogic Administration Console under Domain Structure, expand Services and select Persistent Stores. The Summary of Persistent Stores screen appears. 2 In the Data Source field, select your non-xa multi data source (Figure 12) and click Save. 40 Kofax, Inc.

47 Figure 12. Reset Data Source to non-xa Multi Data Source 3 Repeat the steps above to reset the data source for each of your persistent stores. Note If you change the prefix name, you must restart the associated managed server for the change to occur. 4 To verify the configuration, go into the database, and for each managed server you should see a table <prefix>wl-store where <prefix> is the prefix from a Persistent Store. Now that the data source OracleNonXA is no longer assigned to your persistent stores, you can delete it from the Data Sources table. Configuring Destination Types Two destination types are preinstalled with Kofax Document Exchange Server: Network Location to send documents to a network folder Kofax Queue to send documents to a queue Both destinations, like all Kofax Document Exchange destinations, need to be enabled in Kofax Administration Console. Note For information about configuring network folders to use as destinations and setting up queues, refer to the Kofax Document Exchange Server Administrator s Guide. Kofax, Inc. 41

48 Deploying Connectors for Additional Destinations To configure Kofax Document Exchange Server for additional destination types, you need to copy and modify one or more configuration files and deploy a connector file. For each destination (Kofax Capture or IBM Content Manager for example), there is a configuration or installation guide with instructions on which files to use and where to deploy them. You will find the configuration guides in the following folders: The \Documentation\Guides folder where Kofax Document Exchange Server is installed (usually C:\Program Files\Kofax\Document Exchange Server). The \setup\guides folder on the Kofax Document Exchange Server installation media. The Kofax Fax Connector Installation Guide provides installation and configuration instructions for the Kofax Fax Connector. If you select to install Documentation during the setup process, the guide is installed with Kofax Document Exchange in the \OtherResources\FaxConnector folder. Follow the instructions below to deploy or delete a connector on WebLogic. To deploy a connector 1 In the WebLogic Server Administration Console in your Document Exchange Server domain, select Deployments and click the Lock & Edit button. Figure 13. Lock & Edit Button 2 In the Deployments table, click Install, and then on the Install Application Assistant page click the link upload your file(s). 3 Click the Deployment Archive Browse button. Browse to the DES\setup folder where Kofax Document Exchange Server was installed and select the connector file. 4 Click Next. The connector name appears in the Location table (Figure 14). 5 In the Location table, select the connector. You may have to scroll down to see the connector in the list. 42 Kofax, Inc.

49 Figure 14. Location Table 6 Click Next, and choose the targeting style Install this deployment as an application. 7 Click Next, and select the entire cluster as the deployment target. Figure 15. Cluster Target 8 Click Next. You can view the optional settings, but no optional changes are needed so you can click Next. 9 Review the summary and then click Finish to complete the installation. 10 Under Change Center, click Activate Changes to complete the connector deployment. Kofax, Inc. 43

50 Figure 16. Activate Changes Button 11 The connector state is Prepared, so you need to activate it. Click Deployments and select the check box to the left of the connector name. Figure 17. Deployments Table with Connector Selected 12 Click Start Servicing all requests. Click Yes when prompted. The connector should now be deployed and active. 13 In Kofax Administration Console, be sure the connector is enabled. To delete a connector 1 In the WebLogic Server Administration Console in your Document Exchange Server domain, select Deployments and click the Lock & Edit button. 2 If the connector you want to delete is in an Active state, you must stop it before it can be deleted. Select the check box to the left of the connector name and click Stop Force Stop Now (or appropriate selection, depending on whether there is work to be completed). 3 Select Yes when prompted. The connector State returns to Prepared. 4 Select the check box to the left of the connector name of the connector you want to delete. 5 Click the Delete button and click Yes when prompted. 6 Click the Activate Changes button. The connector should now be deleted. 44 Kofax, Inc.

51 Installing MFP Front Panel Software Your MFP may require additional software to display Kofax Document Exchange Server shortcut buttons on the front panel. Instructions for installing the software and other information about setting up the MFP are in administrator guides in the following folders: The Documentation\Guides folder where Kofax Document Exchange Server is installed (usually C:\Program Files\Kofax\Document Exchange Server) The setup\guides folder on the Kofax Document Exchange Server installation media For more information about supported MFPs, refer to the Kofax Web site. Other Configuration Tasks Refer to the Kofax Document Exchange Server Administrator s Guide for instructions for modifying properties files and making other configuration changes. What if Port 7001 is in Use: Changing the Admnistration Server Port The installation command ant install-admin-server fails when avalin.domain.port in the Install.properties file is changed from its default value of (SPR ) If you cannot use port 7001 because another application is using it, reconfigure that application to temporarily use another port and perform the Kofax Document Exchange Server installation using port When installation is complete, change the administration server port. To change the Administration server port 1 Under Domain Structure, expand Environment and select Servers. The Summary of Servers screen appears. 2 In the Servers table in the Name column, click AdminServer(name). The Settings for AdminServer screen appears. 3 Click the Lock & Edit, then type the desired port number in the Listen Address: field. 4 Click the Save button, then under the Change Center click the Activate Changes button. 5 Stop the cluster. 6 On the administration server, in the AppServer\install folder where Kofax Document Exchange Server was installed, edit both the install.properties and install_default.properties files and change all occurrences of the port value 7001 to the value you want to use. Note You only have to edit these files on the administration server: the files on the managed servers do not need to be changed. 7 Save and close the files, and start the cluster. The administration server should now be using the new port. 8 Port 7001 can now be restored to the original application. Kofax, Inc. 45

52 Changing the WebLogic Administrator Credentials After installation, you can change the password to the WebLogic user that was created during Kofax Document Exchange Server installation, or change to another WebLogic user. To change the WebLogic administrator user 1 With the cluster started, in the WebLogic Administration Console, add a new user and give Administrator rights or change the password of the weblogic user. 2 Save and Activate the changes and log off the console. 3 Stop the cluster. 4 If you just need to change the user name, change the install.properties file on the administration server and then copy it to each machine in the cluster, including the proxy server machine. Go to step 6. 5 If you changed the password, do the following to encrypt it: a Start the administration server using the appropriate script: ant start-avalin-cluster ant start-avlain-cluster-with-proxy b The password will now be encrypted in the install.properties file. c Copy the file to each machine in the cluster, including the proxy server. 6 Stop and then restart the cluster. 7 You can now log on the the WebLogic Administration Console using the new credentials. Stopping and Restarting Kofax Document Exchange Server You may need to stop and restart a managed server or your cluster when changing configuration files or for routine maintenance. Use the WebLogic Administration Console to manage the cluster and your managed servers. You can also manage the cluster from the command line: To start the cluster from the command line: If you are using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type ant start-avalin-cluster-with-proxy. If you are not using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type ant start-avalin-cluster. To stop the cluster from the command line: If you are using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type ant stop-avalin-cluster-with-proxy. If you are not using a proxy server, at the folder \AppServer\install where Kofax Document Exchange Server was installed, type ant stop-avalin-cluster. Troubleshooting This section provides installation troubleshooting information. 46 Kofax, Inc.

53 Technical Support For additional technical information about Kofax products, visit the Kofax Web site at and select an appropriate option from the Support menu. The Kofax Support pages provide product-specific information, such as current revision levels, the latest drivers and software patches, online documentation and user manuals, updates to product release notes (if any), technical tips, and an extensive searchable knowledgebase. The Kofax Web site also contains information that describes support options for Kofax products. Please review the site for details about the available support options. If you need to contact Kofax Technical Support, please have the following information available: Kofax Document Exchange Server software version and build number Operating system and service pack version MFP or scanner make and model Kofax Document Scan Server version Destination type name, version, and configuration Special/custom configuration or integration information Kofax, Inc. 47

54 48 Kofax, Inc.