Overview: Enterprise Integration

To learn more about how IPRO applications are integrated on the Enterprise platform, review the following information by expanding the sections that follow.

ClosedEnterprise Network Configuration Diagram

eCapture is designed to run on several computers networked to a SQL server. The following diagram shows an example of a typical eCapture network configuration:

ClosedEnterprise Services Integration

eCapture integrates with IPRO (Cloud) Services so that a managing client, client, and case created in Ipro Eclipse is also created in eCapture semi-automatically. At the same time, managing clients, clients, and cases (projects) created in eCapture can be selected in Eclipse. This integration process promotes consistency in the Enterprise platform environment while removing the manual steps that were previously required to move data and output across the Enterprise platform.

In Enterprise, a case is the organizational tool for the data and documents in your eDiscovery project, from initial data ingestion/document discovery in eCapture through review and production in Eclipse. Cases created in Eclipse or eCapture are listed in Enterprise and can be managed in Enterprise or the individual applications.

In addition to standard clients and cases (projects), a managing client was added for those organizations that do business with multiple clients, such as law firms. This can be thought of as a one-to-one relationship. Managing clients provide the basis of the relationship between cases and reviewers (groups and users). For service providers, managing clients are the companies and firms the provider does business with. For law firms, the firm itself is the managing client.

To further expand on the integration with Enterprise Services, Enterprise Code Names is used to organize one or more product-specific cases (projects) under a single Enterprise-level case. Enterprise Code Names can also be used to provide an alias to the actual case (project) name.

At this time, Managing Clients cannot be deleted from within eCapture. New Clients and Cases (Projects) that are eCapture specific, and not shared with Ipro Eclipse, may be deleted from within eCapture directly. The associated properties are also deleted. However, if the Client or Case (Project) is shared with Eclipse, then Enterprise Services manages the deletion. An Enterprise Services integrated client is deleted successfully provided there are no other cases (projects) that are active in any other Eclipse application environment.

ClosedConfigure Integration with Other Enterprise Applications

An Environment Name is used to identify and group all the Enterprise application components that check in with Enterprise Services. If the Environment Name is not set automatically when eCapture Controller initially launches, then the Controller sets it to the name of the eCapture Configuration database, and the name is registered in Enterprise Services assuming a successful connection is made through the login credentials. This name may be changed if desired. An upgrade will not overwrite the existing Environment Name.

For Enterprise Services, it is only necessary to log in one time. Subsequent edits may be made, if necessary, by using the Edit button in the Enterprise Integration dialog box.

Enterprise Services, a centralized environment and case management application, is used to authenticate login credentials and register components across the Enterprise applications (eCapture and Eclipse). Ensure that Enterprise Services is set up and configured before integrating.

eCapture integrates other Enterprise applications by automatically populating a user-defined directory with the necessary files (EXEs and DLLs). eCapture takes advantage of the Eclipse Import Scheduler for loading data directly from an Export Job into Eclipse.

To configure an integration with other Enterprise applications, do the following:

  1. Create an integration directory. This directory is used to store the necessary files used to integrate with the Enterprise applications. This directory should be mutually accessible to all Enterprise products. Use a UNC path rather than a mapped drive letter. Ensure there is enough space for storing the necessary files required by the system.

  2. On the eCapture Controller menu, choose Tools > Configure Application Integration > Enterprise. The Enterprise Integration dialog box appears.

  3. Note the Environment Name: This field is populated automatically with the eCapture Configuration database name indicated at installation time. Ensure that this name is unique for each environment. The system does not validate across the Enterprise application to ensure uniqueness. This name may be subsequently changed. Click Apply to apply the changes.

  4. Configure the Integration Directory (required if Enterprise Integration Service is installed):

    1. Click  to open the Browse for Folder dialog box.

    2. Navigate to the directory (created in step 1) through the UNC path (mapped and local drive letters not permitted).

    3. Click OK. The External Integration Configuration Complete dialog box appears and displays the selected UNC path directory. The directory automatically populates with the files required to integrate with Enterprise applications.

    4. Click Apply to apply the changes. If necessary, configure the Enterprise Services Connection.

  5. To configure the Enterprise Services Connection, do the following:

    1. Enter the Enterprise Services URL Web Address (and if necessary include a custom port) in the Web Address field. Either http or https addresses are allowed. Use the format of http://iprocloud.iprotech.com:1234 or https://iprocloud.iprotech.com:1234.

    2. Enter the user name (in the form of an email address, e.g., username@company.com) and password credentials for the Enterprise Services environment.

    3. Click Apply to apply the changes.

  6. Click OK to close the Enterprise Integration dialog box.

Note: When uploading data to be processed, eCapture Custodians may be created through Enterprise Self-Service. The Custodian and its associated Project display in the eCapture Controller Client Management treeview. For additional details, visit Ipro Online Help.

ClosedManage Cases in Enterprise

The Client Name, Managing Client, Data Directory, and Description/Notes can be created through Enterprise Case Management before starting a Discovery job. The Controller Client Management treeview reflects the created Clients and Managing Clients. For additional details, visit Ipro Online Help.

In addition, the following can be created and edited through Enterprise Case Management:

    • Case (Project) [Note: cannot be edited at this time]

    • Application environment

    • Data Directory (inherited from the Client)

    • Case Templates

Default Template

Used for…



Processing case

Processing & Review case

Settings for eCapture discovery/processing jobs


Processing & Review case

Settings for eCapture export jobs


Review case

Processing & Review case

Settings for Eclipse document evaluation and review (fields, tags, redactions, etc.)


  • The INI settings are used only when process and review databases are created at the same time.

  • An Export Series is created by using the INI settings and mapped as the selected Streaming Export Series.

  • The Export Series name uses the CaseID followed by the export settings INI filename; e.g., if the CaseID = 5 and the export settings INI filename is Case01ExportSettings.INI, then the Export Series name would be ‘5_Case01ExportSettings’


Edits made through Enterprise Case Management are reflected in eCapture. A Client name may be edited through Enterprise Case Management.


Deletions made through Enterprise Case Management are reflected in eCapture. When deleting Cases from eCapture, the Case is removed from Enterprise Case Management and the associated Enterprise Code Name is removed, provided no other Cases are under that same Enterprise Code Name.

When deleting Clients, an exception occurs if:

    • the Client has any associated Cases

    • any active/paused Data Extract or Process Export jobs exist

If dependent Export Jobs (Process or Data Extract) are running in eCapture, deletion of the associated Case in Enterprise Case Management is not permitted. The dependent Export Jobs must be deleted first before the associated Case can be deleted.

When a Case is deleted through Enterprise Case Management, active jobs in the Controller Job Queue are deleted along with the Case.

Refresh Updates in eCapture

To view Enterprise Case Management  updates (adding, editing, or deleting) in eCapture, do the following: right-click the Client, Custodian, or Case in the Client Management treeview to display the context menu and choose Refresh (Client/Custodian/Case). The Managing Client Name and the Enterprise Code Name are updated when the treeview is refreshed.


Related Topics

Introduction to eCapture

Overview: Enterprise Streaming Discovery