Section 1 Section 2 Section 3 Section 4 Section 5 Section 6 Section 7 Section 8 Section 9 Section 10 Section 11 Section 12 Section 13 Section 14 Section 15 15.2 Moving Components 15.2 Moving Components Continued 15.3 Server Aliases and Proxy Setup Section 16 Section 17 Section 18 Appendix A |
15.2 Moving Components to Another Server It is also possible to move an already running installation or several of its components to other servers. This also applies (in slightly different form) if it is necessary to change the host name of the server where the components are installed. 15.2.1 Moving the Maestro User Interface Component to Another Server Install the Maestro User Interface component on the new server. Do not start it at this stage. Shut down the LISTSERV Maestro installation where the old Maestro User Interface is running. The next step depends on whether the Maestro User Interface's internal database is being used, or if the Maestro User Interface is connected to a different external database. If an internal database is being used, copy the following files and folders (including all files and subfolders) to the new server: \Program Files\L-Soft\Application
Server\lui\lui.ini If there is a connection to a different external database, copy only the following files and folders: \Program Files\L-Soft\Application
Server\lui\lui.ini This will overwrite some files and folders on the new server. Depending on the installation, these paths may be slightly different on one or both of the servers. If the files for the internal database in the previous step were copied (including the "my.ini" file), then it might be necessary to edit the file "my.ini" on the new server, in case the installation path on the new server is different than the one on the old server. In the "[mysqld]" section of the file, make sure that the following entries correctly point to the equivalent folders on the new server that corresponds with the ones they pointed to on the old server basedir=... Remember that this step is only required if the component is being moved together with the internal database On the old server, use Windows' "Add/Remove Programs" panel to start the maintenance setup of LISTSERV Maestro. In the setup, choose "Modify" and deselect the Maestro User Interface component, so that it is uninstalled. Start the LISTSERV Maestro installation on the new server (thus starting the new Maestro User Interface component). 15.2.2 Moving the Administration Hub Component to Another Server Install the Administration Hub component on the new server. Do not start it at this stage. Shut down the LISTSERV Maestro installation where the old Administration Hub is running. If the Maestro User Interface and Maestro Tracker components are running on different servers, shut down the LISTSERV Maestro installation on those servers as well. Copy the following files and folders (including all files and subfolders) to the new server: \Program Files\L-Soft\Application Server\hub\hub.ini
This will overwrite some files and folders on the new server. Depending on the installation, these paths may be slightly different on one or both of the servers. Edit the following file of the Maestro User Interface component, which may be installed on an entirely different server! \Program Files\L-Soft\Application Server\lui\lui.ini In the file edit the "RegistryHubHost" entry so that it contains the host name of the new server where the Administration Hub will be running. Edit the following file of the Maestro Tracker component, which may also be installed on an entirely different server! \Program Files\L-Soft\Application Server\trk\tracker.ini In the file edit the "RegistryHubHost" entry so that it contains the host name of the new server where the Administration Hub will be running. On the old server, use Windows' "Add/Remove Programs" panel to start the maintenance setup of LISTSERV Maestro. In the setup, choose "Modify" and deselect the Administration Hub component, so that it is uninstalled. Start the LISTSERV Maestro installation on the new server (thus starting the new Administration Hub component). Restart the Maestro User Interface and Maestro Tracker components on their servers (if they are on different servers). |