FMW SOA Monitoring Module is released. (Supports 11g and 12c)

image

WLSDM SOA Monitoring, Diagnostics & Report Modules

  • SOA Smart Dashboards
    • Monitoring BPEL Engine (Only 11g)
    • BPEL Engine Dashboard (Historical – Only 11g)
    • Monitoring Composite Performance
    • Monitoring Callback and Invoke
    • Monitoring Composite Faults
    • Monitoring Deployed Composites Trend
    • Summarizing Composite List & Endpoint URIs
  • SOA Notifications and Alarms
    • BPEL Engine Notifications
    • Composite Performance Notifications
    • Callback and Invoke (DLV_MESSAGE) Notifications
    • Composite Faults and Errors Notifications
  • SOA Reports
    • Reporting SOA BPEL Engine
    • Reporting SOA Composite Performance
    • Reporting SOA Callback and Invoke (DLV_MESSAGE)
    • Reporting SOA Composite Faults and Errors

Get WLSDM 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

API Management Implementation Case Study by Bob Rhubart

 

imageRead this complete sample chapter from the book Oracle API Management 12c Implementation, written by Oracle ACE Director Luis Weir, Oracle ACE Rolando Carraso, Oracle ACE Associate Arturo Viveros, and Andrew Bell. OAPI_Mgmt_Implement_Case_Study.pdf (1.3 MB)

 

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

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

Monitoring Performance Issues with Integrated Workload Statistics – free online training

clip_image001

For 2nd review of the Monitoring Performance Issues with Integrated Workload Statistics of Oracle SOA Suite 12c Release 12.2.1. Watch the video 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

SOA Suite 12c monitoring with EM 12c Cloud Control by Michel Schildmeijer

 

clip_image002Good monitoring is knowing how your systems and application are doing at past, present and future time. There are many  monitoring tools & solutions at the market, all with pro’s and cons. Building monitoring takes time and effort but in the end gives you the benefit of less disturbance and more guarantee of business continuity.

At the customers I work for, I often implemented Oracle’s Enterprise manager 12c Cloud Control to build a monitoring framework. In this blog I will tell about what needs to be done to build such a framework.

Pre Requirements

Before start building a solution, make sure you have:

  • The proper monitoring pack licenses; for SOA Suite that will be:
    • The WebLogic Diagnostics & Monitoring Pack
    • The SOA Suite Diagnostics & Montitoring Pack
  • Agents installed on every physical (or virtual ) host where WebLogic / SOA is running

Building Steps

Deploying Agents to Targets

If not already done so, agents need to be deployed to the hostst were middleware is running. I will not discuss this any further because this is more Enterprise Manager generic.

Discover Middleware Targets

Discovering Middleware Targets is just as it is as with other Targets. 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

Monitoring large flow traces with Oracle SOA Suite by Martin Günther

End-to-end monitoring of BPEL process instances acro ss composite borders is a great feature of Oracle SOA/Business Process Management Suite 11g. It is shown in nearly every PreSales presentation and when you were used to know SOA Suite 10g or to work with other kinds of distributed, heterogenous systems it is a real improvement.

But when you implement large process chains you might realize that the newly won process transparency can raise new challenges. Imagine you have a root process which creates several instances of sub-processes. In such a case without doing any extra work you will get one flow trace for the process and all of its sub-process instances. For large process chains you need to consider the following facts:

  • Transparency: Although it shows an end-to-end view of the whole execution tree, trying to find a faulted sub-process might be a real challenge. It doesn’t matter if you start the search from the root process instance or from one of the sub-processes – the flow trace always displays all components of the execution context. When you click on a sub-process and you go back to the flow trace you might have to expand all child nodes again and again.
  • DataSetTooLargeException:  When your flow trace becomes longer and longer, you will observe, that there is a maximum size for the audit trail that can be displayed by Enterprise Manager. Usually it results in a java.lang.RuntimeException: oracle.soa.management.facade.DataSetTooLargeException: Requested audit trail size is larger than threshold … chars
    For large execution trees, sub-process instances might not be displayed or you might not be able to see things in detail.
  • Low Memory: It is not only the visible representation of your instance, which struggles. A huge audit trail implicitly means that your needed memory allocation for executing your process instance grows. It can grow to this extent that your process instance crashes because of running low 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 Mix Forum