RFC Adapter issue

Hi,
I have a strange behavior from the RFC adapter.
When I submit from a report data via RFC to XI, everything works. If I try it a second time, the RFC call fails. Also a RFC connection test to XI fails.
After restarting the RFC Adapter in the Visual Admin, I can execute the scenario for another time. A second time fails then again.
Does someone know this problem?

Hi Michal,
changed the param initialRfcClientConnectCheck to false. Restart the RFC Adatpter, but I am still facing the same problem.
Sometimes I am facing connection problems with LCRSAPRFC, too. Sometime a connection test is successful, sometimes not.
The error I get is: "CPIC-CALL: ThSAPCMRCV no data received". After a view tries it works again - but for not very long.
Message was edited by:
Chris Sell

Similar Messages

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Sender RFC Adapter Issue

Hi ,
I am using the following scenarion (SAP ECC)Sender RFC>PI 7.1->Receiver JDBC(ThirdParty).
The issue is whenever the the ECC system is down and is up again , the RFC sender messages are getting struck in SM58(tRFC queue).What I manually do is , go the RFC Sender communication channel in PI and reactivate it again, by making a small change in the description of the communication channel.
So, my question is , whether there is a automatical ways to handel this issue.
Any other suggestions would be highly appreciated.
Thanks,
Venu

There is no standard way to perform this automatically. I think restart of ECC is not a frequent practice in any business, therefore ideally you should add this as one of the post processing procedures after ECC restart.
Technically, there is possibility of creating a scenario which can run through a job on ECC running once after each restart. This can call webservice in PI to fetch communication channel information and reactivate it. Not a solution I would recommend.
Regards,
Prateek

RFC to XML-RFC Parsing issue in RFC Adapter as Sender

Hi all,
I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
DATA: BEGIN OF ID_STR,
 ID_VERSION(8) TYPE C,
 ID(96) TYPE C,
 ELEMENT_NAME(50) TYPE C,
 ELEMENT_VALUE(128) TYPE C,
 END OF ID_STR.
DATA: it_id LIKE TABLE OF ID_STR,
 ls_id LIKE ID_STR.
ls_id-ID_VERSION = 'EPC_1.30'.
ls_id-ID = '30340242206DC3C00000000A'.
ls_id-element_name = 'BATCH_ID'.
ls_id-element_value = 'BATCH001'.
APPEND ls_id TO it_id.
CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
IN BACKGROUND TASK
DESTINATION 'RFC_UPDATEAII'
EXPORTING
 IV_BUSINESS_PROCESS = '09'
 IV_COMMAND = 'DO'
 IV_ACTION_TYPE = 'APL2'
 IV_PRT_ID = '31140242200000000F000000'
 IV_DEVGRP_EXTID = 'MOBILE'
TABLES
 IT_ID = it_id
commit work.
And the parsed RFC-XML message is:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:_-AIN_-UI_MOBILE_MSG_SEND
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
<IV_BTD_EXTID />
<IV_BTD_TYPE />
<IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
<IV_COMMAND>DO</IV_COMMAND>
<IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
<IV_LOC_EXTID />
<IV_LOC_TYPE />
<IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
<IV_PRT_ID_VERSION />
<IV_REASON_CODE />
<IV_UNAME/>
<ET_RETURN />
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>206DC3C00000000A BATCH_ID</ID>
<ELEMENT_NAME />
<ELEMENT_VALUE />
</item>
</IT_ID>
</rfc:_-AIN_-UI_MOBILE_MSG_SEND>
You can see the data in the table is all wrong, it should be:
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>30340242206DC3C00000000A</ID>
<ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
<ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
</item>
</IT_ID>
The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
Have any of you seen this problem and how you resolve it?
Thanks a lot for your help!
Regards,
Hart

Hi Hart
long time no seen - hope you remember me
>The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
there is an easy way (guess max 3-4 hours) to solve all of your issues
and get rid of a BPM
use IDOC - XI - ABAP Proxy
then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
maybe you can go this way and IDOCs always work...
good luck,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

RFC receiver adapter issue - ECC side we are seeing blank data for the RFC

