Pipeline Entry

Hi,
I was reading through some XI materials and it mentioned about the Pipeline entry being accessed via
http://<host>:<port>/sap/xi/engine?type=entry
I went to check it out and saw that its just a webpage.
I just want to find out about the usage of the URL.
Im guessing the URL might be used by a httpclient when it sends a message straight to the Integration Engine?

Hello,
This is the link used by adapters for sending the requests to Integration Engine for serving the requests ,you can send the request to the same by using http client also even though HTTP resides on ABAP stack (not a part of J2EE adapter list)
Regards
Rajesh

Similar Messages

Pipeline entry error.

Hi ,
I am sending the data to the web service from the xml spy.
the message is failing in XI .
I checked the RWB audit log and the error is
Transmitting the message to endpoint http://xxxx:50000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not Found.
the J2ee (http) port is 50000
and the R3 HTTP port is 8000.
In the SDL the business system of XI has the pipeline address with the port as 8000 and also the same in integration server config in R/3.
I refreshed the cache too from the administration page .
any idea why is this error still occuring
Thanks
Nikhil

Hi,
Check this thread-
HTTP_RESP_STATUS_CODE_NOT_OK 404 Error
Go to SXI_CACHE and refresh the cache. Or delete the cache.
Also go to SLD->Business system->Integration Server URL it should use Http Port (8xxx)
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

File to ABAP Server Proxy Scenario

