SOA Suite 12c: keep running instances using ANT by Martien van den Akker
August 30, 2018 Leave a comment
At my current customer I implemented a poor man’s devops solution for Release and Deploy. It was based on a framework created as bunch of Ant projects, that I created years ago. It was based on scripts from Edwin Biemond. See for instance here, here and here. I never wrote about my solution, because although I refactored them quite intensively, the basics were already described thoroughly by him.
What I did was that I modularized the lot, split the environment property files, added logging, added OSB 12c support, based on the config jar tool, etc.
One thing I ran into this week was that at first deployment from our team to the test environment using my framework, the running instances for the BPM projects were aborted.
Now, if you take a look at the deploy.sarLocation target in Edwin’s article about deploying soa suite composites you’ll find that he also supported the overwrite and forceDefault properties.
When re-deploying a composite from JDeveloper you’re probably familiar with the ‘keep running instances’ checkbox. I was looking for the ANT alternative in the ${oracle.home}/bin/ant-sca-deploy.xml scripting. First I looked in the 12c docs (see 47.9.4 How to Use ant to Deploy a SOA Composite Application), but it is not documented there.
But when I opened the particular ant-sca-deploy.xml script I read: Read the complete article here.
For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Facebook
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress
