Project

General

Profile

Bug #5423

Put kepler-server war file and kepler executatlbe as part of normal installation procedure

Added by Jing Tao almost 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Category:
sensor-view
Target version:
Start date:
06/13/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5423

Description

We will have a kepler-server component, it consists of three parts:
1. scheduler
2. workflow run engine
3. kepler itself.

First we should put them into a servlet war file.

Then will design and implement installer for these to put war and kepler
executable in place as part of the normal installation procedure.

Note: we should NOT have the duplicated kepler executables in the installer.

The priority order of the installer including the server components is

linux > mac > windows

History

#1 Updated by Jing Tao about 7 years ago

Now we are creating a product named kepler-run-engine. It consists four components -- the workflow run engine, the workflow run engine client, the scheduler and the scheduler client. This product will be released soon.

#2 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5423

Also available in: Atom PDF