Clinet for RFC Connection in Java Installation

hi ,
I am in the process of installing Java Add on for EP.
I have BW installed in Client 100
But during instlaltion pls tell me teh client no i should give for RFC Connection

Hello Balaji,
In case of BW only one client can be used as BW client. Since your AS ABAP the BW client is 100 it has to be 100 in case of Java Add-in as well.
Regards.
Ruchit.

Similar Messages

  • Sample JAVA code using Resource Adapter for RFC Connections

    Hi Java Knowledgeable Ones.
    I have successfully deployed the SAP Netweaver J2ee Engine "Resource Adapter for RFC Connections to ABAP Systems" to my Web Application Server.  Now I need to develop a JAVA application that would utilize this deployed resource adapter.  The resource adapter specifies the SAPClient, UserName, and password.  I am thinking that the JAVA code to invoke this connection would therefore not need to provide this information as it should be available in the resource adapter.
    Do you have sample code that you could send to me showing how to do this?
    Thanks,
    Kevin

    Hi Kevin,
    this is actually no good style! You should not open the connection with the adaptor knowing the password. Usually it should work via a connection that uses only basic rights  and the user has already authenticated and is using his security ticket.
    For security handling see:
    http://help.sap.com/saphelp_nw04/helpdata/en/61/f8bc3d52f39d33e10000000a11405a/frameset.htm
    Regards,
    Benny

  • Standard way of mutual exclusion control for rfc connection

    Dear expert,
    I want to know the standard way of mutual exclusion control
    for rfc connection.
    I am going to create JAVA screens for ERP ABAP objects.
    As for SAP GUI screen, pessimistic locking is used when editing objects.
    On the other hand, pessimistic locking is defficult for JAVA screens,
    since most of lock objects on ERP are not available for RFC.
    Besides, I'm afrraid if locks are correctly deleted
    when something bad happens on screen.(i.e. Users close browsers.)
    Do you have any recommendations?
    Regards,
    Fukuhara Yohei

    Hello, we raised an OSS note.
    They answered it was not possible to lock tasks.
    Task completion is like a race, the first it completes it wins.
    Regards,
    Marco.

  • RFC connectivity through JAVA

    Hello sir,
    I have create 1 java class file which connects to SAP DB through RFC connection.
    I have put sapjco3.dll,librfc32.dll,sapjcorfc.dll in to the folder windows\system32.
    Its working fine on windowsXP, but not working on Windows Vista and windows server 2003.
    its giving error as
    java.lang.UnsatisfiedLinkError: D:\splerp3\sapjco3.dll: The application has failed to start because
    its side-by-side configuration is incorrect.
    please tell me what configuration i have to do for vista and server 2003.

    Hi guys,
    please pay attention to the given infos on the JCo download site. It says:
    Note: Starting with JCo 2.1.4 and JCo 2.0.11, JCo requires the Visual Studio .NET C/C++ runtime libraries on Windows platforms.
    Starting with JCo 3.0.0, it requires the Visual Studio 2005 C/C++ runtime libraries. See SAP note [684106|https://service.sap.com/sap/support/notes/684106] for details on how to install them.
    Installing the VC redistributable packages from Microsoft will solve this issue.
    Regards,
    Stefan

  • Program ID Required for RFC Connection

    Hi All,
    I'm trying to create a RFC Connection betwen SAP BI and SSIS (SQL Server Integration Services). In SM59 screen i'm unable to get the appropriate Program ID required for the connection. Could someone please help me in knowing how to get it.

    Yogesh,
    While creating TCP\IP type RFC destination, when you select Radio button "Registered server program", there you have to provide Program Id there. So for your information:
    Program Id is a string which can be anything even your name.
    i know only R3 and XI integration and in that case you will make your RFC communication channel active first with a program Id(ant thing) and with logon credentials of other system + gateway host and service.
    then use that program id in RFC destination and test it.
    If get empty request then RFC destination is ok.
    BR,
    Alok

  • Authorizations for RFC connections

    Hi everyone....
    what are the Authorizations required for the user when creating RFC connections in XI.
    Rewards,
    Varun Reddy.K

    Hi,
    Authorization for using RFC destinations
    http://help.sap.com/saphelp_nw04/helpdata/en/6b/af429b12e9214d9a2d6cba921b162f/frameset.htm
    Regards,
    Shabari

  • Help for RFC connection

    hi all,
           source systems when checked is fine but when i try to customize the extractors it says error "opening" rfc connection..any idea why?? during loading have a error saying idocs not posted and idocs with incorrect status..
    help wil be rewarded..
    regards'
    Rajendra

    Hi Rajendra,
    Go to SM59. Open the RFC for your source system by double clicking on it. Click on check connection. There's some issue with the RFC thats why you're seeing this error. Inform the Basis team. Thanks.
    Sumit

  • Authrisations for RFC connections

    Hi everyone....
    what are the Authorizations required for the user when creating RFC  connections in XI.
    Rewards,
    Varun Reddy.K

    Hi Varun,
                    I think you need following authorization adde to your roles, to create an RFC.
    S_RFC_ADM
    plz go thru following link for more information.
    http://help.sap.com/saphelp_nw04s/helpdata/en/84/d3eb4190966024e10000000a1550b0/content.htm
    hope this is helpful.
    PS Award ponis if this is helpful

  • Draft for RFC connection

    Hi Experts,
    could you write me pls a draft coding for an RFC connection?
    Thank you!

    You mean something like this:
    CALL FUNCTION 'Z_FUNCTION_NAME' DESTINATION 'PRD'.
    That's all there is to it.  You just add the Keyword DESTINATION and the name of a destination mainted in SM59 to the CALL FUNCTION statement.  Now that I have typed this, however, I question if this inquiry really belongs in the Web Dynpro ABAP forum. This seems more like a general ABAP question.
    Hint - for WDA specific functionality you can use the Service Call Wizard to generate the context and the logic to call a RFC.  Was that perhaps what you were refering to.

  • XML pay load for RFC call in java mapping

    Hi,
    I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    Say i have 2 import parameters(input1,input2) and one output(output1)......
    Thanks in advance,
    H.L.Babu

    >
    hlbabu123 wrote:
    > Hi,
    > I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    >
    > Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    >
    > Say i have 2 import parameters(input1,input2) and one output(output1)......
    >
    > Thanks in advance,
    > H.L.Babu
    have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
    in case u still have issues do get back

  • Authentication method for JCo connection in XSS installation

    Hi All,
    I have a query which perplexes me.  I am implementing XSS (ESS/MSS) on SAP Portal EP6 SR1 with an ECC5 backend for prototype purposes.
    When I follow SAP's help steps to setup JCo connections, it states that for the metadata connection you should use a security authentication method of 'User/Password', but for the application data connection you should use a security authentication method of 'Ticket'.
    Does anyone know why the difference in methods here?  Is it possible to use 'User/Password' for both?  Any thoughts would be appreciated.

    Hi john,
    User -ID /Pwd method can be used to access the backend for both types of Data as per your scenario.
    User -ID /Pwd method and logon tickets both can be used to access data in backend.
    The difference lies in the scenario with which you are accessing the back-end.
    If all your portal users are same as backend users then you can select Logon ticket methods.
    If they are going to be different then you need User-ID /Pwd method .
    Check the following link to get a clear picture:
    <a href="http://help.sap.com/saphelp_ep50sp2/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm">Scenario to use type of SSO</a>
    Hope it helps.
    Regards,
    Vivekanandan

  • Configuring RFC connections for load balancing.

    Hi ,
    We have the following landscape for our systems.
    The database is installed on z/os , db2 (mainframe). The central services( SCS and ASCS) are also on the mainframe. So the message server is on mainframe.
    The CI is on AIX and The DI is on AIX.
    We have Logon groups configured and load balancing Configured and is RFC enabled.
    1) When we connect to SAP using the SAPGUI and  the portal connection is made to either CI or DI depending upon the best response times.  Now recently we are running the mercury load testing, all the users are connecting to DI. Why are the users connecting to DI even though we have load balancing?
    2) I have a system with SID BP0, with one CI and one DI. The logon group is BP0 and the message server name is cyrix. Now I have other another system EP0. I have created a RFC connection from EP0 to BP0. In SM59 I have selected the load balancing option, and provide the message server name, SID and logon group name. The connection does not work. If I connect directly to the CI or DI the connection works. Please tell me how can I configure load balancing for RFC connections.
    Thanks
    Manmath.

    Dear 917996,
    There are two types of load balancing:
    - Client-side load balancing (setting up the tnsnames.ora on client side). More information here (http://ggsig.blogspot.co.uk/2012/04/client-side-
    load-balancing-in-oracle.html). Very good video produced my friend Igor Melnikov is here (http://www.dsvolk.ru/oracle/racdd4d/demos/video/loadbalance/client/clientloadbalance_viewlet_swf.html)
    -Server-side load balancing (remote_listener and setting service parameter clb_goal). Very good Igor Melnikov's video is here (http://www.dsvolk.ru/oracle/racdd4d/demos/video/loadbalance/server/serverloadbalance_viewlet_swf.html).
    I have read about client side and server side load balancing. By editing tnsnames.ora I have enabled client side load balancing which is suppose to select listeners at random. then why does it only go to second node?Could you please show your tnsnames.ora on client?
    Please can anyone help me to configure server side load balancing with SCAN. I have read many many post but couldn't find a clear answer.Based on your output (remote_listener string cmbtrnrac-scan:1521) you have already configured the server side load balancing.
    SQL> show parameter listener
    NAME TYPE VALUE
    listener_networks string
    local_listener string (DESCRIPTION=(ADDRESS_LIST=(AD
    DRESS=(PROTOCOL=TCP)(HOST=10.1
    7.67.214)(PORT=1521))))
    remote_listener string cmbtrnrac-scan:1521How many SCANs do you use? Do you use DNS?
    regards,
    Gennady

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection

    Hi all SDNers,
    Help is needed on error "WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection".
    This error occured on RCA -> Extractor FWK administration and go to managed system (PI) and from the log, i can see some extraction failed due to error message " Error when opening an RFC connection"
    consequently, JAVA performance data is not appearing in RCA -> workload analysis but work fine for ABAP and adapter engine.
    I've followed below notes and perform the troubleshooting step by step by still to no avail:
    Note 1332428 - Missing data in service sessions from BI/CCDB
    Note 1257308 - FAQ: Using EarlyWatch Alert
    Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP27
    Note 1265070 - Diagnostics - Setup of Managed Systems
    Note 1010428 - End-to-End Diagnostics
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/WorkloadAnalysis-Noapplicabledatafound
    steps that have performed:
    restarted agent
    enlarge RFC resource cap for solmandiag and none
    delete entire SID in SMSY and pull again from SLD, re-setup managed system
    restart PI system
    i've spent 2 days on troubleshooting this issue but lack of information in SMP and SDN, even in google.
    in table E2E_EFWK_STATUS and extractor E2E_JAVA_EXTRACTOR_IF, i see all WLI_ID ended with RC 96, MESSAGE = Error when  opening an RFC connection and LASTRECORDS = 0
    I strongly believe this is the issue that causing no applicable data found for JAVA data.
    fyi, we are on SOLMAN EHP1 SPS27.
    Any kind advise is most welcome.
    Thanks,
    Nicholas Chang

    Gosh! at last i found the solution!!
    I appreciate those who tried to help and i''m sharing the solution as i believe this is the purpose of SDN Forum and help others Netweaver Chap who facing the same problem:
    Problem faced:
    Extractor failed intermittently for WORKLOAD ANALYSIS (Introscope Data) due to error message "Error when opening an RFC connection"
    Due to the above error, performance data is not available in RCA workload analysis for J2EE engine.
    Possible Solution:
    1) Ensure both webadmin & SOLMANDIAG RFC working fine -> SM59 -> TCP/IP
    2) go to SE16 -> E2E_RESOURCES and change the resourcecap to 10 for SOLMANDIAG
    3) go to /smd/services -> Diagnostic System -> Advanced Setup -> Abap connectivity -> Connection Configuration and change server count to 10
    4) Restart webadmin (step 3 & 4 can perform in VA too)
    5) set gw/keepalive &  gw/reg_keepalive to value 0 in RZ11 (without reboot of instance)
    5) again go to SM59 -> TCP/IP -> SOLMANDIAG and put in the gateway host and gateway service correctly, don't leave this empty!!!! -
    > This is the main solution to solve intermittent failed RFC for extractor.
    Now, go back and monitor the extractor log and you should see no RFC error anymore and wait for 1 hour for the data to populate.
    Thanks!
    Nicholas Chang,

  • Source system error - RFC connection failed

    Hi Gurus,
                  I have installed ECC6 on my PC but not when i am trying to created the DS its not allowing me its saying appl comp hierarchy for source susyem "T90*" doesnt not exist.
    so tried going to source system -> done a check for my source system then i got the following errors
    Source system "T90*" is inactive
    Entry in outbound table not found
    Entry in inbound  table not found
    Basic type does not exist
    Check failed for RFC connection T90CLNT090 ; check destination
    can any one tell me how to fix this issue?
    Regards,
    Ravi

    Hi Ravi,
                Did you run appication component hierarchy in source system(TX-RSA9)
    then activate your data source
    then replicate in BW system.
    Check here for BW connectivity with source system.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/bi/stepbyStepBusinessIntelligence
    Thanks,
    Vijay.

Maybe you are looking for