Comparison between ODI and Enterprise Service Bus (ESB)

Hi,
As per my knowledge Oracle has provided two infrastructures, namely ODI and ESB for migrating data across applications.
My query is where I should use ESB and where ODI. Is there any comparison document available? I heard that for bulk data movement ODI is suggested by Oracle. Is there any benchmark exists for comparing these two tools?
I also want to map these tools with Oracle E-Business suite's conversion process. Is it possible to map each stage of a traditional Conversion Process (Data Loading, Validating, Importing to Oracle EBusiness Suite) using these tools?
Any kind of help/idea will be very much appreciated.
Regards.
Tapas

I also think that same way. I do not know what is so apecial about BEA Aqualogic ESB and other market matured ESB products such as TIBCO & SONIC. The samples which BEA has given in their evaluation guide are very simplistic. BEA should do more to provide extensive knowledge/features about their Aqualogic line of products.

Similar Messages

  • WLI as an Enterprise Service Bus (ESB)?

    Hi!
    BEA has previously sold WLI 8.1 as an ESB. See e.g. http://dev2dev.bea.com/pub/a/2004/12/soa_ibarra.html
    Now that AquaLogic Service Bus has beed launched, it seems that the two products have much in common and some overlapping functionalities. E.g. both products have support for messaging and transformations.
    For me it seems that the role of the two is not clearly defined.
    What is new with AquaLogic Service Bus? What is the big difference? Why not just use WLI as previously described in the article by Ibarro?
    Any thoughts? All input appreciated.

    I also think that same way. I do not know what is so apecial about BEA Aqualogic ESB and other market matured ESB products such as TIBCO & SONIC. The samples which BEA has given in their evaluation guide are very simplistic. BEA should do more to provide extensive knowledge/features about their Aqualogic line of products.

  • Difference between Webservice and Enterprise Service

    Hi all,
    In SAP, web service is known as Enterprise Service. What makes Enterprise Service different from a normal web service?

    Hi,
    Enterprise Service is a web service with business semantics.
    The tecnology is same i.e HTTP,SOAP,WSDL.
    But there are some governance rule for defining an Enterprise Service and it can be defined only in ESR(using business objects, process components etc).
    There are no such governance rule for defining a web service. You can simply write a mehtod/functional module to add two nos and expose it as a web service . But would not be called as Enterprise Service.
    Hope this helps.
    Regards,
    Piyush

  • What is SAP ESB (Enterprise Service Bus)?

    Hi fellow sdners gurus…  I have been reading threads about SAP SOA and ESB. 
    I do not want to start a debate on wether XI is an ESB, but more of a statement to what is SAP ESB (if XI it is, then be it).
    1) What is SAP ESB (Enterprise Service Bus) today (I could not find a clear answer to is)? 
    2) Who uses this SAP ESB in production currently and what kind of environment (i.e. strictly SAP backend systems, or combination of various vendors’ backend systems)?
    Can someone share some light on this topic?
    As a reminder, an ESB is expected to exhibit the following characteristics (source Wikipedia):
    •     It is usually operating-system and programming-language agnostic; for example, it should enable interoperability between Java and .NET applications.
    •     It uses XML (eXtensible Markup Language) as the standard communication language.
    •     It supports web-services standards.
    •     It supports various MEPs (Message Exchange Patterns) (e.g., synchronous request/response, asynchronous request/response, send-and-forget, publish/subscribe).
    •     It includes adapters for supporting integration with legacy systems, possibly based on standards such as JCA
    •     It includes a standardized security model to authorize, authenticate and audit use of the ESB.
    •     To facilitate the transformation of data formats and values, it includes transformation services (often via XSLT or XQuery) between the format of the sending application and the receiving application.
    •     It includes validation against schemas for sending and receiving messages.
    •     It can uniformly apply business rules, enriching messages from other sources, the splitting and combining of multiple messages and the handling of exceptions.
    •     It can provide a unified abstraction across multiple layers
    •     It can route or transform messages conditionally, based on a non-centralized policy (i.e. no central rules-engine needs to be present).
    •     It is monitored for various SLA (Service Level Agreement) threshold message latencies and other SLA characteristics.
    •     It (often) facilitates "service classes," responding appropriately to higher and lower priority users.
    •     It supports queuing, holding messages if applications are temporarily unavailable.
    Your help is greatly appreciated.
    Kind Regards,
    Jean-Michel

    PI or XI is the ESB from SAP side. PI is not a full pledged ESB on a reference model of ESB idea but it is the the framework SAP provide as a ESB product.
    A Standard Based ESB Reference Model should fullfil the following features in a framework.
    ESB Features    Service Enablement Phase (1, 2, 3)
    1)     Message brokering between heterogeneous environments                     
    2)     Supports asynchronous, synchronous, publish and subscribe messaging                    
    3)     Supports synchronous and asynchronous bridging                    
    4)     Supports message formats of SOAP                    
    5)     Support for message format of SOAP with attachments                    
    6)     Support for xml message                     
    7)     Support for structured non-XML data                    
    8)     Support for raw data message                    
    9)     Support for text data message                    
    10)     Sport for e-mail with attachment message                    
    11)     Heterogeneous transports between service end points                    
    12)     Supports for FILE protocols                    
    13)     Supports for FTP protocols                     
    14)     Supports for HTTP protocols                    
    15)     Supports for HTTPS protocols                    
    16)     Supports for Multiple JMS providers                    
    17)     Supports for RMI protocols                    
    18)     Supports for web service protocols                    
    19)     Supports for CORBA protocols                    
    20)     Supports for DCOM protocols                    
    21)     Supports for E-mail (POP, SMTP, IMAP) protocols                    
    22)     Support for advanced transformation engine                    
    23)     Support for configuration-driven routing                    
    24)     Message routing based policies                    
    25)     Support for call-outs to external services to support complex routing                    
    26)     Support for point-to-point routing                    
    27)     Support for one-to-many routing scenarios                     
    28)     Support for request response model                    
    29)     Support for publish-subscribe models                    
    30)     Service monitoring                    
    31)     Service logging                    
    32)     Service auditing with search capabilities.                    
    33)     Support for capture of key statistics for message and transport attributes including message invocations, errors, and performance, volume, and SLA violations.                     
    34)     Supports clusters and gathers statistics across the cluster to review SLA violations                    
    35)     Support for service provisioning                     
    36)     Support deployment of new versions of services dynamically through configuration                    
    37)     Migrates configured services and resources between design, staging and production                    
    38)     Supports multiple versions of message resources that are incrementally deployed with selective service access through flexible routing                    
    39)     Configurable policy-driven security                    
    40)     Supports the latest security standards for authentication, encryption-decryption, and digital signatures                    
    41)     Supports SSL for HTTP and JMS transports                    
    42)     Supports multiple authentication models                    
    43)     Policy-driven SLA enforcement                    
    44)     Establishes SLAs on a variety of attributes including                     
    a.     Throughput times                    
    b.     Processing volumes                    
    c.     Success/failure ratios of message processes                    
    d.     Number of errors                    
    e.     Security violations                    
    f.     Schema validation issues                     
    45)     Initiates automated alerts or enables operator-initiated responses to rule violations using flexible mechanisms including                     
    a.     E-mail notifications                    
    b.     Triggered JMS messages                    
    c.     Triggered integration processes with a JMS message                    
    d.     Web services invocations with a JMS message                    
    e.     Administration console alerts.                     
    46)     Support for having multiple LOBs manage their own service bus based on their policies, and a service bus at an enterprise level that could act as a broker for sharing services across the various business units.                    
    47)     Support for agent plug-in to support following features                    
    48)     External provider’s service access for security                    
    49)     External provider’s service management                     
    50)     External provider’s transaction container                    
    a.     External provider’s business orchestration (BPEL Engine) and business work flow service container                    
    51)     Transaction support on message level                    
    52)     IDE Integration                    
    53)     Open standards

  • Enterprise Service Bus and ESA

    Hi ,
    I like to know, how to realize Enterprise Service Bus in the  Enterpise Servise Architecture?
    Thanks in advance.
    Regards
    Lemin.

    hi there,
    for an introduction have a look <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d86cf1a4-0701-0010-409d-c568b1d2519e">here</a>.
    For more in-depth information search <a href="http://help.sap.com">SAP Help</a> for XI & BPEL, e.g.  <a href="http://help.sap.com/saphelp_erp2004/helpdata/en/ce/1d753cab14a909e10000000a11405a/frameset.htm">this</a>.
    hope that helps,
    anton

  • SAP XI versus Sonic's Enterprise Service Bus

    Hi,
    Question 1:
    In David Chappell's book 'Enterprise Service Bus', the Sonic ESB is described. He says that the ESB is more than a hub-and-spoke integration broker: ESB is a MOM and above that several 'generic' services, which handle the traffic and routing on the bus, for instance:
    - Transformation service
    - Content based routing service
    - Orchestration service
    - Splitter service
    - Etc.
    Is this concept adopted in ESA? If so how is this functionality implemented?
    Question 2a: does XI uses xCBL as a XML-dialect?
    Question 2b: does XI make use of the canonical-XML concept (by using xCBL) ?
    Thanks in advance!
    Greetings Theo

    As answer on question 1:
    No I never found any documentation from SAP that described a ESB solution. So al the knowledge must come from other vendors in your case from Sonic.
    But there is hope you can use XI in a ESB way. You must only (add) configure the ESB parts. This is done by adding a service repository for example the UDDI server in combination with some BPML engine.
    By adding it al together you can execute your business processes over multiple system platforms using SOAP in a synchronic way.
    This is the basic concept of a ESB.
    The answer to question 2.
    I don’t know if XI has build in support, but a know that there are free tools that can handle Canonical XML. So you can make a service your self to handle the Canonical XML documents.

  • Practical Enterprise Service Bus Use Cases for SOA & writing for Dev2Dev

    Dev2Dev has just published:
    Practical Enterprise Service Bus Use Cases for SOA
    http://dev2dev.bea.com/pub/a/2006/06/service-bus-use-cases.html
    "What is the role of an ESB within SOA? In this article, Kenny Shin provides some practical advice, illustrating how an ESB adds aspects such as transport security, data validation, and messaging patterns to Web services"
    Check it out. If you'd like to write for Dev2Dev, please contact me - I have plenty of ALSB topics to choose from.
    Regards,
    Jon
    Jon Mountjoy - http://dev2dev.bea.com/pub/au/13

    I also think that same way. I do not know what is so apecial about BEA Aqualogic ESB and other market matured ESB products such as TIBCO & SONIC. The samples which BEA has given in their evaluation guide are very simplistic. BEA should do more to provide extensive knowledge/features about their Aqualogic line of products.

  • How to map business process and enterprise service?

    Recently, I read some documents about ESA. I'm confusing about the relationship between business process and enterprise service. In other word, how to map the business process to enterprise service after the business process is analyzed? Is there any methodology/rule to define business process and wrap them into service in ESA?

    Hi Sherry,
    I like to add some of my thoughts about that discussion. From my point of view ESA is much more than just another BPM or Enterprise BPM. ESA is adresses six key areas and I think all of them are really needed:
    - <b>People Productivity</b> as the word itself describes...it's about portals and productivity.
    - <b>Embedded Analytics</b> has to integrate transactional and analytical content.
    - <b>Service Composition</b> is used for model-driven service composition and services orchestration.
    - <b>Service Enablement</b> is about a Enterprise Services Repository filled with business meaningful Enterprise Services and service patterns for enabled objects. Excactly this is where SAP has years of experiences.
    - <b>Business Process Platform</b> is about service enablement of all application platform objects and engines. This is the place where "BPM" for core business processes resits.
    - <b>Life-Cycle Management</b> has to cover the deployment, configuration, operation and change management for ESA based processes.
    Therefore the term "BPM" is located in serveral layers of an ESA approach. On the level of <u>Business Process Platform</u> BPM is providing the choreography for core business preocesses.
    At <u>Service Enablement</u> BPM needs to compose out of granular services (I would say "atomic" services)
    buiness meaningful services (here we have "molecular" services).
    The third level where BPM could be used is <u>Service Composition</u> because exactly this is the place
    where serveral Enterprise Services could be combined to a process representation.
    To come back to the discussion:
    1. The question should be how to indentify business meaningful services which could represent single process steps. ATP check, Credit card check, ... could be examples. In theory this service could be out-tasked, defined more flexible etc. This means that processes needs to be evaluated for Enterprise Service candidates. Afterwards you can check against SAP's Enterprise Services Repository for already existing Enterprise Services. The evalution for enterprise services candidates will be supported by the metodology mentioned by Kaj and David.
    2. I think domains in this context should be motivated by business and/or functional areas. Depending on the granularity. For example Order Fulfilment Services, Master Data Services, Search Services... These kind of serices can be combined again to services such as "Search of Master Data" (Search Service + Read Master Data Service) etc. or can be used to generate UI to be used in a ESA application.
    Your thoughts?
    Very best regards
    Wulff

  • Hi  all , Need help on Core Services , RFC and Enterprise Services

    Can  anyone provide me links on how to use Core Services , RFC and Enterprise Services.
    I need to communicate with two systems , one uses RFC and the other uses Enterprise Service , so I need to differentiate between them .

    For RFC:
    http://help.sap.com/saphelp_nwce10/helpdata/en/8f/0f6f4132f15c58e10000000a1550b0/frameset.htm
    For modelling external services:
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/174ae492ef5d79e10000000a11466f/frameset.htm
    For Web services:
    http://help.sap.com/saphelp_nwce10/helpdata/en/44/f6087db2b12952e10000000a11466f/frameset.htm
    Developing first web service:
    http://help.sap.com/saphelp_nwce10/helpdata/en/46/917a26cf75581ce10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_nwce10/helpdata/en/27/e49122a62d4dc189b7308c2b0c852e/frameset.htm

  • How to call proxy service at enterprise service bus using flex

    Hi
    I have a proxy service located at wso2 enterprise service bus. How can i call that proxy service using flex?
    Regards
    Minal

    Hi Minal, I think you can communicate with wso2 using mx:HTTPService or mx:WebService, you just need to find out which services you'll be consuming and then create the flex app to present and interact with those services.

  • What's Different Between ODI and FDQM ?

    I need to know What's Different Between ODI and FDQM ?

    At is simplest ODI is an enterprise scale ELT tool that can cope with moving very large amounts of data bwteen heteregeneous systems. It requires a fair degree of technical knowledge to use well and that the user is pretty competent with SQL. It is not really an end user tool and the jobs tend to be lights out scheduled processes with a limited user interface for executing these jobs. FDQM is more of a data quaility tool which gives the average end user the out of the box functionality to be able to transform and load data into various target systems. It is not designed to move very large amounts of data efficiently i.e. multi millions of lines of data like ODI. However it does have a rich user interface that provides an easy to use mapping engine, a repeatbale controlled data load process and has a host of in built reporting and audit features which would have to be built from scratch in a tool like ODI

  • Comparison between 3750 and 3750-metro

    hi folks,
    is there any links which will provide me on the comparison between 3750 and 3750-metro? for exapmple, isis is not support on 3750 but it support on 3750-metro. The product information from cisco site is insufficient in term of the main differences :p
    rgd
    josh.w

    Hi Josh,
    The Cisco Catalyst 3750 Metro Series is built for Metro Ethernet access in a customer location, enabling the delivery of more differentiated Metro Ethernet services. These switches feature bidirectional hierarchical QoS and Traffic Shaping, intelligent 802.1Q tunneling with class-of-service (CoS) mutation, VLAN translation, MPLS, EoMPLS, and Hierarchical Virtual Private LAN Service (H-VPLS) support, and redundant AC or DC power. They are ideal for service providers seeking to deliver profitable business services, such as Layer 2, Layer 3, and MPLS VPNs, in a variety of bandwidths and with different SLAs.
    The metro switches have the PXF chips (which allow hierarchical QoS on the 2 "WAN" GigE ports, so several logical links can share a connection, and have soft bandwidth limits).
    For more details on 3750-M switches have a look at this link
    http://www.cisco.com/en/US/products/hw/switches/ps5532/products_qanda_item09186a00801eb822.shtml
    HTH
    Ankur
    *Pls rate all helpfull post

  • Sun idm adapter for Enterprise Service Bus (Using MQ)

    Hi
    Can you please let me know if any sun idm adapter support Enterprise Service Bus (Using MQ) ?
    Thanks

    As answer on question 1:
    No I never found any documentation from SAP that described a ESB solution. So al the knowledge must come from other vendors in your case from Sonic.
    But there is hope you can use XI in a ESB way. You must only (add) configure the ESB parts. This is done by adding a service repository for example the UDDI server in combination with some BPML engine.
    By adding it al together you can execute your business processes over multiple system platforms using SOAP in a synchronic way.
    This is the basic concept of a ESB.
    The answer to question 2.
    I don’t know if XI has build in support, but a know that there are free tools that can handle Canonical XML. So you can make a service your self to handle the Canonical XML documents.

  • Publish BUS1065 object to Enterprise Service Bus (Tibco)

    Dear forum members,
    We are trying to find out if a concept we designed will work. Our goal is to publish a full business object e.g. BUS 1065 (Employee) to the Enterprise Service Bus (Tibco JMS technology).
    We plan to customize change pointers to the BUS object, which will trigger a replicate of the BUS object. We hope to create an outbound iDoc which will contain the full BUS object. The ESB solution will trigger a JMS publish on receiving the iDoc.
    Does anybody has experience with replicating a business object for a non SAP receiver? Will our concept work?
    kind regards,
    Richard

    Dear forum members,
    We are trying to find out if a concept we designed will work. Our goal is to publish a full business object e.g. BUS 1065 (Employee) to the Enterprise Service Bus (Tibco JMS technology).
    We plan to customize change pointers to the BUS object, which will trigger a replicate of the BUS object. We hope to create an outbound iDoc which will contain the full BUS object. The ESB solution will trigger a JMS publish on receiving the iDoc.
    Does anybody has experience with replicating a business object for a non SAP receiver? Will our concept work?
    kind regards,
    Richard

  • Differences between Personal and Enterprise editions

    Does anybody know where to find the main differences between Personal and Enterprise editions?
    Thanks

    Here is the link to the differences in Oracle 8i:
    http://technet.oracle.com/doc/server.815/a68020/ch4.htm

