Skip to Content
author's profile photo Former Member
Former Member

Number of ABAP Proxy Receiver Channels

Hi all.

I would like to know which is the optimum configuration (for performance) about ABAP Proxy Receiver channels.

We have one R3 system and all the ABAP Proxies are in the same client. So it's enough with a single receiver channel pointing to the R3 destination, but what is better for performance? Single channel for all scenarios or one per scenario?

I've the same question for JDBC receiver channels pointing to the same database.

Thanks,

Gari.

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Dec 05, 2007 at 09:01 AM

    <i>Single channel for all scenarios or one per scenario?</i>

    For one receiver and one interface, u can use only one communication channel. i.e, only one receiver agreement

    Regards,

    Prateek

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 09:12 AM

    Hi,

    You can have only one communication channel for one recevier (only one seneraio at a time).

    And its the same with JBBC also .................

    Click on the link below for mor info

    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

    Reward with ponits if helpfull

    Regards

    Sai Ganesh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 05, 2007 at 09:34 AM

    Hi,

    Hope this will help you a bit.

    Within an SAP Exchange Infrastructure (SAP XI) installation, there are various possible

    resource shortages: on the SAP Web AS ABAP, for example, if ccBPM is used

    extensively, or on the SAP Web AS Java, if huge and complex mappings are executed.

    However, you should only scale the SAP Web AS Add-In installation (ABAP and Java in

    one system) with SAP Web AS Add-Inn dialog instances. By scaling the SAP Web AS

    Add-In installation homogeneously, the dialog instances will all look the same. If you

    change the layout or functionality of some dialog instances, for example, by activating

    specific adapters on only one SAP Web AS Java server node, this might create a new

    SPOF. To keep operational tasks as simple as possible, we recommend that you keep all dialog instances the same.

    From a runtime perspective, the most interesting point in a scaled SAP XI landscape is

    communication. There are two different kinds of communication:

    • Messaging, either from or to business systems, or between the Integration Server

    and the Adapter Engine

    • Internal communication, for example, mapping requests, System Landscape

    Directory (SLD) requests, exchange profile requests, and so on

    Due to specific restrictions, you must not change the exchange profile. All connections

    defined in the exchange profile should point to the central instance. RFC connections are established and SLD associations are created based on these parameters. If you have

    set the exchange profile parameters, it is not possible to apply RFC logon that is based on message server and logon group (due to the need for load balancing).

    Also check The HTTP destination INTEGRATION_DIRECTORY_HMI, as defined in

    transaction SM59, should not point to the load balancer, but directly to the central

    instance. and also check SAP Note: 538405.

    help.sap.com/nw04 → SAP NetWeaver → Solution Life Cycle Management → System

    Management &#8594; Configuration &#8594; Dynamic Logon Load Distribution &#8594; Configure Dynamic Logon

    Load Distribution for RFC Calls.

    SAP XI Internal Communication

    SAP XI uses both SAP Web AS ABAP and SAP Web AS Java at runtime. The

    Integration Server, the plain HTTP adapter, and the IDoc adapter are part of the SAP

    Web AS ABAP, whereas the other adapters and the Java mapping are located on the

    SAP Web AS Java. Therefore, there is some internal communication at runtime.

    If a message is sent to the Integration Server through an adapter which resides on the

    Adapter Engine, for example the SOAP adapter or the file/FTP adapter, the message

    must be sent from the Adapter Engine to the Integration Server (AE to IS) for further

    processing. Messages that need to be delivered through a specific adapter need to be

    sent from the Integration Server to the Adapter Engine (IS to AE).

    Finally you can check more info at www.sdn.sap.com/irj/sdn/howtoguides.

    Regards

    Aashish Sinha

    PS : reward points if helpful

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.