Get Started

WebLogic Remote Console is easy to install and you can quickly start managing your domains.

WebLogic Remote Console is available in two formats:

• Desktop WebLogic Remote Console, a desktop application installed on your computer.
• Hosted WebLogic Remote Console, a web application deployed to an Administration Server and accessed through a browser.

Generally, the two formats have similar functionality, though the desktop application offers certain conveniences that are not possible when using a browser.

If your environment has restrictions on installing applications, consider enabling Hosted WebLogic Remote Console. See Deploy Hosted WebLogic Remote Console.

System Requirements

Review the system requirements needed to run WebLogic Remote Console.

WebLogic Remote Console is compatible with WebLogic Server 12.2.1.4.0 and later.

Desktop WebLogic Remote Console is supported on the following platforms.

We recommend setting the viewport of WebLogic Remote Console to 1300 px or wider. On narrower viewports, UI elements may overlap or disappear.

Install Desktop WebLogic Remote Console

Desktop WebLogic Remote Console is a version of WebLogic Remote Console that is based on the Electron framework and installed as a desktop application.

1. Download the latest version of WebLogic Remote Console from the WebLogic Remote Console GitHub Repository. Choose the appropriate installer for your operating system.

2. Follow the typical process for installing applications on your operating system.

3. Launch WebLogic Remote Console.

If you are using WebLogic Server 14.1.1.0 or earlier, you can enhance the functionality for managing Administration Servers by installing the WebLogic Remote Console extension. See Install the WebLogic Remote Console Extension. The extension comes pre-installed in WebLogic Server 14.1.2.0 and later.

Deploy Hosted WebLogic Remote Console

Hosted WebLogic Remote Console is a version of WebLogic Remote Console that is hosted on the Administration Server of the domain and accessed through a browser.

Hosted WebLogic Remote Console is useful for situations where it is not feasible to install external applications in your environment.

1. Start the Administration Server.

2. Deploy the Hosted WebLogic Remote Console application using the WebLogic Scripting Tool (WLST).

   1. Open a command line terminal and go to ORACLE_HOME/oracle_common/common/bin.

   2. Invoke WLST with the following options:

      wlst.sh *WL_HOME*/server/bin/remote_console_deployment.py t3://*hostname*:*port* *username* < *password.txt*
      

      Where:

      • WL_HOME is the top-level installation directory for WebLogic Server.
      • hostname is the host name of the Administration Server.
      • port is the port number of the Administration Server.
      • username is a user account capable of deploying applications.
      • password.txt is the path to a file containing the password for the specified user account. For example:

      wlst.sh /Users/smithdoe/Oracle/Middleware/Oracle_Home/wlserver/server/bin/remote_console_deployment.py t3://localhost:7001 admin < /Users/smithdoe/password.txt
      

Hosted WebLogic Remote Console is now deployed and will remain active as long as the weblogic-remote-console-app application is deployed and the Administration Server is running.

Do not stop or delete the Hosted WebLogic Remote Console application, weblogic-remote-console-app, if you want to continue to use Hosted WebLogic Remote Console.

To use Hosted WebLogic Remote Console to manage the running Administration Server, see Start Hosted WebLogic Remote Console.

Start Hosted WebLogic Remote Console

Hosted WebLogic Remote Console is a version of WebLogic Remote Console that is accessible using a browser.

Before you can start Hosted WebLogic Remote Console, you must have deployed it. See Deploy Hosted WebLogic Remote Console.

1. Start the Administration Server.

