more sections

rosemarymarano · rosemarymarano · commit e3a714f2be07 · 2021-04-29T12:47:22.000-04:00
diff --git a/documentation/1.9/content/_index.md b/documentation/1.9/content/_index.md
@@ -3,40 +3,26 @@
 Many organizations are using WebLogic Server, with or without other Oracle Fusion Middleware components, to run their enterprise applications.  As more and more organizations move toward Continuous Delivery of their applications, the importance of automated testing grows.  Automating WebLogic Server domain creation and application deployment with hand-coded WLST scripts is challenging.  After those scripts exist for a project, they must be maintained as the project evolves.  WebLogic Deploy Tooling (WDT) removes the need for most users to write WLST scripts for routine domain creation and application deployment tasks.  Instead, you can write a declarative, metadata model describing the domain and applications (with their dependent resources), and use one or more of the single-purpose tools that perform domain lifecycle operations based on the content of the model.  This makes it easy to stand up environments and perform domain lifecycle operations in a repeatable fashion based on a metadata model that can be treated as source and evolve as the project evolves.
 
 
-WDT provides several single-purpose tools, all exposed as shell scripts (for both Windows and UNIX):
+WDT provides several single-purpose tools, all exposed as shell scripts (for both Windows and UNIX). For detailed information, see [WDT Tools]({{< relref "/userguide/tools/" >}}).
 
-- The [Create Domain Tool]({{< relref "/create.md" >}}) (`createDomain`) understands how to create a domain and populate the domain with all resources and applications specified in the model.
-- The [Update Domain Tool]({{< relref "/update.md" >}}) (`updateDomain`) understands how to update an existing domain and populate the domain with all resources and applications specified in the model, either in offline or online mode.
-- The [Deploy Applications Tool]({{< relref "/deploy.md" >}}) (`deployApps`) understands how to add resources and applications to an existing domain, either in offline or online mode.
-- The [Discover Domain Tool]({{< relref "/discover.md" >}}) (`discoverDomain`) introspects an existing domain and creates a model file describing the domain and an archive file of the binaries deployed to the domain.
-- The [Encrypt Model Tool]({{< relref "/encrypt.md" >}}) (`encryptModel`) encrypts the passwords in a model (or its variable file) using a user-provided passphrase.
-- The [Validate Model Tool]({{< relref "/validate.md" >}}) (`validateModel`) provides both standalone validation of a model as well as model usage information to help users write or edit their models.
-- The [Compare Model Tool]({{< relref "/compare.md" >}}) (`compareModel`) compares two model files.
-- The [Prepare Model Tool]({{< relref "/prepare.md" >}}) (`prepareModel`) prepares model files for deploying to WebLogic Kubernetes Operator environment.
-- The [Extract Domain Resource Tool]({{< relref "/kubernetes.md" >}}) (`extractDomainResource`) generates a domain resource YAML for use with the WebLogic Kubernetes Operator.
-- The [Variable Injector Tool]({{< relref "/variable_injection.md" >}}) is used to tokenize a model with variables.
-- The [Model Help Tool]({{< relref "/model_help.md" >}}) (`modelHelp.sh`) provides information about the folders and attributes that are valid for sections and folders of a domain model.
 
-As new use cases are discovered, new tools will likely be added to cover those operations but all will use the metadata model to describe what needs to be done.
+### Current production release
 
