Project

General

Profile

Feature #6377

provide tooling (and UI in the admin interface) to manage appserver agents (start/stop/bounce)

Added by Greg Shah about 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
version:

History

#1 Updated by Greg Shah about 2 years ago

A customer that is heavily invested in classic appserver has to use the "trim" processing to stop appserver agents when they are consuming too many resources. They would prefer a "bounce" capability (stop and then restart) but OE doesn't provide it. This task is meant to expose some back capabilities in this regard. We must expose the rest of the appserver configuration as well as a view of the currently running agents.

#3 Updated by Greg Shah over 1 year ago

See #6878 for an example of the kind of status reporting that is available in OE. We must provide this level or better.

#5 Updated by Greg Shah over 1 year ago

I would prefer to implement this using a REST API. We will provide a CLI (command line interface) and would probably also implement a UI in the admin console. Having a REST API as the backing implementation gives customers the ultimate flexibility. They can create their own tooling if the built-in FWD tools don't meet their needs.

A first pass has been implemented for #7074 using the ServerDriver "status" approach. We will need to shift this to REST when possible.

Also available in: Atom PDF