more content

Author: rosemarymarano

documentation/1.9/content/_index.md

@@ -18,10 +18,10 @@ See the [Release Notes]({{< relref "/release-notes.md" >}}) for recent changes,
 
 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]({{< relref "/concepts/" >}}) explains the underlying metadata model, files, and configurations.
+* The [User guide]({{< relref "/userguide/" >}}) contains detailed usage information, including how to install and configure WebLogic Deploy Tooling, and how to use the tools to .
+* The [Samples]({{< relref "/samples/" >}}) provide detailed example code and instructions that show you how to perform various tasks.
+* The [Developer guide]({{< relref "/developer/" >}}) provides details for people who want to understand how WDT is built, tested, and so on.
 
 
 ### Contributing

documentation/1.9/content/concepts/_index.md

@@ -5,3 +5,5 @@ weight = 1
 chapter = true
 pre = "<b>1. </b>"
 +++
+
+# Concepts

documentation/1.9/content/concepts/archive.md

@@ -14,7 +14,7 @@ Note that file resources that already exist on the target system need not be inc
 - [Archive Structure](#archive-structure)
 - [Using Multiple Archive Files](#using-multiple-archive-files)
 
-## Example
+#### Example
 
 This example shows an application with a `SourcePath` value referencing an EAR file resource contained in the archive.
 
@@ -29,22 +29,22 @@ appDeployments:
 
 The example above shows the attribute `SourcePath` of the `simpleear` application with a value of `wlsdeploy/applications/simpleear.ear`.  The prefix `wlsdeploy/` indicates that the resource is located in the archive file in the specified location, and will be deployed to that directory in the domain, in this case `<domain-home>/wlsdeploy/applications/simpleear.ear`.
 
-## Archive Structure
+### Archive Structure
 
 These are the paths within the archive that are used for different types of resources. Users can create further directory structures underneath these locations to organize the files and directories as they see fit.  
 
-### `atpwallet`
+#### `atpwallet`
 
 The directory where a wallet can be stored for use with Oracle Autonomous Transaction Processing Cloud Database. The file resource name is not specified in the model, and is assumed to be a single ZIP file in the archive at this location.  
 
-### `model`
+#### `model`
 The directory where the model is optionally located. Only one model file, either in YAML or JSON, is allowed, and it must have the appropriate YAML or JSON file extension.
 
-### `opsswallet`
+#### `opsswallet`
 
 The directory where a wallet can be stored for use with Oracle Platform Security Services. The file resource name is not specified in the model, and is assumed to be a single ZIP file in the archive at this location.  
 
-### `wlsdeploy/applications`
+#### `wlsdeploy/applications`
 The root directory under which applications are stored. Applications can be stored in the archive as EAR or WAR files, or expanded* under this folder. A sample expanded WAR application might have these entries:
 ```
 wlsdeploy/applications/myApp/index.jsp
@@ -56,34 +56,34 @@ wlsdeploy/applications/myApp/WEB-INF/weblogic.xml
 
 \* Expanded application directories are supported after WebLogic Deploy Tooling release 1.6.2
 
-### `wlsdeploy/classpathLibraries`
+#### `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.
 
-### `wlsdeploy/coherence`
+#### `wlsdeploy/coherence`
 The root directory under which empty directories must exist for Coherence persistent stores.
 
-### `wlsdeploy/domainBin`
+#### `wlsdeploy/domainBin`
 The root directory under which $DOMAIN_HOME/bin scripts are stored. Only scripts referenced in the `domainInfo/domainBin` section of the model are extracted.
 
-### `wlsdeploy/domainLibraries`
+#### `wlsdeploy/domainLibraries`
 The root directory under which `$DOMAIN_HOME/lib` libraries are stored. Only libraries referenced in the `domainInfo/domainLibraries` section of the model are extracted.
 
-### `wlsdeploy/nodeManager`
+#### `wlsdeploy/nodeManager`
 The root directory under which node manager file resources, such as keystore files, are stored.
 
-### `wlsdeploy/scripts`
+#### `wlsdeploy/scripts`
 The root directory under which scripts are stored. These can include JDBC create scripts, and WLDF action scripts.
 
-### `wlsdeploy/servers`
+#### `wlsdeploy/servers`
 The root directory under which server files, such as keystore files, are stored. These are organized by server name, such as `wlsdeploy/server/my-server/mykey.jks`
 
-### `wlsdeploy/sharedLibraries`
+#### `wlsdeploy/sharedLibraries`
 The root directory under which shared libraries are stored. These are stored as JAR files within the archive.
 
-### `wlsdeploy/stores`
+#### `wlsdeploy/stores`
 The root directory under which empty directories must exist for `FileStore` elements in the model.
 
-## Using Multiple Archive Files
+### Using Multiple Archive Files
 
 The Create Domain, Update Domain, Deploy Applications, and Validate Model Tools allow the specification of multiple archive files on the command line. For example:
 

documentation/1.9/content/concepts/model.md

@@ -31,7 +31,7 @@ The model is written in YAML (or optionally, JSON).  The YAML parser, built into
 
 All assignment statements must have one or more spaces between the colon and the value.  All comments must have a space after the pound sign (also known as hash) to be considered a comment.  YAML doesn't allow comments in all locations.  While the YAML parser used by the framework does not try to enforce these restrictions, it is likely that putting comments in some locations may cause parse errors since YAML is a difficult language to parse due to its complex indention rules.
 
-## Contents
+#### Contents
 
 - [Top-Level Sections](#top-level-model-sections)
 - [Simple Example](#simple-example)

documentation/1.9/content/concepts/target_env.md

@@ -2,7 +2,7 @@
 title: "Target environments"
 date: 2019-02-23T17:19:24-05:00
 draft: false
-weight: 4
+weight: 5
 ---
 
 

documentation/1.9/content/concepts/tool_configuration.md

@@ -6,7 +6,7 @@ weight: 4
 ---
 
 
-## Contents
+#### Contents
  - [Tool Property File](#tool-property-file)
  - [Model Filters](#model-filters)
  - [Target Environments](config/target_env.md)
@@ -15,7 +15,7 @@ weight: 4
  - [Custom Configuration](#custom-configuration)
 
  ### Tool Property File
- You can configure or tune WebLogic Deploy Tooling tools using the tool property file. This property file is installed as `<weblogic-deploy>/lib/tool.properties`. You may change the value of any of the properties in this file to tune the WDT tool. Another option is to configure the tool properties in a Custom Configuration directory. Create the `tool.properties` file in the $WDT_CUSTOM_CONFIG directory.
+ You can configure or tune WebLogic Deploy Tooling tools using the tool property file. This property file is installed as `<weblogic-deploy>/lib/tool.properties`. You may change the value of any of the properties in this file to tune the WDT tool. Another option is to configure the tool properties in a Custom Configuration directory. Create the `tool.properties` file in the `$WDT_CUSTOM_CONFIG` directory.
 
  If a property is removed from the file, or a property value is incorrectly formatted, a `WARNING` message is logged and an internal default value used instead of the missing or bad value.
 

documentation/1.9/content/samples/_index.md

@@ -5,6 +5,7 @@ weight = 3
 chapter = true
 pre = "<b>3. </b>"
 +++
+# Samples
 
 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.

documentation/1.9/content/userguide/_index.md

@@ -6,4 +6,6 @@ chapter = true
 pre = "<b>2. </b>"
 +++
 
+# User Guide
+
 The User Guide provides detailed information about installing and using WebLogic Deploy Tools.