Answer Posted / vru

Functionally these two products are fairly close except for some minor differences in supported standards.

While WebSphere tends to focus more on integration, connectivity, and web services - WebLogic has in the past focused more on emerging J2EE standards and ease-of-use.

Because of WebSphere's rich implementations of J2EE it is a little more involved, but benefits with better performance, more extensive integration and transaction management

In terms of transaction WebLogic is having default transaction attribute as "Supports", but WebSphere does not have any default transaction attribute.

WebSphere strictly follows the J2EE architecture

What is the difference between jboss and weblogic?

987

---

Explain the performance tuning in jdbc?

983

---

How do I prevent errors when running t3dbping? : BEA Weblogic

883

---

How do clients handle dns requests to failed servers?

974

---

What is the local interface used by web logic server?

950

---

Can the messaging bridge handle two-phase or global transactions between separate weblogic server domains or between different releases? : BEA Weblogic

1005

---

How are multi-byte characters used with weblogic jdriver?

999

---

What are the ways in which the dns request of failed servers handled?

985

---

In corba, which of the files generated by the idltojava compiler must be compiled before running the server application? : BEA Weblogic

1019

---

Difference between production and development mode?

968

---

What is the default thread stack size in windows?

1000

---

What are class paths? How can they be set?

1051

---

A client wants to preserve the reference to the ejbhome object of an enterprise bean instance and use it later. Which of the following can be serialized for this purpose? : BEA Weblogic

998

---

How can I control on which weblogic server(s) my application will run? : BEA Weblogic

929

---

How is security handled in the weblogic j2ee connector architecture? : BEA Weblogic

913

---