Starting Managed Servers with a Startup Script

A Managed Server is a WebLogic Server instance that runs deployed applications. It refers to the Administration Server for all of its configuration and deployment information. Usually, you use Managed Servers to run applications in a production environment.

For more information about Managed Servers and Administration Servers, see "Understanding WebLogic Server Domains" in Understanding Domain Configuration.

If you use one of the Configuration Wizard templates that WebLogic Server provides, your domain directory includes a start script named startManagedWebLogic that you can use to start Managed Servers. You can use this script to start all the Managed Servers in a cluster.

For more information on domain directory files, see "Domain Configuration Files" in Understanding Domain Configuration.

This script does not use the Node Manager to start and manage the server. Instead, it uses a Java command to invoke the weblogic.Server class, which is the main class for a WebLogic Server instance. For information about invoking weblogic.Server in a Java command, see "weblogic.Server Command-Line Reference" in WebLogic Server Command Reference.

To use the WebLogic Server scripts to start Managed Servers:

• Refer to Starting Servers: Before You Begin for prerequisite tasks.

• If you have not already done so, create one or more Managed Servers.

See Creating WebLogic Domains Using the Configuration Wizard or "Create Managed Servers" in the Administration Console Online Help.

• Start the domain's Administration Server.

• In a shell (command prompt) on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogic script:
  DOMAIN_NAME\bin\startManagedWebLogic.cmd (Windows)
  DOMAIN_NAME/bin/startManagedWebLogic.sh (UNIX)

where DOMAIN_NAME is the directory in which you located the domain. By default, this directory is BEA_HOME\user_projects\domains\DOMAIN_NAME.

• Enter one of the following commands:

• startManagedWebLogic.cmd managed_server_name admin_url (Windows)
• startManagedWebLogic.sh managed_server_name admin_url (UNIX)

where managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name or IP address) and port number of the domain's Administration Server.

For example, the following command uses startManagedWebLogic.cmd to start a Managed Server named myManagedServer. The listen address for the domain's Administration Server is AdminHost:7001:

c:\bea\user_projects\domains\mydomain\bin\startManagedWebLogic.cmd myManagedServer http://AdminHost:7001

• For each Managed Server that you want to start, open a separate command shell and follow steps 4 and 5. If you are starting Managed Servers on another machine, log in to that machine (remotely or locally) and then follow steps 4 and 5.

For information on running Managed Servers on a remote WebLogic Server host, see "How Do I: Create and Start Managed Servers on a Remote Machine" in Create Templates and Domains Using the Pack and Unpack Commands.

For information on configuring a connection to the Administration Server, see Configuring Managed Server Connections to the Administration Server.

The startManagedWebLogic script does the following:

• Calls the startWebLogic script, which sets the environment variables by invoking WL_HOME\user_projects\domains\DOMAIN_NAME\bin\setDomainEnv.cmd (setDomainEnv.sh on UNIX), where WL_HOME is the location in which you installed WebLogic Server.

• Invokes the java weblogic.Server command, which starts a JVM that is configured to run a WebLogic Server instance.

 

　　If the shell (command prompt) in which you start the server is still open, you can type Ctrl-C

 

When the server successfully completes its startup process, it writes the following message to standard out (which, by default, is the command window):

<Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>