Integrating IBM Datacap with IBM Navigator
Introduction
This document describes how to integrate IBM Datacap capture software with IBM Navigator. IBM
Navigator is IBM’s SaaS offering for ECM and this document describes how to modify a Datacap
application so that documents captured and processed by Datacap can be exported directly to IBM’s
ECM cloud offering, IBM Navigator. The method used to achieve this is Content Management
Interoperability Services (CMIS). This is an open standard that allows different content management
systems to inter-operate over the Internet. Datacap v9 provides support for CMIS when creating a
capture application as well as for exporting images (files such as TIFF and PDF) and metadata to a CMISaware content repository such as IBM Navigaor and also any other CMIS compliant ECM repositories
such as FileNet P8, Microsoft SharePoint, or Alfresco.
Business Value
Thanks to CMIS support, and using a simple drag-and-drop interface, Datacap developers can quickly
create applications that define the necessary index fields to capture metadata for documents that must
be stored in a target repository. In addition, using the new CMIS export capabilities speeds up
integration with any repository that is CMIS-compliant. Existing Datacap applications do not need to be
re-written to take advantage of CMIS complaint repositories, it is a case of simply extending the
functionality of the Datacap application by adding an export function.
Requirements
Basic familiarity with Datacap and IBM Navigator are assumed. Datacap version 9 or above is required to
support CMIS integration.
Approach
The basis for building and testing the integration was through using the TravelDocs sample Datacap
application and was built upon the Version 9 Datacap VMWare image. The TravelDocs application was
used as an example of how to integrate Datacap, but the code demonstrated below could be adapted
and used in any version 9 Datacap application that requires integration with IBM Navigator or any CMIS
compliant repository.
Verifying CMIS connectivity
Before starting, verify CMIS for IBM Navigator is enabled and is connected to your Datacap server by
opening a browser and going to: https://ecmtechsales.navigator.ibmcloud.com/fncmis. You should see
the following page:
Read through the information and make a note of the Repository names. We will be using the Restful
AtomPub service to link to the repository. To validate that this is working, enter the following URL into a
browser: https://ecmtechsales.navigator.ibmcloud.com/fncmis/resources/service
You will be prompted for a username and password to log on. Use the username and password for you
IBM Navigator account.
Record CMIS connection details
Make a note of the CMIS connection details you will need for Datacap.

URL for AtomPub binding
service: https://ecmtechsales.navigator.ibmcloud.com/fncmis/resources/service

Repository ID: DOCMGMT01 (production repository of IBM Navigator)

And the login credentials for user account on IBM Navigator.
Datacap Configuration
Create a new application using Datacap Studio
Open Datacap Studio by going to Start > Programs > IBM Datacap Developer Tools > Datacap Studio.
Close the Applications dialog that appears by default.
Click on the Application Wizard icon and click Next
CMIS support has been added to the Application Wizard for easy access and quick page and field
definition. Select Create a new CMIS application and click Next
Enter the CMIS connection information collected before The CMIS settings you recorded earlier will
allow Datacap to pull document description information from the target repository so you can map
them to pages and fields in Datacap. Enter the CMIS connection details you recorded earlier, as shown
below:
Map CMIS fields
Once connected, the Application Wizard allows you to add new documents, pages, and fields to your
application. Additionally, it allows you to “map in” fields directly from the documents listed on the righthand side.
1. In the DOC hierarchy, expand the nodes and select Page
2. On the right-hand side, locate the document class you wish to use. Note that this list is not
sorted alphabetically. Click the Synchronize icon to copy the fields to Page
Click Finish and Close to complete the process.
Configure application
Log in to the Datacap Server using Datacap Studio. Select your newly created application. Username
admin, password admin.
You can now develop your Datcap application in exaclty the same way as you would any other
application and define rulesets as appropriate. As stated earlier, the TravelDocs Datacap application was
used as an expample to test out connectivity and this was the basis for this integration. Once you are
happy with the functionality of your Datacap application and have tested its functionality, all that
remains is to write the export function and rulesets that will allow you to export data to IBM Navigator.
Add custom export ruleset
A create a custom export ruleset needs to be defined to export the file and its metadata to a content
repository using CMIS, in this case IBM Navigator. This has to be done in Datacap Studio because
FastDoc (Admin) allows only to configure settings for rules, not create new rules and rulesets.
Within Datacap Studio, on the Rulesets tab, right-click your application, and select Add Ruleset. Rename
the Ruleset to Export to CMIS.
Add two rules to the new ruleset, called Batch and Page Close
Attach each rule to the DCO so that Datacap knows they need to be processed at the appropriate level
in the document hierarchy.
Batch rule
Make sure the new ruleset is locked and select the Batch rule. To attach it to the DCO, expand Run rule
at the start of… in the Properties window and select Batch.
Page Close rule
Next, select the Page Close rule. Attach it by expanding Run rule at the end of… in the Properties window
and selecting Page. In this example, Rental_Agreement documents within the TravelDocs application
were to be exported, so therefore type of Rental_agreement was selected as shown below.
This instructs Datacap to run this ruleset when processing a page of type Rental_Agreement is complete.
Save and publish Rulesets.
Export Task Profile
Similarly, you must attach the ruleset to the Export task profile so that Datacap executes the rules,
which are associated with the document hierarchy in the previou section, when the Export task is
carried out. Lock the Task Profiles and add the Export to CMIS ruleset to the Export task profile:
Save and unlock the task profiles.
Add actions
The final step is to add the necessary actions to each rule. The new CMIS actions are available in the
Actions library under CMISCLient. At batch level, in the Batch rule under Function 1, add the same
connection details used earlier as shown below:
Notes that a folder is also created for the batch.
At page level, in Page Close rule under Function 1, we add a number of actions to ensure the page and
its metadata are uploaded correctly. These actions are:

CMISSetVersion: sets the version of the file (page) that is uploaded

CMISSetDocUploadType: sets the document type (Document Class in FileNet)

CMISSetDocUploadProperty: sets a document property. One is required for each field exported

CMISUploadPage: executes the upload action
Before we adding these actions, you need to obtain additional information about what each property is
called in the CMIS repository and record the symbolic name of the Document Class as well as of each of
the properties being uploaded along with the document itself.
With the data obtained, configure the Page Close rule as shown:
Save and publish the rulesets.
Final Steps and further development
Test and run the application and ensure documents are uploaded to IBM Navigator. There are other
CMIS functions available in Datacap and the use of smart parameters is also supported in most of the
functions. Once a working application is developed, experiment with the other functions and smart
parameters to see what actions can be performed from within Datacap.