aboutsummaryrefslogtreecommitdiffstats
path: root/docs/bluePrintsProcessorMS.rst
diff options
context:
space:
mode:
authorEzhilarasi <ezhrajam@in.ibm.com>2019-07-05 13:29:54 +0530
committerEzhilarasi <ezhrajam@in.ibm.com>2019-07-05 13:30:09 +0530
commitde33f3c7218d50d3f2e374796886b536b315a846 (patch)
treee500bc15b523ec1205b41d4b4d121934943ddeaf /docs/bluePrintsProcessorMS.rst
parenta6fae85764a8dfbeba6000a060b8be0f21fb0466 (diff)
Corrected title section in Microservice index
Change-Id: I67a34bdc3709566f86d428f0f703aa5470724eab Issue-ID: CCSDK-1453 Signed-off-by: Ezhilarasi <ezhrajam@in.ibm.com>
Diffstat (limited to 'docs/bluePrintsProcessorMS.rst')
-rw-r--r--docs/bluePrintsProcessorMS.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/bluePrintsProcessorMS.rst b/docs/bluePrintsProcessorMS.rst
index 911f99945..3f308138f 100644
--- a/docs/bluePrintsProcessorMS.rst
+++ b/docs/bluePrintsProcessorMS.rst
@@ -14,7 +14,7 @@ Micro service to Manage Controller Blueprint Models, such as Resource Dictionary
This microservice is used to deploy Controller Blueprint Archive file in Run time database. This also helps to test the Valid Blueprint.
Architecture:
-==============
+-------------
|image0|
@@ -23,7 +23,7 @@ Architecture:
:width: 800px
Running Blueprints Processor Microservice Locally:
-==================================================
+--------------------------------------------------
The purpose of this page is to show how to run the Blueprints Processor microservice locally, using the docker-compose.yaml file provided in the project.
@@ -48,7 +48,7 @@ Build it using the Maven profile called Docker:
mvn clean install -Pdocker
Start Docker containers using docker-composer:
-==============================================
+----------------------------------------------
Navigate to the docker-compose file in the distribution module:
@@ -66,7 +66,7 @@ To verify the logs generated by docker-composer, type:
Testing the environment:
-========================
+------------------------
Point your browser to http://localhost:8000/api/v1/execution-service/ping (please note that the port is 8000, not 8080)