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

Problem creating JCo Destination

Hi All,

I am getting a strange problem creating JCo destinations.

I have created a Web Dynpro application on server A using adaptive RFC model that calls RFC located on server B.

When I go to Web Dynpro content administrator to create JCo destinations, the destinations are shown with red icon. I follow the regular steps to create the destinations pointing to server B, but the final message I get is "JCo destination created in SLD". The Icons against the destinations are still red whereas the JCo destinations are shown in SLD against the relevant WebAS Java system for server B.

Thus even though I try to create JCo destinations, they are showing in SLD but not in Content administrator. Can anybody suggest how to resolve this problem? Is this problem because I am trying to set up a connection to a server other than own server ?

Thanks in advance


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Feb 24, 2009 at 04:27 AM

    Hi Amit

    Did you define the Server B entry in host file of your system

    1. C:\WINDOWS\system32\drivers\etc ,open host file in wordpad

    2. * *//IP address *apcrmdev * //name of the system #AP CRM DEV Installation No-0000000000 // Other credentials of invoked system

    Let me know it it not clear to you.

    Best Regards

    Satish Kumar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 24, 2009 at 04:53 AM

    Please look at the below thread for help


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 24, 2009 at 06:09 AM

    In the content administrator, you can do a Test or Ping to the created JCo destinations for B.

    [Creating JCo Destinations|]

    Ensure that SLD is configured for J2EE A and SLD is running.

    [Troubleshooting JCo Destinations|]


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks folks for your inputs.

      Finally the problem was resolved. The reason was that the two systems A & B are linked to different SLDs. The workaround I found was to create destinations pointing to system A only and then edit them to update connectivity parameters for system B.

      However ,the couple of configurations I had missed were u2013

      1. Create a PUBLIC log on group in tcode SMLG on system B with u2018external RFC enabledu2019 checked.

      2. Maintain entry sapms<SID> 36<nn> in host file on system A where <SID> and <nn> are system id and system number respectively of system B .

      Thanks & Regards


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.