AccuRoute^® Server v5.1.1 Readme

Product: AccuRoute v5.1.1
Release date: May 2017
Version: 052317 1520

Introduction

The AccuRoute v5.1.1 release includes the following new features:

• New FileBound Connector

• New Support for SQL Always-On

• New Support for the SSL/TLS v1.2 Protocol

• New Device Support

This Readme also includes the following sections:

• Installation Instructions

• Upgrade Instructions

• Resolved Issues

• Limitations

New Features

New FileBound Connector

The AccuRoute v5.1.1 release introduces the FileBound Connector for integration with FileBound by Upland. This connector supports all standard DMS connector features, including Default Profiles, Distributions, and Routing Rules. With this connector, for example, you can scan documents to FileBound from an MFP device using either a Routing Sheet or a Personal Distribution that identifies FileBound as the recipient.

For documents that have been OCR'd, the system will automatically store the OCR'd text in the FileBound document's FullText property for search and indexing.

Note: The FileBound Connector requires a DMS license.

Installation and Configuration

Before adding and configuring the FileBound Connector, you must already have a FileBound project (with fields, dividers, and separators) configured.

To create and configure the FileBound Connector on the AccuRoute Server:

1. Right-click Connectors in the console tree and select New AccuRoute connector for > FileBound. The Display Name page appears.

2. FileBound on the Server appears as the default name. Accept this or type a friendly name for this connector in the Name text box and click Next.

3. The Congratulations page appears. Click Finish.

4. The Properties for FileBound on the Server page automatically opens. Enter a Rest EndPoint URL (the FileBound URL address) and the associated Username and Password.
   The FileBound Rest Endpoint URL  would come from your instance of FileBound.

5. Click OK.

To set up the default profile for the FileBound Connector:

1. In Properties for FileBound on the Server, go to the Advanced tab.

2. In the Default Profile Information section click the Create button. The Create Default Profile screen appears.

3. Select the Project of interest and click Next.

4. Enter the appropriate File values and click Next.

5. Select a Divider and/or Separator and click Finish.
   
   A default profile for the FileBound Connector now exists. This default profile can now be used by the Server Rules engine.
   For more information on configuring Rules, refer to the AccuRoute Administrator Online Help.

With the FileBound Connector configured on the AccuRoute Server, you can also enable access for AccuRoute Desktop users in the Administrator Group Properties, as with other DMS providers.

AccuRoute Desktop users need to add the FileBound Connector as a recipient.

To add the FileBound Connector as a recipient in AccuRoute Desktop:

1. Open the AccuRoute Desktop.

2. Select Tools > Configure DMS > FileBound. The Configure FileBound screen appears.

3. Enter the same credentials (Rest EndPoint URL and associated Username and Password) as used in the steps above.

4. Click OK to finish.

New Support for SQL Always On Availability Groups

The AccuRoute v5.1.1 release adds support for using the AccuRoute Server in a SQL Always On Availability Group environment.

Note: The relevant SQL Always On Group must be configured before installing the AccuRoute Server.

After installing the AccuRoute Server, the Server Administrator needs to update the database DSN to allow the configuration to work with SQL Always On functionality.

To configure the AccuRoute Server for SQL Always On:

1. Complete the configuration of your SQL Always On Availability Group.

2. Install AccuRoute, selecting the Primary SQL server for the database.

3. To change the DSN settings for the Primary SQL server, navigate to this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Omtool\Genifax\Current Version\DSN

4. Edit two sections of the DSN as follows:

• Change the Driver= section to {SQL Server Native Client 11.0}
  

• Change the Server= section to TCP:YOURLISTENERHERE, YOURPORTNUMBER

For example:

Driver={SQL Server Native Client 11.0}; Server=TCP:TestAccuListner, 1433; Database=AccuRoute; Trusted_Connection=Yes

This change needs to be made on the following four DSN entries:

• ActivityDB

• ArchiveDB

• DB

• DBMETADATA

And depending on your configuration, this change may also need to be made for these DSN entries within the Administrator:

• Billing

• Archive

