I want to create Spring Boot project which runs without web services because I need to use it to process Kafka messages, SQL queries and webflux client.
Is it possible to disable the rest API functionality and to disable tomcat from exposing server on the network?
Related
I wanted to monitor my web application deployed in the production environment, monitoring tool notify me when the server down or any abnormal cases for that I decided to use spring admin, plz help to find the best resource for set upping spring admin with the spring boot project (correctly I'm using java melody for monitoring purpose, but I does not allow email notification)
I have this requirement that I need to check if the java application (not web app) is running or down via bash script.
It is non springboot application as well. It is just a normal spring application that connects and listen to kafka, get the the object from the topic and call an API.
We thought of to use spring actuator to check the health however it is not a web application.
What is the recommended way to check a non-web and non-springboot application if it is up or down?
Please advise.
I've created a spring boot based service and like to deploy it to existing mule API platform, then I realize there are some challenges I need to face by myself such as, service discovery and policy management.
To be specific, I want to know if there is any way to manage policy for spring boot service from mule API manager? Since there is no agent that mule service has.
The straight forward way is to proxy your custom API by generating a proxy in the Anypoint API Manager.
Deploy that proxy application on a Mule server in CloudHub or on a runtime on-premise.
Then you have your Spring Boot Application API under control and can apply policies, see analytics, etc.
MuleSoft Doc on API Proxy
What is the best way to enable HTTPS calls for my web service server application?
I'm using Spring Boot and gradle.
Thanks
I've developed a spring integration component that is to sit on a server and process messages coming in over an inbound RMI channel do some processing/filtering and then send out some messages over a different RMI channel.
Currently, for testing, I've been running it using a Main class that just loads the context, which sets up the inbound RMI gateway and it's working fine. But I don't think that this is appropriate for a production environment.
What is the best way to deploy this type of project to a server?
If I were working in a .Net I'd be deploying this type of application as a windows service, is that what I should be doing here?
The application that is sending me data is hosted in Tomcat, would it be a good idea to also run this application within the same Tomcat container (Current requirements are for both components to be on the same machine this may change)? And if so how?
I'm currently looking into Spring Boot, am I on the right path?
I think the best would be Spring Boot, as it's made to easily allow running different types of applications. Also, you don't need Tomcat if you can run the same component with a simple Main and not using UI. Spring Boot, also, has a sample using Spring Integration here, so you should be up and running in no time.