Recommendations on maximum connections for RFC receiver channel

In the past I have bumped this up to 10 or 15 but never really understood the significance or impact this can have. How do we size this number? Any idea?
We may need to supply bunch of information to Basis on this before we resize it. Right now I get this for a certain interface which has huge volume.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_Upd_Invoice_RFC_Recv]96d0f28e47aa3214a8d893b51d627ca6 is exhausted. The current pool size limit (max connections) is 1 connections.
Thanks,
Pam

Hi Pam,
Please refer to SAP note 730870 at service.sap.com.  There is a lot of good recommendation from SAP here in regards to RFC adapter configuration for PI/XI 7.0 and 7.1.
thanks.
Jamie

Similar Messages

  • Which user type to user for RFC receiver channel

    Hi Forum,
    I m developing XI scenarios which include RFC receiver chhanel (in IB: Integration Directory), to call a function moule in a R/3,
    which kind of user should i use for this purpose, i mean to say,
    which user type:
                    SYSTEM
                    Dialog
                    Communication
                    System
                    Reference
    and what should be the roles of that user,
    which type of the user doesnt gets locked, on wrong attempts

    Hi,
    Generally S_RFC and S_SERVICE authorizations  are nedded while calling RFC module from R3. Also check for role S_RFC_ADM
    The backend should have the authorization to execute the RFC on the backend.
    You can test the module in R3 and create a role using PFCG assign the tcode - SU53 (authorization check) and also assign the S_RFC and S_SERVICE to role.
    Refer
    RFC Logon user authorizations
    Question on service userid - for RFC call
    End User Authorizations and Roles
    Calling R3 RFC via http
    For RFC different authorization object is requried. You can ask your basis team to add the relevant authorization object in a new role and then add the new role to any existing service user or better create a new system user and add the role.
    Thanks
    swarup

  • Error with RFC receiver channel

    Hi,
    Getting this below error for receiver RFC channel. Can anyone please look into this error urgently.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.adapter.rfc.core.config.RfcConfig.getChannel() of a null object returned from com.sap.aii.adapter.rfc.core.client.RfcClientPool.getConfig()

    Hi,
    Restarted but no result. Getting another error :
    Delivering the message to the application using connection RFC_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: JCO.Exception while calling Z_SD_XI_BAPI_CREATE_VA_SLSORD3 in remote system (RfcClient[CC_RFC_Z_BRONZE_VA_RCVR]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Could not open file /usr/sap/XP3/interfaces/va/br_vaout_20140401_04204.
    I do not understand why RFC receiver channel is giving this error.
    Can any one please look into it on priority.I need it to get resolved very soon.
    Thanks

  • Alert Management for RFC Communication Channel

    Hi All,
    I want to send notification to user using Alert Management in case of System Error in RFC Adapter.
    I tried with defining rule in RWB with * . But still I am not able to find notification in Inbox or Mail Inbox.
    Thanks.

    Infact it is working fine for JDBC CC.
    But in case of RFC Receiver CC it is niether apperas in Alert Inbox nor in Mail Inbox.
    Then there needs no more setting to be done. Are you sure that an error has been reported by the RFC channel (red symbol) and there is no restriction in Alert Configuration....like the interface name/ adapter type etc.
    Uncheck the option Suppress Multiple Alerts of this Rule option

  • How to set up connection for directv receiver, TV, and home theater system?

    Can some one please show me the CORRECT way to connect my Directv receiver (it has no HDMI), Panasonic Viera HDTV (has 3 HDMIs) and my Samsung home theater HT-Z510 (has 1 HDMI)? The second question is with the set up that you advise, can I play the TV sound through my home theater speakers? and How do I do that each time I want to listen the TV sound through my home theater speakers? I am new and confused about all this so please provide or explain step by step please. Thanks in advance.

    Making sense of your connections on a message board is never easy. Hopefully you can piece this information together.
    Direct TV box to Panasonic TV using S-video cable....assuming it's standard definition. Component video if the box is HD. Run standard stereo RCA cables to the appropriate input for sound threw the TV speakers.
    Your Panasonic TV will have a set of stereo(left/white,right/red) outputs. Run cable from that output into the same inputs on the Samsung surround unit. Use the sound units effects to acheive simulated surround. This is assuming you have no digital outputs on your box. If you do, you'll be able to get 5.1 when available using a digital connection.
    Good luck.
    Disclosure: Former BBY employee.

  • RFC receiver channel, message not reflecting in Receiver ECC system

    Hi All,
    We are using Receiver RFC adapter to call a custom RFC (ASynchronous call). It was working fine, But now after we made a few changes in the mapping. The message is successful in PI, but it is not visible in ECC. When I check in RWB, I think the payload is not going correctly to ECC.  I have re-imported the RFC and tried as well. It still does not work.
    Kindlhy let me know what to do.
    Rgds,
    Mithun

    Hi Rajhan,
    My abaper is doing that,  By that time, i just saw the payload in the message display tool(MDT) in RWB...
    it looks like some junk data
    "QT00010101000120120119201201202012012020121231USD38130511T-F399000110000010001585030512T-F299000110000010001210SP0000001002"
    where as in sxmb_moni of PI system the payload after mapping is
    "<?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:BAPI_QUOTATION_CREATEFROMDATA2 xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
    - <QUOTATION_HEADER_IN>
      <DOC_TYPE>QT</DOC_TYPE>
      <SALES_ORG>0001</SALES_ORG>
      <DISTR_CHAN>01</DISTR_CHAN>
      <DIVISION>01</DIVISION>
      <PMNTTRMS>0001</PMNTTRMS>
      <QT_VALID_F>20120119</QT_VALID_F>
      <QT_VALID_T>20120120</QT_VALID_T>
      <CT_VALID_F>20120120</CT_VALID_F>
      <CT_VALID_T>20121231</CT_VALID_T>
      <CURRENCY>USD</CURRENCY>
      </QUOTATION_HEADER_IN>
      <SALESDOCUMENTIN>381</SALESDOCUMENTIN>
    - <QUOTATION_ITEMS_IN>
    - <item>
      <ITM_NUMBER>30511</ITM_NUMBER>
      <MATERIAL>T-F399</MATERIAL>
      <PLANT>0001</PLANT>
      <TARGET_QTY>100</TARGET_QTY>
      <SHORT_TEXT />
      <MATL_GROUP />
      <CUST_GROUP />
      <PMNTTRMS>0001</PMNTTRMS>
      <PRICE_DATE />
      <SHIP_POINT>0001</SHIP_POINT>
      <TARGET_VAL>5850</TARGET_VAL>
      </item>
    - <item>
      <ITM_NUMBER>30512</ITM_NUMBER>
      <MATERIAL>T-F299</MATERIAL>
      <PLANT>0001</PLANT>
      <TARGET_QTY>100</TARGET_QTY>
      <SHORT_TEXT />
      <MATL_GROUP />
      <CUST_GROUP />
      <PMNTTRMS>0001</PMNTTRMS>
      <PRICE_DATE />
      <SHIP_POINT>0001</SHIP_POINT>
      <TARGET_VAL>210</TARGET_VAL>
      </item>
      </QUOTATION_ITEMS_IN>
    - <QUOTATION_PARTNERS>
    - <item>
      <PARTN_ROLE>SP</PARTN_ROLE>
      <PARTN_NUMB>0000001002</PARTN_NUMB>
      <NAME />
      <REGION />
      </item>
      </QUOTATION_PARTNERS>
      </ns1:BAPI_QUOTATION_CREATEFROMDATA2>"
    ANY SUGGESTIONS... This is PI 7.1 so its auto commit for the RFC receiver adapter rite. should i tick some option or what else can we do
    Rgds,
    Mithun

  • "Unauthorized" error for SOAP receiver channel

    Hi all,
    I have a scenario in which I am calling a .NET web service from a UDF in which the XML payload is constructed manually. I have configured a SOAP receiver channel. Also, since the web service needs certificate authentication, I have checked the corresponding parameter in the SOAP channel and selected appropriate client certificate.
    When I execute the mapping, I get the following error -
    com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RCV_IMWS_Change (Party: , Service: IMWS, Object ID: dda07d364ca73d4ab9e89e562a971b36) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'. Cause Exception: 'invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'.
    Is this related to error in certificate authentication process, OR wrongly formed XML payload OR anything else ?
    Regards,
    Shankar

    No. I didn't provide any login info. The web service doesn't specify username login requirement. Instead, it needs client certificate for authentication, which I provided in SOAP receiver channel.
    I am testing the web service by executing the message mapping. The web service was executed successfully from its 'Test Page' like for SAP web services we have web service navigator. So it runs ok from that test page, but gives error when called from UDF.
    Regards,
    Shankar

  • User dynamic for RFC communication channel

    Hello,
    we are developing an architecture for a bank company. We have a JAVA frontend and a R/3 backend, with a XI machine between both. All the authorizations are implemented inside the R/3 backend, and we need that all the users of the frontend exist on the backend. For this reason, when we define the RFC communication channel inside the integration builder configuration, the user must be dynamic. However, on the RFC communication channel only an static user-password is permitted. Could you tell us a possible way to define this user dynamically?

    Hello,
    SSO - Single Sign On is not supported in XI3.0, communication channels need a service id for talking with R3.
    We have been following up with SAP for SSO functionality. Its still in the pipeline. In the near future they may provide SSO.
    Regards,
    Naveen

  • Changing HTTP-Parameters for HTTP Receiver Channel

    Dear all,
    we have a partner we send files to using the simple HTTP adapter.
    We have different types of messages (interfaces) we send to the partner.
    Our partner expects the message type as a parameter of the URL. Such as http://xxx:000/xxx?msgtype=outbound
    In turn, the "outbound" could also be "inbound" - depending on the message type.
    I want to avoid using to services with two adapters.
    Thus, my question to you: Do you have an idea how I could manipulate the parameter's value?
    Thanks in advance,
    Helge

    Hi Helge,
    if you have Sp14 and above you can try setting the url
    dynamically in the mapping using Adapter-Specific Message Attributes in the http receiver channel:
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
    this way it should be no problem to change it
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Error in RFC Receiver Channel

    Hi Experts!
    In my scenarios i am using Receiver RFC for Look up. The RFC Channel is working fine in Dev server after we transport it to the QA. Now we are getting an error message :GenericRFCChannel" is not found in SXMB_moni.
    ID we have made the new configurations. When i have tested in IE the RFC is working fine. so we getting a strange why it is not working while runtime.
    Also i am having one doubt, Is it is mandatory to give the SAP BI details in the Software Component in the IE.Here our RFC are in SAP BI system.
    Pls give me some ideas to debug this issue. Thanks in Advance.
    Regard's
    Preethi.

    Hai !
    I have made a dummy changes nad reactive the channel even now i am getting the error as
    Give me some input to debug this issue. Pls.
    <Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
    <Trace level="1" type="T">Mapping-Object-Id:995C3CC70F88314694147FC81DEB10D0 </Trace>
    <Trace level="1" type="T">Mapping-SWCV:E179B290F08511DFAAACDF94C0A80049 </Trace>
    <Trace level="1" type="T">Mapping-Step:1 </Trace>
    <Trace level="1" type="T">Mapping-Type:JAVA_JDK </Trace>
    <Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_ </Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_
    Thrown:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:148)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626)
    at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92)
    at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60)
    at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87)
    at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:71)
    at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:119)
    at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72)
    at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
    at sun.reflect.GeneratedMethodAccessor555_10000.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy587_10000.processFunction(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183)
    at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:269)
    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:152)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.
    at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:84)
    at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:71)
    at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.__CreateStructures(_dealTicket_OPS_iOam_MM2_.java:276)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.preStart(AMappingProgram.java:307)
    at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.preStart(_dealTicket_OPS_iOam_MM2_.java:802)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:489)
    at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133)
    ... 40 more

  • RFC receiver adapter not getting timed out

    Hello Everyone,
    I have a scenario like this:
    Web-Service --> PI -->RFC (using receiver RFC channel)-->Response back to PI from RFC --> response back to Web-Service
    This RFC is taking more than 5 minutes to give response back to PI but still I am not getting timeout in PI.
    xiadapter.inbound.timeout.default is set to default value 180000.
    Is there any other place where I should check for setting timeout like 10 seconds for rfc receiver channel?
    Thanks,
    Satarupa

    Dear Satarupa,
    You need to set ICM timeouts at Integration Engine level.
    So go to SXMB_ADM and clic on Specific configuration. Edit table and set parameter as follow:
    Category = RUNTIME.
    Parameters = HTTP_TIMEOUT.
    Current Value = [segs] depens your needs.
    If you hasn't this parameter in SXMB_ADM set this parameter yourself.
    Related link.
    http://itsiti.com/increase-sap-icm-http_timeout-runtime
    Regards,
    Jose

  • Schedule Receiver RFC communication channel to call R3 RFC-FM.

    Hi,
    I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
    Below is my configuration detail:
    Configured:
    1. Receiver communication channel - RFC
    2. Receiver agreement with the RFC message type assigned.
    3. Scheduled receiver RFC communication channel via ATP daily
    *(It is possible to make scheduling job in R/3 but we are not considering this way)
    Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
    Thanks!
    Regards,
    SP

    Hi SP,
    As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
    For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
    For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
    I have 2 ideas:
    1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
    2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
    Please let me know still you have any doubts,
    Thanks,
    RK

  • Encoding in RFC Receiver

    Hello,
    I have trouble with the following scenario:
    Data from an R3 system is obtained by an RFC call and then send via SOAP to a 3rd party system.
    On the R3 system the data is encoded in different codepages which need to be converted to UTF-8 before sending them via SOAP.
    So I want to use an adapter module in the RFC receiver channel to make this conversion.
    Unfortunatelly it seems like the data I am receiving in the adapter module is already converted to UTF-8, but from the wrong codepage.
    For example I am expecting data to be sent to me in ISO-8859-9 and there should be the letter I with a dot above it in the payload which equals hex "c4 b0" in UTF-8. But instead I am finding "c3 9d" which is is the letter Y with acute. When I now look into the ISO-8859-9 code table, I find that my c4 b0 letter has the code DD. The letter I am getting instead is not in the ISO-8859-9 table, but it is in the ISO-8859-1 table.. and guess where, it also has code DD. The same goes for other letters.
    So it seems the payload I am getting is already in UTF-8, but got converted to UTF-8 from the wrong codepage (In this case it seems like it was converted to UTF-8 from ISO-8859-1 instead of ISO-8859-9).
    What can I do to receive the payload in the right encoding?

    > When its unicode, you should receive it in UTF-8.
    Unicode or not, the RFC adapter always converts the payload into UTF-8, so there is nothing left to do here.
    Regards
    Stefan

  • SOAP Receiver Channel 2 nodes inactive in Production system

    Hi All,
    We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
    But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
    Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
    Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
    Thank you.
    Regards,
    Sarvesh Desai
    Edited by: Sarvesh  Nispat Desai on Aug 25, 2010 5:25 PM

    There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
    The status "inactive or never used" is shown in channel monitoring at the following two times:
    1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
    2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
    In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
    Hope this answers your query.

  • Time out - SOAP Receiver Channel

    Hi All,
    My Scenario is Database --> PI (7.1) --> SOAP (synchronous) .
    The WebService is taking around 15 mins for giving the Response back to PI SOAP Adapter.But, because of Time Out at the PI SOAP Receiver adapter , I am getting "INBOUND EXPIRED" error.
    I referred the following links and tried to Increase the time out value in the SOAP Receiver communication channel - Module Parameters.But, this is not working.
    1. Note : 856597
    2.XMBWS.Timeout in soap receiver channel not working
    Can you please let me know if there any possible approach to increase the time out for SOAP Receiver Channel ?
    Thanks and regards,
    Midhusha.

    Hi,
    Have a look to below discussions
    XMBWS.Timeout in soap receiver channel not working
    SOAP Receiver communication channel Error
    Timeouts in SOAP Receiver Adapter
    Regards
    Aashish Sinha

Maybe you are looking for