Supported Configurations: Microsoft Windows XP
This section provides the following information:
Oracle support for Windows XP is limited to the following:
Support for use of WebLogic Server remote Java clients, including RMI clients, JMS clients, IIOP clients, Web Services clients, to call services hosted on a separate WebLogic Server server instance, typically hosted on a remote machine. Client Only support does not include Web Server plug-in support. All protocols supported by current WLS remote Java clients are included. Use with and without SSL is included. Client Only support does not include the ability to run a WebLogic Server server instance to host applications/services.
Support for use of WebLogic Server for development and unit testing of applications on a single development machine, is restricted by the SDK license. The SDK license allows up to 5 IP connections to the server since the server has been started. Support includes installing WLS, configuring/upgrading a single server domain, starting the server, using the WLS Console to administer the domain, developing/compiling/deploying applications, and unit testing of the application from the same machine, or up to 5 different machines with separate IP addresses. Support also includes the ability to perform all of the above on a small (such as a two cluster managed server) cluster that runs on a single development machine. The ability to configure clusters and deploy clustered applications is supported, but in general cluster runtime features are not included in development support. For example, cluster load balancing, state replication, and failover features are not included. Performance stress testing and Web Server plug-ins are not supported.
Oracle E-Delivery
or Oracle Technology Network.
http://www.microsoft.com
.
If you are performing a complete install of a WebLogic product (e.g. WebLogic Server, WebLogic Portal) by using the generic installer (.jar) on a platform where Eclipse is not supported or not installed, you might encounter a situation where the generic installer will go into a repeated loop condition. If you are experiencing this condition refer to the Installation Guide, specifically the "Install Eclipse Location Options" section for more information on how to handle the installation.
A Serial Version UID Mismatch Issue may be encountered if you deploy an application on a latest JVM but compiled with an earlier JDK release.
Workaround: To be compatible with the serialization of previously compiled applications, modify the <BEA_HOME>\wlserver_10.3\common\bin\commEnv.cmd
file to include the following command:
JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"
Note: If you intend to deploy new applications with previously compiled applications, they must be recompiled as necessary to have the same Serial Version UID.
For information about known issues with products supported on this configuration, including available workarounds, see the appropriate Release Notes document.
WebLogic Server Known and Resolved Issues:
|
|
WebLogic Portal Release Notes:
|
|
WebLogic Integration Release Notes:
|
|
Workshop for WebLogic Release Notes:
|
You can download Oracle WebLogic products from either the Oracle Technology Network website or the Oracle E-Delivery website.
Oracle E-Delivery
and use the following information to select the WebLogic Media Pack and Part Numbers for download:.jar
or .exe files
.
make sure that your WL_HOME variable is set to the directory in which you installed your product, and export WL_HOME. For example, $ WL_HOME=<your installation directory>/wlserver_10.3