Contributions from the community to the WebLogic Remote Console project help us build a better experience together. You can contribute by raising a bug or enhancement request or by submitting pull requests to address an issue yourself.
Open an issue in the WebLogic Remote Console GitHub repository that describes the issue you plan to address or the enhancement request.
If you only want to file an enhancement request, you can stop here - you’re done! Thank you for helping to improve WebLogic Remote Console.
If you want to fix an issue yourself, you must sign the Oracle Contributor Agreement (OCA) before you can submit a pull request. For instructions, see the Oracle Contributor Agreement.
Fork the WebLogic Remote Console GitHub repository.
Create a branch in your forked repository and implement your changes. Include the issue number in your branch’s name. For example, 1234-fixlink.
Test your changes. Build WebLogic Remote Console as described in Build from Source.
If the base image was changed, update the samples.
Commit your changes. Make sure to include a git commit signoff that lists your name and the email address that matches its entry in the OCA Signatories list. For example, Signed-off-by: Your Name you@example.org. You can add this automatically by adding the –signoff option to your git commit command: git commit–signoff. We cannot merge pull requests from contributors who have not signed the OCA.
Submit the pull request. Include a link to its related issue and describe what you hope to accomplish with your changes and how to validate them.
Thank you for your contribution. We will assign reviewers to your pull request.
If you want to contribute to the WebLogic Remote Console project or just want a better understanding of how WebLogic Remote Console works, then you can generate the project from its source code to create a local build.
Make sure the following software is installed in your local environment.
java -version
mvn --version
node -v
Install the Oracle JET 15.1.0 client libraries.
In Windows environments, run:
npm install --location=global @oracle/ojet-cli@~15.1.0
In Linux or macOS environments, run:
sudo npm install --location=global @oracle/ojet-cli@~15.1.0
You can run ojet –version to verify it installed correctly.
Clone the WebLogic Remote Console repository from the WebLogic Remote Console GitHub repository.
Open a command-line interface and navigate to the home directory of the cloned repository.
Run mvn clean install.
After the build finishes, confirm that /installer/target/console.zip was created.
From the home directory of the repository, run the build-electron.sh script.
The WebLogic Remote Console executable file is created under /electron/dist/.
You can choose to run WebLogic Remote Console from within a browser.
We do not recommend using the browser application to manage domains. It has significant limitations in both security and functionality and should be used for development purposes only.
You must have a modern internet browser installed to run WebLogic Remote Console in the browser.
Build WebLogic Remote Console from its source code. Follow the instructions at Build from Source.
Copy /installer/target/console.zip to a new directory and extract its contents.
Open a command window and navigate to the new directory.
Run java -jar console.jar.
Open a browser window and enter http://localhost:8012 in the address bar.
Connect to a provider and you can manage it as you would in the regular WebLogic Remote Console.
To end the session, enter Ctrl+C in the command window.
Unsaved changes made in the browser application do not persist after you close the browser tab. If you accidentally close or refresh the browser tab, you may lose all of your changes. Changes to an Administration Server provider remain in a pending state and can generally be recovered in a new session. Changes to WDT model files, WDT Composite files, and property lists are lost if you do not click Download File at the end of your session.