WebLogic Server Command Reference
If the Administration Server fails while Managed Servers continue to run, or if you shut down the Administration Server while Managed Servers continue to run, you lose the ability to change the configuration or deploy modules to any server in the domain. To regain this administrative ability, you must restart the Administration Server. By default, an Administration Server finds the last known set of Managed Servers and re-establishes a connection.
If the Administration Server is unable to automatically re-establish a connection to one or more Managed Servers during its startup cycle, you can use this command to re-establish administrative control.
For example, you might have started a Managed Server in the
STANDBY state and did not resume the Managed Server before restarting the Administration Server. The Administration Server discovers only Managed Servers that are in the
java [ SSL Arguments ] weblogic.Admin
[ User Credentials Arguments ]
If you do not specify a server, the Administration Server will discover and re-establish control over all the Managed Servers that are known to be running but disconnected from administrative services.
Forces the Administration Server to use a secure protocol. Without this option, the Administration Server uses the t3 protocol. If you disable a Managed Server's non-SSL listen port, you must specify this option.
For more information about the environment in which this example runs, refer to Example Environment.
In the following example, a Managed Server is configured to listen on port 7021, but you used the
-Dweblogic.ListenPort startup option to temporarily change the listen port to
8201. The following command instructs the Administration Server to re-connect to MedRecManagedServer, which is listening on port 8201: