Use Commands to Start, Stop, and View Status of Processes
You can control software processes using script commands.
You use script commands to start, stop, and view component status.
Start Component Processes in a Domain
Learn about how to start all component processes within a domain.
Assumptions
-
The start command starts Node Manager locally if not already running.
-
The start command runs only from the primary host.
-
The start command doesn't complete until component processes are started or fail consecutively to start the specified number of times in the
restartMaxValue
parameter (-m)
. -
Component processes start in order.
-
The command initially prompts for credentials and automatically creates a
boot.properties
file, so that subsequent runs don't require credentials.
-
You must have file system permissions, and know the boot identity credentials.
-
If the system is clustered across multiple servers, then the Node Manager on each server must be manually started (aside from the primary host) by running
DOMAIN_HOME/bin/startNodeManager.sh
. On Windows, don't start Node Manager as a service in a multi-node, clustered deployment because the system doesn't work in this case.
Permanently Change the Maximum Number of Attempts for Restarting System Components
You can permanently configure the number of times that the Node Manager tries to restart the System Components.
When System Components started by the Node Manager fail, the process automatically attempts to restart them until the maximum number of restart attempts is reached. The default maximum number of restart attempts is set to 5000, but this default value might be too large in cases when the process keeps failing, and you might want the process to fail sooner to avoid using unnecessary resource consumption in the restart attempts (for example, for CPU, memory, or hard disk generated core files disk consumption). You can permanently decrease the number of times that the Node Manager attempts to restart System Components.
You can permanently configure the startup script to use a maximum restart value
that you specify instead of using the default value of 5000. You change the maximum restart
value by customizing max_restart_value
in the startup script.
Note:
As the administrator, you're responsible for making backups and maintaining customizations. Unless specifically noted, patches to the system might overwrite your customizations. Ensure that you back up any files before editing them, and when editing, comment out original code rather than removing it.Stop Component Processes in a Domain
Learn about how to stop running component processes within a domain.
Assumptions
-
The stop command stops Node Manager locally and remotely on clustered servers in the command.
-
The stop command runs only from the primary host.
-
The stop command continues until all specified component processes are shut down.
-
The stop command initially prompts for credentials and automatically creates a boot identity file, so that subsequent runs don't require credentials.
-
Stopping specific process may cause failover, so familiarize yourself with Scale Your Deployment.
Node Manager must be running. The nodemanager.properties
file must include QuitEnabled=true
.
You must have file system permissions, and know the system administrator identity credentials to boot Oracle WebLogic Server.
View the Status of Components in a Domain
Use the status command to view a report displaying the status of components within a domain.
Assumptions
-
The status command reports node manager status.
-
The status command only runs from the primary host.
-
The status command requires the local node manager process to be running.
-
The first run prompts you for credentials, and automatically creates a boot identity file so that subsequent runs don't require credentials.
Prerequisites
You must have file system permissions, and know the boot identity credentials.