Use the DB2 Control Center to create a DB2 database on Windows for the broker or the configuration repository. You can use any other method supported by DB2 (including command line or batch files) if you prefer; refer to the DB2 documentation for details of how to do this.
When
you create a broker or Configuration Manager, you specify
the user ID and password that are used to connect to the database. The user
ID must be known to the database and must own the tables that are being accessed.
When you create the database, ensure that you create them for the right user
ID. DB2 authenticates the user ID using operating system user management,
you do not have to define the user ID to DB2 itself.
If you use the DB2 command line to create the databases, or if you are using DB2 Version 7.2 plus FixPak 9, you must also bind the db2cli package to the configuration repository or broker database. (You do not have to do this if you used either the Create Database Wizard, or the "Preparing the samples for first use" cheat sheet and the Getting Started configuration wizard.)
db2cmd db2 CONNECT to <YourBrokerDatabaseName>
db2 bind C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 bind C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC
db2 CONNECT to <YourConfigurationRepositoryName>
db2 bind C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 bind C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC
If you are creating a DB2 database for a broker, and you deploy message flows that use aggregation, you are recommended to apply row-level locking to the aggregate table in the broker database. See Using aggregation with a DB2 database for instructions on how to do this.
Related tasks
Configuring component databases
Connecting to the databases
Customizing DB2 databases
Authorizing access to the databases
Related reference
Supported databases
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah14470_ |