Edit domain configurations

The domain configuration process in the WebLogic Remote Console is similar to the Administration Console. When you start editing the domain, a configuration lock is placed on the domain that blocks other users from making simultaneous changes. Once you’re are satisfied with your changes, you can ‘activate’ these changes and perpetuate them to the administration and management servers.

Configuration locks do not apply to WDT model files. As WDT model files are not connected to live domains, they do not require any locks to prevent conflicting changes. Additionally, you do not have to save and commit changes; once you save your changes, they are saved to the WDT model file.

WDT model tokens

When editing the domain configuration for a WDT model File, you can substitute model tokens instead of real field values. Model tokens are variables that you can enter into domain configuration settings. Rather than restricting a setting to a single value, the value will update according the variable.

There are several types of model tokens including variable tokens, file tokens, and so on. Model tokens follow this format: @@TYPE:KEY@@, where TYPE is the model token type and KEY is the variable value. For example, you could declare variable token by entering @@PROP:ABCDE@@ into a field.

See WDT Model Tokens for more information.

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-1.0.war, you can also see the specific changes you’ve made and the status of the lock in the Change Manager. Unfortunately, there is currently no support for removing individual items from the shopping cart.

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 locked out of making changes with the other tools.

Some changes can be activated immediately (dynamic) while other changes will only activate following a server restart (non-dynamic). When you need to activate nondynamic changes, navigate to the ‘Running Servers’ table in the Monitoring perspective to see which servers need to be restarted so that they can start using the new configuration.

Edit Administration Servers

1. Open a project and select an Admin Server Connection Provider.
2. Click the Edit Tree perspective and make your changes to the domain configuration. Fields marked with require a server restart.
3. If you have the extension installed, view your changes in the Kiosk.
4. Commit your changes.
5. Restart your server if necessary.
   1. Check if any servers require a restart on the Monitoring Tree perspective > Running Servers page.

Edit a WDT model file

Domain configuration changes in WDT model files offer more flexibility to take advantage of the benefits of a model file. You can enter specific values in fields or enter model tokens to create variable values that update as needed for their environment. model tokens follow this format: @@TYPE:KEY@@.

It’s recommended that you use the desktop application version of the WebLogic Remote Console if you plan to edit a WDT model file.

1. Open a project and select a WDT Model File Provider.
2. Click WDT Model Tree and make your changes to the domain configuration. Make sure to click if you want to enter a model token. The WebLogic Remote Console auto-saves any changes you make to the WDT model file. You don’t need to commit changes to WDT model files.
3. After you finish making changes, you can click Save Now (in the desktop application) or Download File (in the browser) to ensure all changes are saved and downloaded to your computer.

   The browser application behaves slightly differently. While changes to the WDT model file are still saved automatically as you move around the console, they are not saved to your computer. This means that once you’re satisfied with your changes, you must click Download File to download the updated model file to your computer.

   Do not refresh the browser page or you will lose all your changes.

Use the WebLogic Remote Console control operations

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

The Server States page contains the control operations to change the state of a server. Server state signifies the specific condition of a server in the life cycle management.

To change the server state, click the desired control at the top of the table. Then, in the next window, select the servers on which you want to perform the control operation. Consistent with the WebLogic Server Administration Console, the WebLogic Remote Console includes support for graceful shutdowns.

The App Deployments Runtimes page, under Domain Information in the Navigation Tree, provides controls to start and stop applications. To start or stop an application, select the control, then in the next window, select the applications on which you want to perform the operation.

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