Skip navigation.

Supported Configurations: Microsoft Windows XP

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

WebLogic Platform 10.3 on Windows XP

This section provides the following information:

 


Support Restrictions for Windows XP

Oracle support for Windows XP is limited to the following:

Client Only Support

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.

Development Support

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.

Related Information

 


Configuration Requirements

Table 1-1 Requirements for Microsoft Windows XP SP2 on x86 

Operating System Version and Patches

Windows XP Service Pack 2 and later Service Packs

Chip Architecture and Minimum Processor Speed

x86 and compatible chip architectures (1.3 GHz)

JDK

JRockit 6.0 R27.6.0-50) JDK (32-bit) and all later 6.0 releases of JRockit

Sun Java 2 JDK 6.0 (32-bit) with Java HotSpotTM Client VM and all later service packs of 6.0 (version 1.6.0_05)

RAM

1 GB minimum, 2 GB recommended

Performance Pack

server\native\win\32

Product Support

  • WebLogic Server 10.3

  • WebLogic Portal 10.3

  • WebLogic Integration 10.3, WebLogic Integration 10.3.1

  • Workshop for WebLogic 10.3 (Runtime)

Design and Development Tools

  • Supported for design, development, and verification of applications.

  • Not supported for production server deployment.

  • Workshop for WebLogic 10.3 (IDE) on Sun Java 2 JDK 6.0: Supported


 

Table 1-2 Requirements for Microsoft Windows XP on 64-bit Xeon and AMD64 with 32-bit JDK

Operating System Version and Patches

Windows XP

Chip Architecture and Minimum Processor Speed

  • AMD64 (1.3 GHz)

  • 64-bit Xeon (1.3 GHz)

JDK

JRockit 6.0 R27.6.0-50) JDK (32-bit) and all later 6.0 releases of JRockit

Sun Java 2 JDK 6.0 (32-bit) with Java HotSpotTM Client VM and all later service packs of 6.0 (version 1.6.0_05)

RAM

1 GB minimum

Product Support

  • WebLogic Server 10.3

  • WebLogic Integration 10.3, WebLogic Integration 10.3.1

  • Workshop for WebLogic 10.3 (Runtime)


 

 


Known Issues

Doing a Complete Install With a Generic Installer

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.

Serial Version UID Mismatch

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.

Known Issues for Other Products

For information about known issues with products supported on this configuration, including available workarounds, see the appropriate Release Notes document.

Issues related to...

Are described in...

WebLogic Server

WebLogic Server Known and Resolved Issues:

http://download.oracle.com/docs/cd/E12840_01/wls/docs103/issues/index.html

WebLogic Portal

WebLogic Portal Release Notes:

http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/relnotes/index.html

WebLogic Integration

WebLogic Integration Release Notes:

http://download.oracle.com/docs/cd/E13160_01/wli/docs10gr3/relnotes/index.html

Workshop for WebLogic

Workshop for WebLogic Release Notes:

http://download.oracle.com/docs/cd/E13224_01/wlw/docs103/relnotes/index.html


 

 


Download and Installation Instructions

You can download Oracle WebLogic products from either the Oracle Technology Network website or the Oracle E-Delivery website.

  1. Download and install the JDK for your environment.
  2. Go to Oracle E-Delivery and use the following information to select the WebLogic Media Pack and Part Numbers for download:
  3. Install the product using the Installation Guide. Use the sections that describe the process of installing .jar or .exe files.
  4. For WebLogic Portal, make sure that your WL_HOME variable is set to the directory in which you installed your product, and export WL_HOME. For example,
  5. $ WL_HOME=<your installation directory>/wlserver_10.3

 

Skip navigation bar  Back to Top Previous Next