Merge pull request #1037 from oracle/doc-updates-2.0

Documentation updates for 2.0

Author: robertpatrick

documentation/2.0/content/concepts/model.md

@@ -252,7 +252,7 @@ This feature can also remove items that were created by WebLogic Server template
     SecurityConfiguration:
         DefaultRealm: newrealm
         Realm:
-            !myrealm:
+            '!myrealm':
             newrealm:
                 AuthenticationProvider:
                 ...
@@ -333,7 +333,7 @@ and Model 2 looks like:
 ```yaml
 topology:
     Server:
-        !m2:
+        '!m2':
 ```
 The resulting model would be:
 ```yaml
@@ -348,7 +348,7 @@ Similarly, an element without delete notation will completely replace an element
 ```yaml
 topology:
     Server:
-        !m1:
+        '!m1':
 ```
 and Model 2 looks like:
 ```yaml

documentation/2.0/content/release-notes.md

@@ -35,3 +35,9 @@ java.lang.IllegalArgumentException: In production mode, it's not allowed to set
 **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.
 
 **ACTION**: Contact Oracle Support to obtain the patch for bug number 30319071 for your WebLogic Server version before running the tool.
+
+#### Problems setting `RotateLogOnStartup` attribute
+
+**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.
+
+**ACTION**: Contact Oracle Support to obtain the patch for bug number 29547985 for your WebLogic Server version before running the tool.

documentation/2.0/content/userguide/target_env.md

@@ -31,7 +31,7 @@ A target environment is configured in a JSON file at this location:
 $WLSDEPLOY_HOME/lib/target/<target-name>/target.json
 ```
 The `<target-name>` value corresponds to the value of the `-target` argument on the tool's command line. The WLS installation includes three pre-defined targets:
- - [Weblogic Kubernetes Operator](#the-weblogic-kubernetes-operator-target) (named `wko`)
+ - [WebLogic Kubernetes Operator](#the-weblogic-kubernetes-operator-target) (named `wko`)
  - [Verrazzano](#the-verrazzano-target) (named `vz`)
  - [Kubernetes](#generic-kubernetes-target) (named `k8s`)
 
@@ -42,7 +42,8 @@ Here is an example of a target environment file:
 {
     "model_filters" : {
         "discover": [
-            { "name": "vz_prep", "path": "@@TARGET_CONFIG_DIR@@/vz_filter.py" }
+            { "name": "vz_prep", "path": "@@TARGET_CONFIG_DIR@@/vz_filter.py" },
+            { "id": "wko_filter" }
         ]
     },
     "variable_injectors" : {"PORT": {},"HOST": {},"URL": {}},

documentation/2.0/content/userguide/tools-config/domain_def.md

@@ -142,6 +142,21 @@ weight: 2
 
  If there are any server groups in the custom template that should be targeted to managed servers, they should be specified in the `serverGroupsToTarget` attribute, similar to `MY_MAN_SVR` in the example above.
 
+ #### Using compact profile
+
+ The `topologyProfile` field can be used to create a domain using a specific profile for each of the templates. This partial example will apply the compact profile for each of the specified templates.
+```json
+{
+  "copyright": "Copyright (c) 2022, Oracle Corporation and/or its affiliates.  All rights reserved.",
+  "license": "Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl",
+  "name": "JRF-Compact",
+  "description": "JRF type domain with a compact profile definitions",
+  "topologyProfile": "Compact",
+  ...
+}
+```
+ WebLogic Deploy Tooling provides the `JRF-Compact.json` type definition file that can be used to create a JRF domain using the compact profile.
+
  #### Targeting in earlier WebLogic Server versions
 
  Templates in WebLogic Server versions prior to 12.2.1 may require the use of the `applyJRF` WLST command to correctly target resources to the correct clusters and servers. The default behavior for WebLogic Deploy Tooling is to invoke `applyJRF` only when the `extensionTemplates` list includes JRF templates.

documentation/2.0/content/userguide/tools-config/model_filters.md

@@ -44,3 +44,22 @@ This example configures two filters for the Create Domain Tool: `fix-password.py
   ]
 }
 ```
+### Internal Filters
+
+Internal filters are provided by WebLogic Deploy Tooling to perform modifications to the domain model. They are referenced by ID in the target configuration file. This example shows the use of the internal filter `wko_filter` and a user-defined filter `fix-password` for use with the Create Domain Tool.
+```json
+{
+  "create": [
+    { "name": "fixPassword", "path": "/home/user/fix-password.py" },
+    { "id": "wko_filter" }
+  ]
+}
+```
+Internal filters cannot be copied or modified like other types of filters.  
+
+#### Internal filter `wko_filter`
+
+This filter prepares the domain model for use with WebLogic Kubernetes Operator. It performs the following modifications:
+- Removes any attributes that can only be deployed in online mode
+- Sets the `CalculatedListenPorts` attribute to false for dynamic clusters
+- Warns if servers in a static cluster have different listen ports