Q1. What is the difference between Weblogic Version 3.2 and Standard Edition v3.3?
Q2. In what area do I need to tweak Standard Edition v3.3 to make it work with Weblogic?
Q3. Do we need to change Web.xml or Weblogic.xml?
Q4. Will there be any change to the Application? There should not be, but I would like to confirm.
Standard Edition 3.3 works with essentially any Java application server, and that definitely includes WebLogic Server, all the way from WLS 7 to WLS 10.3.* (aka "Oracle WebLogic 11g").
Generally you do not need to tweak Standard Edition at all for use with WLS; it uses the same web.xml that it would use with any other app server (declare the servlet filter and map it over all URLs), and it doesn't need a weblogic.xml. The only cases where we have found a need for weblogic.xml are more complex applications that depend on additional third-party libraries -- e.g. examples/net and federation/examples/* -- where we want to ensure that WLS will use the third-party libraries that are included in the application's WAR file rather than conflicting versions of those libraries that may already be present in WLS, so we use a weblogic.xml to specify <prefer-web-inf-classes>true</prefer-web-inf-classes>. This is NOT needed for normal Standard Edition functionality; it is only needed to avoid JAR-version hell in sample applications that depend on some extra third-party libraries.
The reason that Standard Edition works with essentially any Java app server is that Standard Edition integrates with each Java web application (as a servlet filter), _not_ with the app server (in fact the app server is oblivious to the presence of Standard Edition). By contrast, WebLogic Edition integrates into the app server (WebLogic Server) using WLS-specific SPIs, as a WebLogic SSPI Authenticator and as an IdentityAsserter. This provides tighter integration with WLS and can be useful in some more complex scenarios, e.g. for using Kerberos (QSJ) to authenticate EJB calls. In contrast to Standard Edition, the WebLogic Edition code must be installed into the WLS instance.