Launch BEX analyzer on remote system

[Former Member]

Hi,

We are implementing NWBC and are using a "frontend" server to host the NWBC and then connect to the backend. We have all the WDA working fine, however i am struggling with the bex analyzer. I have included it as a URL alias via SM30_SSM_VAR from the frontend server to the backend, however

When i launch the link it doesn't connect to the correct client. My target system is client 300 and it tries to connect to client 010 which is my frontend server client.

If i execute the link directly in PFCG then it is working fine.

I tried to integrate a launchpad from LPD_CUST, however i can't see that launchpad reference at all 😞

I hope someone are able to help me out.

[Former Member · Accepted solution]

Hi Jakob,

Is client 010 the default client in the target system?

You could also send the sap-client URL parameter to force it to use client 300 (e.g. sap-client=300)

Hth,

Simon

[Former Member · Accepted solution]

Hi Simon,

Thanks for your response. I have tried to use the sap-client=300 parameter with no lock and 300 is the default client 😉

[Former Member · Accepted solution]

I'd suggest you use a tool like Fiddler (I assume you are using NWBC desktop client), to look at the HTTP traffic being generated. That might give you a clue as to what is going wrong.

Fiddler has become a very good friend of mine in the last few months!

[Former Member · Accepted solution]

Thanks for that, that at least gave me the error. It generates the url both with client 10 and client 300

GET /SAP/BW/BEX?QUERY=ZCATS_Q006&sap-client=010&sap-language=EN&sap-theme=sap_corbu&sap_client=300 HTTP/1.1.

Right now this link is generated via an alias in SM30_SSM_VAR, do you think i could use a launchpad to do this instead? or du you have another suggestion?

[Former Member · Accepted solution]

That looks a bit odd... sap_client and sap-client in the same request. Is sap-client specified at all in SSM_VAR?

Next thing I would probably do is set a breakpoint in the NWBC runtime classes /ui2/cl_nwbc_runtime35 (I think from memory), step through and try to see how it is generating this URL.

It might be bug, check your NWBC runtime version. Not sure about using an ABAP launchpad... do you mean then having a menu entry that calls the launchpad page and then link from there to the BEX Analyser?

[Former Member · Accepted solution]

Yeah something like that.

To be honest i have never used the launchpad inside  NWBC before, and i tried to add in a launchpad reference, but i can not use that as a link to the bex analyzer.

I have patched the NWBC abap to 43, so that shouldn't be the issue.

I will try with the debugger to see if i can get that to work.

[Former Member · Accepted solution]

Ok interesting observation is that i can use NWBC for desktop and then the URL is rendered correctly and i am send to the right client. But not in NWBC for HTML

[Former Member · Accepted solution]

Ok got it working now.

If you set the launch application to a stand alone, then it renders correctly.