Overview
You would like to test upgrading your ListManager production server in a test environment and want to know how you can clone the production server and apply its license to the test server without disabling the production license.
Prerequisites
- You have been issued a valid development license for testing purposes
Solution
To complete this solution, Stop ListManager Services, Backup the Database, then Install and Configure the ListManager Test server
Stop ListManager Services
Stop your ListManager services in Windows as Services, in Windows from the webserver, or in Linux.
Stop ListManager Services in Windows as Services
- As a Windows Administrator on your webserver, click Start and type "Services"
- Right-click on the ListManager Service
- Click Stop
- Right-click on the ListManagerWeb Service
- Click Stop
Stop ListManager Services in Windows From the Webserver
- As a Windows Administrator on your webserver, open the ListManager window
- Press CTRL+C and the window will close
- Open the ListManager webserver window
- Press CTRL+C and the window will close
Stop ListManager Services in Linux
- As root on your ListManager webserver, navigate to your ListManager directory. e.g. /usr/local/lm/bin
- Enter ./S96lm stop to stop ListManager
- Enter ./S96httpd-lm stop to stop ListManager webserver
Back up the ListManager Production Database
- Log on to your Production Microsoft SQL Server as an Administrator
- Using File Explorer, navigate to your SQL Server Data directory,
C:\Program Files\Microsoft SQL Server\MSSQL\Data\
- Copy the
ListManager_Data.MDF
andListManager_Log.LDF
files
- Log on to your Production ListManager server and edit 'lmcfg.txt' located in the LM install directory:
Windows: C:\Program Files\ListManager\lmcfg.txt
Linux: ~/ListManager/bin/lmcfg.txt
Copy the$Node_Name
value. You will need this value later.
Install and Configure the ListManager Test Server
- Install LM to a new server. During the install, select 'new install'. When it prompts for database credentials, enter invalid info like 'asdf' for the database location, username, and password. The install will say that it cannot connect to the server, and ask if you want to adjust settings and try again. Select 'No' to continue the install
- Copy the
ListManager_Data.MDF
andListManager_Log.LDF
files to the sameC:\Program Files\Microsoft SQL Server\MSSQL\Data\
directory on your Test server
- On the Test server, edit the 'lmcfg.txt' located in the LM install directory. Use the $node_name value from the Production server. Set the database login info to point to the Test database
- Open a command prompt as admin and change the directory to the ListManager install directory
- Run this command where
x.x.x.x
is the IP of the Test server:lm tclportbindip x.x.x.x
- In the ListManager install directory, verify if the following parameters have the correct information in the ListManager\tclweb\bin\tclhttpd.rc config file:
Config ipaddr {x.x.x.x}
Config https_ipaddr {x.x.x.x}
- In the command prompt window, run the following commands one at a time and verify if they ran successfully:
lm serial DevSerialHere
Example:lm serial Devtest-12s4f5da3s5f45d
lm clearactivation
lm getactivation
- In the command prompt, start ListManager service in no mail mode and clear queues (any active mailings) to avoid conflicts with your Lyris production environment:
lm start nomail noincoming
- Open another command prompt window as admin and navigate to ListManager\tclweb\bin\
- Run:
httpd-lm.exe
- Check the output for any errors
- Check the output for any errors
- If everything started successfully, open the ListManager interface and log in as an Administrator
- Navigate to Utilities > Administration > Server > Server Settings > Node Settings, IP Addresses tab and ensure that the correct IP addresses are listed. After any change of IP address, e.g. after a migration, add and delete the IP addressed here
- Select one or more IP addresses from the 'TCLPORT IP addresses' dropdown.
By default, no TCLPORT IP addresses are selected.
(IP addressed listed are not highlighted). So select one or more IP addresses from the list.
- Check Mailstream IP Addresses, navigate to Utilities > Administration > MailStream > MailStream Administration > Select mailstream
- Remove the old IP address and add in the new IP address. Repeat this for each Mailstream configured
- Remove the old IP address and add in the new IP address. Repeat this for each Mailstream configured
- Check Internet Hostname, navigate to Utilities > Administration > Sites, then Click to edit Site
The Internet Hostname is the hostname ListManager will use if URL tracking is turned on per list. Make sure the Hostname points to the new IP address.
The Test environment is a clone of your Production environment enabling you to test modifications or upgrades without impacting your Production operations.
Priyanka Bhotika
Comments