Configure product integration - assure_dq - 10.1.0

Assure DQ Server Installation

Product type
Software
Portfolio
Verify
Product family
Assure
Product
Assure DQ
Version
10.1.0
ft:locale
en-US
Product name
Assure DQ, ER, Insight and Perceive
ft:title
Assure DQ Server Installation
Copyright
2025
First publish date
2005
ft:lastEdition
2025-11-28
ft:lastPublication
2025-11-28T07:35:54.959000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Legacy Infogix DQ
L5_Product_Group
Legacy Infogix DQ
L6_Product_Name
Product Feature
Assure DQ

The Precisely product suite is designed to share information between products. The following topics describe the various ways in which information can flow between products.

To enable shared security directories between integrated products, see Shared Embedded Security.

Assure DQ and ER

Assure DQ and ER can have two-way communication.

This section contains information about the tasks to perform to enable communication between Assure DQ and ER.

Tip: It is recommended that ER be deployed on its own host so each application is installed on its own JVM.
Important: If the applications do not share the same JVM, you will need to specify the values for the ER gateway properties in IA.properties.

The instructions assume that one application has already been installed. As you follow the basic instructions to install the second Precisely application, include the following tasks:

  1. When you set up the database, create a separate database schema for each application. You can set up the schemas for both applications in the same or a separate database.
  2. If you are using shared embedded security, configure the properties in the embedded.directory.properties file. See Shared Embedded Security.
  3. Enable the gateways between the two applications:
    1. In the IA.properties file, set the ENABLE_ERGATEWAY property to true.
    2. In the ER.properties file, set the ASSURE_GATEWAY_ENABLED property to true only if you require control points for execution during start of day (SOD) or end of day (EOD).
  4. Edit the Assure DQ gateway properties, as applicable, in the ER.properties file. See the Assure DQ Gateway Properties section in the “ER Properties” chapter of the Properties Guide.
  5. Edit the ER gateway properties, as applicable, in the IA.properties file. See the ER Gateway Properties section in the “Assure DQ Properties” chapter of the Properties Guide.

Assure DQ and Insight

Assure DQ works with Insight to provide continuous controls monitoring for Assure DQ controls.

This section contains information about the tasks to perform to enable communication between Assure DQ and Insight.

The instructions assume that the first Precisely application, either Assure DQ or Insight, has already been installed, and that the two applications will share the same JVM.

Important: If the applications do not share the same JVM, you will need to specify the values for the Insight gateway properties in IA.properties.

As you follow the basic instructions to install the second Precisely application, include the following tasks:

  1. When you set up the database, create a separate database schema for each application. You can set up the schemas for both applications in the same or a separate database.
  2. If you are using shared embedded security, configure the properties in the embedded.directory.properties file. See Shared Embedded Security.
  3. In the IA.properties file, set the INSIGHT_GATEWAY_ENABLED property to true.
  4. Edit the Insight gateway properties, as applicable, in the IA.properties file. See the Insight Properties section in the “Assure DQ Properties” chapter of the Properties Guide.
  5. In the II.properties file, edit the following properties, as applicable:
    1. If you do not interface with ACR and you do not use case management, set the REPORTS_AUTOLOADING property to off to save processing time.
    2. If you do not interface with ACR, set the HISTORY_AUTOLOADING property to off to save processing time.

See the “Insight Properties” chapter of the Properties Guide.

Assure DQ and Perceive

Assure DQ can export data to Perceive for more flexible reporting on control data and results.

The instructions assume that Assure DQ has already been installed, and that the two applications will share the same JVM.

This section contains information about the tasks to perform to enable Perceive to receive data from Assure DQ.

  1. When you set up the database, create a separate database schema for each application. You can set up the schemas for both applications in the same or a separate database.
  2. If you are using shared embedded security, configure the properties in the embedded.directory.properties file. See Shared Embedded Security.
  3. In the IV.properties file, configure the following properties:
    1. Check the default value for the ASSURE_EXPORT_DIR and IVP_IMPORT_DIR properties. The values must point to the same location. You can override the default setting.
    2. Specify the value for the ASSURE_EXPORT_TIMEOUT property.

    See the Shared Directory Properties section in the “Perceive Properties” chapter of the Properties Guide.

  4. In the Perceive > User Interface, define an Assure DQ source system from which to extract data.

See the Perceive documentation or the online help.

Assure DQ and ACR

This section contains information about the tasks to perform to enable communication between Assure DQ and ACR™.

Assure DQ can receive data from ACR/Summary®, through an ACR/Connector® node. To enable communication between Assure DQ and ACR/Summary, complete the tasks below.

  1. Open <install_folder>/Infogix/config/default/IA.properties file, and configure the following ACR/Connector properties:
    • XPG_GATEWAY_ENABLED
    • IIA_HOST
    • IIA_PORT
    • XPG_LIST_PLATFORMS_DYNAMIC

See the ACR/Connector Properties section in the “Assure DQ Properties” chapter of the Properties Guide.

ER and Perceive

This section contains information about the tasks to perform to enable Perceive to extract data from ER.

Tip: It is recommended that ER be deployed on its own host so each application is installed on its own JVM.
  1. When you set up the database, create a separate database schema for each application. You can set up the schemas for both applications in the same or a separate database.

    Configure Product Integration

  2. If you are using shared embedded security, configure the properties in the embedded.directory.properties file. See Shared Embedded Security.
  3. Important: ER must be installed to complete these steps.
    See the Perceive documentation or the online help.
  4. In the Perceive > User Interface, complete the following tasks:
    1. Define an ER source system from which to extract data.
    2. Set up an ER data transfer option. For example, specify the ER Data Source as InfogixERDS.
  5. Add the ER data source, with the JNDI name InfogixERDS, in Perceive. The data source must point to the ER database.
    1. For WildFly, add a new set of properties in the datasource.properties file that define the database connection properties of ER. See Chapter 6, “Data Source Properties”, in the Properties Guide for more information on configuring external datasources.
      1. For the property ds.DATABASE_JNDI_NAME.n, specify the name of the ER Data Source defined above (InfogixERDS).
    2. For WebSphere, use the WebSphere Integrated Solutions Console to define the new data source for ER.

Insight and ACR

ACR works with Insight to provide continuous controls monitoring for ACR controls.

To enable communication between Insight and ACR, see the Visibility API guide.

Insight and Perceive

Insight works with Perceive to provide a full visibility solution with custom views.

No integration tasks are required at the time of installation.

Later, you will need to identify Perceive as an information source through the Insight > User Interface.

Perceive and ACR

ACR works with Perceive to provide additional reporting capabilities for ACR controls.

To enable communication between Perceive and ACR, see the Visibility API guide.