Administration Servers

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.

Connect to a WebLogic Administration Server

  1. Start the WebLogic Administration Server.
  2. Expand the Kiosk and beside the project name, click ⋮. Select Add Admin Server Connection Provider.
  3. Enter a name for the Administration Server connection. This is the name that will appear in the Project list of providers so you can identify which provider you’re working on.
  4. Enter a username and password for a user account with editing privileges in the selected Administration Server. As with the Administration Console, your management capabilities will be limited depending on the level of access granted to your user account. See Understand access discrepancies for more information. You can choose to have multiple connections to the same Administration Server with different users.
  5. Enter the URL for the Administration Server.
  6. Click OK to connect the WebLogic Remote Console to the WebLogic Administration Server.

The WebLogic Remote Console is now connected to a WebLogic Administration Server. You can make changes to the domain as desired.

Edit a WebLogic Administration Server

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.

  1. Expand the Kiosk and select the Administration Server you want to edit.
  2. Click the Edit Tree perspective and make your changes to the domain configuration. Fields marked with Server restart icon require a server restart.
  3. Click Save on every page after making your changes.
  4. If you have the extension installed, expand the Kiosk and select Shopping Cart to view your changes.
  5. Commit your changes. In the upper right corner of the content pane, click Server restart icon and then Commit Changes.
  6. Restart your server if necessary.
    1. Check if any servers require a restart on the Monitoring Tree perspective > Environment > Servers page.

You can restore fields to their default value. Right-click on a field and click Restore to default.

Shopping cart

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-x.x.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.

Edit the connection details of a WebLogic Administration Server

  1. Expand the Kiosk and beside the WebLogic Administration Server connection that you want to edit, click the Settings icon icon.
  2. Edit the details of the WebLogic Administration Server. You can change its name in WebLogic Remote Console, switch user accounts or update the URL.
  3. Click OK to save your changes.

View the connection details of a WebLogic Administration Server

It’s easy to view the details of a WebLogic Server Connection.

  1. Expand the Kiosk and beside the WebLogic Administration Server, click the Settings icon icon.

A list of connection details will appear, including:

  • Provider ID
  • Domain Name
  • Domain URL
  • Domain Version
  • Username
  • Role

Delete a connection to a WebLogic Administration Server

This will only delete the WebLogic Remote Console access to the WebLogic Administration Server. The domain itself will be unaffected.

  1. Expand the Kiosk and beside the WebLogic Administration Server, click the Settings icon icon.

Create a managed server

  1. In the Edit Tree perspective, expand the Environment > Servers node.
  2. Click New.
  3. Enter a name for the new server.
  4. Optional: If you want to copy the settings from an existing server onto your new server, select a server from the Copy settings from another server dropdown. Only the server’s settings will be copied; children, such as channels, are not copied. Any settings that are not supported by the WebLogic Server REST API are also not copied.
  5. Click Create.

Control Operations

The WebLogic Remote Console provides control operations for the Administration Server in the Monitoring perspective.

Change server state

Server state indicates the specific condition of a server in the life cycle management.

  1. Expand the Kiosk and select a WebLogic Administration Server connection.
  2. Choose the Monitoring perspective from the home page.
  3. Go to Environment > Servers
  4. Choose the action for the server(s):
    • Start
    • Resume
    • Suspend
    • Shutdown
    • Restart SSL
  5. Choose when to initiate the action:
    • When work completes
    • Force shutdown now
  6. In the dialog box, move the servers whose state you want to change from Available to Chosen.
  7. Initiate the action.

Start or stop an application

  1. Expand the Kiosk and select a WebLogic Administration Server connection.
  2. Choose the Monitoring perspective from the home page.
  3. Go to Deployments > App Deployment Runtimes.
  4. Choose the action for the application:
    • Start
    • Stop
  5. In the dialog box, move the applications whose state you want to change from Available to Chosen.
  6. Initiate the change.

Create MBeans

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.