The dbinit utility is used to create/destroy tables needed by the JMS server.
dbinit <options>
where options include:
-help print out this message
-props <prop file> use specified properties file
-create create the store
-migrate migrate from v1.0, v1.1 or v1.3 to v2.1
-info <destination> display information (about destination)
-destroy destroy the store
The JMS server uses a database for storing persistent messages, destinations, and security information. The dbinit utility is used to create the database tables needed by the JMS server.
The msgsvc.name
property is used to prefix all the objects
defined in the database. This makes it possible to share a database (but
not tables) between multiple JMS servers.
-help
Prints out the command syntax.
-props propsFile
Use the specified property file instead of the default file available from the
lib
directory. For example:dbinit -props my.properties -create-create
Create the tables needed by the JMS server.
-destroy
-migrateDestroy the tables needed by the JMS server.
Migrate the JMS database from a previous version to version 5.2. If both the -migrate and -create flags are created, the tools with create or migrate the database tables as needed.
-info
Print out information about the JMS database. Without any additional arguments, the info command will print information about all destinations. If the -info command is followed by a destination name, information will be printed about that destination, including destination properties and unconsumed messages. As an example, this command will print information about 'myTopic':
dbinit -info myTopic
It is possible to pass arguments to the jvm using the -J flag. In order to set the heap size to 250 MB, the following command line may be used:
dbinit -J-Xms250m -create
Copyright © 2003, 2004 Novell, Inc. All rights reserved. Copyright © 2001, 2002, 2003 SilverStream Software, LLC. All rights reserved.