Hello Anthony Ford -
eStatus is part of eInput which is End of Life. Therefore there are no plans to update this solution any further. Per the support site, here are the relevant dates for this products support lifecycle:
Primary support ends Dec. 31, 2015
Extended Support ends Dec. 31, 2016
In lieu of this, I would encourage you to check out the new Captiva Web Capture solution that debuted with 7.5. It is not a 1 for 1 replacement of eInput but does offer some very compelling features that in my opinion are game changing; things like Real-Time Image Processing and Advanced Recognition services.
Whats the best practices for maintaining remote capture while on 7.1 past Dec 2015? Captiva 7.1 would still be in primary support, but eInput is not. Is Captiva Web Capture available for 7.1?
Hi Micah -
Re: What are the best practices for doing image assignments in CaptureFlow Designer? In IPP development, even modules like ODBC required an InputImage. What modules do and do not require such an assignment in 7.1?
Currently this forum is geared toward installing and upgrading Captiva Capture. Your question seems to fall more on the configuration side of things (post install/upgrade). I would recommend posting this question to the main Captiva User Community Forum or open up a SR with Support.
I just want to add that it is always recommended to download the latest Release Notes and Help Files for the version you are interested in learning more about. These can only be found on the Support portal. For example, the 7.1 release notes have been updated 10 times since the initial release of the software to include items such as new DBS version support. There is a revision history at the top of each release notes. It is not enough to trust the release notes and documentation that are part of each installer because the installer is not updated when there are doc fixes/updates.
Micah – Re: Whats the best practices for maintaining remote capture while on 7.1 past Dec 2015? Captiva 7.1 would still be in primary support, but eInput is not. Is Captiva Web Capture available for 7.1?
Correct. eInput goes off of primary support before 7.1 goes off of primary support. The EOL notice for eInput was sent out in April of 2015 and is also available on the support portal. Captiva Web Client (CWC) is only available for 7.5 unfortunately.
It is our recommendation to contact your Account Manager to discuss options for 7.1 which, in short, can include obtaining extended support for an additional year or move to a partner solution that is supported on 7.1:
Please keep in mind that the initial release of CWC allows users to Scan and Index in the same interface, at scan time. This has its benefits as the OCR can be set to occur in real time while scanning is taking place using the RESTful services component in 7.5. The results are delivered back to the browser in a matter of seconds. There currently does not exist an option to perform web-based indexing downstream at a later point in time. If batch indexing is required later in the process, then Captiva Completion will be needed for that task.
Did you know, before installing IA Server the machine name of the InputAccel Server must not be longer than 15 bytes; otherwise, client machines will be unable to connect. Also, EMC recommends disabling antivirus software and Data Execution Prevention (DEP), and to close any open programs before installing the InputAccel Server.
Please feel free to post your questions on this forum around 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:
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.