Derek — WebLogic Remote Console

The WebLogic Remote Console (WRC) is an Electron + Java/Helidon app distributed as a Linux AppImage. The Electron frontend has chrome-sandbox setuid issues on some Linux setups; the Java backend can be run headlessly instead.

AppImage Location

/home/john/pl/DB/weblogic-remote-console-2.4.19-linux.AppImage

Running the Backend Headlessly

Extract the AppImage and run just the Java/Helidon backend — the full WRC UI is a web app served by it:

# Extract AppImage (one-time; /tmp is lost on reboot)
/home/john/pl/DB/weblogic-remote-console-2.4.19-linux.AppImage --appimage-extract
mv squashfs-root /tmp/

# Run the backend
/tmp/squashfs-root/customjre/bin/java -jar /tmp/squashfs-root/backend/console.jar > /tmp/wrc.log 2>&1 &

# Find which port it bound to
grep -i 'port\|listen\|started' /tmp/wrc.log
# Typically port 8012 — browse to http://localhost:8012

Adding a Provider (WebLogic Connection)

In the UI choose "Add Admin Server Connection". Providers are stored in ~/.config/weblogic-remote-console/user-projects.json.

Port 7001 on lab hosts is opened to the controller IP by deploy_weblogic_ldap.yml — connect directly to http://<host>:7001, no SSH tunnel required.

Known Issues

"The domain is experiencing REST communication issues between servers" — this banner appears in all single-server (non-clustered) domains and is benign. WRC health-checks inter-server REST calls which don't apply with a single managed/admin server. It does not block configuration or change activation.

Activating Changes

Changes go into a pending queue. To commit: click the shopping cart icon → "Activate Changes". WLS writes config.xml and restarts affected subsystems.