To stop the Application Server, you can either use the Application Server tray icon in Windows (see Starting Application Server), or stop the server from a command line. The command line to stop a server is pmstopall.
If you have not automated server startup, then you can use the stopappserver and stopmedserver scripts to stop these servers, even remotely. Here is the syntax:
stopappserver <hostname>:1099 -u <username> -p <password>
stopmedserver <hostname>:1099 -u <username> -p <password>
Both -u and -p are optional parameters. If you omit username, the application assumes OWAdmin is the user. If you omit a password, the application assumes a blank password.
Using Ctrl+C in the application server shell may stop the application server, but processes can linger which you must stop manually before you can successfully restart application server. One example occurs when the application server shell displays “.... FAILED TO LISTEN ON TRAP PORT 162 .... “during startup. If this occurs, use task manager to stop WMIBeam and WMINotification processes. If such processes do not exist in task manager, reboot before starting application server.
If you have not logged in and changed the password for OWAdmin with the application’s login screen or the Oware Management Center, the login to stop the server fails. By default, OWAdmin and the installing user have the role OWServerAdmin. Any user assigned this role can stop the appserver. Blank passwords are valid if they are defined for the user.
If you used startappserver (or startmedserver) in a shell to start the Application Server (or mediation server), you can stop the server by either interrupting that shell with Ctrl+C or by closing the shell. Ultimately, you can kill the Java processes on your machine to halt a server.
See Updating an Existing Installation for additional notes about shutting down processes and services. If you uninstall when a server is active, the uninstallation will attempt to shut it down and failing that will prompt you to shut it down manually.