| Item |
Type |
Comment |
Response |
| 1 |
Clarification |
Under "Update Center Integration", exactly how is the admin console stub replaced by the real admin console without restarting the app server? Also, is IPS used to install the real admin console package/module? |
in TP2, we have an adminConsoleAdaptor that intercept the first request to admin console and download the admingui.war from maven repo. UpdateCenter is providing API for us to download from the UC. Other plugin modules will also be available through UC. Yes, all this these will be IPS. |
| 2 |
Clarification |
Under "Update Center Integration", how do you limit the list of modules displayed to only those that plug into the console? And why do you limit it to just these modules? |
You are right that we can't tell the difference. This means we will list and allow update/install of all the modules detected. One Pager has been modified. |
| 3 |
Clarification |
Under "Limited Branding Support", how is the selection of branding elements controlled? Is it a choice made at runtime? Based on the environment? Based on properties? Or is it a choice made at build time? |
No details yet, probably will be using the same approach as OEM support in the pluggability one pager. |
| 4 |
Clarification |
Under "Domain Restart", why would a domain not be restartable? |
Domain restart requires support from admin infracstructure. Kedar mentioned that to be able to 'restart domain', user will need to specify an option when they start the domain, otherwise, it can't be restarted. Kedar will provide an API to let us know if such option exists. |
| 5 |
Clarification |
Under "Dependencies", what REST API are you referring to? The admin "CLI" REST API? Why do you use both that API and AMX? |
This REST API dependency is for getting the monitoring data only. Another approach may be through the telemetry object. AMX is not available to retrieve these data. |
