WebLogic Remote Console offers several avenues to receive support and help.
Stay up-to-date with the latest release of WebLogic Remote Console to get the latest features and fixes. If you experience issues, try upgrading to the latest release, which may address your issue. For more information, see Upgrade Desktop WebLogic Remote Console.
In addition to the current guide, you can retrieve information on WebLogic Remote Console from within the user interface. Click the Help icon in the Tool Bar or in dialog boxes to reveal descriptions of the fields on your current page.
You can also view general documentation for WebLogic Server at Oracle WebLogic Server in the Oracle Help Center.
Support for WebLogic Remote Console is available to Oracle customers that have purchased support for WebLogic Server.
Join our Slack channel at #remote-console in the Oracle WebLogic workspace! Ask questions, make suggestions, or just get in touch with developers and other users of WebLogic Remote Console.
Visit our GitHub repository where you can contribute directly to the development of WebLogic Remote Console, whether it’s through raising issues or submitting your own code.
WebLogic Remote Console is one of several tools available to manage your WebLogic Server domain. For a list of alternative administration options, see Choosing the Appropriate Technology for Your Administrative Tasks in Understanding Oracle WebLogic Server.
WebLogic Remote Console is an evolving product that continues to add new features with each release. As WebLogic Remote Console is an open-source product, you can view our progress in our WebLogic Remote Console GitHub repository.
This section provides answers to frequently asked questions about WebLogic Remote Console.
For WebLogic Remote Console to connect to a domain’s Administration Server, the management endpoint of the domain, management/*, must be publicly accessible. If your Administration Server is behind a firewall or load balancer, or otherwise externally unavailable, you will need to expose the endpoint manually.
If you use the Hosted WebLogic Remote Console, you will also need to expose rconsole/*.
Tip:
If you needed to expose console/* to access the WebLogic Server Administration Console for your domain, simply follow the same procedure to expose management/* for WebLogic Remote Console.
Yes, you can. First, make sure that the domain’s Administration Server is publicly accessible so WebLogic Remote Console can establish a connection to it. Then, in WebLogic Remote Console, enter your credentials and the publicly accessible URL for the WebLogic Administration Server.
Yes, you can connect to other cloud providers. You’ll need to make sure the domain’s Administration Server is publicly accessible to allow a connection between WebLogic Remote Console and the cloud provider. Then, in WebLogic Remote Console, enter your credentials and the publicly accessible URL for the WebLogic Administration Server.
Visit your cloud providers’ documentation for more specific instructions on how to expose the management/* endpoint of the WebLogic Server.
Yes. For details on how to set up access to WebLogic Server domains running on Kubernetes, see Use the WebLogic Remote Console in the WebLogic Kubernetes Operator User Guide.
WebLogic Remote Console is compatible with WebLogic Server 12.2.1.3 or later.
It depends on the WebLogic Server release that you have installed. The Administration Console was removed in WebLogic Server 14.1.2.0.0 and therefore is not available as of that release.
However, if you’re running WebLogic Server 14.1.1.0 or earlier, then you can continue to use the Administration Console for domain management alongside WebLogic Remote Console. Any changes you make in WebLogic Remote Console are reflected in the Administration Console.
As with any combination of system administration tools, avoid using them simultaneously as it can cause configuration conflicts and unexpected behavior.
To see a full list of the tools that you can use to administer WebLogic Server, see Overview of WebLogic Server System Administration in Understanding Oracle WebLogic Server.
No, older releases of WebLogic Remote Console will continue to work with newer releases of WebLogic Server. However, we recommend that you update WebLogic Remote Console (and its extension) as frequently as possible to take advantage of any fixes and improvements, both to WebLogic Remote Console itself and those added in WebLogic Server patches.
For example, if new fields or WebLogic MBeans were added in a WebLogic Server update, then outdated versions of WebLogic Remote Console will not detect or display those fields.
No, WebLogic Remote Console accesses WebLogic Administration Servers through its standard WebLogic REST API, which is available out of the box. However, since your computer will be accessing potentially sensitive data, you need to make sure it is protected and secure.
When you make changes to the domain configuration using system properties, the properties override but do not change the config.xml file. The Edit Tree perspective, which is generated from config.xml, will only show the state of the domain as specified in the configuration file. In contrast, the Configuration View Tree perspective shows the current and effective state of the domain, including command line options.
See Perspectives in the Administration Server Provider.
As an example, if your domain is set to secured production mode and you choose to temporarily disable secured production mode with the following system property, -Dweblogic.securemode.SecureModeEnabled=false, then only the Configuration View Tree will accurately report the domain mode as production mode. The Edit Tree (and config.xml) will continue to report that secured production mode is enabled, even though it is not.
See Verifying Attribute Values That Are Set on the Command Line in Command Reference for Oracle WebLogic Server.