Copyright © Cloud Software Group, Inc. All Rights Reserved |
1.
2.
• 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
− 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).
− “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).
If you are using queues held in the iProcess database (version = 0003), you should note that:
− 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.
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.
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).
Copyright © Cloud Software Group, Inc. All Rights Reserved |