Installing and Configuring WLS-VE: Main Steps
Preparing for the Installation
Understanding Machine Roles
Verifying That Your Environment Supports WLS-VE
Planning Your Virtualized Installation
Determining Appropriate Applications for WLS-VE
Designing a File Storage Solution
Understanding the WLS-VE Storage Architecture
Storage for Exclusive File Access
Storage for Shared File Access
WLS-VE ISO Image Considerations
Planning System Capacity
Determine Disk Space Requirements
Determine the Number of Physical Machines
Determine Physical Memory Requirements
Downloading WLS-VE
DVD Distribution
Windows and Linux Installers
Understanding User Access Credentials
WebLogic Server Credentials
VMware VirtualCenter Credentials
NFS Server
Understanding WLS-VE Directories
Creating and Sharing Directories
Example Configuration of Directory Shares
Example of Accessing Directory Shares from Windows
Alternative Installation Approach
WLS-VE Installation Directories
The BEA Home Directory
Sharing the BEA Home Directory with Other BEA Products
Structure of the WLS-VE BEA Home Directory
The WLS-VE Product Installation Directory
Structure of the WLS-VE Product Installation Directory
The Installation Directory for the WLS-VE ISO Image
The WLS-VE Windows Shortcuts
Using the Installation Program
Starting the Installation Program on Windows Platforms
Starting in Graphical Mode
Starting in Console Mode
Starting the Installation Program on Linux Platforms
Starting Graphical-Mode Installation
Starting Console-Mode Installation
Starting the Installation Program in Silent Mode
Startup Options
Generating a Verbose Installation Log
Specifying Temporary Disk Space
What's Next?
Copying the ISO Image
Configuring System Security
WLS Security Measures
NFS Security Measures
VMware VirtualCenter Security Measures
Configuring LiquidVM Connection Parameters
Before You Begin
Configuring LiquidVM in the Graphic Mode
Configuring LiquidVM in the Console Mode
The bea.lvm.info File
Troubleshooting a LiquidVM Configuration
Configuring and Starting WLS-VE Domains
Before You Begin
Ensure Proper Components are in Place
Comparing Startup, Configuration, and Logging Options to Non-virtualized WLS
Creating WLS-VE Domains
Other VM Configuration Properties
Configuring Group and User Names
DemoIdentity Keystore Warning
Upgrading and Promoting Domains
Upgrade from a Non-virtualized WebLogic Server 9.2 to WLS-VE 9.2
Upgrade from an Earlier Version of WebLogic Server to WLS-VE 9.2
Moving a WebLogic Server VE Domain To a Production Environment
Starting WLS-VE
From the Command Line
From VirtualCenter
Stopping WLS-VE
Additional Configuration Tasks
Tuning LiquidVM
WLS-VE Configuration Properties
Deploying an Application to WLS-VE
Installing and Updating License Files
About BEA Product Licenses
Updating Your license.bea File
Updating license.bea Using the UpdateLicense Utility
Upgrading Licenses from Previous Software Releases
Installing Licenses for Use with Promotional DVD Distributions
Uninstalling the Software
About the Uninstallation Program
Uninstalling Your Software in Graphical Mode
Uninstalling Your Software in Console Mode
Deleting the ISO Image File
Reinstalling Your Software
Working with WLS-VE Using VirtualCenter
Setting Up VMware and Enabling SSL
Starting (and Stopping) WLS-VE
Editing VM Properties
Pausing a VM
Working with the Console Tab
Inactive Keyboard
Console Log
Pre-console Log
Diagnostics and Troubleshooting
Troubleshooting WLS-VE Problems
Troubleshooting Common WLS-VE Issues
"Could not find the disk" Error
"Could not lookup NFS server" Error
"Could not ping NFS server" Error
"(Mount Daemon) not registered" Error
"Failed to open conslog" Error
The Server Shuts Down Soon After Startup I
The Server Shuts Down Soon After Startup II
"multiple gid provided only one allowed" Error
"uid=# must be a number" Error
"Configured IP [...] in use by MAC" Error
Troubleshooting WebLogic Server Issues
Other WebLogic Server Problems
Troubleshooting LiquidVM Issues
Handling Suspend Files
Displaying Version Information
Reporting a Problem to BEA Support
Trouble Reporting Process Overview
Identify Your Problem Type
Verify That You're Running a Supported Configuration
Collect Enough Information to Define Your Issue