directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject directory-fortress-core git commit: more readme cleanup
Date Fri, 08 Jan 2016 05:13:21 GMT
Repository: directory-fortress-core
Updated Branches:
  refs/heads/master c01364c4a -> 53c00e263


more readme cleanup


Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/commit/53c00e26
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/tree/53c00e26
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/diff/53c00e26

Branch: refs/heads/master
Commit: 53c00e263548e8d2dc2fcdef5db6800e0920e406
Parents: c01364c
Author: Shawn McKinney <smckinney@apache.org>
Authored: Thu Jan 7 23:13:18 2016 -0600
Committer: Shawn McKinney <smckinney@apache.org>
Committed: Thu Jan 7 23:13:18 2016 -0600

----------------------------------------------------------------------
 README-CONFIG.md           |  57 ++++++++++-------------
 README-QUICKSTART-SLAPD.md |  28 +++++------
 README-TEN-MINUTE-GUIDE.md |   5 +-
 README.md                  | 100 ++++++++++++++++++++++------------------
 4 files changed, 95 insertions(+), 95 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/53c00e26/README-CONFIG.md
----------------------------------------------------------------------
diff --git a/README-CONFIG.md b/README-CONFIG.md
index 6e62127..a00c0f9 100644
--- a/README-CONFIG.md
+++ b/README-CONFIG.md
@@ -19,16 +19,17 @@
 # README for Apache Fortress Configuration Subsystem
 -------------------------------------------------------------------------------
 
-### This README covers these sections:
- * SECTION 1 - Fortress Configuration Subsystem Overview
- * SECTION 2 - Fortress Ant Property Files
- * SECTION 3 - Fortress Configuration Artifacts
- * SECTION 4 - Fortress Configuration Overrides
- * SECTION 5 - Precedence of Artifacts found in the Fortress Configuration Subsystem
- * SECTION 6 - Configuration Subsystem Usage
+## Table of Contents
+
+ * SECTION 1. Fortress Configuration Subsystem Overview.
+ * SECTION 2. Fortress Ant Property Files.
+ * SECTION 3. Fortress Configuration Artifacts.
+ * SECTION 4. Fortress Configuration Overrides.
+ * SECTION 5. Precedence of Artifacts found in the Fortress Configuration Subsystem.
+ * SECTION 6. Configuration Subsystem Usage.
 
 -------------------------------------------------------------------------------
-# SECTION 1.  Fortress Configuration Subsystem Overview
+## SECTION 1.  Fortress Configuration Subsystem Overview
 
 Fortress uses the following source property files to bootstrap configuration:
 
@@ -50,7 +51,7 @@ Notice the substitution parameters, **@name@**, contained within the above
confi
   substitution to seed implementation specific variables, e.g. host names, ports, pw's, into
its config artifacts used at runtime.
 
 -------------------------------------------------------------------------------
-# SECTION 2.  Fortress Ant Property Files
+## SECTION 2.  Fortress Ant Property Files
 
 Fortress configuration artifacts are seeded using Ant property files.
  * user.properties  - optional, when found, located in user's home directory.  Properties
found here take precedence over those following.
@@ -58,7 +59,7 @@ Fortress configuration artifacts are seeded using Ant property files.
  * build.properties - this file is required and must be located in the root folder of the
package.
 
 -------------------------------------------------------------------------------
-# SECTION 3.  Fortress Configuration Artifacts
+## SECTION 3.  Fortress Configuration Artifacts
 
 The ant config task, **init-fortress-config**, uses the values found within the Ant property
files to seed into the following targets:.
  * fortress.properties - contains name/value pairs inside of a property file.
@@ -66,9 +67,9 @@ The ant config task, **init-fortress-config**, uses the values found within
the
  * slapd.conf files - (optional) used to bind fortress to openldap.
 
 -------------------------------------------------------------------------------
-# SECTION 4.  Fortress Configuration Overrides
+## SECTION 4.  Fortress Configuration Overrides
 
-## Optional - Used to override fortress properties at runtime.
+### Optional - Used to override fortress properties at runtime.
 
  These fortress properties may be overridden at runtime by setting as Java System Properties:
  * fortress.host
@@ -86,19 +87,14 @@ The ant config task, **init-fortress-config**, uses the values found within
the
  * fortress.ldap.server.type
 
 ___________________________________________________________________________________
