Section 1
Introduction

Section 2
Configuring for First Use

Section 3
Changing Admin Password

Section 4
Creating Accounts

Section 5
Global Component Settings

Section 6
Backups

Section 7
Log Files

Section 8
User Interface Settings

Section 9
Database Connections

Section 10
Non-Standard Ports

Section 11
Firewalls

Section 12
SSL

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

Example 2
As a second example, assume that the proxy has three assigned DNS names "lui.sample.com", "hub.sample.com", and "trk.sample.com", which are used to decide which local host to access, so the proxy could be configured to do the following:

Forward access on
lui.sample.com:80
to local host LUI (192.168.1.1), port 80

Forward access on
hub.sample.com:80
to local host HUB (192.168.1.2), port 8080

Forward access on
trk.sample.com:80
to local host TRK (192.168.1.3), port 8888

In this example the "splitting" is realized by using three different host names, all assigned to the same server, where access on the standard HTTP-port 80 is mapped to the different local hosts (LUI, HUB, TRK) and their corresponding ports (80, 8080, 8888) depending on the DNS name used to access the proxy. Users wanting to access the Maestro User Interface would have to use a URL like "http://lui.sample.com/lui". Users accessing the Administration Hub would use "http://hub.sample.com/hub" and the tracking URLs would contain the URL "http://trk.sample.com/trk".

The example demonstrates that the host names of the servers hosting the LISTSERV Maestro components may differ when viewed locally or from the "outside" world. Internally, the LISTSERV Maestro components always use the local names to communicate. When setting host names in INI files (or during the setup), use the names that are locally valid (which can also be externally valid names, if only the names work for local access too). Whenever the local names are different from the external names (usually because some sort of proxying or forwarding is involved), the administrator needs to perform some additional configuration steps to make LISTSERV Maestro aware of the differences.

The following list describes what to do if the local name or HTTP port of a host differs from the externally known name or port:

  • The Maestro User Interface component's server has a local host name or port that is different from the external name, edit the file:

    \Program Files\L-Soft\Application Server\lui\lui.ini

    Add or edit the entry "ExternalHostName" to read "ExternalHostName=HOST:PORT"

    where "HOST" is replaced with the external name of the server running the Maestro User Interface component and "PORT" with its external HTTP port (if the external HTTP port is the default "80", leave out ":PORT" and only write "ExternalHostName=HOST").

  • The Administration Hub component's server has a local host name or port that is different from the external name, edit the file:

    \Program Files\L-Soft\Application Server\lui\lui.ini

    Add or edit the entry "ExternalHubHostName" to read: "ExternalHubHostName=HOST:PORT"

    where "HOST" is replaced with the external host name of the server running the Administration Hub component and "PORT" with its external HTTP port (if the external HTTP port is the default "80", leave out ":PORT" and only write "ExternalHubHostName=HOST").

    Important Note: This entry has to go into the "lui.ini", not into the "hub.ini".

  • The Maestro Tracker component's server has a local host name or port that is different from external name, set the external host name and/or port in the "Tracking URL" settings in the Administration Hub. Please see Section 10 for more details.

To actualize the examples above, the following changes to the administration settings would have to be made:

For Example 1, two lui.ini entries are required:

ExternalHostName=maestro.sample.com:9001

ExternalHubHostName=maestro.sample.com:9002

Also, the Administration Hub would be used to configure the tracking URL to use a "Tracker Host" of "maestro.sample.com" and a "HTTP Port" of "9003".

For Example 2, two lui.ini entries are required:

ExternalHostName=lui.sample.com

ExternalHubHostName=hub.sample.com

Also the Administration Hub would be used to configure the tracking URL to use a "Tracker Host" of "trk.sample.com" and a "HTTP Port" of "80". Next, it would be necessary to configure the proxy accordingly, so that it transparently forwards the requests as described above - but this depends on the proxy software used and is not part of the LISTSERV Maestro setup.

Back One Page | Forward One Page