LISTSERV Maestro uses a “system” database to store its working data – recipient profiles, job ID numbers, tracking information, and so on. An “internal” database (based on MySQL) is included as part of the application and may be used as the system database. Using this internal database will allow the application to run “out-of-the-box”. An optional external database may be configured in place of the default internal database if desired. Switching the system database from internal to external and vice versa can be done at any time as long as both databases are accessible to LISTSERV Maestro during the transfer.
Notes: See
http://www.mysql.com for details about MySQL 4.1.7 and its features to determine if it meets your requirements and expectations for a production database. Reviewing the features will help you decide if you want to use the internal database or if you prefer to install a different external system database.
You can install any of these databases (or a compatible version) on the server where you have installed the Maestro User Interface component (or on any other server that is reachable over the network) and configure the Maestro User Interface to use this database instead of the internal database. (Please refer to the documentation of the database in question for details about how to install and configure the database).
Note: SQL Server 7.0, MySQL 3.23.x and MySQL 4.0 as a system database are also supported but for backwards compatibility with existing installations only. These versions are
not recommended to be used with new installations and it is strongly recommended to upgrade existing installations to a newer SQL Server or MySQL version (or switch to one of the other supported databases).
In order to use an external database as the system database, the database must be prepared for use with LISTSERV Maestro, and LISTSERV Maestro must be configured to use the prepared database. LISTSERV Maestro must transfer all data from the old database to the new database in order to switch from the internal system database to an external database, even before LISTSERV Maestro is first used.
Both databases must be running and accessible to LISTSERV Maestro during the transfer.
Important: If one external database is being switched for another external database, both external databases must be accessible to LISTSERV Maestro simultaneously so that the data can be automatically transferred.
b.
Select The following external database is used as the System Database.
c.
Click the Database Plugin drop-down menu and select an external database to use as the System Database.
|
e.
|
Click [OK] to submit the change.
|
|
7.
|
Wait for the transfer of data between the two databases to be completed. Depending on the amount of data to be transferred and other factors such as network speed and disk I/O, this could take minutes or hours. Check the LUI logs to verify the successful completion of the transfer before proceeding to the next step. Logs are documented in Section 13 Maestro Logs. Do not shut down the server while the transfer is taking place or you will have to restore from backup and start over.
|
Under normal operation, it will never be necessary to revert from an external system database to the internal system database. However, if the need ever arises, follow these steps to restore the internal system database:
Before the Maestro User Interface can be used together with a freshly installed system database, the database must be prepared in certain ways. Outlined below are explanations of the required preparation steps, followed by details specific to each of the supported database management systems.
LISTSERV Maestro must have its own database, separate from any other databases. The database may use the same database server as another database, but must not interact with the other databases on that server. Even if a database is created for storing recipient information for LISTSERV Maestro or for storing LISTSERV lists, it should be a separate database
1. LISTSERV Maestro can be given access to these recipient databases separately (see Section 9
Defining External Database Connections).
A user account must be created within the database server for LISTSERV Maestro to access the system database. This user will then be selected from the Maestro User Interface to connect to the database. Certain privileges are required for the user account, as described in the DBMS-specific sections below.
The database that is used as storage for the Maestro User Interface should be configured in a way that it allows dynamic growth because the data stored by the Maestro User Interface grows over time. The growth rate corresponds to the number and the size of the email jobs that are delivered. Large email jobs with a high volume of collected tracking events will use more database storage space than smaller email jobs.
User space quota – Most databases limit the amount of space that a given user may store in the database. This limit should be set to "unlimited" or a sufficiently large value for an organization’s database usage.
Database or tablespace size – Many database vendors, especially those supporting larger database environments, support the sub-division of the database server in smaller areas, sometimes called "tablespaces" or a similar term (see the database documentation for details). Normally, each database account is assigned to one of these areas, which is then referred to as "default tablespace" or "standard tablespace". This part of the database should be configured in a way that it allows dynamic growth, if possible.
Note: It is possible to use the Maestro User Interface with a database that does not support this type of dynamic growth. To do so, an administrator should make it part of the daily or weekly routine to check the amount of space available for the Maestro User Interface, and then increase it manually when necessary.
File system size – Like other server applications storing persistent data on the file system, the database storing the Maestro User Interface data must reside on a server whose file system is monitored on a regular basis, either through automated system administration tools or by an administrator who regularly checks the system.
Important: Deleting or archiving old jobs from LISTSERV Maestro
on a regular basis will prevent the database from becoming unnecessarily slow.
Tip: The amount of table space and file system space utilized by LISTSERV Maestro will vary drastically based upon the particular usage of the system. Regular monitoring of the database and disk usage are essential to ensure adequate storage space at all times.
In the SQL Server Management Console, create a new database for sole use by the Maestro User Interface. Please see the SQL Server documentation for details about how to create, configure, and optimize a database.
Important: No matter if you create a new database or use an existing one, make sure that the database uses a
case-insensitive collation. L-Soft recommends using the
Latin1_General_CI_AS collation. This means that if you want to use an existing database, then you can only do so if this existing database already uses a case-insensitive collation.
Once a new database has been created, create a user account that the Maestro User Interface can use to connect to the database. Create a new user with any desired name and give it the
db_owner role for the created or selected database.
A new Oracle database for sole use by the Maestro User Interface must be created so that it uses
UTF-8 as its database character set. The database character set
UTF-8 is
required and the Maestro User Interface will not work with a database that has a different character set. (See the Oracle documentation for details).
Use an Oracle administration tool (such as SQL*Plus), to create a new user. This new user must have the
CREATE SESSION and the
CREATE TABLE privilege and a sufficiently large table space quota in the user's default table space.
The Maestro User Interface does not require unusually large rollback segments. If duplicate elimination is performed for large email jobs, larger temporary segments are needed as duplicate elimination is performed with a database sorting operation. See the Oracle documentation for more details on how to configure and optimize databases.
The “maximum key length” value is a feature specific to Oracle. This value is an internal value inherent to each Oracle installation. It is determined mainly by the block size used by the database but may also be influenced by other factors, like the operating system.
For LISTSERV Maestro to be able to create its database table in an optimal manner, it needs to know the maximum key length value used by the Oracle database that is used as the system database. LISTSERV Maestro cannot query the database for this value. The administrator has to determine the maximum key length value used internally by the Oracle database installation and input the correct value.
If the value entered exceeds the actual maximum key length used by the database, runtime errors could result, and LISTSERV Maestro will not work correctly. If a value that is smaller than the actual value is entered, LISTSERV Maestro will tailor its database tables accordingly in order to meet this smaller value. As a result, the database tables will be created with a sub-optimal structure and the user may run into database column size limitations, which would be avoidable if the correct maximum key length value had been supplied on the System Database Connection Details screen.
Oracle documentation concerning which maximum key length value is used under which circumstances is sparse. A commonly used “rule-of-thumb” value is that with a block size of
4K, the maximum key length is
1578. With a block size of
8K, the maximum key length is double the value of 4K, or
3156. Generally, the maximum key length seems to be about 38% - 40% of the block size. If in doubt, please consult the Oracle documentation or contact Oracle support.
To use a DB2 database for the Maestro User Interface, verify that your selected database supports the code set UTF-8. If this code set is not supported by your chosen database, you need to use the DB2 Control Center application to create a new database and define UTF-8 as the database code set.
To configure an existing database that already has the code set UTF-8, verify that at least one user regular tablespace and one system temporary tablespace with a page size of 32K each exist. You may also need to create a buffer pool with a page size of 32K before you can create tablespaces with 32K page size.
Then you will need to create a new database user for sole use by the Maestro User Interface. This user must be configured to use a regular tablespace with 32K page size, otherwise the Maestro User Interface will not work. The new user needs the Database Administration authority for the new database. Then, adjust the database performance parameter Application Heap Size to the highest possible value.
Note: Usage of the native driver is not recommended for the system database. It is only still supported for backwards compatibility reasons. If you are using this driver for the system database, it is strongly recommended that you switch to the “V8.2 Thin Driver” instead (and upgrade to DB2 V8.2 or later, if necessary).
For the native driver, you need to create a database alias on the server that is running the Maestro User Interface component (this is very probably not the server where the database itself is installed!). This is done by starting the IBM DB2 Client Configuration Assistant on this server. (This is a runtime client database tool that comes with the IBM DB2 installation and needs to be installed on the Maestro User Interface component server.)
In the Client Configuration Assistant, click the [Add] button to create a new alias. Select the
Search the network option and continue with the wizard.
Note: The name of this alias is the value for the "Database name" parameter of the IBM DB2 database plugin that comes with the Maestro User Interface.
LISTSERV Maestro supports the older 3.23.x versions of MySQL (with 3.23.42 being the oldest officially supported build), as well as the current 4.0, 4.1 and 5.0 versions (5.0 being the most recent one at the time this was written). However, even though the older builds are supported, if you want to use MySQL as the system database, 4.1.7 or later is recommended.
To use the Maestro User Interface with MySQL, set up MySQL to use the InnoDB Tables table type (see the MySQL manual for more details). This table type supports transactions, and the Maestro User Interface requires a table type that supports transactions. Recent versions of MySQL (for example, version 4.1.7) come with a MySQL Server Instance Config wizard that lets the user specify settings for the database server. These settings will automatically be written to the MySQL configuration file. Within the configuration wizard, specify a database usage type that enables the transactional InnoDB storage engine. If no configuration wizard is available for your MySQL version, the InnoDB storage engine must be enabled manually in the configuration file. See the MySQL manual for more details.
In MySQL versions 3.23.50 and later, the InnoDB tablespace files can be configured to be “auto-extending”, i.e., they will grow automatically as needed. (This is the default when using the configuration wizard; otherwise, the auto-extend option should be manually specified in the configuration file.) For sites running earlier versions of MySQL, the InnoDB data files and log files must be created with sufficient size to accommodate the planned usage of LISTSERV Maestro. The database administrator should monitor the remaining capacity of the tablespace regularly and extend it as necessary.
After the MySQL database server is set up to use the InnoDB table type, create a new database specifically for use with the Maestro User Interface. Create a user to use with LISTSERV Maestro.
To connect to the database, start the MySQL client program mysql.exe from the
bin folder of the MySQL binary installation (on Linux/Solaris, the client program is
mysql.) To create a new database, enter the following command in the MySQL client:
create database DBNAME; where
DBNAME is replaced with the name of the database. Grant privileges by entering the following grant command for the username:
grant all on DBNAME.* to NAME@HOST identified by 'PASSWORD'; where the uppercase values are replaced as follows:
|
•
|
DBNAME: The name of the database to be used with the Maestro User Interface. (This is usually the same name used in the “ create database” command; see above. It is recommended that you use an all-lowercase spelling for the database name.)
|
|
•
|
NAME: The user name of the user to be created and granted privileges.
|
|
•
|
HOST: The host name of the server where the Maestro User Interface is running that will access this database.
|
|
•
|
PASSWORD: The password associated with the user name.
|
Using “grant all” as described above grants all privileges on the given database to the given user. This is usually acceptable if the particular database was created specifically for use with the Maestro User Interface. However, if there is concern about granting the full set of privileges to the user, use the following privilege list instead of “
all”:
select, insert, update, delete, index, create, drop
The following general information about how the Maestro User Interface uses the database can help optimize the database installation for use with the Maestro User Interface.
|
•
|
During normal usage, the Maestro User Interface behaves with OLTP (online transaction processing) characteristics. There is a constant switch between read and write on the database. However, if there are many reports running on the collected tracking data, the characteristics of the Maestro User Interface’s behavior shift more and more into OLAP (online analytical processing), where the amount of (complex) reads outnumbers the amount of writes.
|
If you connect the Maestro User Interface to an external database, there is no longer a need for the internal MySQL database to 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 an external database.
To uninstall the internal database, you’ll need to run the LISTSERV Maestro Setup wizard on the server where the Maestro User Interface component is installed. (See the Installation Manual for further information.) Once you start the Setup wizard, simply
modify the installation and deselect the
Internal MySQL database component. Leave the other components as they were. The Setup wizard will automatically uninstall the internal database.
Important: After the internal database is disabled, it is no longer possible to select the
Use the internal database as the System Database option on the System Database Connection screen of the Maestro User Interface (see Figure 57 System Database Connection Screen5). If this choice is selected by mistake, and LISTSERV Maestro is restarted with no external database configured, 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-installed.
