WDT 3.0 Doc Updates

documentation/2.0/content/concepts/model.md → documentation/3.0/content/concepts/model.md

@@ -15,6 +15,7 @@ weight: 1
 - [Model semantics](#model-semantics)
 - [Declaring named MBeans to delete](#declaring-named-mbeans-to-delete)
 - [Using multiple models](#using-multiple-models)
+- [Upgrading from WDT 1.x to WDT 2.x YAML files](#upgrading-from-wdt-1x-to-wdt-2x-yaml-files)
 
 ### Overview
 
@@ -264,7 +265,7 @@ In addition to deleting named mbeans, you can remove items from a list. Most pra
   JMSSystemResource:
       BPMJMSModule:
           Target: soa_cluster,'!AdminServer'
-              
+
 ```
 In this example, the BPMJMSModule has the AdminServer target removed from the target list.
 
@@ -360,3 +361,53 @@ topology:
             ListenPort: 7000
             Notes: Server 1
 ```
+
+### Upgrading from WDT 1.x to WDT 2.x YAML files
+
+Beginning in 2.0, WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
+This may require some changes to existing models in order to be parsed correctly.
+   - Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need to be escaped in single or double quotation marks.
+   ```yaml
+   topology:
+       Server:
+           '!ms1':
+           ms2:
+   ```
+
+
+   - Model elements under the same parent should be indented to the exact same level. The previous YAML parser did not enforce this restriction,
+   but it is standard for YAML. In this example, each cluster is indented four spaces.
+   ```yaml
+   topology:
+       Cluster:
+           cluster1:
+               ClientCertProxyEnabled: True
+           cluster2:
+               WeblogicPluginEnabled: true
+   ```
+
+
+
+- Object lists in the `kubernetes` section of the model now should be specified in a hyphenated list format,
+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/).
+
+   ```yaml
+       clusters:
+       - clusterName: 'cluster1'
+         allowReplicasBelowMinDynClusterSize: true
+       - clusterName: 'cluster2'
+         allowReplicasBelowMinDynClusterSize: true
+   ```
+
+   - The "named object list" format is deprecated now, and will cause warning messages to be displayed.
+   ```yaml
+       clusters:
+         'cluster1':
+           allowReplicasBelowMinDynClusterSize: true
+         'cluster2':
+           allowReplicasBelowMinDynClusterSize: true
+   ```
+
+
+- The deprecated argument `-model_sample` has been removed from the Model Help Tool.
+The Model Help Tool has used model sample format, by default, since release 1.9.2.

documentation/2.0/content/developer/alias-definitions.md → documentation/3.0/content/developer/alias-definitions.md

@@ -136,7 +136,13 @@ This key element specifies which method should be used for retrieving the value
 
 #### `access`
 
-By default, an attribute is read write in both WLST and MODEL. This element is used to set an attribute to read-only. The two read-only attributes are `RO` and `ROD`. The latter indicates that the attribute is read-only and will not be written into the domain. However, it will be discovered by the Discover Domain Tool into the model.
+By default, an attribute is read write in both WLST and MODEL. This element is used to set an attribute to read-only
+or ignored.  The two attribute values are:
+
+- `RO`       indicates that the attribute is read-only and will not be written into the domain; however, it will be
+             discovered and written into the model by the Discover Domain Tool.
+- `IGNORED`  indicates that the attribute is both known and tolerated in the model but is never discovered or written
+             into the domain.
 #### `preferred_model_type`
 
 This key element specifies the preferred data type that should be used to put data in the model during discovery. As an example, list values can be represented in the model as comma-separated text, such as `"value1, value2"`, or as a YAML list, such as `["value1", "value2"]`. If the list values can contain commas, a YAML list must be used.

documentation/3.0/content/release-notes/_index.md

@@ -0,0 +1,88 @@
++++
+title = "Release Notes"
+date = 2019-02-22T15:27:38-05:00
+weight = 95
+pre = "<b> </b>"
++++
+
+
+### Changes in Release 3.0.0
+- [Major New Features](#major-new-features)
+- [Other Changes](#other-changes)
+- [Bugs Fixes](#bug-fixes)
+- [Known Issues](#known-issues)
+
+
+#### Major New Features
+- #1355: Added `-remote` option to the `deployApps` tool that support deploying applications and shared libraries from a remote machine. (Issue #1312)
+- #1355: Added `-remote` option to the `updateDomain` tool that allows configuration changes not requiring archive file changes
+  (except for applications and shared libraries) to be made from a remote machine. (Issue #1167)
+- #1365: Added new `verrazzano` section of the model that can be used to augment/override the YAML files generated by the Verrazzano-related `-target` options. (WDT-688)
+- #1367: New `archiveHelper` tool for helping to create and update the archive file from the command line. (WDT-711)
+- Cleaned up the aliases to clean up online discovery and put tests in place to ensure that they align properly with the
+  various WebLogic Server releases and PSUs.  The resulting model from online discovery is now much closer to the one generated by offline discovery.
+
+#### Other Changes
+- #1255: Renamed model attributes to align with the offline naming strategy:
+
+  - SystemComponent `MWHome` model attribute renamed to `MwHome`.
+  - WebserviceSecurity `DefaultCredentialProviderSTSURI` model attribute renamed to `DefaultCredentialProviderStsuri`.
+
+- #1299: Renamed model attributes to align with the offline naming strategy:
+
+  - SecurityConfiguration `IdentityAssertionCacheTTL` model attribute renamed to `IdentityAssertionCacheTtl`.
+
+- #1310: Resolved issue that was causing the PSU version of several 12.2.1.3 PSUs to be incorrect.
+- #1314, #1342: Adding knowledge to the aliases to understand how default values change when using `production mode` and `secure production mode`. (WDT-678)
+- #1328: Changed tool exit code handling to exit with exit code 1 if warnings exist and exit code 2 if errors exist in the summary report. (WDT-692)
+- #1331: Deprecated the old archive locations of the OPSS wallet and ATP wallet in the archive file.  The old locations will be
+  honored but will result in one or more deprecation messages. (WDT-687)
+- #1334: Removed support for storing the model files in the archive. (WDT-643)
+- #1341: Remove deprecated `-domain_resource_file` argument from the `extractDomainResource` tool. (WDT-706)
+- #1348: Renamed the old ATP wallet to `rcu` wallet. (WDT-709)
+- #1348: Add support for adding wallets either as a zip file or an exploded directory with one or more files.  When the wallet is
+  added as a zip file, the `createDomain` and `updateDomain` tools will expand the zip into the domain home, just as before.
+- #1348: Added database wallet support for multiple wallets. Other database wallets can be added, as needed. (WDT-710)
+- #1351: Removed support for the deprecated "named object list" format from the `kubernetes` section of the model. (WDT-688)
+- #1366: Refactored ATP and SSL database support to be more unified in their modeling approach.
+- #1369: Added a special log level for deprecation messages so that they can show up in the tools' summary reports without causing a non-zero exit status. (WDT-721)
+- #1375: Revamped application installation directory discovery to capture the entire application installation directory. (WDT-715)
+- #1379: Added the ability for discovery to collect the JDBC wallet file(s) in the archive.
+- #1380: Updated the approach for generating the Verrazzano custom resource related to the Ingress Trait routing rules to add
+  a destination host/port and allow the user to add Paths via the new `verrazzano` section of the model. (WDT-696)
+- #1383: Removed the `DomainVersion` domain-level attribute from discovered models and replaced it with a comment describing the
+  WDT and WebLogic Server version numbers used to discover the model and which WLST mode was used for discovery. (WDT-698)
+- #1386: Changed attribute not valid in the current WebLogic version warnings with to log `INFO` level messages instead. (WDT-724)
+- #1389: Added additional model and WebLogic Kubernetes Operator/Verrazzano target validation around dynamic cluster to catch modeling issues prior to domain creation. (WDT-726)
+- #1391: Revamped tool summary report and remote report generated when using remote discovery. (WDT-637)
+- #1395: Added unclustered servers to the WKTUI integration output of `prepareModel` (WDT-730)
+
+#### Bug Fixes
+- #1261, #1266: Corrected a `discoverDomain` error message when a keystore was missing. (WDT-685)
+- #1324: Resolved an issue causing secure mode not to be discovered. (WDT-694)
+- #1327: Resolved an issue where WLST errors in WLS 12.2.1.0.0 were showing up in the tools' summary reports. (WDT-691)
+- #1329: Changed the tools summary log handler to not accept any messages that did not originate in WDT proper. (WDT-701)
+- #1330: Fixed a Windows issue with environment variable substitution where environment variable references in the model that were not all upper-case were not working properly.
+- #1335: Removed unused and undocumented `-prev_model_file` argument `deployApps` and `updateDomain` tools. (WDT-707)
+- #1344: Removed `-archive_file` argument from the `extractDomainResource` tool since the model can no longer be stored in the archive file. (WDT-708)
+- #1367: Corrected the behavior of the archive class to rename directories when an existing directory of the same name already exists.
+  This makes the behavior for files and directories consistent. (WDT-722)
+- #1374: Corrected a problem discovering a domain with a Coherence cluster with a custom configuration file.
+- #1376: Corrected an issue with `compareModel` pertaining to comparisons of the JVM arguments and whitespace (Issue #1370)
+- #1382: Removed misleading log entries during startup that displayed the WebLogic Server version with no PSU information (WDT-727)
+- #1392: Fixing an issue with online discovery of domains with dynamic clusters where the dynamic servers were erroneously being added as configured servers.
+- #1393: Fixing an issue causing an empty `SecureMode` folder to show up in an online discovered model. (WDT-731)
+- #1394: Fixing alias entries to prevent some `INFO` messages with errors related to alias entries during online discovery.
+
+#### Known Issues
+1. When running `discoverDomain` with the `-remote` flag, there are several MBeans that are not being properly handled that
+   will result in `INFO` level messages that look similar to the example shown below.  These errors seem to happen only when the MBean is
+   non-existent so the resulting model should still be accurate.  These issues are expected to be fixed in a future release.
+
+```
+####<Feb 16, 2023 1:40:00 PM> <INFO> <Discoverer> <_add_to_dictionary> <WLSDPLY-06106> <Unable to add ServerFailureTrigger
+from location /Clusters/mycluster/OverloadProtection/mycluster to the model : Failed to convert the wlst attribute name and
+value for the model at location (model_folders = ['Cluster', 'OverloadProtection'],  'name_tokens' = {'DOMAIN': 'tododomain',
+'CLUSTER': 'mycluster','OVERLOADPROTECTION': 'mycluster'}) : The wlst attribute ServerFailureTrigger is not defined for the
+model folder /Cluster/OverloadProtection>
+```

documentation/2.0/content/release-notes/release-2.4.0.md → documentation/3.0/content/release-notes/release-2.4.0.md

@@ -1,7 +1,7 @@
 +++
 title = "Release 2.4.0"
 date = 2022-11-02T15:27:38-05:00
-weight = 5
+weight = 100
 pre = "<b> </b>"
 +++
 
@@ -34,5 +34,3 @@ pre = "<b> </b>"
 #### Known Issues
 - Due to the changes made for WDT-663, the resulting remotely discovered model contains extra fields that would not normally be there.
   This is an area of ongoing work to clean up the online aliases to not depend on these extra remote calls to produce a clean model.
-
-

documentation/2.0/content/release-notes/release-2.4.1.md → documentation/3.0/content/release-notes/release-2.4.1.md

@@ -1,7 +1,7 @@
 +++
 title = "Release 2.4.1"
 date = 2022-11-03T15:27:38-05:00
-weight = 5
+weight = 99
 pre = "<b> </b>"
 +++
 
@@ -24,5 +24,3 @@ None
 #### Known Issues
 - Due to the changes made for WDT-663 in WDT 2.4.0, the resulting remotely discovered model contains extra fields that would not normally be there.
   This is an area of ongoing work to clean up the online aliases to not depend on these extra remote calls to produce a clean model.
-
-

documentation/2.0/content/release-notes/release-2.4.2.md → documentation/3.0/content/release-notes/release-2.4.2.md

@@ -1,7 +1,7 @@
 +++
 title = "Release 2.4.2"
 date = 2022-11-10T15:27:38-05:00
-weight = 5
+weight = 98
 pre = "<b> </b>"
 +++
 
@@ -25,5 +25,3 @@ None
 #### Known Issues
 - Due to the changes made for WDT-663 in WDT 2.4.0, the resulting remotely discovered model contains extra fields that would not normally be there.
   This is an area of ongoing work to clean up the online aliases to not depend on these extra remote calls to produce a clean model.
-
-

documentation/2.0/content/release-notes/release-2.4.3.md → documentation/3.0/content/release-notes/release-2.4.3.md

@@ -1,7 +1,7 @@
 +++
 title = "Release 2.4.3"
 date = 2023-01-13T15:27:38-05:00
-weight = 5
+weight = 97
 pre = "<b> </b>"
 +++
 

documentation/2.0/content/release-notes/release-2.4.4.md → documentation/3.0/content/release-notes/release-2.4.4.md

@@ -1,7 +1,7 @@
 +++
 title = "Release 2.4.4"
 date = 2023-01-20T15:27:38-05:00
-weight = 5
+weight = 96
 pre = "<b> </b>"
 +++
 

documentation/2.0/content/rcuinfo.md → documentation/3.0/content/userguide/database/connect-db.md

@@ -1,10 +1,18 @@
+---
+title: "Connect to a Database"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 3
+description: "Create a connection to access your database."
+---
+
 ### Specifying RCU connection information in the model
 
-When creating a JRF domain, you can provide all the RCU connection information in a section `RCUDbInfo` under the `domainInfo` section in the model.  
-It provides you with more flexibility over the basic command-line arguments of 
+When creating a JRF domain, you can provide all the RCU connection information in a section `RCUDbInfo` under the `domainInfo` section in the model.
+It provides you with more flexibility over the basic command-line arguments of
 `-rcu_db` and `-rcu_prefix`.  Use this when the connection string is more complex and requires extra options.
 
-### Background on JRF domain RCU tables 
+### Background on JRF domain RCU tables
 
 A JRF domain creates several data sources from the JRF domain template.
 
@@ -156,7 +164,7 @@ domainInfo:
         rcu_admin_password : <database admin password is required only when you specify -run_rcu flag, will be prompted
          if not specified>
         rcu_db_conn_string : dbhost:1521/pdborcl
-```        
+```
 
 ### Specify variables for RCU
 
@@ -166,7 +174,7 @@ RCU `-variables` option of the repository creation utility can now be included i
 domainInfo:
     RCUDbInfo:
         rcu_variables : xxxx
-```    
+```
 
 ### Specify extended XML files for RCU
 
@@ -189,9 +197,9 @@ In the following examples of the JRF data source sparse model, you can use it to
 
 #### Default template data source
 
-This is a sparse model for JRF data sources with the RCU prefix `FMW1`.  
-You will need to update at least the `URL`, `PasswordEncrypted`, and the `user` property value.  When you specify the value of `URL`, it 
-must be a valid `JDBC URL` format, which is different from the `rcu_db_conn_string` which does not require the `jdbc:oracle:thin:...` part. 
+This is a sparse model for JRF data sources with the RCU prefix `FMW1`.
+You will need to update at least the `URL`, `PasswordEncrypted`, and the `user` property value.  When you specify the value of `URL`, it
+must be a valid `JDBC URL` format, which is different from the `rcu_db_conn_string` which does not require the `jdbc:oracle:thin:...` part.
 
 ```yaml
 resources:
@@ -313,7 +321,7 @@ resources:
 
 #### Oracle Active Grid Link Data Source (AGL)
 
-For setting the data source to access Oracle Active Grid Link database, besides updating the `URL`, `PasswordEncrypted`, and the `user` property value; 
+For setting the data source to access Oracle Active Grid Link database, besides updating the `URL`, `PasswordEncrypted`, and the `user` property value;
 you can specify additional `JDBCOracleParams` under `JdbcResource` of each data source.  For example,
 
 ```yaml
@@ -325,7 +333,7 @@ you can specify additional `JDBCOracleParams` under `JdbcResource` of each data
                 ....
 ```
 
-For the complete list of fields, run the WDT command, 
+For the complete list of fields, run the WDT command,
 
 ```shell
 modelHelp.sh -oracle_home <oracle home> resources:/JDBCSystemResource/JdbcResource/JDBCOracleParams
@@ -349,7 +357,7 @@ For example (note: details replaced by `....` for easier reading):
                 JDBCDriverParams:
                     URL: jdbc:oracle:thin://@somewhere:1521/db-node1
                     PasswordEncrypted:  'actualpassword`
-           .... 
+           ....
        'opss-data-source-1':
            ....
                JDBCDataSourceParams:
@@ -391,4 +399,3 @@ For the complete list of fields, run the WDT command,
 ```shell
 modelHelp.sh -oracle_home <oracle home> resources:/JDBCSystemResource/JdbcResource/JDBCOracleParams
 ```
-

documentation/2.0/content/release-notes/_index.md → documentation/3.0/content/userguide/limitations/limitations.md

@@ -1,63 +1,13 @@
-+++
-title = "Release Notes"
-date = 2019-02-22T15:27:38-05:00
-weight = 5
-pre = "<b> </b>"
-+++
-
-Review the following release notes for recent changes to WebLogic Deploy Tooling and known issues.
-
-- WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
-This may require some changes to existing models in order to be parsed correctly.
-   - Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need to be escaped in single or double quotation marks.
-   ```yaml
-   topology:
-       Server:
-           '!ms1':
-           ms2:
-   ```
-
-
-   - Model elements under the same parent should be indented to the exact same level. The previous YAML parser did not enforce this restriction,
-   but it is standard for YAML. In this example, each cluster is indented four spaces.
-   ```yaml
-   topology:
-       Cluster:
-           cluster1:
-               ClientCertProxyEnabled: True
-           cluster2:
-               WeblogicPluginEnabled: true
-   ```
-
-
-
-- Object lists in the `kubernetes` section of the model now should be specified in a hyphenated list format,
-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/).
-
-   ```yaml
-       clusters:
-       - clusterName: 'cluster1'
-         allowReplicasBelowMinDynClusterSize: true
-       - clusterName: 'cluster2'
-         allowReplicasBelowMinDynClusterSize: true
-   ```
-
-   - The "named object list" format is deprecated now, and will cause warning messages to be displayed.
-   ```yaml
-       clusters:
-         'cluster1':
-           allowReplicasBelowMinDynClusterSize: true
-         'cluster2':
-           allowReplicasBelowMinDynClusterSize: true
-   ```
-
-
-- The deprecated argument `-model_sample` has been removed from the Model Help Tool.
-The Model Help Tool has used model sample format by default since release 1.9.2.
-
-## Known issues for WebLogic Deploy Tooling
-
-The following list contains known issues. Each issue may contain a workaround or an associated issue number.
+---
+title: "Limitations"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 4
+description: "Review existing WDT limitations."
+---
+
+
+The following sections describe known limitations for WebLogic Deploy Tooling. Each issue may contain a workaround or an associated issue number.
 
 #### Discover Domain Tool `SEVERE` messages