Owner's Manual

56 Installation
Uninstalling removes all installed files and files created by using the installed system (that it has
permission to delete). It does
not remove directories that were not created by this application’s
installation or runtime. User-created directories in the product’s directory path remain after
product removal.
NOTE:
Uninstaller may freeze on hosts with inadequate resources. Also: The uninstaller deletes uninstall.exe, if
you press the cancel button. After the canceling uninstallation, several directories and files remaining on
disk that require manually deletion to completely uninstall.
Stopping Servers
To stop the Application Server, you can either use the Application Server tray icon in Windows (see
Starting Application Server on page 50), 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. 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.
CAUTION:
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 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 in a shell to start the Application 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 on page 54 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.