PI 7.1- Message going thru Integration Engine

Scenario:
ECC<-----SoapAdapter(Synch)> PI7.11 <JDBCAdapter(Synch)--
>OracleDatabase
Use of Local Processing required in this project.
I've successfully completed Design work and then completed Integrated Configuration (all those tabs, Inbound processing, Receiver, Receiver Interfaces, Outbound Processing look correct)
Then I did the ABAP backend communication on the ECC side
(SM59-RFC Destination to point to AAE,
then SXMIF - defined Sender Interface,
then sxmb_adm - IE Engine Config.-->Specific Config where I added IS_URL.
Ran my test from ECC. It is still going thru IE engine and cannot find receiver.
What am I doing wrong? Please advise...

I did.
In SXMSIF,  I only created a sender ID (named it, RECONREPORT) where I
Left Agency and Schema blank
Party and Service: put *
Request - Put my Sender Interface and Sender namespace
Then in SXMB_ADM-->Specific config.
I created a new entry of
Catogery: Runtime
Parameters: IS_URL
Subparameter: I copied the text of Sender ID from SXMSIF and pasted it.
Current value: dest://AAE_PEH
on a different note, in SM59 I have
RFC Destination: AAE_PEH
Target host: put my java host
Service no: put my java port here.

Similar Messages

  • PI7.11 - Still going thru Integration Engine and Can't find Receiver

    Scenario:
    ECC<-----SoapAdapter(Synch)> PI7.11 <JDBCAdapter(Synch)--
    >OracleDatabase
    Use of Local Processing required in this project.
    I've successfully completed Design work and then completed Integrated Configuration (all those tabs, Inbound processing, Receiver, Receiver Interfaces, Outbound Processing look correct)
    Then I did the ABAP backend communication on the ECC side
    (SM59-RFC Destination to point to AAE,
    then SXMIF - defined Sender Interface,
    then sxmb_adm - IE Engine Config.-->Specific Config where I added IS_URL.
    Ran my test from ECC.  It is still going thru IE engine and cannot find receiver.
    What am I doing wrong?  Please advise...
    Edited by: Maurice Gonsalves on Dec 8, 2010 2:53 AM

    I did.
    In SXMSIF,  I only created a sender ID (named it, RECONREPORT) where I
    Left Agency and Schema blank
    Party and Service: put *
    Request - Put my Sender Interface and Sender namespace
    Then in SXMB_ADM-->Specific config.
    I created a new entry of
    Catogery: Runtime
    Parameters: IS_URL
    Subparameter: I copied the text of Sender ID from SXMSIF and pasted it.
    Current value: dest://AAE_PEH
    on a different note, in SM59 I have
    RFC Destination: AAE_PEH
    Target host: put my java host
    Service no: put my java port here.

  • Auto Cancellation of Messages in the Integration Engine.

    Dear all,
    Issue: Auto Cancellation of Messages in the Integration Engine.
    Description: Actually Today, I'm facing Problem in message mapping and its showing error "JCO_SYSTEM_FAILURE". Finally the message is Auto Canceled and showing the status in the Message Monitoring as Canceled with Errors.
    I have doubt here how the messages are Auto Canceled with Error? Is there any system or ABAP program which cancelling these messages?
    Waiting for yours valuable reply on the above issueu2026
    Edited by: BhavinPatel on Oct 7, 2010 8:15 AM

    Hi Bhavin,
      Two report program are there to cancel error msgs automatically..
    1) RSQIWKEX
    2) RSXMB_CANCEL_MESSAGES
    Regds,
    Pinangshuk.

  • Message ID in Integration Engine and Adapter Engine

    Hello,
    I have one question related to messages generated in XI.
    Is the Message ID specified in the Integration Engine same as the Message ID used during the Message transformation in the Adapter engine?
    What is the message flow once the message reaches XI and vice versa?
    Regards,
    Gajendra.

    Yes.it is the same ID used .
    once the message reaches XI it goes thorough IS which has pipe line steps such as inbound processing receivr determination ,interface determination, techincal routing,mapping,outboundporcessing etc.
    for more look at this link
    http://help.sap.com/saphelp_nw04/helpdata/en/01/d9d43fb9490c65e10000000a114b1d/frameset.htm

  • Large Messages fail on Integration Engine

    Hello Guys!
    I have an integration scenario with <b>large</b> messages going from ECC to XI (RFC -> XI -> JDBC) and these messages frequently fail on Integration Engine (inbound queue SYSFAIL).
    1) Can't XI process large messages?
    OR
    2) Is there an integration engine configuration parameter that limits message size? (<i>I think that's not the case, because sometimes I can manually restart a message that failed on a first attemp</i>)
    OR
    3) Is there an integration engine configuration parameter that limits processing time of a message?
    Thanks
    Julio

    Hi Julio,
    i think you can click on the sysfail to get more info. Check as well SM21 for the error. Assumedly it was too much for Java Runtime and you should find a temporary down destination AI_RUNTIME_JCOSERVER.
    SAP note 723909 shows how to tune JVM and increase Java Heap Size.
    You should control if more than one msg leads to the error. If that is the case, may be a simple change of QOS to EOIO could solve the task to avoid more than one msg processing parallel. Reducing parallel JCO server threads would be similar strategy.
    A direct Java Maping could be another idea. Message Mappings will be generated to Java with a quite huge source code, a direct written mapping could be more performant / stabil.
    Regards,
    Udo

  • How to retrive the old messages in sxmb_moni (integration engine)

    Hi Expert,
    We were trying to call RFC and send some messages through XI. Due to some connection issue the message was failed in integration engine(MONI). As this messages had failed last week. We are not able to see the messages in MONI.
    Now we wanted to get the payload of the messages which had failed.
    Can you please suggest how can we see those messages and get the payload which is now not visible in MONI.
    Thanks in advance.
    Thanks,
    Nutan Champia.

    Hi All,
    Thanks for your response. I am able to see some messages in the mentioned table but I am not able to open those messages in MONI with the message id given in the table SXMSPMAST2 (SXMSPMAST) and SXMSPHIST to get the payload. (I have given date selection critaria as 1st of Nov 2011 till date). As this is very important for us would you please help us.
    Hi Venkata Ramesh,
    So if I have correctly understood you, then you mean to say that these messages which is not visible in moni we can not retrive the payload.
    Would you please help me to understand where can we see the settings to mention the number of days for which these messages should appear in MONI. (So that we can increase or can see the current settings for our project)
    Thanks
    Nutan

  • No message reach into Integration Engine ...

    Hello,
    I have following problem. I send message to XI through SOAP adapter. But the message doesn't reach of Integration Engine. It is delivered into Adapter Engine and then it stays in status "Waiting". When open message detail in RWB I get these information:
    Message Data
    Attribute     Value
    Engine     Adapter Engine
    Status     Waiting
    Repeatable     Yes
    Cancelable     Yes
    Start     29.08.2008 12:14:59
    End     29.08.2008 12:14:59
    +Sender Party     +
    Sender Service     BS_GetSupperior
    Sender Interface     http://sntcz.cz/xmlns/holidays
    MI_Holiday
    +Receiver Party     +
    +Receiver Service     +
    +Receiver Interface     +
    Quality of Service     Exactly Once
    Error Category     XI_J2EE_ADAPTER_XI_HANDLER
    Error Code     GENERAL_ERROR
    Message     55C9628075B311DDABE200301875333B
    +Reference     +
    ... and in defaultTrace file occures this message:
    #1.5#00301875333B0057000000DE0000109C00045596D2CD72D8#1220006176812#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XISUPER#18255d00759d11ddc1a500301875333b#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#
    #1.5#00301875333B004B0000009D0000109C00045596D2CE9B64#1220006176890#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#XISUPER#2919##srvbr05_NW4_2798750#XISUPER#ecff64f075af11dda90200301875333b#XI SOAP[BS_GetSupperior_SOAP/BS_GetSupperior/]_2449##0#0#Error##Plain###no message ID available#
    #1.5#00301875333B0049000001270000109C00045596D3111C00#1220006181250#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#sap.com/com.sap.xi.mdt#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#XISUPER#2920##srvbr05_NW4_2798750##f03f74c075af11ddb4ce00301875333b#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###enrichMessageData(): Error during retrieving the end-to-end-monitoring information
    Thrown:
    com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception:
         at sun.reflect.GeneratedConstructorAccessor358.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
         at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:82)
         at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
         at com.sap.aii.rwb.endtoendmonitoring.util.PMI_PortType.sxmb_Get_Pmi_Info(PMI_PortType.java:28)
         at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:965)
         at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:762)
         at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:568)
         at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl0.getPureMessageList(MessageMonitoringObjectImpl0.java:1016)
         at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1772)
         at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:354)
         at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:744)
         at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:552)
         at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:657)
         at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:810)
         at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1254)
         at jsp_monitor_new1219936385390._jspService(jsp_monitor_new1219936385390.java:9)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
         at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    If I try to send message to XI directly through HTTP adapter the message is not delivered into Integration Engine.
    Do you have any idea what to check or where could be problem?
    Thank you in advance for every advice!
    Best regards,
    Zbynek

    Hi Zbynek,
    I think the problem is in the structure of the xml you want to send. I mean, that the structure of the message you are sending by means of SOAP adapter is not the same that the structure in the Inegration Repository.
    When you test your message with a wrong BS it is sent to the IE and you can see this message in sxmb_moni with error status. It`s obvius, there is no configuration for this scenario. However if you test your scenario with right parametes but the content (xml structure) is wrong, the step when the content of the call is converted to the structure of the IR will fail. And the message doesn`t get the IE.
    So check the content of your call.
    I hope it is useful for you.
    Regards,
    Carlos

  • Change status for 18 million messages in the Integration Engine

    Hello there!
    I have the following situation and I wonder that maybe you could help. Currently I have more than 18 million messages for the BC_XMB object in the Integration Engine for a BI System (connected to a PI system).
    The problem here is that the archiving/deletion jobs in this BI system are faulty since maybe a couple of years ago and all of these messages are marked as "Archivable":
    What I'm trying to do here is to change the status for these 18 million messages from "can be archived" to "to be deleted" since there is no way that I can archive this 18 million messages (filesystem capacity). I've been looking many option but I cannot figure out how to do it.
    Maybe, if you know an alternative way to do this, I will be very pleased to hear it.
    Thanks a lot in advance.
    Carlos

    Raghu.
    I've done the following:
    1. I've executed SE38 tx code.
    2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
    3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
    4. There are no available variants, so I clicked on the "Execute immed." button.
    5. The job starts. I can monitor it on the SM37 tx code.
    6. It only deleted 20 messages.
    What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
    what do you think of it??
    regards
    Carlos.

  • Message Flow in Integration Engine

    Dear Friends,
    Kindly can someody share  how the message is flowing in Intergration engine after the message taken from Adapter engine.
    If you have any block diagram it will be helpful for me

    Hi Karthik,
    There are 6 stpes for the message processing thats only called
    PIPELINE Steps.
    what are all the steps involved in the Pipeline processing.
    Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
    XI pipeline steps are:-
    ->Sender Agreement
    ->Receiver Determination
    ->Interface Determination
    ->Interface Mapping
    ->Receiver Agreement.
    When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
    1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
    2) Interface Determination: For each receiver determine which interface will should receiver the message.
    3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
    4) Message Mapping: Mapping to transform the source message to destination message format.
    5) Technical Routing: Bind a specific destination and protocol to the message.
    6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
    One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
    message flow in XI
    The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
           The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
    Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
    ONWARD JOURNEY:
    Fig1. Message flow from Adapter Engine to Integration Server
    1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Here creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
    2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
    3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
    4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
    5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
    6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
    7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
    8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
    Fig2. Audit Log of message during onward journey
    RETURN JOURNEY:
    The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D
    br>
    Fig3. Message flow from Integration Server to Adapter Engine
    1.     When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.
    2.     As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.
    3.     The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.
    4.     The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.
    5.     The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D
    6.     The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.
    7.     The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD.

  • Message stuck in Integration engine

    Hi,
    I have a very simple file to file scenerio.
    I am sending a file from SAP system to Non Sap system and archiving the file later.
    My file is getting archived but its not reaching the destination.
    When I check it in the Run time workbench, it says WAITING status in Integration engine.
    I don't know why it is taking so long, my polling interval is 10 mins.
    And in SXMB_MONI it says that it is in the queue.
    Regards,
    Lokesh

    but in smq2 my queue XBTO2___0000 has 643 enteries and its in a running state for really long time.
    If not production, then delete the first message in the queue (if it is not getting re-processed)
    For DEV/ TEST encironment you can even delete the queue, if the stuck messages can be ignored (not to be processed).
    Regards,
    Abhishek.

  • Message Duplication in Integration Engine

    Dear all,
    We have issue in one of our PI Production Servers.
    It is an inbound interface, Idoc flat files are being picked up by PI and are converted into proper SAP Idocs by ABAP Mapping.
    In this case, messages are getting duplicated and SAP Idocs of previous messages are getting copied in the subsequent messages.
    In the duplicated messages, we have observed that,
    1. In SXMB_MONI, some pipeline steps are not getting displayed when compared to the successful messages.
    Successful Message, Pipeline Steps
    Inbound Message ( CENTRAL )
    Receiver Grouping
    Call Adapter
    Duplicated Message, Pipeline Steps
    Inbound Message ( CENTRAL )
    Receiver Grouping
    Request Message Mapping
    Response
    The converted message is having multiple entries of   <?xml version="1.0" encoding="UTF-8" ?>
    Will this help out in tracing the issue.
    Regards,
    Younus

    hi Younus Mohd ,
    the tool itself does not duplicate messages. you should chech 2 thing.
    1) if the flat file is not greater than 1000 segments
    2) test your abap mapping in a dev enviromentto check why the mapping fails with the file.
    Thanks
    Rodrigo P.

  • Message Monitoring Tool in RWB for Integration Engine Messages not working

    Hi all
    We currently work on a Pi 7.11 system. I f we start the runtime workbench and going to the message monitoring, we want to get in to a message in the integration engine.  Normaly we should get the same sxi_monitor in the web browser, but we only get the soap envelope. The pipeline steps on the  left side and also the payload cannot be seen.
    We increased the rights of the user to sap_all but this did not changed anything. We also implemented the J2EE monitoring rule.
    Seems to me as we forgot a setting after installation, but which??
    Thanks in advance for  your help.
    Oliver

    Hi Oliver,
    I work on PI 7.0 and I know it's very different from 7.1x releases, but your problem sounds like a similar "problem" on 7.0.
    Is your message sycronous? At PI 7.0 the default configuration is defined to remove the payload of sync messages. You can change it on JAVA Visual Administrator.
    Try to find this parameter in Java Visual Administrator and set it to "false", below you will find the PI 7.0 path to this:
    Server >> Services >> SAP XI AF Messaging >> messaging.syncMessageRemover.removeBody
    I hope it helps,
    Marcelo Vieira

  • Message Version option in Message Monitoring(integration engine)??

    Hi All
    While Message Monitoring in Integration engine, when i was checking the message contents in audit log i found a small drop down at the top saying "message version" which has version 0, version 1......
    Not all messages were having the same versions, some were having 2 some 8.
    What is this Message version option???
    Any information on this will be appreciated.
    Regards
    Jabbs

    hi,
    >>>What is this Message version option???
    have a look here
    http://help.sap.com/saphelp_NW04/helpdata/en/c9/775b3b82646c3ae10000000a114084/frameset.htm
    basically it lets you compare xml message after each pipeline step
    Regards,
    Michal Krawczyk

  • How to delete / cancel messages in PI adapter engine

    Hello expert,
    we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
    Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
    seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
    My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
    Thanks
    Jayson

    Hi Team,
    I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                          RSXMB_CHECK_MSG_QUEUE" and manage  to delete few entries.Could you please suggest how to reduce fill level to below 100%
    Switch Procedure (for Persistence Tables) Deactivated
    Number of Table Entries                                                           
    3.185.992
    Maximum Number of Table Entries                                                   
    830.000
    Current Fill Level in %                                                           
    384
    Threshold value for fill level for executing a switch run in %                    
    60
    Number of Logically Deleted Table Entries                                         
    0
    Decline of Fill Level in % Following Deletion                                     
    384
    Delete or archive processed XML messages
    Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
    Date       Time     Message text                                                                               Message class Message no. Message
    13.03.2013 06:39:55 Job started                                                                                     00           516          S
    13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
    13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
    13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
    13.03.2013 07:28:00 Job finished                                                                                    00           517          S

  • Split Mapping message IDs in Adapter Engine

    Hi Experts,
    I have to get the message ID of all messages from adapter engine where these messages are created as a result of a split mapping.
    I only have the inbound message ID in integration engine. Is there any place where this correlation is maintained.
    Regards,
    Ravi.

    hi,
    Check out this blog also:
    /people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
    Rgd, Adapter Engine:In general
    http://help.sap.com/saphelp_nw70/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
    Message Flow for some extent:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
    hope this may help you,
    regards,
    srinivas

Maybe you are looking for