Hi 2 all,
I am running File to Server(ABAP) Proxy scenario...
I have checked the ABAP Server Proxy at application server only and it is working fine....But when i am running the whole scenario my server proxy is not getting executed..( i.e my file is being picked up but proxy is not getting called ..:(( )
Can i expect some valuable inputs regarding this issue..?
Regards,

to debug the problem....
first check SXMB_MONI of R3 system... where proxy has been created.
1 .check whether your proxy has been called ... it will be evident you get any message in moni for you interface or namespace..
2. check you proxy message has not got stucked in queue... sometimes message get stucked in queue and hence proxy are not called.. release the messaeg using smq2.
ELSE
1 .go to SXMB_MONI...of XI..
2. select 'Call Adapter' in right hand of monitor.
3. check the 'trace' under Call Adapter.
4. if you go at end of trace or somewhat near to end.. there should trace like...this ...
Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: destination</Trace>
<Trace level="3" type="T">Destination = D67CLNT103_HTTP</Trace>
<Trace level="3" type="T">Attributes of destination: D67CLNT103_HTTP</Trace>
<Trace level="3" type="T">Type = H</Trace>
<Trace level="3" type="T">Pipeline = ENTRY</Trace>
<Trace level="3" type="T">Action = EXECUTE</Trace>
<Trace level="3" type="T">Host = XXXXXXX</Trace>
<Trace level="3" type="T">Port = XXXX7</Trace>
<Trace level="3" type="T">Client = 103</Trace>
<Trace level="3" type="T">User = XIAPPLUSER</Trace>
<Trace level="3" type="T">Language = E</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">SSL not active</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
check whether connection establishment between XI and R3 is successful or not...
if you are getting same message as above ,,that means ur RFC is working fine...
problem is on r3 side.. for this go to r3 and check moni...

IDoc error on outbound side

Hi.
I'm setting up a communication with (JMS adapter -> XI -> IDoc adapter).
No w to the problem. When we send the message with the IDoc adapter we get the following error.
Message has error status on outbd. side
We can see this message when I put my cursor over the red flag in the outbound status column in SXMB_MONI.
I do not think there's anything wrong with the adapter because we are using it to send an other IDoc and that IDoc gets processed correctly to the target system.
What can cause the error on the that I get above?
BR
Kalle

Hi,
go to details of that transaction and check the error that caused idoc in outbound status failure...
an error tab can be seen in the outbound binding pipeline entry of that transaction and check the error caiused that
Rajesh

** HTTP 401 Unauthorized - IDoc to IDoc scenario

Hi Friends,
I am doing IDoc to IDoc scenario. For the sender side I am using XI adapter instead of IDoc Adapter. Because, we don't have access of third party source (SAP) system. We take the source payload from message mapping and test the same in RWB --> Component Monitoring --> Integration Server --> Adapter Engine XD1 --> Test Message Tab.
After give all the sender details, when I test the scenario, it throws the following error 'Error while sending message; invalid content type for SOAP; TEXT/HTML; HTTP 401 Unauthorized'.
What could be the problem ? Could you kindly tell me friends.
Kind Regards,
Jegathees P.

Hi
Check Pipeling entry in SLD
SLD -> Business System -> Open your XI business system and check for the pipeline entry there.
It should be http://server:httpport/sap/xi/engine?type=entry
Check also this blog for HTTP 401 Error
Http* Errors in XI

XI-BW integration problem!

I need to send data from XI to BW.
I ve done all steps as described in this how-to-guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
("How To Integrate XI and BI in SAP NetWeaver 2004s")
I've configured both the BW part of configuration (created datasource, webservice, abap xi proxy in bw system...) and xi configuration accordingly to that guide.
But.... No messages are in BW system. In XI message monitor is all ok - the messages are sent.
I am confused!
I have some doubts about XI configuration.
1) For example I doubt about XI adapter configuration.
The name of BW system - sapbw. HTTP service number of BW is 8030.
The name of XI system - sapxi. HTTP service number of XI is 8040.
The full url of IS is http://sapxi:8040/sap/xi/engine?type=entry
What URL settings of XI adapter should be for inbound interface of BW system?
I've set http://sapbw:8030/sap/xi/engine?type=entry.
But I think it is wrong! Because BW system is not IS but it is Apllication system.
(By the way I set url http://sapxi:8040/sap/xi/engine?type=entry - the same result is no messages in BW)
So tell me please, in what place I must send the messages for BW by XI adapter?
2) And what about Proxy? At what step I use it? I cannot see Proxy usage in my configuration.

Hi,
XI adapter configuration itslef means proxy. Once you have the inbound interface in your scneario, you have to generate proxy on the BW system
One point here is, what the WAS version of you BW system? WAS >= 6.20 only support proxy configuration. This is because, there is an IS built in WAS. If that is not the case, you would have to go with RFC or IDoc communication.
In the Receiver XI adapater, you have to mention the name of the server (fully qualified), ABAP port, Pipeline entry path, Language and client. Remember this is only when the WAS is >= 6.20.
VJ

While doing change in Idoc/ abap what need to change at XI side

I have to do some change in my abap program, need to add some field over there.
Please let me what I need to change at XI side.
Here Idoc is at sender side.
I am using XSLT mapping over here.
I have one more questions, abt the concept of pipelining in XI, Do you have any one some document with example, where we can use the concept of pipelining in XI in real time problems.
Thanks

Hi Ram,
Please check these threads..
Problems with XI Pipeline queue setup
Pipeline entry error.
XI Pipeline Logging
XI Pipeline
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
cheers,
Prashanth
P.S : Please mark helpful answers

How to test the integrated configuration?

Hi Guys,
I have created a integrated scenarion and i want to know how can we test it from the RWB. I am getting the errors when i post the payload from the test tab to the adapter engine.
Thanks,
Srini

Hi Srinivas,
Integrated scenario can be run only for those adapters which lies on the adapter engine. This can be tested from end to end using sender channel onlybecause in RWB testing, u cant test it using the test tab of integration engine because that is used to put the message on the pipeline entry URL. But in case of integrated scenario , the message processing happens in the Advance adapter engine. The message doesnt pass from the Integration engine and So the message which are executed as integrated scenario are not available in the SXMB_MONI also.
This is a feature in PI 7.1. This enhance the performance and all the steps i.e
1) Receiver determinatiom
2) Interface determination
3) Sender agreement
4) receiver agreement
are present under a single object (Intrgrated scenario) which is cached in the adapter engine cache.
Hope this clear the Integrated scenario concept.
Thanks
Ajay

Receiver Proxy adapter

Hello Experts,
I am getting a message in SXMB_MONI "Pipeline ENTRY does not exist (table SXMSPIPE)" <SAP:Category>XIServer</SAP:Category>
I am using a receiver XI adapter with HTTP protocol. Appreciate your help in resolving this.
Thanks
Ricky

Hi Ricky,
Just curious, but I assume the system that issued the message is the receiving R/3 6.20 System?
The error message says: "Pipeline ENTRY does not exist".
This means that the system that issued the message is looking for a pipeline called 'ENTRY' in its 'XML Message Server: Pipeline Definition' table SXMSPIPE.
The question is "Why would the system that issued the message be looking for a pipeline called 'ENTRY'". A possible answer follows.
I noticed in the SAP Note 602959, mentioned earlier in the forum thread, the following paragraph:
Begin of SAP Note quoted paragraph ****
The correct URL is http://<host>:<port>/sap/xi/engine?type=entry&pipelineid=entry whereby you ... transaction SMICM (Goto -> Services).
If you are working exclusively in XI 2.0 (that is, you do not have a XI 1.0 sender), the correct URL is: http://<host>:<port>/sap/xi/engine?type=entry
End of SAP Note quoted paragraph ****
I notice that the first URL in the above paragraph contains the parameter '&pipelineid=entry' while the second URL does not.
I don't know if you have control over the URL that calls the proxy in the receiving R/3 6.20 System, but if I were you, I'd try to make sure that the URL doesn't contain the parameter '&pipelineid=entry' because I think this parameter might be the reason for the system trying to find a pipeline called 'ENTRY'.
What do you think?
Best Regards,
Andy

