summaryrefslogtreecommitdiffstats
path: root/docs/microservices/bluePrintsProcessorMS.rst
diff options
context:
space:
mode:
authorEzhilarasi <ezhrajam@in.ibm.com>2019-07-17 20:11:06 +0530
committerEzhilarasi <ezhrajam@in.ibm.com>2019-07-17 20:12:04 +0530
commit9f2794df0faeba95707fdf6459ad3b214ed90b39 (patch)
tree511b55c381c973bb1b1361b9a62ca63e7027e2a4 /docs/microservices/bluePrintsProcessorMS.rst
parentd42b731ce248b58d530901f02ac924e551b8d519 (diff)
Title section correction in BP MS
Change-Id: Ib97079159e9772408e4ea2dc2479992e4452a24a Issue-ID: CCSDK-1453 Signed-off-by: Ezhilarasi <ezhrajam@in.ibm.com>
Diffstat (limited to 'docs/microservices/bluePrintsProcessorMS.rst')
-rw-r--r--docs/microservices/bluePrintsProcessorMS.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/microservices/bluePrintsProcessorMS.rst b/docs/microservices/bluePrintsProcessorMS.rst
index 911f99945..3f308138f 100644
--- a/docs/microservices/bluePrintsProcessorMS.rst
+++ b/docs/microservices/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)