Robert van Molken
(4 comments, 5 posts)
Robert is a experienced Fusion Middleware / SOA developer for nearly 5 years. He focuses in particular on building service-oriented business processes. He is mostly very good in IT technologies like Java / JEE, Oracle and SOA. Where his specialty is with BPEL, SCA, SOAP, XPath, XML, Java, JAX-WS, Advanced Queueing, and PL / SQL.
Posts by Robert van Molken
By: Robert van Mölken and Tim Askamp
An end-to-end application usually consists of multiple components that are one-way or another decoupled. A component can be an ADF frontend, OSB proxy, SOA Suite Composite, Database package or JAXWS web service. For maintaining all the components of an end-to-end application the components need to be checked individually to know if everything is in working order. So if there is for example a performance issue with the application there is no simple task to checked which component in the chain is responsible for this.
For one of our clients we’ve developed a ‘Probe’ application. The reason was that maintenance needed a simple way to determine if the SOA and Database environment: was running, configured as required and the basics where functioning. So basically we needed to mimic service operations that use the following components: OSB, SOA Suite, JAX-WS and ADF Business Components. Executing this functionality should lead to a traceable path of the used components. In this blog we will explain the solution we developed.
When running a Weblogic server and its managed servers I have heard at multiple projects that there is a need of automatic startup of these server processes. There is not default an options to create a windows service when installing Weblogic and for example SOA Suite. The one option that is available is to create a windows service for the node manager.
This small guide will show how to create a windows service for the Weblogic AdminServer, the node manager and the Managed server and setting up the evironment settings. For creating the Windows services a tool called NSSM (the Non-Sucking Service Manager) is used.
This week Oracle released it sixth patchset (22.214.171.124) of the SOA Suite and it’s IDE JDeveloper. In this new release there are some small changes in the IDE, but there are also some mayor changes like two new adapters; healthcare and the UMS (User Messaging Service). This blog will look into the use of the UMS adapter as a inbound and outbound service in a SOA Composite. This adapter was already available as beta in PS5 but now it is an official adapter.
By using the UMS (User Messaging Service) adapter as an inbound service you can initiate a instance of a SOA composite by receiving a email message on one or more configured recipients. By using the UMS adapter as an outbound service you can send email messages to one or more recipients with an optional option to send data message as an attachment. (more…)
It has been almost a year since my last post about the metadata services. I talked about how-to set up a File-based MDS and DB-based MDS. This post talks about the usage of the files, placed in the MDS, in the different components available in a SOA composite. If the MDS is a new thing for you then I advise to read my previous about this subject first.
You can spot the presence of a file that is a reference to the MDS if it uses the oramds: URI annotation. Files are no longer referenced to a hardcoded or relative file path.
To start using you’re MDS that you have set up we will create a new SOA application. Let call the application WorkflowSOAapp and create a SOA project and call it WebformService.
Before I talk about the advantages en methods of using the MDS, I want to introduce myself, because this is my first public post on the AMIS technology blog. My name is Robert van Mölken and I’m 26 years old. I’m now actively working, as a SOA Consultant / Developer, for nearly 5 years. My main toolstack is SOA Suite (3,5 years 10gR3 and 1,5 years 11gR1), but also have experience with opensource BPEL / ESB alternatives from Apache.
In many big SOA application all the composites use the same canonical1 data model (message definitions) for their service contracts. Many entities and elements (complex- and simple types) are reused. Therefor it is not a good choice to use a local copy for the service contracts (WSDLs) and message definition files (XSDs) in each SOA composite project.
If you do so and a mayor (common) part of the message definitions changes then you need to update all the SOA composite projects, where these files are used, with the new version of the files. Oracle created the MDS to solve this issue. MDS stands for MetaData Services. The MDS holds all kind of xml-based files, like WSDLs, XSDs, Domain Values Maps but can also hold fault policies and event definitions More >