Users Guide
Starting Servers | Completing Post-Installation Tasks
OMNM 6.5.3 Installation Guide 69
If you have not automated server startup, then you can use the
stopappserver
and
stopmedserver
scripts to stop these servers, even remotely. Single server platforms are set to
Auto start by default. These commands do not apply.
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 that
you must stop manually before you can successfully restart the 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
Uninstalling the Application
on page 45 for additional notes about shutting down processes
and services.
Starting Servers
In Windows, use the shortcuts in the
Start
button menu to start an Application server or
Mediation server, and (after the Application server has had time to start) the application itself.
Right-clicking an Apache icon lets you start and stop the Web server.
Start Linux applications after logging out, and logging back in either from the installed icon on the
desktop, or from a command line.
Single server platform are set to Auto start by default. The following commands do not apply.
These command lines assume you run
oware
or
. /etc/.dsienv
before running them, to set
the environment correctly. The commands:
startappserver
startmedserver
Both
stopappserver
and
startappserver
scripts may require username/passwords as
parameters, if you have an installation that requires a password. To see the syntax of either of these
scripts, append -? to them on a command line. Here is the help output from
stopappserver
:
~/:stopappserver -?
Usage(1): stopappserver server_url [-u username] [-p password]
Usage(2): stopappserver server_url password
example - stopappserver localhost:1099 -u OWAdmin -p secret
example - stopappserver localhost:1099 secret
If omitted, username will be assumed to be OWAdmin.
If omitted, password will be assumed to be blank.
If no arguments are provided, server_url will be assumed to be localhost:1099.