Deploying-and-Running-the-Build.md

@@ -13,7 +13,8 @@ To avoid conflicts between library versions (e.g. Hazelcast).
 5. The Postgres driver jar must be copied into the **/glassfish/lib** folder. After that, Payara must be restarted **asadmin restart-domain**.
 ![image](https://user-images.githubusercontent.com/102658834/170981340-66fa7c68-5013-42ce-a5d9-a0b3fcc15c93.png)
 
-![image](https://user-images.githubusercontent.com/102658834/170981363-dcb0041e-5311-467c-abbf-fe2ce1feb18d.png)
+![image](https://user-images.githubusercontent.com/102675978/171004076-829b6591-49ae-4f63-8dfd-2e0775e61024.png)
+
 
 6. In **UrbanPulse/UrbanPulseResources/** there is a file called **glassfish-resources.xml**. This contains information (in the form of Java Naming and Directory Interface short JNDI variables and connection pools) such as connection to the database, connection to a keycloak server (comes later), etc.
 
@@ -41,7 +42,8 @@ To avoid conflicts between library versions (e.g. Hazelcast).
 
 14. 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)
+![image](https://user-images.githubusercontent.com/102675978/171005027-f5982a5a-6b30-44ac-b4bb-a10905b1588f.png)
+
 
 15. 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.
 
@@ -59,6 +61,11 @@ To avoid conflicts between library versions (e.g. Hazelcast).
 
 **java -Dvertx.hazelcast.config=..\default-cluster.xml -jar target\persistence-module-v3-11.0.13-SNAPSHOT.jar -conf config.json --cluster -SMinClusterSize=3**
 
+Example as screenshot > 
+
+![image](https://user-images.githubusercontent.com/102675978/171004533-e28ff9ae-8f72-4c74-943e-bfad2bacea2c.png)
+
+
 19. The module consists of a Complex Event Processing Engine and some configuration elements. The task of the CEP module is to receive and analyze events from the other platform modules to perform temporary analysis against the moving event stream.