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

This Autodeploy directory provides a quick-to-deploy Applicationsto a development server. When the WebLogic Server instance was Runningin development mode, applications and modules in this directory are Automatica Lly 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?

<?xml version= ' 1.0 ' encoding= ' UTF-8 '? ><domain xmlns= "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 "> <name >base_domain</name> <domain-version>12.1.3.0.0</domain-version> <security-configuration > <name>base_domain</name> <realm> <sec:authentication-provider xsi:type= "Wls:default-authenticatortype" > <sec:name>DefaultAuthenticator</sec:name> </sec:authentication-provider> <sec:password -validator xmlns:pas= "Http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type= "pas: System-password-validatortype "> <sec:name>SystemPasswordValidator</sec:name> <pas:min-pass Word-length>8</pas:min-password-length> <pas:min-numeric-or-special-characters>1</pas: min-numeric-or-special-characters> </sec:password-validator> </realm> <default-realm>myrea Lm</default-realm> <credential-encrypted>{aes}xlpxh4gct6jertb+toxrz1pqpas+mgmuqnnxzu/ osxwmqtb8152ggdbulhksxugc9f959ol7tizyziu9xdeajlkk9vau9cqlcklluaumyl5ty4c0uuja99b14er7oiu4</ Credential-encrypted> <node-manager-username>weblogic</node-manager-username> <node-manager-password-encrypted>{aes}n3lldgmasocproyurffr2wawolez6kdfsp7+gbyneo8=</ node-manager-password-encrypted> </security-configuration> <server> <name>adminserver</ name> <listen-address></listen-address> </server> <embedded-ldap> <name>base_doma In</name> <credential-encrypted>{aes}21z8vcicbuayqssj5t5+y6qvey8de3ndnr0zdg+ K3edwweubzk9vmx79di43oxqx</credential-encrypted> </embedded-ldap> <configuration-version> 12.1.3.0.0</configuration-version> <admin-server-name>adminserver</admin-server-name></ Domain>

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

<configuration-version>12.1.3.0.0</configuration-version>  <app-deployment>  <name >servletDemo</name>  <target>AdminServer</target>  <module-type>war</ module-type>  <source-path>C:\Users\ZhangQi\Desktop\servletDemo.war</source-path>  < security-dd-model>ddonly</security-dd-model>    </app-deployment>  <admin-server-name >AdminServer</admin-server-name>

You can then start the WebLogic service.

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

It's too late today, sleep, good night!

WebLogic Deployment Projects Three ways