Users Guide

Auto Starting Servers | Completing Post-Installation Tasks
OMNM 6.5.3 Installation Guide 71
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.
While you can always run the startappserver command-line script
, a second Application server on
the same port fails. Also, the Windows Start Application Server shortcut does not appear in the
Start menu when you elect autostart, assuming your installation offers that as an option.
If you select
no autostart , then no autostart service installs, and you must manually start the
Application server either from the Start menu (in Windows), or from a command line with the
startappserver script. (See
Starting Servers on page 69.)
If you want to install the service (daemon) after you have already installed the rest of the
application, you must run the installprocman script from a command line. See
Installing Server
Manager
on page 72 for details.
Autorun is useful for production server installations. However, if you do not select this option, then
you must manually start the Application server and Mediation server yourself (using the
startappserver and startmedagent command lines or the item in the Windows Start
button menu).
For Oracle/Windows installations with autostart selected for a server, the last step in the
installation may prompt you about whether to start process monitor immediately. This potentially
lets you defer appserver startup until the next reboot for Oracle’s sake.
NOTE:
Autostart takes some time for the initial load. You cannot see progress for the process unless you tail the
server.log file.