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.

Similar Messages

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.

How do I turn on my wireless keyboard and make it 'discoverable'? I got a message that the batteries were low, so I changed them for new ones and now the keyboard doesn't work.

I got a message saying that the batteries were low, so changed them for new ones and now the keyboard cannot be 'found'. There seems to be no way to turn it on and make it 'discoverable' to the system. At the moment I'm typing this on a spare keyboard plugged into the back of my mac via a USB. Please help!

Have you checked to make sure the batteries are inserted the correct way? Have you tried to turn it on by pushing the right upper (round) edge of the keyboard - if you do that, do you see a tiny little green light? Since you have a wired keyboard, can you get to the Bluetooth setup/preference pane so you can manually try to sync the keyboard?
PS - posting duplicate posts is not helpful - it makes things too confusing, so I've asked the hosts to remove your other (identical) post.

Messages "to be delivered" at the integration Engine

Hi
Since Yesterday, we have a lot of messages with the status "to be delivered".
I have checked the SMQ1, the SMQ2 and nothing is there, but I saw 2 entries in SM58, blocked.
I deleted those entries but the system is still not working.
SMQR is showing the process as "inactive", and if I do not start it manually, it does not start automatically, but even starting it manually, nothing seems to happen.
I am unable to delete the firtst message that stays "to be delivered" its status is Cancelable No, Repeatable No.
The messages are in the Integration Engine.
I checked with no luck:
- Register Queues and Activate again the Queues
- Transaction SLDCHECK shows everything Ok
- AI_DIRECTORY_JCOSERVER , AI_RUNTIME_JCOSERVER and INTEGRATION_DIRECTORY_HMI seem to be Ok
- Stop and Start the SAP
- Refreshing the Cache
what else to check?
many thanks

Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords

What messages does it shows the integration engine(sycn/ asyn)?

What messages does it shows the integration engine(sycn/ asyn)?

Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords

XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

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.

Registration of Business system for the Integration Engine Java in the SLD issue

Hi,
We have completed the installation of PI-AEX 7.4 SR1 then we ran the below wizards successfully.
- Configuration Wizard: PI-AEX initial setup
- Configuration Wizard: PI Self Test for AEX
However when we were Checking the AEX Configuration as per help.sap.com
Check the registration of a business system for the Integration Engine Java in the SLD:
    Enter https://<host>:<port>/sld .
    Choose Start of the navigation path Business System Next navigation step Integration Engine Java <SID> Next navigation step Integration End of the navigation path.
    The pipeline URL must be: http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet?ximessage=true .
More information: SAP Note 1435392
for us the Pipeline URL is as below
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
and the rest " ?ximessage=true " is not there.
Also we ran the below wizard
Configuration Wizard: PI Self Test for AEX
and it finished successfully without any issue.
Any Suggestions what could be missing.
Thanks,
Regard
Ahmed Mohammed

Hi,
I found the below SAPNOTE which confirms that the Pipeline URL should be
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
1564449 - PI CTC Wrong Pipeline Url after AEX Initial Setup
However on help.sap.com it is different.
Any one experienced the same ?
Regards
Ahmed Mohammed

MTOM support in the integration engine

Hi,
Short description of the process.
3rd party application -> PI WSDL -> SAP ERP
A 3rd party application sents a request to our WSDL on PI and the PI
starts a process (BPM). After the process is finished, PI sents the
result to SAP ERP over XI adapter.
Because the 3rd party application cannot add authentication parameters
for our Web Service we changed our URL to a service in SICF.
sap->xi->engine and added default authentication parameters. So that when the 3rd party application sents a request to PI, PI will not ask for
authentication.
(this
thread explains the problem with authentication and why we did used the
SICF solution. first entry by Michal Krawczyk)
Now, when the 3rd party sent a message (SOAP message with MTOM) with
attachment it is recognized by PI as a Multipart message.
The Service in SICF which gets executed when the message comes calls a
class inside. (cl_xms_http_handler) This class gets an exception while
parsing the MTOM enabled message. And it does not sent the message to the
PI engine.
Is the MTOM feature supported by this class? If yes, what may be the problem.
Thanks.
Sample MTOM Message:
--MIMEBoundaryurn_uuid_B7A0A8F29AF9AF0E5F1285180614419
content-type: application/xopxml; charset=UTF-8; type="application/soapxml"
content-transfer-encoding: binary
content-id: ïş
¢Sr ñ Fu02C6...
MIMEBoundaryurn_uuid_B7A0A8F29AF9AF0E5F1285180614419

