Feature #1845
runtime configuration UI and "wizard"
0%
Related issues
History
#1 Updated by Greg Shah almost 14 years ago
Make it easy to create all configuration to bring up a new server. It will need features to handle any dynamic/changing portions at client sites.
- private keys, certificates, keystores, truststores
- bootstrap configs
- directories
- ...
Configuration sources:
- the model for the original system architecture
- database servers
- appservers/pasoe instances
- clients
- GUI
- ChUI
- batch
- external system dependencies
- which components communicate with with others, via which protocols/APIs
- outputs from conversion such as the name map
- default values for OpenEdge
- scripts
- property files (e.g. for appserver/pasoe...)
.pffiles
We may need to parse some of these sources such as the .pf and property files.
#2 Updated by Greg Shah almost 14 years ago
- Target version set to Deployment and Management Improvements
#3 Updated by Greg Shah over 9 years ago
- Target version deleted (
Deployment and Management Improvements)
#4 Updated by Greg Shah over 5 years ago
- Related to Feature #5000: create a UI for managing the entire process/lifecycle of a conversion project added
#5 Updated by Greg Shah over 5 years ago
The UI for this task should be part of the project "IDE" (see #5000).
#6 Updated by Greg Shah 14 days ago
- Related to Feature #11355: VSCode extension added
#7 Updated by Greg Shah 14 days ago
- Subject changed from create a simple tool (and docs) to provide easy creation/import of the configuration for a new server to runtime configuration UI and "wizard"
Our develoment tools support is centered around VSCode (see #11355). We need a UI as part of that support which we can use for 2 purposes:
1. A guided approach (a "wizard") that creates a fully working runtime configuration based on answers to specific prompts. I expect this to be a deterministic tool that will create the runtime cfg based on a list of known answers. The UI should prompt the user for these answers and then run the tool. It is possible that some of these answers might come from reading cfg files from the legacy OE install.
2. A full UI for editing the runtime cfg, even for values not set via the wizard approach.
The runtime configuration to be created/edited is not just the server, it should include all aspects of a runtime configuration including things like batch processes, appserver/REST/SOAP/WEB agents and client configurations.
I wonder if item 2 above should be backed (at least partially) by our admin REST API to making live edits to an environment.
#8 Updated by Greg Shah 14 days ago
- Related to Feature #10459: migrate all project configuration into a single jSON configuration file added