With the release of Oracle Enterprise Repository 12c another product was released. Oracle API Catalog 12c (OAC) allows you to build a catalog of your organization APIs. OAC provides a layer of visibility to those APIs so application development knows what and which one to use. OAC includes a simple metamodel for an API asset, automation to populate OAC, and the ability for users to search OAC for APIs and understand the details of the APIs to assess their fit in the user’s application.
I’m not going to bore you with the details about the installation by giving a installation guide. It took me about 40 minutes from scratch (excluding downlOERoad time). The steps are describes in the installation guide Oracle provides. OAC is part of the OER 12c installation jar, but can be licensed and installed, as an own managed domain, without licensing and installing OER.
The Order To Cash Process Integration Pack (O2C PIP)is a packaged solution on top of the Application Integration Architecture (AIA). AIA is n Oracle SOA solution, designed to deliver building Blocks for Integrations (AIA Foundation Pack) or pre integrated Integration Solutions, the Process Integration packs .
The O2C PIP is an important Integration Flow because it is the enabler of Oracle’s Telecommunications Business Support System (BSS) Order Management Solution, called Rapid Offer Design & Order Delivery (RODOD).
In the following we will give a high level Introduction to RODOD , a short introduction to the Application Integration Architecture and a detailed description of the Order To Cash Process Integration Pack
Oracle BPM provides us with various components to control the flow of a process such as gateways, timer events, errors, message events, send and receive tasks, loop markers and multi-instance markers. In this article I will be elaborating the gateway control flow components and how we can use them to define the flow of our process. Gateways are very similar to a flowchart decision element. Using a gateway you can define the control points within your process by splitting and merging paths. At runtime a gateway will determine based on the control points defined at design time the path that a token will take through a process. There are five gateway types; Exclusive Gateway (XOR), Inclusive Gateway (OR), Parallel Gateway, Event Based Gateway and Complex Gateway
With the help of my A-Team colleagues (Sushil Shukla, Siming Mu, John Featherly, Pete Farkas), and based on collective experiences visiting numerous BPM customers worldwide, I have put together my “Top 10″ list of things everyone should know when embarking on a BPM project.
You might agree, you might disagree, most of all, feel free to comment.
Cloud service broker definition
Cloud service broker role & services
Cloud service broker market opportunity
Challenges cloud service broker
Examining the cloud broker market opportunity & role of IP
Cloud broker IaaS
In the SOA Magazine III “Cloud Computing Definition & Architecture for Cloud Service Brokers” we introduced the cloud computing definition, concepts and the idea of Cloud Service Broker. In this article we discuss the Cloud Service Brokers in details including their roles, services, market opportunity and challenges.
Cloud service broker definition
The paper “Defining Cloud Services Brokerage: Taking Intermediation to the Next Level” written by Daryl C. Plummer, Benoit J. Lheureux, Frances Karamouzis and published by Gartner in October 2010, defines cloud services brokerage (CSB) as "A cloud services brokerage is a business model in which a company or other entity adds value to one or more (generally public or hybrid, but possibly private) cloud services on behalf of one or more consumers of those services." The authors do not define cloud brokers in categories like the NIST definition in 2011 (Service Intermediation & Service Aggregation & Service Arbitration). Instead the paper highlights the types of CSBs by backup & recovery, integration, customer development, governance or service marketplace. In recent papers Gartner follows the NIST cloud broker categories.
Oracle released SOA Suite 12c (12.1.3) bringing a further integration between components and a bunch of new features. Most of them are quite spectacular, but at the same time all are useful. A release to persuade potential buyers and a lot more to please users of the product.
This blog will go through the most important new features in summary and will reference the blogs that will go through the new features per technology. This blog will list the most game changing feature(s) per technology/tooling; Jdeveloper, SOA Suite (SCA Composites), Service Bus (SB), Enterprise Manager, OEP, Managed File Transfer (MFT), etc.
Disclamer: Screenshots are made in Beta version of SOA Suite 12c, so may differ in final version!
Developer Productivity & Integration
Developer installer with integrated server
To kick-start developing with 12c, ’30 minutes to Hello World’, Oracle created a single download for JDeveloper and Database, Weblogic and SOA Suite. It’s one single package which include JDeveloper, a integrated Weblogic service with SOA Suite (including Service Bus), JavaDB (for it’s Database) and the Enterprise Manager.
A frequently discussed topic these days is the Micorservices architectural paradigm. Discussions on various internet blogs and forums are showing the trend that proponents of this approach are not tired of emphasizing why Microservices are different to a holistic SOA approach, when dealing with breaking up or avoiding monolithic software architectures.
For this reason it’s time for the Cattle Crew team, to take a closer look on this arising architectural style and the corresponding discussions from a different perspective.
Amongst others Martin Fowler published a blog about what is characteristic for Microservices and applications build on the foundation of this architectural style . According to this and other blog posts (see also , ), the goal of a Microservices approach is to avoid software systems to become monolithic, inflexible and hardly manageable, by splitting a system into modular, lightweight and maximum cohesive services. Applications build on this architecture should ensure the agility regarding changes caused by changed business requirements, because affected services of an application can simply be adapted and be redeployed independently from other components.
Effectively a Microservice is a in itself cohesive, atomic application, which fulfills a dedicated purpose. Therefore it encapsulates all needed elements, e.g. UIs, logic components, may also have its own separated persistent store and may run in a separate JVM, to ensure as less impairment to other services as possible. Furthermore the implementation technologies for a specific service may vary. For each service the best-fitting technology should be used; there should be no restrictions regarding the used technologies.
Much has been said about Oracle SOA Suite 10g (or JCaps) upgrades to 11g and how features map between both versions. There is also plenty of information online about this topic both official and unofficial. It’s not news to many that for example SOA Suite 10g is currently in extended support and product will enter sustaining support by the end of 2014 (I will explain more about what extended and sustaining support means later in the blog). However one fact remains truth: There are still many companies out there running platforms that are (or soon will be) in sustaining support, and that don’t yet have an upgrade strategy. I say this based on my own experience as I am currently helping several customers do exactly this.
Having said that, I wrote this blog in an attempt to give SOA experts, Integration Leads and Architects key pointers that can serve as inspiration to come up with a transformational approach when defining an upgrade strategy. Note that I am using the word “transformation” deliberately and I will explain why shortly.
Note that although this article is mainly related to the Oracle SOA 10g to 11g technology stacks, the approaches, tips and information provided in this blog should also be applicable when defining any technology upgrade. In fact, once 12c is more mature I will probably refresh this blog to cover 11g to 12c upgrades.
Following my key pointers to help you define your upgrade as a SOA Transformation:
1) Understand the product roadmaps and planning to move in advance
This is one of the most important points and one that many have either failed to understand or have just ignored (hence why many companies still stuck in 10g and have no plan to upgrade yet). This is important because by understanding the product releases and features, release dates, and support lifeline you can plan in advance an upgrade approach and avoid having to do something tactically, in a rush and with limited budget.
Companies delivering services to customers are all faced with the same high-level challenges.
- How can we improve our services towards the customers;
- How can we challenge the cost aspects;
- How to deal with the new regulations imposed by the regulator;
These challenges impact the way the end-to-end delivery of the services to the customers is executed. There are a lot of informal end-to-end processes in organizations supporting the customer service services. These end-to-end processes are usually supported by scattered applications, email, spreadsheets and a lot of goodwill of the personnel involved. When compliance, regulations and/or customer demands are imposed on an organization, these end-to-end processes do not have the ability to comply with new demands due to lack of support from the current application landscape.
In the financial, public and utilities market organizations are re-landscaping their existing application portfolio due to these higher compliance, regulations and customer demands. This re-landscaping is usually not an overnight exercise and can span multiple years. Case management can help to cross the bridge from the current landscape towards a landscape aimed at delivering these higher demands.
Let’s explain this with the process of complaints. This functionality is needed in any market where customer contact is present, and where due to increasing compliance and customer demands the bar needs to be raised to deliver better quality, such as delivering an answer within a given timeframe. The process starts when a customer, who is not satisfied, sends a complaint to the company.