WebSphere Message Brokers
File: ah35004_
Writer: Pete Seddon

Concept topic

This build: July 31, 2007 21:30:45

Using Derby databases on Windows

Set up your environment to access a Derby database.

Derby refers to the DB2 database product that is based on the Apache Derby open source project from the Apache Software Foundation. Derby database support is embedded in the broker component on Windows only.

This topic describes the processes, services, IP ports, and database files that are required to support Derby on Windows.

Security

The Derby database has no associated security controls, and no optimizations have been performed. For these reasons, do not use Derby in a production environment.

DB2 Run-Time Client use

WebSphere Message Broker uses ODBC to connect to Derby databases. Derby is a native Java database engine without ODBC support. The DB2 Run-Time Client provides the drivers that allow ODBC to access Derby databases. The DB2 Run-Time Client is used only for providing and managing the ODBC connection between WebSphere Message Broker and the Derby databases. It does not provide a DB2 database and therefore does not consume the resources that a full DB2 installation typically requires.

Database Instance Manager (managing, creating, deleting, and running databases)

You must create and start a network server to enable access to Derby databases through ODBC. The network server provides access to Derby databases from external programs. When you create the first Derby database using the mqsicreatedb command, a Windows service is also created. The service is called IBM MQSeries Broker DatabaseInstanceMgr6 and starts automatically when Windows starts, under the user name that you supplied with the mqsicreatedb command. The service is referred to as DatabaseInstanceMgr component, and starts the network server. DbInstMgr is the internal component name of the Database Instance Manager.

All Derby databases that you create using the mqsicreatedb command are served by one instance of the DatabaseInstanceMgr and network server. Before the network server can function, it requires a TCP/IP port number. The default port number for Derby is 1527 (use this when you create a Derby database). You can specify a different port number when you issue the mqsicreatedb command to create a Derby database for the first time. However, you cannot subsequently change the port number after a network server has been set up, without first using mqsideletedb to remove all Derby databases.

Issue the mqsilist DatabaseInstanceMgr command to produce a list all of the databases that have been created by the mqsicreatedb command. You can remove the DatabaseInstanceMgr and the network server after the last Derby database has been deleted, using the mqsideletedb command.

If the password of the user name under which the Windows service runs is changed, use the mqsichangedbimgr command to update the service with the new password. You can also use the mqsichangedbimgr command to change the user name of the service. Use the mqsistart and mqsistop commands to start and stop the DatabaseInstanceMgr component.

Multiplicity (brokers, dbiMgrs, installations, databases)

The number of databases that you can create with the mqsicreatedb command is limited only by availability of system resources. A maximum of one DatabaseInstanceMgr is created irrespective of how many databases have been created. If you have installed multiple instances of WebSphere Message Broker, all instances use a single of the DatabaseInstanceMgr component.

Removing databases and the DatabaseInstanceMgr component

Use the mqsideletedb command to clear all resources created by the mqsicreatedb command. When the last Derby database is deleted, the DatabaseInstanceMgr and network server are also stopped and removed. If the database files cannot be deleted using the mqsideletedb command, you can delete them manually.

Related concepts
Issuing database commands on Windows
Related reference
mqsicreatedb command
mqsideletedb command
mqsichangedbimgr command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:45

ah35004_ This topic's URL is: