1. Create DAS 1.1 Default Cluster Config
We need to add ability to create a domain with default cluster config. create-domain command should have this. For example,
% asadmin create-domain myDomain
1.2 Centralized Administration - Dealing with Multiple Configs
When DAS is starting up, it needs to read the associated config (server-config). It also needs to read all other configuration elements for management (ex. create-jdbc-resource --target cluster1) on-demand. During phase one of this project, it is okay to load all configuration into DAS's memory. We must do the performance optimization later on so that DAS is able to scale with large domain.xml configuration.
| Feature |
Description |
Supported in v2.x |
Required in 3.1 |
Comment |
| Profiles |
--profile option |
developer or cluster profile |
No |
Profiles was a workaround in v2.x for not handling different configurations dynamically and efficiently. Not needed in 3.1. Differences in the default values between developer and cluster profile also. developer profile is tuned for developer productivity while cluster profile is tuned for deployment performance. We will need some sort of templating mechanism for initial configuration. |
| Dynamic default config |
Dynamically set optimal default values based on current modules. |
No |
Yes if possible |
We don't make any upfront commitment about using developer profile or cluster profile. If "clustering" module(s) are used and loaded in the system, we will need to set optimal values for clustering configuration. v2 developer vs cluster profile |
| Default cluster config |
Add default-cluster-config element to basic domain.xml template |
No, used cluster profile |
Yes |
Don't load/start any cluster services/modules(GMS) unless a cluster is defined. |
| New Templates |
--template option where user may specify new templates |
Yes |
Low priority |
We may want to expand on this for 3rd party config pluggability. |
|
