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.

To stop all servers, you run stoplaw. To start all servers, you must start the Infor Lawson subsystem.

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	/EnvironmentDirectory/law/system/ladb.log	dbmode dbusers dbadmin
lajs	stopjobq startlajs	lajs.cfg	/EnvironmentDirectory/law/system/lajs.log
latm	stoplatm startlatm	latm.cfg	/EnvironmentDirectory/law/system/latm.log	tmmon tmcontrol
LAWCOMPQ	stopqueue startqueue	None	$LAWDIR/system/queue.log Each program that is compiled also has its own error file.	qstatus qcontrol
All Infor Lawson servers	stoplaw Start subsystem command	N/A	Log file for specific server	N/A