How to control deplomyent order of DCs in an SC for dependencies ?
I have two DCs in one SC: DC A is a J2EE application that depends on DC which is a J2EE library. I have deployed them separately to our development portal and everything works well.
I then checked it into the NWDI, built the SC as an SDA and tried to deploy it to our QA portal.
This deployment has failed and according to the log file it first tried to deploy DC A, this has ended with the following error: "Application <app> cannot be started. Reason: it has hard reference to DC B". Only then it deployed DC B successfully.
My question is: How come the deployment process does not take into account dependencies when deploying? Is there a way to control the deployment process and avoid this error?