Use WebDispatcher for MI patches

[Former Member]

Hello,

We're using a SAP Webdispatcher for MI7.0

We have server SERV1 with icm http port 8005.

For the webdispatcher we have WEBD1 with port 8300 which connects to http port 8105 of the message server of server SERV1.

For the synchronization of data everything works fine via http://WEBD1:8300 because this resides on the ABAP side.

Now we want to distribute patches but therefore the webdispatcher has to connect to the J2EE side. The webdispatcher connects to SERV1 through it's message server but then it comes to the ABAP side and cannot find the patch. The url it tries to find doesn't use the icm port 8005 but the j2ee port 50500...

What do we have to do on the webdispatcher to make this work? Or do we have to change the behaviour of server SERV1?

Kind Regards,

Jeroen

[Jnouwen · Accepted solution]

(I am a colleague of Jeroen and try to solve the same problem)

What we want to realize is depicted here: http://help.sap.com/saphelp_nw70/helpdata/en/5f/7a343cd46acc68e10000000a114084/content.htm

The issue is that the forwarding of url's from the ICM on the ABAP stack towards the Java stack does not function.

According to the specs, the following two url's should give the same result on a double stack installation:

http://server.domain.com:8100/useradmin and http://server.domain.com:50000/useradmin

(where port 8100 is the message server port of the abap stack and 50000 the http port of the java stack)

The response for the first url is:

The termination occurred in system SID with error code 404 and for the reason Not found.

The selected virtual host was 0 .

The issue is actually not wether server.domain.com is a web dispatcher or a sap host. Both set-ups give the same (unexpected) result.

Thx for your reply !

[Former Member · Accepted solution]

1) the first url's port should be 8000. Please check smicm->goto->services, see what is there.

2) the second url: what is the system number of the dual stack? I guess it's not 00.

[Jnouwen · Accepted solution]

The example is indeed based on system number 00, 8100 is than the port of the message server (ms/http).

[Former Member · Accepted solution]

Hi,

We just received the solution from SAP support. The problem is solved by updating the j2ee enging. See note 1048692 - Various problems with HTTP requests via ICM - for more details on how this can be done.

Rgds.

[Former Member]

Hi

You can do this using the NetWeaver Administrator(NWA). In your NWA, go to Mobile Components link and in here for all the mobile components (addons, applications) that wish to deploy on the client, you can assign a web dispatcher value. Basically select the mobile component and at the bottom you will find values named Webpath, Webserver, Web dispatcher and Download Link. Just click on add web dispatcher button and in here enter http://<weddispatcher>:<port>. Now test the download link and check if the mobile component can be successfully downloaded. Once this is done, assign the mobile component to the client.

Hope this helps,

Best Regards

Sivakumar

[Former Member]

Hi,

I forgot to mention but we did already this step of assigning a webdispatcher value in the NWMA for the mobile component of the patch.

We can download the patch when testing the url http://SERV1:50500/me.......zip this works, when using url (which the mobile client requests) http://WEBD1:8105/me.....zip it doesn't work...

So there is a mapping problem to find the zip file on the correct place via the web dispatcher.

Kind regards,

Jeroen

[Former Member]

Hi,

I had the same problem. What I did was simple: I entered the correct URL (port 50500) in the download link and so whenever I want to download the data this link gets downloaded to the device and it is working fine. I know - I skip the dispatcher, but the result was the one that counted in my case.

Regards,

Oliver

Edited by: Oliver Kaluscha on Feb 24, 2008 9:17 PM

[Former Member]

If I understand you correctly you added that link in the mobile administrator as webdispatcher url?

This only works if the MI server is located in the DMZ. This is true in our case. The mobile client must download via the webdispatcher.

Kind regards,

Jeroen

[Former Member]

Hi,

and now I got it

Go to the visual Administrator of your J2EE server. I think there is a value missing/wrong in there. That was my error at the end...... sorry for the confusion.

In the Visual Admin -> Mobile -> Application -> JSP -> theApp (in my case sap.com_XAP-MBA.....

I opened the configuration details, went to the webserver and then changed the value of the webserver in there to the correct one - in our case the one for the WebDispatcher. So I entered the http://seerver.domain:port in there and set the custom flag at the end. Saved it, and from that moment on the WebDispatcher URL workd fine. No idea why the other setting in NWA was not working.

Hope it helps in your case as well.

Regards,

Oliver