WebLogic Deployment Projects Three ways

There are typically three ways to deploy a project in WebLogic: First, install the deployment in the console, second, deploy the deployment package in the domain Autodeploy directory, and third, deploy the project using the config file in the domain, config.

Console deployment

1 Start the WebLogic service, log in to the WebLogic console page, enter your username and password, and log in to the console

2 Click on the left side of the deployment

3 Click the Install button on the right to prepare for the project installation

4 See the Path input box below to select the location of the project you want to deploy

5 You can also directly enter the location of the package to be deployed, hit enter

6 Click Next to

7 continue to the next step

8 Click the Finish button

9 Saving settings for the previous steps

10 when the save is complete, you will see a prompt to activate the change, and no restart is required.

11 then you can test, enter the project name, see the project's Welcome page, the project deployment is successful.

If the previous steps are complete, but you still cannot access the project, you can refer to the following supplemental steps

Supplemental steps

1 Click Deploy, tick on project, click Start

After 2 to start, the project status is active and the health status is OK, continue the test.

Autodeploy Automatic Deployment

There is no need to log in to the console for automatic deployment, there is a autodeploy directory under the domain's home directory, and you can copy the project package directly under the Autodeploy directory.

Autodeploy directory There is a Readme.txt document, open to see, here to pick the first paragraph out

[HTML]View PlainCopy

1. This Autodeploy directory provides a quick-to-deploy applications
2. to a development server. When the WebLogic Server instance is running
3. In development mode, applications and modules in the This directory is
4. Automatically deployed.

What is the main thing to say, is the development mode below, when WebLogic is started, the items under the Autodeploy directory are automatically deployed.

Drop the deployment package Servletdemo.war to the Autodeploy directory, start Startweblogic.cmd, Servletdemo access, and you can still see

Welcome page.

Config configuration file deployment

The. config file is under the Config directory of the domain, and Config. Metabase is primarily configured with some information about domain domains

Where do we deploy the project, and where to configure it?

[HTML]View PlainCopy

2. <? xml version= '1.0 ' encoding=' UTF-8 '?>
3. <Domainxmlns="Http://xmlns.oracle.com/weblogic/domain"Xmlns:sec="Http://xmlns.oracle.com/weblogic/security"xmlns:wls= "http://xmlns.oracle.com/weblogic/security/wls " xmlns:xsi=" http://www.w3.org/2001/ Xmlschema-instance " xsi:schemalocation="/http Xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd  http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/ weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/ Domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security  http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls  http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd ">&NBSP;&NBSP;
5. <name>base_domain</name>
7. <domain-version>12.1.3.0.0</domain-version>
9. <security-configuration>
11. <name>base_domain</name>
13. <realm>
15. <sec:authentication-provider xsi:type="Wls:default-authenticatortype">
17. <sec:name>defaultauthenticator</sec:name>
19. </sec:authentication-provider>
21. <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/ Passwordvalidator " xsi:type="pas:system-password-validatortype ">
23. <sec:name>systempasswordvalidator</sec:name>
25. <pas:min-password-length>8</pas:min-password-length>
27. <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters >
29. </sec:password-validator>
31. </Realm>
33. <default-realm>myrealm</default-realm>
35. <credential-encrypted>{aes}xlpxh4gct6jertb+toxrz1pqpas+mgmuqnnxzu/ Osxwmqtb8152ggdbulhksxugc9f959ol7tizyziu9xdeajlkk9vau9cqlcklluaumyl5ty4c0uuja99b14er7oiu4</ credential-encrypted>
37. <node-manager-username>weblogic</node-manager-username>
39. <node-manager-password-encrypted>{aes}n3lldgmasocproyurffr2wawolez6kdfsp7+gByNeo8= </node-manager-password-encrypted>
41. </security-configuration>
43. <server>
45. <name>adminserver</name>
47. <listen-address></listen-address>
49. </Server>
51. <embedded-ldap>
53. <name>base_domain</name>
55. <credential-encrypted>{AES}21Z8VCICBUAYQSSJ5T5+Y6QVEY8DE3NDNR0ZDG+K3EDWWEUBZK9VMX79DI43OXQX </credential-encrypted>
57. </embedded-ldap>
59. <configuration-version>12.1.3.0.0</configuration-version>
61. <admin-server-name>adminserver</admin-server-name>
63. </domain>

Our project deployment information is added between Configuration-version and Admin-server-name

[HTML]View PlainCopy

2. <configuration-version>12.1.3.0.0</configuration-version>
4. <app-deployment>
6. <name>servletdemo</name>
8. <target>adminserver</target>
10. <module-type>war</module-type>
12. <source-path>c:\users\zhangqi\desktop\servletdemo</source-path>
14. <security-dd-model>ddonly</security-dd-model>
16. </app-deployment>
18. <admin-server-name>adminserver</admin-server-name>

At the beginning of the config file configuration files deployment, there are 404, modified the next configuration can be

Unzip the deployed war package as a folder, and then

Change the war in <module-type>war</module-type> to dir

[HTML]View PlainCopy

2. <app-deployment>
4. <name>servletdemo</name>
6. <target>adminserver</target>
8. <module-type>dir</module-type>
10. <source-path>c:\users\zhangqi\desktop\servletdemo</source-path>
12. <security-dd-model>ddonly</security-dd-model>
14. <staging-mode>nostage</staging-mode>
16. </app-deployment>

You can then start the WebLogic service.

Three deployment methods can achieve the purpose of the deployment project, as for the pros and cons of three deployment methods, say it tomorrow.

The previous blog post WebLogic Three ways to deploy a project, including installing the deployment in the console, placing the deployment package in the domain Autodeploy directory, deploying the project using the config file in the domain, config. In the development environment and the formal production environment, how to choose how to deploy, here according to their own experience, provide a little reference.

Console deployment

This can be used in this general formal production environment or test environment. At this point, you need to modify the operating mode of the WebLogic to production mode, put the deployment package into a unified place for management, installation, update, delete deployment directly in the console, easy to monitor.

Autodeploy

This development with a little more, easy to manage. When developing, it is convenient to copy the project directly under Autodeploy and then 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 not be good to get the files through some absolute paths in the project, so that the war package can be decompressed into a folder for easy file reading. At development time, it is convenient to copy the modified files directly under the Autodeploy directory via ant or other tools.

Config configuration deployment

The configuration deployment of Config. Autodeploy is similar, except that Autodeploy automatic deployment must place the project's deployment package under the Autodeploy directory, but the deployment package for the config deployment can be put anywhere. This approach is also used in the development environment, the individual does not recommend this way, because each time a new project is deployed, you have to go to the domain to find config, and then modify the risk of error is too large, rather than directly use Autodeploy way.

With the analysis above, the deployment is deployed using the console in production , and the deployment is configured in development using autodeploy or config . In development, if you use Eclipse for development, you can integrate the WebLogic plug-in, start the WebLogic directly in Eclipse, stop, and refer to the Eclipse installation WebLogic plugin.

WebLogic Deployment Projects Three ways