Starting Instances of WebLogic Server

In the following table, WL_HOME refers to the top-level installation directory for WebLogic Server, such as c:\Oracle\Middleware\wlserver_10.3\.

Table A-1 Starting Server Instances

To Start

Do The Following

The MedRec server

Invoke:

WL_HOME\samples\domains\medrec\bin\startWebLogic.cmd (Windows)

WL_HOME/samples/domains/medrec/bin/startWebLogic.sh (UNIX)

The server starts as an Administration Server in the medrec domain.

On Windows, you can start the Medical Records Server from the Start menu (WebLogic Server > Examples > Start Medical Records Server). By default, the username for the medrec domain is set to weblogic and the password is welcome1.

The MedRec server (Spring version)

Invoke:

WL_HOME\samples\domains\medrec-spring\bin\startWebLogic.cmd (Windows)

WL_HOME/samples/domains/medrec-spring/bin/startWebLogic.sh (UNIX)

The server starts as an Administration Server in the medrec-spring domain.

On Windows, you can start the Medical Records Server (Spring version) from the Start menu (WebLogic Server > Examples > Start Medical Records Server (Spring version)). By default, the username for the medrec domain is set to weblogic and the password is welcome1.

The Examples server

Invoke:

WL_HOME\samples\domains\wl_server\bin\startWebLogic.cmd (Windows)

WL_HOME/samples/domains/wl_server/bin/startWebLogic.sh (UNIX)

The server starts as an Administration Server in the wl_server domain.

On Windows, you can start the Examples Server from the Start menu (WebLogic Server > Examples > Start Examples Server). By default, the username for the wl_server domain is set to weblogic and the password is welcome1.

An Administration Server that you have created

Invoke:

DOMAIN_NAME\bin\startWebLogic.cmd (Windows)

DOMAIN_NAME/bin/startWebLogic.sh (UNIX)

where DOMAIN_NAME is the name of the directory in which you located the domain, typically MW_HOME\user_projects\domains\DOMAIN_NAME.

NOTE: In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly on the Administration Server. In a production environment, you typically create Managed Servers to run applications.

On Windows, the Configuration Wizard creates a shortcut on the Start menu to start the Administration Server that you created (User Projects > DOMAIN_NAME > Start Admin Server for WebLogic Domain ).

Managed Servers

Start the domain's Administration Server.

Start the Node Manager on the computer that will host the Managed Server you want to start.

The WebLogic Server custom installation process optionally installs and starts Node Manager as a Windows service on Windows systems.

If it's not already running, you can start Node Manager manually at a command prompt or with a script. See "Starting Node Manager" in the Node Manager Administrator's Guide for Oracle WebLogic Server.

On Windows, you can use a shortcut on the Start menu to start the Node Manager (WebLogic Server > Tools > Node Manager).

On Windows, you can stop the Medical Records Server, Medical Records Server (Spring version), Examples Server, and Administration Servers that you have created using the Configuration Wizard, from the Start menu.

Scripting on this page enhances content navigation, but does not change the content in any way.