Merge "user guide demo for monitoring gui"

[policy/parent.git] / docs / drools / tutorial_cl.rst

diff --git a/docs/drools/tutorial_cl.rst b/docs/drools/tutorial_cl.rst
index 6579ed4..d7c2430 100644 (file)
--- a/docs/drools/tutorial_cl.rst
+++ b/docs/drools/tutorial_cl.rst
@@ -32,11 +32,13 @@ without companion components.
         sed -i "s/^RELEASE_REPOSITORY_ID=.*$/RELEASE_REPOSITORY_ID=/g" base.conf
         sed -i "s/^RELEASE_REPOSITORY_URL=.*$/RELEASE_REPOSITORY_URL=/g" base.conf
 
+        Note: For MacOS use - sed -i'' -e "s/^SQL_HOST=.*$/SQL_HOST=/g" base.conf and similar for all sed commands.
+
 **Step 3:** Open a *bash* shell into the PDP-D Control Loop container.
 
     .. code-block:: bash
 
-        docker run --rm --env-file config/base.conf -p 9696:9696 -it --name pdp nexus3.onap.org:10001/onap/policy-pdpd-cl:1.4.1 bash
+        docker run --rm --env-file config/base.conf -p 9696:9696 -p 6969:6969 -it --name pdpd -h pdpd nexus3.onap.org:10001/onap/policy-pdpd-cl:1.4.1 bash
 
 **Step 4:** Disable the distributed-locking feature, since this is a single CL PDP-D instance.
 
@@ -44,26 +46,34 @@ without companion components.
 
         features disable distributed-locking
 
-**Step 4:** [OPTIONAL] If using simulators (see tutorials), enable the *controlloop-utils* feature.
+**Step 5:** If using simulators (see tutorials), enable the *controlloop-utils* feature.
 
     .. code-block:: bash
 
         features enable controlloop-utils
 
-**Step 5:** [OPTIONAL] To reduce error logs due to being unable to communicate with DMaaP, change the official configuration to use *noop* topics instead (no network IO involved).
+**Step 6:** To reduce error logs due to being unable to communicate with DMaaP, change the official configuration to use *noop* topics instead (no network IO involved).
 
     .. code-block:: bash
 
         cd $POLICY_HOME/config
         sed -i "s/^dmaap/noop/g" *.properties
 
-**Step 5:** Start the CL PDP-D.
+**Step 7:** Disable PDP-X guard functionality.
+
+    .. code-block:: bash
+
+        cd $POLICY_HOME/config
+        sed -i "s/^guard.disabled=*$/guard.disabled=true/g" $POLICY_HOME/config/controlloop.properties.environment
+        sed -i "s/^aai.customQuery=*$/aai.customQuery=false/g" $POLICY_HOME/config/controlloop.properties.environment
+
+**Step 8:** Start the CL PDP-D.
 
     .. code-block:: bash
 
         policy start
 
-**Step 6:** Place the CL PDP-D in *ACTIVE* mode.
+**Step 9:** Place the CL PDP-D in *ACTIVE* mode.
 
     .. code-block:: bash
 
@@ -73,7 +83,7 @@ without companion components.
           "messageName": "PDP_STATE_CHANGE",
           "requestId": "385146af-adeb-4157-b97d-6ae85c1ddcb3",
           "timestampMs": 1555791893587,
-          "name": "8a9e0c256c59",
+          "name": "pdpd",
           "pdpGroup": "controlloop",
           "pdpSubgroup": "drools"
         }
@@ -90,10 +100,8 @@ Proceed with testing your new policy as described in the specific tutorials:
 • vCPE - `Tutorial: Testing the vCPE use case in a standalone PDP-D <tutorial_vCPE.html>`_
 • vDNS - `Tutorial: Testing the vDNS Use Case in a standalone PDP-D <tutorial_vDNS.html>`_
 • vFW - `Tutorial: Testing the vFW flow in a standalone PDP-D <tutorial_vFW.html>`_
-• VoLTE - `Tutorial: Testing the VOLTE Use Case in a standalone PDP-D <tutorial_VOLTE.html>`_
-
 
-.. seealso:: To deploy a control loop in Eclipse from the control loop archetype template, refer to `Modifying the Release Template  <modAmsterTemplate.html>`_.
+.. seealso:: `Methods to run PDP-D <runningPDPD.html>`_.
 
 
 End of Document