Skip to Content
author's profile photo Former Member
Former Member

rfc adapter

Hi

I configured rfc adapter as given the config guide(same as below), but when i restart it throws an error: "Attempt to start RFC adapter failed: com/sap/mw/jco/JCO$Record "

Pl. let me know on how to solve this isse.

Thanks

Pandari

classname=com.sap.aii.rfcadapter.core.RfcAdapterModule

#

  1. ------------------------------------

  2. RFC ADAPTER CONFIGURATION PROPERTIES

  3. ------------------------------------

  4. Tue Jan 21 13:27:43 CET 2003

#

#

  1. 1. GENERAL SECTION

#

  1. 1.1 trace settings

#

RfcAdapter.trace=1

  1. -> adapter trace level 0 = none

  2. 1 = error

  3. 2 = standard

  4. 3 = request

  5. 4 = payload

  6. 5 = binary payload outbound

#

#RfcAdapter.traceStack=0

#RfcAdapter.listenException=0

#RfcAdapter.listenState=0

  1. -> additional trace switches (in general not needed)

#

RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log

  1. -> name of trace file (traces to stdout if not specified)

  2. NOTE: in a productive environment, the trace file should be written to the

  3. log-file directory of the Adapter Engine

#

  1. 1.2 connectivity settings

#

RfcAdapter.registerInbound=sourceBackend CRM

  1. -> space-delimited list of logical names for inbound R/3 systems subsections.

  2. The adapter will register with all R/3 systems defined in this list and

  3. those systems can send RFC requests into the XI via an RFC destination

  4. that has to be setup in SM59 to point to the RFC Adapter

#

RfcAdapter.accessInbound=toXmb

  1. -> logical name for inbound access to XMB subsection

#

RfcAdapter.registerOutbound=fromXmb

  1. -> logical name for outbound access from XMB subsection

#

RfcAdapter.accessOutbound=targetBackend DEV

  1. -> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.

  2. This is an option to speed up connection setup during request processing. The RFC Adapter

  3. preallocates sessions to all listed R/3 systems.

#

RfcAdapter.clientCloseConn=1

  1. -> close calling connections after call (1) or just reset session (0)

  2. NOTE: the reset mechanism is slightly faster for request processing. However, it does

  3. not re-connect after a target system shutdown and hence requires a restart of the

  4. RFC Adapter in such a situation.

#RfcAdapter.maxDynPools=128

  1. -> maximum number of dynamically allocated client pools to access outbound R/3 systems

#

#RfcAdapter.minDynPoolSize=4

  1. -> initial number of clients in dynamically allocated client pools

#

#RfcAdapter.incDynPoolSize=4

  1. -> increment number of clients in dynamically allocated client pools

#

#RfcAdapter.maxDynPoolSize=64

  1. -> maximum number of clients in dynamically allocated client pools

#

  1. 2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS

  2. (one subsection per incoming R/3 system; requires callback service user for repository access)

#

RfcAdapter.sourceBackendCRM.host=sealcrm

RfcAdapter.sourceBackendCRM.sysnr=00

RfcAdapter.sourceBackendCRM.progid=Rfc2XmbService

  1. -> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService

RfcAdapter.sourceBackendCRM.poolsize=2

RfcAdapter.sourceBackendCRM.unicode=1

  1. -> source system is Unicode installation (1) or not (0)

RfcAdapter.sourceBackendCRM.client=333

RfcAdapter.sourceBackendCRM.user=<crmuser>

RfcAdapter.sourceBackendCRM.passwd=xxx

RfcAdapter.sourceBackendCRM.lang=EN

#RfcAdapter.sourceBackend.trace=0

  1. -> enable RFC trace for this connection (1) or not (0)

#RfcAdapter.sourceBackend.sncName=<SNC_name_of_adapter>

  1. -> e.g. RfcAdapter.sourceBackend.sncName=p:CN=USERNAME, O=ORGNAME, C=DE

#RfcAdapter.sourceBackend.sncLib=<SNC_library_path>

  1. -> e.g. on Win2K: RfcAdapter.sourceBackend.sncLib=C:
    Program Files
    SECUDE
    SECUDE for R3
    secude.dll

#RfcAdapter.sourceBackend.sncQop=<SNC_quality_of_protection>

  1. -> 1,2,3,8,9 e.g. RfcAdapter.sourceBackend.sncQop=1

#RfcAdapter.sourceBackend.sncAcl=<SNC_access_control_list>

  1. -> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q

#RfcAdapter.sourceBackend.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE

#RfcAdapter.sourceBackend.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE

  1. -> details for peer ACL lists

#

  1. 3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE

  2. (only one entry possible)

#

RfcAdapter.toXmb.host=<xihost>

RfcAdapter.toXmb.sysnr=00

RfcAdapter.toXmb.poolsize=3

RfcAdapter.toXmb.client=111

