What those extra Healthcare flags on Oracle SOA 12.1.3.0.5 and 12.2.1 update are for? by Bruno Neves Alves

 

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:
        – hc.sequencedEndpoints
                + 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.

SOA & BPM Partner Community

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.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

B2B 12c – HTTP Generic Channel with transport callout by Bruno Neves Alves

 

First of all, season’s greetings to everyone!

Then, let me introduce this post saying that, already in the version 11g, a generic HTTP listening channel for message posting to B2B using the HTTP protocol was available. Any configured trading partner could use this generic channel to post messages to B2B.

A single common URL was available by default:
http://%5Bhost-name%5D:%5Bhost-port%5D/b2b/httpReceiver

In this way, a single listening channel is able to serve multiple trading partners for every HTTP communications with B2B.

When this channel is used, the process follows the default steps for message processing, namely:

Sender identification (i.e. using HTTP Header);

Document protocol/version/type identification ;

Agreement identification;

Message processing (parsing and validation);

Synchronous delivery to a back-end application.

The only differentiation factor is: since this channel is generic and not configurable or even available on the list of listening channels in B2B console, make it unavailable for channel callout configuration.

This has now changed with the 12c version.

With the version 12c of B2B is now possible to define a generic HTTP transport callout and associate it with a specific transport level callout.

As of now, this is driven by an B2B configuration Fusion Middleware property that needs to be added on Oracle Enterprise Manager Fusion Middleware Control

Read the complete article here.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

SOA Suite/B2B as a Critical Mission Hub for a High Volume Message Use Case by Bruno Alves

 

clip_image002

In this article, you will find described high availability solution architecture, covering B2B and core SOA Suite components as BPEL, along with Business Rules, Mediator and BAM integration, as well as lessons learned in conducting such a complex and mission-critical project starting from a set of legacy applications. Read the complete article here.

SOA & BPM Partner Community

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.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

B2B 12c – Listening Channel activation and deactivation in bulk Bruno Neves Alves

 

clip_image002With the version 12c of B2B the possibility to activate and deactivate all listening channels in one single command was introduced. Previously, it was necessary to provide the name of the listening channels to perform the action, what, in scenarios with a considerable number of listening channels, made the task ineffective.

Different scenarios can be pointed out where this functionality is extremely useful:

· After importing a B2B configuration the channels are always in deactivated status. This command can be then executed in order to activate all the listening channels in bulk;

· Deactivate all listening channels to stop momentously all message consumption for corrective or preventive reasons into B2B or back-end applications;

· Switching the message consumption between two environments;

The feature is also provided in a command line based approach since is an extension to the already existing feature of enable/disable a particular listening channel. Therefore it is respecting the same prerequisites.

Prior to executing any B2B command line tool is necessary to set the following environment variables: Read the complete article here.

SOA & BPM Partner Community

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.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki