3

Assume I have a java program packaged in a executable jar which I normally start from the command line using java -jar myappjar.jar. Now I want to develop remote management application to launch this java program and also once launched I want to be able to stop it by which I mean it must call a method shutdown in my program which will do clean up work and exit the program.

Also when I launch the remote management application itself, it should tell me if the program I want to launch is already running, if so then stop it first.

Is all of above possible and how to achieve that ? Especially the most important is to be able to launch the program that is not running already.

The program that I launch is a server that keeps running forever until shutdown either manually or via remote management application. This server should in no way depend on JMX Agent or remote management application i.e. remote management application/JMX agent can be shutdown and server program still keeps running or server can be manually launched and later remote management application can be started to instrument this server program if so desired.

Improve this question

3 Answers 3

Reset to default
4
+175

What you actually need is a some kind of Management agent:

A Management agent is a software agent that runs on a managed node and provides an interface to manage it. It can perform operations on managed objects in the node and can also forward notifications to the manager.

Please see an example:

enter image description here

In your case it will be a JMX protocol between Management tool and applications. It is a precondition to have an Agent up and running on a remote host. It doesn't seem to be a hard task to develop a basic agent, capable of the following:

  • download/deploy an application
  • start/stop the application
  • monitor deployed application

Agent is a very simple application with several commands (management actions) implemented.

enter image description here

Useful link: Agents in Network Management

Update: glu agent example

glu is a free/open source deployment and monitoring automation platform. Glu is solving the following problems:

  • deploy (and monitor) applications to an arbitrary large set of nodes:
  • efficiently
  • with minimum/no human interaction
  • securely
  • in a reproducible manner

It is based on the same principle and has an agent in it:

The glu agent is an active process that needs to run on every host where applications need to be deployed. Its main role is to run glu scripts. It is the central piece of the deployment automation platform and is the only required piece of infrastructure. It exposes a REST api and a command line (which invokes the REST api under the cover).

Feel free to ask if you need some additional comments.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Assume I have class MyApp in myappjar.jar. In the main method of this class I instantiate an instance of my class after which my application keeps running like a server application. Your answer seems to suggest that JMX agent is part of my application so when I manually run my application from command line, this JMX agent will create instance of MyApp class? If so then if my application is manually shutdown which means the JMX agent will also be shutdown then how remote management application can start my application?
I'm suggesting to implement Agent as a separate application, capable of running your primary application. Agent can be designed as a some kind of persistent service - always up, always running. It should not be a problem, since it's functionality is very limited and footprint is very small.
If this Agent is shutdown, it will also shutdown my application along with it or my application can keep running? I am still trying to understand your solution.
No, agent and your applications has separate life-cycles. Agent is just a some kind of "remotely controlled application launcher".
2

Maybe I don't understand the question well, but JMX is just used to control your management application and it is somehow not relevant to problem of starting or stopping your application, isn't it?

Basically you can start new Process to execute java -jar myappjar.jar from your management application (e.g. via Runtime.exec()) Since you want controlled shutdown, you need kind of inter-process communication, so that your management application can shutdown your application, e.g. by sockets. This can be later on used also for "running" detection.

Improve this answer

Comments

1

Jenkins is a java based Continuous Integration Server which can launch applications remotely. You may check its source code for ideas.

For UNIX machine based setups, it uses SSH based approach (probably jsch)

Jenkins manages windows remoting using j-interop.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.