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/3.0/content/concepts/model.md
+52-1Lines changed: 52 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@ weight: 1
15
15
-[Model semantics](#model-semantics)
16
16
-[Declaring named MBeans to delete](#declaring-named-mbeans-to-delete)
17
17
-[Using multiple models](#using-multiple-models)
18
+
-[Upgrading from WDT 1.x to WDT 2.x YAML files](#upgrading-from-wdt-1x-to-wdt-2x-yaml-files)
18
19
19
20
### Overview
20
21
@@ -264,7 +265,7 @@ In addition to deleting named mbeans, you can remove items from a list. Most pra
264
265
JMSSystemResource:
265
266
BPMJMSModule:
266
267
Target: soa_cluster,'!AdminServer'
267
-
268
+
268
269
```
269
270
In this example, the BPMJMSModule has the AdminServer target removed from the target list.
270
271
@@ -360,3 +361,53 @@ topology:
360
361
ListenPort: 7000
361
362
Notes: Server 1
362
363
```
364
+
365
+
### Upgrading from WDT 1.x to WDT 2.x YAML files
366
+
367
+
Beginning in 2.0, WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
368
+
This may require some changes to existing models in order to be parsed correctly.
369
+
- Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need to be escaped in single or double quotation marks.
370
+
```yaml
371
+
topology:
372
+
Server:
373
+
'!ms1':
374
+
ms2:
375
+
```
376
+
377
+
378
+
- Model elements under the same parent should be indented to the exact same level. The previous YAML parser did not enforce this restriction,
379
+
but it is standard for YAML. In this example, each cluster is indented four spaces.
380
+
```yaml
381
+
topology:
382
+
Cluster:
383
+
cluster1:
384
+
ClientCertProxyEnabled: True
385
+
cluster2:
386
+
WeblogicPluginEnabled: true
387
+
```
388
+
389
+
390
+
391
+
- Object lists in the `kubernetes` section of the model now should be specified in a hyphenated list format,
392
+
similar to how they appear in the domain resource file produced for [WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/managing-domains/domain-resource/).
393
+
394
+
```yaml
395
+
clusters:
396
+
- clusterName: 'cluster1'
397
+
allowReplicasBelowMinDynClusterSize: true
398
+
- clusterName: 'cluster2'
399
+
allowReplicasBelowMinDynClusterSize: true
400
+
```
401
+
402
+
- The "named object list" format is deprecated now, and will cause warning messages to be displayed.
403
+
```yaml
404
+
clusters:
405
+
'cluster1':
406
+
allowReplicasBelowMinDynClusterSize: true
407
+
'cluster2':
408
+
allowReplicasBelowMinDynClusterSize: true
409
+
```
410
+
411
+
412
+
- The deprecated argument `-model_sample` has been removed from the Model Help Tool.
413
+
The Model Help Tool has used model sample format, by default, since release 1.9.2.
Copy file name to clipboardExpand all lines: documentation/3.0/content/release-notes/_index.md
+11-86Lines changed: 11 additions & 86 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,96 +5,21 @@ weight = 5
5
5
pre = "<b> </b>"
6
6
+++
7
7
8
-
Review the following release notes for recent changes to WebLogic Deploy Tooling and known issues.
9
8
10
-
- WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
11
-
This may require some changes to existing models in order to be parsed correctly.
12
-
- Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need to be escaped in single or double quotation marks.
13
-
```yaml
14
-
topology:
15
-
Server:
16
-
'!ms1':
17
-
ms2:
18
-
```
9
+
### Changes in Release 3.0.0
10
+
-[Major New Features](#major-new-features)
11
+
-[Other Changes](#other-changes)
12
+
-[Bugs Fixes](#bug-fixes)
13
+
-[Known Issues](#known-issues)
19
14
20
15
21
-
- Model elements under the same parent should be indented to the exact same level. The previous YAML parser did not enforce this restriction,
22
-
but it is standard for YAML. In this example, each cluster is indented four spaces.
23
-
```yaml
24
-
topology:
25
-
Cluster:
26
-
cluster1:
27
-
ClientCertProxyEnabled: True
28
-
cluster2:
29
-
WeblogicPluginEnabled: true
30
-
```
16
+
#### Major New Features
17
+
None
31
18
19
+
#### Other Changes
20
+
None
32
21
22
+
#### Bug Fixes
33
23
34
-
- Object lists in the `kubernetes` section of the model now should be specified in a hyphenated list format,
35
-
similar to how they appear in the domain resource file produced for [WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/managing-domains/domain-resource/).
36
24
37
-
```yaml
38
-
clusters:
39
-
- clusterName: 'cluster1'
40
-
allowReplicasBelowMinDynClusterSize: true
41
-
- clusterName: 'cluster2'
42
-
allowReplicasBelowMinDynClusterSize: true
43
-
```
44
-
45
-
- The "named object list" format is deprecated now, and will cause warning messages to be displayed.
46
-
```yaml
47
-
clusters:
48
-
'cluster1':
49
-
allowReplicasBelowMinDynClusterSize: true
50
-
'cluster2':
51
-
allowReplicasBelowMinDynClusterSize: true
52
-
```
53
-
54
-
55
-
- The deprecated argument `-model_sample` has been removed from the Model Help Tool.
56
-
The Model Help Tool has used model sample format by default since release 1.9.2.
57
-
58
-
## Known issues for WebLogic Deploy Tooling
59
-
60
-
The following list contains known issues. Each issue may contain a workaround or an associated issue number.
61
-
62
-
#### Discover Domain Tool `SEVERE` messages
63
-
64
-
**ISSUE**:
65
-
The `discoverDomain` STDOUT contains many SEVERE messages about `cd()` and `ls()` when it is run against a 12.2.1.0 domain. The Discover Domain Tool navigates through the domain MBeans using WLST to determine which MBeans are present in a domain. When it tests an MBean that is not present, an error message is logged by WLST. There is no 12.2.1.0 PSU available to address this WLST problem. It is resolved in 12.2.1.1.
66
-
67
-
**ACTION**:
68
-
Ignore the following messages logged during discovery of a 12.2.1.0 domain.
The Create Domain Tool cannot initialize RCU for 11g JRF domains. The tool will issue error messages in the log and terminate the create process.
78
-
79
-
**ACTION**:
80
-
Run the WLS `rcu` command before executing `createDomain` for JRF domains
81
-
82
-
#### Credential in security configuration
83
-
84
-
**ISSUE**: For WLS versions prior to 14.1.1, there is a problem setting the `CredentialEncrypted` attribute in the `topology/SecurityConfiguration` folder. The value is not encrypted properly in the configuration and the domain will fail to start with the error:
85
-
```
86
-
java.lang.IllegalArgumentException: In production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean
87
-
```
88
-
**ACTION**: Contact Oracle Support to obtain the patch for bug number 30874677 for your WebLogic Server version before running the tool.
89
-
90
-
#### Assigning security groups to users
91
-
92
-
**ISSUE**: For WLS versions prior to 14.1.1, there is a problem setting the `GroupMemberOf` attribute in the `topology/Security/User` folder. The value is not persisted correctly, and the assignment will not be present when the domain is started.
93
-
94
-
**ACTION**: Contact Oracle Support to obtain the patch for bug number 30319071 for your WebLogic Server version before running the tool.
**ISSUE**: For existing WLS versions, there is a problem setting the `RotateLogOnStartup` attribute in various log file folders. The value is not persisted correctly, and the assignment will not be present when the domain is started.
99
-
100
-
**ACTION**: Contact Oracle Support to obtain the patch for bug number 29547985 for your WebLogic Server version before running the tool.
The following sections describe known limitations for WebLogic Deploy Tooling. Each issue may contain a workaround or an associated issue number.
11
+
12
+
#### Discover Domain Tool `SEVERE` messages
13
+
14
+
**ISSUE**:
15
+
The `discoverDomain` STDOUT contains many SEVERE messages about `cd()` and `ls()` when it is run against a 12.2.1.0 domain. The Discover Domain Tool navigates through the domain MBeans using WLST to determine which MBeans are present in a domain. When it tests an MBean that is not present, an error message is logged by WLST. There is no 12.2.1.0 PSU available to address this WLST problem. It is resolved in 12.2.1.1.
16
+
17
+
**ACTION**:
18
+
Ignore the following messages logged during discovery of a 12.2.1.0 domain.
The Create Domain Tool cannot initialize RCU for 11g JRF domains. The tool will issue error messages in the log and terminate the create process.
28
+
29
+
**ACTION**:
30
+
Run the WLS `rcu` command before executing `createDomain` for JRF domains
31
+
32
+
#### Credential in security configuration
33
+
34
+
**ISSUE**: For WLS versions prior to 14.1.1, there is a problem setting the `CredentialEncrypted` attribute in the `topology/SecurityConfiguration` folder. The value is not encrypted properly in the configuration and the domain will fail to start with the error:
35
+
```
36
+
java.lang.IllegalArgumentException: In production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean
37
+
```
38
+
**ACTION**: Contact Oracle Support to obtain the patch for bug number 30874677 for your WebLogic Server version before running the tool.
39
+
40
+
#### Assigning security groups to users
41
+
42
+
**ISSUE**: For WLS versions prior to 14.1.1, there is a problem setting the `GroupMemberOf` attribute in the `topology/Security/User` folder. The value is not persisted correctly, and the assignment will not be present when the domain is started.
43
+
44
+
**ACTION**: Contact Oracle Support to obtain the patch for bug number 30319071 for your WebLogic Server version before running the tool.
**ISSUE**: For existing WLS versions, there is a problem setting the `RotateLogOnStartup` attribute in various log file folders. The value is not persisted correctly, and the assignment will not be present when the domain is started.
49
+
50
+
**ACTION**: Contact Oracle Support to obtain the patch for bug number 29547985 for your WebLogic Server version before running the tool.
0 commit comments