Updated Deploying and Running the Build (markdown) authored by vijaykumardksr's avatar vijaykumardksr
......@@ -24,24 +24,20 @@ To avoid conflicts between library versions (e.g. Hazelcast).
![image](https://user-images.githubusercontent.com/102658834/170981716-654c5eaf-b186-47fa-ba00-00244d06eae8.png)
10. The JDNI Resource is at **Resources -> JNDI ->Custom** Resources and can also be edited in the portal.
10. The project can be built with **mvn clean install**. As a result, a *.war Datei file is will be created at **UrbanPulse/UrbanPulseManagement/target** as described in [2](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Building-the-Code)
Insert Image here
11. The project can be built with **mvn clean install**. As a result, a *.war Datei file is will be created at **UrbanPulse/UrbanPulseManagement/target** as described in [2](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Building-the-Code)
12. The file can also be deployed to Payara in Payara‘s management page, under unter **Applications -> Deploy**.
11. The file can also be deployed to Payara in Payara‘s management page, under unter **Applications -> Deploy**.
![image](https://user-images.githubusercontent.com/102658834/170982081-fbee5a03-3185-4149-9db4-393f90baac64.png)
13. Use **Choose File** to navigate to the ***.war** file in **/UrbanPulseManagement/target** and select it.
12. Use **Choose File** to navigate to the ***.war** file in **/UrbanPulseManagement/target** and select it.
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}/**
13. 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/
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)
......
......