The management database (APWMQ) is used to store a variety of information. This consists of definitions, configuration data, events, audit and statistics managed by the WorkGroup Server (WGS). Each of these will be discussed in more detail below.
- Definitions: This consists of remote definitions for managers such as queue managers, kafka clusters, and other management brokers. These definitions can be created from the web interface, utilities or REST API. It also contains nodes, connection manager and agent registration information created during their startup (or manually in cases where registration fails). These definitions are restored into memory at start up of the management server. They are persisted until deleted. Backup files (.info) are also created automatically as part of WGS operation in the most recent updates.
-
Configuration data: This represents recent information about the managed systems and includes detailed configuration information about the managers, topics, queues, and other objects depending on the type of system. This does not include volatile status information such as current depth or active users since this data would be out of date immediately. The data is optionally written from the interval cache to the database tables on an interval.
- At one time, this information was commonly accessed via SQL. We no longer recommend using SQL to query the data. We now recommend the REST API for access. The REST API has many advantages, such as reporting the current information, providing status information, standard security access and many others. As such, this data is not needed in most situations. Specifying "minimal cache startup" in General properties does not restore this data on WGS restart. See Controlling Reading and Writing of Management Configuration Data for more information.
-
Asynchronous data: This data is buffered on arrival and written to the database. Once written, the information is only read on request. These tables support a wrap around design that allows you to keep the amount of table space allocated to a minimum.
- Events: Events are created from a variety of conditions. Some are generated when certain conditions are met, such as an alter event when an object changed. Others are forwarded from the managed system such as queue full events from IBM MQ.
- Audit: Very similar to events but written as the result of audited actions with the management interface. These could be the result of interactions via the web interface, utilities or REST API. By default, the Audit table does not wrap and can get very large. See Why is the table adtinfo so large?
- Statistics: Contains statistical data about the managed system and objects.