Wednesday, February 29, 2012

Couldn't create DC_P8 FileNet object error with IBM Datacap Taskmaster Capture

Couldn't create DC_P8 FileNet object


error with Datacap Taskmaster Capture


Abstract


Running FileNet P8 actions with Taskmaster Capture generates the following error:

Couldn't create DC_P8 FileNet object.
ERROR!!! N-2147024894

Cause




Components required for the P8 Export are missing or not registered. These requirements apply to both the 35DIME and MTOM interfaces.


Resolving the problem




To resolve this, verify the following:

  1. There is only one version of DC_P8_Server.dll on the server.

  2. The dll is registered. To confirm, run the following command. The command will need to be modified if the dll is not in the C:\Datacap\dcshared folder.
    C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe C:\Datacap\dcshared\DC_P8_Server.dll /codebase

  3. Web Services Enhancements (WSE) are installed as shown in Add/Remove Programs.

    • Datacap Taskmaster 8.0.1 Fix Pack 2 and earlier requires Web Services Enhancements 2.0 SP3.

    • Datacap Taskmaster 8.0.1 Fix Pack 3 and newer requires Web Services Enhancements 3.0.



  4. For Datacap Taskmaster 8.0.1 Fix Pack 3 and newer, verify the IBM FileNet P8 Content Engine Client files are installed and correct for the version of P8 that Taskmaster is exporting to. To confirm the client files, check that both of the following:

    • Content Engine .Net API is listed in Add/Remove Programs.

    • FileNet.API.dll is listed in the \Windows\assembly folder.







 

Tuesday, February 28, 2012

Basic form design and capture in IBM Datacap Taskmaster Capture

Basic form design and capture in IBM Datacap


Taskmaster Capture


this post  highlights some of the functionality that Taskmaster has available to assist

in ensuring good form design. This chapter also highlights general guidelines to follow.
PaperGray font
Datacap ships with its own font called PaperGray. This font is in the

C:\Datacap\support\fonts directory.

Forms that are designed with this font allow segregation of handwritten
characters without the use of lines, which can interfere with captured text. This
font allows, through use of the image enhance despeckle function, the ability to
remove the boxes easily and effectively with minimal impact to the written
characters. Although the use of lines enforces character separation, the line
removal process, in some situations, can affect the written characters that we are
attempting to capture.

Notice how the boxes have been removed with minimal impact to the text.
Barcodes
Use dimensional (1D) and two dimensional (2D) barcodes where possible. These
barcodes aid in identifying a document. They can also carry a large amount of
data and, in some situations, all the data you need from the form.
Ideally barcodes must be printed or attached so that they are square with the
page. Barcodes that are attached at extreme angles can be difficult to capture.
Colors
Use of color helps to create appealing looking forms. However, the colors must
be of a specific range that scanners can drop out (that is, removal of the
constrained text box lines that we need).
Most color scanners have a drop-out color that you can specify, which is red or
green. These scanners can perform almost the same output as the PaperGray
font after despeckling.

Some scanners can produce two images simultaneously. One image is a color
image that you can use for export. The other image is a bi-tonal (black and white)
TIFF image, with the color removed that we can use for processing.
Always test the color that you want to use before you print large quantities of
forms to ensure successful drop out.
Use of colored paper for forms can also affect scanning quality.
Fonts
Ideally use a 10–14 sized font to capture data. Smaller or larger fonts can start to
cause issues with the Optical Character Recognition (OCR) engines.
Resolution
The resolution a form that is scanned in can determine the quality of the OCR,
Intelligent Character Recognition (ICR), or Optical Mark Recognition (OMR)
results. A low-resolution image can make some characters illegible to the OCR,
ICR, and OMR engines and cause low confidence or incorrect reads. A higher
resolution, although better quality, can pick up additional marks on the form,
increasing the number of incorrect reads. This resolution also increases the size
of the image that is being stored.
Determine the resolution on a case-by-case basis. However, a general rule is to
use 200–300 dpi. Always use at least 300 dpi for OCR/A.
Layout
Use of constrained text boxes for handwritten recognition is important in
establishing good results. The text boxes help to define the area where text will
reside, the number of characters expected, and potentially the type of character,
that is numeric or alphabetic. It also defines the size of characters that is
required. These text boxes must be of adequate size so that the person who is
completing the form can write legibly. Use the PaperGray font to create
constrained boxes (see “PaperGray font” on page 290).
Try to get the person who is completing the form to use black ink and to write in
clear, well-formed uppercase characters were possible. Therefore, include
instructions in a noticeable area of the form that advise the person completing
the form to follow these guidelines. These guidelines can assist in improving the
accuracy of the ICR engine.
Ensure that OMR check boxes are of adequate size. Check boxes must not be
too small and so close that the person who completing the form selects multiple
check boxes. The check boxes must not be too large so that the person only
selects a small portion of the box.

