Starting with ILINX Capture v6, the Release configurations are stored within the ILINX database. In ILINX Capture v5x, the ILINX Release configurations were stored in XML files on a disk. ILINX Capture called ILINX Release using a SendAndReceivedReply IXM. The change to store the settings within the ILINX database is very useful for a number of reasons: Release settings are part of the batch profile allowing for simpler migrations between environments, Release is much easier to configure, all configurations are in the database, etc. However, this change can create some extra work when upgrading from ILINX Capture 5x to ILINX Capture 6x. Because of the different architecture, ILINX Release needs to be completely reconfigured for the existing batch profiles. In addition, the Release XML doesn’t change, but there is a shortcut that can be taken. After you have upgraded ILINX Capture to v6, you’ll notice a new IXM in the palette: 
The existing ILINX workflow will likely have a SendAndReceiveReply IXM on the map that the 5x version of ILINX Capture used to call ILINX Release. Most likely, it would look like this:
To configure ILINX Release for ILINX Capture 6x, the SendAndReceiveReply IXM will need to be removed from the map and a Release IXM must be dragged onto the workflow map in its place. Once the new Release IXM is on the map, it will need to be configured. This is where the shortcut can be taken. Instead of having to manually enter in the correct URLs, map the metadata values, and configure any other settings, do this:
Configure and save Release with some place holder settings: I normally leave the settings at default and enter in the bare minimum:
Once ILINX Release configuration is saved and the workflow map is published, there will be a new entry in the ILINX Capture database Capture WorkflowAppSettings table. The CaptureWorkflowAppSettings.SettingsXML column is where the Release configuration is stored. Now it’s time to update the SettingsXML column with the XML from the ILINX Release 5x job settings file. The Release job should be on the ILINX Release 5.x server at c:ProgramDataImageSourceILINXReleaseSettingsJobs. The only caveat here is to be sure to place single quotes around the XML content. Here is what the SQL update statement would look like:
update [ILINX CAPTURE DATABASE].[dbo]. [CaptureWorkflowAppSettings]
set SettingsXml = ‘COPY AND PASTE ALL TEXT FROM 5.4 OR PRIOR RELEASE JOB SETTINGS FILE HERE’
where settingsID = ‘APPROIATE ID HERE’
Following this procedure can save some time if upgrading an ILINX Capture 5x system that has a lot of batch profiles. A lot of the time spent on the upgrade could be in the ILINX Release configuration. If I was upgrading a system with only a few batch profiles, I would probably just reconfigure them. If I was upgrading a system with a lot of batch profiles, I would go through the above steps to save some time.
John Linehan
Sr. Systems Engineer
ImageSource, Inc.
There’s nothing quite like logging in to a customer’s system first thing Monday morning only to be greeted with this:
I discovered this when I wasn’t able to log into the customer’s ILINX Capture implementation. The logged error (failure to locate the SQL Server) led me to take a look at the SQL Server’s configuration to confirm that its service was not running on either node of the cluster, and the error I got when trying to start that (a clustered resource could not be activated) led me to check on the clustered resources themselves.
Continue reading
ImageSource was the privately contracted vendor for a California County Assessor’s Office that embarked upon a major project designed to create a paperless work environment. The project processed and imaged 25 million pages of file documents. Documents were scanned at the rate of 125 images per minute, 8 hours a day. The County also implemented day-forward imaging rather than filing incoming paper documents. The entire project was completed in approximately one year.
When researching Enterprise Content Management capture projects, the question of handwriting recognition comes up again and again — and many people aren’t sure what to expect. More commonly, their expectations are unrealistic. They think there is no hope at all, ever. On the other end of the spectrum, some think that tiny fevered cursive scribblings from a rushed meeting can be scanned (or even faxed) and read with accuracy. In helping people think about their forms and the viability of capturing handwriting, I have a few simple guidelines to consider which seem to apply in a majority of cases.
At our company we have a lab environment that we utilize to replicate a large number of our customer implementations. This environment runs on Virtual Servers in order to keep the cost and maintenance down for our organization. Here are a few of the many advantages for us to maintain this type of environment for our customers;
One issue that does arise on occasion is the ability to reproduce an issue that is occurring in a customer environment where we don’t have the underlying hardware or software. This can be due to a proprietary product the software is interfacing with or a solution that is not realistic for us to manage internally. One such case is with OpenText RightFax (formerly Captaris RightFax). We have customers with all types of configurations from analog and digital fax boards to fax over IP (FOIP), and it doesn’t make sense for us to maintain all types of solutions.
The good news is that RightFax provides an “out of the box” capability to setup a RightFax solution without requiring fax boards or phone lines. The power of this functionality is that it allows you to send and receive faxes internally to your RightFax system in order to simulate the real world functionality of the software. This capability is referred to as running RightFax in simulation mode. The following information takes you through the steps to enable simulation mode on your RightFax v9.4 (older versions of the software also have simulation mode, but the configuration is slightly different) system:
