The WebLogic Remote Console can connect directly to a WebLogic Administration Server to view and edit its domain, much like the WebLogic Server Administration Console, though there are some differences.
You can save the connection details for multiple WebLogic Administration Servers, making it easy to switch between domains with a click.
The WebLogic Remote Console is now connected to a WebLogic Administration Server. You can make changes to the domain as desired.
Editing a domain in the WebLogic Remote Console is similar in process to the Administration Console. When you start editing a domain, a configuration lock is created that blocks other users from making simultaneous changes. Once you’re satisfied with your changes, you can activate these changes and perpetuate them to the Administration and Management Servers.
Certain areas and actions in the WebLogic Remote Console are hidden from non-administrations. For example, users with the Operator role cannot see the Edit Tree at all. For more information on what each user role can (or cannot) access, see Understand Access Discrepancies.
You can restore fields to their default value. Right-click on a field and click Restore to default.
The Shopping Cart (equivalent to the Change List in the WebLogic Server Administration Console) holds all the pending changes for the current session in the WebLogic Remote Console. In the shopping cart, you can see if any changes are pending, commit those changes or discard them entirely.
If you installed the console extension,
console-rest-ext-5.0.war, you can also see the specific changes you’ve made and the status of the lock in the Change Manager. If you need to undo a change, you must discard all shopping cart contents or manually revert the change in the Edit Tree perspective.
The configuration change lock does not prevent you from making conflicting configuration edits using the same administrator user account. For example, if you obtain a configuration change lock in the WebLogic Remote Console, and then use the Administration Console or WebLogic Scripting Tool (WLST) with the same user account, you will access the same edit session that you opened in the WebLogic Remote Console and you will not be blocked from making changes with the other tools.
We recommend against making changes using multiple tools because when one of the sessions activates their changes, it releases the lock and the other session will not be able to save or activate their changes.
Some changes can be activated immediately (dynamic) while other changes require a server start to activate (non-dynamic). When you need to activate non-dynamic changes, navigate to the Environment > Servers node in the Monitoring perspective to see which servers need a restart.
It’s easy to view the details of a WebLogic Server Connection.
A list of connection details will appear, including:
This will only delete the WebLogic Remote Console access to the WebLogic Administration Server. The domain itself will be unaffected.
The WebLogic Remote Console provides control operations for the Administration Server in the Monitoring perspective.
Server state indicates the specific condition of a server in the life cycle management.
The WebLogic Remote Console includes simplified wizards for deploying applications and creating JDBC system resources.
In most other cases, when you create a new MBean on a page, you are prompted to fill in a few key properties, such as Name, then click Create. Unlike the WebLogic Server Administration Console, the WebLogic Remote Console does not guide you through configuring other properties that you typically need to complete the configuration. Instead, it displays the new bean’s pages where you can click through the tabs to finish configuring the bean.
When you configure a bean property that references another bean, you must first create the other bean. For example, if you want to assign Server1 to Cluster1, you need to create Cluster1 first, unlike in the WebLogic Server Administration Console where you can choose to create Cluster1 during server creation.