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

Problems with Synchronous Java Proxy

Hi All.

I have a scenarium composed by a syncronous interface with a sender ABAP Proxy and a receiver Java Proxy.

When I try to execute it, I got the following error:

"SAP XI Java Proxy Runtime: Error getting JPR configuration from SLD. Exception: No entity of class SAP_J2EEEngineCluster for prt.Java.null found Please check availability of System Landscape Directory on XI Integration Server. See also trace file in log destination library_com.sap.aii.proxy.xiruntime_JPRTrace."

I have already created a Business system in SLD pointing to the "Web as Java" technical system created when the integration engine was installed.

What can be wrong?

Any help will be welcome.

Thank you.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Apr 21, 2005 at 09:33 PM

    Hi,

    you can check:

    http://server:port/mdt/amtServlet

    (adapter monitoring) if JPR has a green status first

    maybe you'll find some errors there

    Regards,

    michal

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 24, 2005 at 08:46 AM

    Check the associations of the Business System in the SLD:

    Go to "Content Maintenance"

    Choose subset "Landscape Description" Class "Business System". Choose your Java Business System. Click on "5 Associated Instances". Check for "Business System Viewed J2EE Engine Cluster".

    If this entry is not available, try to delete the business system and create this again, if this does not help, create the association manually.

    Hope that helps,

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Stefan Grube

      Hi All.

      I've just found out that this was never a problem with my Java Proxy.

      Although I see this error message in J2EE engine log, and the JPR appears red in the adapter monitoring, the scenario is working fine. The problem was with my message mapping that was receiving the message from the Java Proxy. It had a problem, and was not processing the message correctly.

      It's strange that I got this error message in the log and in the adapter monitoring, but the scenario is actually working.

      Thanks

      Deise

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.