Section 1

Section 2
Configuring for First Use

Section 3
Changing Admin Password

Section 4
Creating Accounts

Section 5
Global Component Settings

Section 6

Section 7
Log Files

Section 8
User Interface Settings

Section 9
Database Connections

Section 10
Non-Standard Ports

Section 11

Section 12

Section 13
Tracking and Recipient Profiles

Section 14
Editing INI Files

Section 15
Distributed Components

15.2 Moving Components

15.2 Moving Components Continued

15.3 Server Aliases and Proxy Setup

15.3 Continued

Section 16
User Interface Branding

Section 17
Evaluation Mode

Section 18
International Character Sets

Appendix A
Standard Default Ports

Section 15
Distributed Components

The components of LISTSERV® Maestro can be distributed in a variety of ways. Each component can run on its own server, all components can run on the same server, or combinations of components can run on any combination of servers.

Distributing components has several advantages:

  • Load Distribution - Processor and disk load is shared between several servers, giving each component more "room" to operate.
  • Separate Maintenance - All components do not have to be shut down or re-started, whenever a maintenance task on one of them requires it. The other components may continue running (of course, when a component that other components rely on is shut down, this is no longer entirely true, since the other components can not run properly while the one component is down).

The Maestro Tracker component has very rigid uptime requirements. This component should constantly be running to be able to collect the tracking data from the messages that are sent. It can only do so while it is running and connected to the Internet. Therefore it is not a good idea to shut down the server on which the Maestro Tracker component is running - this should only be done as a last resort.

Other components however do not have these strict uptime requirements. For example, the Maestro User Interface component actually needs to be restarted if a new database is to be used or if a new JDBC database driver is installed (see Section 9 Database Connection for more information). To take advantage of this, it may be a good idea to have the Maestro User Interface and the Maestro Tracker components on separate servers.

For optimal performance for a high-end installation, a component distribution on four servers is recommended:

  • User-Interface and Hub Server - Contains the LISTSERV Maestro components Maestro User Interface and Administration Hub.
  • Tracker Server - Contains the Maestro Tracker component.
  • Database Server - Contains the database used by the Maestro User Interface component.
  • LISTSERV Server - Contains the LISTSERV external component.
  • LSMTP Server - Contains the LSMTP external component.

LISTSERV/LSMTP Server - Contains the LISTSERV and LSMTP external components.

15.1 Fresh Installation with Distributed Components

A fresh installation with distributed components is a straightforward operation. To install any of the three LISTSERV Maestro components, simply run the LISTSERV Maestro setup on the server where the component(s) will be installed and then select the required components from the list, while leaving all components to be installed on other servers unchecked. The other external components (database, LISTSERV, and LSMTP) have separate setup instructions. Simply execute each application setup on the respective server(s).

Back One Page | Forward One Page