Weblogic 10 Server Compatibility

BEA attempts to support binary and source-level compatibility between the current version of WebLogic Server and all versions as far back as 8.1 in the areas of persistent data, generated classes, and API compatibility. In some cases, it is impossible to avoid incompatibilities. Where incompatibilities arise, they are fully documented in the Upgrading WebLogic Application Environments guide.

Java EE 5 Compatibility

BEA WebLogic Server 10.0 is JEE5 compatible. This compatibility allows a Java EE 5 compliant application to be developed on one operating system platform, and deployed for production on another, without requiring Java EE 5 application code changes. BEA ensures this compatibility of Java EE 5 application portability within a WebLogic Server release level.

Generated Classes Compatibility

With one exception, upgrading to WebLogic Server 10.0 does not require you to recompile applications in order to create new generated classes.

The 10.0 version of the EJBGen utility recognizes only JDK 5.0 metadata annotation-style EJBGen tags and not the old Javadoc-style tags. This means that source files that use the Javadoc-style tags must be upgraded to use the equivalent annotation, and then recompiled using the 10.0 version of EJBGen.

Compatibility Within a Domain

• All WebLogic Server instances within the same Administrative domain must be at the same major and minor version. You cannot mix server versions within a domain.


• Servers within an Administrative domain can be at different Service Pack levels as long as the Administration Server is at the same Service Pack. Level or higher than its Managed Servers.


• All servers within a cluster must be at the same Service Pack level.

JMX Compatibility

See JMX 1.2 Implementation in Upgrading WebLogic Application Environments.

Persistent Data Compatibility

Upgrading to WebLogic Server 10.0 does not require you to make any changes to WebLogic Server 8.1, 9.0, 9.1, or 9.2 persistent data storage, including configuration files, deployment descriptors, transaction logs, and JMS messages.

API Compatibility

WebLogic Server 8.1, 9.0, 9.1, and 9.2 applications deployed on WebLogic Server 9.2 will function without modification. Exceptions to this rule include cases where API behavior was changed in order to conform to a specification or to fix incorrect behavior. In certain circumstances, a correction may cause your application to behave differently.

Protocol Compatibility

Interoperability between WebLogic Server 10.0 and WebLogic Server 8.1, 9.0, 9.1 and 9.2 is supported in the following scenarios:

• A WebLogic Server 8.1, 9.0, 9.1 or 9.2 client can invoke RMI-based applications hosted on a WebLogic Server 10.0 server using IIOP, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.


• A WebLogic Server 10.0 client can invoke RMI-based applications hosted on a WebLogic Server 8.1, 9.0, 9.1 or 9.2 server using IIOP, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.


• A WebLogic Server 10.0 Web server plug-in can proxy to the latest service pack release of a 8.1, 9.0, 9.1 or 9.2 server.

Interoperability between WebLogic Server 7.0 and WebLogic Server 10.0 is supported in the following scenarios. You will need the WebLogic Server 7.0 patch that is associated with CR295275 for this interoperability to work. This patch is applicable to WLS 7.0 SP6 and WLS 7.0 SP7. You can request this patch by contacting BEA support and requesting the patch associated with CR295275. Additionally, for RMI/IIOP interoperability support, start the WLS 7.0 client using the following flag: -Dweblogic.system.iiop.enableClient=true

• A WebLogic Server 7.0 client can invoke RMI-based applications hosted on a WebLogic Server 10.0 server using T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.


• A WebLogic Server 10.0 client can invoke RMI-based applications hosted on a WebLogic Server 7.0 server using T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.


• A WebLogic Server 10.0 Web server plug-in can proxy to the latest service pack release of a 7.0 server.

Oracle Workshop for WebLogic 10g R3

Oracle Introduced Weblogic 10.3g with lot of additional features.And Workshop version 10.3 is supported by Windows Vista also.

Added Features :

1. Support for Java Enterprise Edition 5
Workshop support for Java EE5 includes support for the following technologies:

Servlet 2.5
JSP 2.1
JSF 1.2
JSTL 1.2
EJB 3.0
JAX-WS
JAXB 2.0

2. Built on Eclipse 3.3.2 and Web Tools Platform 2.0.3
3. Supported by Windows Vista
4. XMLBeans 2.3
5. WorkSpace Studio launcher has been discontinued.
6. Provide a tool to Upgrade from 8,9.2 to 10.3g
7. DbXplorer and DBXaminer for working with databases and etc..

If you want more information ,check here:

Oracle Workshop for WebLogic™10.3
Download Weblogic Server 10.3g
Download Free Oracle Weblogic Worksho 10.3g
Upgarding Tutorial from 8.1 to 10.3g
Oracle 10.3g Tutorial

Oracle gives this software for free of cost now .........

FAST : The System Error 1069 has occured

This error comes because of the user Privileges.
During the installation of the FAST Server,it will automatically create 2 windows services(FAST SEARCH,FAST Web Server).It resides in OS start up scripts.

User Should have the full admin Privileges to start these services.If it doesn't have it,system though out the error message like "System Error 1069 has occured".

Solution :

Users are added in Local User's & Groups when they logged in with OS.

-> Contrl Panel -> Adminstrative Tools -> Computer Management
-> Local User's & Groups -> Users.

Just click the corresponding user to view/edit their Credentials.

Right Click -> Properties


Here we can see five options like :
1. User Must Change Password in Next Login
2. User Can't Change Password
3. Password Never Expire
4. Account is Disabled
5. Account Locked Out

To start these services we should change the follwing credentials like :
-> Password Never Expired : Checked
-> Account Locked Out : UnChecked