Integration Engine Persistance Layer Analysis

Folks,
These are the entries in Persistance Layer Analysis
<i><b>Current Table Load
      Number of Table Entries                                                 338,417
      Maximum Number of Table Entries                                         890,000
      Current Fill Level in %                       </b></i>                               38
Can anybody tell me how to increase the Maximum Number of Table entries ?
Records,
Manish

In case anyone else has this same problem, I asked SAP:
"This is only a theoretical value. This value was calculated by DDic. Depending on table size category, DB Hardware,etc. You can see this value by the table size category. ( Transaction SE11 (table e.g. SXMSPMAST) -> Technical Settings -> Sizecategory )
The description is:
The size category determines the probable space requirement for a table in the database.
You can select the categories 0 to 4 for your table. Each category is assigned a specific fixed storage area value in the database. When you create a table, initial space is saved for it in the database. If more space is required later as a result of data that has been entered, the storage space is increased in accordance with the category selected.
Press F4 on the field Size category to see the number of data records that can be maintained for the individual categories of your table without complications ensuing. These complications could be for example a reorganization becoming necessary because the maximum space to be
reserved for the table was exceeded due to the maintained size category."

Similar Messages

  • Persistance Layer Anaysis shows high percentage

    Hello Experts,
    The PI System is showing high percentage (500 plus) of usage in persistance layer analysis. Recently I encountered queue blockages with TIME_OUT exception as the records were not able to insert in the table SXMSCLUP.
    Can anyone tell me should I be worried about so much usage in the persistance layer? However, all the archiving and deletion jobs are running regularly.
    Thanks in advance,
    Anand Patil

    Hello Anand,
    What is current setting for Integration Engine's parameter DROP_MAX_TABLE_LOAD?
    Please also advise approx. amount of processed messages per day and retention period (you can check SAP Note 872388 for general calculation logic of DROP_MAX_TABLE_LOAD based on these two input parameters).
    What is approx. volume of processed messages?
    Did you follow the logic described in the mentioned Note (872388) for scheduling archiving/deletion jobs or some other considerations?
    In general, persistence layer should be cleaned on regular basis and since you observe exceptions when querying it, the attention for double-checking of current parameters for archiving/deletion jobs vs. persistence layer usage should surely be paid.
    My regards,
    Vadim

  • Persistence Layer Analysis

    Hi Experts,
         what do we check in Sxmb_moni - Integration Engine Monitering - Persistence Layer Analysis.
    and the utility of the tab - Status records for sync / async communication.
    Regards,
    Arnab .

    Hi Arnab,
    Status records for sync / async communication
    USE:
       You use the monitor for sync/async communication to display status information about persisted      messages where a coupling of synchronous and asynchronous processing has occurred.
    The status monitor for sync/async communication provides the following information as the default:
    ·        The number of active synchronous calls that are still waiting for a response
    ·        The number of processes with errors (synchronous calls) whose status has not yet been deleted
    ·        A table containing status information about the involved synchronous request messages
    The system displays the following status information:
    ¡        The overall status with a green, yellow, or red traffic light
    Activities
    In the status monitor for sync/async communication, you can execute the following activities:
    ·        Close all processes with errors.
    ·        Update the entire display by choosing Update in the application function bar.
    ·        Update the table of displayed messages by choosing Update in the table symbol bar.
    ·        Navigate from the list of displayed messages to the corresponding workflow log. To do this, click the message ID of the respective message.
    Regards
    Praveen K

  • Integration engine problem

    Dear All ,
    I am facing one problem related to file generation and pickup . In file to IDOC AND IDOC TO FIle SCENARIO PROCEESING IS NOT BEING DONE BY INTEGRATION ENGINE .
    When I am checking the status of message in SXMB_MONI
    IT IS SHOWING <b>"RECORDED"</b> , <b>it is not showing message " processed successfuly</b> . <b>It is also showing the message is waiting in queue "to be delivered ".</b>em .
    Can some body suggest how to remove this problIt was working fine IDOC TO FILE and FILE TO IDOC before this probelem occured .
    Thanks in advance
    Regards
    Prabhat

    Hi Prabhat
    Follow the steps mentioned in this link, it is a Problem Analysis Guide.
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    cheers
    Sameer

  • 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.

  • Interaction between Qout scheduler and Integration engine

    Hello,
    I would like to understand more about the XI 3 architecture regarding the place of qRFC. If I understood right, depending on the QOS, the qOUT scheduler is used to send XML documents comming from the Integration Engine. The qOUT scheduler is able to process and queue rfc calls using traditional RFC ports (for example in case of CIF for APO). I imagine that in the case of XML message shipping, the qOUT scheduler is  called by the Integration Engine messaging logic layer. But then, I don't understand how outgoing SOAP calls occure. Are the queued RFC calls in destination of the local SOAP framework which uses the ICM to talk SOAP with the partner?
    Thanks for your lights,
    Christian.

    Thanks Holger for youor quick and precise answer,
    You mean, that the connection between the adapter framework and the integration engine is pure rfc based and not Soap-based XI protocol ?
    Is XI protocol used between the two engines each time no qRFC is envolved and in this case, the Abap-based Soap framework and the ICM are used by the integration logic layer of the central integration engine to communicate with the adapter engine ?
    Thanks,
    Christian.

  • 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.

  • Error while testing message from Integration Engine.

    Hi,
    Trying to send message to Integration engine from RWB, using test mesage tab in Integration engine.
    I pasted the payload(IDOC payload) , entered sender service, interface name and namespace and also username and password. Selected quality of servie as Exactly once.
    While sending the message getting the following error - "Error while sending".
    What could be possible reasons for this error.
    Thanks.

    Hi,
       Please check the following possibilities:
    1. Make sure you have selected integration Engine oprtion and not the adapter engine.
    2. The USERID and password should be correct.
    Please let me know if you still face the problem.
    Regards,
    Shwetambari.

  • Java bean, works in Integration Engine but does not work in Adapter Engine.

    In connection to the following thread:
    PayloadZipBean - variable filename inside the archive
    I am trying to use the same bean.
    However I can see, that the bean is working correctly when I use Integration Engine.
    But if I am using ICo (AAE) and using the same bean in the receiver, I can see, that the bean gets called but does not work correctly.
    The audit log added to my bean shows, that the bean could read the filename correctly from the Dyanic Config in the message, but it cannot write the same into the message.
    Could you please help on this?

    Your above posted system details show multiple Java Console extensions.
    You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
    See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
    See also http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0
    Disable the Java Quick Starter extension: Tools -> Addons -> Extensions
    Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
    You can try a direct connection: <br />
    Control Panel > Java > General tab > "Network Settings...": "Direct Connection" (enable)

  • Bypassing integration engine in pi 7.0

    Hi
    Am supposed to work on bypassing the integration engine in case of file to Jdbc. Am working on version pi 7.0. How can I bypass integration engine ?

    hi,
    Am supposed to work on bypassing the integration engine in case of file to Jdbc. Am working on version pi 7.0. How can I bypass integration engine ?
    as per my knowledge(bypassing the integration engine in case of file to Jdbc) that is possiable from pi 7.1 by using ICO(AAE) concept only .
    thanks,

  • Problems with namespace XML Parsing of ABAP PI 7.0 Integration Engine

    Hi,
    I discovered the following problem.
    The customer sends a SOAP message with is forwarded through a SOAP Adapter in the integration engine.
    The structure of the message is very simple:
    <Envelope>
    <Body>
    <ORDERS05>...</ORDERS05>
    </Body>
    </Envelope>
    The customer adds the namespace information a special way:
    <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope">
    <Body>
    <orders05 xmlns="">...</orders05>
    </Body>
    <Envelope>
    Here the namespaces is declared in the first element. It should be inherited into all child elements. The 'orders05' should not have the namespace ' xmlns="http://schemas.xmlsoap.org/soap/envelope" ', therefore the namespace is overwritten with ' xmlns="" '. However I don't know if this is a correct xml statement, the SAP system did not understand this.
    The integration throws an error which is stated in the message in the adapter engine:
    2008-11-06 17:31:44 Fehler SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIProtocol/ITEM_MISSING; Params: /@mustUnderstand, ST: ST_XMS_MSGHDR30_RM; AdditionalText: Attribut 'mustUnderstand' erwartet; ApplicationFaultMessage: ; ErrorStack: Das XML-Element /@mustUnderstand fehlt im SOAP-Message Header (SAP XI Extension) Attribut 'mustUnderstand' erwartet
    2008-11-06 17:31:44 Fehler Fehler beim Übertragen der Message zum Endpunkt http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header
    If I changed the SOAP message to the common format, it is accepted by the integration engine.
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope">
    <SOAP:Body>
    <orders05>...</orders05>
    </SOAP:Body>
    </SOAP:Envelope>
    Here the namespace ' xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope" ' is defined with a prefix and assigned to the elements 'envelope' and 'body'. The 'orders05' element has no namespace.
    However due to the xml syntax both messages are the same, so why the integration engine handle the messages different?
    Best regards,
    Nils Kloth

    The valid SOAP format supported by XI is as follows
    <SOAP:Envelope
      xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Body>
        <m:MessageTypeName xmlns:m="Some-URI">
          <Price>34.5</Price>
        </m:MessageTypeName>
      </SOAP:Body>
    </SOAP:Envelope>
    Ur sender system is not sending the data in correct Soap format and thats the cause of message rejection. The option you have to use the Soap adapter in "no soap" mode.
    Regards,
    Prateek

  • Error in integration Engine

    Hi All,
    In integration Engine im getting error as "Exception occurred during XSLT mapping of the application".
    when i tried to test the mapping its showing the warning as "javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: Could not execute operation on Java Object. -> java.lang.reflect.InvocationTargetException at "
    Please help me reagrding this issue to proceed further!!!

    Hi,
    Can u please explain the problem little detail...
    Are u getting this error in SXMB_MONI??
    If yes then can u copy the source payload and check it in the Message Mapping once??
    If problem is coming from mapping... try to analyze.. else u can put now vtz exactly the prblm is..
    Babu

  • HTTP error 403 from Integration engine

    Hello,
    Problem a)
    While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
    The error message states:
    ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
    Problem b)
    In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following 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.net.ConnectException: Connection timed out: connect.
    I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
    It looks like these error due to security reason, it seems some authorization profile is missing or may be some other issue,kindly help us at that front.
    Thanks and Regards,
    Satish

    Hi Suraj,
         Thanks for the update.We had checked the URL before posting this message,it is picking up correct URL with namespoace, UID and PWD.Exact error that we are getting is as follows:
    ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=pisuper&sap-password=sap$29&sap-client=001&sap-language=EN. Please contact your system administrator.
    Here all information are correct.We have checked the SLD check, that is also working fine.Also it is not connectivity related issue, as we are able to transmit XML file to E-Sourcing.
       It looks like security issue, but what authorization needs tobe given exactly for HTTP call, we need to know or may be some other issue.
    Thanks and Regards,
    Satish

  • HTTP error 403 to Integration engine

    Hello,
    Problem a)
    While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
    The error message states:
    ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
    Problem b)
    In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following 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.net.ConnectException: Connection timed out: connect.
    I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
    Please help.
    Thanks and Regards,
    Himadri
    Edited by: Himadri Chakraborty on Feb 9, 2010 3:35 PM

    Time Out Error
    In order to get rid of it, Your basis person need to play around with follwing three parameters in order to find an appropriate values as per your hardware sizing and requirement......
    icm/conn_timeout
    icm/keep_alive_timeout
    icm/server_port_< n >
    How ever, in general SAP recommandation is as follow....
    icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600 to allow a maximum processing time of 10 minutes.
    Hope this helps !!!
    Regards,
    J Augastine

  • Mail-Adapter Integration Engine Error during parsing of SOAP header

    Hello,
    we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
    Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
    ?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
    pi.RecoverableException: Received HTTP response code 500 : Error during
    parsing of SOAP header.
    Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
    due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
    response code 500 : Error during parsing of SOAP header.
    Retries exceded, set message
    4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
    Has somebody else the same problem and solved it or any idea what the matter could be?
    Thanks for your help
    Christian

    Hi Reddy,
    We´ve got the following scenario:
    Exchange-Server (is always up)
    XI Mail-ReceiverAdapter
    I use IMAP4 to access the Outlook-Email-Box
    Everything works fine. But some Emails aren´t processed.
    I think it´s a problem between adapterframework and the integration engine?
    There is no difference between the emails?
    If you´ll need further informations ask me?
    Thanks

Maybe you are looking for

  • HDMI output not working with AT 200 under ICS

    Hello, I connected the HDMI output to a Sony KDL 32 E 5500. It simply does not work. The same TV HDMI input works fine with a DVD player. The AT 200 tablet is under ICS (upgrade in France). I tried both HDMI configurations : full screen and video win

  • Is there any way to retrieve deleted photos if they weren't backed up?

    Please please these photos are so important.

  • Dns resolve some website slowly

    Dns is resolving a lot of website quickly, but there are some websites like cnn.com , bbc.com take around 15 second to resolve the host name , I used nslookup then ping cnn.com and bbc.com and then take time also . I have 2 dns , and I have 3 dns for

  • Update for itunes

    I tried changing from 16 also it did not help. I get deep base and hardly any other sound, I also tried to un in stall and re in stall, no luck. Is there a patch out there to help us with this problem?

  • Netflix error on itouch

    my netflix will not launch on my itouch. i just get an outbound failure to connect message. i've tried to delete and re-download the app with nothing. i evem went as far as doing a restore. anyone having this issue and can offer some advice?