RfcAdapter.toXmb.user=XIAPPLUSER

RfcAdapter.toXmb.passwd=xipass

RfcAdapter.toXmb.lang=EN

#RfcAdapter.toXmb.trace=0

#

  1. 4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE

  2. (only one entry possible)

#

RfcAdapter.fromXmb.host=<xi_host>

RfcAdapter.fromXmb.sysnr=00

RfcAdapter.fromXmb.progid=Xmb2RfcService

  1. this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59

RfcAdapter.fromXmb.poolsize=2

RfcAdapter.fromXmb.unicode=0

  1. -> source system is Unicode installation (1) or not (0)

#RfcAdapter.fromXmb.trace=0

#

  1. 5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS

  2. (one subsection per outgoing R/3 system; pre-allocated connection pools via service user)

#

RfcAdapter.targetBackend.host=<R/3host_dev>

RfcAdapter.targetBackend.sysnr=00

RfcAdapter.targetBackend.poolsize=3

RfcAdapter.targetBackend.client=020

RfcAdapter.targetBackend.user=user

RfcAdapter.targetBackend.passwd=xxx

RfcAdapter.targetBackend.lang=EN

#RfcAdapter.targetBackend.trace=0

#

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Mar 25, 2004 at 01:10 PM

    Hi Pandari,

    here is a working RFC-Konfiguration. Just replace the R/3-Backend System an XI with your.

    regards,

    Ly-Na Phu

    #

    1. RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE

    #

    classname=com.sap.aii.rfcadapter.core.RfcAdapterModule

    #

    1. ------------------------------------

    2. RFC ADAPTER CONFIGURATION PROPERTIES

    3. ------------------------------------

    4. Tue Jan 21 13:27:43 CET 2003

    #

    #

    1. 1. GENERAL SECTION

    #

    1. Passwortverschluesselung aktivieren

    PWD.tokenHandler=PWtokens

    1. 1.1 trace settings

    #

    RfcAdapter.trace=5

    1. -> adapter trace level 0 = none

    2. 1 = error

    3. 2 = standard

    4. 3 = request

    5. 4 = payload

    6. 5 = binary payload outbound

    #

    #RfcAdapter.traceStack=0

    #RfcAdapter.listenException=0

    #RfcAdapter.listenState=0

    1. -> additional trace switches (in general not needed)

    #

    RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log

    1. -> name of trace file (traces to stdout if not specified)

    2. NOTE: in a productive environment, the trace file should be written to the

    3. log-file directory of the Adapter Engine

    #

    1. 1.2 connectivity settings

    #

    RfcAdapter.registerInbound=sourceBackend_EKR

    1. -> space-delimited list of logical names for inbound R/3 systems subsections.

    2. The adapter will register with all R/3 systems defined in this list and

    3. those systems can send RFC requests into the XI via an RFC destination

    4. that has to be setup in SM59 to point to the RFC Adapter

    #

    RfcAdapter.accessInbound=toXmb

    1. -> logical name for inbound access to XMB subsection

    #

    RfcAdapter.registerOutbound=fromXmb

    1. -> logical name for outbound access from XMB subsection

    #

    RfcAdapter.accessOutbound=targetBackend_EKR

    1. -> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.

    2. This is an option to speed up connection setup during request processing. The RFC Adapter

    3. preallocates sessions to all listed R/3 systems.

    #

    RfcAdapter.clientCloseConn=1

    1. -> close calling connections after call (1) or just reset session (0)

    2. NOTE: the reset mechanism is slightly faster for request processing. However, it does

    3. not re-connect after a target system shutdown and hence requires a restart of the

    4. RFC Adapter in such a situation.

    #RfcAdapter.maxDynPools=128

    1. -> maximum number of dynamically allocated client pools to access outbound R/3 systems

    #

    #RfcAdapter.minDynPoolSize=4

    1. -> initial number of clients in dynamically allocated client pools

    #

    #RfcAdapter.incDynPoolSize=4

    1. -> increment number of clients in dynamically allocated client pools

    #

    #RfcAdapter.maxDynPoolSize=64

    1. -> maximum number of clients in dynamically allocated client pools

    #

    1. 2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS

    2. (one subsection per incoming R/3 system; requires callback service user for repository access)

    #

    1. VORSICHT: Es genuegt einen Eintrag fuer ein R/3-System zu definieren. Auch wenn ein

    2. R/3-System mehrere Mandanten hat, darf man nur einmal definieren. Es ist nicht mehr

    3. notwendig auch noch fur den Mandant 094 und 095 jeweils einen neuen Eintrag zu definieren.

    4. Es reicht nur fuer den Mandant 002 einmal festzulegen. Alle RFC-Aufrufe geht ueber diesen

    5. Konfigurationseintrag. Wenn man aus Versehen fuer den Mandanten 094 und 095 auch

    6. Eintraege definiert hat, dann funktioniert die RFC-Aufrufe vom System EKR nicht. Es scheint

    7. als wuerde nichts ankommen, man kann weder in sm58 noch in Monitoring etwas sehen!

    #

    1. R/3-System EKR, Nur einmal pro System!!!!

    RfcAdapter.sourceBackend_EKR.host=dbciekr.mn-man.biz

    RfcAdapter.sourceBackend_EKR.sysnr=29

    RfcAdapter.sourceBackend_EKR.progid=Rfc2XmbService

    1. -> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService

    RfcAdapter.sourceBackend_EKR.poolsize=5

    RfcAdapter.sourceBackend_EKR.unicode=0

    1. -> source system is Unicode installation (1) or not (0)

    2. Wenn R/3-Backend als Unicode konfiguriert ist, dann 1 setzen. Wenn nicht dann 0 setzen. Sonst funktioniert die RFC-Destination nicht!

    RfcAdapter.sourceBackend_EKR.client=002

    RfcAdapter.sourceBackend_EKR.user=xi_rfc_adap

    RfcAdapter.sourceBackend_EKR.passwd=xirfcpwd

    RfcAdapter.sourceBackend_EKR.lang=DE

    RfcAdapter.sourceBackend_EKR.trace=1

    1. -> enable RFC trace for this connection (1) or not (0)

    #RfcAdapter.sourceBackend.sncName=<SNC_name_of_adapter>

    1. -> e.g. RfcAdapter.sourceBackend.sncName=p:CN=USERNAME, O=ORGNAME, C=DE

    #RfcAdapter.sourceBackend.sncLib=<SNC_library_path>

    1. -> e.g. on Win2K: RfcAdapter.sourceBackend.sncLib=C:
      Program Files
      SECUDE
      SECUDE for R3
      secude.dll

    #RfcAdapter.sourceBackend.sncQop=<SNC_quality_of_protection>

    1. -> 1,2,3,8,9 e.g. RfcAdapter.sourceBackend.sncQop=1

    #RfcAdapter.sourceBackend.sncAcl=<SNC_access_control_list>

    1. -> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q

    #RfcAdapter.sourceBackend.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE

    #RfcAdapter.sourceBackend.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE

    1. -> details for peer ACL lists

    #

    1. 3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE

    2. (only one entry possible)

    #

    RfcAdapter.toXmb.host=mmsap011

    RfcAdapter.toXmb.sysnr=06

    RfcAdapter.toXmb.poolsize=5

    RfcAdapter.toXmb.client=002

    RfcAdapter.toXmb.user=XIAPPLUSER

    #RfcAdapter.toXmb.passwd=XIPASS

    RfcAdapter.toXmb.passwd=<!%xiappluser%!>

    RfcAdapter.toXmb.lang=DE

    RfcAdapter.toXmb.trace=2

    #

    1. 4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE

    2. (only one entry possible)

    #

    RfcAdapter.fromXmb.host=mmsap011

    RfcAdapter.fromXmb.sysnr=06

    RfcAdapter.fromXmb.progid=Xmb2RfcService

    1. this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59

    RfcAdapter.fromXmb.poolsize=5

    RfcAdapter.fromXmb.unicode=1

    1. -> source system is Unicode installation (1) or not (0)

    RfcAdapter.fromXmb.trace=5

    #

    1. 5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS

    2. (one subsection per outgoing R/3 system; pre-allocated connection pools via service user)

    #

    1. R/3-System EKR, Mandant 002

    RfcAdapter.targetBackend_EKR.host=dbciekr.mn-man.biz

    RfcAdapter.targetBackend_EKR.sysnr=29

    RfcAdapter.targetBackend_EKR.poolsize=5

    RfcAdapter.targetBackend_EKR.client=002

    RfcAdapter.targetBackend_EKR.user=xi_rfc_adap

    RfcAdapter.targetBackend_EKR.passwd=xirfcpwd

    RfcAdapter.targetBackend_EKR.lang=DE

    RfcAdapter.targetBackend_EKR.trace=5

    #

    1. -------------------------------------------

    2. END OF RFC ADAPTER CONFIGURATION PROPERTIES

    3. -------------------------------------------

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 29, 2004 at 04:26 PM

    Hi Ly,

    Thanks. This works. The only difference is "adapter guide" is incorrect. The source backend should be defined as mentioned in your document.

    pandari

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      HI there,

      We are trying to test the RFC adapter by making a RFC call from a R/3 system to another R/3 system through XI.

      When we test the RFC adapter we get the following error message:

      The error we got is:

      "4252: can not get business system".

      This happens when we call the BAPI_VENDOR_FIND function from SE37 on the remote destination (XI System) XD1_210_N which is the (Logical destination) RFC adapter definition .

      Thanks for any feedback!

      Rob

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.