WebLogic Extension for VS Code
A VS Code extension for managing Oracle WebLogic Server domains on Windows. Covers server lifecycle, application deployment, JDWP debugging, web resource publishing, JVM configuration, and JDBC data source management — without leaving the editor.
Getting Started
Prerequisites
First-Time Setup
- Open VS Code.
- Launch the Setup Wizard using
Ctrl+Alt+W, or open the Command Palette (Ctrl+Shift+P) and search for WebLogic: Run Setup Wizard.
- Follow the wizard to set your Oracle Middleware home and Java home. The wizard scans for existing domains automatically.
- Once setup is complete, domains discovered during setup are available to add as servers directly from the wizard.
Adding a Server
Open the Oracle WebLogic Servers panel in the Explorer sidebar. Click Add WebLogic Server and choose one of:
- Select existing domain — pick from domains auto-discovered under your middleware home.
- Browse — navigate to any valid domain directory (must contain
config/config.xml and bin/).
- Create new domain — create a domain using WLST and add it immediately.
- Duplicate domain — copy an existing domain to a new directory with a different port.
The extension reads credentials directly from the domain's config.xml — no manual username or password entry required.
Opening the Extension
The Oracle WebLogic Servers tree view appears in the VS Code Explorer sidebar. It lists all configured servers, their status, and their deployed applications.
Supported Functionality
| Area |
What you can do |
| Server lifecycle |
Start, stop, restart, sync, clean with redeploy |
| Domain setup |
Create domain, duplicate domain, import existing domain |
| Credentials |
Auto-extracted from domain config; no manual entry |
| Deployment |
Deploy / undeploy / redeploy EAR, WAR, JAR |
| Web publish |
Push static/web files to running deployment instantly |
| Auto-publish |
Publish on save with configurable debounce |
| Debugging |
JDWP attach with auto Java project detection |
| JVM memory |
Preset or custom heap / metaspace settings |
| JVM properties |
Add/edit/remove -D system properties |
| Data sources |
Create, import, delete Oracle JDBC sources |
| Logs |
Open Admin Server, domain, and application logs in editor |
| Admin console |
Open in browser directly from the tree |
| Port management |
Change admin port on stopped servers |
Limitations
- Windows only — the extension has been developed and tested on Windows. macOS and Linux are not officially supported.
- Admin Server focused — the extension manages the Admin Server. There is no dedicated UI for starting or stopping individual Managed Servers.
- Credential storage — server credentials (username and password) are stored in VS Code's
globalState. They are not stored in the OS keychain or a secrets manager.
- HTTP only by default — the REST client and admin console link use HTTP. HTTPS is not configured by default.
- Oracle data source form — the guided creation form is Oracle-only. MySQL, PostgreSQL, and SQL Server data sources must be added by importing an existing
*-jdbc.xml descriptor.
- No cluster-aware deployment — applications are deployed targeting the Admin Server. Cluster targets must be configured manually in
config.xml after deployment.
- No graphical monitoring — the extension reports server state (running, stopped, etc.) and application state but does not provide heap charts, thread metrics, or other runtime statistics.
- Web resource publish requires a known deployment mapping — publish works for applications deployed through this extension. Applications deployed by other tools require a one-time source folder configuration step.
- Port conflict detection is extension-scoped — conflicts are detected only between servers registered in this extension. An external process occupying the same port will not be identified as the cause.
- Domain creation uses the default WebLogic template — the create-domain flow does not expose a template picker. Custom domain templates are not supported through the UI.
- WLST required for credential extraction and deployment — WLST ships with WebLogic but must be accessible via the configured Middleware home.
Configuration
| Setting |
Type |
Default |
Description |
weblogic.defaultDomainPath |
string |
"" |
Default directory for WebLogic domains |
weblogic.javaHome |
string |
"" |
Java installation directory |
weblogic.middlewareHome |
string |
"" |
Oracle Middleware home directory |
weblogic.showOutputOnStart |
boolean |
true |
Show the output panel when starting a server |
weblogic.autoPublish.enabled |
boolean |
false |
Automatically publish web resources on file save |
weblogic.autoPublish.delay |
number |
500 |
Debounce delay in milliseconds before auto-publish fires (100–5000) |
weblogic.debug.javaProjectName |
string |
"" |
Global Java project name override for debugger attach. Leave blank for per-server auto-detection. |
weblogic.debug.enableCacheLogs |
boolean |
false |
Enable verbose WLST cache logging in the output channel (diagnostic use only) |
All settings are available via File > Preferences > Settings under WebLogic Server.
Keyboard Shortcuts
| Action |
Shortcut |
| Add Server |
Ctrl+Alt+A |
| Refresh |
Ctrl+Alt+R |
| Toggle Auto-Publish |
Ctrl+Alt+P |
| Run Setup Wizard |
Ctrl+Alt+W |
| Open Domain Folder |
Ctrl+Alt+E |
| Deploy Application |
Ctrl+Alt+D |
| Start Server |
Ctrl+Alt+S |
| Stop Server |
Ctrl+Alt+X |
| Open Admin Console |
Ctrl+Alt+, |
| View Admin Log |
Ctrl+Alt+L |
Author
Naomi Parte
License
Copyright (c) 2026
All rights reserved.
| |