Where possible, do not to place constrained text boxes or OMR fields close to the
edge of the form. When a form is scanned, a slight misalignment can lead to
parts of the image not scanning correctly, resulting in a loss of data.
Constrained text boxes that contain hint characters can also cause issues when
scanning if the hint character is not properly removed.

Scanning
To obtain good capture results, use a suitable scanner. When scanning from
multiple scanners, the results can differ. The quality from one scanner can be
worse than the quality of other scanners. Poor scanning quality can lead to
poorly recognized documents. Therefore, make sure that scanners undergo
routine maintenance to ensure that they are all working optimally and are not
outputting poor quality images.
As indicated earlier, try to not use color on the forms. Although this practice is
preferred, certain colors that can be dropped out are permissible. Some
scanners can drop out colors at scan time, meaning that they never make it to the
original image.
Separator sheets
When using barcode separator sheets, print the separator sheets on lightly
colored paper. By using lightly colored paper, they can be easily removed from
the scanned batches and reused.

Test any colored paper that you use for separator sheets to ensure that the
background appears white. A light blue or yellow color works well with most
scanners.
If you are using both document and attachment separator sheets, use of a
different color for each sheet allows for easier sorting upon separator removal.
Always use the first generation or barcode separator sheets. Repeated
photocopying of the original causes eventual degradation of the barcode to the
point where it might become unreadable.

Monday, February 27, 2012

APTlayout.aspx does not display properly with IBM Datacap Taskmaster Capture

APTlayout.aspx does not display properly with


IBM Datacap Taskmaster Capture


Abstract


When Taskmaster Web has been configured to use the aptlayout.aspx page, it does not display properly, having grayed out sections and not fitting properly on the screen.

Cause




Aptlayout.aspx was designed for a screen resolution of 1024 x 768. Higher resolutions, particularly ones above 1280 pixels horizontally, will not display properly.


Resolving the problem




Lower the resolution of the desktop to 1024 x 768 or another resolution that displays aptlayout satisfactorily.

Exception has been thrown by the target of an invocation error with IBM Datacap Taskmaster Capture

Exception has been thrown by the target of an invocation


error with IBM Datacap Taskmaster Capture


Abstract


Datacap Studio fails to start, stating that an exception has been thrown by the target of an invocation.

Symptom




The following message box appears:



Title: Studio
Body: application error! Exception has been thrown by the target of an invocation.


Cause




This issue can occur if a necessary font such as Arial is not installed on the workstation.


Resolving the problem




Ensure that all standard fonts are installed on the workstation, to include Arial by confirming it is visible in the %windir%\Fonts folder. If not, install the font.

Wednesday, February 22, 2012

AutoDelete Batches with NENU

AutoDelete Batches with NENU


Abstract


As users process batches, the Taskmaster application’s “batches” folder can become very
large. For many applications, a batch loses much of its value after the Export task copies the
verified data to an export file or database in another location. If you wish, you can create a
NENU ruleset to periodically purge old batches from the application’s “batches” folder and
remove the corresponding records from the application’s engine database.

