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	  number(5)		NOT NULL,
    	queue_name	  varchar2(24)		NOT NULL,
    	queue_type	  number(2)		NOT NULL,
    	queue_phys_descr  varchar2(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 Oracle AQ queue that is used to hold this message queue. See: Format of the Oracle AQ QueueID for a description of the format used for this value. Oracle AQ Queue Tables and Queues for more information about the required structure of AQ queue tables and queues, and how to create them.

## Format of the Oracle AQ QueueID

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

`0001:[``instance``]:``queue_table``:``queue`

where:

| • | `0001` indicates that the remainder of the string uses Oracle AQ format.

| • | `instance` is the Oracle Service Name of the Oracle instance that holds the AQ queue. If this is blank, the default local instance is assumed.

| • | `queue_table` is the name of the AQ queue table that holds the AQ queue.

| • | `queue` is the name of the AQ queue used to hold this message queue.

For example, the entry:

    0001::bgmboxtable1:bgmboxqueue1

describes the AQ queue called `bgmboxqueue1` contained in queue table `bgmboxtable1` on the default Oracle instance.

## Default Message Queues and AQ Tables

When the iProcess Engine is installed, the `init2Kora.sql` (on UNIX, or on Windows `init2Kora_tok.sql`) script creates the following default set of message queues and AQ queue tables required by the system.

Queue Name | Oracle AQ Queue ID
`BGMBOX1` | `0001::bgmboxtable1:bgmboxqueue1`
`BGMBOX2` | `0001::bgmboxtable2:bgmboxqueue2`
`WISMBOX1` | `0001::wismboxtable1:wismboxqueue1`
`WISMBOX2` | `0001::wismboxtable2:wismboxqueue2`
`PREDICTMBOX1` | `0001::predictmboxtable1:predictmboxqueue1`
`PREDICTMBOX2` | `0001::predictmboxtable2:predictmboxqueue2`

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s) | Index Tablespace
`pk_iql_queues` | `queue_id` | TINYINDEXSPACE

## Foreign Keys

None.

## Indexes

None.

## Storage

The following STORAGE values are defined for this table.

Value | Definition
Initial | TINYTABLESIZE
Percentage Increase | TINYTABLEPCTINCREASE
Tablespace | TINYTABLESPACE

## 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