# Release Notes

# WebLogic Server Virtual Edition Release Notes

This document includes information about the following topics:

- What's New in WebLogic Server Virtual Edition 9.2v1.1
- Known and Resolved Issues

## What's New in WebLogic Server Virtual Edition 9.2v1.1

The following sections summarize the new features and enhancements in this release of WebLogic Server Virtual Edition:

- Support for Virtual Local Disks
- Improved Security

### Support for Virtual Local Disks

LiquidVM 1.1 provides a virtual local disk for each virtual machine. This removes the dependence on NFS and provides faster, more secure file transfers. The local disk can be mapped to a SAN attached to the ESX server. For more information, see Using the Virtual Local Disk in the WLS-VE Configuration and User Guide.

### Improved Security

LiquidVM 1.1 provides a built-in SSH server that provides a secure mechanism to transfer files, including WebLogic domains, both to and from the LiquidVM instance on the hypervisor host. The SSH server supports the following:

- AES-128 encryption protocol
- Temporary random password generation by default for the first login
- Public/private key authentication
- Auditing

For more information, see Using the LiquidVM SSH Service in the WLS-VE Configuration and User Guide.

### Performance Improvements

This release includes the following performance improvements:

- Simplified Java heap configuration and improved memory efficiency. You no longer need to use a minimum Java heap size setting (`-Xms`) because adaptive optimizations ensure the heap automatically grows under high memory pressure and shrinks when it is no longer needed.
- Improved disk I/O performance with virtual local disks.

## Known and Resolved Issues

This following table describes problems that have been identified in this release of WLS-VE. Where applicable, a Change Request Number is specified for the problem. These Change Request Numbers enable BEA and users to monitor the status of issues while solutions are being developed. Entries include a description of the problem, and a workaround or solution where appropriate.

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
| Limited scaling from additional virtual CPUs. While WLS-VE supports multi-processor virtual machines, using multiple processors does not improve performance to the extent it does with non-virtualized WLS server instances. |  |
| When you install WLS-VE, the installer generates a DemoIdentity keystore that includes a certificate for the host that runs the installer. This is not the host from which you will run the WLS-VE. The installer then stores this certificate on the ISO. If SSL is used, this certificate is the default if no other certificate is specified. When you launch WLS-VE, it uses the IP address for the virtual machine, not the IP address of the installation machine. WebLogic Server generates a warning that the hostname is not the same as the host for the certificate. You can ignore this warning and the machine will run normally. |  |
CR316773 | Using Ctrl-C to shut down a WLS-VE server instance in the Virtual Infrastructure Client console window can cause an error: `Error connecting: VMX Connection handshake failed for mks of /vmfs/volumes/<volume-id-string>/<WLS-VE instance name>/<WLS-VE instance name>.vmx` `Do you want to try again?` This error is harmless and can be ignored. | 9.2 v1.0 |
CR322574 | The uninstallation program reports servers as running, even though they have been shut down. You get the following message: `Uninstaller has detected at least one server is running. It is recommended to shutdown all running servers before uninstallation. Do you want to continue? If yes, certain files will not be uninstalled.` Workaround: Delete the file `domain_name/servers/server_name/tmp`, and then run the uninstallation program. | 9.2 v1.0 |
CR322659 | When you shut down an Administration or Managed Server using the WLS Administration Console, the following message is displayed: `The administration server is shutting down, and the console is no longer available. You will have to manually start the Administration Server using the node manager or a command line to continue administering this domain.` You cannot use Node Manager with WLS-VE. Instead, you should restart the servers by pressing Power On in the Virtual Infrastructure Client or by executing the start scripts. For more information about starting servers, see Starting and Stopping WLS-VE in the WLS-VE Configuration and User Guide. | 1.0 |
CR353914 | Windows Start menu entries that are created by the domain Configuration Wizard cannot be used to start and stop WLS-VE servers. Workaround: Edit the start scripts as required for your configuration and execute the scripts from the command line. For more information, see Creating and Copying WLS-VE Domains in the WLS-VE Configuration and User Guide. | 1.0 |
CR354408 | The `weblogic.policy` file that resides in the ISO image, and which is copied to the virtual machine, contains pathnames for the machine on which you executed the installation program. These pathnames will not work on the virtual machine. Workaround: If you are using the Java Security Manager, create a new `weblogic.policy` file and copy it to the local disk on the virtual machine. | 1.0 |
CR355553 | When a local disk is created for the LVM, the current working directory defaults to `/domain` on the local disk. If the `weblogic.RootDirectory` refers to another directory, either on an NFS mount or on the local disk, application deployments can fail, particularly if the application contains web services. Workaround: Edit the start script to ensure that the current working directory parameter (`cwd`) matches the `weblogic.RootDirectory`. | 1.1 |
CR356210 | When enabling log rotation for a WLS server running in development mode, limiting the number of rotated files that can accumulate should default to `true` if `<number-of-files-limited>` is not explicitly set. However, this default behavior is not occurring. Workaround: Explicitly set `<number-of-files-limited>` to `true` if a file limit is to be enforced. | 1.1 |
CR357340 | LiquidVM launcher does not recognize spaces in pathnames. Workaround: Do not use pathnames that contain spaces in the server start scripts, such as `C:\Documents and Settings`. | 1.1 |
CR358159 | When you create a domain using the Configuration Wizard, the `readme_wlsve.txt` created in the `BEA_HOME``\user_projects\domains\``DOMAIN_NAME` directory contains information that is not correct if you are using the virtual local disk. Workaround: Refer to the instructions in Creating and Copying WLS-VE Domains in WLS-VE Configuration and User Guide. | 1.1 |