Weblogic project deployment method selection analysis and weblogic deployment

Weblogic project deployment method selection analysis and weblogic deployment

In the previous blog, I wrote three methods to deploy the weblogic project, including installing and deploying on the console, placing the deployment package under the autodeploy directory in the domain, and using the configuration file config in the domain. xml for project deployment. In the development environment and formal production environment, how should we select the deployment method? Here, based on my own experience, I would like to provide some reference.

Console deployment

This method can be used in a general formal production environment or test environment. In this case, you need to change the weblogic running mode to the production mode, and place the deployment package in a unified place for management, installation, update, and deletion. The deployment is directly performed on the console to facilitate monitoring.

Autodeploy

This development process is more convenient to manage. During development, copy the project to autodeploy and start the weblogic service. Considering that the weblogic service does not automatically decompress the war package (which is not as good as tomcat), it may be difficult to obtain files from some absolute paths in the project, in this case, you can decompress the war package into a folder to facilitate file reading. During development, you can use ant or other tools to directly copy the modified files to the autodeploy Directory, which is convenient.

Config. xml configuration and deployment

Config. xml configuration deployment is similar to autodeploy. The difference is that autodeploy automatic deployment must put the project deployment package under the autodeploy directory, but the config. xml configuration deployment package can be put anywhere. This method is also used in the development environment, which is not recommended by individuals, because every time a new project is deployed, you have to go to the domain to find the config. xml configuration, and then modify it. The error risk is too high. It is better to use autodeploy directly.

After the above analysis,ProductionUsed inConsole deployment,DevelopmentUsed inAutodeploy or config. xml configurationDeployment. If eclipse is used for development, You can integrate the weblogic plug-in to start and stop weblogic directly in eclipse. For details, refer to installing the weblogic plug-in eclipse.