Transmitting message to entry pipeline failed !!

Hi all,
We have configured a file adapter to poll a specific directory. Now the adapter polls the file , deletes it after reading it , however it fails to deliver the message to entry pipeline.
We are getting an error msg that reads:
Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..
We have already gone through the link:
Transmitting message to entry pipeline failed !!
Accordingly we have checked but we have not used any business system.
There are two business service(one sender and the other reciever).
We have checked sxmb_adm and httpport in the exchange profile but all of them are filled with the respective values:
com.sap.aii.connect.integrationserver.r3.httpport = 8030.
com.sap.aii.connect.integrationserver.httpport = 53000.
in sxmb_adm we have given url as http://10.119.4.33:8030/sap/xi/engine?type=entry
But still in the error msg the url reads as:
http://itcxi1:53000/sap/xi/engine?type=entry
The entire audit log shown is:
2006-05-24 12:59:10 Success
Channel SenderChannel: Send binary file "D:\usr\sap\trans\tmp\sender\xi_input.xml". Size 363 with QoS EO
2006-05-24 12:59:10 Success
Application attempting to send an XI message asynchronously using connection AFW.
2006-05-24 12:59:10 Success
Trying to put the message into the send queue.
2006-05-24 12:59:10 Success
Message successfully put into the queue.
2006-05-24 12:59:10 Success
The application sent the message asynchronously using connection AFW. Returning to application.
2006-05-24 12:59:11 Success
The message was successfully retrieved from the send queue.
2006-05-24 12:59:11 Success File "D:\usr\sap\trans\tmp\sender\xi_input.xml" deleted after processing
2006-05-24 12:59:11 Success
The message status set to DLNG.
2006-05-24 12:59:11 Error
Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..
2006-05-24 12:59:11 Success
The asynchronous message was successfully scheduled to be delivered at Wed May 24 13:04:11 GMT+05:30 2006.
2006-05-24 12:59:11 Success
The message status set to WAIT.
2006-05-24 13:04:11
Success Retrying to send message. Retry: 1
This same process is repeated 4 times.
Pls suggest what else do i need to check.
Regards
Neetu

Hi Michal,
Thanks for ur prompt response.
Actually in this scenario i am not using any business system.
As mentioned before i have two business services one of which acts as the sender service and the other one acts as the receiver service.
Each one of them have their corresponding communication channels.
So where do i change the url.
My sld has a business system for xi in which i changed the url, putting the port as 8XXX.
Next i imported this system to my scenario and tried sending a message again but got the same error.
What should i do next?
Regards
Neetu

Error in pipeline material creation

hi,
we want to create one pipeline material as per our new requirement for showing gas consumption.during material creation with mat type PIPE, it's showing an error:The field Profit Center is defined as a required field; it does not contain
an entry.
Procedure
If the field is the material group or unit of weight, and the field is not ready for input, check whether the material is locked. If it is locked, you cannot extend the Purchasing view or the Sales view. If either of these views needs to be extended, the material must first be unlocked. This can be done only by a user with special authorization.
thanx,
sheetal

Hi
In your client if Profit center accounting(PCA) is activated ,then you need to maintain the Profit center for the material.
Option 1: goto OMS2, got details of pipleine material & select the Costing View of the material.
Now goto MM01 in creation of pipeline material & maintain the profit center in Cotsing 1 View.
Deactivating the field from mandatory to optional will not serve your purpose as PCA will get affected.
Thanks & Regards
Kishore

MRKO, For document type RE, an entry is required in field Doc. Hdr Text

Hello,
I'm doing consigment settelment with MRKO transaction. At invoice verification we have obligatory field "documet header text". Because with MRKO (transaction) settlement this posting is automaticali doing fi posting I can't enter document header text...
Is there any chance to fill in the document header text somewere?!?, and this is then copied to the fi posting durring the MRKO settelement?
Thanks
Saso

Hi
Try using the enhancement RMVKON00 is used in the settlement of "consignment and pipeline liabilities" in Logistics Invoice Verification. This enables you to create invoice documents posted in the report with a different
format to that defined in the standard system.
The enhancement comprises two function modules for making changes to:
o Invoice data before posting the invoice
o Entries in table RKWA at goods withdrawal
For further information, see the documentation on these function
modules.
Regards
Antony

Pipeline URL

