On this subject, there are already many fine articles. I have borrowed from at least a dozen to understand what should happen and to make it work. You will find them listed under resources. I have collected wisdom from most of these and created a new description, that works for me and for SOA Suite 12c and will have you sending emails from the SOA Suite 12c through your GMail account in no time at all.
I was completely stuck with Service Bus 12c project deployment from JDeveloper to the Service Bus run time. Every deployment met with the same fate: Conflicts found during publish – OSB-398016, Error loading the WSDL from the repository: The WSDL is not semantically valid: Failed to read wsdl file from url due to — java.net.MalformedURLException: Unknown protocol: servicebus.
I was completely lost and frustrated – not even a simple hello_world could make it to the server.
Then, Google and Daniel Dias from Link Consulting to the rescue: http://middlewarebylink.wordpress.com/2014/07/17/soa-12c-end-to-end-e2e-tutorial-error-deploying-validatepayment/. He had run into the same problem – and he had a fix for it! Extremely hard to find if you ask me, but fairly easy to apply.
In recent previous articles I have discussed the use of Vagrant and Puppet for the automated creation of Virtual Machines, for example with various Oracle software components completely installed into them. In this article, I am merely the consumer of goodies. Edwin Biemond published on GitHub the complete set of Vagrant and Puppet configuration files for creating VMs with the SOA Infra database (Oracle Database 126.96.36.199, populated with the RCU installer) and the SOA Suite 12.1.3 run time environment – including Service Bus, see: WebLogic 12.1.3 infra (JRF) with SOA,OSB.
In this article, I will describe the steps I took to actually produce the two VMs using Edwin’s scripts. The visual description of the whole process looks something like the next figure:
In SOA Suite 12c, the Service Bus specific run time browser interface is not intended for administration activities: all administration around SOA Suite 12c is consolidated into Enterprise Manager Fusion Middleware Control. So a valid question now becomes: how to locate pipeline alerts produced in 12c Service Bus run time environments? These are of course to be found in EM FMW Control. But where and how exactly?
Let’s start with a very simple 12c Service Bus project. This project – was first introduced in an earlier article.
The pipeline receives a fairly simple request message, performs an XQuery transformation on the contents of the $body and returns the result.
Configuring Pipeline Alerts
Create a new Alert Destination – to later on send the alerts to:
Set the name for Alert Destination then press Finish:
Configure the Alert Destination – ensure that Alert Logging is on (this means that alerts are save to the operational Service Bus infrastructure data store):
Open the Pipeline editor. Add an Alert activity to the Request pipeline:
Configure the Alert activity as shown here:
Most important is the link to the Alert Destination.
The next step is to run the pipeline or the proxy service. In both instances, the service is deployed to the Service Bus run time engine in the Integrated WLS.
Pipeline Alerts at Run-time
In the Enterprise Manager FMW Control, the Pipelines Alerts can be inspected in the home page for the Service Bus node (that takes the place of the Operations tab in the 11g Service Bus Console). The first tab provides an overview of various types of (recent and aggregate) information.
The second tab provides details on recent as well as not so recent Alerts. On this tab can selected alerts also be purged.
When you click on the alert summary link, a pop up appears with the alert details:
On the home page for the Service Bus Project can we check the services in the project.
We can switch to the Operations tab get a more detailed overview per operation of what operational settings have been made. On this page, the pipeline needs to have Pipeline Alerts enabled in order for pipeline alerts to be produced from it:
By clicking on an operation (service, pipeline, split join), we can drill down to the next detail page where largely the same information is presented and can be manipulated.
If we enable monitoring, the Service Bus will start to collect aggregate information about the number of messages, errors, alerts etc. This information can be reviewed on the Dashboard tab for the Pipeline:
Clearly we have made some additional test calls to the service – already six alerts have been counted!
The MDS repository is an important mechanism for SOA Suite 12c, both at design time during development as well as at run time. At design time, MDS is used to host shared resources such as WSDL and XSD documents that are referenced in many different places. Instead of copying these resources between applications and projects, or creating central shared folders that are managed manually and at file system level, MDS is concept that is native to JDeveloper and therefore much easier to use with these shared resources.
In SOA Suite 12c, a design time, file based MDS repository is part of the development environment – out of the box. You can create your own file based MDS repositories in addition to this out-of-the-box instance.
When you open the Resource window, under IDE Connections | SOA-MDS, you will find the connection to this local, file based repository – that is initially empty.
Resources can be added to the MDS, for example by transferring them from SOA composite or Service Bus projects. Resources can also be transferred from the MDS to Service Bus projects. I am not sure yet how to transfer resources from MDS to a SOA composite application.
However, as stated before, this out of the box file based design time MDS repository is local. Resources added to it, are not shared with MDS repositories in some other location. SOA composites that contain references that start with oramds: cannot be shared unless the sharing partners all have the referenced resources in their local MDS repositories. That’s why it is very convenient to be able to export selected resources from a design time file based MDS environment – to a jar-file – and import resources from this jar-file to MDS repositories in other environments. I just used this mechanism to bring resources across from one VM to another.
Presentation from the Oracle and AMIS co-organized ADF Enterprise Mobility Conference (21-23 May 2014). Web Oriented Architecture (WOA) and Mobile Oriented Architecture (MOA) are terms coined for the architecture backing modern HTML 5 web applications (rich client/thin server) as well as mobile applications. A pivotal part of WOA and MOA is a layer of services that exposes relevant aspects – both data and functions – of enterprise systems, in a standardized fashion that can easily be consumed. RESTful services using JSON for message payloads are commonly preferred for this. The next generation of the SOA Suite has cloud integration, JSON processing and REST-services as one of its core themes. In this session, we will discuss how a MOA & WOA is designed and how the Oracle SOA Suite & Service Bus – both the current 11g and the upcoming 12c release – can be used to create the services layer.