During the maintenance of your ArcIMS site, you may need to restart the ArcIMS Monitor and Application Server. This happens when you edit a Monitor or Application Server property file or Spatial Server configuration file. You must stop and start the Monitor and Application Server NT Services or UNIX and Linux daemons for the changes to take effect.
On all platforms, when restarting services, you must use the following order:
The reason for this specific order is that the Application Server must be running before the Monitor can register itself to the Application Server.
If your entire site is using Windows platforms, you only need to restart the Application Server.
All Monitors associated with the Application Server, even on remote machines, are automatically restarted. This feature is available on Windows only.
ArcIMS Tasker is another NT Service or daemon. It only needs to be restarted when you make changes to Tasker.properties or need to restart Tasker for some other reason. You do not need to restart Monitor or the Application Server when you restart Tasker.
For more information about how these NT services and daemons work, see ArcIMS Application Server, Monitor, Spatial Server, and Tasker processes.
Option 1: Restarting Monitor and Application Server separately.
Option 2: Restarting only the Application Server.
All Monitors associated with the Application Server will automatically restart.
./aimsmonitor stop &
Repeat this step on all machines running a Monitor.
./aimsappsrvr stop &
./aimsappsrvr start &
./aimsmonitor start &
Repeat this step on all machines running a Monitor.
./aimstasker stop &
./aimstasker start &