Skip to content

Commit c394289

Browse files
lfeigenlfeigen
committed
Initial checkin
0 parents  commit c394289

File tree

2,421 files changed

+275739
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

2,421 files changed

+275739
-0
lines changed

‎.gitignore

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
*~
2+
*#
3+
.#*
4+
**/*.iml
5+
**/*.bak
6+
**/.idea
7+
target/*
8+
target
9+
**/.classpath
10+
**/.project
11+
.classpath
12+
.project
13+
.settings
14+
**/.settings
15+
**/.settings/*
16+
release.properties
17+
**/pom.xml.releaseBackup
18+
*.hold
19+
.flattened-pom.xml
20+
CBE.out
21+
console-0.9-*
22+
# Ignore Mac DS_Store files
23+
**/.DS_Store
24+
runnable
25+
runnable/*
26+
frontend/coverage/**
27+
weblogic-bean-types/src/*
28+
frontend/node_modules
29+
frontend/staged-themes
30+
frontend/web
31+
frontend/.vscode/
32+
frontend/settings.json
33+
frontend/.DS_Store
34+
frontend/**/.idea
35+
frontend/libs
36+
frontend/src/css/images
37+
frontend/package-lock.json
38+
frontend/oraclejetconfig.json
39+
.vscode/*
40+
client.log.*
41+
/bin/
42+
weblogic-bean-info-harvester/build-*
43+
run/work
44+
fortify-output/**

‎CONTRIBUTING.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Contributing
2+
3+
Oracle welcomes contributions to this repository from anyone.
4+
5+
If you want to submit a pull request to fix a bug or enhance an existing
6+
feature, please first open an issue and link to that issue when you
7+
submit your pull request.
8+
9+
If you have any questions about a possible submission, feel free to open
10+
an issue too.
11+
12+
## Contributing to the WebLogic Server Remote Console repository
13+
14+
Pull requests can be made under
15+
[The Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) (OCA).
16+
17+
For pull requests to be accepted, the bottom of your commit message must have
18+
the following line using your name and e-mail address as it appears in the
19+
OCA Signatories list.
20+
21+
```
22+
Signed-off-by: Your Name <[email protected]>
23+
```
24+
25+
This can be automatically added to pull requests by committing with:
26+
27+
```
28+
git commit --signoff
29+
```
30+
31+
Only pull requests from committers that can be verified as having
32+
signed the OCA can be accepted.
33+
34+
### Pull request process
35+
36+
1. Fork this repository
37+
1. Create a branch in your fork to implement the changes. We recommend using
38+
the issue number as part of your branch name, e.g. `1234-fixes`
39+
1. Ensure that any documentation is updated with the changes that are required
40+
by your fix.
41+
1. Ensure that any samples are updated if the base image has been changed.
42+
1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
43+
what your changes are meant to do and provide simple steps on how to validate
44+
your changes. Ensure that you reference the issue you created as well.
45+
We will assign the pull request to 2-3 people for review before it is merged.

‎LICENSE.txt

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
Copyright (c) 2020 Oracle and/or its affiliates. All rights reserved
2+
3+
The Universal Permissive License (UPL), Version 1.0
4+
5+
Subject to the condition set forth below, permission is hereby granted to any
6+
person obtaining a copy of this software, associated documentation and/or data
7+
(collectively the "Software"), free of charge and under any and all copyright
8+
rights in the Software, and any and all patent rights owned or freely
9+
licensable by each licensor hereunder covering either (i) the unmodified
10+
Software as contributed to or provided by such licensor, or (ii) the Larger
11+
Works (as defined below), to deal in both
12+
13+
(a) the Software, and
14+
(b) any piece of software and/or hardware listed in the lrgrwrks.txt file if
15+
one is included with the Software (each a "Larger Work" to which the Software
16+
is contributed by such licensors),
17+
18+
without restriction, including without limitation the rights to copy, create
19+
derivative works of, display, perform, and distribute the Software and make,
20+
use, sell, offer for sale, import, export, have made, and have sold the
21+
Software and the Larger Work(s), and to sublicense the foregoing rights on
22+
either these or other terms.
23+
24+
This license is subject to the following condition:
25+
The above copyright notice and either this complete permission notice or at
26+
a minimum a reference to the UPL must be included in all copies or
27+
substantial portions of the Software.
28+
29+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
30+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
31+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
32+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
33+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
34+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
35+
SOFTWARE.

‎README.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
2+
# Oracle WebLogic Server Remote Console
3+
4+
The Oracle WebLogic Server Remote Console is a lightweight, open source console that you can use to manage your WebLogic Server domain running anywhere, such as on a physical or virtual machine, in a container, Kubernetes, or in the Oracle Cloud. The Remote Console does not need to be colocated with the WebLogic Server domain. You can install and run the Remote Console anywhere. You simply start the console server, display the console in your browser, and connect to the Administration Server of the domain using WebLogic REST APIs.
5+
6+
The Remote Console is fully supported with WebLogic Server 12.2.1.3, 12.2.1.4, and 14.1.1.
7+
8+
9+
## Key Features of the WebLogic Server Remote Console
10+
The WebLogic Server Remote Console provides an alternative WebLogic Server administration GUI that enables REST-based access to WebLogic management information, in alignment with current cloud-native trends. When connected to a WebLogic domain using the Remote Console, you can:
11+
* Configure WebLogic Server instances
12+
* Configure WebLogic Server clusters
13+
* Configure WebLogic Server services, such as database connectivity (JDBC), and messaging (JMS)
14+
* Deploy and undeploy applications
15+
* Start and stop servers and applications
16+
* Monitor server and application performance
17+
* View server and domain log files
18+
* View application deployment descriptors
19+
* Edit selected runtime application deployment descriptor elements
20+
21+
22+
## Differences With the WebLogic Server Administration Console
23+
If you are already familiar with the WebLogic Server Administration Console deployed as part of your WebLogic domain, you'll notice these key differences in the WebLogic Server Remote Console:
24+
* The user interface has been completely redesigned to conform to the Oracle Alta UI Design system and the Oracle Redwood theme included with Oracle JET.
25+
* The configuration and monitoring content is separated into separate pages in the Remote Console. In the WebLogic Server Administration Console, the configuration and runtime information is presented on one page.
26+
* The Change Center is now expressed as a shopping cart.
27+
* Instead of logging directly into the Administration Console deployed in a WebLogic domain, the Remote Console connects to the Administration Server in a WebLogic domain, with the credentials supplied by the user, using WebLogic REST APIs.
28+
29+
## Get Started
30+
The Oracle WebLogic Server Remote Console project repository is located at GitHub-URL. You can download a `console.zip` installer, or build the console from source. In this version, the console consists of the Remote Console JAR file, associated libraries necessary to use the console, and a web application that provides an extension that you can configure in your WebLogic Server domain. The extension provides additional functionality that is not available with the console only. Although installing the extension is optional, we recommend that you install it to get the optimum functionality from the Remote Console.
31+
32+
To install the software, simply unzip the `console.zip` installer on a machine that has JDK 11 installed. After unzipping the archive, the console is ready to use. You simply start the console application, enter the console URL in a browser, and provide the Administration credentials and URL for the domain of your choice.
33+
34+
For details about installing and running the Remote Console using the ZIP installer, see [Install and Configure the WebLogic Server Remote Console](site/install_config.md).
35+
36+
To build the Remote Console from source, see the [Developer Guide](site/developer_guide.md).
37+
38+
## Known Issues
39+
See the following list of [Known Issues](site/known_issues.md), limitations, and workarounds.
40+
41+
## Additional Information
42+
43+
* For information about the console user interface, see [Console Design and Usage Notes](site/console_uidesign.md).
44+
* For information for tuning the environment, see [Tuning the Remote Console Environment](site/tuning.md).
45+
* For information for developers, such as building the Remote Console from source, see the [Developer Guide](site/developer_guide.md).
46+
* For information to help troubleshoot configuration issues, see [Troubleshoot](site/troubleshoot.md).

‎SECURITY.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Reporting Security Vulnerabilities
2+
3+
Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security and privacy of all our users.
4+
5+
Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, please submit a report to [email protected] preferably with a proof of concept. We provide additional information on [how to report security vulnerabilities to Oracle](https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html) which includes public encryption keys for secure email.
6+
7+
We ask that you do not use other channels or contact project contributors directly.
8+
9+
Non-vulnerability related security issues such as new great new ideas for security features are welcome on GitHub Issues.
10+
11+
## Security Updates, Alerts and Bulletins
12+
13+
Security updates will be released on a regular cadence. Many of our projects will typically release security fixes in conjunction with the [Oracle Critical Patch Update](https://www.oracle.com/security-alerts/) program. Security updates are released on the Tuesday closest to the 17th day of January, April, July and October. A pre-release announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our [Security Alerts](https://www.oracle.com/security-alerts/) page.
14+
15+
## Security-Related Information
16+
17+
We will provide security related information such as a threat model, considerations for secure use, or any known security issues in our documentation. Please note that labs and sample code are intended to demonstrate a concept and may not be sufficiently hardened for production use.
18+

0 commit comments

Comments
 (0)