You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/staging/1.2/content/navigate/model.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,16 +32,23 @@ Tooling documentation.
32
32
33
33
### Design View
34
34
The `Design View` is provided through integration with the [WebLogic Remote Console](https://github.com/oracle/weblogic-remote-console/releases).
35
-
For version details, see [Prerequisites]({{< relref "/setup/prerequisites.md" >}}).
35
+
For version details, see [Prerequisites]({{< relref "/setup/prerequisites.md" >}}). Upon first access, provide the location of the
36
+
Remote Console installation directory, then click **Start WebLogic Remote Console**.
36
37
37
-
Upon first access, provide the location of the Remote Console installation directory, then click **Start WebLogic Remote Console**.
38
-
Then use the WebLogic Server domain configuration pages to create or edit WDT model files. For reference, see
38
+
Use the Model `Design View` pages to create or edit your WDT model files. For reference, see
39
39
[WDT Model Files](https://oracle.github.io/weblogic-remote-console/userguide/providers/wdt-model/) in the Remote Console documentation.
40
-
41
-
Use the Help (?) icon to the left of each field to access summary and detailed help for the field. Or,
40
+
In addition, use the Help (?) icon to the left of each field to access summary and detailed help for the field. Or,
42
41
click the ? icon in the top right of the content pane to toggle the view of the reference information for all of the fields displayed on the page.
43
42
44
-
The WDT model file that you configured will be reflected in the `Code View`.
43
+
The WDT model files that you configure will be reflected in the `Code View`. Note that currently, the WKTUI supports only a single WDT model file
44
+
(YAML file with the domain definition) per project but the collection of that model file, the variables file, and the archive file can also be referred to as "model files."
45
+
Using the Model `Design View` pages, if you select the "circle/arrow" icon beside a field, a dialog appears with the option of setting the field to a variable.
46
+
The variable will show up in both the model and the variables editor on the `Code View` page. Likewise, when adding an application, you supply the path to the EAR,
47
+
WAR, or JAR file (or directory); that path will be put in the archive editor on the `Code View` page.
48
+
49
+
Note that if you create a new model using the `Design View` pages, the `Design View` will insert the `AdminUserName` and `AdminPassword` fields
50
+
into the `domainInfo` section of the model with their values set to variables whose values you will need to provide.
51
+
This is intended to help you create a domain with all of the required fields.
45
52
46
53
### Code View
47
54
Using an IDE-like layout, the `Code View` provides editor panes for editing the model, variables, and archive files,
0 commit comments