how to create an AutoDelete ruleset :
• Locate batches completed within a given timeframe (for example, more than five days
ago).
• Delete those batches from the application’s “batches” folder, or move them to an archive
folder.
• Delete the records relating to the deleted batches from the application’s engine database, or
move those records to a separate archive database.
• Generate a log file documenting the results of the process.
You can then schedule the AutoDelete ruleset to run automatically on a scheduled basis (for
more information, see Configure Windows Task Scheduler to Run Ruleset Automatically
(Windows 7, Windows 2008) and Configure Windows Task Scheduler to Run Ruleset
Automatically (Windows 2003)).
AutoDelete Process
When you run a batch through the application workflow, Taskmaster does the following:
• Updates the image files, page data, etc. in the application’s “batches” folder.
• Updates the batch status information in the application’s engine database
IBM Datacap Taskmaster Capture
Copyright © 1994, 2011 Datacap Inc. Page 209
In order to delete old batches from the system, you must remove the information from the
“batches” folder and the engine database. Typically you will move the data to a backup
location:
• You can move the batch folders to any available local drive or network share using the
ProcessMoveBatches action. For an example, see Sample AutoDelete Ruleset.
• You must move the database information to another database with the same format as the
engine database. The easiest way to create the database is to create another Taskmaster
application. You can then move the records use the ProcessMoveDBRecords action. For
an example, see Sample AutoDelete Ruleset.
Sample AutoDelete Ruleset
The sample ruleset found below removes all batches that were completed more than five days
ago (the age is specified in seconds). It uses a separate Taskmaster application called
“BackupApp” as an archive repository for the batches and database records that are removed
from the production application (“APT” in this example).
Each of the actions in the sample AutoDelete ruleset is described in the following table. For
more information, see the section titled Summary of NENU Actions or the embedded help in
Datacap Studio.

AutoDelete
Rule1
Function1
SetApplication(“APT”) ;                                                               ->    Set application to APT
SetUser(“admin”) ;                                                                          ->   Set username
SetPassword(“admin”) ;                                                                ->   Set password
SetStation(“1”) ;                                                                               ->    Set station
SetupOpenApplication() ;                                                            ->   Connect to APT application
QuerySetStatus(“Job done”) ;                                                    ->   Locate batches with status “Job done”
QuerySetAge(“432000”, False) ;                                              ->   Locate batches completed more than 5 days
ago (age is specified in seconds)
ProcessRunSQLQuery()                                                                ->   Execute query
ProcessMoveBatches(“G:\BackupApp\batches”) ;           ->  Move batch folders to backup location
ProcessMoveDBRecords(“BackupApp”, “”, “”,
“”, False, “admin”, “admin”, “1”, True);                                 ->   Move database records to backup application
database

 

“Store” and “Queue to” Properties of a Task Definition in Datacap Taskmaster

“Store” and “Queue to” Properties of a Task Definition 


in Data cap Taskmaster


Abstract


The Store and Queue to properties of a Task Definition determine which operators and workstations 
can process individual batches. (Chapter 5 reviews the impact of these settings.)

The Store property looks forward; the Queue to property looks backwards.
In the Workflow tab of the Taskmaster Administrator, the Queue to and Store fields are drop-down lists
that display their values when you click once on the field. The following table lists and explains these options.

























Store…



Queueueue



Explanation



None” or “Station ID and User ID”



Anywhere, Anytime



The Anywhere, Anytime value allows any operator and Station ID to process batches in the task’s queue – and thus overrides the Station ID and User value assigned to an earlier task’s Store property.



Station ID” or “Station ID and User ID”



by Station”



The task can process only those batches previously processed from the same workstation ID.



UserID” or “Station ID and User ID”



by User”



The task can process only those batches previously processed by the same operator.

































Station ID” or “Station ID and User ID”



by Other Station”



The task can process only those batches previously processed from a different workstation ID.



Station ID and User ID”



by Station and User”



The task can process only those batches previously processed by the same operator, from the same workstation ID.



Station ID and User ID”



by Station and other User”



The task can process only those batches previously processed by a different operator, from the same workstation ID.



Station ID and User ID”



by User and Other Station ”



The task can process only those batches previously processed by the same operator, from a different workstation ID.



Station ID and User ID”



by other Station and other User ID”



The task can process only those batches previously processed by a different operator, from a different workstation ID.




Standard Processing Actions



A Task Definition that includes a processing condition must specify the action the task is to take when it encounters the condition.




The actions include:




