The components of LISTSERV Maestro use a number of ports to communicate with each other and with the external world. The ports used are standard ports and will work well under most circumstances. Under certain conditions, it may be desirable to change one or several of the ports to other ports – for example, if another application installed on the same server already uses one of the ports LISTSERV Maestro is set to use. Changing ports may require editing certain INI files. For more information on editing LISTSERV Maestro INI files, see Section 20
Editing LISTSERV Maestro INI Files.
If any of the ports described in the previous sections are already in use on the server where the LISTSERV Maestro component is installed, it is possible to change the use of this port. Note that some components make use of the same port as other components. This is not a problem between the different components of LISTSERV Maestro. If there are several components on the same server, then the components share usage of these ports (port 80 for HTTP access and port 1099 for internal communication, for example). It is not necessary or even possible to configure one component to use a different port than the other while the components are on the same server.
If you do not configure the Port entry, then the default port (
80 for HTTP or
443 for HTTPS) will be used.
If there are several LISTSERV Maestro components installed on the same server, then they will all be affected by this change. It is
not possible to use different HTTP ports for each of the components if the components are installed on the same server. However, if the components are installed on different servers, they can use different HTTP ports. These changes will only be effective after a restart of the component in question.
[maestro_install_folder]/lui/lui.ini
•
|
The Maestro User Interface and the Administration Hub User Interface are both accessed using an HTTP port. This implies that if this port is changed, it will no longer be possible to access these interfaces by entering the default URL into the location field of a browser. Instead, it is necessary to add the port number (with a colon “ :”) to the URL. For example, if the HTTP port is changed to 8080, then the access URL will need to include the port number as shown below:
|
•
|
Changing the HTTP port also affects the CompileAll command (this command is a tool to pre-compile all pages before first use – see the Installation Manual for details). Usually this command is only executed once, right after installation. However, if CompileAll needs to be run again (for example after an upgrade installation), and the HTTP access port has been changed for the LISTSERV Maestro installation, the following files must be edited:
|
•
|
The “hub.host” file is located on the server where the Administration Hub component is installed, while the lui.host file is located on the server where the Maestro User Interface component is installed. If both components are on the same server, then the two files will be as well.
|
•
|
The file can be edited with any text editor. It contains a single line, comprised of the access-URL (including host-name and port) for the Administration Hub and the Maestro User Interface component, respectively. Change it so that it contains the new HTTP port with a colon “ :” after the host name (or leave out port and colon if the port is the standard port 80). For example, if the HTTP port was changed to 8888, then the Maestro User Interface entry must look like this:
|
Important: Maestro Tracker will work most effectively if it uses port 80. Many sites have firewalls that prevent their users from connecting to other ports for HTTP connections, which would not only prevent them from being tracked, but from reaching the actual Web pages whose access is being tracked.
This port can be configured independently for each component. However, if the components are installed on the same server, then they must all use the same internal communications port.
Edit or add the entry RMIPort. If the entry is not present or is commented out, the component defaults to port 1099. For example:
RMIPort=5310
Edit the entry HubRMIPort (if this entry is not present or is commented out, it defaults to port 1099).
Edit or add the entry RMIPort. If the entry is not present or is commented out, the component defaults to port 1099. Example:
RMIPort=5310
Edit or add the entry RMIPort. If the entry is not present or is commented out, the component defaults to port 1099. Example:
RMIPort=5310
This port is only used by the Maestro User Interface (LUI) to communicate with Maestro Tracker component (TRK). It can easily be configured using the Administration Hub. Simply enter the Administration Hub, click the
Global Component Settings icon, and then
Maestro Tracker. Edit the port number. Click
[OK] to save. The change will be effective immediately.
LISTSERV Maestro comes with an internal database that can be used as the system database. The Internal Database Connection port is only used by the Maestro User Interface component when it is configured to use this internal database. To configure it, edit the following file:
In this file, find the entry port both in the
[client] and [
mysqld] sections. Edit the value of
both of these entries to change the database connection port. In addition, edit the following file:
Edit the “MySQLConnectorJDriverPlugin.databasePort” entry or the “
MySQLDriverPlugin.databasePort” entry (whichever is present) to point to the same port number. These changes will only be effective after restarting the Maestro User Interface component.