WDT metadata models are descriptions of a WebLogic Server domain configuration, generally written in YAML but occasionally JSON. These models are not connected to a live domain and you edit them ‘offline’ before using the WebLogic Deploy Tooling (WDT) to build or modify live domains from the models.
See the WebLogic Deploy Tooling documentation for more information.
We recommend that you use the desktop application over the browser application when working with WDT model files.
Additionally, the WebLogic Remote Console assumes WDT model files are in YAML format. If you upload a file with no file extension, the WebLogic Remote Console will convert it to YAML format after you save your changes.
If you’ve already created a WDT model file, you can upload it to WebLogic Remote Console where you can continue to edit it.
Expand the Kiosk and select the WDT model file you want to edit.
Click WDT Model Tree and make your changes to the domain configuration. Make sure to click if you want to enter a model token.
|Restore field to its default value.
|Select a reference to a component that exists in the current WDT model file.
|Enter a fixed value.
|Enter Model Token
|Enter a WDT model token.
|Enter Unresolved Reference
|Enter a reference to a component that does not exist in the current WDT model file but will exist at a later point.
|Select Model Token Variable
|Select a model token variable from the list of available options. The WDT model file must be connected with a property list to see this option.
|Create Model Token Variable
|Enter a Variable Name and Variable Value to create a new model token variable. New model token variables are added to the connected property list. The WDT model file must be connected with a property list to see this option.
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.
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 differently than the desktop application. 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 WDT model file to your computer.
Do not refresh the browser page or you will lose all your changes.
If you want to restore fields to their default value, right-click on a field and click Restore to default.
WDT model tokens are variables that you can use to replace fixed values in WDT model files. With WDT model tokens, WDT model files become more versatile - you can create a single WDT model file with model tokens and when you build a domain from it, you only need to update the model token values, rather than create multiple, static WDT model files.
There are several types of model tokens including variable tokens, file tokens, and so on. Model tokens follow this format:
TYPE is the model token type and
KEY is the variable value. For example, you can declare a variable token by entering
@@PROP:ABCDE@@ into a field.
See WDT Model Tokens in the WebLogic Deploy Tooling documentation for more information.
WDT variables make it even easier to manage WDT model tokens in the WebLogic Remote Console. When you add WDT variables to your WDT model file, you create a link between the WDT model file and a property list. You can then pull in properties from the property list and use them as WDT model tokens. Then, when you want to update a property value, just open the associated property list and make your changes there.
You can use both standalone WDT model tokens and WDT variables in a WDT model file, but only one property list provider per WDT model file. Multiple WDT model files can use the same property list.
This will only remove the WDT model file from the WebLogic Remote Console. It will remain in the location designated on your computer. However, if you are using the browser application (and want to keep this WDT model file), make sure to download the file before deleting it in WebLogic Remote Console.
This will not delete any associated property list providers.
When you’re satisfied with the properties of your WDT model file, you can transform it into a live WebLogic Server domain with WebLogic Deploy Tooling (WDT).
If WDT reports an error when opening the WDT model file from WebLogic Remote Console, upgrade your WDT to the latest available version and try again.