What those extra Healthcare flags on Oracle SOA 188.8.131.52.5 and 12.2.1 update are for? by Bruno Neves Alves
January 15, 2017 Leave a comment
Whilst upgrading to 12.1.3.05 I came across the following Post Installation actions at the READ.ME doc of the 22524811 patch:
"4 Post-Installation Instructions"
2. Add em property : hc.jmsAndDBSameTxn with ‘true’ value.
3. Following Healthcare Server properties are needed:
+ ALL,<EP_1>,<EP_2> – comman separate value
+ Any endpoints after ALL will not be sequenced.
+ In this example, <EP_1> will have sequcing turned off. <EP_2> will have sequencing turned off.
Note for Bug 20029769:
hc.HCMode (true/false, default false) – need to set to true
At the customer, we intended to promote the upgrade to the actual production environment and, because of this, it required further validation of the impacts of such upgrade could bring.
Since the description was not clear enough and I could not find information anywhere else, I raised a service request at Oracle Support for further clarification.
First, I would like to thanks Silviu from Oracle Support for his help and support he have been providing me for the last few years 🙂
And here are the conclusions of the service request and clarification of the new flags usage:
hc.jmsAndDBSameTxn - if true, committing to the JMS for customer JMS will be on the same transaction as database. If database is rolled back, then the message will not be committed to JMS as well. (I’m waiting additional clarification for this point and will add it here once I have it). Read the complete article here.
For regular information on Oracle SOA Suite 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.