Saturday Jun 04, 2016

Integrate Oracle SOA Healthcare and Oracle SOA Suite back-end composites across segregated domains by Bruno Neves Alves


clip_image001When implementing a composite with JDeveloper, one of the available adapters - since early versions of the 11g release of Oracle SOA Suite - is the Healthcare Adapter. This adapter allows to connect, both as exposed service (inbound) and as reference (outbound), to an Oracle SOA Suite for Healthcare Integration (SSHI) installation enabling document trading with other applications in the healthcare ecosystem.

The SSHI is mostly used for  HL7 documents exchange between back-end healthcare solutions and its satellite applications. However, in some other cases, SSHI is even implemented as a hub for document exchange, connecting heterogeneous healthcare applications.

The Healthcare adapter comes in two integration type flavors:

  • Default - in memory integration;
  • JMS - integration based on AQ or JMS queues.

The first one, based in memory, allows the SSHI application to integrate with the composites through the Healthcare Adapter using the JVM memory - what makes the integration quite efficient and fast - however, with one limitation: both SSHI and the SOA composites have to be deployed in the same domain.

Now, one of the best practices that should be taken in consideration when architecturing a large scale integration platform with SSHI and SOA Suite is to deploy the SSHI and the SOA back-end composite application in separated domains, favoring:

  • Tuning and configuration - domain configuration isolation is key to reach the sweet spot in such implementation. The domain where the composites are being deployed will likely demand different configuration compared with the SSHI dedicated one. This segregation will allow to apply different tuning strategies to one another.
  • Database partitioning - The fact that the SSHI and back-end composite application are persisting into separated SOA_INFRA schemas promotes separated database grow management strategies. This empowers an adequate data partitioning and purging strategies for each of the domains.

As explained, for an in memory integration, both domains needs to rely over the same JVM, therefore, separating the domains will presuppose two separated JVMs leaving the Default options as unusable.

This article demonstrates how the JMS integration can be implemented between SSHI and the back-end application available from two separated domains.
For questions of demonstrability it will follow a simplistic SSHI as a hub implementation. Because of that, the article additionally covers all the necessary steps to implement the integration scenario between two healthcare MLLP endpoints through a composite back-end.

Ingredients
  • 2 separated SOA Suite domains with cross domain authentication active
  • 1 inbound Weblogic JMS queue and connection factory
  • 1 outbound Weblogic JMS  queue and connection factory
  • 1 composite with two Healthcare Adapters, one as exposed service and another one as reference
  • 1 SSHI MLLP inbound endpoint
  • 1 SSHI MLLP outbound endpoint
  • 1 "Send to Internal" Internal Delivery Channel
  • 1 "Receive from Internal" Internal Delivery Channel

Read the complete article series here Part 1 and Part 2 and Part 3


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

Saturday May 14, 2016

New Oracle Fusion Middleware 12c (12.2.1.0.0) Released!! by Bruno Neves Alves

The version 12.2.1 is officially and finally out! Check what's new:
Oracle B2B
Moving B2B Agreement from a Test to a Production Environment - Test to production (T2P) process is now simpler with the use of configuration plans to change the endpoints

  • Enabling AS4–Based Message Exchange - Applicability Statement 4 (AS4) standard is now supported!
  • Message Flow Throttling - Oracle B2B can pause, or throttle, the endpoint to publish messages
  • Securing Messages with PGP - Oracle B2B and Healthcare support message level security using PGP

Oracle SSHI (Soa Suite for Healthcare Integration)
Cloning Endpoints - As possible with B2B agreements, its now possible to clone SSHI endpoints

  • Synchronous Request/Reply over MLLP - Request/reply communication between two MLLP endpoints is not facilitated by the introduction of the sync communication feature at the endpoint configuration 
  • Message Flow Throttling - same as B2B
  • Securing Messages with PGP - Same as B2B

Oracle SOA Suite (BPEL, Mediator, Business Rules and Human Workflow)
Support for patching running composite instances - Enabling the patching of running instances of a composite and recover faulted instances after patching

  • Support for In-Memory SOA Using In-Memory SOA - Improve System Performance executing short living processes only in memory

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

Sunday Jun 08, 2014

BPM Workspace and Webforms customization by Bruno Neves Alves

Under the propose of a project customization customization on BPM workspace and designed webforms were applied using custom css and used as skin and as webforms theme. Its important also to highlight that a workspace skin appliance is enough to bring customization to your webforms since they will inherit the workspace skin customization, nevertheless, themes offers you the possibility to enrich that customization or even to overlap it if desired. This blog post shares my experience trying what is available today as sample from Oracle Samples site but also how I found it starting from scratch.
I have follow the following contents to achieve a full workspace and webforms customization: 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

About





Search

Archives
« July 2016
SunMonTueWedThuFriSat
     
26
27
28
29
30
31
      
Today