[원격에서 업로드 배포]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -deploy -upload d:\app_root\app\TestWebApp
[Application 배포]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -deploy -name myTestDeployment -source /myDeployments/myApplication.ear -targets myCluster -stage -plan /myDeployments/myAppPlan.xml
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -deploy -name myTestDeployment -source /myDeployments/myApplication.ear -targets ManagedServer-1,ManagedServer-2 -stage -plan /myDeployments/myAppPlan.xml
[Version Identifier]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -deploy -name myTestDeployment -source /myDeployments/myApplication/91Beta -targets myCluster -stage -appversion 91beta
[New Version]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -redeploy -name myTestDeployment -source /myDeployments/myApplication/1.0GA -targets myCluster -stage -appversion 1.0GA -retiretimeout 300
[Display Version Information for Deployed Applications]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -listapps
[Redeploy]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -redeploy -name myTestDeployment -source /myDeployments/myApplcation/1.0GA -retiretimeout 300
[Undeploy]
java weblogic.Deployer -adminurl localhost:7001 -user weblogic -password weblogic -undeploy -name myTestDeployment -appversion .91Beta
Distributing Applications to a Production Environment
Distributing an application prepares it for deployment by copying its deployment files to all target servers and validating it. After you distribute an application, you can start it in Administration mode, which restricts access to the application to a configured Administration channel and allows you to distribute the application to a production environment (or distribute a new version of an application) without opening the application to external client connections.
While in Administration mode, you can connect to an application only via a configured Administration channel. This allows you to perform final (“sanity”) checking of the application directly in the production environment without disrupting clients. After performing final testing, you can either undeploy the application to make further changes, or start the application to make it generally available to clients.
You can use the -adminmode option application in Administration mode. For information, see Starting a Distributed Application in Administration Mode.
Distributing an Application
To distribute an application, use the weblogic.Deployer -distribute command, as in:
java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password weblogic -distribute -name myTestDeployment
/myDeployments/myApplication/
Starting a Distributed Application in Administration Mode
After WebLogic Server distributes the deployment files, you can start the application in Administration mode so that you can access and test it via a configured Administration channel. To configure an administration channel, see Configuring Network Resources in Designing and Configuring WebLogic Server Environments.
To start a distributed application in Administration mode, use the -start command with the -adminmode option:
java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password weblogic -start -adminmode -name myTestDeployment
/myDeployments/myApplication/
Starting a Distributed Application
After performing final testing of a distributed application using a configured Administration channel, you can open the application to new client connections by using the weblogic.Deployer -start command without the -adminmode option:
java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password weblogic -start -name myTestDeployment
Example usage of weblogic deployer utilityDeploy application on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -deploy c:/myapps/myapp.ear
Deploy individual modules in application to different targets:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -targets mywar@webserver,myjar@ejbserver -deploy c:/myapps/myapp.ear
Undeploy application from specified targets:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -undeploy -targets server1,server2..
Redeploy application on current targets:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -redeploy
Redeploy individual module in an application:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -redeploy -targets moduleA@serverA,moduleA@serverB
Partially redeploy, for example, to update a JSP in a exploded webapp:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -redeploy mywar/index.jsp
The path of JSP to be updated is relative to the root of the application.
If a directory is specified the entire subtree is updated.
Multiple servers sharing the same physical deployment:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -targets server1,server2 -nostage -deploy c:/myapps/myapp.ear
The -nostage option indicates that the application is available
on all target servers at the same path and hence server should not copy
files to the managed servers.
Deploy the first application version on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -deploy c:/myapps/myapp_v1.ear
Perform Production Redeployment of a new application version on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -redeploy -source c:/myapps/myapp_v2.ear
Deploy application to administration mode on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -deploy c:/myapps/myapp.ear -adminmode
Transition application from administration mode to running on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -start
Transition application from running to administration mode on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name myapp -stop -adminmode
Deploy a library on admin server:
java weblogic.Deployer -adminurl url -username username -password password -name mylib -library -libspecver 1.0 -libimplver 2.0 -deploy c:/myapps/mylib.jar
Deploy an application on admin server with a deployment plan:
java weblogic.Deployer -adminurl url -username username -password password -plan c:/myapps/myapp/plan/plan.xml -deploy c:/myapps/myapp/app/myapp.jar
Update an application configuration:
java weblogic.Deployer -adminurl url -username username -password password -plan c:/myapps/myapp/plan/newplan.xml -name myapp -update
Deploy a queue to a specific JMS server
java weblogic.Deployer -adminurl url -username username -password password -submoduletargets myqueue@myjmsmodule@JMSServer -deploy c:/myapps/myapp/app/myapp.ear