Message Interface : Outbound, Inbound, Abstract  ?

Hi all,
does anyone have tips to use an Outbound, an Inbound or an Abstract Message Interface ? When data is sent from XI, should we use an outbound one ?
Thx to all.

Hi Elliot,
Always think in perspective of the sender and receiver systems.
For sender system, it is output to sender so, Outbound
For receiver system, it is input to receiver so, Inbound
Abstract is used for BPM it can act as both inbound and outbound.
Regards,
Sreenivas
Message was edited by:
        Sreenivas Nettem

Similar Messages

  • Usage of Abstract Message Interface for non-BPM

    Hi,
    I have a message that I am using as both as an inbound and an outbound for 2 different mapping. I am not using BPM. Is it better to create 2 message interfacesone for outbound and one for inboundor should I just create 1 abstract message interface that can be used in both mappings? What are the advantages and disadvantages of using 2 message interfaces (1 inbound and 1 outbound) against 1 abstract message interface? Would using abstract cause a lot of problems or performance problems in the future?
    Thanks in advance.
    Regards,
    Elbert

    hi,
    abstract messages are only used for BPMs
    so I suggest creating 2 instead if you don's use a BPM
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/3355d5617d0a4cb0fe8e042c752caa/content.htm
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • SOAP XI scenario, ambiguity in Abstract Message Interface

    Hi Forum,
    I have a SOAP client(synchronous)--->XI scenario,
    let me describe the scenario,
    Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
    Step 2. in BPM, it does some transformation
    Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
    Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
    now the problem is,  In integration builder, Design,.........
    when i make the abstract Synchronous MI (for the SOAP client to send request), i use 2 message types RequestMessage (output message) and ResponseMessage (input message), ******sounds bit oppsosite ..but it is like that only......but the source of ambiguity
    but when i create the WSDL using the web service creation tool, in integration builder, Configuration, ....... the WSDL is bit unexpected, it shows input as ResponeMessage and output as RequestMessage....hmm.....as such i cant use that WSDL in any tool like altova to create the SOAP request automatically....
    ****the source of all ambiguity is....in the screen for creating the Message interface (as Synchronous abstract/outboud), we give OUTPUT MESSAGE as the input message type and vice versa...
    do u agree.......
    am i wrong?
    in that case how can i make a correct WSDL

    Let us discuss point by point.
    You are doing a scenario SOAP to XI with no end point on the other side. Means you are using XI as the end point for simulating. This is my assumption.
    Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
    Ok.
    Step 2. in BPM, it does some transformation
    Ok
    Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
    You should not use a synchronous send step here. You should be using an Async send here. The sync asyn bridge must start in the first receive step and end here.
    Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
    You shuld create the WSDL for the Outbound Synchronous message interface which should have been created to supply the message to Abstract Synchronous interface. Then only you will be able to test the message.
    So.. you need totally
    1. OB Syn MI
    2. Abstrac Syn MI (Receive in BPM)
    3. Abstract Async MI (to send response to SOAP caller)
    VJ

  • Outbound and Abstract Sync message Interface difference

    Hi Experts,
    Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
    Do we  need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
    Regards
    Sara

    ---Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
    No there is not. U can select any message type irrespective of the type of message interface.
    ---Do we need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
    Yes. As per ur requirement u can specify the same.
    Regards,
    Prateek

  • Unable to view Abstract Message Interface(Sync) in Container Step of BPM

    Dear Friends,
    This is IDOC---SOAP Sync Communication Interface
    I have created the External Def by exporting & importing the Standard Idoc
    and Imported the WSDL File which has the Request & response Structure
    I have created the Outbound Sync message Interface for Idoc side
    and Abstract Sync message Interface for the same to use in BPM
    and also created Inbound Sync Message Interface for Webservice side
    and Abstract Sync Message Interface for the same to use in BPM
    Problem is::::
    While creating the Container varible inside the Integration Process, i have to select the Abstract Message Interface which i created for Idoc.
    But it is not at all visible in the list.
    What might be the problem
    REgards
    Seshagiri

    Hi,
    I have created
    For Idoc side
    1) Create O/b Sync by having request of Idoc and response structure of Idoc 
    2) Create ABS Sync by having the request of Idoc and response structure of Idoc 
    3) Create ABS Async by having the Request of Idoc Only
    For Webservice side
    1) Create I/b Sync by having the request of webservice and response of that
    2) Create ABS Sync by having the request of webservice and response of that
    3) Create ABS Async by having the Response of Webservice only
    I created the Steps inside the Integration Process as showed in the screens.
    1)Integration Process graph
    http://img145.imageshack.us/img145/4848/ipviewwv1.jpg
    2)Receive Step
    http://img293.imageshack.us/img293/1756/receivepropng8.jpg
    3)Send step1
    http://img179.imageshack.us/img179/2200/send1bd0.jpg
    4)Send Step2
    http://img182.imageshack.us/img182/8468/send2wl1.jpg
    When i check the F7, it is throwing the error like
    http://img247.imageshack.us/img247/4356/errortx3.jpg
    Regards
    Seshagiri

  • Requirement of a abstract message interface

    Hello,
    I wonder when to use abstract message interfaces?
    The documentations says:
    An abstract message interface has no implementation in an application system. You cannot generate a proxy for this interface type. You use abstract interfaces in business processes, for example, to receive or send messages from application systems. You can use the same abstract interface to receive or to send.
    What does IMPLEMENTATION mean in this context? Can anybody discribe a concrete need for abstract message interfaces?
    Thank You

    Hi Mario,
    you only use those interfaces inside a BPM:
    send step, receive step, transformations etc
    (no other use)
    - you cannot create proxies from it
    - you must have an normal (not abstract) interface
    to send data to XI or to receive data
    (so once you create everything inside your integration process - with the use of abstract interfaces)
    inside ID you still have to use standard interfaces
    (outbound or inbound)
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • What is an Abstract in message interface ?

    hai pals,
         can anybody clarify ,what is an Abtract in message interface of integration builder of xi.
          Is this,neccessary to specify and create the interface with type abstract.
           if yes , can u pls tell me why?
    right answers will be appricited
    have a nice day.
    raj

    you can also take a look at this definition:
    "Interface for which no direction is defined initially.
    An abstract message interface has no implementation in an
    application system. You <b>cannot generate a proxy</b> for this
    interface type. You use abstract interfaces in business
    processes, for example, to receive or send messages from
    application systems. You can use the same abstract
    interface to receive or to send."
    from:
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/3355d5617d0a4cb0fe8e042c752caa/content.htm
    Regards,
    michal

  • Abstract asynchronous message interface for fault (exception) messages

    Hi,
    Has anyone yet discovered how to create an abstract asynchronous message interface for a fault message so that said message can be referenced in an Integration Process? I am currently at a loss as to how to reference the exception message returned by a synchronous RFC call, and how to return the fault message of a synchronous MI from a BPM.
    Thanks for any help you can provide on this issue - please do not refer me to existing blogs or forum messages if they do not specifically answer this question in a positive manner. I have just been through the SAP Notes and the SDN forum and Google and while I have seen many questions about this topic I have not seen any answers. 
    Stephen

    hi stephen,
    never worked on this but out ofcuriosity after seeing ur question i tried to  create one:
    but i found these:
    fault message types will only be used in case of synchronous messages.....if it is asynchronous the fault message type radio button it self will not seen while creating message interface..just check.
    you need to create a Fault message type to use it in an interface...u can add your own fields also if u want.
    in your present case you mentioned you are using synchronous RFC...try creating a synchronous abstract interface there you can give fault message type also...just check by creating one...
    correct me if i am wrong...
    regards.

  • Outbound Service/Message interface in PI 7.1

    Can anybody let me know the following please...
    How should I go about "Creating an Outbound Service/Message interface in PI 7.1 " ? Or even check if there is an existing one already. ?
    How to access ESR/IR ?
    Thanks

    Hi Tony,
    Could you please explain a little more on your scenario.
    Please refer the document  for help Consume Enterprise Services in Java Using
    SAP NetWeaver Developer Studio
    [Consume Enterprise Services in Java Using SAP NetWeaver Developer Studio|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80d9fbfe-1e97-2c10-e9b3-ad9a10f1f6cb?quicklink=index&overridelayout=true]
    Also you can find good links in this forum [post|Java Proxy & NWDS;
    try if you get some clue to your problem after going through these documents.
    Regards.
    Srinivas
    Helpful => Star

  • Message Interface Inbound

    Hi All!!
    I want to create a Message Interface Inbound to generate an ABAP Proxy on SPROXY.
    Somebody could give me some tutorial or "step by step" which guide me on the process, please??
    I won´t forget for awarding points.
    Thanks and regards,
    Manuel.

    Hi,
    Just go through these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
    ABAP Server Proxies By Siva Maranani
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    /people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    File to R/3 via ABAP Proxy with good example
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
    http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
    Generating java proxies..
    /people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
    /people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
    Regards,
    Sarvesh

  • Exposing mutiple outbound message interface as a single Web service

    Hi all,
    My Scenario is SOAP <--> PI 7.0 <---> SAP R/3 (Proxy communication). A third party portal will communicate 24/7 online with SAP R/3 via PI 7.0. I have to expose all the outbound message interfaces as a single webservice, so that the third party portal will consume that web service and will communicate to SAP R/3. The communication between Portal and PI 7.0 will be SOAP and from PI to SAP R/3 as proxy communication. I can able to expose a each outbound message interface as a webservice individually i.e each message interface gets separate WSDL file. But the portal people asking me to generate single WSDL (web service) in which all the message interfaces should be included as operations. Could you please send me the information, how to generate a single web service for all the message interfaces?
    I have gone through the entire SDN community, but could nt able to get the information. If anybody worked on similer issue , please guide me to approach to get the solution.
    Regards
    Vijayanand Poreddy

    Hi,
    It is possible to expose all operation using one endpoint by overwritting the default interface name and interface namespace in one "generic" soap sender CC. To achieve it, you need to set the following options Use Encoded Headers and Use Query String in your sender CC.
    Unfortunatelly, there is one drowback of this approach. Before portal will send the request, it has to concatenate the generic endpoint:
    http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
    with URL encoded interface information:
    &version=3.0&Interface=http%3A%2F%2Fsap.com%2Ftest%5ETest
    for each operations.
    For more detail ref these docs:
    [How To… Use the XI 3.0 SOAP Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79]
    [Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wbCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597&nlang=EN&smpsrv=https%3a%2f%2fwebsmp210%2esap-ag%2ede]
    I guess that in PI 7.1 this disadvantage will be enhanced.
    Regards,
    Jakub

  • BPM - Message Interface

    Hello all,
    I have some doubts about Messages Interface used in BPM.
    BPM just used Abstract Message Interfaces, but to expose the Interface to sender aplication, XI need the same Message Interfaces that is declared abstract but no abstract.
    My question is how the Business Process Engine that the Outbound Message Interface, that my application is using, is the Abstract Interface that activate my Integration Process???
    Regards,
    Luiz

    Hi
    BPM can process only through abstract interfaces.
    Those abstract interfaces attached to a receive step in BPM(Receive step is a mandatory step to start the integration process) are automatically assigned as inbound interfaces with respect to BPM and will be outbound interfaces with respect to sender side and similarly in the receiver side.
    I didnt get your question properly.hope i am giving the answer you needed.
    Thanks and Regards,
    Vineetha

  • Sync to Asyn Message interface mapping

    Hi all,
    I have a scenario where source message interface is a sync interface and target is async. Can any body suggest if it is possible to map the request message structure of source to target (async) and the response need to have a fixed value.
    Is it required to use BPM or is it possible without BPM. Can any body please suggest? Any help will be appreciated.
    Thanks
    -Kulwant

    Hi,
    Defining Sync/Async Communication
    Use
    To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
    You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
    See: Async/Sync and Sync/Async Bridge in JMS Adapter
    We use Sync/Async bridge to establish the Sync communication between the Applications.
    Normally the Technical adapters like File will not support the Sync communication to send back the Response to the Sender system from the File system.
    So in this case we will use Sync/Async bridge to establish the connection using BPM.
    Check these
    Bridging the Sync-Async bridge with Fork (XI)
    Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
    Structure of a Sync/Async Bridge
    The following table outlines the minimum components of a sync/async bridge:
    *Step
    Use*
    Receive step to open the sync/async bridge
    Receives the message request from the synchronously calling business system and opens the sync/async bridge
    Asynchronous send step
    Sends the received message asynchronously to the asynchronously called business system
    Receive step
    Receives the message from the asynchronously called business system
    Send step to close the sync/async bridge
    Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
    Performance Considerations
    If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
    Fault Messages
    It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
    Procedure
    Define a Receive Step to Open the Sync/Async Bridge
    1. Insert the receive step to open the sync/async bridge in the integration process.
    *You can do this at the following points: *
    Directly after the start marker
    As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
    As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
    2. In the object area, define the container element that receives the synchronously sent message.
    Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
    3. Select this container element in the Message field in the properties area of the receive step.
    4. In the Mode field, select Open S/A Bridge.
    5. Select the Start Process field.
    The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
    6. Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
    Define an Asynchronous Send Step
    7. Insert a send step that sends the received message asynchronously to the asynchronously called business system.
    See also: Sending Messages from Integration Processes Asynchronously
    Define a Receive Step
    8. Insert a receive step that receives the message from the asynchronously called business system.
    Define a Send Step to Close the Sync/Async Bridge
    9. Insert the send step at the required position in the process definition.
    Do not insert the send step in a loop, block, or fork.
    10. In the Mode field, select Close S/A Bridge.
    The integration process must not contain any further send steps to close a sync/async bridge.
    11. In the Opened By field, specify the receive step that opened the sync/async bridge.
    12. In the message field, specify the message that is sent to the synchronous interface.
    This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
    Example
    You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
    For a description of the example, see Example: Sync/Async Communication.
    BPM is an additional advantage of Netweaver XI. it provides features like Sync-Async Bridge, Async-Sync Bridge, stateful msgt processing.....so on.
    Sync-Async Bridge acts as a bridge between a synchronous Business system and Asynchronous business system.
    forex: if u r communicating with a synchronous RFC to a File system(always asynchronous, which is not able to send any response to synchronous RFC Interface).
    In this kind of scenarios BPM Sync-Async Bridge enables communication between a Synchronous RFC to Asynchronous File system or vice versa..
    Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
    Plz go thru the following:
    - Use of Synch - Asynch bridge in ccBPM
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
    Asyn - Synch BPM -
    http://help.sap.com/saphelp_nw70/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
    Example on Sync/Async communication:
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
    Thanks,
    Swathi

  • Data &message types,message interface, interface&message mapping

    hi
    I am very new to XI, i want to know about
    1) Data Types
    2)Message Types
    3)message interface
    4) interface mapping
    5)message mapping
    i am totally confused with eachother, can you please give me the clear definitions for these things
    regards
    pradeep

    Hi Pradeep,
    A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged
    ->A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
    A data type is an XML Schema Definition (XSD). This definition determines how the valid payload of a message will look. Data types in XML schema are only an abstract description of a structure that you can assign to elements in an XML schema definition. A message type or a fault message type that references a data type determines the name of the root element of a message.
    Ref link
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    2)Message Types
    A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
    ·        More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
    ·        When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
    3)message interface
    You use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
    4) interface mapping
    Interface mappings register your mapping program for an interface pair in the Integration Repository.
    5)message mapping
    A message mapping refers to a mapping of messages and is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures and connect to a value mapping.
    Follow these Ref Link for all answers...
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    Regards,
    Ramesh.

  • Creation of Server Proxy for  Message interface with External Defination

    Dear All,
    I am getting a problem while generating a server proxy for the inbound interface . The request message used in the inbound interface is a external definition which is uploaded using a XSD file. The XSD file was supplied by a third party which is having very high complex strucuture and used lot of abstract data types in the design. When i tried to generate the proxy in the R/3 system (Transaction SPROXY) for the inbound interface i am getting following error.
    Interface uses external and internal message definitions
    Message no. SPRX122 *
    Diagnosis
    In a message interface you can use messages from different sources:
    Message types and fault message types edited in the Enterprise Services Repository
    Messages imported into the Enterprise Services Repository (external definitions, RFC, IDoc)
    In the current message interface, message types from different sources have been used. Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
    System Response
    The interface cannot be generated.
    Procedure
    Change the interface definition accordingly in the Enterprise Services Repository.
    Please guide me, how to generate the proxy for the interface with external defination message. I could nt geneate manullay, because it is having very high complexity and its a big structure.
    Is there is any way to generate the proxy for interface with external definition
    Regards
    Vijayanand

    Hi,
    i.       Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
    ii.       Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
    Check this, it may help you
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
    REgards
    Seshagiri

Maybe you are looking for