-# SECTION 5.  Precedence of Artifacts found in the Fortress Configuration Subsystem
-
-### Fortress uses apache commons configuration system to manage its properties inside its
Java runtime environment.
+## SECTION 5.  Precedence of Artifacts found in the Fortress Configuration Subsystem
 
 This subsystem has been hard wired to pick up properties in the following order:
  1. fortress.properties file - found on the classpath of that name.
  2. Java system properties - to override any of the 13 properties listed above.
  3. LDAP configuration node - found by config coordinates set in the fortress.properties
file itself.
-
-
-These properties are mutable inside the fortress config subsystem which allows C's values
to override B's to override A's.
-___________________________________________________________________________________
-# SECTION 6.  Configuration Subsystem Usage
+__________________________________________________________________________________
+## SECTION 6.  Configuration Subsystem Usage
 
 The general flow is the fortress.properties provide the coordinates to locate an ldap entry
on a remote server.
 The fortress.properties file is picked off the runtime classpath during startup.  Some props
may be overridden as Java system properties.
@@ -130,19 +126,14 @@ Or B
 The A script refreshes the entire LDAP server DIT, which includes deletes of all entries
under the suffix, recreating the DIT node structure, and re-adding of the config node.
 B just updates the configuration node with the new values, preserving all other data.
 
- * If you need to change an existing ldap system already in use by others, you may modify
the values inside the fortress.properties directly, skipping the interim step of updating
the ant properties files and re-running mvn install.
- * If the config node must be changed, use any general purpose ldapbrowser to mod its values.
 Fortress also has config apis to use (ConfigMgr) that add, update and delete configuration
entries.
- * Fortress Web will soon have a configuration dialogue page for doing this.
-
-### More notes:
- * Use caution when running the -Dload.file target with 'refreshLDAPData.xml' as that script
also deletes all nodes the suffix before it reloads anew.
- * Use the config node update script if you want to update values in the remote configuration
without scrubbing data from the DIT.
- * Don't run refreshLDAPData.xml in production, run ConfigNodeUPdate.xml instead.
- * There is nothing stopping you from placing all properties inside the fortress.properties
file and not the configuration node.
- * The idea is to minimize the number of locations where the same data must be stored.  Imagine
a network with hundreds, even thousands of fortress agents running.
- * We don't need to replicate the same data everywhere which is where remote config nodes
are used.
- * Tailor these procedures to match your requirements.
- * For more info on which parameters are used where, look at the init-fortress-config target
located inside the build.xml file.
+
+ ### More notes:
+ * Use caution when running the **refreshLDAPData.xml** script.  It deletes all nodes below
the suffix before readding.
+ * To change values in a config node, use a general purpose ldapbrowser.  Fortress has config
apis for this (ConfigMgr) to perform CRUD on config data.
+ * Another option is to use a script like **ConfigNodeUpdate.xml** to perform the CRUD ops.
+ * You can also *simply* place the properties inside the fortress.properties file (only).
 The idea is to minimize the number of locations
+ where the same data must be stored.  Imagine a network with hundreds, even thousands of
fortress agents running.  We don't need to replicate the same data everywhere which is where
remote config nodes help.
+ * For more info on which parameters are used where, look at the **init-fortress-config**
target located inside the [build.xml](build.xml) file.
 
  ___________________________________________________________________________________
   #### END OF README-CONFIG
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/53c00e26/README-QUICKSTART-SLAPD.md
----------------------------------------------------------------------
diff --git a/README-QUICKSTART-SLAPD.md b/README-QUICKSTART-SLAPD.md
index 7e50cba..584d5bc 100644
--- a/README-QUICKSTART-SLAPD.md
+++ b/README-QUICKSTART-SLAPD.md
@@ -17,22 +17,22 @@
    under the License.
 
 # Apache Fortress and OpenLDAP QUICKSTART
+
  Apache Fortress Version 1.0-RC41 System Architecture Diagram
  ![OpenLDAP Accelerator System Architecture](images/fortress-openldap-accel-system-arch.png
"OpenLDAP & Apache Fortress System Architecture")
 
 -------------------------------------------------------------------------------
+## Table of Contents
 
