Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

oracle ebs free web service integration tools

Wird geladen in …3

Hier ansehen

1 von 22 Anzeige

oracle ebs free web service integration tools

Herunterladen, um offline zu lesen

E-Business Suite comes packed with great tools. Learn more about the free web service integration tools included in the Oracle software you already own. Check out our free whitepaper for more information: http://www.smartdogservices.com/whitepapers/free-web-service-integration-tools-included-in-ebs/

E-Business Suite comes packed with great tools. Learn more about the free web service integration tools included in the Oracle software you already own. Check out our free whitepaper for more information: http://www.smartdogservices.com/whitepapers/free-web-service-integration-tools-included-in-ebs/


Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (20)


Ähnlich wie oracle ebs free web service integration tools (20)

Aktuellste (20)


oracle ebs free web service integration tools

  1. 1. 1 Your friend in the business. How to Use The Free Integration Tools That Come with Oracle E- Business Suite
  2. 2. 2 Topics for Today Problem Statement Overview of Integration Options EBS Web Service Integration Web Service Demonstration Questions Agenda Customers that run the E-Business Suite have been challenged trying to get these systems to work seamlessly with internal and external systems. This webinar talks about the integration tools that are available in Oracle EBS that you can use today and in the future.
  3. 3. 3 EBS is Your Primary ERP System You run other systems • Disparate Technologies • Inside and Outside the Firewall • SaaS and In House Business Needs have Changed • Need them to Talk to One Another • Need these systems to work well together as a single system Problem Statement Custom System ? ? ? ? ? ? How do we get them to all work together?
  4. 4. 4 What are my Options? Point-to-Point This is the traditional method of sending integrating two systems through file transfers and the loading of data for a specific purpose. Since many SaaS solutions do not support this method, it is not an option for this discussion. Option 1 – EBS SOA Gateway (SOAP & REST Web Services) EBS SOA gateway provides hosting for “out-of-the-box” Web services from Oracle E- Business Suite. It provides capable integration functionality, but only for a defined set of integration points. Also, there are licensing changes that will be in effect as you move your environment to 12.2. Option 2 – Oracle RESTful Data Services (ORDS) REST is fast becoming the de facto standard for providing data for easy consumption by mobile apps, web apps as well as for in house and cloud based applications. ORDS is a new product from Oracle which allows us to quickly and securely host REST web services Option 3 - Middleware (Full SOA Integration) Full SOA integration through middleware is the most robust and comprehensive solution for developing an integrated application architecture.
  5. 5. 5 Comparison Chart Scenario EBS SOA Gateway ORDS Middleware Solution Limited orchestration required Limited routing or queuing required Web Services primarily REST based Limited orchestration required Limited routing or queuing required Need to host SOAP web services Significant orchestration required Need for off-line queuing and throttling Need for routing of messages Multiple consumers of the data No Cost Option for 12.2.X * SOA Gateway REST is No Cost SOAP is Not No Cost for 12.1.X Yes Yes Yes No Maybe Maybe Maybe Yes No YesNo No Yes Yes No
  6. 6. 6 • Standards Based • REST, SOAP (http, https) • Real-Time Integration • Immediate results • Interoperable • Platform and Language Agnostic • Versatile & Accessible • Easier to consume and access • Promote Re-Use • One service consumed by multiple clients • Mobile, Web Site, Cloud Saas System • New Technology • Google, PayPal, AWS, Twitter • SaaS systems primarily support web services Options 1&2 – Simple SOAP & REST Services
  7. 7. 7 Option 3 – Middleware Solution • Routing • Mediation • Monitoring • Connectivity • Transformation • Business Rules • Service Orchestration
  8. 8. 8 • Can be Overkill • Expensive • Complex to Manage • Specialist Resources Option 3 – Middleware Solution
  9. 9. 9 How can I integrate my systems today (without spending a fortune) and still enable the business to grow in the future? Down The Road
  10. 10. 10 • Gain immediate benefits • Consume data from other systems • Expose your data to SaaS systems, other corporate systems, mobile applications etc. • Start with Simple Web Services • Depending on your Integration requirements, move to full Middleware Integration • Preparation for middleware integration • Services 100% re-usable in middleware solution • Build your service catalog • Ease into middleware integration solution Service Enablement Strategy: Option 1 and/or 2 – depending on your needs
  11. 11. 11 EBS Web Service Integration Options
  12. 12. 12 • No cost option in 12.1.3. • Note: For 12.2+ you need a separate license for SOAP based services. • Oracle Integration Repository • Large repository of existing services exposed by applications within EBS • Produce and consume web services • REST and SOAP • Build in PL/SQL or Java Integrated SOA Gateway
  13. 13. 13 SOA Gateway Scenario EBS to RightNow • SOA Gateway SOAP Service • Create Customer • Get Customer • RightNow calls EBS to create new customer • RightNow calls EBS to get customer details • Build in PL/SQL • Expose as Web-Service • Register in Repository
  14. 14. 14 • No Cost Option • Host REST web services • Consume SOAP & REST • Build in PL/SQL • Authenticate (oauth2) • Authorize via PL/SQL • Json & XML payloads • Certified with R11 & R12 • 5 click Web Service! Oracle REST Data Services
  15. 15. 15 • ImageNow calls Service to create AP invoice in EBS • Service hosted by ORDS ORDS Scenario EBS & ImageNow • ORDS • Exposes URL to Client Applications • Accepts inbound http request • Parses http variables into PL/SQL • Executes PL/SQL block (Web service program logic) • Returns http response back to client (200, 400 etc.)
  16. 16. 16 ORDS Scenario REST Service Anatomy • Module • Collection of related resources • Template / Resource • Object with data, relationships to other resources and methods • Handler/Method • Action to perform on Resource, GET, POST, PUT etc.
  17. 17. 17 ap/invoice Resource (Method: POST) • URI (portion of http URL) ap/invoice • Method (GET, DELETE, PUT, POST) • Source Code Type PL/SQL • MIME Type / Message Format XML • PL/SQL Block / Web Service Program Logic ORDS Scenario
  18. 18. 18 ORDS Scenario Sample REST Web Service Call
  19. 19. 19 /customer Demonstration
  20. 20. 20 Comparison Chart Scenario EBS SOA Gateway ORDS Middleware Solution Limited orchestration required Limited routing or queuing required Web Services primarily REST based Limited orchestration required Limited routing or queuing required Need to host SOAP web services Significant orchestration required Need for off-line queuing and throttling Need for routing of messages Multiple consumers of the data No Cost Option for 12.2.X * SOA Gateway REST is No Cost SOAP is Not No Cost for 12.1.X Yes Yes Yes No Maybe Maybe Maybe Yes No YesNo No Yes Yes No
  21. 21. 21 Things to Remember • Customers that run EBS have powerful integration tools available to them at no additional cost. • These tools can provide a simple and robust integration to SaaS and other external systems. • These tools can be used to quickly build connectors between E-Business Suite to third party or SaaS Solutions. • Once you build these connectors, they can be reused later as your environment changes and you evolve to a fully integrated application architecture. “Let’s Get Started”
  22. 22. 22 Let’s get started.

