Open topic with navigation

TIBCO ActiveSpaces® 4.8.0

# tibdgadmind

tibdgadmind is an administrative daemon for ActiveSpaces. The SQL ExecuteUpdate command requires tibdgadmind running in the data grid.

Syntax

    tibdgadmind [-r realm_service_URL] [-l listen_URL][--logfile <file>][--max-log-size <bytes>] [--max-logs <num-files>][--trace <level>]

By default, tibdgadmind listens on http://localhost:7171.

If more than one tibdgadmind needs to run on the same host or in a production environment where processes on other hosts must be able to communicate with the tibdgadmind, the listen URL must be specified and must be something other than the default value `localhost:7171`. The value can be changed by specifying `-l listen_URL`.

More than one realm service URL can be specified by separating the URLs with the pipe (|) character when starting the tibdgadmind process.

After connecting to the realm service, tibdgadmind can process requests for table configuration changes such as creating a table, dropping a table, creating an index, and deleting an index.

To make table and index configuration updates to your data grid, you must run a realm service and an active data grid, a tibdgadmind process, and you must use the ExecuteUpdate API of the tibdgSession object. For more information, see Defining a Table by Using SQL DDL Commands.

Use the `--logfile <file>` command-line option to specify a file name or prefix to log to.

Use the `--max-log-size <bytes>` command-line option to specify the maximum size of a log file (bytes), This option is ignored if a log file is not set. The default size is `9223372036854775807 bytes`.

Use the `--max-logs <num-files>` command-line option to specify the maximum number of log files. This option is ignored if a log file is not set. The default size is `1`.

Use the `--trace <level>` command-line option to set the log level. The valid values are `severe`, `warn`, `info`, or `debug`. The default value is `severe`.

The `trace` command-line option differs slightly from the equivalent option for the other processes. Also, the other processes have logging modules that allow for finer control of logging whereas `tibdgadmind` does not provide finer control. You can only specify a log level as documented in the `--trace` level section.

To provide fault tolerance, multiple tibdgadmind processes can be run.

Copyright © 2009-2022. Cloud Software Group, Inc. All Rights Reserved.