How to find the RFC connection used by Portal

[aneeth_gajapathi]

Hi,

Could someone help me with this issue please?

Some of our users get a 500 internal server error when trying to access BW Reports through Enterprise Portal. Logs indicated that new RFC connections couldn't be opened to the BW Systems. So I checked SM04 in BW and found that the number of RFC connections has reached the maximum limit of 200. I could see some of the connections are more than 10 days old. I manually did an "End Session" for some of these old ones.

Before the connections reach the maximum limit again, I would like to know:

1. Why the old connections are still there with a status of "Connected"? Is there a Parameter/Configuration that will close these connections after users close the Portal?

2. How do I find the exact "RFC Destination" and "Jco RFC Provider" that are used by a specific portal report to connect to BW?

Any help will be much appreciated.

Thanks.

[Former Member · Accepted solution]

This message was moderated.

[aneeth_gajapathi · Accepted solution]

Thanks for the reply Ivan and sorry for not responding any sooner. I looked in to these notes and could see that we have all the parameters with the right values. I'm currently looking to add the Portal URLs to the white list of the Popup blocker and see if that helps in closing the connections on the ABAP side. One of the notes suggested trying this. I will keep you posted.

Regarding my second question, I still can't figure out which particular RFC Destination or Jco RFC Provider is used to connect from Portal to BW. We currently have only one Jco RFC Provider and I turned it off and tried using the portal. It was still able to connect to BW and run the reports. So I'm not sure how it is connecting to BW ABAP.

Thanks

[aneeth_gajapathi · Accepted solution]

This issue is related to another one in a separate thread. Please see there: http://scn.sap.com/thread/3780875