What Exactly Goes on with V2 Config?

Experiment:

1. Create a new domain with this command:
   • asadmin create-domain --profile cluster --savelogin --adminport 4848 --user admin domain1
2. Edit domain.xml and add a marker property to default-config so we can verify if and when it gets copied. 1.xml
3. create a cluster with the following command 2.xml
   • asadmin create-cluster c1
4. create a node-agent 3.xml
5. Add a new marker property to c1-config name (C1-MARKER) and also change the value of the old MARKER 4.xml
   • asadmin set c1-config.system-property.MARKER=from-cluster-config
   • asadmin set c1-config.system-property.C1-MARKER=from-cluster-config-only
6. create a clustered instance 5.xml
   • asadmin create-instance --cluster c1 --nodeagent na1 ci1
7. create a stand-alone instance 6.xml
   • asadmin create-instance --nodeagent na1 ui1

Conclusions

• create-cluster made an exact copy of the config element named default-config and named it c1-config.
• When the stand-alone instance was created, an exact copy of default-config was made and named ui1-config
• When the clustered instance was made it simply referred to the cluster-config. No new config element was created.
• When a second clustered instance is created the PORTS are overridden in the server element but the same config (c1-config) is used again.
• At runtime in V3.1 we have to look at all the info in the config element for an instance AND all the info in the server element. The latter must override the former if applicable.