I'm having some trouble deploying an esb process to another server then it was developed on, using ant.
Using Sjoerd's excellent article (http://www.oracle.com/technology/tech/soa/soa-suite-best-practices/auto-deploy.html) we created ant tasks that deploy our esb process to the server.
After extracting the deployment plan, deploying to the same server as we're developing on works fine.
However, if I change the url's in my deployment plan, and deploy to another server, the deployment fails. The exceptions I keep getting are due to the fact that ESB can't find files in a temp location:
[esb:deployESBProjects] Deployment Attempt Response :
[esb:deployESBProjects] <deploymentSummary>
[esb:deployESBProjects] <message>Entity Deployment Failed</message>
[esb:deployESBProjects] <errors>
[esb:deployESBProjects] <error code="1049" severity="5">
[esb:deployESBProjects] <description>WSDL "esb:///ESB_Projects/temp_ESB_FundeonAsyncEventRouter_srvhw21.kao.sbwinfra.nl/Fundit_wijzigingErkenningRS.wsdl" of service "Fundit.wijzigingErkenning
RS" is invalid or unaccessible. Following error is thrown by WSDL Parser : WSDL Parsing Failed: org.apache.slide.structure.ObjectNotFoundException: No object found at /files/ESB_Projects/temp_ESB_Fund
eonAsyncEventRouter_srvhw21.kao.sbwinfra.nl</description>
[esb:deployESBProjects] <fix>Ensure that the WSDL is accessible and valid. If the problem persists, Contact Oracle Support.</fix>
[esb:deployESBProjects] </error>
[esb:deployESBProjects] </errors>
[esb:deployESBProjects] </deploymentSummary>
[esb:deployESBProjects]
Somehow, ESB thinks it's a smart decision to concatenate the servername to this temporary directory called temp_ESB_FundeonAsyncEventRouter_srvhw21.kao.sbwinfra.nl.
The problem of course is, that this is different for development and test (and acceptance and production and... and...).
So now in the .esbsvc files there's a hardcoded location pointing to a directory with srvhw21 in it, while we're deploying on another server which has srvhw23.
Did anyone have this problem? Can I parametrize this setting by e.g. adding something to the deployment plan? Or maybe use variables in the .esbsvc files??
I tried a 'hack' by creating a symbolic on our (linux) server using ln -s, but that doesn't work (nor is it desirable).
Any help is much appreciated!
Cheers,
Bas