Ask the Expert: Best Practices – 7.x Installation and Upgrade

During a new install there is a settings.ini setting that can be very helpful.

RequireLatestClient - Ensures that the client module version matches the version of InputAccel Server that is running.

Setting this value to 1 disallows any client modules to connect that use a client DLL prior to the release of the InputAccel Server. Typically this only allows compatibility enforcement of major product revisions, for example, requiring 7.0 client modules with InputAccel Server 7.0. Setting this value to 0 enables an older or current client module version to connect to the InputAccel Server.

Did you know...

Sometimes when attempting to apply a CAF file to a new install, the server ID and Serial number will remain 0 and thus appear that the CAF file did not ‘take’. It did not.

The serial should immediately change to reflect the CAF number that was applied.

Resolution: To get CAF file to apply properly, close admin and add http://127.0.0.1 as a trusted site in Internet Explorer. Captiva Administrator leverages IE libraries and in some environments with tighter

security, adding localhost as a trusted site will correct this issue.

To avoid potential security risks, when creating the InputAccel Database an SQL Server user account with restricted access should be created, rather than using a system administration account.

The SQL Server user account must be configured with the following:

• The user account must use SQL Server authentication (can be changed to Windows authentication in 7.1 and 7.5 post-installation).

• The Default database must be set to the InputAccel Database.

• The user account must be mapped to the InputAccel Database and the database role membership

must be set to Public.

• Grant the following permissions to the InputAccel Database:

— Connect

— Delete

— Execute

— Insert

— Select

— Update

Hi Guys,

We recently upgraded to Captiva 7.1 from 6.0. But we still using the deprecated modules in 7.1. Coming to Captiva 7.1 instead of IndexPlus we need to use Captiva Desktop. But from the IndexPlus module we are connecting to documentum for data lookup with the help of these dll’s(iadctmval4.dll and iadctmval5.dll).

What are the best approaches for this in Captiva 7.1 or later versions is there way where we can connect to documentum from Captiva Desktop for lookup. In Captiva 7.1  from the Captiva Designer  there is a configuration settings to connect to  database, similarly is there way where we can connect to documentum database through DFC.properties and get the lookup data into Captiva Desktop.

Thank you,

Bala.

Hi Bala,

For 7.5 we have made it easy to create a Documentum connection using Captiva Designer.  Check out the following topics in the Captiva 7.5 Help to guide you:

Captiva Designer Guide > Preparing a Capture System > Defining Connections > Creating a Documentum Connection

Captiva Designer Guide > Preparing a Capture System > Defining Queries > Adding a Query > DQL Query Statement

As for 7.1, unfortunately this functionality wasn't added yet, so you will need to write scripting to connect to Documentum from Captiva Desktop.

Thanks,

Stacie

Thank you for the update, this helps  us a lot  and we can plan accordingly.

Is there any sample or document that talk about writing script for connecting documentum from Captiva Desktop it will be a good starting point for us for implementing this in Captiva 7.1 until we upgrade to Captiva 7.5.

Thank you,

Bala.

Hello Bala,

Since this is a post installation and scripting question, I would encourage you to open an SR with support for further investigation on Captiva Desktop and to get any sample script.

We hope to hear more from you on installation and upgrade!

Thank you,

Shaishiv

Did you know that the capture flow file (XPP) format is updated in version 7.5?

Whilst Capture Flow Designer automatically converts Capture Flows to the new version, it is recommended to follow the procedure below in order to mitigate against any potential problems:

- Ensure you have a backup copy of the XPP files

- [Optional] Prepare separate (standalone) copies of any meaningful script code from AssemblyInfo.cs

- Upgrade your system

- Open the old Capture Flow (there will be a version warning icon displayed)

- Save as new (the save dialogue is displayed automatically)

- Compile the new Capture Flow and verify new event handlers (BatchDelete, BatchError, StepError) were added to script code

- [Optional] Restore saved code from AssemblyInfo.cs (use _Global.cs)

- Upgrade/Install process on test server

- Remove the old Capture Flow

Please check out the white papers on the support site notably this one:

https://my.syncplicity.com/share/vvewdcza2fzhspt/Combining%20Scripting%20APIs%20to%20Develop%20Advanced%20Functionality%20in%20Captiva%20Desktop

Did you know that Captiva Capture 7.5 Server was improved as a 64-bit application? This means higher performance enabling more batches to be loaded in memory and also larger batches.

As part of the move to 64-bit the Server parameter BatchMaskAddressSpaceK should be set to Max Physical Memory - .5 GB. For e.g., for a 16 GB memory set BatchMaskAddressSpaceK to 15.5 GB.

Only batches created from a 7.5 XPP run in 64-bit mode. Otherwise, all batches created prior to 7.5 processes, including 7.1 XPP, run in 32-bit mode. However, the Server is backward compatible with 7.1 and older batches/processes.

Upgrade to 7.5 and take advantage of 64-bit performance!

When upgrading Captiva Capture, ensure that you have the following minimum hard disk space free to run the Captiva Capture installers:

- Database and Captiva Capture Server: 4GB

- Captive Capture Client modules: 16GB

These temporary hard disk requirements are necessary because the Microsoft Windows installer backs up the existing files before upgrading to the new version.

One thing to remember is that when configuring a module to run as a service, do not enable Allow service to

interact with desktop. When a module runs as a service, it suppresses its user interface and

does not run properly when configured to interact with the desktop.

Another Expert, Bryan Gard, touched on this but did you know that there is a new distributed capture client, Captiva Web Client, that was released in Captiva Capture 7.5 and will be our long term remote capture?

Captiva Capture Web Client provides the following features:

• Captures paper documents from scanners and imports computer files.
• Enhances images to improve recognition results.
• Enables rearranging pages within and between documents.
• Identifies documents so that they are routed to the appropriate data extraction processes.
• Enables operators to change document identification (also known as Document Types).
• Enables data extraction from identified documents
• Assists in simple field validation using patterns.
• Enables operators to check, correct, and finalize extracted data.

Upgrade to 7.5 and take advantage of new easier to use distributed capture Captiva Web Client!

Hello,

We are in our second and final week of "Ask The Expert" event. I encourage everyone to actively participate and take advantage of this event.

Please feel free to reach out to us should you have any questions around "Best Practices - 7.x Installation and Upgrade".

Shaishiv