-This README Covers:
-
- * SECTION 1 - Prerequisites
- * SECTION 2 - Apache Fortress Core and OpenLDAP Setup
- * SECTION 3 - Apache Fortress Realm Setup
- * SECTION 4 - Apache Tomcat Setup
- * SECTION 5 - Apache Fortress Rest Setup
- * SECTION 6 - Apache Fortress Web Setup
+ * SECTION 1. Prerequisites
+ * SECTION 2. Apache Fortress Core and OpenLDAP Setup
+ * SECTION 3. Apache Fortress Realm Setup
+ * SECTION 4. Apache Tomcat Setup
+ * SECTION 5. Apache Fortress Rest Setup
+ * SECTION 6. Apache Fortress Web Setup
 
 -------------------------------------------------------------------------------
-# SECTION 1 - Prerequisites
+## SECTION 1. Prerequisites
 
 Minimum hardware requirements:
  * 2 Cores
@@ -46,7 +46,7 @@ Minimum software requirements:
 
 Everything else covered in steps that follow.  Tested on Debian & Centos systems.
 ___________________________________________________________________________________
-# SECTION 2 - Apache Fortress Core and OpenLDAP Setup
+## SECTION 2. Apache Fortress Core and OpenLDAP Setup
 
 1. Download and prepare the package:
 
@@ -150,7 +150,7 @@ ________________________________________________________________________________
  * SECTION 14. Instructions to performance test.
 
 ___________________________________________________________________________________
-# SECTION 3 - Apache Fortress Realm Setup
+## SECTION 3. Apache Fortress Realm Setup
 
 During this section, you will be asked to setup Apache Fortress Realm.
 
@@ -168,7 +168,7 @@ During this section, you will be asked to setup Apache Fortress Realm.
  ```
 
 ___________________________________________________________________________________
-# SECTION 4 - Apache Tomcat Setup
+## SECTION 4. Apache Tomcat Setup
 
 During this section, you will be asked to setup Apache Tomcat 8 and prepare for usage with
Apache Fortress
 
@@ -223,7 +223,7 @@ During this section, you will be asked to setup Apache Tomcat 8 and prepare
for
  ```
 
 ___________________________________________________________________________________
-# SECTION 5 - Apache Fortress Rest Setup
+## SECTION 5. Apache Fortress Rest Setup
 
 During this section, you will be asked to setup Apache Fortress Rest Application
 
