The broker uses ODBC to access its database and you must set up
an ODBC data source name (DSN) definition
on each broker
system.
Each program that accesses a database through ODBC creates
a connection to do this. At any one time there can be multiple connections
using the same DSN definition.
This topic describes the connections that
a broker database needs, and the ODBC parameters that you must tailor for
the connections:
If
you are using the Default Configuration Wizard or the database commands to
create a broker or a database on Windows, the ODBC DSNs
are
automatically created for you.
To define the DSN explicitly,
link to the topic for your operating system and data source type.
The number of connections required by the broker to its database depend to some extent on the actions of the message flows it is processing. The following connections are required for each broker:
If you are using the same database for several brokers, you must take account of all brokers in your calculations.
The connections for neighbors and publication nodes are only required if you are using retained publications.
When you start a broker, it opens all connections that it requires to the broker database for its own operation. When you stop the broker, it releases all current database connection handles.
If you are using DB2 for your database, the default action taken by DB2 is to limit the number of concurrent connections to a database to the value of the maxappls configuration parameter. The default for maxappls is 40. If you believe the connections that the broker might require exceed the value for maxappls, increase this and the associated parameter maxagents to new values based on your calculations.
Configure the template files by updating the following list of configurable parameters. Some parameters are not applicable to all databases, as shown.
<servername or IP address>, <portnumber>
<servername or IP address>, <portnumber>
For example Sybaseserver, 5000. You can also specify the IP address directly, for example 199.226.224.34, 5000. You can find the port number in the Sybase interfaces file which is typically named interfaces, interfac, or sql.ini, depending on the operating system.
Once you have configured your ODBC data source
names
, you must also configure the environment for issuing console commands,
and for running the broker, so that it can access the required database libraries.
For example, if you have a DB2 broker
database, you must add the DB2 client
libraries to your library search path.
On Windows platforms, this is likely to have been done for you when you installed the database product. On UNIX systems, and Linux, you need to run a profile for each database you need to access. For example, on DB2 you must run db2profile; other database vendors have similar profiles.
If you are using a 64-bit DB2 instance, ensure that
you add <DB2 instance directory>/sqllib/lib32 to the start
of the library search path environment variable after running db2profile.
If you are using a 64-bit Oracle instance, ensure that you add $ORACLE_HOME/lib32 to
the start of the library search path environment variable. If you are using
64-bit execution groups, ensure that you set the environment variable MQSI_LIBPATH64 to
include the regular 64-bit database libraries.
Additionally, ensure that you access the correct set of libraries (32-bit) as this might not be the default.
If you are using WebSphere MQ Version
6, refer to the section 'Implications of a 64-bit queue manager' in the WebSphere MQ Quick Beginnings book for your
operating environment.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah14440_ |