Multiple Java virtual machines - 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
Assure DQ
Product Feature

The default installation process installs all applications to the same JVM.

For large volumes of data, multiple configurations are recommended to avoid memory errors. Each configuration uses its own JVM.

If you want each product installation to use its own JVM, proceed through the installation process for each subsequent installation, with the following modifications:

  1. To create the properties files, run the following command:

    for Windows

    init-config.bat -c <myConfigName> <product>

    for UNIX or Linux

    ./init-config.sh -c <myConfigName> <product>

    where <myConfigName> represents the name of your configuration and product is the parameter for your application.

    • For Assure DQ, specify IA.
    • For ER, specify ER.
    • For Insight, specify II.
    • For Perceive, specify IV.

    Product parameters are case-sensitive.

    The command creates the properties files and places them in a folder with the name that you specified. This folder is at the same level and has the same file structure as the default configuration folder.

  2. When you configure the properties files, include the following tasks:
    • In the appserver.properties file, specify a unique port number for each of the different ports for the JVM.
    • In the product-specific properties files, edit the gateway properties to reflect your environment.
  3. Add the configuration name and product parameters, described in step 1, to the validate and deploy commands:
    1. for Windows

      validate-config-values.bat -c <myConfigName> <product>

      for UNIX or Linux

      ./validate-config-values.sh -c <myConfigName>

      <product>

    2. for Windows

      deploy.bat -c <myConfigName> <product>

      for UNIX or Linux

      ./deploy.sh -c <myConfigName> <product>

      where <myConfigName> represents the name of your configuration and <product> is the parameter for your application.

      If you use WildFly, add the configuration name parameter and follow the steps described in “Deploy on WildFly”