Posts tagged soa
Wil je als ontwikkelaar met Oracle Service Bus (OSB), onderdeel van de Oracle SOA Stack, aan de slag op een project; als beheerder OSB willen beheren en monitoren; of als architect meer begrijpen van de positionering van het OSB, dan is deze hands-on training iets voor jou. Je leert de sterke punten, maar ook de beperkingen van OSB kennen. De juiste balans tussen theorie en praktijk, minimaal de helft van de tijd wordt besteed aan het maken van opgaven, leidt je op tot een niveau waarmee je kunt instromen op een OSB-ontwikkeltraject.
De training bevat een breed spectrum van onderwerpen, de meeste aandacht gaat uit naar de waar je als OSB-ontwikkelaar direct mee aan de slag gaat op een project.
Mocht je vooraf interesse hebben in de tweedaagse XML training, laat dit dan weten via email@example.com
Voor meer informatie en inschrijving van de OSB training, klik hier.
Oracle OpenWorld is a monster event – 10Ks of attendees, thousands of sessions and 100Ks of private conversations that all help convey and define the message about Oracle’s strategy and the roadmap for its close to 4000 thousand products. Concurrent with OOW is the JavaOne conference that – at a slightly smaller scale – does the same thing for the world of the Java platform, the JVM and the Java community.
AMIS each year sends a substantial delegation to attend and contribute to the conference. We speak in many sessions, ask questions in even more and do our utmost to gather information, digest it and distill the real meaning and relevant details. We have just completed our yearly review of the Oracle OpenWorld and JavaOne 2013 conferences: a 60-page PDF document that answers the ultimate question about life, the universe and everything [Oracle].
This white paper describes the major transitions that the industry at large and Oracle in specific is going through. It explains what these transitions mean to Oracle, cause in terms of product evolution and will result in for the users. The major product announcements are listed and commented on. The roadmaps for the most relevant More >
(this article is a live blog: it is a work in progress – as I am currently reading this book – and this article will be updated in the next few days and weeks; when completed, the marker Live Blog will be removed)
- Title: Oracle SOA Governance 11g Implementation
- By: Luis Augusto Weir, Andrew Bell
- Publisher: Packt
- Released: September 2013
- Pages: 440
- ISBN : 1849689083
- ISBN 13 : 9781849689083
The title of this book is clear: the term SOA Governance is fairly well known. Oracle SOA Governance 11g is a product suite from Oracle, released in February 2010:
“Oracle SOA Governance 11g consisting of Oracle Enterprise Repository, Oracle Service Registry, SOA Management with Oracle Enterprise Manager, and Oracle Web Services Manager. Oracle SOA Governance 11g, a component of Oracle Fusion Middleware, enables organizations to manage their heterogeneous software project artifacts under a unified governance umbrella. Fully integrated with Oracle SOA Suite 11g, the new release [of SOA Governance 11g] helps organizations simplify governance of software development projects. Oracle SOA Governance 11g is fully integrated with Oracle AmberPoint, a leader in Service-Oriented Architecture (SOA) More >
The story of NOPERU – the National Organization for Permits for Emissions and Resource Usage – is an interesting one. Because it reveals the business drivers for embarking on a journey of modernization, enterprise architecture and application of SOA principles using Oracle Fusion Middleware. It also outlines a roadmap: which steps were taken to move NOPERU from classic, silo-oriented, distributed (in isolation) and largely paper-based to a modern enterprise – both IT-wise and Business-wise. With 24/7 B2B and B2C interaction, centralized administration, automated processes and almost paperless operations.
The story describes the architecture design and ensuing technology selection as well as the implementation steps. It explains why and how an agile approach was selected for executing software development and maintenance. It also makes clear when and how Oracle technology components such as WebCenter Content, Service Bus, SOA Suite, ADF, Database, WebLogic and BPM Suite were used.
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.
It was fairly difficult to come up with a title for this article that sort of covers the content. To me it is quite clear what this is about – but how to convey that in a title? Let me explain: today in our project we discussed the implementation of a data service. The service operation under scrutiny takes a city as input and returns a list all open orders from customers located in that city. Nothing very special there. The interesting complication lies in the fact that the customers are part of a different domain than the orders. This means – under our architecture guidelines – that we cannot create a single SQL query that joins together the customers table with the orders table. A database link to join the tables across databases is out of the question and even if these tables currently reside in the same database – such a join is not allowed. Different data domains are treated as independent entities and no direct dependencies between the two should be created. Every design has pass the check ‘will it still work if one of the domains involved were to be relocated to the cloud or be replaced by a third party application’.
The architecture is service oriented. Every domain More >