If you are deploying a system bundle fragment for the 1st time to CQ, you may notice that the CQ server shuts down.
This issue is fixed in later CQ versions. If you have an M&S contract and require an urgent hotfix for this in CQ5.5 SP2.1 you should contact Daycare support.
Restart the CQ instance manually and everything should work as normal.
In LiveCycle ES it is possible to track the dependencies of parent forms to form fragments and vice versa using the functionality in Workbench ES.
In LiveCycle ES2 it is also possible to view the form fragments used by a parent form in Workbench > Form Design > Properties:
It is not possible to track the dependencies from a form fragment to see in which parent forms the fragment is used. This is due to the architectural changes related to the new application model in LiveCycle ES2.
In LiveCycle ES3 it is again possible to track the dependencies of parent forms to fragments and vice versa.
If you have a requirement to track the dependencies from fragments to parent forms in LiveCycle ES2, then you can do this using the LiveCycle API using code similar to below:
ResourceRepositoryClient repositoryClient = new ResourceRepositoryClient(myFactory);
String fragmentUri = "/Applications/TestApplication/1.0/fragments/AddressFragment.xdp";
List relations = repositoryClient.getRelated(fragmentUri, false, Relation.TYPE_DEPENDANT_OF);
Here is a full sample class you can execute to test this functionality against a running LC server (you will need to adjust the settings for your environment): ListDependencies.java