To start the Administration Server:

1. Go to the Domain_home/bin directory.
2. Enter the following command:

   ./startWebLogic.sh
   

3. If you selected a production startup mode, you are prompted for the login credentials of the Administrator user.

You can create a boot identity file to bypass the need to provide a user name and password when starting the Administration Server in production mode. For more information, see "Creating a Boot Identity File for an Administration Server" in Oracle Fusion Middleware Administering Server Startup and Shutdown for Oracle WebLogic Server.

To start Node Manager:

1. Go to the Domain_home/bin directory.
2. Enter the following command:

   ./startNodeManager.sh
   

Oracle recommends that you install Node Manager to run as a startup service, which allows Node Manager to start up automatically each time the system restarts. For more information about installing a per domain Node Manager service, see "Running Node Manager as a Startup Service" in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.

Before starting your managed servers for the first time, copy the Domain_home/security/SerializedSystemIni.dat file from the Administration Server to the same directory on each managed server.

To start a managed server:

1. Log in to the target system.
2. Go to the Domain_home/bin directory.
3. Enter the following command:

   ./startManagedWebLogic.sh managed_server_name admin_server_url
   

   where:

   • managed_server_name is the name of the managed server you want to start.
   • admin_server_url is the full URL of the Administration Server.

The following shows sample commands for starting occas_server_1 and occas_server_2:

./startManagedWebLogic.sh occas_server_1 t3://host.example.com:7001 &
./startManagedWebLogic.sh occas_server_2 t3://host.example.com:7001 &

For more information about starting managed servers, see "Starting and Stopping Managed Servers" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.