Ritu,
Can you tell whether it is production or not and availability of physical servers for the same
Please refer
http://dev2dev.bea.com/pub/a/2004/07/WLSAdmin_bpr.html Deploy user applications on managed server instances. This separates the administration application (console) and the domain configurations from user applications. Avoid using automatic deployment of applications in production and multiple-server environments. Running the WebLogic domain in "Production Mode" will disable the automatic deployment in production. If you create scripts for deploying applications as a part of an overall build, consider using the wldeploy
Ant task.
If you deploy an application (or module) with the On Future Redeploys option set to Ignore Roles and Policies From DD one or more times before setting it to Initialize Roles and Policies From DD, you can set security policies and security roles using the admin console. But these changes using admin console will override security specified in deployment descriptors.
Tips
* Use production mode to run production applications.
* Avoid deploying user applications on admin server instance.
* To specify the server's default Web application, use an empty context-root element or an element with a value "/" in the weblogic.xml or application.xml file.
* Changing security policies for an application after deployment in the admin console overrides the policies in the deployment descriptor.