Moved to Axis adapter which solved our problem

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.

Configurate the integration engine of an R/3

hi experts!
I need to configurate the integration engine of an R/3 receiver .... ( R3 SENDER>XI-->R3 RECEIVER )....in order to be able to see aynchronous messages (corrects an incorrects) and asynchronous messages (corrects), and honestly speaking i don't know hot to do it or the values that i have to chose.
the parameters that I have, are this:
ARCHIVE----
PERSIST_ARCH_MANUAL_CHANGES
ARCHIVE--PERSIST_DURATION--
ASYNC
DELETION-----PERSIST_DURATION--
ASYNC
DELETION-----PERSIST_DURATION--
SYNC
DELETION-----PERSIST_DURATION_ERROR--
SYNC
DELETION-----RELATED_OBJECTS--
ASYNC
DELETION-----RELATED_OBJECTS--
ROWS
DELETION-------ROWS_PER_LOOP
HTTP_PLAIN----SUPPRESS_URL_PARAMETER
IDOC----
EXTERNAL_MAPPER
IDOC----
SYNTAX_CHECK
IDOC----
XML_CONVERSION
MONITOR----
CCMS_MONITORING
MONITOR----
QRFC_RESTART_ALLOWED
PERF----
DAYS_TO_KEEP_DATA - -
AGGREGATION_ITEM
PERF----DAY_KEEP_DATA -
MEASUREMNT_ITEMS
PERF----
MAX_ENTRIES
PERF----
MEASUREMENT_LEVEL
PERF----
MEASUREMENT_PERSIST
RFCADAPTER----LOGGING
RUNTIME-------ACK_SYSTEM_FAILURE
RUNTIME-------CACHE_DIRTY_READ
RUNTIME-------ENGINE_TYPE
RUNTIME-------ENTRY_LOCK
TUNING----
EO_OUTBOUND_PARALLEL
TUNING----
EO_OUTBOUND_PARALLEL_SPLIT
TUNING----
IS_RETRY_LIMIT
and my actually configuration is this:
ARCHIVE    PERSIST_DURATION          ASYNC   2        1
DELETION   PERSIST_DURATION          ASYNC   2        1
DELETION   PERSIST_DRATION            SYNC     2        0
DELETION   PERSIST_DURATION_ER    SYNC     2        1
MONITOR    CCMS_MONITORING                        1        0
MONITOR    QRFC_RESTART_ALLOWED             1        0
RUNTIME    ENGINE_TYPE                         LOC UNDEFNED
RUNTIME    IS_URL                                        des:/XID
THANKS...

Hi,
What you are searching for is only about RUNTIME category parameters. Try changing parameters LOGGING (for async) and LOGGING_SYNC from default to 1. You can also try some other parameters, you can search for the documentation for each one or just changing and testing.
ACK_SYSTEM_FAILURE
ACL_CHECK
CACHE_DIRTY_READ
CACHE_REFRESH_PACKAGE_SIZE
ENGINE_TYPE
ENTRY_LOCK
ERROR_ON_NO_RECV_FOUND
HTTP_TIMEOUT
IS_RFC_DESTINATION
IS_URL
LOCK_MESSAGE
LOGGING
LOGGING_AMF_ERR
LOGGING_PROPAGATION
LOGGING_SYNC
PACKAGING
QUEUE_COUPLING
RFC_DEST_QUEUE_COUPLING
TRACE_LEVEL
TRACE_LEVEL_PROPAGATION
regards.
roberti

Using the SOAP inbound channel of the Integration Engine

