Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# iql_queues

The `iql_queues` table defines each message queue that is available on this iProcess Engine node.

## Structure

The `iql_queues` table has the following structure:

    TABLE iql_tables (
    	queue_id	  INTEGER		NOT NULL,
    	queue_name	  VARCHAR(24)		NOT NULL,
    	queue_type	  SMALLINT		NOT NULL,
    	queue_phys_descr  VARCHAR(100)		NOT NULL)

Column | Description
`queue_id` | Unique identifier for this message queue.
`queue_name` | Name of this message queue.
`queue_type` | Message type used by this message queue. This value is always `1`, for local messages.
`queue_phys_descr` | ID of the DB2 database queue table that is used to hold this message queue. See: Format of the DB2 Database Queue TableID for a description of the format used for this value. Default DB2 Database Queue Tables (Test) for more information about the default SQL database queue tables, and how to create additional tables.

## Format of the DB2 Database Queue TableID

The ID of the DB2 database table that is used to hold this message queue (in the `queue_phys_descr` column) is specified using the following format:

`0003:[``database_name``.][``owner``.]` `queue_table`

where:

| • | `0003` indicates that the remainder of the string uses DB2 format.

| • | `database_name` is the name of the database that holds this `queue_table`. If this option is omitted, the iProcess database is used by default.

| • | `owner` is the username of the user that owns this `queue_table`. If this option is omitted, the iProcess background user owns the table by default.

| • | `queue_table` is the name of the DB2 database table used to hold this message queue. Each individual queue must be held in its own database table.

For example, the entry:

`0003:sw_db_bgqueue_1`

describes the DB2 database table called `sw_db_bgqueue_1`, which is stored in the default iProcess database and owned by the iProcess background user.

The entry:

`0003:sw.swpro1.sw_db_bgqueue_3`

describes the DB2 database table called `sw_db_bgqueue_3`, which is stored in the `sw` database (on the DB2 Server hosting the iProcess database) and owned by user `swpro1`.

## Default Message Queues and Tables

When the iProcess Engine is installed, the `init2Kdb2.sql` script creates the following default set of message queues and DB2 database queue tables required by the system.

Queue Name | DB2 Database Table Queue ID
`BGMBOX1` | `0003:swpro.sw_db_bgqueue_1`
`BGMBOX2` | `0003:swpro.sw_db_bgqueue_2`
`WISMBOX1` | `0003:swpro.sw_db_wisqueue_1`
`WISMBOX2` | `0003:swpro.sw_db_wisqueue_2`
`DEADQUEUE` | `0003:swpro.sw_db_deadqueue`
`PREDICTMBOX1` | `0003:swpro.sw_db_predictqueue_1`
`PREDICTMBOX2` | `0003:swpro.sw_db_predictqueue_2`

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s)
`pk_iql_queues` | `queue_id`

## Foreign Keys

None.

## Indexes

None.

## Table Activity

The `iql_queues` table contains one row for each message queue that is available on this node.

Rows are added, updated and deleted in the following situations.

A row is... | When...
added | a new message queue is added to the node, either at installation or by using the `SWDIR``\util\swadm` utility.
updated | a message queue’s details are updated, using the `SWDIR``\util\swadm` utility.
deleted | a message queue is deleted from the node, using the `SWDIR``\util\swadm` utility.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine