Starting Application Server

If you are installing mediation or Application Server(s), an option appears during installation that lets you configure the server so it automatically start when the server boots. The final screen in the installation asks whether you want to start the application server. See Stopping Servers for instructions about stopping Application Server.

If you install without autostart selected, the required boot configuration in files on Solaris do not get updated rendering the pmstartall, pmgetstatus or pmstopall commands inoperable.

The startup sequence: Database server starts first, then Application server. Mediation server can start anytime before or after this sequence, and will wait for application server.

You can stop, start and monitor the Application Server service, with command lines (pmstopall, pmstartall, and pmgetstatus), or use a system tray tool for controlling Application Server. As always, run oware in Windows, or . /etc/.dsienv in Linux / Solaris before running command lines.

For security reasons, pmstopall has a security requirements similar to stopappserver. Here is a sample command line:

pmstopall <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.

While you can always run the command-line script startappserver, a second Application Server on same ports would fail. Also, the start Application Server shortcut does not appear in the Start menu when you elect autostart, assuming your installation offers that as an option. This service appears in the Windows Services dialog as .

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 startappserver. (See startappserver / stopappserver Command Lines)

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 for details.

Automatic restarts are useful for production server installations. However, if you do not elect 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 the sake of Oracle.

When using this auto-start option, it takes some time for the initial load. You cannot see progress for the process unless you tail the server.log file.