Hi All,
I want some clarifications regarding the Pipeline URL's that we specify in the SLD .
In our Landscape we have a XI 3.0 SP10 J2EE engine as well a Plain J2SE Adapter Engine Installed.
Then, Is that we will have two Integration Server's in the SLD or I am confused about this....
When I see the Pipeline URls of the Integration Server's:
http://sapxi30:8000/sap/xi/engine?type=entry
http://sapxi30.nwk.amer.csc.com:8000/sap/xi/engine/?type=entry
What is the difference between these two URL's ?
Then one more question ....
What is the diff between giving ?type=entry and action=execute ?
I suppose that I am asking some Basic Questions but I want some clarifications or Suggested Documents to get cleared with this stuff.
Many thanks,
Romit.

Hi Romit,
1. The URL's you mention are both identical. The first one (http://sapxi30:8000/sap/xi/engine?type=entry) only consists of the hostname of the XI-server. This will only work when the client which makes connection resides in the same domain or when the hostname is mentioned in the hosts file.
The second one (http://sapxi30.nwk.amer.csc.com:8000/sap/xi/engine/?type=entry) is the Fully Qualified Domain Name (FQDN). In your cade nwk.amer.csc.com is the dns-name of the domain in which your XI host resides. This is the URL which should be used normally, even when the clients are in other domains, this one should work.
I hope I've made it a bit clearer. If not, you should as one of the network guys from your company, he can also explain this.
2. The difference between ?type=entry and action=execute ?
?type = entry is part of the URL the integration server pipeline, as you know.
action=execute is something different. This is an attribute which can be used in an JDBC-message.
Best regards,
Alwin

BPM Sync/Async Scenario: error: "Timeout condition of pipeline reached"..!

Hi,
I am doing Sync/Async BPM scenario.
-> Receive message and process and response back to the sender.
Sometimes it will correct correctly. Sometime the message will come and stay in XI and fails with error
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I observed that the messages will stay in transaction "SXMS_SAMON" . and will fail after sometime.
What might be the reason. ? what need to do to stop these kind of errors?
Thanks
Deepthi.

Hi Praveen,
Webservice <--> XI -->BW .
BPM :
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.
Messages are getting struck in SMQ1 and SM58 at these three points.
1. Message comes and stays in SXMB_MONI in status "Log Version"
The messages are stuck in SMQ1 in READY status without doing any processing.
XBQO$PE_WS90100002 WORKFLOW_LOCAL_100 1 READY 26.02.2009
Once I push the queue by Activating/Unlocking, it will process.
2. when it is trying to send the message to R/3 (Backend system) it is waiting in SM58 with below entry.
WF-BATCH SWW_WI_EXECUTE_INTERNAL_RFC WORKFLOW_LOCAL_100 Transaction recorded
Manually I execute LUW to push it. Once I done the message will go to R/3 system and Response mapping also complete.
3. Again it is waiting at SM58 with below deatails while sending the response to sender.
PIAFUSER SWW_WI_COMP_EVENT_RECEIVE_IBF WORKFLOW_LOCAL_100 Transaction recorded
we are again manually execute LUW. Once we done the response message will go back to Sender.
Any Idea to solve this..?
Thanks
Deepthi

Entry missing in sxmb_moni

Hi,
My interface recived meeages through http and uses a BPM for some other synchronous calls in the flow.
We were testing negative test cases and asked the sender system to send a wrongly formatted message.
but the problem now is that a message that was sent by a third party to XI entered the BPM and i can see the entry in the transaction 'sxmb_moni_bpe' but where it failed (as expected) but when i try to see the corresponding entry in transaction 'sxmb_moni' i'm not able to.
It looks like the message hit the BPE but not the IE !
However this did not happen in the test environment. Could any one who has a suggestion or experienced similar cases help ?

Hi Bharath,
Please check both LOGGING & LOGGING_SYNC parameters configuration on both TEST and PROduction environments
baiscally these 2 or LOGGING_PROPAGATION parameter used to perform logging/tracing fuctionality globally of IE.
Parameter LOGGING or LOGGING_SYNC (category RUNTIME) to activate logging of asynchronous or synchronous messages locally for the whole Integration Engine. This means that all service calls of all pipelines of this Integration Engine are logged.
Parameter LOGGING_PROPAGATION (category RUNTIME) to activate logging globally. This means that message processing is logged until it is complete on all involved Integration Engines.
And also, check how these 2 parameters are configured TRACE_LEVEL, TRACE_LEVEL_PROPAGATION for category RUNTIME in both the environments.
Regards
Sekhar

Pipeline Entry

Similar Messages

Maybe you are looking for