Weblogic deployment project in three ways, weblogic in three ways

Weblogic deployment project in three ways, weblogic in three ways

There are three methods to deploy a project in weblogic: first, install and deploy the project in the console; second, deploy the deployment package in the autodeploy directory in the domain; and third, use the config file in the domain. xml for project deployment.

Console deployment

1. Start the weblogic service, log on to the weblogic console page, enter the user name and password, and log on to the console.

 

2. Click deployment on the left.

 

3. Click the Install button on the right to install the project.

 

4. The path input box is displayed. You can select the location of the project to be deployed below.

 

5. Enter the location of the package to be deployed and press Enter.

6. click Next.

7. continue to the next step

8. Click Finish.

9. Save the settings in the previous steps.

10. After saving the changes, you will be prompted to activate the changes without restarting.

11. Then you can perform the test. Enter the project name and you will see the welcome page of the project, that is, the project is successfully deployed.

If the previous steps are completed, but the project still cannot be accessed, you can refer to the following supplementary steps.

Procedure

1. Click deploy, select projects, and click Start.

2. When the project status is active and the health status is OK, continue the test.

Autodeploy automatic deployment

You do not need to log on to the console during Automatic deployment. There is an autodeploy directory under the main directory of the domain. You can directly copy the project package to the autodeploy directory.

There is a readme.txt file in the autodeploydirectory. open the file and read the first section.

This autodeploy directory provides a quick way to deploy applicationsto a development server. When the WebLogic Server instance is runningin development mode, applications and modules in this directory are automatically deployed.

In the development mode, when weblogic is started, the project under the autodeploy directory is automatically deployed.

Drop the deployment package servletDemo. war to the autodeploy directory, start startWeblogic. cmd, and access the servletDemo.

Welcome Page.

Config. xml configuration file deployment

The config. xml file is under the config directory of the domain. config. xml mainly configures some information about the domain.

Where should we configure the project to be deployed?

  base_domain  12.1.3.0.0      base_domain                  DefaultAuthenticator                    SystemPasswordValidator        8        1              myrealm    {AES}xLPXh4gcT6JErTB+toxRZ1pQpAS+MGMuqnnXzu/OsxWMQTB8152ggdbUlhkSXUGC9f959oL7tIzyZiu9XdeajlkK9vAu9cQlCKLLUaUMyl5Ty4C0uuJA99b14eR7oIu4    weblogic    {AES}n3LLdgmAsocPRoYUrFfR2waWOlEz6KDFsp7+gByNeo8=       AdminServer            base_domain    {AES}21z8vCiCbuaYqsSj5t5+y6qvEY8dE3NdNr0zDG+K3EdwWEubzk9Vmx79Di43oxqX    12.1.3.0.0  AdminServer

The project deployment information is added between configuration-version and admin-server-name.

12.1.3.0.0    servletDemo  AdminServer  war  C:\Users\ZhangQi\Desktop\servletDemo  DDOnly      AdminServer

When you first deploy the config. xml configuration file, 404 is displayed. You can modify the configuration.

Decompress the deployed war package as a folder, and then

WarChangeDirYou can.

 

  servletDemo  AdminServer  dir  C:\Users\ZhangQi\Desktop\servletDemoDDOnlynostage

Start the weblogic service.

The three deployment methods can achieve the purpose of project deployment. For the advantages and disadvantages of the three deployment methods, see:

 

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 myeclipse is used for development, You can integrate the weblogic plug-in to start and stop weblogic directly in myeclipse. For details, refer to the previous blog.