Downloading my comments for a reply:
We don’t know his entire scenario, but I have some indications:
That application allows you to deploy a . War to an external IP. Knowing clients' Ips, you can generate a script that goes from IP to IP by deploying the new version.
connect http://IP_DO_CLIENTE:8080/manager usuario senha
deploy aplicacao.war
I don’t know if there is a continuous integration process in your company. If so, you can associate the execution at the end of a new release, for example.
You can also develop an application that acts as an updater, which from time to time goes into a repository and checks if there is a newer version of that artifact. If yes, drop and make the new deploy
The two approaches have their technical and implementation difficulties. I suggest you take this answer as a north to be able to deepen your research :)
Good afternoon Pedro, not everyone. I agreed to this situation by creating a mediator who records the client’s ip from time to time. Since the backend is in the client, it sends the internal and external ip information of the same. I know there is no-ip, but I dismissed this question.
– Sérgio Thiago Mendonça
Well, in Wildfly there is Jboss-cli, which is a CLI that allows you to connect remote and deploy.. I believe there is something similar to Tomcat. I don’t know how is your continuous integration process, but I think valid, for example, after a "release", run a script that goes from ip to ip deploying the new applications
– Pedro
https://github.com/tomcatmanager/tomcatmanager
– Pedro
or you can take the reverse path, have a client application that searches your repository for a newer version
– Pedro
Thank you, I’ll read about.
– Sérgio Thiago Mendonça