on 03-14-2008 6:37 AM
Hi All ..!
What is the benefit of loose coupling in Xi.
How is this achived?
Loose coupling in XI.
The coupling between distributed application systems can be either loose or narrow. A loose coupling is implemented with asynchronous communications and is used for write accesses. A narrow coupling, in contrast, is implemented with synchronous calls, and should only be used for reading data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Outbound and inbound interfaces are used to separate (potential) senders and receivers. The interface parameters do not have to match for a message exchange to be possible (but a mapping is required at runtime if they do not). This enables various different senders and receivers to communicate with each other. In particular, this loose coupling also enables you to assign interfaces to each other when one side of the communication must not, or cannot be changed. For example, an outbound interface can be a message interface for calling an RFC in a 4.6C SAP system. In this call, the RFC has the role of an inbound interface.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The essence of loose coupling is to allow changes or problems that happen on "one end of the wire" to avoid impacting the other end
The coupling between distributed application systems can be either loose or narrow. A loose coupling is implemented with asynchronous communications and is used for write accesses. A narrow coupling, in contrast, is implemented with synchronous calls, and should only be used for reading data.
Both types of coupling can be implemented by calling BAPIs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abiram
Loose coupling is primarily achieved in XI using Async scenarios. In async scenario, the sender is least bothered whether the receiver is up and running at the time when sender sends the data. It is responsibility of XI to handle the confirmed posting of message to receiver. This way sender and receiver are loosely coupled
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The essence of loose coupling is to allow changes or problems that happen on "one end of the wire" to avoid impacting the other end
The coupling between distributed application systems can be either loose or narrow. A loose coupling is implemented with asynchronous communications and is used for write accesses. A narrow coupling, in contrast, is implemented with synchronous calls, and should only be used for reading data.
Both types of coupling can be implemented by calling BAPIs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhiram,
Just check here what is meaning of 'loose coupling"?
http://searchsoa.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid26_gci1069559,00.html
Loose coupling in XI.
The coupling between distributed application systems can be either loose or narrow. A loose coupling is implemented with asynchronous communications and is used for write accesses. A narrow coupling, in contrast, is implemented with synchronous calls, and should only be used for reading data.
Loose Coupling
In a distributed environment, it is especially important that the systems be loosely coupled and independent of one another. If the called system is down, or a communication error occurs, the calling system can continue working normally. One example in which a loose coupling is essential is inventory management: When an inventory management component is combined with an accounting component, it must be possible to post goods movements even when the accounting component is unavailable.
Loose coupling means that the individual systems for the most part communicate asynchronously with each other. In this type of communication, messages are exchanged between the systems. The data format used for these messages is called the Intermediate Document (IDoc). IDocs are structured data containers in which the data can be stored hierarchically.
see here for more info...
http://help.sap.com/saphelp_46c/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
Thanqs
biplab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Loose coupling is primarily achieved in XI using Async scenarios. In async scenario, the sender is least bothered whether the receiver is up and running at the time when sender sends the data. It is responsibility of XI to handle the confirmed posting of message to receiver. This way sender and receiver are loosely coupled
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Loose coupling is a design goal most sought by organizations that are implementing an Enterprise Messaging System (EMS). Loose coupling is often achieved by programming to an interface.
The Loose coupling concept has multiple dimensions. For example, integration between two applications may be loosely coupled in time using Message-oriented middleware - meaning the availability of one system does not affect the other. Alternatively, integration may be loosely coupled in format using middleware to perform Data transformation - meaning differences in data models do not prevent integration. In Web Services or Service Oriented Architecture, loose coupling may mean simply that the implementation is hidden from the caller.
Loose coupling can be applied to any friction-free linking enabled by open architectures. Loosely coupled services, even if they use incompatible system technologies, may be able to be joined together on demand to create composite services, or disassembled just as easily into their functional components. Participants can establish (normatively or inceptively) a shared semantic framework to ensure messages retain a consistent meaning across participating services.
Loose coupling describes an approach where integration interfaces are developed with minimal assumptions between the sending/receiving parties, thus reducing the risk that a change in one application/module will force a change in another application/module.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
loose coupling is very similar to what we call as "plug and play" in terms of attaching devices to a computer.
In terms of XI, loose coupling would imply integrating different kinds of systems/interfaces with least difficulty for which XI stands for...
in XI, this is obtained by a rich collection of adapters to literally integrate with any system of your choice...
regards
krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.