it's good here you defined dev=prod but in real time how they will make prod and dev and test as different with pointing is that with the property files or any changes in the platform??
Hi if the deployement type is onpremise, how can we make use of this properties,,,,because ours is a linux server and we have different ports while deploying we have to specify the port of the listener based on the environment and then we are deploying. will u please suggest how can we do this,,one idea which i got is simply dynamically i can specify the global property in global elements and then deploying the code...is that ok with Onprem deployemnt...
Already we provided "env"in global properties then y we need to give in run as arguments.simply changing in global properties isnt enough?. Kindly explain me about this
For more quality content on various integration tools & technologies, visit: tutorialspedia.com
The explanation was clear and easy to follow. It worked perfectly for me
it's good here you defined dev=prod but in real time how they will make prod and dev and test as different with pointing is that with the property files or any changes in the platform??
explanation is nice and easy to understand. It worked for me
Thanks for your feedback Sai Mohan.
Hi if the deployement type is onpremise, how can we make use of this properties,,,,because ours is a linux server and we have different ports while deploying we have to specify the port of the listener based on the environment and then we are deploying. will u please suggest how can we do this,,one idea which i got is simply dynamically i can specify the global property in global elements and then deploying the code...is that ok with Onprem deployemnt...
Already we provided "env"in global properties then y we need to give in run as arguments.simply changing in global properties isnt enough?. Kindly explain me about this
Very nice