@@ -266,7 +266,7 @@ During this section, you will be asked to setup Apache Fortress Rest Application
  ```
 
 ___________________________________________________________________________________
-# SECTION 6 - Apache Fortress Web Setup
+## SECTION 6. Apache Fortress Web Setup
 
 During this section, you will be asked to setup Apache Fortress Web Application
 

http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/53c00e26/README-TEN-MINUTE-GUIDE.md
----------------------------------------------------------------------
diff --git a/README-TEN-MINUTE-GUIDE.md b/README-TEN-MINUTE-GUIDE.md
index 0c9e06b..e5a81e0 100644
--- a/README-TEN-MINUTE-GUIDE.md
+++ b/README-TEN-MINUTE-GUIDE.md
@@ -18,6 +18,7 @@
 
 -------------------------------------------------------------------------------
 # README for Apache Fortress Ten Minute Guide
+
  * Version 1.0-RC41
  * last updated: January 6, 2016
 
@@ -29,7 +30,7 @@ and install Apache Fortress software from source.  It also shows how to
install
 ApacheDS LDAP server and get it working with Fortress.
 
 -------------------------------------------------------------------------------
-# Prerequisites
+## Prerequisites
 
 Minimum hardware requirements:
  * 2 Cores
@@ -43,7 +44,7 @@ Minimum software requirements:
 Everything else covered in steps that follow.  Tested on Debian & Centos systems.
 
 -------------------------------------------------------------------------------
-# Instructions for downloading app and generating the install doc:
+## Instructions for downloading app and generating the install doc:
 
 1. Clone the directory-fortress repos from apache git by commands:
 

http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/53c00e26/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index dc45bc8..0f0035e 100755
--- a/README.md
+++ b/README.md
@@ -18,23 +18,25 @@
 
 -------------------------------------------------------------------------------
 # README for Apache Fortress Core
+
  * Version 1.0-RC41
  * last updated: January 7, 2016
  * Apache Fortress Core System Architecture Diagram
  ![Apache Fortress Core System Architecture](images/fortress-core-system-arch.png "Apache
Fortress Core System Architecture")
 
 -------------------------------------------------------------------------------
-# Table of Contents
+## Table of Contents
+
  * Document Overview
- * Tips for first-time users of Apache Fortress
+ * Tips for first-time users.
  * SECTION 0.  Prerequisites
- * SECTION 1.  Options for using Apache Fortress and LDAP server together.
+ * SECTION 1.  Options for using Apache Fortress and LDAP.
  * SECTION 2.  Instructions for using Apache Fortress and ApacheDS LDAP server.
  * SECTION 3.  Instructions for using Apache Fortress and Symas OpenLDAP server.
  * SECTION 4.  Instructions for using Apache Fortress and native OpenLDAP server.
  * SECTION 5.  Instructions to pull Apache Fortress Core source code from GIT.
  * SECTION 6.  Instructions to build software package.
- * SECTION 7.  Instructions for installing OpenLDAP.
+ * SECTION 7.  Instructions for configuring OpenLDAP.
  * SECTION 8.  Instructions for using Apache Fortress with OpenLDAP.
  * SECTION 9.  Instructions to integration test.
  * SECTION 10. Instructions to load policy data using Apache Fortress Load utility.
@@ -45,22 +47,24 @@
  * SECTION 15. Instructions to encrypt LDAP passwords used in config files.
 
 ___________________________________________________________________________________
-# Document Overview
+## Document Overview
+
 This document contains instructions to download, build, and test operations with an LDAP
server using the Apache Fortress Core SDK.
 If you don't already have an LDAP server installed, goto **SECTION 1** for options.
 
 ___________________________________________________________________________________
-#  Tips for first-time users
+##  Tips for first-time users
+
  * If you see **FORTRESS_HOME**, refer to the package [root folder](.).
  * If you see **OPENLDAP_HOME**, refer to the root of OpenLDAP binary installation folder,
e.g. /opt/etc/openldap
  * This package's Apache Maven [pom.xml](./pom.xml) and Apache Ant [build.xml](./build.xml)
files are found in root folder.
  * Apache Ant is deprecated (in favor of Maven), but still used for some things.
-  * The configuration subsystem [README-CONFIG.md](./README-CONFIG.md) has more details.
+  * The configuration subsystem [README-CONFIG](./README-CONFIG.md) has more details.
  * Questions about this software package should be directed to its mailing list:
    * http://mail-archives.apache.org/mod_mbox/directory-fortress/
 
 -------------------------------------------------------------------------------
-# SECTION 0. Prerequisites
+## SECTION 0. Prerequisites
 
 Minimum hardware requirements to test on machine with an LDAP server:
  * 2 Cores
@@ -77,40 +81,40 @@ Notes:
  * Tested on Debian, Centos and Windows machines.
 
 ___________________________________________________________________________________
-# SECTION 1.  Options for using Apache Fortress and LDAP server together.
+## SECTION 1.  Options for using Apache Fortress and LDAP server
 
 This document describes three options to use Apache Fortress with:
 
-1. ApacheDS LDAP server (recommended for first-time users).
- * **SECTION 2** Apache Fortress and ApacheDS LDAP server.
+1. ApacheDS LDAP server (recommended for first-time users)
+ * **SECTION 2**. Apache Fortress and ApacheDS LDAP server
 2. Symas OpenLDAP server (quickstart)
- * **SECTION 3** Apache Fortress and Symas OpenLDAP server.
+ * **SECTION 3**. Apache Fortress and Symas OpenLDAP server
 3. Pre-existing OpenLDAP server (advanced)
- * **SECTION 4** Apache Fortress and native OpenLDAP server.
+ * **SECTION 4**. Apache Fortress and native OpenLDAP server
 
 ___________________________________________________________________________________
-# SECTION 2. Instructions for using Apache Fortress and ApacheDS LDAP server.
+## SECTION 2. Instructions for using Apache Fortress and ApacheDS LDAP server
 
- * Follow these instructions: [README-TEN-MINUTE-GUIDE.md](./README-TEN-MINUTE-GUIDE.md)
+ * Follow these instructions: [README-TEN-MINUTE-GUIDE](./README-TEN-MINUTE-GUIDE.md)
 
 ___________________________________________________________________________________
-# SECTION 3. Instructions for using Apache Fortress and Symas OpenLDAP server.
+## SECTION 3. Instructions for using Apache Fortress and Symas OpenLDAP server
 
- * Follow these instructions: [README-QUICKSTART-SLAPD.md](./README-QUICKSTART-SLAPD.md)
+ * Follow these instructions: [README-QUICKSTART-SLAPD](./README-QUICKSTART-SLAPD.md)
 
 ___________________________________________________________________________________
-# SECTION 4. Instructions for using Apache Fortress and native OpenLDAP server.
+## SECTION 4. Instructions for using Apache Fortress and native OpenLDAP server
 
  Do these sections:
 
  * SECTION 5.  Instructions to pull Apache Fortress Core source code from Apache GIT
- * SECTION 6.  Instructions to build software package.
- * SECTION 7.  Instructions for installing OpenLDAP.
- * SECTION 8.  Instructions for using Apache Fortress with OpenLDAP.
- * SECTION 9.  Instructions to integration test.
+ * SECTION 6.  Instructions to build software package
+ * SECTION 7.  Instructions for configuring OpenLDAP
+ * SECTION 8.  Instructions for using Apache Fortress with OpenLDAP
+ * SECTION 9.  Instructions to integration test
 
 ___________________________________________________________________________________
-# SECTION 5. Instructions to pull Apache Fortress source code from GIT.
+## SECTION 5. Instructions to pull Apache Fortress source code from GIT
 
 SNAPSHOTs from Apache GIT Software Repo:
 https://git-wip-us.apache.org/repos/asf?p=directory-fortress-core.git
@@ -120,7 +124,7 @@ Clone the Apache Fortress Core Git Repo::
  git clone https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
  ```
 ___________________________________________________________________________________
