Free tools Windows power users keep installed
One-click scans. No signup required.
Use Oracle’s weblogic.Deployer utility to deploy an EAR, WAR, JAR, or Java EE library through a WebLogic Administration Server. The basic workflow is to connect to the Administration Server, specify the archive and target, and choose whether to deploy directly or upload a remote file. Add a deployment plan when the environment requires configuration overrides; for a controlled rollout, distribute the application, test it in administration mode, and then start it for clients.
What you need before deploying
- A reachable WebLogic Administration Server and its URL, such as
http://localhost:7001. - Credentials authorized to deploy applications.
- An EAR, WAR, JAR, or library package, plus any deployment plan you intend to apply.
- A configured target, such as a server or cluster. The target determines where WebLogic runs the deployment.
Run weblogic.Deployer from a WebLogic environment where the utility is available. The Administration Server is the deployment control endpoint; it is not necessarily the machine where you run the command.
Deploy an application archive
For a file accessible to the Administration Server, pass the archive path with -deploy. Supply -name if you want a deployment name independent of the filename; otherwise WebLogic derives the default name from the archive name. Oracle documents the command options and basic deployment workflow in its deployment guide and weblogic.Deployer reference.
java weblogic.Deployer -adminurl http://localhost:7001
-username weblogic -password '***'
-deploy -name myTestApplication /path/to/myApplication.earReplace the sample URL, account, and file path with your environment’s values. Avoid leaving a real password in shell history or scripts; use your organization’s approved credential-handling method.
#1 Best Overall
Deploy a file from a remote client
If the archive is on the client machine and is not accessible at the path seen by the Administration Server, add -upload so WebLogic transfers it to the server before deployment:
java weblogic.Deployer -adminurl http://admin.example:7001
-username weblogic -password '***'
-deploy -upload /local/path/myapp.earUse a direct path without -upload when the archive is already visible to the Administration Server, for example on a shared or mounted filesystem. The distinction is about file accessibility from the server side, not simply whether the command is being run remotely.
Choose a target and apply a deployment plan
Use -targets to specify a configured server, virtual host, comma-separated server list, or cluster. For example, this command deploys an archive to a cluster, stages it, and applies an environment-specific plan:
java weblogic.Deployer -adminurl http://localhost:7001
-username weblogic -password '***'
-deploy -name myTestDeployment
-source /deployments/myApplication.ear
-targets myCluster -stage
-plan /deployments/myAppPlan.xmlThe plan supplies deployment configuration for the target environment. It and the WebLogic deployment descriptors must define a valid target configuration: required resource bindings cannot be left null, or deployment fails. Oracle explains plan configuration and deployment behavior in its deployment guide and deployment-plan documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
A cluster target generally means deployment to every server instance in that cluster. Oracle notes that deployment can fail if an available cluster member cannot deploy the application. Check the target configuration and the status of all relevant members when a cluster deployment does not complete.
Use a staged rollout for controlled testing
Instead of making a deployment available to clients immediately, separate distribution, testing, and activation. Oracle documents this command-line sequence for controlled rollout:
Rank #4
- Distribute the application: use
-distributeto copy the application to the target servers without starting it. - Start in administration mode: use
-start -adminmodeto allow controlled testing through an administration channel. - Open it to clients: after testing, use
-startto make the application available to clients.
When a deployment plan is used, the plan and generated descriptors are copied with the application sources into target staging directories. See Oracle’s deployment guide for the deployment and staging options.
Register a shared Java EE library
A Java EE library can be a standalone Java EE module, a group of modules packaged in an EAR, or a plain JAR registered with the application container. Deploy it with -library and target it to the same server instances that will run applications that reference it.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11java weblogic.Deployer -adminurl http://localhost:7001
-username weblogic -password '***'
-deploy -targets myserver1,myserver2
-library /deployments/myLibraryApplication/If the library or optional package has no version strings in its manifest, specify -libspecver and -libimplversion. If the command-line version values conflict with versions in the manifest, deployment fails. Oracle’s deployment guide covers library deployment options, and its Java EE library documentation describes library registration.
Use model-driven automation for repeatable deployments
For deployments generated from repeatable configuration models, Oracle WebLogic Deploy Tooling provides a deployApps command. It accepts an Administration Server URL, user, Oracle home, model file, variable file, and archive file. This approach is useful when a team manages deployment configuration as reusable model and variable files rather than assembling each deployment command by hand. See Oracle’s Deploy Tooling deployApps documentation.
Quick Recap
Which command-line approach fits?
| Need | Approach |
|---|---|
| Archive is accessible to the Administration Server | Use -deploy with the archive path. |
| Archive is on the client and must be transferred | Add -upload. |
| Environment-specific deployment settings | Use -plan and validate required resource bindings. |
| Controlled test before client access | Use -distribute, then -start -adminmode, then -start. |
| Application must run on a cluster | Use -targets with the cluster name and ensure cluster members can deploy it. |
| Reusable Java EE library | Deploy with -library and target the servers that run referencing applications. |
| Repeatable, model-based deployments | Consider Deploy Tooling’s deployApps command. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
