How to Change the IP Address of a Lawson App Server

I've had to do this when our company was merged with another and we had to re ip 3000+ instruments and Computers. We went from 172.x.x.x to 10.x.x.x for our IP range. A lot of this has to do with how you did your original install, did you use an alias or the ip address of the server. If you used alias you probably only need to update the servers entry in the DNS server if not you'll have more work to do.

What OS is your app server on UNIX or Windows?? Ours is on UNIX so here is what I did.

1) Updated/checked the $LAWDIR/system/install.cfg file to change/verify the app's entry. (Lawson's upgrades are always looking at this file, so fix it now or it'll bite you later)
2) Dumped iosconfig (5, 6) to a file and searched for the IP address of the app server, if the ip was in the file I changed it and used it to reload when I was ready for the change.
3) Checked the /etc/hosts file and updated any IP's in that file.
4) Updated the /etc/resolv.conf file to point to the new DNS server (you don't need to do this if your DNS isn't changing).
5) Updated the /etc/ntp.conf file to point to the new Time Server (I have one UNIX server going out to Annapolis MD for it's time and the others check that server for their time corrections).
6) Check the $IBMHTTP_HOME/conf/http.conf file for any IP entries that might need changed there.
7) In $LAWDIR/system ran:

find . -exec grep -q "172.16.8.22" '{}' \; -print > support.dat

looking for the old IP addresses in configuration files.

8) I also went through all the *.cfg, *.properities, *.perms, etc files in $LAWDIR/system to make sure there wasn't any other IP entries.
9) Check your $LAWDIR/webdocs/lawson/portal/portalconfig.xml file for any IP address in it (if you used the alias you shouldn't have problem). We use Lawson Time Management Application and server.
10) If you are using Lawson Time Management (we are 5.2 MSP11) there are more IP's that have to be checked and fixed. Some are stored in files, some are stored in the database, some are on a Windows server and some are on a UNIX server.
11) Here are other files you should check, if you have them.

Unix
$GENDIR/install/ssoconfig.xml
$LAWDIR/webdocs/lawson/portal/servenv.js
$IBMHTTP_HOME/conf/httpd.conf

Windows
c:\program files\lawsonPSA\system\ssoconfig.xml
c:\program files\lawsonPSA\system\sasystem.properties
c:\program files\lawsonPSA\root\servenv.js

12) If your Oracle database is on the same server you'll have to check/update your

$ORACLE_HOME\network\admin\listener.ora
$ORACLE_HOME\network\admin\tnsnames.ora
$ORACLE_HOME\network\admin\sqlnet.ora

Also, if you have other tnsnames.ora files on other servers or a global one it'll have to be updated.


Once all the IP's are updated you'll have to restart Lawson. But, first take a backup of your install directory before any changes are made. You may need it.

Good luck.

I had more problems with Lawson when I was force to change the Lawson passwords to strong passwording and going to a new domain.

Tom,

We're a Windows shop with SQL server. I'll go through your list and report back.

Thanks!
-Randy