-# SECTION 6. Instructions to build software package.
+## SECTION 6. Instructions to build software package
 
 1. Set Java and Maven home on machines.
 
@@ -155,13 +159,17 @@ Build Notes:
  * Running ```mvn install``` calls out to maven-ant **init-fortress-config** task in [build.xml](./build.xml)
to regenerate configuration artifacts (more info here: [README-CONFIG](./README-CONFIG.md)).
 
 ___________________________________________________________________________________
-# SECTION 7. Instructions for installing OpenLDAP.
+## SECTION 7. Instructions for configuring OpenLDAP
 
 1. Install OpenLDAP using preferred method.
- * For example (existing package management system):
-   * On Debian systems: http://wiki.debian.org/LDAP/OpenLDAPSetup
-   * Ubuntu: https://help.ubuntu.com/community/OpenLDAPServer
-   * etc.
+
+ For example:
+
+ A. On Debian systems: http://wiki.debian.org/LDAP/OpenLDAPSetup
+
+ B. Ubuntu: https://help.ubuntu.com/community/OpenLDAPServer
+
+ C. etc.
 
 2. Copy fortress schema to openldap schema folder:
 
@@ -179,7 +187,7 @@ ________________________________________________________________________________
 
  Add to the top of the file:
  ```
-include	   OPENLDAP_HOME/etc/openldap/schema/fortress.schema
+ include OPENLDAP_HOME/etc/openldap/schema/fortress.schema
  ```
 
 4. For password policy support, enable pwpolicy overlay.
