WebDynpro for Java Deploy and run error. URL port number is "-1".

[Former Member]

I've written a simple WDJ application (straight from the tutorials) using NWDS on my workstation.

When I want to run this, I need to configure a WAS Java server to run it. I have provided the host name and the instance number when prompted and NWDS then detected and reported on the SCS on that server.

When I choose my application and right click to "Deploy new archive and run" the build and deploy process appears to complete satisfactorily and a browser window is launched. However, the URL does not contain the correct port number and execution fails. The port number here should be 5nn00 where nn is my portal's SAP instance number; instead it is "-1".

http://portalhost.mycompany.com:-1/webdynpro/dispatcher/local/Welcome/WelcomeApp?SAPtestId=3

Obviously I'm missing something significant but I don't know what.

[Former Member]

Dear Nicholas,

When portal server is installed, it assigns a specific port for running the portal. Normally the port is 500XX when xx is your instance number. There seems to be some problem in your case.

Please carry out following steps to see/resolve the issue:

1. Open the visual administrator

2. Navigate to Dispatcher -> Services -> HTTP Provider

This HTTP Provider specifies the ports used by portal.

You change the ports to something like : (Port:80,Type:http)(Port:443,Type:ssl)

Save your settings and now open the browser and open the portal like http://<host>/irj/portal (because 80 is default port). If you specify some other port you need to enter like http://<host>:<port>/irj/portal

This should resolve your issue:

Enjoy

Best Regards,

Ravi

[Former Member]

Thanks Ravi

My portal is working fine on for the standard applications and iViews we've developed for the project. It's accessible through the standard SAP 5nn00 port as http://portal.mycompany.com:5xx00/irj.

The problem I encounter is that during the deployment of my new WDJ application my browser tries to connect to a URL which contains a port number of "-1" as shown in the URL in my original post. If I manually type in the URL in the previous paragraph, with the standard port number etc, the portal runs fine.

Murray

[Former Member]

Hi Murray,

Please check your J2EE Engine settings by navigating to Window > Preferences > SAP J2EE Engine.

Here you need to give the IP & Port of the server. This port is the SDM port number.

You can also verify if the J2EE ngine/SDM is working by opening Window > J2EE Engine (All nodes should be in Green).

Cheers,

Arafat

[Former Member]

My menu path is slightly different.

I'm running

SAP NetWeaver Developer Studio

SAP NetWeaver 7.1 Composition Environment SP07 PAT0003

Build id: 200902281924

Under window->preferences I have "SAP AS Java" which has a data page requesting the SAP System ID, the hostname and the instance number. When that information is completed and the instance is registered NWDS connects to the SAP server and finds additional instances such as the SCS.

This means I don't get to explicitly enter any SDM details. NWDS, presumably, is smart enough now to know what the default ports and connections are and to make the appropriate selection. Unfortunately, it doesn't seem to do so.

[Former Member]

--removed the incomplete message posted by mistake

[former_member201361]

Hi Murray,

Try this :

1. Stop the server instance.

2. Shutdown the server machine .

3. restart the server machine and start the server instance.

then deploy ur application ...

hope this will solve ur problem.

Thanks and Regards

[Former Member]

My server machine is the development server for a major project currently struggling to meet the critical path timeline. Restarting the portal instance might be a possibility but restarting the server (HPUX) is less achievable.

What is the rationale behind this suggestion please? In general I don't believe in rebooting servers or restarting applications without having some sort of expectation of success and that usually implies a degree of understanding of the underlying problem which is to be fixed by the restart.