# Configuration and User Guide

# Starting and Stopping WLS-VE

The following topics describe how to start and stop virtualized servers in a WebLogic domain.

- Starting WLS-VE
- Starting the Administration Console
- Stopping WLS-VE Instances

## Starting WLS-VE

When you convert a physical WebLogic domain to a WLS-VE domain using the P2V utility, scripts to start WLS-VE instances on the virtual machine are created in the `/virtual` directory generated by the P2V utility, as shown in Table 7-1:

Table 7-1 P2V-generated Start Scripts
Platform | Start Script Names
--- | ---
Windows | `DOMAIN_NAME``\virtual\` `start` `servername``.cmd` `commonVEStart.cmd`
Linux | `DOMAIN_NAME``/virtual/` `startservername``.sh` `commonVEStart.sh`

where `DOMAIN_NAME` is the directory name of the domain that was selected for virtualization, typically `BEA_HOME``\user_projects\domains\``DOMAIN_NAME``.`

The startup scripts also call the `commonVEStart.cmd` startup script in the `/virtual` directory. Therefore, when you start a WLS-VE instance, LiquidVM boots (in `active` mode) and simultaneously boots the associated server. For more information about LiquidVM, see Configuring LiquidVM Connection Parameters.

Note: | You can also start a LiquidVM instance in `passive` mode. In `passive` mode, only the LiquidVM services are started; the server is not started. For instructions about starting LiquidVM in passive mode, see Task 1: Start LiquidVM in Passive Mode.

Initially, the scripts must be run from a command-line to complete the P2V configuration process, After you have started a WLS-VE instance from the command-line at least once, you can restart it either from the command-line or from the VMware VI Client running on the ESX host.

Note: | You cannot start a WLS-VE server instance from the WLS Administration Console, nor can you use the Administration Console to resume or suspend a WLS-VE server instance. However, you can, and should, use the Administration Console to shut down a WLS-VE server instance.

### Starting WLS-VE from a Command-line

To start the WLS-VE instances and the LiquidVM launcher, follow these steps:

1. Open a command-line shell and navigate to the `DOMAIN_NAME``/virtual` directory containing the start scripts.
2. Execute the start command by entering the name of the server start script at the prompt. Sample start script commands are shown in Table 7-2.

Table 7-2 Running the Start Scripts
To . . . | Enter . . .
--- | ---
Start a WLS-VE Administration Server | Windows — `start` `AdminServerName``.cmd` Linux — `start` `AdminServerName``.sh`
Start a WLS-VE Managed Server | Windows — `start` `ManagedServerName``.cmd` Linux — `start` `ManagedServerName``.sh`

### Starting WLS-VE from the VMware VI Client

After you have started a virtual server from the command-line at least once, you can then start it from the VMware VI Client:

1. Log into the Virtual Infrastructure Client.
2. Use the Inventory panel to select the WLS-VE instance you want to start.
3. Do one of the following:

- Click the Power On button .
- Select the Summary tab and select Power On in the Commands pane.
- Right-click a machine on the Hosts and Clusters list and select Power On from the context menu that appears.

As the WLS-VE instance starts, a progress meter appears in the Recent Tasks pane.

Once WLS-VE has successfully started, the task status changes to Completed.

## Starting the Administration Console

After you have started a virtual Administration Server from the command-line at least once, you can start the Administration Console on the launcher machine to remotely administer and shut-down its managed WLS-VE instances.

To start the Administration Console, open a supported Web browser and open the following URL:

    http://hostname:port/console

where `hostname` is the DNS name or IP address of the Administration Server and `port` is the address of the port on which the Administration Server is listening for requests (7001 by default).

If you start the Administration Server using Secure Sockets Layer (SSL), you must add an “`s`” after `http` as follows:

    https://hostname:port/console

For detailed information about using the Administration Console, see the WLS Administration Console Online Help.

## Stopping WLS-VE Instances

Stopping WLS-VE instances should be carefully considered as the ripple effects of an improper shutdown can cause unexpected results, such as losing any underlying server connections, with no guarantee that these connections will be restored when the instance is restarted. For this reason, stopping WLS-VE instances using VirtualCenter is not recommended. If you must stop WLS-VE, use one of following methods:

- Use the WLS Administration Console for the machine and request the server to gracefully shutdown.

- For information on shutting down a server, see Shut Down a Server Instance and Control Graceful Shutdowns in the Administration Console Online Help.
- For information on gracefully shutting down the Managed Servers in a cluster, see Shut Down Servers in a Cluster in the Administration Console Online Help.

- Use WLST scripts to request the server to gracefully shutdown. For more information, see Shutdown in the WLST Command and Variable Reference.

Note: | Pressing Ctrl-C or clicking the Power Off button in the VI Client results in a forced WLS shutdown, similar to pressing Ctrl-C in a standard OS.