• Volume Lists

• Audit

For more information about the AccuRoute Server installation process, refer to the AccuRoute Server Installation and Integration Guide.

New Support for the SSL/TLS v1.2 Protocol

The AccuRoute v5.1.1 release provides support for using the SSL/TLS v1.2 Protocol.

To use TLS v1.2 in your environment, you will need to acquire a certificate with the appropriate signature algorithm. You will also need to enable TLS v1.2 on the AccuRoute Server and on the relevant HP devices. You may also need to update relevant DSN entries on the AccuRoute Server.

Note: The AccuRoute v5.1.1 release supports SSL/TLS v1.2 only on Windows 2012 and 2016.

To enable TLS 1.2 on the HP CR Server:

If you were previously using TLS v1.0 or v1.1, when you are turning those off and selecting TLS v1.2 instead, you also need to edit the AccuRoute Server's DSN entries to point to the correct  SQL Server driver.

1. To change the DSN settings for the SQL Server driver, navigate to this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Omtool\Genifax\Current Version\DSN

2. Edit the Driver={SQL Server} section of the DSN to Driver={SQL Server Native Client 11.0}

For example:

Driver={SQL Server Native Client 11.0}; Server=TCP:TestAccuListner, 1433; Database=AccuRoute; Trusted_Connection=Yes

This change needs to be made on the following four DSN entries:

• ActivityDB

• ArchiveDB

• DB

• DBMETADATA

And depending on your configuration, this change may also need to be made for these DSN entries within the Administrator:

• Billing

• Archive

• Volume Lists

• Audit

Enabling TLS 1.2 on your HP device:

Sign in to the device via your browser and:

• For FutureSmart 3 devices, go to the Networking tab, select Mgmt. Protocols, and in the Web Mgmt. Secure Communication section, select the TLS 1.2 check box. Click Apply.

• For FutureSmart 4 devices, go to the Networking tab, select Secure Communication, and in the SSL/TLS Protocol section, select the TLS 1.2 check box. Click Apply.

New Device Support

The AccuRoute v5.1.1 Embedded Device Client now supports the  following HP devices:

Note: The user experience with FutureSmart 4 devices will be consistent with previously released FutureSmart devices.

Installation Instructions

Consult the AccuRoute Server Installation and Integration Guide for system requirements and step-by-step installation instructions. You can use this update to install AccuRoute v5.1.1 directly, without first installing v5.1.

Upgrade Instructions

AccuRoute v5.1.1 supports upgrading from AccuRoute v5.x environments. For instructions on how to upgrade from a legacy AccuRoute environment, consult the AccuRoute Server and Clients Upgrade Guide.

Note: Before upgrading, you need to disable the User Account Control (UAC), allowing the installation process to retain permissions in case a system reboot is required. The UAC needs to be re-enabled after the installation.

To disable the User Account Control:

1. Go to the Control Panel > User Accounts > Change User Account Control Settings.

2. In the User Account Control Settings, move the slider down to Never notify and click OK.

3. Reboot your system, and then begin the AccuRoute upgrade installation.

4. When the upgrade is complete, return the UAC to its original setting.

Note: At the start of the AccuRoute v5.1.1 upgrade process, the system initially asks for the user service account and password before proceeding with the upgrade installation.

For a list of all documentation related to AccuRoute v5.1.1, including hardware, software and other client requirements, consult the AccuRoute v5.1 documentation page.

Resolved Issues

The following issues were found during testing and are resolved in AccuRoute v5.1.1:

Limitations

The following limitation exists in AccuRoute v5.1.1:

Release Notes

For details on all recent features, enhancements, resolved issues, and known issues, consult the Release Notes for AccuRoute v5.1.

Additional Information

Technical articles in the Omtool Knowledge Base provide valuable troubleshooting information and describe issues reported after a release.

To access the Omtool Knowledgebase:

1. Go to http://www.omtool.com/support.

2. Log in using your customer number.

3. Click Knowledge Base.

4. Search by keyword or article ID, or browse by product.

© 2017, Omtool, Ltd. All Rights reserved.