2. Open a browser and enter http://hostname:port/rconsole (or for HTTPS, https://hostname:port/rconsole).

   Where hostname and port match the values you set when you deployed Hosted WebLogic Remote Console.

   If your Administration Server is behind a firewall or load balancer, or otherwise externally unavailable, you must manually expose the rconsole/* endpoint to make it accessible, similar to exposing console/* for the WebLogic Server Administration Console.

   This is in addition to exposing the management/* endpoint which is required for general domain configuration.

3. Log in to Hosted WebLogic Remote Console.

4. In the Providers drawer, select This Server.

Hosted WebLogic Remote Console is active as long as the weblogic-remote-console-app application is deployed and the Administration Server is running.

Install the WebLogic Remote Console Extension

The WebLogic Remote Console extension enhances the management capabilities of WebLogic Remote Console for Administration Server connections.

For an overview of the functionality provided by the WebLogic Remote Console extension, see Features of the WebLogic Remote Console Extension.

1. Under DOMAIN_HOME, create a folder and name it management-services-ext.

2. Download the latest WebLogic Remote Console extension, console-rest-ext-2.4.13.war, from the WebLogic Remote Console GitHub Repository.

3. Save the extension under management-services-ext.

   You do not need to deploy console-rest-ext-2.4.13.war as an application in your domain.

4. Restart the Administration Server.

5. In WebLogic Remote Console, disconnect and then reconnect to the Administration Server.

The WebLogic Remote Console extension is updated with WebLogic Remote Console. Whenever you update WebLogic Remote Console, make sure you also update the extension to match.

If you need to update the WebLogic Remote Console extension separately from the console, follow the instructions outlined in step 2 of Upgrade Desktop WebLogic Remote Console.

Features of the WebLogic Remote Console Extension

The WebLogic Remote Console extension adds many features to WebLogic Remote Console that are useful for the administration of WebLogic Server domains.

When the WebLogic Remote Console extension is installed, it grants the following capabilities to WebLogic Remote Console:

• View pending changes - Identify any changes that are saved to the domain but not yet committed. Pending changes are listed in the Shopping Cart.

• Access the Security Data Tree perspective - Edit security data that is stored in the embedded LDAP server, including, but not limited to, managing:

  • Users and Groups

  • Roles and Policies

  • Credential Mappings

  You can also view (but not edit) the users and groups for any authentication provider that supports it.

• Create and edit application deployment plans - Use deployment plans to extend or override an application’s deployment descriptors.

• Manage JMS messages - Import, export, or delete messages.

• Manage JTA transactions - Import, export, or delete transactions.

• Test data source connections - Verify that the domain can successfully connect to the configured database.

• View objects in JNDI structure - Examine objects such as Java EE services and components such as RMI, JMS, EJBs, and JDBC data sources.

• Upload applications or database client data for redeployment - Update and redeploy applications or database client data with new versions that were not already deployed to the Administration Server.

  The redeployment of applications or database client data that are already on the server is supported without the extension.

• Analyze server connection issues - Test connections between the Administration Server and Managed Servers or clusters.

For installation instructions, see Install the WebLogic Remote Console Extension.

Provider Types

Use WebLogic Remote Console to connect to the following provider types, each of which offers a different approach for managing your WebLogic Server domains.

Connect to a Provider

You can connect WebLogic Remote Console to a WebLogic Administration Server, WDT model file, or another provider.

1. Open the Providers drawer and click More ︙.

2. Choose a provider type from the list:

   • Add Admin Server Connection Provider
   • Add WDT Model File Provider
   • Add WDT Composite Model File Provider
   • Add Property List Provider
   • Create Provider for new WDT Model File
   • Create Provider for New Property List For information on the different providers, see Provider Types.

3. Fill in any required connection details for the selected provider.

4. Click OK to establish the connection.

   The Administration Server must be running for the connection to succeed.

Upgrade Desktop WebLogic Remote Console

Upgrade to the latest version of Desktop WebLogic Remote Console and take advantage of the latest features in both the console and WebLogic Server.

If a newer version of Desktop WebLogic Remote Console is available, an alert will appear in the menu bar.

1. In Desktop WebLogic Remote Console, open Updates Available, then Download and install.

   Desktop WebLogic Remote Console update runs in the background so you can continue working in WebLogic Remote Console with no interruptions. The next time the console is launched, the updates will apply.

   You can also go directly to the WebLogic Remote Console GitHub Repository to download and apply the update manually.

2. Update the WebLogic Remote Console extension.

   For the best experience, you should keep the versions of WebLogic Remote Console and its extension in sync with each other. That is, when you are running WebLogic Remote Console 2.4.13, you should have console-rest-ext-2.4.13.war installed.

   With the release of WebLogic Remote Console 2.4.11, the versioning scheme of the extension was updated to match WebLogic Remote Console. Due to this change, the extension version jumps from console-rest-ext-9.0.war to console-rest-ext-2.4.11.war.

   1. While connected to the domain, open the Providers drawer and beside the provider connection, click the Get Info icon to see the Console Extension Version. If it matches WebLogic Remote Console version, you can skip the rest of the steps. Otherwise, continue.

   2. Go to DOMAIN_HOME/management-services-ext and delete the existing WebLogic Remote Console extension.

   3. Download the WebLogic Remote Console extension that matches your WebLogic Remote Console from the WebLogic Remote Console GitHub Repository. It will be within the matching WebLogic Remote Console release section.

   4. Save the extension to DOMAIN_HOME/management-services-ext.

   5. Restart the Administration Server.