Fusion Order Demo - tips, tricks and traps
By clemens.utschig on Nov 26, 2009
As the latest version of Fusion Order Demo introduced a few new features, deployment got a little more complex as well (behind the scenes that is).
I have seen people in the field hitting two issues, over and over again.
The first one manifests itself through the following in the ant output:
[wldeploy] Task 3 initiated: [Deployer:149026]deploy application ExternalPartnerSupplierEjb on soa_server1.
[wldeploy] Task 3 failed: [Deployer:149026]deploy application ExternalPartnerSupplierEjb on soa_server1.
[wldeploy] Target state: deploy failed on Server soa_server1
[wldeploy] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: weblogic-sca, exact-match: false].
This happens because the ExternalSupplierEjb has a dependency on a shared library that get's deployed earlier - and in this case case could not be deployed. The key is to get "soa.server.oracle.home" in bin/build.properties right.
In my case this property points to "/scratch/cutschig/fmwhome/AS11gR1SOA". In a sibling directory of AS11gR1SOA you should find the wlserver_10.3 directory (in my case /scratch/cutschig/fmwhome/wlserver_10.3)
Secondly although it might seem deployment went through fine - you get
[clientgen] [ERROR] Invalid WSDL http://localhost:8001/soa-infra/services/default/OrderBookingComposite!1.0/orderprocessor_client_ep?wsdl during testing.
This means that your foreign.mds.type is NOT db and while compilation works, the deployment must fail, because the shared artifacts are simply not available on the remote server.
For the next version of FOD I'll make sure these problems can be found easier - sorry for the inconvenience.