Diff B/W Development – Production

Development Mode
The default JDK for development domain is Sun Hotspot
You can use the demo certificates for SSL
Auto deployment is enabled
Server instances rotate their log files on startup
Admin Server uses an automatically created boot.properties during startup
The default maximum capacity for JDBC Datasource is 15
The debug Flag which is used to start the Weblogic Workshop Debugger is enabled

Production Mode
The default JDK for production domain is JRockit
If you use the demo certificates for SSL a warning is displayed
Auto deployment is disabled
Server instances rotate their log files when it reaches 5MB
Admin Server prompts for username and password during startup
The default maximum capacity for JDBC Datasource is 25
The debug Flag which is used to start the Weblogic Workshop Debugger is disabled

**********************************************************************

What is the difference between weblogic and WebSphere?

Though the functionality of these two products are closer, there are minor differences in the
standards that support.
These differences are:
1) WebSphere’s focus is more on connectivity, integration and web services whereas Web
Logic’s focus is more on emerging standards and ease-of-use of J2EE.
2) WebSphere’s performance is better in terms of implementations of J2EE is little more
involved, and supports more integration and transaction management to a great extent.
3) Weblogic is supported by default transaction attribute “Supports”, whereas WebSphere has
not default transaction attribute.
4) WebSphere strictly follows J2EE architecture

**********************************************************************
What is the differences between XA vs NON-XA Transactions?
An XA transaction, in the most general terms, is a "global transaction" that may span multiple
resources. A non-XA transaction always involves just one resource. 
An XA transaction involves a coordinating transaction manager, with one or more databases (or
other resources, like JMS) all involved in a single global transaction. Non-XA transactions have
no transaction coordinator, and a single resource is doing all its transaction work itself (this is
sometimes called local transactions). 

Most of the time we use non-XA - a Servlet or EJB or plain old JDBC in a Java application
talking to a single database. XA gets involved when you want to work with multiple
resources - 2 or more databases, a database and a JMS connection, all of those plus
maybe a JCA resource - all in a single transaction. Here, Weblogic will be acting as the
Transaction Manager, and your various resources (Oracle, Sybase, IBM MQ JMS, SAP,
whatever) acting as transaction resources. Your code can then
update/delete/publish/whatever across the many resources. When you say "commit",
the results are commit.
**********************************************************************