@@ -247,7 +255,7 @@ include	   OPENLDAP_HOME/etc/openldap/schema/fortress.schema
  ```
 
 ___________________________________________________________________________________
-# SECTION 8. Instructions for using Apache Fortress with OpenLDAP.
+## SECTION 8. Instructions for using Apache Fortress with OpenLDAP
 
 1. Copy FORTRESS_HOME/build.properties.example to build.properties and FORTRESS_HOME/slapd.properties.example
to slapd.properties:
 
@@ -347,11 +355,11 @@ ________________________________________________________________________________
 
 More Usage Notes:
  * For newcomers just trying to learn the ropes the defaults usually work.
- * [slapd.properties.example](slapd.properties.example) is where the OpenLDAP server defaults
reside.  This file, after being renamed to **slapd.properties**, will override values found
in build.properties.  Learn more about the configuration subsystem: [README-CONFIG.md](./README-CONFIG.md)
+ * [slapd.properties.example](slapd.properties.example) is where the OpenLDAP server defaults
reside.  This file, after being renamed to **slapd.properties**, will override values found
in build.properties.  Learn more about the configuration subsystem: [README-CONFIG](./README-CONFIG.md)
  * Unless you know what you are doing, don't change ant substitution parameters within the
properties.  These are are anything inside and including '${}'.  i.e. ${param1}.
 
 ___________________________________________________________________________________
-# SECTION 9. Instructions to integration test.
+## SECTION 9. Instructions to integration test
 
 1. From **FORTRESS_HOME** enter the following commands:
 
@@ -438,7 +446,7 @@ ________________________________________________________________________________
   * Warning messages are negative tests in action.
 
 ___________________________________________________________________________________
-# SECTION 10. Instructions to load policy data using Apache Fortress Load utility.
+## SECTION 10. Instructions to load policy data using Apache Fortress Load utility
 
  The Load utility is useful to create base policy configurations that need to be rerun many
times in different test and production environments.
  For samples look here: [./ldap/setup](./ldap/setup).
@@ -459,7 +467,7 @@ Policy Load Notes:
   * [./target/site/apidocs/org/apache/directory/fortress/core/ant/FortressAntTask.html](./target/site/apidocs/org/apache/directory/fortress/core/ant/FortressAntTask.html)
 
 ___________________________________________________________________________________
-# SECTION 11. Instructions to run the Apache Fortress Command Line Interpreter (CLI).
+## SECTION 11. Instructions to run the Apache Fortress Command Line Interpreter (CLI)
 
  The CLI is useful for ad-hoc policy administration in runtime environments.
 
@@ -516,7 +524,7 @@ ________________________________________________________________________________
  * [./target/site/apidocs/org/apache/directory/fortress/core/cli/package-summary.html/package-summary.html](./target/site/apidocs/org/apache/directory/fortress/core/cli/package-summary.html)
 
 ___________________________________________________________________________________
-# SECTION 12. Instructions to run the Apache Fortress Command Console.
+## SECTION 12. Instructions to run the Apache Fortress Command Console
 
  The Command Console is an interactive program that is allows ad-hoc edit and reporting on
data stored in LDAP server.
 
@@ -619,7 +627,7 @@ CHOOSE ADMIN MANAGER FUNCTION:
 6. etc... for PW Policy, ARBAC, Groups.
 
 ___________________________________________________________________________________
-# SECTION 13. Instructions to build and test the Apache Fortress samples.
+## SECTION 13. Instructions to build and test the Apache Fortress samples
 
 1. From **FORTRESS_HOME** enter the following command:
 
@@ -659,19 +667,19 @@ Sample Notes:
  * The 2nd and subsequent times runs, it will tear down the data loaded during the prior
run.
 
 ___________________________________________________________________________________
-# SECTION 14. Instructions to performance test.
+## SECTION 14. Instructions to performance test
 
  This section describes the Apache Fortress jmeter test programs.
 
-1. The .jmx files located in [.src/test/jmeter](.src/test/jmeter) folder are used to control
test settings.
+1. The .jmx files located in [.src/test/jmeter](.src/test/jmeter) folder are used to control
test settings for the following:
 
- * Fortress CheckAccess:
+ A. Fortress CheckAccess:
   [src/test/jmeter/ftCheckAccess.jmx](src/test/jmeter/ftCheckAccess.jmx)
 
- * Accelerator CheckAccess:
+ B. Accelerator CheckAccess:
   [src/test/jmeter/acCheckAccess.jmx](src/test/jmeter/acCheckAccess.jmx)
 
- * Accelerator CreateSession:
+ C. Accelerator CreateSession:
   [src/test/jmeter/acCreateSession.jmx](src/test/jmeter/acCreateSession.jmx)
 
 2. Load the security policy and users required by the jmeter test routines:
@@ -682,24 +690,24 @@ ________________________________________________________________________________
 
 3. From **FORTRESS_HOME** folder, enter the following command from a system prompt:
 
- * Fortress CheckAccess:
+ A. Fortress CheckAccess:
   ```
   mvn -Ploadtest-ftca jmeter:jmeter
   ```
 
- * Accelerator CheckAccess:
+ B. Accelerator CheckAccess:
   ```
   mvn -Ploadtest-accel jmeter:jmeter
   ```
 
- * Accelerator CreateSession:
+ C. Accelerator CreateSession:
   ```
   mvn -Ploadtest-accel-createsess
   ```
  The tests will run and produce measurements for throughput and latency.
 
 ___________________________________________________________________________________
-# SECTION 15. Instructions to encrypt LDAP passwords used in config files.
+## SECTION 15. Instructions to encrypt LDAP passwords used in config files
 
 If you need the passwords for LDAP service accounts to be encrypted before loading into Fortress
properties files you can
 use the 'encrypt' ant target.


Mime
View raw message