Externalize queues on WebSphere - 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 process for a WebSphere deployment automatically creates and configures the required JMS queue connection factories, the JMS queues, and the JMS activation specifications. Optionally, you can manually create the connection factories, queues, and activation specifications.

If you re-deploy or upgrade, the connection factories, queues, and activation specifications are deleted and you will have to recreate them. However, for manually created connection factories, queues, and activation specifications, you can specify which JMS components to retain; externalized queues remain unchanged following a redeployment or an upgrade.

This topic assumes that you are familiar with the WebSphere Integrated Solutions Console and know how to create JMS queue connection factories, JMS queues, and JMS activation specifications.

Within each product-specific properties file, the WEBSPHERE_EXTERNAL_QUEUES property lists the required queues for that particular product. The property resides in the Do Not Change section, and by default, is commented out. If you leave the property as is, the system follows the default process to automatically create connection factories, queues, and activation specifications.

Externalize all queues

To externalize all queues for the product, follow the instructions below:

  1. Locate the WEBSPHERE_EXTERNAL_QUEUES property in the product-specific properties file.
    • For Assure DQ, this property is in the IA.properties file.
    • For ER, this property is in the ER.properties file.
    • For Insight, this property is in the II.properties file.
    • For Perceive, this property is in the IV.properties file.
  2. Uncomment the property.

    When you run the deploy script, the system will not create the connection factories, queues, or activation specifications.

  3. From within the WebSphere Integrated Solutions Console, create the connection factories, queues, and activation specifications.

Externalize some queues

To externalize some but not all queues for a product, follow the instructions below:

  1. Locate the WEBSPHERE_EXTERNAL_QUEUES property in the product-specific properties file.
    • For Assure DQ, this property is in the IA.properties file.
    • For ER, this property is in the ER.properties file.
    • For Insight, this property is in the II.properties file.
    • For Perceive, this property is in the IV.properties file.
  2. Uncomment the property in the product-specific properties file
  3. Delete the queue names for which you want to automatically create queues.

    When you run the deploy script, the system will create the connection factories, queues, and activation specifications for unlisted queues but will not create the connection factories, queues, or activation specifications for the names in the list.

  4. From within the WebSphere Integrated Solutions Console, create the connection factories, queues, and activation specifications for those names listed under the uncommented WEBSPHERE_EXTERNAL_QUEUES property.