Hi All,
We are using Receiver RFC adapter to call a custom RFC (Synchronous call). It was working fine, but recently RFC was modified (They added new fields). We re-imported the RFC into ESR and also modified the mapping to reflect the new RFC strucuture. Now when we execute the RFC, at the ECC side no data is beeing seen. On the PI side we see data in sxmb_moni. It looks fine. However we don't see anydata in ECC. We did full cache refresh but it did not help.
Please let me know if anyone has any thoughts on this issue.
Thanks
-Pradeep

I enabled the the RFC adapter trace in PI. It appears like adapter is not sending the structure and tabled that are populated. IT is sending only 230 bytes. Any clue why would rfc adapter drop the tables and structures??
FUNCTION Z_FI_AA_BAPI_ASSET_CHANGE
 handle = 2
 parameter = <null>
 parameter = <null>
 tables = <null>
>>>> [2] <unknown> EXT <ac: 6> >>> FLUSH (READ) (88578752)
Send RFCHEADER [2]: 01/BIG/IEEE/SPACE-U2/52494850
Send UNICODE-RFCHEADER [2]: cp:4102/ce:IGNORE/et:6/cs:2/rc:0x00000023
UUID: send_rfcuuid B6D708F0-B946-11E0-BC35-EEB4AC138154
UUID: RfcCallNew send the uuid to the partner:B6D708F0-B946-11E0-BC35-EEB4AC138154
>>>> [2] <unknown> EXT <ac: 7> >>> WRITE (88578752)
000000 | 01010008 01020105 04010002 01010103 |................
000010 | 00040000 020B0103 0106000B 04010002 |................
000020 | 01060200 00002301 06000700 1A003100 |......#.......1.
000030 | 37003200 2E003100 39002E00 31003200 |7.2...1.9...1.2.
000040 | 39002E00 38003400 07001100 02004500 |9...8.4.......E.
000050 | 11001200 06003600 34003200 12001300 |......6.4.2.....
000060 | 08003700 30003000 20001300 08001800 |..7.0.0. .......
000070 | 73006100 70007000 69002D00 64006500 |s.a.p.p.i.-.d.e.
000080 | 76002D00 64003100 08000600 28007300 |v.-.d.1.....(.s.
000090 | 61007000 72006400 62002D00 64006500 |a.p.r.d.b.-.d.e.
0000a0 | 76002D00 64003000 5F004400 52003300 |v.-.d.0._.D.R.3.
0000b0 | 5F003000 30000605 140010B6 D708F0B9 |_.0.0...........
0000c0 | 4611E0BC 35EEB4AC 13815405 14050200 |F...5.....T.....
0000d0 | 00050200 0B000600 36003400 32000B01 |........6.4.2...
0000e0 | 02003200 5A005F00 46004900 5F004100 |..2.Z._.F.I._.A.
0000f0 | 41005F00 42004100 50004900 5F004100 |A._.B.A.P.I._.A.
000100 | 53005300 45005400 5F004300 48004100 |S.S.E.T._.C.H.A.
000110 | 4E004700 45010203 37000003 37051400 |N.G.E...7...7...
000120 | 10B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
000130 | 54051401 3100E62A 54482A03 00E60000 |T...1..TH.....
000140 | 00000000 00000000 00000000 00000000 |................
000150 | 00000000 00000000 00000000 00000000 |................
000160 | 00000000 00000000 00000000 00000000 |................
000170 | 00000000 00000000 00000000 00000000 |................
000180 | 00000000 00000000 00000000 00000000 |................
000190 | 00000000 00000000 00000000 00000000 |................
0001a0 | 00000000 00000000 00000000 73617070 |............sapp
0001b0 | 692D6465 762D6431 5F445049 5F313839 |i-dev-d1_DPI_189
0001c0 | 34303530 00000000 00000000 63303432 |4050........c042
0001d0 | 35313733 62393435 31316530 38373562 |5173b94511e0875b
0001e0 | 30303030 30303163 65366132 00000000 |0000001ce6a2....
0001f0 | 02C04251 73B94511 E0875B00 00001CE6 |..BQs.E...[.....
000200 | A2B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
000210 | 54000000 01000000 002A5448 2A0131FF |T........TH.1.
000220 | FF0000FF FF000000 00000000 00000000 |................
 >> CPIC native call CMSEND [2] convid: 88578752 14:23:39,159
 << CPIC native call CMSEND [2] convid: 88578752 rc: 0 14:23:39,159

RFC Adapter - Locking Issue

Hi,
Our SAP production environment was down for two days. While it was down the login used by one of my RFC Receiver Adapters was locked. This meant the adapter could not run. Fair enough.
When the Production environment was brought back up the login used by the RFC Receiver Adapter was unlocked. However, I continued to get an error in Runtime Workbench claiming that the login was locked.
Checked with the security team and they confirmed the user wasn't locked.
Just to try something I went into the RFC adapter in question and simply retyped the login/pwd, saved the adapter and activated it. This seemed to clear the problem and it's now running as expected !!
Question is why did this work ? The adapter was saying the login was locked. It wasn't. All I did was effectively resubmit an updated version of the adapter and it worked again, even though no part of the adapter had actually changed. Is this some sort of caching issue ? Any thoughts ?
Cheers,
PaulC.

User was unlocked yesterday and was still giving locked error this morning. It's now working. Just surprised that a new call of an adapter would continue to say locked when it wasn't. Can only think it's some for of caching but this is a pretty unsatisfactory answer. Makes me worry that it might happen again.

RFC Adapter reconnect issue

hi
We have a problem with RFC connection with SAP System on production.
I consuder to change initialRfcClientConnectCheck to false.
But in this case RFC adapter will check connection each time. It is not good for performace.
What doy think is it good practice to have initialRfcClientConnectCheck=false on production system? I don't see another way How to force XI reconnect after shutdown of SAP System.

Hi,
Apart from setting this option there is no other way out.
We have made this change in our production and we have faced no issue in terms of perfromance after setting the parameter!
Regards
Bhavesh

RFC Receiver Adapter Issue

Hi all,
I'm sending a sales order from my ftp server to my R/3 system through RFC. I want this sales order to be created in the R/3 system, For this i'm using BAPI_SALESORDER_CREATEFROMDAT2. Now when i'm configuring my RFC Receiver adapter using the help given on the help.sap.com under "adapters"->"rfc adapter"-> "configuring the rfc adapter", i'm not able to find the parameters mentioned under " Advanced Mode" Heading. In this page, it says that after checking the Advanced mode checkbox, one should get the additional parameters and then we need to set the indicater for the parameter "Commit Control for Individual BAPI Calls". Since i'm not able to find these parameters even after checking the chekbox, i'm stuck. I understand that if i don't get this parameter, my BAPI will not commint and hence the sales order will not be created in R/3.
Kindly suggest.
Regards.
Naveen

Hi Naveen -
>>>In this page, it says that after checking the Advanced mode checkbox, one should get the additional parameters and then we need to set the indicater for the parameter "Commit Control for Individual BAPI Calls". Since i'm not able to find these parameters even after checking the chekbox, i'm stuck.
For this I agree with Sameer. It's probably an adapter metadata issue. As mentioned your XI system needs to be at least on SP14. Also, in the Int. Repository, check SAP BASIS 6.40 SWC SP Level by right clicking on the SAP BASIS 6.40 SWCV, then Display Support Package - this is where the adapter metatdata is delivered. By default, the highest one displayed is wha'ts current on the system. You should see at least SP14 here. Incidentally, this does not confirm the SP level that the rest of the XI components are on, just this SWC.
>>>When i checked in the integration engine, transaction sxmb_moni, i found that the message was processed successfully ! But when i checked in my R/3 system, i didn't find any sales order ! Kindly give me some inputs for this issue.
It probably failed in the adapter engine. Check the adapter engine monitor via the RWB - so once in RWB, goto Message Monitoring, select Adapter Engine (important), then look for your message.
Regards,
Jin
Message was edited by: Jin Shin

RFC Receiver adapter issue. Pls advice

Hi All,
When XI is sending data back to R/3 system though RFC Receiver Adapter I am getting the below error. Any suggestions
Error Category XI_J2EE_ADAPTER_RFC
Error Code RECEIVER_GENERAL_ERROR
Pls advice.

Rick, your question is very unspecific, so anyone trying to help can only guess very roughly.
So I only have a very rough hint for you, which is the FAQ for RFC adapter.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373330383730%7d

RFC Adapter Problem: Necessary Roles?

Hi XI Gurus,
Our team is working with a File-to-RFC scenario. We are using a custom RFC, which uses BAPI_GOODSMVT_CREATE within it, to post data for Goods issue, Goods receipt and Transfer Posting. We are using the credemtials of a user, sapxiuser, within the RFC adapter. Can anyone please tell me what are the roles that are to be maintained for this particular user at the R/3 end?
Points will be rewarded!
Thanking in anticipation,
Amitabha

Hi,
Remember to add explicit commit in the communication channel:
"
Commit Control for Individual BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
"
Regards,
Wojciech

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

RFC Adapter

Hi
I am using RFC adapter, I am facing java.lang.outOfMemory Exception whenever payload size increases.
Important point: In XI everything is successful.
 But in R-3 I am facing the problem.
Please guide me, how to solve this issue.
Piyush

Hi All
I have set up the connection for Integration builder in R-3.
In sproxy I am able to see inbound and outboud interfaces, I have generated the class for th outbound interface and configured default logical port for the same.
The report is as follows:
REPORT ZAK_TEST_PROXY.
DATA:
Reference variables for proxy and exception class
lo_clientProxy TYPE REF TO ZCO_EMPLOYEE_MASTER_DAT,
lo_sys_exception TYPE REF TO cx_ai_system_fault,
Structures to set and get message content
 ls_request TYPE ZEMPLOYEE_MASTER_DAT361,
 ls_response TYPE ZEMPLOYEE_MASTER_DAT360.
 Instantiate your client proxy.
TRY.
create proxy client
 CREATE OBJECT lo_clientProxy.
 ( LOGICAL_PORT_NAME )
*LOGICAL_PORT_NAME is the name of the logical port that you want to use, which is used to define the receiver. You can omit this parameter if you are using a default port or the XI runtime.
 To send a message, call the corresponding client proxy method. WSDL allows several such methods (specified by the element <operation>). In XI, there is only one method, with the default name EXECUTE_SYNCHRONOUS or EXECUTE_ASYNCHRONOUS. Catch at
*least the exception cx_ai_system_fault:
do synchronous client proxy call
 CALL METHOD lo_clientProxy->execute_synchronous
 EXPORTING output = ls_request
 IMPORTING input = ls_response.
 CATCH cx_ai_system_fault INTO lo_sys_exception.
Error handling
write:/ lo_sys_exception->errortext.
ENDTRY.

RFC Adapter not Call

Hello Friends,
I am working on XI 2.0
My Scenario is
IDOC --> XI --> RFC Adapter --> R/3 System
I am configuring the RFC adapter for the SAP system.
But when I am able to try to call using the Integration Engine its not call the RFC adapter.
I define the end point as
RFC Adapter
(X) Load Balancing Deactivated
Application Server -- <host name>
System Number -- 00
When I run the scenario it show me in the sm58 transaction as
Connection Close (no Data)
And in the SXMB_MONI Transaction it shows
A. Status as Green Flag means Message schedule on outbound side.
So can you please identify and suggest me the solution or what else configuration is required.
Thanks & Regards,
Gaurav Jain

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
 at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
 at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
 at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

Sender SOAP Adapter issue with webservices for authorization.

Hi All
Issue:
As we are developing a Web Service to fetch account balance from SAP(upon receiving the account no from client) and have given the wsdl file to J2EE application to call or make use of the service. But as a part of that service they expect userid/password to be entered manually from client pop-up. At this point of time, we don't want to enter userid/password manually but we want this to be hardcoded/embedded in Webservice so that there is no need of manual intervention upon calling this service.
Actual Requirement:
From Webservices to R/3-ECC6.0-IS-Banking-RFC (Synchronous Interface)
Sender: SOAP Adapter synchronous
Receiver: RFC Adapter synchronous
Note: Requesting a account number and getting response from RFC is account Balance and Date to webservice
Regards
Kiran kumar.s

Hi praveen,
Thanks for ur reply.What you said is exactly right but for time being i have to make the client not get the authorization(password--Username and password(pop-up)) when he invokes the WSDL into webservice for that u told that to write some hardcode in J2EE application,but i don't know that where to write and what to write.so, if possible can u give me the code and procedure.
This is the URL:
http://hcl3sap:50000/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_SOAPSENDER
Regards,
kiran kumar.

RFC Adapter issue

Similar Messages

Maybe you are looking for