Add a Message Queue

When adding queues, you have to add:

1. a queue
2. an Mbox set
3. the queue to the Mbox set.

To set up a new queue on your system (so that you can then add it to an Mbox set), use the following command:

swadm add_queue queue_name message_type queue_description

where:

• queue_name is a descriptive alphanumeric name for the queue.
• message_type is used to identify the message type. This should be Local (for local messages).
• queue_description specifies the physical database table that is used to hold the queue, in the following format:

version: table

where:

— version is an internal number used by iProcess Suite to identify the physical syntax of the string that follows it. This should be either:
  • 0001, for Oracle AQ.
  • 0003, for queues that are held in the iProcess database.
— table is the name of the database table that holds the queue, and must be specified in the format needed to access the table (e.g. MS-SQL, DB2, or Oracle AQ).

The database table used to hold the queue must already exist and must conform to the appropriate format. If it does not, messages cannot be added to or read from the queue and iProcess Engine will not function correctly. For more information, see:

— “Oracle AQ Queue Tables and Queues” in TIBCO iProcess Engine (Oracle) Administrator's Guide (for Oracle AQ tables).
— “iProcess DB2 Database Queues” in TIBCO iProcess Engine (DB2)s Administrator's Guide (for iProcess database tables in a DB2 database).

“iProcess SQL Server Database Queues” in TIBCO iProcess Engine (SQL): Administrator's Guide (for iProcess database tables in a SQL Server database).

Note:

If you are using queues held in the iProcess database (version = 0003), you should note that:

• Each queue used by iProcess Engine must be held in its database table. These tables must be held in either:
— the database being used by iProcess Suite (the default option).
— a different database on the same database server.
• Wherever the tables are held, the following permissions must be set up:
— The iProcess Engine database schema owner (default swpro) must have at least insert, select and delete permissions on the database table used to hold the queue.
— The iProcess Engine database user (default swuser) must have at least insert permissions on the database table used to hold the queue.

Examples

  1. This example (for Windows/SQL Server) adds a queue called BGMBOX3. This queue is the physical queue sw_db_wisqueue3, owned by swpro, in the current iProcess database.

    swadm add_queue BGMBOX3 Local 0003:swpro.sw_db_wisqueue3

  2. This example (for Windows/SQL Server) adds a queue called BGMBOX4. This queue is the physical queue sw_db_bgqueue4 owned by user Bart, in the sw database (on the SQL server hosting the iProcess database).

    swadm add_queue BGMBOX4 Local 0003:sw.bart.sw_db_bgqueue4