Hi,
I am following the blog of Stefan Grube.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
However I have difficulties.
Is this blog still relevant for SAP PI7.10?
I have set this up as a test for a scenario I have.
Current Scenario NOT using your Blog and working perfectly.
SandBox PI       Development PI
File > SOAP >   SOAP > ABAP Proxy
What I am attempting now is.
SandBox PI      Development PI
File > SOAP > Integration Engine > ABAP Proxy
I am using our SAP PI Sandbox to push a SOAP message using a Receiver SOAP adapter channel.
Transport Protocol: u201CHTTPu201D
Message Protocol: u201CSOAPu201D
Conversion Parameters:      u201CDo not Use SOAP Envelopeu201D
Target URL: u201Chttp://<Integratio Server Host Development PI>:<Port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=FigmentD&Interface=urn:figment-co-za:fleetcard:efuel_50ppm^oa_Msg50ppm&QualityOfService=ExactlyOnce&sap-user=<PIAPPLUSER>&sap-password=<PASSWORD>u201D
SOAP Action: u201Chttp://sap.com/xi/WebService/soap1.1u201D
I am however getting the following error on the SandBox Pi AE.
u201CSOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 MOVED TEMPORARILYu201D
Please can you assist in this matter.
Regards
Willie Hugo

Hi williem,
Stefans weblog works great. The error you are getting is some wrong data you are sending. Please verify the data you are sending is correct. Also check this threads for the same errror:
ADAPTER.HTTP_EXCEPTION / HTTP 302 Moved Temporarily
Re: SOAP client receives HTTP 302 Found
Re: Synchronous RFC-XI-Web Service with no request method
HTTP Error (302) Found when calling Web Service on XI
Regards,
---Satish

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

How to call the integration engine not the remote function.

Hi!
I want to get the data from the client 000 with an rfc call through the xi (client 001). But when I call the function via rfc, the funciton is executed in the client 001, instead of forwarding the call to the integration engine.
How can I forwarded to the engine this call?
I only made a sender communication channel in the DI which is an sener adapter type RFC.

Thanks for the reply.
But I have no receiver channel yet. so i can't even reach any server if my call would be catched by the intergration engine.
But unfortunately I can reach the target system without the engine.
I use java connector to connect the external system to my intergration server.
Please help.

Atack interface directly in the integration engine

Hi guys.
Id like to know how to make to consume a sender interfece directly attacking the integration engine.
We work with an EDI enterprise and we only provide them the interface XSD, inteface name, interface namespace, remote user and password and they achive to consume this inteface but I don't know how.
There isn't any sender channel assoicate to this sender interface...
How could they get this? Java?
Thanks a lot!!!

Hi,
You can directly post to integration engine from your EDI using the below URL if thats what you are looking for.
http://<host>:8000/sap/xi/adapter_plain?namespace=<ns>&interface=<intface>&service=<BS>&QOS=<EO>&sap-client=<003>&sap-language=<EN>&sap-user=<user>&sap-password=<password>
This would be a direct HTTP communication and no sender channel is required. its served by the integration engine itself.
please check
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
regards,
francis

I wanna ask you something. My bro has an iPhone 5s that disabled for 23 million because of the time changed to 1976. So, how to make it back into 2015, make it enabled without erase the data

I wanna Ask you something. My brother has an iPhone 5s that disabled for about 23 millions minutes the time changed to 1976. So how to make it back into 2015 without waiting for 23 millions minutes later and enabled it without erasing any data? Please answer me ASAP because I really need it. Thank you for answer!

Hello theshadowhunters,
There is not much you can do to change the time back because he will not have access to change the time. The only option to get passed this is to restore the iPhone. Once the iPhone is restored and have a back up, you can put that back on once the restore is complete. For more information, take a look at the article below.
Forgot passcode for your iPhone, iPad, or iPod touch, or your device is disabled
https://support.apple.com/en-us/HT204306
Regards,
-Norm G.

Change status for 18 million messages in the Integration Engine

Similar Messages

Maybe you are looking for