Problems with Synchronous Java Proxy

[Former Member]

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.

[stefan_grube]

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

[Former Member]

Hi Stefan.

I've checked this, and for "Business System Viewed J2EE Engine Cluster", I have this information:

System Element: SAP J2EE Engine Cluster: XID on xidev

XID is my integration server. When I click on this XID on xidev link I can see that the class name is defined to be SAP_J2EEEngineCluster, that is exactly the class that the JPR complains is missing...

I don't know, but it seems like this is the way to solve the problem... If you have any more suggestions, I thank you.

Regards,

Deise Lima.

[stefan_grube]

Did you try to remove the Web AS Java Business System and create it new?

It might be a cache problem.

Stefan

[Former Member]

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

[MichalKrawczyk]

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

[Former Member]

Hi Michal.

Thanks for answering.

My JPR in adapter monitoring is red, not green. In SLD Access, I've got exactly the same error:

SLD host:port = xidev.cantv.com.ve:50000

Error getting JPR configuration from SLD. Exception: No entity of class SAP_J2EEEngineCluster for prt.Java.null found

No access to get JPR configuration

Any other suggestion?

Thank you and Regards,

Deise

[MichalKrawczyk]

is your sld configured correctly ?

TCODE - SLDCHECK

regards,

michal

[Former Member]

Hi Michal.

Yes, my sldcheck functions correctly.

I'm using the Java Proxy Runtime in the XI Integration Server (not in a local integration engine) and I have many interfaces running on this server. In this way, this should not be a SLD communication problem.

Thank you!

Deise

[MichalKrawczyk]

are you sure all of the datails in the

communication channel are correct?

http://help.sap.com/saphelp_nw04/helpdata/en/5b/12b7e6a466456aa71ef852af033b34/content.htm

regards,

michal

[Former Member]

Yes, the communication channel configuration is following the instruction on help.sap.com.

And this is the same communication channel that I use for my asynchronous scenario.

Regards,

Deise

[Former Member]

Hi Deise,

What SP level do you have?

Can you also make sure in SLD, the BS you created has the right Integration Server assigned?

Hart

[Former Member]

Hi Hart.

I'm in SP9.

And yes, the BS I've created is asigned to the rigth Integration Server.

Regards,

Deise

[Former Member]

I suggest you should upgrade to SP11. I am using SP11 and do not have any problem with either inbound or outbound Java proxy.

Hart