Starting Application Server

If you are installing mediation or Application Server(s), an option appears that lets you automatically start the server. Selecting Yes (the default) automatically starts the server when the system boots. 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.
Also: The stopappserver script does not stop application server during its startup. Wait until application server is running before running the stopappserver script.

The following are Redcell’s process monitor commands:

startpm -- Starts the process monitor and a managed server instance

stoppm -- Stops the process monitor and a managed server instance

pmstartall -- Starts a managed server instance

pmstopall -- Stops a managed server instance

pmgetstatus -- Reports the status of a managed server instance


If you execute startpm manually, issuing nohup before doing it is a safety precaution to ensure it is not interrupted when a user logs off a host. For example:

nohup startpm&

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 Java.exe.

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.

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.