Deploying-and-Running-the-Build.md

@@ -39,6 +39,18 @@ Insert Image here
 14. Click **OK** and wait. (It would be good to change the **Context Root** to **UrbanPulseManagement**). The API will then be accesible at **http(s)://{hostname}:{port}/{ContextRoot}/** 
 
 
+![image](https://user-images.githubusercontent.com/102658834/170985312-6405640f-a7f1-4ec7-bd22-b6b128b28a74.png)
+
+15. After successful deployment the list of running applications is shown again. At https://localhost:8181/UrbanPulseManagement/status/ should now be able to see the status page of. You can find the Swagger description of the API at https://localhost:8181/UrbanPulseManagement/docs/
+
+![image](https://user-images.githubusercontent.com/102658834/170985381-3c4cf4db-1d77-4997-bb3c-f5f01b38f9d9.png)
+
+16. The Inbound module is in the **/UrbanPulse/HttpInboundModule** folder. The inbound interfaces are the entry point for data from different data sources, which can be integrated with [ui!] connectors. To configure the module, it is best to insert the configurations in the database in the up_inbound_setup table a few times to be able to deploy the module multiple times - insert into **up_inbound_setup (setupjson) values  ('{"receiverCount":1,"sendDestinations":["theCEP","thePersistence"]}‘);** The sendDestinations are the **Vertx addresses** or **Topics** where the received messages are sent.
+
+17. That folder also has a **config.json** file, which contains additional information like host and port (where the data is received default is 40777), keystore and keystorePassword to secure the server.
+
+18. To start the inbound you can use **run.bat** or **run.sh**. It is important that each module contains a valid **-Dvertx.hazelcast.config=..\default-cluster.xml** so that the Hazelcast service discovery can work. Example config under **/UrbanPulse/default-cluster.xml**.
+