Hi all,
Here is a quick view of a differences between Production and Development mode of Weblogic server.
Development mode:
- The default JDK for development domain is Sun Hotspot.
- Admin Server uses an automatically created boot.properties during startup
- The debugFlag which is used to start the WebLogic Workshop Debugger is enabled.
- You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL. For more information about managing security, see "Configuring SSL" in Securing WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/secmanage/ssl.html
- WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain).It is recommended that this method be used only in a single-server development environment.For more information, see "Auto-Deploying Applications in Development Domains" in Deploying Applications to WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/deployment/deploy.html#autodeploy.
- When you start a server, the server automatically renames (rotates) its local server log file as server-name.log.n. For the remainder of the server session, the server rotates its local log file whenever the size of the file reaches 500 kilobytes.
Production mode:
- The default JDK for production domain is JRockit
- If you use the demo certificates for SSL a warning is displayed
- Admin Server prompts for username and password during startup
- The default maximum capacity for JDBC Datasource is 25
- The debugFlag which is used to start the WebLogic Workshop Debugger is disabled.
- The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the WebLogic Deployer tool, or the WebLogic Scripting Tool (WLST)
- A server rotates its local log file after the size of the file reaches 5000 kilobytes. When the server is configured for production mode, by default, all versions of the log files are retained. Administrators may want to customize the number of log files retained.
Feel free to add more
Have a nice day,
Zeeshan Baig
Another related post:
ReplyDeletehttp://oraclefusionfacts.blogspot.com/2011/06/weblogic-server-development-mode-vs.html
jrockit it is not necessarily the default jdk in production environments simply because on some platform jrockit is not available.
ReplyDeleteAlso in development mode, jre mode is -client and in production mode it's -server.
Log levels also change between both modes and AFAIK default number of threads in the thread pool
Thanks for additional info.
ReplyDeleteZeeshan
In production mode jsp page_check_seconds is -1 which means updated jsps, even those deployed outside the autodeploy directory, are not detected.
ReplyDeleteHowever, in development mode, you can edit a jsp, again even those deployed by means other than dropping in autodeploy dir, and they will be recompiled and served.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/weblogic_xml.html#wp1038491
Hi Zeeshan,
ReplyDeleteIt might not be relevent question here but let me ask what is the basic difference between Weblogic console and the Enterprise manager.
Thanks
Salman Dasti
Hi,
DeleteThere is no such difference. From 12c release both tools can do the similar functionality. In console you can setup JDBC datasources, JMS Queues and Security Providers. In EM you can start and stop services and configure other security features such as KEY Maps and other stuff. Both can be used to start and stop servers.
Hope it helps.
Zeeshan