Kbase 21680: Configuring the Progress Database as a SonicMQ Message Store
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/17/2002 |
|
SUMMARY:
This Solution applies to SonicMQ 4.x and Progress Database Version 9.1C14. It discusses some configuration considerations for using the Progress Database as a SonicMQ message store.
SOLUTION:
To use the Progress Database as a SonicMQ data store, you need the following Progress Database products:
Enterprise Database
Client Networking
SQL-92 Client Access
If you are running the SonicMQ broker and the Progress Database on the same machine, install the Enterprise Database.
If you are running the SonicMQ broker and the Progress Database on different machines, install the Enterprise Database product and Progress Client Networking on one machine. On the machine where you install and run the SonicMQ broker, you must also install the Progress Client Networking and SQL-92 Client Access products.
SonicMQ uses SQL-92 tables to access the Progress Database. During the Progress product installation, when you are asked what Server Engine you wish to install, select SQL-92 or Both (use Both if you need to use 4GL access as well). You must also choose the "Complete" installation type.
Because the Progress Database will be used as the message store, it could grow larger than 2GB, thus it is recommended that you enable the large file feature of this database. Progress Knowledge Base Solution 21184 describes the large file feature.
To enable the large file feature of the Progress Database for use as a SonicMQ message store, do the following:
Use PROSTRCT CREATE to create the Progress Database structure with the following information in the structured description file (.st):
# SCHEMA AREA with a fixed length file of 3GB and a variable
# length file with a maximum size of 1TB
#
d "Schema Area":6,64 tests/largedb.d1 f 3145728
d "Schema Area":6,64 tests/largedb.d2
For PROSTRCT CREATE to enable the large file feature, there must be a line specifying a fixed size over 2GB for the area before the variable size line in the structured description file. This will allow the variable size of the area to increase up to 1TB.
Although the Progress Database large file feature could support up to 1TB variable size, it is still limited by the file system of the operating system and disk size of the machine.
After creating the Progress Database structure, you need to create an empty Progress Database. You must do this before you can create the SonicMQ database tables. It is recommended that you use a dedicated database for SonicMQ tables. Use the PROCOPY utility to create the empty database.
To start the Progress Database that you've created, go to the directory where you created the database, and enter a command similar to the following :
PROSERVE -S <db-port> -Mn 15 <database-name>
You may use other parameters of the PROSERVE command as necessary. For SonicMQ, the -Mn parameter has to specify a value of 15 or higher.
The user name specified by the DB_USER parameter in the Progress Database section of the SonicMQ initialization file (broker.ini) must have access to the database and must be granted RESOURCE privileges to create the SonicMQ tables.
If you need to stop the database server, you must shut down the SonicMQ broker first.
References to Written Documentation:
Progress Database Administration Guide and Reference.
Progress Knowledge Base Solutions:
21184, "Version 9.1C Allows Database Files Larger Than 2GB"
21681, "Configuring SonicMQ To Use Progress Database As A Message Store"