Boot order of the SOA composites

Question

Hi
Do we have any option to define the boot order of the SOA composites, during a server recycle.?
We are having issues in server during recycle. The dependent services are not brought up first, hence call to such not brought up services are failing.
The caller services are configured with MDS artifacts of the callee services, hence they can be brought up, even if the dependent services are not active.
Please suggest, if you have any options.

Answer 1

Hi,
Do you use 11g? In that case the best thing to do is to put the abstract version of all the services into the MDS.
Than base all the ui-wsdl references and all the wsdl-imports on the reference to the abstract wsdl in the mds (eg. replace all the wsdl-references with an oramds:/apps/... reference to the path in the mds).
In service references in the composite you should keep the ws.binding attributes (location and port) referencing the concrete (deployed) values. These are used on runtime.
If you do so (which is I think best practice), then there is no dependency at startup, so the chronology of starting up does not matter. At startup time it will use the abstract (ui) versions of the wsdl's. Only on runtime the concrete ones. See for instance: http://www.albinsblog.com/2011/11/oracle-soa-suite-10g-to-11g-migration_06.html.
If you use SOASuite 10g, you could do about the same. But then you should put all the wsdl's in a subfolder in the htdocs folder of the apache server. Then in the bpel.xml you there are the wsdlLocation and the wsdlRuntimeLocation properties for the designtime (abstract) and the runtime version (concrete) of the wsdl.
Regards,
Martien