Sender communication channel for  HTTP and IDOC

Why the sender communication channel is not necessary for HTTP and IDOC

Hi,
Because they lie on ABAP stack ie on Integration Engine...so that they can process directly but other adapter lies on Adapter engine.
Regards
Hemant

Similar Messages

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • BIC Module Error in Sender Communication channel for EDI to File scenario.

    Hi Experts,
    We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
    Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
    Thanks & Regards,
    Abhishek

    Hi Abhishek,
    Is there any special character present in the EDI file?
    the parser is not able to parse the data.
    you can check the BIC conversion log for more information.
    Regards,
    Harish

  • How to set up the communication channel for third party idoc

    Hello,
    I am trying to send an idoc from an sap 4.6c system to an third party system. The third party system is supporting idcos with trfc.
    My problem is to set up the communication channel in the integration builder (configuration) for the third party system. The idoc is waitung in XI to transport.
    My settings are:
    adapter type: idoc
    transport protocol: idoc
    message protocol: idoc
    adapter engine: integration engine
    rfc destination: xyz (is working fine)
    interface version: sap release 4.0 or higher
    port: ??
    sap release 46c
    My problem is the port. should i set up a port in idx1? But the third party is not an sap system and so i dont have a client.
    On the xi i have defined a port in transaction we21 (transactional rfc) for the third party with my rfc destination xyz. But if i enter that port in communication channel i got error messages.
    Thanks for any help.

    Hi Christian,
    yes, you have to mainztain that port in idx1.
    First ypi load the rfc-metadata from an SAP referenzsystem and afterwards copy this metadata to the third party port.
    For further details check the onlinedocumentation "IDoc Processing with the IDoc Adapter" XI -> runtime -> adapter
    Good luck,
    Holger

  • Run Sender Communication channel for every 4Hrs

    Dear all,
    I have requirement to schedule sender CC in production for every 4hrs.
    We have option called daily but not hourly !!!
    Is it possible  to schedule sender CC like this for every 4hrs??
    Note: For Some reasons i can't increase the polling to 4hrs in sender channel to solve this issue
    Regards

    Bhavana,
    Found a solution. Create a unix script and run the command to start and stop the communication channel as per your requirement.
    Below is the syntax.  You can try using wget command or curl in unix followed by the below command
    http(s)://host:port/AdapterFramework/ChannelAdminServlet?party=party&service=service&channel=channel&action=action
    wget http(s)://...
    or
    curl http(s)://...
    check this link
    /people/william.li/blog/2007/05/04/control-communication-channels-externally-without-using-rwb

  • 5 Sender communication channels and 1 receiver channel

    My scenario demands to handle 5 different select queries from single data base.
    I need to have 5 sender communication channels for editing an employee and only 1 receiver channel at receiver side and i'm using one common Functional module to handle.
    Can i handle the above situation in one single interface??? like having 5 sender communication channel at sender side and 1 receiver communication channel at receiver side??
    Thanks
    LN

    like having 5 sender communication channel at sender side and 1 receiver communication channel at receiver side??
    Yes it is possible....if it is not possible for you to combine the query into one.
    How is the data to be processed? Is the data pulled by the 5 sender channels, to be merged into one target message? Is yes then you have to make use of a BPM.
    If the Data from 5 sender channels will be individually forwarded  to the receiver channel then there is no need of a BPM.

  • Regd Sender  Communication channel

    Hi all,
    I have configured a sender communication channel for picking a file. Everything looks fine to me, but the file is not getting picked up.
    I checked in RWB for channel, channel is configured fine.its says  processing started, and processing finished successfully.No message ID is showing.But the file is not getting picked from the location.
    In moni , no messages to display.
    can you suggest how to trace out the possible error? the path and file names are perfect, check it number of times.

    Hi Anika,
    in sender file comm channel, set the processing mode to delete and activate it.............
    then in source file system, ask the file system guys to check the file permissions of the source file........it should have read, write, execute for others............
    then your source file should be picked.........if still your source file is not getting picked, then ask your basis guys to do a full CPACache refresh using PIDIRUSER and then re-run your scenario......
    Regards,
    Rajeev Gupta

  • Why is a sender communication channel not required for IDOC and PROXY ?

    Hello,
    In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
    Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..)  when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
    Though this might be a regular question, I am not able to find a proper reason.
    Please let me know the reason for the above request.
    Thanks & Regards.

    You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
    But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
    Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
    Regards,
    Raj

  • Communication Channels for IDOC scenario

    Hi!
    I have a conceptual question regarding the communication channels within IDoc scenario.
    Case 1:
    - File_to_RFC scenario
    Here I defined a File communication channel from business system A.
    1a) For which system (business system A or B) do I need to define a IDoc communication channel?
    1b) What is the RFC destination and Port I need here?
    Case 2:
    - IDOC_to_IDOC scenario
    2a) Do I need in this scenario only one communication channel for business system A?
    2b) What is the RFC destination and Port I need here?
    Thank you very much!
    Thom

    >
    Thom Heinemann wrote:
    > Hi!
    >
    > I have a conceptual question regarding the communication channels within IDoc scenario.
    >
    > Case 1:
    > - File_to_RFC scenario
    > Here I defined a File communication channel from business system A.
    > 1a) For which system (business system A or B) do I need to define a IDoc communication channel?
    >  1b) What is the RFC destination and Port I need here?
    >
    in this case no IDoc CC is involved. All you need is a File sender adapter and RFC receiver adapter
    > Case 2:
    > - IDOC_to_IDOC scenario
    > 2a) Do I need in this scenario only one communication channel for business system A?
    >  2b) What is the RFC destination and Port I need here?
    >
    >
    > Thank you very much!
    >
    > Thom
    in this case you will need a IDoc receiver adapter only.
    The basic settings:
    In XI
    SM59 - R3 connection pointing to R3
    IDX1 - define the port with the above dest.
    In R3
    SM59 - R3 connection pointing to XI
    WE21 - define the port with the above dest.
    WE20 - Partner profile type outbound/Inbound
    Further ref:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

  • JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

    Hi All,
    Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
    I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
    If you know of any documentation regarding this, can you please post it?
    Thanks,
    Jay

    Jung,
    Are you looking for this help:
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    Also check this sap help:
    http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
    ---Satish

  • HOW TO CREATE SERVICE FOR SENDER SOAP COMMUNICATION CHANNEL FOR ECC PROXY

    Hi Experts,
    I need generate the service for sender soap communication channel for target url to receive the  inbound proxy.
    my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method .
    i am using SOAP sender and SOAp receiver communication channel .i need to provide the target url for this communication channel.
    how to generate the url for this and what is the transaction code .
    Please help us.
    Regards
    Ravinder.S

    Hi Ravinder,
    Q.my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method.
    SOAP to Poxy in this case.
    For sender  SOAP system, we can generate the WSDL link in ID part.
    for Reveiver proxy give the integration engine URL.
    http://IP:PORT/sap/xi/engine?type=entry
    how to generate the url for this and what is the transaction code
    There is no transaction code for generating the URL.
    i hope this will help.
    Regards,
    Kesava.

  • Clarification for HTTP and HTTPS Sender Adapter

    Hello together,
    after some investigating concering scenarios with HTTP and HTTPS sender there are still some points that are not absolutely clear for me.
    I know that it is not necessary to configure an HTTP sender communication channel. However if I want to enforce HTTPS sender communication I think I need to add an HTTP sender communication channel with security settings enabled as well as a sender agreement.
    To my understanding these settings are activated on the Adapter Engine (Java Stack), HTTP requests however call the ABAP stack directly. How does this work exactly?
    Thank you very much for your additional explanation.

    Hi,
    see below is the format for HTTP URL
    http://<hostname:port>/<path>?<query-string>
    now query straing can only have values as given in the below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    a way around can be to specify the payload for &party or &agency or &schema(if you are not using them) but then XI should be able to identify them correctly(which i m not sure how it will do),secondly the length can be a constraint coz if you add the whole payload ,the URL will become really long.
    so i would suggest you not to use it but if you really have to,then explore it properly first and then only use
    plz reward points
    thnq

  • Party communication channel for multiple stores with multiple user id and passwords in sap pi

    Hi Exeperts,
    I have a scenario proxy to SAOP . where i am sending some information from my stores to third party company   with single user id and password in communication channel.
    but requirement  is changed now  i have 20 stores  with 20 user id and password for communication channel.how can i achieve this requirement?
    Can i create 20 communication channels  for 20 stores  or can handle through the party based communication ?
    Please  help us achieve the requirement.
    Regards
    Ravinder.s

    Hi,
    In the SOAP Receiver adapter, you can only store 10 userid/password combinations via Authorization Keys. These are called via Dynamic Configuration via technical name TAuthKey. In your case, for it to work, you need:
    1. 2 business components/2 SOAP receiver communication channels.
    2. 1 receiver determination with xPath for username to determine correct business component
    3. 1 interface determination
    4. 2 receiver agreements (one for each cc)
    Hope this helps,
    Mark

  • Configuring a Communication Channel for an AE other than the default IS

    Configuring a Communication Channel for an Adapter Engine other than the default engine.
    See:  help.sap.com for Communication Channel http://help.sap.com/saphelp_nw04/helpdata/en/1b/d5ef3b1ad56d4fe10000000a114084/frameset.htm
    It states under 'Adapter Configuration', that you can specify the Adapter Engine you want to use in the Adapter Engine dropdown box.
    I have activated the XI components on my ERP system using transaction SICF, but what do I have to do to make the other adapter engines show up in the dropdown list when configuring an adapter?
    Maybe some background would be helpful:  This is for a scenario that will send a file from an external system to one of the ERP systems in our landscape.  BUT, the system admins have decided to revoke our FTP accounts (because they have their reasons), so I need to create a File Adapter that will drop the file on the file system of that ERP system, due to visibility I want to use the integrated Adapter Engine that comes with the ERP system, but need to know how/what I'm missing in setting up this scenario.

    Hi Anesh,
    >>>>but what do I have to do to make the other adapter engines show up in the dropdown list when configuring an adapter?
    in order to use some other adapter engine you
    have to install it first by dafault only one
    (central) adapter engine is used and it is all
    most clients need
    if you'd like to use some other adapter engine
    (decentralized for example) have a look at thid guide:
    <b>Configuring a Local Adapter Engine to Work with a Central Instance</b>
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • JMS Sender Communication  Channel problem

    Hi XI gurus!!
    I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
    In defaultTrace.XX.trc I see the following information and errors:
    #1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
    #1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
    {GenericConnectionProfileImpl
    {Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
    JmsMessageSelector=,
    ConnectionFactoryConstructor=null,
    ConnectionFactoryFactoryInvocation=null,
    ConnectionFactoryInvocations=[],
    DestinationConstructor=
    {ConstructorInvocation
    {className=null,
    invokeParams=[]
    DestinationInvocations=[],
    MessageInvocations=[],
    DestinationName=null,
    User=,
    Password=,
    isJmsSessionTransacted=true,
    InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
    LookupConnectionFactory=QueueConnectionFactory,
    LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
    SerializedConnectionFactoryPath=null,
    SerializedDestinationPath=null,
    Flags=0000000000000000000000000000000000000000000000000000100000000010
    #1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
    #1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    #1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
    Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
    BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
    Thanks

    HI,
    As per the trace details given please consider few of the below options....
    What do u see in adapter monitoring tool for JMS adapter?
    http://hostname:5XX00/mdt/amtServlet
    Did you follow the document on correlation of JMS messages?
    In communication channel You have to set
    Correlation ID -> XI conversationID
    XI message ID->GUID
    XI Conversation ID -> JMS correlation ID.
    Now in the custom J2EE application you should set
    jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
    This thread deals with the issue..
    JMS Queue monitoring
    Check  if the JMS Sender adapter EOIO is with serialized messages 
    Thanks
    Swarup

Maybe you are looking for