Updated Deploying and Running the Build (markdown) authored by OSPODksr's avatar OSPODksr
After installing the required Components as described in [1](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Software-Components-Required), the next step is to configure the Payara Application Server and deploying the build from [2]. After installing the required Components as described in [1](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Software-Components-Required), the next step is to configure the Payara Application Server and deploying the build from [2].
1. In a shell, change to the Payara folder under /bin. That is where the start scripts of Payara (cmd and sh) are. 1. In a shell, change to the Payara folder under **/bin**. That is where the start scripts of Payara (cmd and sh) are.
2. Run **asadmin start-domain** in the shell to start Payara. If everything is ok, the output will show information regarding paths Logs, Admin Port, etc. The management console should be accessible at **http://localhost:4848/** 2. Run **asadmin start-domain** in the shell to start Payara. If everything is ok, the output will show information regarding paths Logs, Admin Port, etc. The management console should be accessible at **http://localhost:4848/**
![image](https://user-images.githubusercontent.com/102658834/170981057-6e8aed26-e297-4b66-8a94-75062e914688.png)
3. Then **asadmin create-jvm-options --target server-config "-Dfish.payara.classloading.delegate=false"**
To avoid conflicts between library versions (e.g. Hazelcast).