Hinweis der Redaktion

  • SmartDog Services is the Oracle Customer’s Best Friend. Focused solely on the Oracle community for more than 2 decades, we focus on helping customers get more value out of their software – this presentation is a great example.
  • Welcome
    Welcome to the Webinar. I am exited to talk to you all today about a topic that is relevant, important and fun (well at least I think it is).

    Let’s start by briefly reviewing today’s agenda:
    > We will begin by reviewing a problem statement that I believe is relevant to many if not all of you folks listening today.
    > After that we will review some of the current options that are available to help us solve this problem.
    > Then we will dive a little deeper into some web service integration options that are available to you today, with the software that you already own.
    > Finally, I’ll run a demonstration which will show you how we can achieve real time integration between EBS and another system using REST web services.
    > At the end of the call, with time permitting, we will review any of the chat questions we did not answer during the call. For those questions we don’t get to we will try and answer them via a future blog posting.
    Before I get started I would like to thank Eric Nelson from Oracle for his help in reviewing the content and making sure our message is consistent with Oracle’s current direction.
  • So, let’s start with a problem statement.
    There are very few IT Organizations today, if any, that do not have to deal with systems outside of their core ERP. Increasingly the business is driving the move into SaaS based solutions to stabilize costs and more easily introduce best of breed applications.
    Even though there are powerful reasons to do this, it does not come without a cost to IT. IT has to manage this disparate collection of applications and make them work as a cohesive unit.
    In addition, it is no longer enough to just implement these systems. You must also integrate them with your primary ERP system (the single source of truth).
  • OK, so what are my options in solving this problem.

    Historically, the go to option was a point-to-point interface where we would generate a flat file from system A and then send it across to system B. System B would then consume that data and store that data locally. Since many of today’s SaaS based solutions do not support real time integration using this approach we will not discuss this option today.

    It is the other 3 options that we will cover today, namely, the Integrated SOA Gateway, ORDS and fully fledged Middleware SOA Integration.
  • This chart shows the three options we will discuss today as well as some high level logic that we can use to decide which is the best option for a particular scenario.
    We will revisit this slide in a little while but I wanted to show you up front that it is not necessarily obvious what the best option is.
  • Whether we use the Integrated SOA Gateway or ORDS, we are basically talking about integration using simple SOAP or REST web services.

    I am sure everyone on the call has come across the term Web Service from both a business and consumer perspective.

    Integrating using web services involves exposing your business data as a web service and employing a come and get it approach to data integration. It is true that in many cases you do not need to send that item price to Salesforce and have two copies of it. Instead you can have Salesforce come and get it from EBS in real time.

    In addition, most of today’s cloud based SaaS solutions only allow real time integration via web service calls. If you want to make a real time call to Salesforce for example the only way to do this is via a web service call.

    Web Services are standards based, allow real time integration and are both platform and technology agnostic. They make accessing your data easier and at the same time promote re-use because of that.
  • Probably the option most of you have already looked into is the 10,000 lb gorilla or the full Middleware based integration solution.
    Examples of SOA Integration Solutions include Mule, Jitterbit, CastIron and Oracle SOA Suite.
    These tools provide the most flexibility and features to handle almost any integration requirement.
  • Having said that, we do need to be careful to ensure that we are not blindly led down this path without understanding what it means to our organization.

    > A full middleware solution can definitely be overkill. There are many situations where it is just not the right fit for your requirements or your organization. This is the proverbial sledge hammer and nut scenario.
    > In addition, middleware solutions often come with a hefty price tag and we need to weight up these costs against potential benefits.
    > These solutions are typically more complex. There are many moving parts, both hardware and software that have to be managed, backed up, cloned, upgraded, maintained etc.
    > This introduces my final point which is that the resources needed to setup and manage middleware solutions are generally highly specialized and themselves come with a hefty price tag.
  • OK, so if I web service enable my data now and develop ‘point to point’ web service integrations, what happens in a few years time when my architecture becomes more complicated and I need to move to a full middleware solution?
  • Well, the good news is that by service enabling your data and integrations now you are really paving that road to future middleware solutions (should your organization need to go that route).

    You gain immediate benefits now by allowing other systems to access your EBS data in a easy and secure manner. And as I mentioned previously, in many cases, web services are the only show in town for real time integrations with SaaS systems.

    Start today by building simple web services and move to a full middleware solution in the future if you need to. If you do move to a middleware solution these web services can be used as is without the need for re-work.
  • So, lets drill down a level and look at some specifics about what web service integration options come with E-Business Suite.
  • The obvious choice is the Integrated SOA Gateway. This capability is a built in part of EBS (with some patching) and provides a number of great features.
    It is a no cost option for 12.1.3 but you should note that this is changing in 12.2. In 12.2 you will need a separate license for SOAP based web services although REST services will still be included at no cost.
    SOA Gateway comes with a catalogue of existing services that you can employ as well as a UI for viewing and adding items to the catalogue.
    SOA Gateway allows you to produce and consume SOAP and REST services and allows you to build web services using either PL/SQL or Java.
  • Here we are illustrating an example of an integration between EBS and Oracle’s RightNow service cloud offering.

    In this example we are hosting both a create and get customer, SOAP based service in EBS using the Integrated SOA gateway.

    RIghtNow can call these services to create and lookup EBS customers in real time using a SOAP based web service call.
  • Now, lets move on to an option you may not yet have been exposed to, which is
    Oracle RESTful Data Services or ORDS.
    This product was previously known as the APEX Listener. The Apex Listener was initially created as a middle tier application to serve web pages generated by Oracle’s Application Express Web Development tool. In recent versions Oracle built in functionality for hosting REST based web services and since this change in focus they renamed the product to ORDS.

    ORDS is a no cost option for the Oracle Database. ORDS, used in conjunction with APEX allows you to host REST web services and consume both SOAP and REST based web services.
    When you create a REST service in ORDS, all of the API logic is in PL/SQL so you can leverage your existing PL/SQL skills and code extensively.
    ORDS comes with a complete mechanism for authenticating access using OAUTH2 which is the current industry standard for web service authentication. Once authenticated you can employ PL/SQL logic for authorization (i.e. what data am I allowed to see).
    ORDS is certified for both R11 and R12 of EBS and is the official home of the 5 click web service. Once configured you can literally host a REST web service in just 5 clicks!
  • This slide describes a scenario for a REST service created in ORDS being called by ImageNow in order to create an AP Invoice in EBS.

    In this scenario ImageNow makes a real time call to the REST service URL, passing an XML message with the AP Invoice details. ORDS will accept the request and call the PL/SQL block in the web service definition to perform the web service logic. At this point ORDS will also automatically parse the HTTP header variables into PL/SQL bind variables.

    Code within the PL/SQL block will then call a PL/SQL API which will validate the payload and insert the invoice details into the AP Open Interface table for processing.

    Finally, ORDS will take care of returning the appropriate response and status to ImageNow.
  • Before we get into the demo I wanted to briefly show you the APEX pages that are used to define a REST web service in ORDS.

    ORDS allows you to categorize collections of related services into modules. Within a module, we can have a collection of templates which equate to a resource or object for example customer or invoice. Finally we have a handler which is the action we want to perform on the resource e.g. GET, POST, PUT, DELETE.
  • At the handler level we define what should happen when the service is called with the specified method (get, put, post etc.).

    Here you can see that at the end of the day ORDS is just calling a PL/SQL block which will contain your web service logic.
  • Another advantage of REST services is that you can easily test them using a variety of different testing tools. This screen shot shows you an example of a REST web service call using as free Google Chrome plugin called Postman.
    From this, you can also see the anatomy of a REST based web service call, at the top we have the URL of the service then we have http headers which are being used to pass parameters and the authentication token. Finally we have the payload or the message that will be passed to the web service.

  • Before I start the demonstration I wanted to set the scene so you can better understand what I am going to show you.

    We have an APEX instance running in the Amazon cloud. In this instance, we have created a simple Application in APEX where a user can create and update a customer.

    Internally at SmartDog we have an EBS R12.1.3 instance with ORDS installed. On this instance we have created a customer web service which will allow create, update and select of customer data in EBS.

    When the user creates a customer in the Amazon APEX application the application makes a call to the customer web service on the EBS environment and the customer is created/updated in the EBS instance in real time.

    In the EBS Live area we will see a real time extract of customer data to illustrate how we can deliver data to other environments without those environments needing to store that data locally.
  • Finally, back to the comparison chart.

    We have been through the options in some detail. Now, it’s time for you to decide which is the right option for you!