SOAP to RFC Scenario - Error at Sender Communication channel !!
Hi Experts ,
I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
My findings :-
1. Error at RWB 9/24/09 4:24:10 PM error occured
9/24/09 4:24:06 PM request received
2. At SOAP UI client tool :
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
3. At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
1. I don't see any issue in authorization as i am having SAP_ALL .
2. URL string seems to be O.K :
http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
Kindly advice !!!
Regards ,
1. Check PI id and password is working fine.
Check if the user you are using has SAP_XI_APPL_SERV_USER role.
Another way is to pass id and pwd in URL
Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
2.Provide SOAP URL like -
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Similar Messages
-
Hi PI Experts,
For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
so kindly please help me to solve this scenario.
Thanks & Regards,
B.Srinivas Prasad.I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
Make sure that its in the below format :
From SAP help :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
and check Sender Soap Channel Status is it activated/not and check Cache Status -
Help SOAP to RFC Scenario using BPM (Synchronous communication)
Hi,
I am doing a scenario from SOAP to RFC scenario(Synchronous communication). Here I am creating a PM Notification in the SAP system through a webservice.
I am using three BAPI'S here,
1. BAPI_ALM_NOTIF_CREATE
2. BAPI_ALM_NOTIF_SAVE
3. BAPI_TRANSACTION_COMMIT
I am successful in calling the first BAPI from the Web Service. For this I have not used BPM. But to commit the transaction(PM notification in this case), I have to execute the other two BAPI's as well. I have to pass the output of first BAPI to the second BAPI and then execute the 2nd BAPI. And finally have to execute the 3rd BAPI. FYI, 3rd BAPI is not dependent on any output. It has to be executed independently after execution of the first two BAPI's.
How can I execute this scenario? Do I have to use BPM? If yes please let me know the steps in detail. I have not done any BPM scenario till now. So please answer me in detail.
Thanks in Advance,
Vijay
p.s. reward points are mustHi Vijay,
Yes, You will indeed need a BPM in this case...
Based on my understanding of the Scenario u have explained, here are the steps that would be needed.
1. Receive With the Sync-Async Bridge open.
2. Transformation Step (Between the source Request and The BAPI_ALM_NOTIF_CREATE Request)
3. Send Synchronous
4. Fork
5. In one Branch of the fork - Transformation (Between the BAPI_ALM_NOTIF_CREATE Response and API_ALM_NOTIF_SAVE Request)
6. In the other branch of the fork - Transformation (Between a Dummy Source and the BAPI_TRANSACTION_COMMIT Request)
7. Send Synchronous (to make the 2nd BAPI Call)
6. Transformation ( BAPI_ALM_NOTIF_SAVE Response and the source Response)
7. Send Asynchronous (to make the 3rd BAPI call)
8. Send the Source Response and close the Sync-Async Bridge.
There might be alternative ways also of doing it...
Also a better design would be to take care of the 2nd and the 3rd BAPI call within the code of the 1st RFC Function Module.
Regards,
Abhy Thomas -
BIC Module Error in Sender Communication channel for EDI to File scenario.
Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
AbhishekHi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish -
Error in sender communication channel
Hi,
I am doing File to RFC scenario in which i am using Standard bapi to get the cost from the sap system
while sending the data in sender communication channel the processing mode is in delete mode but it is not deleting and throwing the error
Error: com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
this error is from sender communciation channel..
can any one give some inputs for this...
regards,
KishoreK.P.N.,
i have checked it getting the same error. in moni also administrative cache clear error is coming
do we need to do any workaround...
regards
Kishore -
XI-Multiple instance scenario -File & SQL sender communication channels
Hi
i have a basic question regarding how file sender communication channel ( where we poll for a particular file pattern either using file/ftp types in a particular subfolder ) or a sql sender communication channel - ( selecting records from a sql source ) would work in a scenario with two active XI instances and j2EE file and sql adapter services running on both of the J2EE servers ?
1. How would the file polling from both J2EE servers - avoid a conflict looking for the same file pattern ? Is there any inbuilt mechanism from SAP to make multiple instances work with the file polling - without a confict ?
2. Simlar question for SQL sender type communication channel ?
If SAP does have a mechanism to handle multiple instance scenarios for file and sql sender adapter based communication channels, is there a link/document on this ?Hi Karthik,
Please see my comments.
I am just wondering aloud - what will happen if we use a select for update clause in the sql sender adapter communication channel -
Gouri: Yes you can use select + update. In fact that is the right way.
will this ensure that polling from one J2EE instance will lock the selected records so that the second instance does not select the same set of records from the sql server ? Or should we not use a select for update and use a simple select statement ?
Gouri: Yes. SQL DB will ensure that same data will not be picked by another node. As I mentioned earlier use serilizable option from advanced mode.
-Gouri -
SOAP to RFC Scenario Timeout in Sender Application ...
Hi All,
We have SOAP sender webservice (.Net app) To RFC receiver on SAP side through PI 7.1.The problem we are facing is the RFC from SAP side is taking more time to send response back and by the time PI sends the response back to calling webservice application ,they timeout on their side.Can PI by anymeans tell the calling application to wait until we get a respose back from SAP.
Any thoughts and recommendations greatly appreciated.
Thanks
CDo we need to check the timeout of xiadapter.inbound.timeout.default in Pi and set the same in the sender application.
We don't have timeouts in PI so I don't think we have to increase timeout in PI.
Is there a way we can hold sender application to wait until PI sending the response back without ind=creasing their timeout ?
C -
NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario
Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AMHi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Inbound Message --> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace><!-- ************************************ -->
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez. -
Sender Communication Channel Monitoring Error
Hi....Experts,
i am doing rfc-soap scenario synchronous . this is B2B scenario, under party i created business services, under this created 2 communication channels. in RWB, Communication Channel monitoring i am getting this error at sender side..
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: only partyless services are supported but party : xxxxx is set for service sender business service name and sender CC name..
pls suggest me how can i rectify these errors..
for helpful answers i will give points*********
regards,
Pasi.
Edited by: pasi s on May 5, 2008 8:35 AM
Edited by: pasi s on May 5, 2008 8:40 AMHi Pasi,
Check if you are using the same business service (under which u have created the Channels) at sender side in configuration.
You have to use the same business serivce for sender under which your communication channels are created...................
Or
Create a sender communication channel in the service that u have used at sender side.............
So i think in your case there is a mismatch of using the diff sender service at diff stages.............
Hope this will solve your problem
Thanks
Sai
PS: kindly reward points if helpful -
Hello Guru's
Im trying the basic SOAP TO RFC scenario, in which RFC is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL
and the out bound interface consists of only basic feilds i.e.
REQUEST MESSAGE TYPE : AirlineID
ConnID
Fldate
RESPONSE MESSAGE TYPE : Ecnofree
Bussfree
Firstfree
and no fault message type.
i created the scenario with out any errors, and i defined webservies in ID with the following URL
http://starxi:50000/XISOAPAdapter/MessageServlet?Channel=:SXI_BS_SOAPRFC_SENDER:SOAP_RFCSENDER
it is according to the following syntax
htt://<xi server>:<J2EE Port>/XISOAPAdapter/MessageServlet?channel=:<sender business system>:communication channel.
But im not able to post SOAP request to the xi server. it is saying following error
"SOAP Request cannot be posted <with url > 403"
403 is the error code.
please can anyone help me in overcoming the above problem. and where iam wrong.
Thanks in advance
arjunHi!
Please check once again reg SOAP URL while generating the WSDL.
[http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>]
[Re: Using SOAP Sender adapter in PI 7.1]
1. Check whether your SOAP URL s correct or not which you are giving in the receiver SOAP adapter
2. Also check you are giving the SOAP action in the receiver SOAP adatper correctly or not.
3. Finally check the SOAP service is activei or not in SAP>BC>XI-->SOAP in ABAP stack
4. Since FIle is only for ASYN comm and while using FILE for sync interface you need to pass module paramters in the Sender File CC
ERROR 403 means::
This error will be comming mostly in the synch scenarios like SOAP to RFC - SOAP and FIle to RFC--FILE
when the target system is down or service is inactive.
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.
Regards::
Amar Srinivas Eli -
Reg:soap-xi-rfc scenario
In soap-xi-rfc scenario if the RFC function modules processed in R/3 system with some errors then , how to handle the errors , do we need to create the error structure in xi by using the fault message type or there is any other way to handle the application errors?
pls help with suitable answers
regards
chandrakanth.kHi,
The best way to go with ur senario is make it as SOAP XI Proxy.....in proxy u can catch the errors using the fault mesage typw and if u want to validate the data that can be done......if u want to send the error report that can be done in proxy....were u can collect all the errors and send they to the enduser or display them in Application server...
Think this option if possible....
check somelinks on fault mesage.
ExchangeFalultData & ExchangeLogData
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Regards,
Phani
Edited by: phani kumar on Mar 12, 2008 1:05 PM -
Sender Communication Channel Error
Hi all,
iam working on JDBC scenario.For this iam using party and business service.
iam getting following error at jdbc sender communication channel.
Error occurred while sending message: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
Erlier it worked fine.But now iam getting this problem.
We are having some other channels which r working fine.
any ideas......?
Thanks,
Sreedhar Goud.1. If you know the user, who having admin rights;
1.Open the VA tool; ex: C:\usr\sap\X67\JC01\j2ee\admin --> click on "go.bat"
2. Click on "New" button ( this is on Logon Dialog box)
3. Enter "Display name"; and select "Direct Connection To a Dispatcher Node".
4. Say "Next"
5. Enter "User Name","Host" and "Port" and Save the data.
6. Select User and click on "Connect"
2. Did you forget the J2EE_ADMIN password? Just follow below steps:
Just follow below steps:
1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat
Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat
2. "Switch to configuration mode" for that Click on "Pencil" icon;
3. Click on "Pencil" icon means "Swith to Configuration Edit mode" then say "YES"
4. cluster_data --> server --> cfg --> services -->
click on "Propertysheet com.sap.security.core.ume.service
select properties:
ume.superadmin.activated = True
ume.superadmin.password = <enter password >
then say "OK"
Click on "Pencial ICON.
5. Save & restart Java Engine.
Login with "Administrator"
1. http://<host>:<Port>/useradmin/index.jsp
2. Enter userid / Password as "Administrator / <password>
3. it will ask change password just change it.
Please follow steps one by one. it should resolve your issue. -
Sender communication channel stopped after error "Connection Timed Out"
Hi experts,
in our scenario we have an asyncronous sender communication channel with polling every 6 seconds to an external FTP server.
Yesterday evening a "Connection Timed Out" error came.
After this error the polling stopped but channel in communication channel monitoring still remains green.
So status green but no polling.
To solve this problem we stopped and then restarted channel from CC monitoring.
The channel is configured "manually".
The question is: Is it possible to avoid this problem? Maybe there's a parameter in configuration to set?
After a time out error the channel must go on polling, it should not stop. Or it must shows red status.
Thanks
Fabio BoniHI,
I think PI level is "SAP J2EE Engine 7.00 PatchLevel 109886.44"
Thanks
Fabio -
Using common SOAP Sender Communication Channel.
Hi,
Env: PI 7.1
Scenario: Same SOAP Sender communication channel is used in more than one scenario.
Properties "Use Encoded Headers" and "Use Query Strings" are checked.
Problem: SOAP channel is getting binded with the first interface/call. Subsequent calls from other interface proxies fails. It always shows the interface which used this channel for the first time.
My aim is to use the common channel in multiple scenarios and do not want to create separate channel for each.
This was working fine in PI 7.0.
Please help.A workaround would be creating multiple sender agreements using the same channel. For this while creating the sender agreement, use the option "Sender uses virtual receiver". This was u may use same set of sender service and sender interface with same channel.
Regards,
Prateek -
Public URL for Synchronous SOAP to RFC scenario
Hello Everyone,
I have synchronous SOAP to RFC scenario.
i have created the http URL for testing environment through sender agreement.
However, now the user wants a public URL and that too secured one ... means ( https ) in production.
i tried this blog, but Service registry is not configured in our landscape.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725
is there any other way ..?
Regards,
RaviThe process of creating the wsdl will remain same. The url in your case will start with HTTPS instead of HTTP. Note that the port at which HTTPS data would be received will be different than HTTP port and thererfore you need to change that as well. You don't have to set any client authentication unless there is a business requirement. You may simply use certificates for SSL.
In some cases, if PI always receives data through web-dipatcher (ask your network team), then the data hostname and port of web-dispatcher should be used.
Regards,
Prateek Raj Srivastava
Maybe you are looking for
-
How to setup new site in dreamweaver if not working with Local Site Folder?
Dear All, I am working with a website design (wordpress) project with a group of people, since we are working together on the same design, our developing site is not located in the local folder but on remote server, but I can't setup the website in D
-
Running out of disk space - IGS Log Trace
Hello, for a few weeks we are continuously running out of disk space on our CE7.2 Application Server. The following files are increasing every second: Path: usr\sap\C72\J00\igs\log mux_sapce72.trc pw_sapce72_0.trc pw_sapce72_1.trc The entry that is w
-
Multiple (independent) Image Rotation
Usually I'm good at finding information to solve problems by searching the forums. but honestly I've never seen this problem solved or ever heard any mention of it. . . . here goes. I'm writing a space shooter that uses images as the hero and enemy s
-
Photoshop elements 11 freezes when I try to back up the catalogue. i get a message "Please wait while Elements Organizer prepares for backup". what do i do?
-
Photoshop hangs on launch of encore menu
I've been using a menu repeatedly in different projects for a month or so... and now suddenly when I click the 'edit in photoshop button' on my menu's, photoshop hangs, followed by the error 'Adobe Photoshop Cs5 has stopped working.' and then windows