cancel
Showing results for 
Search instead for 
Did you mean: 

WPINTEGRATION.JS could not find SAPWF_sendSessInfo()

Former Member
0 Kudos

Hi,

"WPINTEGRATION.JS could not find SAPWF_sendSessInfo() to send bbpwebmonitor's SessInfo to DSM Portals. DSM interface might have changed."

this is the error coming up in the Portal. I have gone through SAP-Note 897796 - which points to SAP-Note 595519.

In Note 595519, it is specified to include an EBP 3.X (and higher) in a portal 5.X (and higher). Where can i find EBP and how can it be included in the portal?

If anyone have integrated EBP in portal, please provide stepwise solution on how to do this?

We were using EP 7.0 SP10 with backend components ECC 6.0, SRM 5.0 and ESS/MSS BP 1.0 sp7 with java applications.

Thanks,

VV.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I realize this is an older thread; however, we are experiencing this problem in our EBP system.

Recently, we activated HTTPS (secured) communication on our EP machine. Could this be a result of the SSL activation?

regards,

Eric Green

Former Member
0 Kudos

Did you resolve this issue; we are in same situation and recently activated SSL in Portal.

Please help us.

Tiru

rpalotai
Participant
0 Kudos

Hi!

When you use SRM via Portal you have to be sure that protocol and domain is the same for both server.

This is because otherwise JavaScript can't access other JS code within a different frame.

The WPINTEGRATION.JS contains the integration functions for SRM to be used under the portal.

So portal Js and SRM JS must cooperate. If the above conditions are not met, then you will receive the above message. However this is only one reason for such an alert popup.

Other problem can be, when this JS file is out of date, so it is not compatible with portal EPCF (EP Client Framework). In this case try to find an updated WPINTEGRATION.JS file from an OSS Note, or install the latest SP, or just copy it from an updated SRM system. (But this latest one is not really recommended.)

Now another problem can be when the browser's local cache keeps an old version of the file, however the SRM server contains a correct version. So it is necessary to empty the local cache of the browser. In this case the tipical symptom is that only a few user is complaining about such popup.

Hope this helps you out, pls. reward points if you find it useful.

BR.

Richard