Often with a breakthrough concept, showing is better than just telling. Here is a chance for you to login to a JumpCenter environment and see an interactive demo of how implementation of applications are represented, controlled and recovered.
Click on: http://demo.jumpsoft.net
You’ll be able to:
- Click on an implementation, and then stop and start a process.
- See how JumpCenter responds to a crash and recovers an application.
- Watch how the crash impacts the implementation and other processes.
- Restart an implementation and see how JumpCenter stops and start all the dependent process in the correct order.
There is a comments tab in each implementation that contains an explanation of the architecture and dependencies of the implementation.
Documentation and Videos
If you want more information about how JumpCenter works
Glossary of Terms
As you go through the interactive demo, you may find it useful to review the following terminology:
An implementation is the grouping of one to many related processes, monitors and underlying hosts that are to be viewed as a higher level business entity, such as an instance of a specific application.
The state of an object can be up, degraded, partial or down. JumpCenter uses the following colors and symbols to differentiate these states across the system:
The term ‘process’ refers to something that runs on a HOST. This can be something run from the command line or managed as a service. Examples of processes include an Oracle database, WebLogic application server, Windows service, Apache Web service or custom programs. Processes can be started and stopped. There must also be a way to determine the status of whether a process is running or not.
The term ‘ACTION’ represents something that can be initiated from the UI by a user or by automatically by the Dynamix engine. Action availability will vary based on configuration rules, the state of things and user permissions. An example of an action would be to restart processes or run a command.
The term ‘monitor’ refers to an execution of a task that can be run to track the state of something over time. Within JumpCenter, monitors are used to help determine the overall state of things from a layer-7 application perspective.