From a SOA development perspective adf-config.xml file is a configuration file which helps you in storing MDS related connection details. In case your project has references to any artifacts stored in MDS, the adf-config file will help you in connecting to, validating the artifact from MDS using the MDS store connection details provided in adf-config.xml.
I am listing few points below based on my experiences with adf-config.xml.
- During deployment, the entries inside the adf-config.xml are accessed to retrieve MDS connection details and connect to the MDS store for validating the artifacts before compilation of the composite.
- Further to deployment, adf-config.xml need to exist in the composite classes folder but contents will not be used.
- During loading of composites after bouncing the server any reference to oramds in composite files will look for the adf-config.xml in classes folder, even though the contents are not used.
- After deployment soa-infra will be referring to the mds-soa datasource for validation and loading the artifacts during server startup. The soainfra app will use its own adf-config.xml which just happens to have a single partition accessed through jdbc/mds/MDS_LocalTxDataSource. The partition is configured in Metadata repositories. When you run RCU the MDS repositories are created and repositories get registered in the EM. In case you want to configure new partitions for MDS or change DB –based to file based, those configurations can be done in Weblogic Domain > domain >Metadata Repositories
Thats it :)