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

No Messages in integration server

Hi all,

I have configured the sender file adapter which picks up the file from file adapter and is sending it successfully to integration server. But i am not able to

see the messages in integration server using the transaction sxmb_moni. There are no messages at all.

here i am giving the log of the sender file adapter. Plz suggest.

15:40:08 (4001): File adapter terminated

  • Wed Jan 12 15:40:08 IST 2005 *****

15:40:08 (4012): "Guaranteed Delivery" operation for 2 file(s) pending

15:40:12 (4023): File adapter initialized successfully

15:40:12 (4007): File adapter started

15:40:14 (4029): Process 1 file(s):

15:40:14 : custbank.txt

15:40:15 (4030): Start processing "TXT" file "custbank.txt" size 18 in "EO mode

15:40:15 (4059): Start converting to XML format

15:40:15 (4061): Converted complete file content to XML format

15:40:15 (4062): Sending text message "277f23b1-6482-11d9-8369-d084ac190476" type "text/plain" to Integration Engine... (message size: 164 bytes, URL: "http://ht56f4:8000/sap/xi/engine/?type=entry")

15:40:15 (4037): "custbank.txt" sent to Integration Engine successfully

15:40:15 (4038): Confirmation complete. File deleted on FTP server "custbank.txt"

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 12, 2005 at 11:24 AM

    These are the xml messages with error.

    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

    - <!-- Receiver Grouping

    -->

    - http://sap.com/exchange/MessageFormat">

    - <SAP:serviceEntry version="20">

    <SAP:sender>PS_LEGACY</SAP:sender>

    - <SAP:outboundInterface>

    http://ps_crm.com

    <SAP:name>Customer_out</SAP:name>

    </SAP:outboundInterface>

    <SAP:receiver>BUS_SAP</SAP:receiver>

    - <SAP:inboundInterface>

    <SAP:nameSpace>urn:sap-com:document:sap:idoc:messages</SAP:nameSpace>

    <SAP:name>DEBMAS.DEBMAS03</SAP:name>

    </SAP:inboundInterface>

    - <SAP:address version="20">

    <SAP:systemKey>BUS_SAP</SAP:systemKey>

    <SAP:endpointType>IDOC</SAP:endpointType>

    <SAP:url>IDOC://SAPER2?RFCDEST=test&DOCREL=3.0&VERSION=3&SAPREL=620</SAP:url>

    </SAP:address>

    - <SAP:auth version="20">

    <SAP:authMethod />

    </SAP:auth>

    </SAP:serviceEntry>

    </SAP:TechnicalRouting>

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 12, 2005 at 10:34 AM

    Hi Sri,

    Are your filter settings correct in transaction sxmb_moni?

    Cheers,

    Frank

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 12, 2005 at 11:23 AM

    Hi Frank,

    thanks for your reply. Now i could see xml messages. But they are stucked there with error 'unable to determine the receiver'.

    I am using file xi idoc scenario in sap xi 2.0.

    1. I have defined both sender and receving systems as

    technical and business systems in SLD.

    2. I have completed all the dev. work in i.repos.

    3. I have configured both sender and rece. system in i.deirectory.

    can you plz suggest where could be the problem??

    Thanks in advance.

    Rgds,

    Sriram

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 12, 2005 at 12:55 PM

    Hi Frank,

    Thanks for your suggestion. i made some settings in integration directory and now they are able find the sender and aswell as receiver. But the messages are with error 'Meta data EDISDEF for port SAPER2, IDoc type DEBMAS03 and CIM type not maintained'.

    I went into idx2 transaction and able to see the idoc type

    debmas and client etc..

    Plz suggest.

    Regards,

    Sriram

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 13, 2005 at 07:17 AM

    Hi,

    Please make sure the port and RFC connection maintained in the receiver IDOC communication channel is exactly the same as maintained in transaction IDX1. If that is the case, you can remove the IDOC type in IDX2 and reassign the IDOC type again.

    Cheers,

    Paul

    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.