9.4 Disabling and Enabling Internal Database
If the Maestro User Interface is connected to a different database, there is no longer a need for the internal database (based on MySQL) to be run together with LISTSERV Maestro. To reduce the resource usage of LISTSERV Maestro, disable the internal database after configuring the Maestro User Interface to use a different database.
To disable the internal
database, execute the following command:
This will stop the internal MySQL database if it is currently
running and will disable it, so that it will not be started
again if LISTSERV Maestro is restarted. Also, the Windows
service in which the internal database was run is uninstalled.
It is no longer possible to choose the “Use Internal Connection”
choice in the Database Connection subsection of the “Maestro
User Interface” section (located in Global Component Settings
in the Administration Hub). If this choice is selected by
mistake, and LISTSERV Maestro is restarted, the Maestro User
Interface component will not start, as it will not be able
to find the now disabled instance of the internal database.
If, at a later point, the internal database is desired, it
must be re-enabled with this command:
This will re-enable the internal database and install the necessary Windows service. The next time LISTSERV Maestro is restarted, the internal database will also be restarted, and can then be used.
LISTSERV Maestro uses “database plugins” to give access to different JDBC drivers (and through them to different databases) available to the Maestro User Interface. Before a plugin can be used, it must first be registered in the list of known plugins. Some plugins are already pre-registered when LISTSERV Maestro is installed; while others need to be registered after the corresponding JDBC driver has been installed.
To register a new plugin, log into the Administration Hub and click the Global Component Settings link, next click the Maestro User Interface link, and finally, the Database Plugins link. Click on Register New Database Plugin. In the text box, enter the full class name of the plugin to be registered.
For the L-Soft MySQL driver plugin:
For the IBM DB2 V7.2 driver plugin:
For the Oracle 8i thin driver plugin:
For the Microsoft SQL Server 2000 drive plugin:
For the I-net SPRINTA driver for MS SQL Server 7.0/2000 plugin:
Click OK to submit the class name. If the plugin was registered correctly, it will now appear in the list of plugins. If there was a problem during the registration, an error message describing the problem will appear. The most probable causes for problems are misspellings of the class name (which is case sensitive) or a faulty installation of the JDBC driver that is used by the plugin in question (see Section 9.6 Installing JDBC-Drivers for Different Databases for more information).