RfcAFBean

Dear Guys
I am using a RFC function STFC_CONNECTION to test RFC connection to XI from System A (4.7). I created a TCP/IP type destincation having gateway name sapgw00 and ip address of XI. Also registered a program with name XI in J2ee engine.
Connection Testing is successful. I also created two communication channel. Sender and Receiver both have parameters pointing to System A. As System A will send and receive the message back.
But I am getting the following errors.
java.lang.NoSuchException:com.sap.j2ee.tests.ejb.stfcbeans.STFC_CONNECTIONLocalObjectImpl0.processFunction
Current I am trying to Test connection through STFC_CONNECTION RFC. RFC is also returning the following error.
Incompatible Bean Type No Processing Function Found.
RFC Communication channel is using a module named RfcAFBean. What is this RfcAFBean and is the above errors are due to RfcAFBean.
Thanks

Adnan,
Some info for you........
Any adapter need a EJB to communicate with the module processor of the Adapter Engine. The RfcAdapter will use one which is called 'localejbs/RfcAFBean'. This can be configured in the Integration Directory for each communication channel on the tab 'Module'. If the list is empty on this tab, it defaults to the EJB named above and nothing has to be done. So if no modules should be used, everything will work without a special configuration. If some custom modules are configured to be used, the last module always has to be the RfcAdapter module. This will establish the communication between the adapter and the Adapter Engine.
So then the next question is to enable trace here...so as to debug it.......
Open the J2EE Visual Administrator, log into the J2EE Engine and choose tab 'Cluster'. Open the server node for which tracing should be enabled and open Services->Log Configurator. Choose tab 'Locations' and open com->sap->aii->af then choose the location 'rfc'. In the right frame the name 'com.sap.aii.af.rfc' shows up with the current serverity. Set this serverity level to 'Debug' and also click on the button 'Copy severity to subtree'. After this click on the 'Apply' button (save symbol) so save the changes. For an RFC sender channel also choose 'SAP XI Adapter: RFC' beneath 'Services' in the left frame. Set the properties 'traceExceptionListener' and 'traceServerErrorListener' to 'true' (in the right frame). Save these changes with the save button. Notice that the RfcAdapter J2EE service has to be restarted to affect this changes. A dialog box will open upon save which can perform the restart after choosing 'Yes'. After enabling the traces the scenario can be reproduced and the default traces can be found at "\usr\sap\<SYSID>\<INSTANCEID>\j2ee\cluster\server0\log" folder.
Hope that helps
Regards
Ravi Raman
While(pointsAreAssigned ==true){
boolean getAReply = true;
else{
System.exit(0);

Similar Messages

  • Error during processing local bean: localejbs/RfcAFBean

    Hi everybody
    we currently trying to perform a RFC Call to our developpment system. The scenario is a simple File to RFC Scenario and it worked until yesterday. Since today the Messages stuck in the RFC receiver Adapter with the following errors in the audit log:
    MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
    Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
    Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
    The deffaultTrace.trc show the following entries. Looks like an error in localejbs/RfcAFBean:
    RfcFunctionName:ZPSCD_INTERFACE_XXXXX
    Date : 07/13/2007
    Time : 9:32:39:301
    Message : 
    [EXCEPTION]
    com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
         at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
         ... 14 more
    Severity : Error
    Category :
    Location : com.sap.engine.services.ejb
    Application : sap.com/com.sap.aii.adapter.rfc.app
    Thread : SAPEngine_Application_Thread[impl:3]_44
    Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 0003BA5D1D27006D000002BF0000653B000435201DA336D6
    Source Name : com.sap.engine.services.ejb
    Argument Objs : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
         at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
         ... 14 more
    Arguments : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
         at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
         at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
         at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
         ... 14 more
    Dsr Component :
    Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.sap.engine.services.ejb
    ThreadObject : SAPEngine_Application_Thread[impl:3]_44
    Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
    User : J2EE_GUEST
    Date : 07/13/2007
    Time : 9:32:39:304
    Message : Error during processing local bean: localejbs/RfcAFBean
    Severity : Error
    Category :
    Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
    Application : sap.com/com.sap.aii.af.app
    Thread : SAPEngine_Application_Thread[impl:3]_44
    Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 0003BA5D1D27006D000002C00000653B000435201DA33A4D
    Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
    ThreadObject : SAPEngine_Application_Thread[impl:3]_44
    Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
    User : J2EE_GUEST
    Date : 07/13/2007
    Time : 9:32:39:306
    Message : Rolling back transaction for message 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND) due to: Exception thrown in method process. The transaction is marked for rollback.
    Severity : Error
    Category :
    Location : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)
    Application :
    Thread : SAPEngine_Application_Thread[impl:3]_44
    Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 0003BA5D1D27006D000002C10000653B000435201DA341C8
    Source Name : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer
    Argument Objs : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,
    Arguments : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,
    Dsr Component :
    Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer
    ThreadObject : SAPEngine_Application_Thread[impl:3]_44
    Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
    User : J2EE_GUEST
    It looks like the JCO Bean has an error. Any Ideas
    Regards Oliver

    Hi Bhavesh
    I found some more interesting log entries and it seems to be a user password problem:
    Retries exceded, set message 38f10280-3388-11dc-9c91-0003ba5d1d27(INBOUND) to status NON_DELIVERED.
    Name or password is incorrect (repeat logon)
    JCoClient connection missingHost:xdsci_XDS_31|AdapterType:MessagingSystem|Sender::FileServer|Receiver::PSCD_CDD|Interface:ZPSCD_INTERFACE_DECLAR_TVA:urn:sap-com:document:sap:rfc:functions|MsgID:38f10280-3388-11dc-9c91-0003ba5d1d27
    Is this the user/password of the channel or is it service user for the JCO?
    Regards Oliver

  • XI error: Object not found in lookup of RfcAFBean

    Hi Forum,
    In a scenario, I have a BPM, which makes a synchronous call to R/3 for execution of a rfc enabled Function module, while doing so, it gives an error as a response, which i can see in the MONI:
    <b>com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of RfcAFBean</b>
    what can be the reason for the error? and how can it be avoided?
    pls help

    it might be a cache problem, run the CPA cache and check.
    ir, id cache the data here also.

  • Error in Adapter engine-"No_Spedin"

    Hi All,
    I have observed the below error in adapter engine today(System error).
    JCO.Exception while calling /SEEAG/RELI_XI_EDIINH_FILE in remote system (RfcClient[PEQ_RFC_INBOUND]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Exception condition "NO_SPEDIN" raised.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException
    The message is going to print Sumfax to SAP ECC.There are no errors in the mapping and the communication channel is also running fine.there was an upgrade in SAp recently after which i observe this error and it didnot exist before.
    Can anybody please help me!

    Hi Sudha
    check Abhishek's Reply  may be helpful  at this thread for com.sap.aii.af.rfc.afcommunication.RfcAFWException
    Re: Error during processing local bean: localejbs/RfcAFBean
    also check the The Sender Agreement Interface , it is either missing or not correct in ID
    Regards
    Abhishek

  • RFC Sender Adapter - MP: exception caught

    Hi Friends,
    We have one RFC to SOAP scenario in our PRD system.
    When we execute an RFC in the R/3 side, the sender RFC CC receives the message. (The message id is generated). But, the message is not entered into SXMB_MONI.
    When we checked the audit log. The error is as below:
    RfcAdapter received sRFC for Z_RFC_SUPER_ACK from P88/300. Trying to send message synchronously.
    MP: entering1
    MP: processing local module localejbs/RfcAFBean
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection RFC_http://sap.com/xi/XI/System is currently not started.
    We have checked Program ID, RFC Connections in R/3 system. It is correct. The standard module "  localejbs/RfcAFBean -  Local Enterprise Bean " is used in the sender CC, only this module.
    We have few RFC receiver communication channels, all are working fine.
    Only this Sender RFC CC, we are facing this problem.
    We found the similar thread "RFC-Connection not started ?".  The same problem we are facing. They suggested to bounce the system and restart.
    Since it is PRD system, it is not able to do that immediately.  Since all RFC receivers are working fine, we feel that it is not required to bounce.
    Can you kindly help me friends, how to solve this problem.
    Thanking you,
    Kind regards,
    Jegathees P.

    Hi Sabarish
    The RFC sender cc is active in ID and started. 
    The status of the channel in CC monitoring is red. (due to this error).

  • Custom Module

    Hi All,
    Is it possible to add custom module to RFC adapter..?  Also using custom module is it possible to convert a payload into attachment in XI..?

    Hi,
    Generally The RfcAdapter will use one which is called 'localejbs/RfcAFBean'. This can be configured in the Integration Directory for each communication channel on the tab 'Module'. If the list is empty on this tab, it defaults to the EJB named above and nothing has to be done. So if no modules should be used, everything will work without a special configuration. If some custom modules are configured to be used, the last module always has to be the RfcAdapter module. This will establish the communication between the adapter and the Adapter Engine.
    Can you go through the below urls which may help you in developing a new module processor:
    /people/sap.user72/blog/2005/07/04/read-excel-instead-of-xml-through-fileadapter
    /people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible
    /people/gowtham.kuchipudi2/blog/2006/01/04/testing-sample-adapter
    Also go through the help which might answer your queries:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/content.htm
    Thanks
    Swarup

  • XI RFC call failing

    Hello,
       I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
       I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
       In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
       Does anyone have any idea why this is so?
    Thanks,
    Murtaza.
    Message was edited by:
            Murtaza Madraswala

    Hi Amitabha,
       I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
    Time Stamp Status Description
    2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
    2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2007-06-18 15:17:54 Success Message successfully put into the queue.
    2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
    2007-06-18 15:17:54 Success The message status set to DLNG.
    2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
    2007-06-18 15:17:54 Success MP: entering
    2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
    2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
    2007-06-18 15:17:55 Success MP: leaving
    2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
    2007-06-18 15:17:55 Success The message status set to DLVD.
       The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
       I appreciate your help. Please let me know if you have any clues.
    Thanks,
    Murtaza.

  • Error: java.lang.NullPointerException

    Hi,
    In my File - RFC - File scenario (PI 7.1), i am facing the error in the communication channel
    File processing failed with java.lang.NullPointerException
    But in SXMB_MONI it the status shows Processed Successfully.
    From File to RFc it displays all the details like Sender Namespace, Sender Interface, Receiver component etc.
             RFC to File it doesn't display any details other than Message ID.
    The following steps are executed in RFc to File message:
        Inbound Message ( CENTRAL )
       XML Validation Inbound Channel Response
       Request Message Mapping
       XML Validation Outbound Channel Response
    these steps also contain the output file format in xml structure:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP xmlns:ns1="http://lotusnotes.uniform.com">
    - <ITAB_OUT>
    - <item>
      <STR>20000000|3022|-10.25|09.11.2009|Testing 1111|</STR>
      </item>
    - <item>
      <STR>20000000|3022|800.99|10.11.2009|Testing 22222|</STR>
      </item>
    - <item>
      <STR>20000015|3022|200|09.11.2009|Testing 333333|</STR>
      </item>
      </ITAB_OUT>
      </ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP>
    pls let me know how to solve this error

    Hi,
    Please see the audit log
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:21 Information Channel CC_LOTUSNOTES_UNIFORM_SND_FILE: Converted complete file content to XML format.
    2009-12-08 07:18:21 Information Send text file  "/home/ftp/home/ftpusr/test/in/20091109PYI_UNIFOR.txt", size 402, encoding ISO8859-1with QoS BE.
    2009-12-08 07:18:21 Information MP: entering1
    2009-12-08 07:18:21 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean
    2009-12-08 07:18:21 Information RRB: entering RequestResponseBean
    2009-12-08 07:18:21 Information RRB: passing through ...
    2009-12-08 07:18:21 Information RRB: leaving RequestResponseBean
    2009-12-08 07:18:21 Information MP: processing local module localejbs/CallSapAdapter
    2009-12-08 07:18:21 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
    2009-12-08 07:18:21 Information Trying to put the message into the call queue.
       Page 1 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:21 Information Message successfully put into the queue.
    2009-12-08 07:18:21 Information The message was successfully retrieved from the call queue.
    2009-12-08 07:18:21 Information The message status was set to DLNG.
    2009-12-08 07:18:22 Information The message was successfully received by the messaging system. Protocol: XI URL: http://sdnpi1.sap.spoolzgroupit:50800/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2009-12-08 07:18:22 Information Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    2009-12-08 07:18:22 Information Message successfully put into the queue.
    2009-12-08 07:18:22 Information The message was successfully retrieved from the request queue.
    2009-12-08 07:18:22 Information The message status was set to DLNG.
    2009-12-08 07:18:22 Information Delivering to channel: CC_LOTUSNOTES_UNIFORM_RCV_RFC
    2009-12-08 07:18:22 Information MP: entering1
       Page 2 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:22 Information MP: processing local module localejbs/RfcAFBean
    2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for Z_PI_LOTUSNOTES_UNIFORM.
    2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for J2EE_GUEST.
    2009-12-08 07:18:22 Information MP: leaving
    2009-12-08 07:18:22 Information The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
    2009-12-08 07:18:22 Information The message status was set to DLVD.
    2009-12-08 07:18:22 Information The application sent the message synchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
    2009-12-08 07:18:22 Information MP: processing local module localejbs/AF_Modules/ResponseOnewayBean
    2009-12-08 07:18:22 Information The message was successfully transmitted to endpoint http://sdnpi1.sap.spoolzgroupit:50800/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
    2009-12-08 07:18:22 Information The message status was set to DLVD.
       Page 3 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:22 Information MP: leaving
    *2009-12-08 07:18:22 Error File processing failed with java.lang.NullPointerException:  *
       Page 4 / 4
    Edited by: jjma1706 on Dec 8, 2009 9:05 AM

  • Messages got stuck in Adapter engine

    We are doing http to RFC sysnchronous scenario
    Message got stuck in adapter engine.so we are getting 500 HTTP timeout error in Http client.
    Please help us to find why messages got stuck in Adapter engine.
    Below Adapter engine audit log message is pasted for your reference.
    Audit Log message:
    Time Stamp Status Description
    26.09.2008 06:33:54 Success Message successfully received by messaging system. Profile: XI URL: http://devsap01:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    26.09.2008 06:33:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    26.09.2008 06:33:54 Success Message successfully put into the queue.
    26.09.2008 06:33:54 Success The message was successfully retrieved from the request queue.
    26.09.2008 06:33:54 Success The message status set to DLNG.
    26.09.2008 06:33:54 Success Delivering to channel: RFC_out_Test
    26.09.2008 06:33:54 Success MP: entering
    26.09.2008 06:33:54 Success MP: processing local module localejbs/RfcAFBean
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for ZFTestRFC
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for J2EE_GUEST
    ime Stamp Status Description
    26.09.2008 06:56:15 Success MP: leaving
    26.09.2008 06:56:15 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
    26.09.2008 06:56:15 Error The message status set to FAIL.
    26.09.2008 06:56:15 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
    Kindly advise us on this issue.

    Hi krish,
           when i send a http request it got stuck in adapter engine with status "delivering" for some time....
    We found that RFC got successfully executed in R/3 system but the synchronous message is not delivered to PI.since adapter engine message is having status "delivering"
    after some time we got adapter engine message status as "cancelled with error"
    Error is Message expired exception which you can see audit log message I have pasted in my previous post.
    Meanwhile we also got HTTP timeout error in Http client.
    Could you please tell me why it got stuck in Adapter engine with status "delivering" since RFC is executed successfully.
    Why we are not getting synchronous message reply back to PI?

  • File to RFC Scenario - Not working with AAE

    I have a File to RFC Scenario (calling RFC /POSDW/CREATE_TRANSACTIONS_EXT)  using AAE but it is failing with following error in PI .
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
    But When I run the same scenario using IE instead of AAE, it is successful from PI. So probably there is nothing wrong in RFC channel configuration.
    There's an OSS note-730870  on this error ,it says the XML document sent to RFC Adapter may not be RFC-XML but as I am using AAE, payload generated after technical routing cannot be viewed.
    Could you all please suggest why this error is coming and solution for the same?
    Thanks,
    Ankit

    Hi Debashish,Monica,
    Thanks for your help, I checked this SAP note its question 16 do describe my problem but do not provide solution and as I am using AAE it does not allows me to see the target structure generated whereas if I use IE the target structure generated is sucessfully getting posted.
    Also, the functional module is present in target system. I have reimported the RFC also.
    Is there some AAE related configuration required to enable AAE with RFC which could be missing?
    This is what I get in log as the RFC reciever is called..
    06.09.2011 14:15:31 Information MP: entering1
    06.09.2011 14:15:31 Information MP: processing local module localejbs/RfcAFBean
    06.09.2011 14:15:31 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    06.09.2011 14:15:31 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    06.09.2011 14:15:31 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
    Thanks,
    Ankit

  • Regarding error showing as exception caught  by adapter framework

    hi all.
    here in my scenario iam doing a file to rfc.
    but when iam sending a file to rfc and when i see in sxmb_moni its showing as sucess.
    bue when i look at runtime workbench under message monitoring (tab) it was showing as
    MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
    Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
    SO WHAT COULD BE THE ERROR IS THE EROR THAT WS SHOWING RELATED TO XI R SAP R3(system that was recieving)
    waiting for the excellent answer.
    cheers.
    seeta ram.

    HI Matias.
    yes i did with the custom Rfc and the result is still the same
    and to be more confident i was creates another xi scenario from file to Standerd Bapi   BAPI_COMPANYCODE_GETDETAIL by creating a simple file with only one field and mappedwith only the request Message type of this Bapi and tested it.
    and even this scenario is also showing the same in reciever rfc and under runtime work ench its showing the same as my old scenario and it is as follows
    2007-10-15 10:47:51 Success Message successfully received by messaging system. Profile: XI URL: http://jssxid0:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2007-10-15 10:47:51 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2007-10-15 10:47:51 Success Message successfully put into the queue.
    2007-10-15 10:47:51 Success The message was successfully retrieved from the receive queue.
    2007-10-15 10:47:51 Success The message status set to DLNG.
    2007-10-15 10:47:51 Success Delivering to channel: ReceieverChannel_RFC
    2007-10-15 10:47:51 Success MP: entering
    2007-10-15 10:47:51 Success MP: processing local module localejbs/RfcAFBean
    2007-10-15 10:47:51 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
    2007-10-15 10:47:51 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
    Time Stamp Status Description
    2007-10-15 10:47:51 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
    2007-10-15 10:47:51 Success The asynchronous message was successfully scheduled to be delivered at Mon Oct 15 10:52:51 SAST 2007.
    2007-10-15 10:47:52 Success The message status set to WAIT.
    2007-10-15 10:52:52 Success Retrying to deliver message to the application. Retry: 1
    2007-10-15 10:52:52 Success The message was successfully retrieved from the receive queue.
    2007-10-15 10:52:52 Success The message status set to DLNG.
    2007-10-15 10:52:52 Success Delivering to channel: ReceieverChannel_RFC
    2007-10-15 10:52:52 Success MP: entering
    2007-10-15 10:52:52 Success MP: processing local module localejbs/RfcAFBean
    2007-10-15 10:52:52 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
    and the message in sxmb_moni shows as it is processed sucessfully and
    at reciever rfc as
    Receiver channel 'ReceieverChannel_RFC' for party '', service 'CD103' (internal name 'RfcClient[ReceieverChannel_RFC]')
    Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
    Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
    Current pool size: 0, maximum pool size : 1
    waiting for your great answer.
    cheers.
    seeta ram.

  • Problems at receiving messages at RFC-Sender

    Hi all,
    i have configured the following scenario in NWDS for testing a message flow in PO:
    SOAP request comes into PI -> map Request to RFC -> send request to ERP Test System -> wait for RFC Response -> send to PI -> map Response to SOAP -> send to File
    Therefore i have, amongst others, created a RFC Channel for sending the RFC response to the mapping operation.When i run the scenario for the first time everything worked pretty well without any error messages. But after testing it the second time the message got stuck in the ERP Test System and couln't be forwarded anymore. It turned out that whenever i deployed the channel with some config changes, the message flow worked for the first time, but crashed after every following.
    In the error log i get the following message:
    java.lang.RuntimeException: Bean Z_PP_PDES_RESPONSE not found on host xxx, ProgId =RFC_HMC100_POD: Object not found in lookup of Z_PP_PDES_RESPONSE.
    at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:121)
    at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of Z_PP_PDES_RESPONSE.
    When i look in the message log at the same position of a successful message, the log says...
    MP: processing local module localejbs/RfcAFBean
    ... which is actually the module defined in the channel.
    So for me it looks like that after the first run something in the module config crashes and the channel tries to use Z_PP_PDES_RESPONSE instead of the RfcAFBean.
    Any help very much appreciated!!!
    Thanks,
    Maurice

    Issue has been solved! There has been a running jco server with same program id as the one of the scenario. This led to complications. After stopping the server it worked perfectly...

  • PI 7.1 --- rfc scenario---bean stfc_connection not found on host

    Hi,
    I am  trying to execute STFC_CONNECTION  but   getting  an error bean stfc_connection not found on host
    I had checked following things..
    1)SM59 connection tested and it is working fine.
    2I)imported  RFC in to PI created sender, receiver communication channels,sender, receiver agreements etc..
    3)Checked all the threads in SDN could n't find any solution..
    Please suggest me if you know anything about this issue
    Thanks in advance

    Dear Gowri,
    Concerning the error you are getting, kindly perform a Full CPA Cache refresh using the URL :
      - http://<host>:<Java-Port>/CPACache/refresh?mode=full
    If that does not help, please check the following :
    - Have you imported the structure of STFC_CONNECTION function module from the R/3 system into the integration repository?
    - In integration directory, check the RFC_sender and RFC_receiver communication channels, click on module tab, see if localejbs/RfcAFBean is listed there. If not, please add it.
    Also, kindly go through the note : 1135947 which might help you.
    Best Regards
    Nishwanth

  • SOAP Client Error:- INVALID CHANNEL

    Dear Friends,
                           I am configuring a simple SOAP to RFC syn scenario .
    after generating the wsdl when  I am testing it using SOAP UI  the following error is thrown:-
    !!!!!1<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>Exception</code>
                   <text>java.lang.Exception: invalid channel (party:service:channel) = &lt;null>
    As a part of debugging i tried to test my sender channel :-
    using this URL "http://sapxi:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:JEEVANBS:SOAPTORFC_SENDER_CC"
    In respose I got
    <?xml version="1.0" ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>f5c38e38b7b239b8a1a2e3cfbb70b72a</channelID>
      <name>SOAPTORFC_SENDER_CC</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>JEEVANBS</service>
      </s:ChannelInfo>
    No wi think my Sender Channel is fine;
    The URL is used in generating WSDL is:-Link:[http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
    channel=:<service>:<channel>]
    and by tring the same in the browser i am getting
    (MessageServlet OK ).
    Now i dont understand where I went wrong.
    Please help.
    Jeevan.

    http://<host>:<port>/CPACache
    CPA Cache: Monitoring
    View cache update history
    Current CPA cache service initialization: DIRECTORY
    DISPLAY CACHE CONTENT
    CPAObject: (Channel) keys: ObjectId=09c2240d575430f7a460ff5a1c18f682 values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">RECEIVER.XML</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">C:/TEMP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=FILE_RECEIVER_CC
    CPAObject: (Channel) keys: ObjectId=fc51c44174c739fbbf3ce80867e9e7c4 values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.processingLocked</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.processingOrder</Name><Value dataType="xsd:string">byName</Value></Attribute><Attribute xmlns=""><Name>file.checkFileModification</Name><Value dataType="xsd:string">0</Value></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">inactive</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.sourceFileName</Name><Value dataType="xsd:string">sender2.xml</Value></Attribute><Attribute xmlns=""><Name>file.pollInterval</Name><Value dataType="xsd:string">30</Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.additionalPayloads</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.archiveDir</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.retryInterval</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveWithTimestamp</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.sourceDir</Name><Value dataType="xsd:string">c:/temp</Value></Attribute><Attribute xmlns=""><Name>file.processingMode</Name><Value dataType="xsd:string">delete</Value></Attribute><Attribute xmlns=""><Name>file.qualityOfService</Name><Value dataType="xsd:string">EO</Value></Attribute><Attribute xmlns=""><Name>file.addPayloadNames</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.queueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollIntervalMsecs</Name><Value dataType="xsd:string"></Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=sender_file2
    CPAObject: (Channel) keys: ObjectId=f5c38e38b7b239b8a1a2e3cfbb70b72a values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers= AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=SOAP EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=SOAP Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>PersistDuration</Name><Value dataType="xsd:timePeriod">2592000000</Value></Attribute><Attribute xmlns=""><Name>isMessageSecurity</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XMBWS.UseEncoded</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>XMBWS.KeepAttachments</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XI.Interface</Name><Value dataType="xsd:string">SOAPTORFC_SENDER_MI</Value></Attribute><Attribute xmlns=""><Name>XMBWS.UseQueryString</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XI.QueueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>XI.QualityOfService</Name><Value dataType="xsd:string">BE</Value></Attribute><Attribute xmlns=""><Name>XI.InterfaceNamespace</Name><Value dataType="xsd:string">http://soap_to_rfc</Value></Attribute><Attribute xmlns=""><Name>XMBWS.KeepHeaders</Name><Value dataType="xsd:boolean">0</Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=SOAP Channel=SOAPTORFC_SENDER_CC
    CPAObject: (Channel) keys: ObjectId=3cc5f044fc4b3ec09ff525970087d20c values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">inactive</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">receiver2.xml</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">c:/temp</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=receiver2_file_cc
    CPAObject: (Channel) keys: ObjectId=06316b8e39743e149b7d4984d85d7a76 values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.processingLocked</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.processingOrder</Name><Value dataType="xsd:string">byName</Value></Attribute><Attribute xmlns=""><Name>file.checkFileModification</Name><Value dataType="xsd:string">0</Value></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollInterval</Name><Value dataType="xsd:string">20</Value></Attribute><Attribute xmlns=""><Name>file.sourceFileName</Name><Value dataType="xsd:string">SENDER.XML</Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.additionalPayloads</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveDir</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveWithTimestamp</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.retryInterval</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.sourceDir</Name><Value dataType="xsd:string">C:/TEMP</Value></Attribute><Attribute xmlns=""><Name>file.processingMode</Name><Value dataType="xsd:string">delete</Value></Attribute><Attribute xmlns=""><Name>file.qualityOfService</Name><Value dataType="xsd:string">EO</Value></Attribute><Attribute xmlns=""><Name>file.addPayloadNames</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.queueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollIntervalMsecs</Name><Value dataType="xsd:string"></Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=FILE_SENDER_CC
    CPAObject: (Channel) keys: ObjectId=f311e58a8d643de698d69aa267c22966 values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers= AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=RFC EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=RFC Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>repository.QoP</Name><Value dataType="xsd:string">open</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>messageServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>loadBalancing</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>logonLanguage</Name><Value dataType="xsd:string">EN</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>maxPoolSize</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonUser</Name><Value dataType="xsd:string">SAPUSER</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.systemID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonLanguage</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>QoP</Name><Value dataType="xsd:string">open</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>systemNumber</Name><Value dataType="xsd:string">00</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverProgramID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>systemID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.SNCPartnerName</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.authenticationModeBasicSNC</Name><Value dataType="xsd:string">basicSAP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>externalServer</Name><Value dataType="xsd:string">SAP</Value></Attribute><Attribute xmlns=""><Name>repository.messageServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverGatewayService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>additionalParameter</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>logonGroup</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonGroup</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverGatewayHost</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonClient</Name><Value dataType="xsd:string">800</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonPassword</Name><Value isPassword="true" encryption="hw" dataType="xsd:string">AUNENT0wOj0=</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.loadBalancing</Name><Value dataType="xsd:boolean">0</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonPassword</Name><Value isPassword="true" encryption="hw" dataType="xsd:string">AQ==</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>applicationServer</Name><Value dataType="xsd:string">RRM</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>SNCPartnerName</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.additionalParameter</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>repository.logonUser</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>messageServerService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.applicationServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.messageServerService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonClient</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.systemNumber</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.additionalRepository</Name><Value dataType="xsd:boolean">0</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>authenticationModeBasicSNC</Name><Value dataType="xsd:string">basicSAP</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=RFC Channel=SOAPTORFC_RECEIVER_CC
    CPAObject: (Channel) keys: ObjectId=d8b2da4e236131e594ea8b9305a65a7c values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">IDOC.XML</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">C:/TEMP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=RCV_FILE_IDOC_CC
    CPAObject: (Binding) keys: ObjectId=e05905bf213f3b3cbb6c441ddbd72c0a values: Direction=I ActionNamespace=http://flie_to_file_2 ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=sender1_mi AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=fc51c44174c739fbbf3ce80867e9e7c4
    CPAObject: (Binding) keys: ObjectId=03109a4771e83c639ca0dc1263d49be5 values: Direction=O ActionNamespace=http://file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=FILE_IN_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=09c2240d575430f7a460ff5a1c18f682
    CPAObject: (Binding) keys: ObjectId=08cf01c7cb1a3b0fa0fd0d0f4023279b values: Direction=O ActionNamespace=http://Training/file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=RECEIVER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=09c2240d575430f7a460ff5a1c18f682
    CPAObject: (Binding) keys: ObjectId=91652630b1eb33d88757e17b714a3c04 values: Direction=I ActionNamespace=http://soap_to_rfc ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=SOAPTORFC_SENDER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=SOAP MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>wsse.namespace</Name><Value dataType="xsd:string">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd</Value></Attribute><Attribute xmlns=""><Name>verifySignatureKeyStore</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>verifySignatureIssuerDN</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>verifySignatureSubjectDN</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ChannelId=f5c38e38b7b239b8a1a2e3cfbb70b72a
    CPAObject: (Binding) keys: ObjectId=e8bb20ce05103c18834ae4c226bed7c7 values: Direction=I ActionNamespace=http://file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=FILE_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=06316b8e39743e149b7d4984d85d7a76
    CPAObject: (Binding) keys: ObjectId=2b26714c0b85307981f91ffc66f18006 values: Direction=O ActionNamespace=http://flie_to_file_2 ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=receiver1_mi AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=3cc5f044fc4b3ec09ff525970087d20c
    CPAObject: (Binding) keys: ObjectId=9d0a49a48df33131ad80937d45bc4d49 values: Direction=O ActionNamespace=http://soap_to_rfc ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=SOAPTORFC_RECEIVER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=RFC MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=f311e58a8d643de698d69aa267c22966
    CPAObject: (Binding) keys: ObjectId=0cb0b225a81a3824b6da3e22e3a07a87 values: Direction=O ActionNamespace=http://IDOC_TO_FILE ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=IDOC_TO_FILE_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=SAPRRM AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=d8b2da4e236131e594ea8b9305a65a7c
    CPAObject: (Attributes:Channel:RFC:OUTBOUND) values: repository.QoP=open messageServer= loadBalancing=false logonLanguage=EN maxPoolSize=1 logonUser=SAPUSER repository.logonLanguage= repository.systemID= adapterStatus=active QoP=open systemNumber=00 serverProgramID= additionalParameterTable=com.sap.aii.af.service.cpa.TableData@136efa7 systemID= repository.SNCPartnerName= repository.authenticationModeBasicSNC=basicSAP externalServer=SAP repository.additionalParameterTable=com.sap.aii.af.service.cpa.TableData@1afe177 serverGatewayService= repository.messageServer= additionalParameter=false repository.logonGroup= logonGroup= serverGatewayHost= logonClient=800 logonPassword=AUNENT0wOj0= repository.logonPassword=AQ== repository.loadBalancing=false applicationServer=RRM SNCPartnerName= repository.additionalParameter=false repository.logonUser= messageServerService= repository.applicationServer= repository.logonClient= repository.messageServerService= repository.additionalRepository=false repository.systemNumber= authenticationModeBasicSNC=basicSAP
    CPAObject: (Attributes:Binding:File:OUTBOUND) values:
    CPAObject: (Attributes:Binding:RFC:OUTBOUND) values:
    CPAObject: (Attributes:Binding:SOAP:INBOUND) values: wsse.namespace=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd verifySignatureKeyStore= verifySignatureSubjectDN= verifySignatureIssuerDN=
    CPAObject: (Attributes:Binding:File:OUTBOUND) values:
    CPAObject: (Attributes:Binding:File:OUTBOUND) values:
    CPAObject: (Attributes:Channel:File:INBOUND) values: xml.documentNamespace=null ftp.user=anonymous ftp.sourceDir=null file.checkFileModification=0 file.adapterStatus=inactive ftp.processingMode=test file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1fb80cf file.execute= file.sourceFileName=sender2.xml file.pollInterval=30 ftp.archiveOnFtpServer=false xml.recordsetNamespace=null file.archiveDir= file.encoding= ftp.transferMode=bin file.archiveWithTimestamp=false file.sourceDir=c:/temp file.processingMode=delete file.qualityOfService=EO ftp.anonymous=false xml.recordsetStructure=null ftp.port=21 file.advanced=false xml.recordsetsPerMessage=null file.pollIntervalMsecs= xml.keyfieldName=null file.processingLocked=false ftp.host=null file.processingOrder=byName xml.documentName=null file.type=bin file.addPayloadParams=com.sap.aii.af.service.cpa.TableData@c5bd01 ftp.password=ftp file.additionalPayloads=false file.retryInterval= xml.recordsetName=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1fbc471 file.addPayloadNames= ftp.connection=permanently file.queueName= xml.keyfieldType=StrS  xml.documentSkipFirstRows=null
    CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=active file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1dec3f file.execute= file.targetFileName=IDOC.XML file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=C:/TEMP ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@814530 ftp.connection=permanently file.counterStep=1
    CPAObject: (Attributes:Binding:File:OUTBOUND) values:
    CPAObject: (Attributes:Binding:File:INBOUND) values:
    CPAObject: (Attributes:Binding:File:INBOUND) values:
    CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=active file.addParameterParams=com.sap.aii.af.service.cpa.TableData@e581c2 file.execute= file.targetFileName=RECEIVER.XML file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=C:/TEMP ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1a9fd8e ftp.connection=permanently file.counterStep=1
    CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=inactive file.addParameterParams=com.sap.aii.af.service.cpa.TableData@145974f file.execute= file.targetFileName=receiver2.xml file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=c:/temp ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1d104d0 ftp.connection=permanently file.counterStep=1
    CPAObject: (Attributes:Channel:SOAP:INBOUND) values: PersistDuration=2592000000 isMessageSecurity=false XMBWS.UseEncoded=false adapterStatus=active XI.Interface=SOAPTORFC_SENDER_MI XMBWS.KeepAttachments=false XMBWS.UseQueryString=false XI.QueueName= XI.QualityOfService=BE XI.InterfaceNamespace=http://soap_to_rfc XMBWS.KeepHeaders=false
    CPAObject: (Attributes:Channel:File:INBOUND) values: xml.documentNamespace=null ftp.user=anonymous ftp.sourceDir=null file.checkFileModification=0 file.adapterStatus=active ftp.processingMode=test file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1930d3d file.execute= file.sourceFileName=SENDER.XML file.pollInterval=20 ftp.archiveOnFtpServer=false xml.recordsetNamespace=null file.archiveDir= file.encoding= ftp.transferMode=bin file.archiveWithTimestamp=false file.sourceDir=C:/TEMP file.processingMode=delete file.qualityOfService=EO ftp.anonymous=false xml.recordsetStructure=null ftp.port=21 file.advanced=false xml.recordsetsPerMessage=null file.pollIntervalMsecs= xml.keyfieldName=null file.processingLocked=false ftp.host=null file.processingOrder=byName xml.documentName=null file.type=bin file.addPayloadParams=com.sap.aii.af.service.cpa.TableData@14a28ce ftp.password=ftp file.additionalPayloads=false file.retryInterval= xml.recordsetName=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1bd1406 file.addPayloadNames= ftp.connection=permanently file.queueName= xml.keyfieldType=StrS  xml.documentSkipFirstRows=null
    CPAObject: (Service) keys: ObjectId=606ce974c84f37a983f014e1d3f6d67b values: Service=JEEVANBS Party= ServiceType=BS
    CPAObject: (Service) keys: ObjectId=10c2d6f515c43629be60b9671dfb5326 values: Service=TEST Party= ServiceType=SR
    CPAObject: (ServiceIdentifier) keys: ObjectId=7fe7f1f60069b2d9db121585afd90e5d values: Service=JEEVANBS Party= ServiceSchema=LogicalSystem ServiceIdentifier=
    CPAObject: (ModuleSequence) keys: ObjectId=dedc7b4bb748a47830f244e3c5d79456 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=09c2240d575430f7a460ff5a1c18f682 ModuleType=L ModuleNamespace=0
    CPAObject: (ModuleSequence) keys: ObjectId=0475467f699834c80d2786ccc9281230 values: ModuleName=localejbs/RfcAFBean Position=0 ChannelId=f311e58a8d643de698d69aa267c22966 ModuleType=L ModuleNamespace=0
    CPAObject: (ModuleSequence) keys: ObjectId=360f00a2a25a77f3713162c6c0aba328 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=d8b2da4e236131e594ea8b9305a65a7c ModuleType=L ModuleNamespace=0
    CPAObject: (ModuleSequence) keys: ObjectId=6a430f286f924cbb522a8b879ba0aeff values: ModuleName=localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean Position=0 ChannelId=f5c38e38b7b239b8a1a2e3cfbb70b72a ModuleType=L ModuleNamespace=soap
    CPAObject: (ModuleSequence) keys: ObjectId=bf933cd5567345f2385df4854d8cfaac values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=fc51c44174c739fbbf3ce80867e9e7c4 ModuleType=L ModuleNamespace=0
    CPAObject: (ModuleSequence) keys: ObjectId=96af99731794cb61b2c217c8bc8bd9c7 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=3cc5f044fc4b3ec09ff525970087d20c ModuleType=L ModuleNamespace=0
    CPAObject: (ModuleSequence) keys: ObjectId=b9a4fcf7a0d7b115b96c01cb760e459c values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=06316b8e39743e149b7d4984d85d7a76 ModuleType=L ModuleNamespace=0
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=3025930377ab37a9978a279039f80b9e values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=SOAP AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=ee79718d103f3db39d8001892a09012a values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=RNIF AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=be8d625a7a143cf6b724f17ed9fc75be values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=Marketplace AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=7b88b1289df431cabbc58227fc562518 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=Mail AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=5f9815c5a6a934f8856756f25f21b552 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=BC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=2768c3679ef9355a95a6aed25b82d230 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=XI AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=34d11731f5e43144ab4da458750d7bb4 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=CIDX AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=b4d22907ab93382bbac6321aef9f866d values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=File AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=b9d29c6630363ebba0ec15d3bc80084a values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=RFC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=08ea74ec778939dfa31e166d4b23f357 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=JDBC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=be9ad1ffaf643ce58ccc2fd53e7e4504 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=HTTP AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=99648243744a3efea5952abe216b49f5 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=JMS AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
    CPAObject: (AdapterTypeMetaData) keys: ObjectId=8b95769f448d3977899254c65a2c8ec6

  • Problem in the scenario SOAP to RFC Syn

    Hello All,
    i developed one scenario for our client and development is same like below link.
    http://www.riyaz.net/blog/xipi-consuming-xi-web-services-using-web-dynpro-part-i/technology/sap/6/
    when i test the interface iam getting below error, Please tell me do i need to install any patch in Xi server or do i need to implement any note.
    My SAP XI server version 3.0 and Service pack:19
    2010-07-19 07:24:57     Operation performed     The message has been received by the mail system. Profile: XI URL: http://xxxxxxxxx:50000/MessagingSystem/receive/AFW/XI credential (User): XIISUSER
    2010-07-19 07:24:57     Operation performed     With the connection RFC_http: / / sap.com / xi / XI / System. Attempted placement of the message in the queue of requests.
    2010-07-19 07:24:57     Operation performed     Message queued dCaution
    2010-07-19 07:24:57     Operation performed     The message has been retrieved from the queue dCaution queries.
    2010-07-19 07:24:57     Operation performed     The status of the message has been activated on DLNG
    2010-07-19 07:24:58     Operation performed     Paper channel: CC_R_RFC
    2010-07-19 07:24:58     Operation performed     MP: entering
    2010-07-19 07:24:58     Operation performed     MP: processing local module localejbs/RfcAFBean
    2010-07-19 07:24:58     Error     MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
    2010-07-19 07:24:58     Error     Exceptions occurred for Adapter Framework: Exception in method process.
    2010-07-19 07:24:58     Error     The dissemination of the message to the application via RFC_http: / / sap.com / xi / XI / System failed due to com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.:
    com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method Process .. Enabled message "Failed".
    2010-07-19 07:24:58     Error     The status of the message has been activated on FAIL
    2010-07-19 07:24:58     Error     Return of the synchronous error message to the calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.: Com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception method in process ..
    Thanks and Regards,
    Chinna
    Edited by: chinnasapxi on Jul 19, 2010 10:55 AM
    Edited by: chinnasapxi on Jul 19, 2010 10:56 AM

    Hi Cinna,
    >just now i checked the RFC it is working
    this together with the header "Problem in the scenario SOAP to RFC Syn" is missunderstoobable. But ok, the error is inside RFC adapter: may be it cannot create the DIAG RFC call with the XML what you provided in RTW.
    To be shure to have sent the right XML send a message but use a Message Mapping with RFC module as target.
    Regards,
    Udo

Maybe you are looking for