Mobile Integration Using Oracle Service Bus 12c
November 5, 2014 2 Comments
Mobile Integration Using Oracle Service Bus Oracle Service Bus 12c enables enterprises to deliver on mobile as an extension of the integration platform . Developers can create REST /JSON APIs and simplify the process of creating customizable applications from reusable components. Oracle Service Bus 12c makes it easy to extend onpremise and cloud applications to the mobile channel. Read the datasheet here.
Oracle Service Bus 12c enables enterprises to deliver on mobile as an extension of the integration platform. Developers can create REST/JSON APIs and simplify the process of creating customizable applications from reusable components. Oracle Service Bus 12c makes it easy to extend on-premise and cloud applications to the mobile channel.
The Oracle Mobile Suite utilizes standard technologies and tools to expose many data formats for exchange data and functions with any mobile application and includes Oracle Service Bus and Oracle Mobile Application Framework. Oracle Service Bus supports all types of connections between applications on mobile devices and back end business systems including the popular REST/JSON.
Using Service Bus, organizations can shield front-end mobile applications from changes that might occur in the backend. They can also shield mobile developers from often intricate and complex details of underlying implementations of back-end applications, such as legacy protocols. In addition, Service Bus can simplify and reduce the information exposed by API interfaces to ensure both optimization of bandwidth and greater control on information shared with mobile users.
Oracle Service Bus is a part of Oracle SOA Suite 12c. It introduces a REST binding within JDeveloper to simplify mobile enablement by exposing traditional SOAP services, Enterprise Java Beans (EJBs), JCA adapters connecting backend applications or just about any other underlying implementation through REST/JSON. The REST binding is available for SOA composites and Oracle Service Bus services and allows the configuration of REST interactions as exposed service or proxy service. It also allows the invocation of externally available REST services.
To learn more on Oracle Service Bus 12c for Mobile Integration:
Datasheet for Mobile Integration using Oracle Service Bus 12c
Screencast on Mobile Enablement with SOA by Suhash Uliyar, VP of Mobile Strategy at Oracle
Customer Stories:
Agilent Delivers on Mobile Strategy with Oracle SOA
Ricoh Differentiates Business with Mobile Enablement
Blog Series on Simplifying Mobile Integration with SOA:
1. Simplifying Enterprise Mobile Integration
2. Mobile Service Enablement with Oracle Service Bus
3. API Management as a Solution to Mobile Enablement
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
Facebook
Wiki
The Service Bus seems to be a turn-key type solution. As I think about this and read the additional Data Sheet material the question that comes to mind is “What is the Cost?” or maybe the better question, “Where is the Cost?”.
The Service bus has popped up in a few contexts during the last number of years – Maybe it is time to “Get on the Bus” 🙂
Hi Miller
yes a Service Bus is a first important step for a SOA based Architecture, to achieve data mediation. There are many tools to calculate ROI in the internet – see also https://blogs.oracle.com/SOA/entry/justifying_the_roi_of_soa.
Would like to suggest to look into your use case and find similar industry specific references. Your Oracle account manager can support you with this information or visit http://www.oracle.com/soa
Best regards Jürgen Kress