Specifications

VMware and BEA WebLogic Solutions Deployment Guide
122
machine retains the identity and settings of the original physical machine. These include: machine name,
SID, hard disks (partitions), data files, application and user settings. This process does not require the P2V
Assistant or a helper machine (physical or virtual). It does require that the cloned disk be detached from the
helper virtual machine, if that was used.
If you plan to run the new virtual machine on the same network as the original source machine, you need to
modify the identity (name, IP address, and networking) of the virtual machine so the machines can co-exist
on the same network.
Note: While the P2V Assistant simplifies the physical-to-virtual migration process by automating
several steps, it is not intended to serve as an unattended migration tool for casual use. Migration is
complex — and whether using the P2V Assistant or not, only technical system administrators with a
good understanding of and familiarity with operating systems, drivers, imaging tools, and VMware
products should attempt the physical-to-virtual migration process.
Fundamentally, you need the following components to perform P2V:
1. The source system – physical system with the OS and BEA WebLogic Server applications
configured
2. A Virtual Machine (also known as helper VM) on the current ESX Server host running the same OS
as the source system (recommended). P2V assistant will be installed on this helper virtual
machine.
3. A new Virtual Machine that will be the final destination for the post P2V virtual environment.
8.1 Installing VMware P2V Assistant
Create a new VM with Windows 2003 EE SP1 loaded on it. This VM is called the helper VM and P2V
assistant will be installed on this VM. (In our lab, we decided to use our base image VM (BEAVMBase) for
this purpose)
Download the P2V assistant software executable. Start the installation.