+The current [release](https://github.com/oracle/weblogic-deploy-tooling/releases) of WebLogic Deploy Tooling is 1.9.11. This release was published on March, 2021.
 
+### Recent changes and known issues
 
-### Supported WLS Versions
+See the [Release Notes]({{< relref "/release-notes.md" >}}) for recent changes, known issues, and workarounds.
 
-For the supported WebLogic Server and JDK versions required to run WebLogic Deploy Tooling, see [Supported WLS Versions]({{< relref "/wls_versions.md" >}}).
+### About this documentation
 
+This documentation includes sections targeted to different audiences. To help you find what you are looking for more easily, please consult this table of contents:
 
-## Concepts
+ 
 
-- [The Model]({{< relref "/model.md" >}})
-- [The Archive File]({{< relref "/archive.md" >}})
-- [Model Use Cases]({{< relref "/use_cases.md" >}})
-- [Tools Configuration]({{< relref "/tool_configuration.md" >}})
 
-## Developer Guide
 
-For information for developers, see the [Developer Guide]({{< relref "/developer/_index.md" >}}).
 
-## Known Issues
 
-See the following list of [Known Issues]({{< relref "/KnownIssues.md" >}}) and workarounds.
+### Contributing
+Those who wish to contribute to the WebLogic Deploy Tooling code will find useful information [here](https://github.com/oracle/weblogic-deploy-tooling/blob/master/CONTRIBUTING.md).
diff --git a/documentation/1.9/content/concepts/_index.md b/documentation/1.9/content/concepts/_index.md
@@ -0,0 +1,7 @@
++++
+title = "Concepts"
+date = 2019-02-22T15:27:54-05:00
+weight = 1
+chapter = true
+pre = "<b>1. </b>"
++++
diff --git a/documentation/1.9/content/concepts/archive.md b/documentation/1.9/content/concepts/archive.md
@@ -1,4 +1,10 @@
-# The Archive File
+---
+title: "Archive File"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 2
+---
+
 
 The archive file is used to deploy binaries and other file resources to the target domain. The archive is a ZIP file with a specific directory structure.  Any file resources referenced in the model that are not already on the target system must be stored in the correct location in the archive, and the model must reflect the path into the archive. The model itself can also be stored inside the archive, if desired.
 
@@ -51,7 +57,7 @@ wlsdeploy/applications/myApp/WEB-INF/weblogic.xml
 \* Expanded application directories are supported after WebLogic Deploy Tooling release 1.6.2
 
 ### `wlsdeploy/classpathLibraries`
-The root directory under which JARs/directories used for server classpaths are stored. Every file resource under this directory is extracted, even those not referenced in the model. 
+The root directory under which JARs/directories used for server classpaths are stored. Every file resource under this directory is extracted, even those not referenced in the model.
 
 ### `wlsdeploy/coherence`
 The root directory under which empty directories must exist for Coherence persistent stores.
@@ -84,7 +90,7 @@ The Create Domain, Update Domain, Deploy Applications, and Validate Model Tools
     weblogic-deploy\bin\createDomain.cmd -archive_file one.zip,two.zip,three.zip ...
 
 File resources can be present in any of these archives. Resources in each archive will supersede resources found in previous archives.
- 
+
 When the model references a resource that is present in multiple archives, the latest in the list takes precedence. For example, if the model references `wlsdeploy/applications/myapp.ear`, and that resource is present in archives `one.zip` and `two.zip`, the resource in `two.zip` will be used.
 
 A similar rule applies for resources that have an assumed location, but are not specifically called out in the model. For example, if archive `two.zip` has a wallet in location `atpwallet/wallet2.zip`, and `three.zip` has a wallet in location `atpwallet/wallet3.zip`, the wallet `atpwallet/wallet3.zip` will be used.
diff --git a/documentation/1.9/content/concepts/model.md b/documentation/1.9/content/concepts/model.md
@@ -1,4 +1,10 @@
-## The Metadata Model
+---
+title: "Metadata Model"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 1
+---
+
 
 The metadata model (or model, for short) is a version-independent description of a WebLogic Server domain configuration.  The tools are designed to support a sparse model so that the model need only describe what is required for the specific operation without describing other artifacts.  For example, to deploy an application that depends on a JDBC data source into an existing domain that may contain other applications or data sources, the model needs to describe only the application and the data source in question.  If the data source was previously created, the `deployApps` tool will not try to recreate it but may update part of that data source's configuration if the model description is different than the existing values.  If the application was previously deployed, the `deployApps` tool will compare the binaries to determine if the application needs to be redeployed or not.
 
diff --git a/documentation/1.9/content/concepts/target_env.md b/documentation/1.9/content/concepts/target_env.md
@@ -1,4 +1,10 @@
-## Target environments
+---
+title: "Target environments"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 4
+---
+
 
 The [Discover Domain]({{< relref "/discover.md" >}}) and [Prepare Model]({{< relref "/prepare.md" >}}) Tools allow you to customize the model and other files produced to be compatible with a specific target environment. Options for a target environment may include:
 - Using model tokens for some attributes in the model (see [Model Tokens]({{< relref "/model#model-tokens" >}}))
diff --git a/documentation/1.9/content/concepts/tool_configuration.md b/documentation/1.9/content/concepts/tool_configuration.md
@@ -1,4 +1,12 @@
-## Tools Configuration
+---
+title: "Tools Configuration"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 4
+---
+
+
+## Contents
  - [Tool Property File](#tool-property-file)
  - [Model Filters](#model-filters)
  - [Target Environments](config/target_env.md)
diff --git a/documentation/1.9/content/concepts/use_cases.md b/documentation/1.9/content/concepts/use_cases.md
@@ -1,4 +1,12 @@
-## Model Use Cases
+---
+title: "Model Use Cases"
+date: 2019-02-23T17:19:24-05:00
+draft: false
+weight: 3
+---
+
+
+## Contents
 
  - [Customizing the Administration Server](#administration-server-configuration)
  - [Modeling a Configured Cluster](#configured-cluster-sample)
diff --git a/documentation/1.9/content/release-notes.md b/documentation/1.9/content/release-notes.md
@@ -0,0 +1,48 @@
+
+#### WDT Version 1.9.11
+
+Issues addressed in this release:
+
+* Fixed validate process to recognize float values as strings.
+* Fixed JMS Server issue with jarray in store.
+* Fixed issue with recognizing NodeManager properties user and password as credentials.
+* Fixed discovery of SAFRemoteContext.
+* Fixed discovery of ServerTemplate DataSource.
+
+#### Known Issues for WebLogic Deploy Tooling
+
+The following list contains known issues. Each issue may contain a workaround or an associated issue number.
+
+##### Discover Domain Tool SEVERE Messages
+
+**ISSUE**:
+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.
+
+**ACTION**:
+Ignore the following messages logged during discovery of a 12.2.1.0 domain.
+```
+<Jan 14, 2019 1:14:21 PM> <SEVERE> <CommandExceptionHandler> <handleException> <> <Error: cd() failed.>
+<Jan 14, 2019 1:14:21 PM> <SEVERE> <CommandExceptionHandler> <handleException> <> <Error: ls() failed.>
+```
+
+##### Create Domain Tool with 11g JRF Domains
+
+**ISSUE**:
+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.
+
+**ACTION**:
+Run the WLS `rcu` command before executing `createDomain` for JRF domains
+
+##### Credential in Security Configuration
+
+**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:
+```
+java.lang.IllegalArgumentException: In production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean
+```
+**ACTION**: Contact Oracle Support to obtain the patch for bug number 30874677 for your WebLogic Server version before running the tool.
+
+##### Assigning Security Groups to Users
+
+**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.
diff --git a/documentation/1.9/content/samples/_index.md b/documentation/1.9/content/samples/_index.md
@@ -0,0 +1,10 @@
++++
+title = "Samples"
+date = 2019-02-22T15:27:54-05:00
+weight = 3
+chapter = true
+pre = "<b>3. </b>"
++++
+
+The samples provide demonstrations of how to accomplish common tasks.
+These samples are provided for educational and demonstration purposes only; they are not intended to be used in production deployments or to be depended upon to create production environments.
diff --git a/documentation/1.9/content/userguide/install.md b/documentation/1.9/content/userguide/install.md
@@ -4,10 +4,38 @@ date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 1
 ---
+
 #### Download and Install the Software
 
 The WebLogic Deploy Tooling project repository is located at [`https://github.com/oracle/weblogic-deploy-tooling`](https://github.com/oracle/weblogic-deploy-tooling).  
 Binary distributions of the `weblogic-deploy.zip` installer can be downloaded from the [GitHub Releases page](https://github.com/oracle/weblogic-deploy-tooling/releases).  
 
 1. To install the software, simply unzip the `weblogic-deploy.zip` installer on a machine that has the desired versions of WebLogic Server installed.  
 1. After being unzipped, the software is ready to use, just set the `JAVA_HOME` environment variable to point to a Java 7 or higher JDK  and the shell scripts are ready to run.
+
+#### Supported WLS Versions
+
+The following table specifies the supported WebLogic Server versions, along with the JDK versions, that must be used to run the WDT tool. You must set the `JAVA_HOME` environment variable to specify a JDK version different from the system default version.
+
+ To create a domain with the proper JDK (particularly if the `JAVA_HOME` is different from the one which will be used by the target domain), set the domain `JavaHome` attribute in the domain model.
+
+ **Note**: The WDT Encryption Model Tool used to encrypt and decrypt clear text passwords in the model and variable files, requires WDT to run with a minimum JDK version of 1.8.
+
+  | WebLogic Server Version | Tool JDK Version |
+  |--------------------------|-------------------|
+  | 10.3.6                   | 1.7               |
+  | 12.1.1                   | 1.7, 1.8          |
+  | 12.1.2 <sup>[1]</sup><sup>[2]</sup>         | 1.7, 1.8          |
+  | 12.1.3                   | 1.7, 1.8          |
+  | 12.2.1 <sup>[3]</sup>               | 1.8               |
+  | 12.2.1.1 <sup>[4]</sup>             | 1.8               |
+  | 12.2.1.2                 | 1.8               |
+  | 12.2.1.3                 | 1.8               |
+  | 12.2.1.4 <sup>[5]</sup>  | 1.8               |
+  | 14.1.1                   | 1.8, 1.11         |    
+
+***1*** First release dynamic clusters are supported  
+***2*** First release Coherence clusters are supported  
+***3*** First release WLS roles are supported  
+***4*** First release multitenancy is supported  
+***5*** Last release multitenancy is supported