None. This is the default, temporary setting you can use as you assemble the task’s response: it makes certain that there is no impact on the processing of a batch.




Branch. This action diverts the batch that the task is processing from the parent job to the task(s) of a child job. When the child job is finished, the batch returns to the parent job. Alert! A workflow can contain a child job hierarchy in which a task in a child job branches to a child job on a lower tier. In this situation, the first child job becomes the parent to the second child job.




�� Most conditions lead to the Branch action.




Jump. This action is a processing shortcut that skips one or more tasks in the workflow, and places the batch in a more advanced position, or in an earlier position. The jump action uses a value in the Steps property to indicate the next task, and does not involve the use of a child job.




Split: The Split action splits one or more documents from the current batch. The task in the parent job creates a sub-batch, adds the document(s) to it and sends the sub-batch to a child job for special processing. While the child job takes care of the sub-batch, the parent job processes the remaining documents in the batch. The child job does not return the sub-batch to the parent job when processing is complete.




Stop: This action terminates Taskmaster’s processing of the batch.




Hub: The Hub action combines features of the Branch and Split actions. Hub splits documents from the batch, adds them to sub-batches, and delivers the sub-batches to various child jobs. When the child jobs have processed the sub-batches, they return to the parent jobs.

Datacap admin Database: migrate_access_to_sql_server_2005

Prerequisites

  • .Net Framework Version 2.0

  • SQL Server 2005 (Express, Standard, Enterprise) installed

  • MS Access (2000,2002,2003) file to be migrated

  • MS Visual J# Version 2.0

  • SQL Server Migration Assistant (SMAS)


Download Links

Assumptions

  • .Net Framework Version 2.0 is installed



  • SQL Server 2005 is installed and remote connections are enabled


How-To

Instructions

  1. Log into your SQL Server 2005 data source

  2. Right click Databases and click “New Database…”

  3. In the “Database Name” field, enter the name of the database that you would like to create and press “OK” when done

  4. Download MS Visual J# Version 2.0 from the download link above

  5. Install MS Visual J# Version 2.0

  6. Download SQL Server Management Services (SMAS) from the download link above

  7. Install SSMA

  8. Start the SSMA application

  9. Create a new project by clicking File > New Project … or click the New Project icon

  10. Give the project a name and location of where to save the project file like Figure 1


Figure 1



  1. To preserve primary key numbering

    1. Click Tools > Project Settings

    2. Click the “Migration” link

    3. Change “Keep Identity” to true see Figure 2




Figure 2 - You can change other settings here to match your desired database environment

  1. Press “Apply” and “OK”

  2. Add your MS Access file to the SSMA project by clicking the “Add Files” graphic in the upper left of your SMAS screen

  3. Under the Access Metadata Explorer, you can now expand the tree to see all of the objects related to this Access file and then click the name of database to make sure all of your objects are highlighted


Figure 3

  1. Add your SQL Server 2005 connection to the SSMA project by click the “Connect to SQL Server” graphic in the upper left

  2. Enter your database server, database name, authentication, user name and password to connect to your SQL Server 2005 instance in Figure 4


Figure 4

  1. You will see in the SQL Server Metadata Explorer, the list of databases available to your SQL Server. Click the name of the database you will be importing the MS Access data into


Figure 5

  1. From your Access Metadata Explorer, click the name of your Access database and then click the “Convert Schema” graphic

  2. Along the bottom, you will see the output panel start outputting the conversions of the schema in Figure 6


Figure 6

  1. From your SQL Server Metadata explorer, expand “dbo” tree and then expand the “Tables” tree and you will see that the converted schema was loaded into the database in Figure 7


Figure 7

  1. Now right-click the “Tables” folder that is above the tblTest table icon and from the options window you will see an option that says “Load to Database” or click the graphic. This will create and modify all of the tables that you have loaded into the schema and place them into the database as table objects.

  2. From your Access Metadata explorer, left click the “Tables” folder under your Access file tree see Figure 3

  3. You will see the “Migrate Data” graphic become enabled

  4. Click “Migrate Data” and the data from your Access database will be exported into SQL Server 2005

  5. A report of the completed tasks will pop up, press close and your migration is complete