Maybe you are looking for

  • Outlook 2011 for Mac / Synching issues

    Hi there, it seems that I'm not alone with 'issues' in synching Outlook for Mac 2011 with mobile devices.. The setup I am trying to arm wrestle into submission is MacBook Air (brand new) Mavericks 10.9.3 iPhone 5 iOS 7.1.1. Outlook 2013 (brand new) I

  • Runtime error in xi abap stack -while getting AE logon details

    Hi XI gurus                  We are getting a error in abap stack , transaction SMQ2 in XI box - whose details in sxmb_moni are as follows <SAP:Category>XIServer</SAP:Category>   <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>   <SAP:P1>40

  • Itunes can't sync contacts

    iPhone 4, brand new but not a 4s, Installed iTunes 10.5  on Windows XP comptuer.  iTunes failed to backup phone. Then crashed with message saying it needed to be reloaded.  Reloaded it with the same version 10.5.  iTunes page says 10.5 is compatible

  • Unsupported media type status code 415 error.

    Hi All, I am getting an error "The server is refusing to process the request because the entity has a unsupported format" while Executing the URI for POST. Below are the details: URI:  /sap/opu/odata/sap/YMM7G_UMP_CON_SUPPLIER_SRV/SupplierSplitSet Re

  • Breakpoints in nested classes don't work

    I've noticed that when I set a breakpoint in a nested class, it doesn't work to stop the code, unless I set the breakpoint after I've created an instance of the class. In the code example below, if I set breakpoints A, B, C and D, only breakpoints A