Difference Between Transport and message protocols in XI

Hi,
    Can u please explain with some example , Difference Between Transport and message protocols in XI.
thanks
dhanush

Hi dhanush,
This two can have different attributes which were assigned in the adapter metadata. Please see this help for some info on this:
http://help.sap.com/saphelp_nw04/helpdata/en/79/e462405c910272e10000000a155106/content.htm
Go to SAP BASIS 6.40 or 7.00 software compoenent and open namespace http://sap.com/xi/XI/System. Go to Adapter objects and open Adapter metadata. Then open any adapter. Here you can see all the properties of your adapter which support.
Transport protocol gives information about outside of message details, kind of system, security details.
A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
Message protocol gives you an idea of message type XI payload
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm
Regards
Biplab
<b><i>
note:reward with points if helpful</i></b>

Similar Messages

  • Differences between Issue and Message?

    Hi all,
    Can anyone know the exact difference between issue and message? 
    In testing perspective, which one should we post?
    Regards,
    Vijaya Bhaskar

    Hi Vijaya,
    The difference starts in the concept.
    Issues are meant to handle project problems, like lack of human resources, lack of expertise, go-live strategy decision, that is all problems that are mainly linked to a managerial decision/order and can have impact on business.
    Messages are meant to handle system problems, like printer not working, message error when saving a purchase order, lack of authorizations,etc.
    Because of these differences, also the funcions available for each one and the workflow will be different.
    Hope this could make this more clear to you.
    Regards,
    Val

  • JMS paging store - what is difference between bytes and messages threshholds?

              You can activate and configure both "bytes paging" and "message paging". What
              is the difference? Why use one or the other or are both required?
              Thanks,
              John
              

    Hi Mr. Black,
              Cool name.
              Message paging is based on number of messages. Bytes paging is based
              on the size of message payload (properties, body, corr-id, and type),
              where the payload does not include the header size. One can set
              either or both -- if both are set, paging kicks in as soon
              as the first threshhold is reached.
              As for which one to use, you may wish to set both. The former
              accounts for large numbers of small messages, and the latter
              handles large messages. (eg 1000 small 10 byte messages
              will charge 10,000 bytes toward quota but actually use up
              128,000 bytes of JVM memory once the header is thrown in...)
              Tom
              John Black wrote:
              > You can activate and configure both "bytes paging" and "message
              paging". What
              > is the difference? Why use one or the other or are both required?
              >
              > Thanks,
              > John
              

  • What is difference between transport protocol and message protocol

    what is difference between transport protocol and message protocol
    please give definition and small explanation

    Hi,
    Transport protocol gives information about outside of message details, kind of system, security details.
    A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
    Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
    Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
    Message protocol gives you an idea of message type XI payload
    http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm

  • What's the difference between transport route and transport layer

    what's the difference between transport route and transport layer,Can somebody give me some explaination? thks in advance!

    Hi,
    Transport Layer in ABAP Workbench
        The Change and Transport System supports the distribution of development
        work on large projects across multiple SAP Systems.
        The packages in each development system are grouped into one transport
        layer.
        The transport layer determines whether objects are assigned to a local
        or transportable change request.
    Use
        Each of your SAP development systems is assigned a transport layer as
        its standard transport layer. If you use Extended Transport Control, you
        can assign different standard transport layers to certain clients.
        You can define at the most one consolidation target for each SAP System
    and transport layer.
    When you create a package, it is assigned the standard transport layer
    of the SAP System.
    If you want to assign a different transport layer to a package, you
    require the administration authorization for the Change and Transport
    System.
    The objects in a package automatically have the transport attributes
    defined for the corresponding transport layer.
    o   If a consolidation route originating in their SAP System is defined,
         then the objects are assigned to a transportable request, and
         transported into the consolidation target when it is released.
    o   If a consolidation route is not defined, the objects are assigned to
         a local request, and are not transported.
    Customizing settings are not assigned to a package. They have the
    transport attributes of the standard transport layer of the system or
    client.
    It is best to assign a package a standard transport layer for which a
    consolidation route originating in the development system is defined.
    To display and maintain the transport layers and routes, use the
    Transport Management System (transaction STMS).
    Only the system adminstrator can make changes.
    Caution:
         The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of
         Release 4.0A and cannot be maintained.
    Regards
    Ben

  • Difference between u2018Workbenchu2019 and u2018Customizeu2019 Transport request.

    Hi Experts,
    What is the difference between u2018Workbenchu2019 and u2018Customizeu2019 Transport request.
    Thanks

    Workbench Requests
    When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
    Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
    Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
    Customizing requests
    Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
    Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
    Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually

  • Difference between CTS and Transport request

    Hi,
    i need to know what is the Difference between CTS and Transport request.
    kindly expecting replies

    CTS (Change & Transport System)
    The CTS is a tool that helps you to organize development projects in the ABAP workbench & in customizing and then transport the changes between the SAP Systems & clients in your system landscape.
    This docuentation provides you with an overviewof how to manage changes with the CTS & essential information on setting up your system & client lanscape & deciding on a transport strategy. Read & follow the documentation when planning ur development project.
    For practical information on working with the Change & Transport system, see Change & transport Organizer & Transport Management System.
    Transport Request
    Transport Request is a Request number where the developments are given logical storage number which in turn help in transporting the developments to one system / server to other server.
    T.Code SE09 & SE10 are used to Transport the request..
    Click the Display button.
    The list of Workbench ( Workbench request )Customizing ( Customizing request) are shown.
    Reward Points if useful.

  • Difference between a persistent messages  and non persistent messages in JM

    Hi
    This question is with respect to persistent messages , and non persistent messages .
    As per the docs it says that for persistent messages the QueueSender.send() blocks until it recivies an acknowledgement .
    Here my question is what is the difference between a persistent messages , and non persistent messages
    Thanks in advance .

    The exact behaviour depends on the JMS provider being used. But since non-persistent messages are defined to be unreliable, the provider may indeed decide that it's not necessary for the server to acknowledge the receipt of a non-durable message from a producer.
    Nigel

  • Difference between BAPI and IDocs

    hello all
    what is difference between BAPI and IDocs

    Hi,
    BAPI
    One of the big plusses for BAPIs is that the interface and function are not supposed to change.  This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
    Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
    The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
    You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
    BAPIs probably have better performance since they don't do the screen flow processing.
    In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
    BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    IDOC
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed.   Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data.   The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    Regards,
    Bhaskar

  • What is the difference between rfc and idoc

    hi,
       My name is rambabu.can anyone of u please tell me the main differences between idoc and rfc??
    Thanks in Advance

    hi Ramesh,
    Remote Function Calls (RFC) and data exchange through IDoc
    message documents. RFC makes direct and synchronous calls of a program in
    the remote system. If the caller is an external program it will call an
    RFC-enabled function in R/3 and if the calling program is the R/3 system
    it will call an RFC-function in another R/3-system or it will call a
    non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are
    a subset of the RFC-enabled function modules, especially designed as
    Application Programming Interface (API) to the SAP business object, or in
    other words: are function modules officially released by SAP to be called
    from external programs.
    IDocs are text encoded documents with a rigid structure that are used to
    exchange data between R/3 and a foreign system. Instead of calling a
    program in the destination system directly, the data is first packed into
    an IDoc and then sent to the receiving system, where it is analyzed and
    properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls
    and IDoc data exchange is the fact, that every action performed on IDocs
    are protocolled by R/3 and IDocs can be reprocessed if an error occurred
    in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE
    are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to
    deliver data to the receiving system. ALE is basically the scheduling
    mechanism that defines when and between which partners and what kind of
    data will be exchanged on a regular or event triggered basis. Such a
    set-up is called an ALE-scenario.
    Regards
    Sreeram.G.Reddy

  • Difference Between Cofiles and Datafiles

    Hi
    Can Any one pls explain the Difference Between Cofiles and Datafiles in Trans Directory.
    Need to know their Role and Internal Process in Transporting the Request or a Client.
    Thanks in Advance
    Dan

    Hi,
    Data file contains actual change data.
    Cofile contains information on change requests (different steps of a change request and their exit codes).
    So you will find cofile of same size for all requests.
    Regards
    Payal
    Message was edited by:
            Payal Patel

  • Can anybody give me the difference between Catt and Ecatt

    Hi gurus,
    Can any body give me the difference between catt and ecatt.

    Hi,
    I think this is new technology in sap.
    I know little bit of this can u go through this.
    eCATT (extended Computer Aided Test Tool)
    What is eCATT?
    eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated. 
    eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
    Features of eCATT:
    Following functions can be performed using eCATT:
    Test transactions, reports and scenarios.
    Call BAPIs and function modules.
    Test remote systems.
    Check authorizations (user profiles).
    Test updates (database, applications, GUI).
    Set up customizing tables.
    Test the effect of changes to customizing settings.
    Perform load testing.
    Check system messages.
    Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
    Supports CATT migration to eCATT.
    All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
    eCATT Objects can easily download & upload in XML with XSD format.
    There can be several versions of Test Scripts, which allows different implementations with different releases.
    The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
    Why eCATT?
    CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
    Due to automation, testing time is reduced to a large extent.
    Due to automation, less manpower is required for testing. This helps financially.
    Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
    Proved to be extremely useful in implementation projects.
    In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
    Differences between CATT and eCATT?
    Till date, CATT could only be used with the R/3 system. eCATT (which is available with SAP Web Application Server 6.20) covers the automatic testing in SAPGUI for Windows and SAP GUI for Java. For other GUIs and Applications, eCATT provides an interface for external tools. This allows companies to perform automated tests from an SAP system in a complete IT solution landscape across system boundaries. These new options enable complete automation of solution landscapes under standard Windows and Web-based user interfaces- resulting in low-cost operation of an IT Solution.
    eCATT (extended Computer Aided Test Tool)
    eCATT requisites
    Web Application Server (WAS) 6.20 or more.
    SAPGUI 6.20 or more.
    R/3 4.6C or more. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.7).
    Before creating Test Scripts using eCATT, some system settings need to be done: 
    Maintain table T000.
    1.      Go to transaction SM31
    2.      Enter T000 and chose MAINTAIN.
    3.      In the Change View “Clients”: Overview screen, select the relevant client and choose “Details”
    4.      In the “CATT and eCATT Restrictions” field, select “CATT and eCATT allowed”.
    5.      Click on SAVE. 
    Enabling scripting at the Front-end
    1.      On any SAP GUI screen, choose “Customizing of Local Layout”.
    2.      Choose Options
    3.      Choose “Scripting Tab”
    4.      Select “Enable Scripting”
    5.      Click Apply and then OK. 
    Enabling Scripting on the Application Server
    1.      Go to transaction RZ11.
    2.      On the Maintain Profile Parameters screen, enter sapgui/user_scripting.
    3.       Choose Display.
    4.      If the Current Value is not set to TRUE, then click on Change Value:
    5.      Enter TRUE in the “New Value”.
    6.      Click on SAVE.
    eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated. 
    eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
    Features of eCATT:
    Following functions can be performed using eCATT:
    Test transactions, reports and scenarios.
    Call BAPIs and function modules.
    Test remote systems.
    Check authorizations (user profiles).
    Test updates (database, applications, GUI).
    Set up customizing tables.
    Test the effect of changes to customizing settings.
    Perform load testing.
    Check system messages.
    Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
    Supports CATT migration to eCATT.
    All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
    eCATT Objects can easily download & upload in XML with XSD format.
    There can be several versions of Test Scripts, which allows different implementations with different releases.
    The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
    Why eCATT?
    CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
    Due to automation, testing time is reduced to a large extent.
    Due to automation, less manpower is required for testing. This helps financially.
    Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
    Proved to be extremely useful in implementation projects.
    In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
    Reward points if it is helpful.
    Rgds,
    P.Nag

  • Difference between IntegrationServer and Integration Engine

    Hi,
    Could you please provide me difference between IntegrationServer and Integration Engine.
    functionality of both and what are the runtime environments exits in XI Server.
    Could you please show me digaram how message flow from
    XI server i.e., through which engines.. what is the input and output of each engine.
    Thanks,
    RamuV

    Hello Ramu,
    Go through this link..
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/0c733cb7d61952e10000000a11405a/frameset.htm
    Use
    Two SAP XI 3.0 Integration Servers are used to exchange messages between the system landscapes of two business partners.
    Description
    An SAP XI  Integration Server of a business partner is connected to the SAP XI  Integration Server of another business partner. Both use SAP XI  message protocol to send or receive messages.
    When an SAP XI  Integration Server receives a message from another Integration Server it understands the message format and so processes the message.
    Example
    A business partner that uses SAP XI  wants to send a message to another business partner who also uses SAP XI .
    ·        The message is sent between the Integration Servers in SAP XI  message format
    ·        The Integration Server of the second business partner then sends the message to the relevant business system
    Integration Engine
    Purpose
    The Integration Engine enables you to process XML messages exchanged between applications in heterogeneous system landscapes. Both applications of SAP components and external applications can communicate with the Integration Engine.
    Using adapters, the Integration Engine can also process IDocs (Intermediate Documents) and RFCs (Remote Function Calls). This option is available for applications that have already defined IDocs or RFCs, as well as for applications of SAP components that do not yet have access to the proxy generation functions.
    Integration
    The Integration Engine is the runtime environment of the SAP Exchange Infrastructure. The following are examples of other important parts of this infrastructure:
    ·        Proxy Generation
    ·        Integration Repository
    ·        Integration Directory
    The integration processes involved can take place between heterogeneous system components within a company, as well as between business partners outside company boundaries.
    Features
    The Integration Engine, as a runtime component of SAP Exchange Infrastructure, has the task of receiving, processing, and forwarding XML messages. During message processing, collaboration agreements are evaluated, the receivers are determined, and mapping activities are executed.
    The individual processing steps are called pipeline services and are defined in pipelines. It is the task of the Integration Engine to process these pipelines correctly and consistently. To guarantee this, you must configure the Integration Engine accordingly and monitor the message processing. Both event-driven message processing and prioritized message processing are possible.
    Thanks,
    Satya Kumar
    Edited by: SATYA KUMAR AKKARABOYANA on Apr 22, 2008 3:34 PM

  • Difference between passive and active data connection mode for  FTP

    Hi,
    Does any body have the idea of passive and active data connection mode for the transport protocol FTP.
    I have one server with FTP, I have to pick the data from this FTP to XI.
    What is the difference between active and passive data connection? Does XI supports both the connections?
    Thanks & Regards
    Katta Mohan Reddy

    Hi
    According to SAP Note - 821267
    Q: Does the File Adapter support active data connections when connecting to an FTP server?
    A: Up to and including SP14, the File Adapter exclusively uses passive data connections. Starting with SP15, active connections will be available.
    Difference between active and passive,
    You can definitely refer to the site mentioned by Suraj
    cheers
    Sameer

  • Difference between b2bmessageid and PROTOCOLMESSAGEID

    Hi,
    Can somebody explain the difference between b2bmessageid and PROTOCOLMESSAGEID?
    When trying to resumit failed outbound message(using resubmission java comand), can I resubmit it based on the protocol message id?
    Thanks,
    Kevin

    Thanks, Kalyan, Ramesh
    We're using the Rosettanet and find that B2BmessageID always has the same values as PROTOCOLMESSAGEID.
    We can NOT manually (using the java oracle.tip.adapter.b2b.data.ReSubmit b2bmessageid) resubmit some outbound message (3A4 Confirmation) that was submitted some time ago, and will get the AIP-50501 error. For other message type in Rosettanet such as 3B2, 3A7, we can resubmit multiple times successfully.
    When resubmission failed, we got the detail error info below. Actually AAA is Seller and BBB is a buyer. Can you please throw some light on it, thanks?
    Description: Unable to identify the trading partner agreement from the given input values.
    Also verify agreement effectiveToDate
    StackTrace:
    Error -: AIP-50501: Trading partner agreement not found for the given input values: From party
    [NAME-ROLE] "AAA-Buyer", To party [NAME-ROLE] "BBB-Seller", Collaboration
    name "3A4"; also verify agreement effectiveToDate
    at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.ja
    va:2056)
    at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:177)
    at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:496)
    at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:208
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:984)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:740)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:394)
    at java.lang.Thread.run(Thread.java:534)
    Thanks,
    Kevin Lei

Maybe you are looking for