SRFC_ADAPTER_SERVICE

Hi,
I am trying to send a message from a Java Proxy to a CRM system, but when I launch my porgram I always get
System error when calling the outbound RFC adapter (JCO.Server could not create server function 'SRFC_ADAPTER_SERVICE')
Does anybody know what could be the cause of this problem?

Hi Mario,
Check you RFC receiver communication channel parameters in the integration directory.
Regards
Prasad

Similar Messages

  • Error in pushing a request to R3 System using RFC Adapter

    I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
    the Application server of the  R3 box.
    In the Transaction SM58 I see and error saying "<i><b>Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:</b></i>"
    Here are the corresponding details:
    Caller: CENTRALADMIN
    Function Module: SRFC_ADAPTER_SERVICE
    Target System: AI_RFCADAPTER_JCOSERVER
    Host: .... (The XI Server)
    Program: SAPMSSY1
    Clnt: 100
    As per the SRFC_ADAPTER_SERVICE function module, the <i><b>purpose stated so...
    "This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."</b></i>
    By the by the RFC adapter is started and I can see no activity in the log after startup.
    I would really appreciate for any idea/leads in solving this. Thanks.<b></b>

    Here are the details
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
    RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
    classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
    RFC ADAPTER CONFIGURATION PROPERTIES
    Tue Jan 21 13:27:43 CET 2003
    1. GENERAL SECTION
      1.1 trace settings
    RfcAdapter.trace=2
    -> adapter trace level 0 = none
                           1 = error
                           2 = standard
                           3 = request
                           4 = payload
                           5 = binary payload outbound
    #RfcAdapter.traceStack=0
    #RfcAdapter.listenException=0
    #RfcAdapter.listenState=0
    -> additional trace switches (in general not needed)
    RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
    -> name of trace file (traces to stdout if not specified)
       NOTE: in a productive environment, the trace file should be written to the
             log-file directory of the Adapter Engine
      1.2 connectivity settings
    RfcAdapter.registerInbound=sourceBackendXD1
    -> space-delimited list of logical names for inbound R/3 systems subsections.
       The adapter will register with all R/3 systems defined in this list and
       those systems can send RFC requests into the XI via an RFC destination
       that has to be setup in SM59 to point to the RFC Adapter
    RfcAdapter.accessInbound=toXmb
    -> logical name for inbound access to XMB subsection
    RfcAdapter.registerOutbound=fromXmb
    -> logical name for outbound access from XMB subsection
    RfcAdapter.accessOutbound=targetBackend
    -> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
       This is an option to speed up connection setup during request processing. The RFC Adapter
       preallocates sessions to all listed R/3 systems.
    RfcAdapter.clientCloseConn=1
    -> close calling connections after call (1) or just reset session (0)
       NOTE: the reset mechanism is slightly faster for request processing. However, it does
             not re-connect after a target system shutdown and hence requires a restart of the
             RFC Adapter in such a situation.
    #RfcAdapter.maxDynPools=128
    -> maximum number of dynamically allocated client pools to access outbound R/3 systems
    #RfcAdapter.minDynPoolSize=4
    -> initial number of clients in dynamically allocated client pools
    #RfcAdapter.incDynPoolSize=4
    -> increment number of clients in dynamically allocated client pools
    #RfcAdapter.maxDynPoolSize=64
    -> maximum number of clients in dynamically allocated client pools
    2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
    (one subsection per incoming R/3 system; requires callback service user for repository access)
    RfcAdapter.sourceBackendXD1.host=db03
    RfcAdapter.sourceBackendXD1.sysnr=00
    RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
    -> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
    RfcAdapter.sourceBackendXD1.poolsize=5
    RfcAdapter.sourceBackendXD1.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.sourceBackendXD1.client=500
    RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
    RfcAdapter.sourceBackendXD1.passwd=********
    RfcAdapter.sourceBackendXD1.lang=EN
    RfcAdapter.sourceBackendXD1.trace=2
    -> enable RFC trace for this connection (1) or not (0)
    #RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
    -> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
    #RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
    -> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
    Program Files
    SECUDE
    SECUDE for R3
    secude.dll
    #RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
    -> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
    #RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
    -> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
    -> details for peer ACL lists
    3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.toXmb.host=web03
    RfcAdapter.toXmb.sysnr=00
    RfcAdapter.toXmb.poolsize=5
    RfcAdapter.toXmb.client=100
    RfcAdapter.toXmb.user=XIAPPLUSER
    RfcAdapter.toXmb.passwd=******
    RfcAdapter.toXmb.lang=EN
    RfcAdapter.toXmb.trace=2
    4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.fromXmb.host=web03
    RfcAdapter.fromXmb.sysnr=00
    RfcAdapter.fromXmb.progid=Xmb2RfcService
    this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
    RfcAdapter.fromXmb.poolsize=5
    RfcAdapter.fromXmb.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.fromXmb.trace=2
    5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
    (one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
    RfcAdapter.targetBackend.host=db03
    RfcAdapter.targetBackend.sysnr=00
    RfcAdapter.targetBackend.poolsize=5
    RfcAdapter.targetBackend.client=500
    RfcAdapter.targetBackend.user=XIAPPLUSER
    RfcAdapter.targetBackend.passwd=*******
    RfcAdapter.targetBackend.lang=EN
    RfcAdapter.targetBackend.trace=2
    END OF RFC ADAPTER CONFIGURATION PROPERTIES
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
    Fri Sep 24 09:50:09 EDT 2004 *****
    09:50:09 (6011): RFC adapter initialized
    09:50:09 (6031): RFC adapter started
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
    Name: AI_RFCADAPTER_JCOSERVER
    Program ID: Xmb2RfcService
    Action Type: Registered Server Program
    Gateway: web03  (Local XI box)
    Gateway Service: sapgw00 (00 is the system number)
    Name: XI_SERVER
    Program ID: Rfc2XmbService
    Action Type: Registered Server Program
    Gateway: db03  (R3 box)
    Gateway Service: sapgw00 (00 is the system number for R3)
    Both the entries are tested fine.

Maybe you are looking for