ImageNow Update Readme Version: 6.6.x Written by: Product Documentation, R&D Date: June 2014 ImageNow and CaptureNow are registered trademarks of Perceptive Software, Inc. All other products produced by Perceptive Software, Inc., including WebNow, are Perceptive Software trademarks. All other brands and product names mentioned in this document are trademarks or registered trademarks of their respective owners. Copyright 2014 Perceptive Software, Inc. All rights reserved.
Table of Contents ImageNow Server 6.6.x Update readme... 3 Prepare for the update... 3 Special considerations... 3 UNC Paths... 3 64-bit... 3 Database... 4 Windows operating systems... 4 Updating ImageNow Server... 5 Updating ImageNow Server on Windows... 5 Updating ImageNow Server on UNIX... 11 Install library files... 20 Start all ImageNow services in Windows... 21 Start all ImageNow services in UNIX... 22 Verify your ImageNow database... 22 Updating Agents... 23 Updating ImageNow Client... 23 Updating WebNow... 23 Updating ImageNow Forms Server... 24 Updating Business Insight... 25 Updating Fax Agent... 25 Updating Output Agent on UNIX... 27 Addendum A: Database Changes by Release... 29 Addendum B: INI Changes by Release... 40 INI changes from 6.1.0 to 6.1.1... 40 INI changes from 6.1.1 to 6.1.2... 40 INI changes from 6.1.2 to 6.1.3... 41 INI changes from 6.1.3 to 6.1.4... 41 INI changes from 6.1.4 to 6.1.5... 41 INI changes from 6.1.5 to 6.2... 42 INI changes from 6.2 to 6.3... 43 INI changes from 6.3 to 6.4... 45 INI changes from 6.4.x to 6.5... 46 INI changes from 6.5.x to 6.6.x... 48 Page 2 of 49
ImageNow Server 6.6.x Update readme This readme file provides important information about updating ImageNow products from a previous version of 6.x to 6.6.x. Read this file before you update ImageNow Server, clients, agents, database, and extensions. Note This document does not provide information on performing a more significant upgrade from a version prior to 6.x. If you are attempting to upgrade from a version previous to 6.x, Perceptive Software recommends you arrange a managed upgrade. For more information visit the Upgrade Center at https://www.perceptivesoftware.com/upgrade, or email upgrade@perceptivesoftware.com. Prepare for the update Make sure to make complete backups of all ImageNow Server data before beginning any update installation. For more information, see the Contingency Planning and Disaster Recover Best Practices Guide. Neither Perceptive Software nor any of its authorized resellers are responsible for lost data caused by the update procedure described below. Before updating your ImageNow system, verify that your system matches the requirements listed in the latest version of the Technical Specifications. To view this document, go to www.perceptivesoftware.com, log in to the Customer Portal, select the Product Documentation link, and select 6.6.x as your product version. In the navigation pane, select Administrator Topics>Technical Specifications, and then open the Technical Specifications for ImageNow file. When you update your ImageNow system from 6.x to this version, you do not need additional licenses. Special considerations Before you perform an update of your ImageNow system, ensure that you keep in mind the considerations specific to your configuration. UNC Paths When you update your system, it is important to understand that Window s Universal Naming Convention (UNC) paths are not recommended for ImageNow versions 6.6 or higher. A UNC path can work as an operating system shortcut to a particular path, for example \\server\volume\directory. However, the operating system does not reliably report information about failures to ImageNow when a UNC path is used. Without the correct information, issues cannot be quickly and/or properly diagnosed, and because of this inaccurate reporting in a Windows environment, UNC paths are not supported. Instead of using UNC paths in a Windows environment, use direct-drive mapping, or if possible, a storage area network (SAN) device or another method of direct-attached storage (DAS). For UNIX, Network File System (NFS) shares should be used because they are a proven and reliable source. 64-bit If you are switching to a 64-bit ImageNow Server machine during your 6.6 update, note that the switch to a 64-bit machine involves changing your operating system. For information about migrating ImageNow to this environment, refer to the Moving ImageNow Server on Windows to 64-bit Best Practices guide, which is available in the Product Documentation tab in the Customer Portal on our website. Before you install WebNow or Forms Server, you must have your web application server, such as Apache Tomcat, successfully installed. The version of the web application server (32 or 64-bit) must be compatible with the WebNow or Forms Server version (32 or 64-bit). Page 3 of 49
If your ImageNow Server machine runs on a 64-bit environment, you must configure external 32-bit agents remotely from 32-bit machines. Verify the compatibility of all of your applications and business applications with a 64-bit operating system before you install ImageNow. Database In ImageNow 6.6, the INOW6 database tables reside in the DBO schema for SQL Server and the INUSER schema for Oracle databases. Starting in version 6.6.0.0878, the INEMUSER schema was added to the database to hold the IN_EXTERN_MSG_SEQ table. This isolates the table from the rest of the INUSER schema. For SQL Server, the INUSER user owns the INEMUSER schema and has full privileges on the schema. For Oracle, in addition to the IN_EXTERN_MSG_SEQ table, there is also a sequence and trigger that is created in the INEMUSER schema that is used for populating the table with sequential numbers. If any database backup or replication jobs are schema based, they should be modified to include the INEMUSER schema. Windows operating systems When you update your ImageNow system on Windows, perform the update steps as the administrator user account used when you originally installed ImageNow. If this account is no longer available, and you licensed your version of ImageNow per machine rather than per user, you can use a local administrator account. Page 4 of 49
Updating ImageNow Server This release contains updates to the ImageNow Server on Windows or UNIX running an external SQL database, such as Oracle or Microsoft SQL. Follow the steps in the procedure below that describes your environment and DBMS. Updating ImageNow Server on Windows Before you begin, check the version of ImageNow 6 that you are running. For example, to check the version in Windows Explorer, right-click inserver.exe and select Properties. In the Properties dialog box, click the Version tab to view the file version. Contact Perceptive Software Technical Support if you have any questions. 1. Perform a complete backup of all ImageNow Server data. For more information about backing up ImageNow data, refer to the Contingency Planning and Disaster Recovery Best Practices Guide. 2. Stop all ImageNow services. All services and client connections must be closed before inserver is stopped, including any remote agents. 1. To see which services are running, launch ImageNow Server Administrator (ISA). 2. To stop services, right-click on the service and select Stop. 3. Stop the ImageNow Server and all other services. 3. To ensure you retain unique customizations or comments in your INI files, back up your INI files to a directory other than inserver6, for example c:/tmp. 4. Run the appropriate DDL script for your database application and the current version of ImageNow Server that you are running. Follow the instructions appropriate for your RDBMS for running an incremental database upgrade script. A qualified DBA should perform this action. The following table outlines the correct incremental database file that you will need for the version of ImageNow that you are currently running. If the Incremental Database File column shows multiple.sql files, make sure that you run them in the order shown. Note The Incremental-SS_6.5.1_to_6.6.0.237.sql script puts the INOW6 database in SINGLE_USER mode while Snapshot Isolation and Row Versioning are enabled. The current upgrade connection remains active. The system stops, rolls back, and then disconnects any other connections to the database in order to successfully complete the READ_COMMITED_SNAPSHOT command. Last, the system returns the database to MULTI_USER mode and executes the rest of the script. Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.0.0 801, 803 Incremental-SS_6.0.0.801_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and Page 5 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.0.0 818 Incremental-SS_6.0.0.818_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.0.1 856, 901, 942 Incremental-SS_6.0.1.856_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.0 99, 116, 122, 126, 141, 200 Incremental-SS_6.1.0.138_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.1 253, 289, 291, 319 Incremental-SS_6.1.1.289_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and Page 6 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.1.2 38, 87, 123, 129 Incremental-SS_6.1.3.51_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.3 23, 47, 54, 81, 88 Incremental-SS_6.1.3.51_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.4 3, 31, 46, 54, 55 Incremental-SS_6.1.4_IndexPack.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.4 68, 76, 85 Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and Page 7 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.1.5 15, 23, 50, 85 Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.2.0 527, 527, 552 Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.2.1 27, 59, 91 Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.3.0 394 Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.4.0 103, 234 Incremental-SS_6.5.0.335_to_6.5.1.19.sql and Page 8 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.4.1 4, 186 Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.5.x 226 Note Run Incremental- SS_6.5.1_to_6.6.0.237.sql for any ImageNow Server build number higher than 6.5.1.19. Incremental-SS_6.5.0.335_to_6.5.1.19.sql and 6.6.x 750 The following table outlines the correct Oracle incremental database file that you need for the version of ImageNow that you are currently running. Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.0.0 801, 803 Incremental-Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.0.0 818 Incremental-Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.0.1 856, 901, 942 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and Page 9 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.1.0 99, 116, 122, 126, 141, 200 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.1 253, 289, 291, 319 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.2 38, 87, 123, 129 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.3 23, 47, 54, 81, 88 Incremental- Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.4 3, 31, 46, 54, 55, 68, 76, 85 Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.5 15, 23, 50, 85 Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.2.0 527, 527, 552 Incremental-ORA_6.2.0.527_to_6.6.0.237.sql and 6.2.1 27, 59, 91 Incremental-ORA_6.2.0.527_to_6.6.0.237.sql and Page 10 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.3.0 394 Incremental-ORA_6.3.0.119_to_6.6.0.237.sql and 6.4.0 103, 234 Incremental-ORA_6.4_to_6.6.0.237.sql and 6.4.1 4, 186 Incremental-ORA_6.4_to_6.6.0.237.sql and 6.5.x 226 Incremental-ORA_6.5.1_to_6.6.0.237.sql and 6.6.x 750 1. Run the ImageNow Server installer. Note During this installation, a message appears to inform you that this is an update. If you do not receive this message, stop the installation and verify that you are logged on as the same Administrator user account used when ImageNow was originally installed. Then, install the update. 2. Compare the previous INI files from your backup copy of the /inserver6/etc directory with the new INI files in /inserver6/etc. The Windows installer automatically adapts your previous settings to the new settings, however, the installer overwrites any custom comments, settings, or notes that you might have previously added. Alter the new INI files in /inserver6/etc as needed. These changes appear in the "Addendum B: INI Changes by Release" section of this document. 3. When you finish updating the ImageNow Server, proceed to the Verify your ImageNow database section of this document. Updating ImageNow Server on UNIX Before you begin, verify the version of ImageNow that you are running. Contact Perceptive Software Technical Support if you have any questions. 1. Perform a complete backup of all ImageNow Server data. For more information about backing up ImageNow data, refer to the Contingency Planning and Disaster Recovery Best Practices Guide. Page 11 of 49
2. From /inserver6/bin, stop all ImageNow services. All services and client connections must be closed before inserver is stopped, including any remote agents. To determine which services are running:./inserver s To stop services:./inserverjob k./inserveralarm k./inserverbatch k./inserver k 3. Copy the contents of /inserver6/bin and /inserver6/etc directory to a backup directory. 4. Move the ImageNow_Server_6.6.0_for_MSSQL_Oracle_Patch_Build_<###>_for_<OSName>.tar.gz file to the /inserver6 directory. This is the format of the installer file, where <###> is the build number and <OSName> is the name of the operating system. Example ImageNow_Server_6.6.0_for_MSSQL_Oracle_Patch_Build_750_for_AIX.tar.gz 5. From /inserver6, gunzip and tar the installer file. gunzip ImageNow_Server_6.6.0_for_MSSQL_Oracle_Patch_Build_<###>_for_<OSName>.tar. gz tar xvf ImageNow_Server_6.6.0_for_MSSQL_Oracle_Patch_Build_<###>_for_<OSName>.tar Page 12 of 49
6. From the inserver6 directory, issue the following command to change ownership: chown R root:bin * 7. Compare the previous INI files from your backup copy of the /inserver6/etc directory with the new INI files in /inserver6/etc. Alter the new INI files in /inserver6/etc as needed. These changes appear in the "Addendum B: INI Changes by Release" section of this document. 8. Look at this table and run the necessary incrementals. Follow the instructions appropriate for your RDBMS for running an incremental database upgrade script. This should be performed by a qualified DBA. Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.0.0 801, 803 Incremental-SS_6.0.0.801_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.0.0 818 Incremental-SS_6.0.0.818_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.0.1 856, 901, 942 Incremental-SS_6.0.1.856_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and Page 13 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.1.0 99, 116, 122, 126, 141, 200 Incremental-SS_6.1.0.138_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.1 253, 289, 291, 319 Incremental-SS_6.1.1.289_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.2 38, 87, 123, 129 Incremental-SS_6.1.3.51_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.3 23, 47, 54, 81, 88 Incremental-SS_6.1.3.51_to_6.1.4.25.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and Page 14 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.1.4 3, 31, 46, 54, 55 Incremental-SS_6.1.4_IndexPack.sql and Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.4 68, 76, 85 Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.1.5 15, 23, 50, 85 Incremental-SS_6.1.4.26_to_6.2.0.527.sql and Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.2.0 527, 527, 552 Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and Page 15 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for SQL 6.2.1 27, 59, 91 Incremental-SS_6.2.0.527_to_6.3.0.119.sql and Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.3.0 394 Incremental-SS_6.3.0.119_to_6.4.1.4.sql and Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.4.0 103, 234 Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.4.1 4, 186 Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.5.x 226 Note Run Incremental- SS_6.5.1_to_6.6.0.237.sql for any ImageNow Server build number higher than 6.5.1.19. Incremental-SS_6.5.0.335_to_6.5.1.19 and 6.6.x 750 Page 16 of 49
The following table outlines the correct Oracle incremental database file that you need for the version of ImageNow that you are currently running. Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.0.0 801, 803 Incremental-Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.0.0 818 Incremental-Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.0.1 856, 901, 942 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.0 99, 116, 122, 126, 141, 200 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.1 253, 289, 291, 319 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.2 38, 87, 123, 129 Incremental-6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.3 23, 47, 54, 81, 88 Incremental- Oral10g_6.0.0.801_to_6.1.4.25.sql and Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and Page 17 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.1.4 3, 31, 46, 54, 55, 68, 76, 85 Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.1.5 15, 23, 50, 85 Incremental-ORA_6.1.4.26_to_6.6.0.237.sql and 6.2.0 527, 527, 552 Incremental-ORA_6.2.0.527_to_6.6.0.237.sql and 6.2.1 27, 59, 91 Incremental-ORA_6.2.0.527_to_6.6.0.237.sql and 6.3.0 394 Incremental-ORA_6.3.0.119_to_6.6.0.237.sql and 6.4.0 103, 234 Incremental-ORA_6.4_to_6.6.0.237.sql and 6.4.1 4, 186 Incremental-ORA_6.4_to_6.6.0.237.sql and 6.5.x 226 Incremental-ORA_6.5.1_to_6.6.0.237.sql and Page 18 of 49
Current Version of ImageNow Build Number of ImageNow Server Incremental Database File for Oracle 6.6.x 750 9. From the /inserver6/etc directory, configure the odbc.ini file and the odbc section of the inow.ini file. Make sure you supply the same name for the protocol name in both INI files. Supply your install directory, database name (INOW6 by default), and host name to replace the following text shown in blue. Update the odbc.ini file: [ODBC Data Sources] SQLServer Wire Protocol=DataDirect 6.0 SQL Server Wire Protocol [SQLServer Wire Protocol] Driver=[INSTALL_DIR]/odbc/lib/IUmsss24.so Description=DataDirect 6.0 SQL Server Wire Protocol Database=[db name] LogonID=inuser Password=imagenow Address=[sqlserverhost name],1433 QuotedId=No AnsiNPW=No [ODBC] Trace=0 TraceFile=[INSTALL_DIR]/log/odbctrace.out TraceDll=[INSTALL_DIR]/odbc/lib/odbctrac.so InstallDir=[INSTALL_DIR]/odbc ConversionTableLocation=[INSTALL_DIR]/odbc/tables UseCursorLib=0 10. Update the odbc section of inow.ini file: [ODBC] odbc.dbms=sqlserver odbc.dsn=[sqlserver Wire Protocol] odbc.userid=inuser odbc.password=jnbhfopx odbc.use_dddriver=true 11. Setup key environment variables by sourcing the setenv.sh script from the /inserver6/bin directory. (This step is necessary every time a new login session is established.)../setenv.sh 12. Navigate to the /inserver6/bin directory and untar the upgrade_scripts.tar file. tar -xvf upgrade_scripts.tar 13. Run the correct upgrade_6x_to_6x.sh file depending on what version you are coming from and updating to../upgrade_6x_to_6x.sh Page 19 of 49
14. Review the update log. This file is located in /inserver6/log directory and is named intool_upgrade_<date>.log. The log contains the changes performed by the update steps. Verify that no errors are listed. Install library files Install the library files specified in this section. Download UNIX supporting files 1. Go to the Perceptive Software website at www.perceptivesoftware.com and log in to the Customer Portal. 2. In the Product Downloads page, search for all downloadable items for the specific product and version you want to use. These files may include a product installer, product documentation, or set of supporting files. 3. Download the relevant files to a temporary directory on your computer. Page 20 of 49
Install library files 1. Navigate to the best location for your server computer to place the files from the downloaded tar file. This directory is referenced as <library_dir> in the remaining steps. If you have enough space, the easiest directory to place these files is /usr/local/waspc6.5. If you use this directory, you do not need to create a symbolic link. If you don t have enough space in the recommended location, then create a subdirectory for these files under the directory you created in the first step. You can use any directory location if you have other server considerations. 2. Navigate to the directory you determined in the previous step. Create a directory on your UNIX server to store the additional libraries required for ImageNow Server to operate properly by entering the following command, replacing <library_dir> with the directory name you want you want to use: mkdir <library_dir> 3. Copy the downloaded.tar file to the new directory. To unzip the file, navigate to the <library_dir> directory, and then type gunzip d <filename>.tar.gz, and then type tar -xvf <filename>.tar, replacing <filename> with the name you supplied during the download. The extracted files and subdirectories appear in <library_dir>. 4. If you did not use the recommended directory of /usr/local/waspc6.5 from previous steps, create a symbolic link from /usr/local/waspc6.5 to <library_dir>/waspc6.5 by entering: ln -s <library_dir>/waspc6.5/usr/local/waspc6.5 Start all ImageNow services in Windows Complete the steps in this section to start the ImageNow services in Windows. Using the command prompt 1. Open a window that accepts command prompts. 2. Navigate to the directory that contains the service you want to start by entering the following command: cd inserver6\bin For a 64-bit environment: cd inserver6\bin64 3. Enter the following command: <service> start Using Windows Computer Management 4. On your Windows Desktop, right-click the My Computer shortcut and select Manage. 5. In the Computer Management dialog box, click Services and Applications. 6. Click Services. 7. In the right-pane, right-click the service you want to start and select Start. Page 21 of 49
Start all ImageNow services in UNIX Complete the steps in this section to start the ImageNow services in UNIX. 1. If this is a new UNIX terminal session, source the setenv.sh file to set up your environment variables. For example, if you are using /bin/bash, the command to source the file is:../setenv.sh. Note If you ran setenv.sh for this session, do not run it again. If you are unsure whether you have run the command, check the IMAGENOWDIR6 environment variable with the following command: echo $IMAGENOWDIR6 2. Start all services and agents. For example, to start the main services and agents (inserver, inserveralarm, inserverbatch, inserverem, inserverfs, inserverimp, inserverjob, inservermonitor, inservermq, inservernotification, inserverosm, inservertask and inserverworkflow), navigate to the inserver6/bin directory and then execute the following commands: `pwd`/inserver start `pwd`/inserveralarm start `pwd`/inserverbatch start `pwd`/inserverem start `pwd`/inserverfs start `pwd`/inserverimp start `pwd`/inserverjob start `pwd`/inservermonitor start `pwd`/inservermq start `pwd`/inservernotification start `pwd`/inserverosm start `pwd`/inservertask start `pwd`/inserverworkflow start Note If you purchased additional ImageNow agents or services, like inserverft or inserverma, you must also start them. Each time you log on, you must set your environment variables, as shown in the previous step, before you execute startup commands like `pwd`/inserver. Verify your ImageNow database Verify your ImageNow database before proceeding. The INTool command you run in this procedure displays any differences between the latest version of the ImageNow database and the one you are currently using. 1. In Windows, complete the following substeps. 1. Click Start, and then click Run. 2. In the Run dialog box, type cmd and then click OK. 3. In the Command Prompt window, change to the [drive:]\inserver6\bin directory. 2. In UNIX, complete the following substeps. 1. Change to the $IMAGENOWDIR6/bin directory. 2. Enter the following command at the prompt: intool --cmd db-schema-validation Test describing the validation appears on the screen. If you see the message: Database validated. No inconsistencies detected, your database is aligned and you do not need to do anything further to update the database. If you get any other message, contact Product Support and provide them with a copy of any message you received. Page 22 of 49
Updating Agents You can update your agents using the procedures described in the installation guides provided for each agent. When you update an ImageNow agent, run the same steps as if you are installing a new version. The installation wizard detects the update and installs the product accordingly. Review the product readme for information about enhancements and changes that apply to specific agents. The agents listed in the following sections in this guide require additional steps. Important If you move your ImageNow Server to a 64-bit machine, you must move any agents that were previously installed on the local ImageNow Server machine to remote 32-bit machines. Updating ImageNow Client Refer to the ImageNow Installation Guide for information about running the installation wizard to update your ImageNow Clients. When you update the ImageNow Client, run the same steps as if you are installing a new version. The installation wizard detects the update and installs the product accordingly. You can update the ImageNow Client several different ways, including installing the client directly or using the automatic updater. To use the automatic updater, refer to the auto update readme file. Review the product readme for information about enhancements and changes for ImageNow Client. All existing ImageNow Client tokens are invalidated during the upgrade, and new tokens are generated as each ImageNow Client connects to the server. Updating WebNow Review the product readme for information about enhancements and changes for WebNow. If you are running WebNow Server in the Windows environment, refer to the WebNow Installation Guide, which is located on our website at www.perceptivesoftware.com. The installation wizard described in the guide updates WebNow Server in the Windows environment. WebNow 6.6.x is only compatible with ImageNow Server 6.6.x. If you are running WebNow Server in UNIX or prefer to use the.war file to update your system, refer to the following procedure. The following steps assume you have an installed version of WebNow and that you are familiar with deploying an application to your web application server. Important In ImageNow, version 6.2 and higher, WebNow requires Tomcat version 6.0. If you are using this configuration, we recommend that you install Business Insight, Forms Server, and WebNow on separate servers to avoid conflicts that might arise by using two separate versions of the Tomcat web application server on the same machine. To upgrade an existing version of WebNow with the latest version manually: 1. Stop the web application server. If you are running Tomcat, remove all files from the jsp folder, which removes the jsp cache so that WebNow runs properly. The Tomcat files are located at the path: \Program Files\Apache Software Foundation\Tomcat 6.0\work\Catalina\localhost\webnow\org\apache\jsp 2. Back up the entire \webnow folder. For example: On Tomcat, back up the \webapps\webnow directory. However, you do not need to back up \work\catalina\localhost\webnow. 3. If you are running the Tomcat web application server, delete the \work\catalina\localhost\webnow directory. 4. Download the war file as shown in the following table: Page 23 of 49
Web Server File to download Location to extract WebLogic (Windows) WebLogic (UNIX) WebSphere weblogic-webnow.war weblogic-webnow.war websphere-webnow.war \bea\user_projects\domains\mydomain \applications\webnow folder. Using the jar utility that comes with the Sun Java SDK, extract weblogic-webnow.war to the ${WL_HOME}\server\bin\applications \webnow folder. The web application server automatically extracts the websphere-webnow.war file. Tomcat tomcat-webnow.war \$TOMCAT_HOME\webapps folder. 5. Rename the war file to webnow.war. 6. Extract the webnow.war file as appropriate for your web application server. For example, in Tomcat, start your web application server and then stop the web application server to extract the WAR file. For more information about extracting the WAR file in your web application server, refer to the WebNow Installation Guide. 7. For installs from version 3.4x to later versions, copy the Properties folder from your backup to <path>/webnow/properties. The Properties folder contains user preferences and user queries. 8. Configure your settings using one of the following actions: For installs from version 6.2.x or earlier, compare the web.xml file in your backup to the new WebNow.settings file and copy the settings from the older file to the new one if necessary. For installs from version 6.3, compare the WebNow.settings file in your backup to the new WebNow.settings file and copy the settings from the older file to the new one if necessary. 9. Start the web application server. After verifying that ImageNow is successfully installed, you can safely remove the backup directory as needed. Updating ImageNow Forms Server If you updated ImageNow Forms Server from version 6.4.x to 6.6.x, you must move the imagenowforms.xml file from your web application server folder to your \inserver6\etc folder. Run the installer as shown in the ImageNow eforms Forms Server installation instructions. Important When you perform an upgrade from an older version to a newer version number, Perceptive Software recommends testing forms in a test environment before implementing in a production environment. Version 6.5 includes enhanced features that make this testing step mandatory if you created customized worksheets on any version previous to 6.5.x. If an error occurs on the form, contact Product Support. Page 24 of 49
Updating Business Insight Review the product readme for information about enhancements and changes for Business Insight. For installation information, refer to the Business Insight Installation Guide located on the Perceptive Software website at www.perceptivesoftware.com. Business Insight 6.6.x is only compatible with ImageNow Server 6.6.x. When you update to version 6.6, all the reports created by your report author remain intact. Upgrading to 6.6 of Business Insight requires you to upgrade to IBM Cognos 8.4.1 server. To upgrade an existing version of Business Insight with the latest version, complete the following procedures on the computer where Business Insight is installed. Before updating your ImageNow Server and Client environments, you should back up your report library. When you update to Business Insight, version 6.6.x, any user with the Manage Report Authoring privilege has the ability to copy and rename reports. Any user with the Manage Reports privilege has the ability to delete reports and folders of reports. 1. Download the 6.6 set-up kit to a temporary directory. 2. To export your Report Library for back up purposes, complete the following substeps. 1. Open an Internet Explorer web browser and access the following URL, where [host name] represents the name of the Business Insight server computer. http://[host name]/cognos8 2. Log in to the web interface. 3. From the Launch menu, select IBM Cognos Administration. 4. On the Configuration tab, in the left pane, click Content Administration. 5. In the Administration toolbar, click New Export and complete the following substeps. 1. Enter a name, an optional description, and a screen tip for the report library archive and then click Next. 2. Under Deployment method, select any reports you want to import into Business Insight 6.6 and click Next. Note If you import a report from Business Insight 6.5 that shares a name with a report from Business Insight 6.6, the imported report overwrites the newer report. 3. Under New archive, verify the name of the archive. 4. Optional. To password protect the archive, select the Encrypt the content of the archive check box. 5. Click Next. 6. If you opted to password protect the archive, enter the encrypted password and click OK. 7. Verify the export details and click Next. 8. Under Action, select Save and run once and then click Finish. 9. Verify the export details and click Run. 10. Click OK. 6. Access the [drive]:/program Files/cognos/c8/deployment directory. 7. Copy the archive you created to another file location. 3. In Internet Information Services (IIS), stop the default website. 4. To uninstall Business Insight, complete the following substeps. Page 25 of 49
1. From the Windows Control Panel, select Add and Remove Programs. 2. In the list, select ImageNow Business Insight and click Remove. 5. To uninstall the Cognos 8.4.0 server, complete the following substeps. 1. Access the [drive]:/program Files/cognos/c8/uninstall directory and double-click Uninstall IBM Cognos 8. 2. In the Uninstall Wizard, under Install Language Selection, select your language and then click Next. 3. Under Select the packages you want to uninstall, select IBM Cognos 8 Business Intelligence Server and click Next. 4. When the wizard completes, click Finish. 6. Delete the [drive]:/program Files/cognos directory. 7. To install the 6.6 version of Business Insight, complete the following substeps. 1. Open the 6.6 set-up kit and double-click the ImageNowBI_Setup.exe file. 2. Run the installer according to your operating system and DBMS. Refer to the Business Insight Installation Guide available in the Product Documentation tab in the Customer Portal on the Perceptive Software website for more information. 3. When the BI Integrator folder opens, close the folder. You do not need to run the Business Insight integration utility. 8. In Internet Information Services (IIS), start the default website. 9. To import the exported archive into your new report environment, copy the exported archive to the [drive]:/program Files/cognos/c8/deployment directory and complete the following substeps. 1. Log into Cognos Connection with your administrator account. 2. In the IBM Cognos Administration section, on the Configuration tab, click the Content Administration link. 3. Click the New Import button and follow the steps outlined in the New Import wizard. 10. To import the new report library, complete the following substeps. 1. Open an Internet Explorer web browser and access the following URL, where [host name] represents the name of the Business Insight server computer. http://[host name]/cognos8 2. Log in to the web interface and then, from the Launch menu, select IBM Cognos Administration. 3. On the Configuration tab, in the left pane, click Content Administration. 4. Select the Business Insight Nightly Build check box and, in the Actions column, click the Set Properties button and then verify the following conditions. 1. On the Import tab, verify that all the folders in the Public folders content list are selected. 2. Under Options, verify that the Include report output versions check box is selected, and under Conflict resolution, that the Keep existing entries option is selected. 3. Click OK. 5. Select the Business Insight Nightly Build check box and, in the Actions column, click the Run button. Page 26 of 49
6. On the update verification page, under Report specification upgrade, select Upgrade all report specifications to the latest version and click Run. 7. If prompted, click OK. 11. Run the INTool commands to update the database enumerations and populate the calendar table. 12. For all reports created or modified by your report author, validate the report specification. For more information on report validation, refer to the "Validate a report" topic in Business Insight Report Studio Help. Updating Fax Agent When you update Fax Agent from a previous version, ensure you back up the btcall.cfg and the callctrl.cfg located in the inserver6\brooktrout\config directory. Place these files in a temporary directory away from the InServer6 directory. Run the installer according to the steps in the Fax Agent Installation and Setup Guide. If the.cfg files are missing, replace them with the files you backed up and place them in the inserver6\brooktrout\config directory. Updating Output Agent on UNIX To update Output Agent on Windows, run the installer according to the Output Agent Installation and Setup Guide. To update Output Agent on UNIX, perform the following steps: 1. Source the setenv.sh file to set up your environment variables. For example, if you are using /bin/bash, the command to source the file is../setenv.sh. 2. From /inserver6/bin, stop the Output Agent service. To stop services:./inserveroutput stop 2. Copy the inserveroutput.ini file from the /inserver6/etc directory to a backup directory. 3. To download the latest version of Output Agent, perform the following substeps: 1. Go to the Perceptive Software website at www.perceptivesoftware.com, click Customer Portal, and then click Downloads. 2. In the Downloads page, in the right pane, in the Content section, click the Clear Search link. 3. In the Downloads page, in the left pane: 1. Expand Platform and select your UNIX platform (Solaris, AIX, or Linux). 2. Expand Product and select Output Agent. 3. Expand Product Release and select 6.6. 4. In the Downloads page, in the right pane, select the check boxes for all of the following files: The latest build of the Output Agent, shown by the highest Build Number. AIX and Linux Supporting Files. 5. Click the Download button and then save the files to a temporary directory on your computer. 4. From /inserver6, gunzip and tar the ImageNow_Output_Agent_<version#>_<build#>_for_<OSName> installer file. This is the format of the installer file, where <version#> is the version number, <build#> is the build number, and <OSName> is the name of the operating system. gunzip ImageNow_Output_Agent_VERSION#_BUILD#_for_PLATFORM.tar.gz tar xvf ImageNow_Output_Agent_VERSION#_BUILD#_for_PLATFORM.tar 5. From the inserver6 directory, issue the following command to change ownership: Page 27 of 49
chown R root:bin * 6. Compare the previous INI files from your backup copy of the /inserver6/etc directory with the new INI files in /inserver6/etc. The Windows installer automatically adapts your previous settings to the new settings; however, the installer overwrites any custom comments, settings, or notes that you might have previously added. Alter the new INI files in /inserver6/etc as needed. These changes appear in the "Addendum B: INI Changes by Release" section of this document. 7. Start the Output Agent service by running `pwd`/service_name for all services in the /inserver6/bin directory../inserveroutput -start Page 28 of 49
Addendum A: Database Changes by Release Use the following Addendum to understand the database changes required by each release. The incremental SQL scripts listed in the steps above perform these changes in your database. Carefully review the incremental database script for to understand the details of the changes. Database Changes Incremental- 801_TO_BUILD814 Description of Changes For all databases: IN_PROJ.PROJ_NAME is now varchar(128), up from varchar(40) IN_SUBOB_ANNOT_FONT.FONT_FACE_NAME is now varchar(40), up from varchar(16) For Oracle 9i and 10g: In addition to the two changes above, there is an Index Pack that is part of the incremental which will increase performance. Incremental- 814_TO_BUILD856 Incremental-856_to_46 Incremental- 6.1.0.46_to_6.1.0.75 For all databases: There are several new indexes, and the columns listed below have increased in size: IN_SUBOB_ANNOT ACTION_VALUE varchar2(768) (from varchar(40)) IN_SUBOB_TEMPL_PROP PROP_VALUE varchar2(768) (from varchar(256)) IN_USR_KEY For all databases: ENC_PRIVATE_KEY varchar2(256) (from varchar(128)) IN_BATCH_PAGE.REQUIRES_FULL_REC --> SUBMIT_TO_CONTENT REMOVED IN_DOC.CONTENT_ID ADDED IN_DOC.CONTENT_STATUS NEW TABLE: IN_DOC_CONTENT For all databases: New Column: IN_SUBOB.COPYABLE New Column: IN_SUBOB_SIG.SID_ID Non-Required Column (now can be NULL): IN_SUBOB_SIG.SIG_IMAGE_ID New Column: IN_USR_PROC_CTRL.SESSION_ID Page 29 of 49
Database Changes Incremental- 6.1.0.75_to_6.1.0.110 Description of Changes For all databases: New Column: IN_ERM_DOC.ITEM_COUNT New Column: IN_LIC_OVERDRAFT.OVERDRAFT_NUM IN_SIG: Removed Column: IS_VOIDED New Column: SIG_STATUS New Column: SIG_STATUS_TIME Removed Column: VOID_TIME New Column: IN_WF_ITEM_QUEUE_HIST.VISIT_COUNT New Column: IN_WF_ITEM_QUEUE_HIST_ARCH.VISIT_COUNT Incremental- 6.1.0.110_to_6.1.0.138 Incremental- 6.1.0.138_to_6.1.0.192 For all databases: New Column: ITEMS_SKIPPED column to IN_UPGRADE_TABLE_STATS table New Index: IN_WF_ITEM For all databases: new table IN_EXTERN_MSG new table IN_EXTERN_MSG_PROP two new columns on IN_LIC table constraints/indexes on new tables altered column IN_DOC.CONTENT_STATUS to NOT NULL added table IN_FAX_RECIPIENT created index FAX_REC_IDX02 ON IN_FAX_RECIPIENT created index VERSION_IDX03 ON IN_VERSION created unique index WF_I_Q_H_A_IDX02 ON IN_WF_ITEM_QUEUE_HIST_ARCH modifying IN_SCRIPT.SCRIPT_NAME column to varchar(128) from varchar(40) created unique index WF_I_Q_H_A_IDX02 ON IN_WF_ITEM_QUEUE_HIST_ARCH modifying IN_SCRIPT.SCRIPT_NAME column to varchar(128) from varchar(40) Page 30 of 49
Database Changes Incremental- 6.1.1.289_to_6.1.4.25 Incremental- 6.1.3.51_to_6.1.4.25 Incremental- 6.1.4 INDEX PACK Description of Changes For all databases: widened WORKING_NAME column for table IN_PHSOB to varchar(260) from varchar(128) added column PRESERVE_CODE_VALS to IN_SUBOB_ANNOT table. For all databases: added index DOC_IDX9 added index PROJ_IDX_09 For all databases: added index INST_PROP_IDX_03 added index INST_PROP_IDX_04 Page 31 of 49
Database Changes Incremental- 6.1.4.26_to_6.2.0.527.sql Description of Changes For all databases: IN_USR - add USR_PREFIX column IN_USR - add USR_SUFFIX column IN_PROJ - change PROJ_TYPE_ID NOT NULL IN_PROJ - PROJ_NAME NOT NULL New IN_PROJ indexes IN_VERSION - add SIG_STATUS column IN_DRAWER - add SIG_VERIFY_INTERVAL column IN_DOC_TYPE - add SIG_VERIFY_INTERVAL column New tables: IN_LM_SE_WINDOWTEXT, IN_LM_SE_IE, IN_CONTEXT_MAP_ITEM, IN_OUTPUT_PROFILE_EMAIL, IN_OUTPUT_PROFILE_PRINTER, IN_CONTEXT_MAP, IN_LM_SE_HYPERLEARN, IN_LM_APP_PLAN, IN_LM_ELEMENT, IN_LM_SE_MSWINDOWS, IN_LM_SCREEN, IN_OUTPUT_PROFILE, IN_LM_SCREEN_CLIPBOARD, IN_LM_SCREEN_ELEMENT, IN_LM_SCREEN_HYPERLEARN, IN_PROJ_TYPE_LIST_MEMBER, IN_LM_SE_CLIPBOARD, IN_OUTPUT_PROFILE_FAX,, IN_OUTPUT_PROFILE_FILE, IN_PROJ_TYPE_LIST, IN_PROJ_TYPE_LIST Update statements to fix flag types with values in VSL Update statement to populate IN_VERSION.SIG_STATUS column IN_SIG - add HASH_VAL column IN_SIG - add HASH_TIME column IN_SIG - add HASH_MODEcolumn IN_SIG - add CREATION_USR_NAME column New tables: IN_RS, IN_RS_WS_OP, IN_RS_WS_SERVICE, IN_TASK, IN_TASK_COMMENT, IN_TASK_HIST, IN_TASK_HIST_DETAIL, IN_TASK_TEMPLATE, IN_USR_TASK_TEMPLATE_PRIV IN_PHSOB - add FORM_ID column IN_BATCH - add FORM_ID_MODE column IN_BATCH - add FORM_CONFIDENCE column IN_VSL_USR_VAR_CONSTRAINT - add RT_VAR_ID column IN_VSL_VAR_CONSTRAINT_VAL - add RT_VAR_ID column IN_VSL_VAR_CONSTRAINT - add RT_VAR_ID column IN_UPGRADE_TABLE_STATS - add TABLE_NAME column Page 32 of 49 New tables: IN_FORM, IN_LIST, IN_LIST_ITEM, IN_LIST_MEMBER, IN_TASK_ASSIGNMENT, IN_USR_VIEW_PRIV, IN_VIEW, IN_VIEW_COL
Database Changes Incremental- 6.2.0.527_to_6.3.0.119.sql Description of Changes New tables: INUSER.IN_LM_ELEMENT_MACRO, INUSER.IN_MACRO, INUSER.IN_MACRO_SETTING, INUSER.IN_USR_OOO_HIST, INUSER.IN_USR_OUT_OF_OFFICE, INUSER.IN_WF_COMMENT INUSER.IN_WF_CONTAINER, INUSER.IN_WF_ROUTE_DEST_CP Added new indexes and constraints for these new tables. Changes to INUSER: In IN_WF_ROUTE, renamed COLUMN IS_ACTIVE to IS_DEFAULT. In IN_RS_WS, added several columns. In IN_VIEW, added a DEFAULT_ACTION NUMBER column. In IN_WF_QUEUE_ATTR, added a Z_ORDER NUMBER column. In IN_WF_ROUTE_DEST, added a STYLE NUMBER column. In IN_TEMPLATE_SCRIPT, dropped the COLUMN SCRIPT_ID column. Dropped the USER_PROC_CT_IDX02 index. In IN_USR_PROC_CTRL, modified the IP_ADDR VARCHAR2 column. In IN_OUTPUT_PROFILE, renamed the XPKIN_OUTPUT_PROFILE constraint to XPKIN_OP. In IN_OUTPUT_PROFILE_EMAIL, renamed the XPKIN_OUTPUT_PROFILE_EMAIL constraint to XPKIN_OP_EMAIL. In IN_OUTPUT_PROFILE_FAX, renamed the XPKIN_OUTPUT_PROFILE_FAX constraint to XPKIN_OP_FAX. In IN_OUTPUT_PROFILE_FILE, renamed XPKIN_OUTPUT_PROFILE_FILE constraint to XPKIN_OP_FILE. In IN_OUTPUT_PROFILE_PRINTER renamed the XPKIN_OUTPUT_PROFILE_PRINTER constraint to XPKIN_OP_PRINTER. In IN_PROJ_TYPE_LIST, renamed the XPKIN_PROJ_TYPE_LIST constraint to XPKIN_PTL. In IN_PROJ_TYPE_LIST_MEMBER, renamed the XPKIN_PROJ_TYPE_LIST_MEMBER constraint to XPKIN_PTLM. In IN_TEMPLATE_SCRIPT, dropped the FK_TS_SCRIPT_ID constraint. Renamed the PROJ_TYPE_LIST_IDX02 index to PTL_IDX02. Page 33 of 49
Database Changes Incremental- SS_6.3.0.119_to_6.4.1.4.sql Description of Changes New tables: IN_APPROVAL, IN_APPROVAL_DEF, IN_APPROVAL_DEF_USR, IN_APPROVAL_RESPONSE, IN_CAPTURE_IP_FILTER, IN_CAPTURE_PROFILE, IN_CAPTURE_PROFILE_CLIENT, IN_CAPTURE_SOURCE, IN_CAPTURE_SOURCE_FILE, IN_CAPTURE_SOURCE_SCANNER, IN_CD_CLASS, IN_CD_RESULT, IN_CD_RUN, IN_CLASS_REL, IN_DEVICE_KOFAX, IN_DEVICE_PIXEL, IN_DEVICE_TWAIN, IN_IMAGE_PROC_FILTER, IN_IP_FILTER_PROP, IN_KOFAX_ADV_PROP, IN_NODE, IN_RT_ACTION_ACCESSION, IN_RT_ACTION_OFFLINE_TRANSFER, IN_RT_ACTION_ONLINE_TRANSFER, IN_RT_APPROVAL_DEF, IN_RT_AUTHORITY, IN_RT_HOLD, IN_RT_HOLD_APPROVAL, IN_RT_HOLD_COMMENT, IN_RT_HOLD_OBJ,IN_RT_HOLD_REASON, IN_RT_ITEM,IN_RT_ITEM_APPROVAL, IN_RT_OFFLINE_LOC, IN_RT_PATH, IN_RT_PATH_ITEM, IN_RT_PATH_QUEUE, IN_RT_PHASE,IN_RT_PHASE_QUEUE, IN_RT_POLICY, IN_RT_POLICY_AUTHORITY, IN_RT_POLICY_COMMENT, IN_RT_POLICY_OBJ, IN_RT_POLICY_OBJ_TYPE, IN_SCAN_DEVICE,IN_TIMING_DATA, IN_TIMING_PARAM, IN_TIMING_REPORT, IN_TIMING_SUMMARY, IN_USR_CAPTURE_PROFILE_PRIV, IN_USR_CAPTURE_SOURCE_PRIV, IN_VIEW_SUMMARY_COL, IN_WF_CONTENT_QUEUE, IN_INSTANCE_REL_TEMPTBL Added new indexes and constraints for these new tables. Dropped an index in IN_PHSOB Altered tables in IN_CLASS, IN_DOC, IN_DOC_TYPE, IN_ELEMENT, IN_FOLDER, IN_PROJ, IN_PROJ_TYPE, IN_PROP, IN_TASK_TEMPLATE, IN_USR, IN_VIEW, IN_WF_CONTAINER, and IN_WF_QUEUE Created indexes in IN_DOC_TYPE,IN_PHSOB, IN_PROJ_TYPE, IN_PROP, and IN_USR Page 34 of 49