Stopping and starting the Infor Lawson servers

Servers must be stopped when you are upgrading your software. It might be necessary to stop and start servers for routine system maintenance and for troubleshooting. When you make a change to a configuration file, you will often need to stop and then restart the affected server to ensure that the change you made takes effect.

You can stop or start servers individually, or you can stop and start them as part of the procedure of shutting down and starting up the Infor Lawson system.

Before stopping ladb individually, stop latm and lajs. If you stop ladb before stopping latm and lajs, latm and lajs will crash instead of stopping normally.

To stop and start all Infor Lawson servers, use the stoplaw and startlaw. The startlaw and stoplaw commands control all servers, except the Infor Lawson Debug Server (ladebug). You can add the debug server to startlaw and stoplaw by editing the startlaw and stoplaw file to include either the startladebug or the stopladebug command.

Any log archiving that needs to happen (as specified by the appropriate parameters in $LAWDIR/system/univ.cfg) will be done when only startlaw (or equivalent system LSF startup) is executed. For example, if latm is stopped and restarted by itself, no log archiving will occur.

If you are shutting down or starting the Infor Lawson system, you must also stop or start the WebSphere application server. Stopping and starting the Lawson system

The following chart lists the server stop and start routines as well as other information associated with each server.

Server	Stop and start routine	.cfg file	Log file	Additional server utilities
ladb	stopladb startladb	ladb.cfg	$LAWDIR/system/ladb.log	dbmode dbusers dbadmin
lajs	stopjobqueue startjobqueue	lajs.cfg	$LAWDIR/system/lajs.log	jqcontrol
latm	stoplatm startlatm	latm.cfg	$LAWDIR/system/latm.log	tmmon tmcontrol
queue	stopqueue startqueue	None	$LAWDIR/system/queue.log Each program that is compiled also has its own error file.	qstatus qcontrol
ladebug	stopladebug startladebug	ladebug.cfg	$LAWDIR/system/ladebug.log	dbgcontrol
All Infor Lawson servers	stoplaw startlaw	N/A	Log file for specific server	N/A