RFC destination Java = ABAP system to wrong system

Hello everyone,
I have a NW04 Java system (WebAs 640, SP19), which has an RFC destination to an ABAP system.
The strange this is this: we changed the target system of the RFC connection to a different one (let's say from SID1 to SID2), they have different system numbers, different host names and different gateways. Only user and password we kept the same, as that's easier to maintain.
We have a self developed java application which uses this RFC connection.
When we call the application using only the <b>not</b>-fully-qualified hostname the RFC connection to the old (SID1) is used, but the destination is defined with SID2.
However, when we use the fully qualified hostname in the URL, it works with SID2 (which is correct).
Does anyone have an idea why that happens and what we can do to prevent that?
Regards,
Cornelia

Hi Mantosh,
it's an RFC connection entered in Visual Administrator of the Java System (service Destinations), so there's no possibility to set an RFC type like in SM59.
Of course you're right concerning the hostnames, but I was wondering how that could happen. Normally, it should read the data which I configured in the RFC connetion and use that.
We deleted temporary files and cookies and all from the workstation were we started the browser, even rebooted the workstation, but no effect.
Do you know any cache were the java system could have the old data left?
Regards,
Cornelia

Similar Messages

  • RFC Destination using ABAP / 4 driver

    hi all
          i want to create RFC Destination using ABAP / 4 driver (Transaction-SM59) so do anyone have detailed steps/any blog/code regarding that. Plz forward it.
    Regards
    Martin

    Martin,
    Hope this link is helpful
    http://help.sap.com/saphelp_nw04/helpdata/en/89/45aad99715462abdf09ec503e151e7/frameset.htm
    Regards
    Kavitha

  • Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14

    Hello SAP Friends! Our NW admin did a dual stack system copy where the ABAP server came from system 1 and the Java server came from system 2. This worked fine for ABAP (duh it was installed first), but the Java system copy was a disaster. the server started but many key services did not.
    Why?
    Many of the configuration entries were not generated properly. For example, a new, unknown SID was created, and many entries referenced System 1 (the ABAP source, not even the Java source). We were able to find and fix some incorrect config entries, but we still couldn't get all of the services we needed to work.
    I think NW is so complicated that such a configuration is probably impossible, but maybe I am wrong.
    Does anyone have tips? Or can confirm that this would never work?
    The current plan is to install the Java Server from scratch as an add-in, which is less effort than searching through all the config files without any certainty that it will work. Hopefully it will work.
    Many thanks in advance.

    Hi Matt,
    What kind of infos are you looking for? I didn't perform the copy, have just been trying to figure out how to get all of the Java stack's services to start properly. As far as I know, it was done using the standard System Copy wizard. The ABAP server was done as a central instance and then the Java server was copied and installed as a java add-in.
    I have asked the admin to post the details to this thread, but it would be helpful if you could mention what types of info and details you are looking for.
    Thanks and Best Regards,
    John

  • System showing wrong system uptime.

    - I got a very weird problem with my Solaris 10 system.
    - System is showing a wrong value of system uptime which is more than thousand days. We tried reboot, RAM & NVRAM changes, all SC parameters changed, but problem is same.
    - Can you please give me some clue or idea on this ?
    - A change of CMOS battery was performed some time back, but not sure if it causes the issue.
    ~Anoop

    Hello Anoop,
    What Kernel rev do you have on that system? (uname -a)
    The problem description would suggest you have an issue with your utmpx file, given that's what the uptime(1M) command references. If the value printed by uptime increases, but is not reset by a system reboot, then uptime is pulling out a very old value from the utmpx database. This would suggest that the utmpx, and possible the wtmpx files are not getting updated or written to as they should.
    You can use logadm(1M) to either truncate or rotate the utmpx/wtmpx databases.
    Have a look at the files to see when they were last updated
    Do other commands which access the utmpx/wtmpx databases also produce strange output? Commands such as:
    $ who -b (Should display the time of the last boot)
    $ who -u
    $ who -l
    $ last
    Regards,
    Steve

  • RFC destination for Sender System  in R/3 4.6c

    Hi All,
    I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?

    Hi Arul,
           One more important point u have missed.
    Program ID,
    When ur configuring sender service from RFC,The most important point is Program ID.
    Use some name and create it.Use the same name in SM59.
    s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
    Reghards
    chandra shekar

  • RFC Destination is required for R/3 receiver system

    Hi All,
    Is RFC destination required for R/3 receiver system? Scenario i,e File >XI> RFC
    How XI system communicate with R/3 receiver system?
    Regards,
    Sameer

    Hi,
    RFC dest is not required in this case, XI will communicate thru RFC channel which you will configure as receiver channel. Hence in this channel, you will mention the required parameters.
    Please search this fourm and you will get plenty for blogs with step - to -step details of configuring the FILE 2 RFC scenario.
    Regards
    Sai Ganesh

  • SWO1 - No destination could be determined for logical system

    Hi there,
    I am trying to call a remote transaction via SWO1, but I am getting the following error:
    No destination could be determined for logical system TSTCLNT120
    Message no. OL860
    Diagnosis
    You attempted to instantiate an object with the specified logical system within the distributed runtime environment. However, an RFC destination has not been defined for this logical system.
    System Response
    The object instance cannot be generated.
    Procedure
    Define the RFC destination or use the local runtime environment.
    I go to SW01 --> Type an object name "TSTC" --> Click TEST --> New Dialog window Clicked on the Full key --> Entered the Logical Name for remote system (ECC), and also Entered Key: SU01 --> When I click on the continue, I am getting the above mentioned error.
    I can clearly see that it is looking for mapping Destination for that Logical name. Can someone please tell me what t-code or table I need to go and map the Logical Name with a RFC destination?
    Thanks in Advance
    Kumar

    hi
    try these links
    Re: R/3 Connections in RFC destination node.
    Assign a logical system in RFC
    Regards
    Sajid

  • RFC DEstination Error

    After creating the Destination in sm59 I tested the connection.
    When testing the connection, it gives the result as
    Connection type:    R/3 connection                                                                               
    Logon:                      2  msec                        
       0  KB:                    0  msec                        
      10  KB:                    1  msec                        
      20  KB:                    1  msec                        
      30  KB:                    1  msec                        
    I'm trying to create a rfc destination to php in the same system with the same hostname in which SAP is also running...I'm working with ides.
    but when I try to run my php file inside sapclasses in www directory it gives an error as
    SAPRFC extension not loaded
    Message: This script use SAPRFC extension module for PHP and the extension isn't loaded. You can download it with installation instructions from http://saprfc.sourceforge.net. If you have already the extension compiled and installed, check your php.ini configuration

    Here's a full text of the error I receive
    <b>Error when processing your request
    What has happened?
    The URL http://<host_server>.com:<port>/sap/bw/BEx was not called due to an error.
    Note
    The following error text was processed in the system BQ1 : com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
    The error occurred on the application server <host_server> and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Form: IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE of program CL_RSRD_DISTRIBUTOR_KM========CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE of program CL_RSRD_SETTING===============CP
    START-OF-SELECTION of program RSRD_BROADCAST_PROCESSOR
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BQ1 in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server <host_server> in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server <host_server>. In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http-c:100-u:COLLINS -l:E-s:BQ1-i:<host_server>_BQ1_00 -w:0-d:20051012-t:121010-v: RABAX_STATE-e:CALL_FUNCTION_REMOTE_ERROR
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    </b>

  • Defunct RFC destination prevents server from starting

    Hi,
    We have EP7.0 SP8 installed in Windows/Oracle.
    There was an RFC destination defined pointing to a BI system and now the system is removed/renamed from the name space.
    When the j2ee engine is started it looks for the system and results RFC_COMMUNICATION_ERROR and changing the status of the server process to "Starting Apps" and hangs in there for ever.
    The dev_server0 log shows the following error: Is there a way to remove this RFC destination offline, without starting the server (assuming this is the root cause of th e problem   or is there something else is going wrong?
    Thanks for your time.
    [Thr 5112] *  LOCATION    SAP-Gateway on host sisbid00 / sapgw00
    [Thr 5112] *  ERROR       internal error
    [Thr 5112] *
    TIME        Tue Sep 19 17:51:34 2006
    [Thr 5112] *  RELEASE     700
    [Thr 5112] *  COMPONENT   NI (network interface)
    [Thr 5112] *  VERSION     38
    [Thr 5112] *  RC          -1
    [Thr 5112] *  MODULE      nixxi.cpp
    [Thr 5112] *  LINE        4329
    [Thr 5112] *  DETAIL      NiIGetSockName
    [Thr 5112] *  SYSTEM CALL getsockname
    [Thr 5112] *  ERRNO       22
    [Thr 5112] *  ERRNO TEXT  Invalid argument
    [Thr 5112] *  COUNTER     5487
    [Thr 5112] *
    [Thr 5112] *****************************************************************************
    [Thr 5820] Tue Sep 19 17:51:37 2006
    [Thr 5820] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]

    Ok I reinstalled the pulseaudio & libpulse upgrades and rebuilt phonon-pulse & kdemultimedia-kmix-pulse against the new versions and it appears to have resolved the issue. I had originally inspected the logs of X & KDM but did not see any errors or information regarding why X would suddenly drop whilst logging in.

  • RFC destination error in SM58

    Hi,
    We are getting an error in SM58 "P85040 does not exist".
    What could be the  reason for this error in PI system?
    When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
    Kindlly help.
    Thanks,
    John

    Hi John,
    The reason can be the host name you are assigning is not existing.
    In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
    You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
    Sachin
    Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

  • Declare rfc destination to receive idoc

    i am trying an example to declare rfc destination to receive idoc.  the directions say to create a new destination of type "L" with the name INTERNAL and desination NONE. When i try to create a new rfc desination with destination NONE is says there is already one there but it is of type "I".  It will not let me change this to type "L" and I cannot delete it.
    Any idea how to do this???
    Also when I create it says give a name of INTERNAL but i see no field which says "name".

    hi,
    u shud create rfc dest tye: R/3 connections...that is type 3.
    refer this:
    R/3 side settings
    1. SM 59 (RFC destinations)
    Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
    2. WE 21 (Ports in IDOC processing)
    Create a transactional port. Give the RFC destination created in this.
    3. BD 54
    Create a logical system.
    4. WE 20 (Partner Profiles)
    a. Create a new partner profile under partner type LS.
    b. Assign the message type in outbound parameters.
    c. Open the message type (Dbl click) and configure the receiver port to the port created.
    XI side settings.
    1. SM59 (RFC destination)
    Configure the RFC destination pointing to the R/3 system.
    2. IDX1 (Port maintenance in IDOC Adapter)
    Create a port and provide the RFC destination.
    [reward if helpful]
    regards,
    latika.

  • RFC Destination type for IDOC to FILE

    Hi,
    wat is the RFC Destination type for IDOC to FILE ?
    jeff

    hi,
    u shud create rfc dest tye: R/3 connections...that is type 3.
    refer this:
    R/3 side settings
    1. SM 59 (RFC destinations)
    Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
    2. WE 21 (Ports in IDOC processing)
    Create a transactional port. Give the RFC destination created in this.
    3. BD 54
    Create a logical system.
    4. WE 20 (Partner Profiles)
    a. Create a new partner profile under partner type LS.
    b. Assign the message type in outbound parameters.
    c. Open the message type (Dbl click) and configure the receiver port to the port created.
    XI side settings.
    1. SM59 (RFC destination)
    Configure the RFC destination pointing to the R/3 system.
    2. IDX1 (Port maintenance in IDOC Adapter)
    Create a port and provide the RFC destination.
    [reward if helpful]
    regards,
    latika.

  • Error in RFC destination SWU3

    Hi Team,
    Recently we have performed System Copy from Production to QAS system.
    After system copy we checked that workflow is not working properly in system and RFC destination
    WORKFLOW_LOCAL_xxx does not exist in system So we went to SWU3 and tried to create RFC destination from there but
    it is giving error :
    Error Creating RFC Destination
        Message no. SWF_CST006
    I have SAP_ALL,SAP_NEW and Super group in system.
    Can you please suggest what could be root cause of this error or from where I can get more details of this error.
    Shivam

    > Can you please suggest what could be root cause of this error or from where I can get more details of this error.
    check
    - the system log (SM21)
    - the workprocess trace
    Markus

  • RFC destination from XI ABAP engine to 4.5 B system

    I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
    It does not work and gives an error.
    <b>Error Details     DETAIL: NiIGetSockName</b>
    -Naveen.

    Hi Naveen,
    First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
    Plz. confirm...
    Regards,
    Audy

  • PI System Copy (JCO RFC destinations missing)

    Hi,
    We are doing a Homogeneous System Copy of a PI 7.0 system:
    - Source system --> PI 7.0 Production system ("PIP")
    - Destination system --> PI 7.0 Development system ("PID")
    We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
    Production system ("AI_RUNTIME_PIP"), is it OK?
    Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
    Thanks in advance.
    Jon Larrucea

    Hi Jon
    Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
    Creating RFC Destinations in the ABAP and Java Environments 
    http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
    Regards
    Mark

Maybe you are looking for