http port for ICM service WebAS6.x0 (SAP BW)

[Former Member]

Hi,

we have BW on WebAS .. ICM Port for http in the profile is 8080, yet dev_icm trace file shows the ICM trying port 80, abandoning that, and activating http services on port 1080. Why whould it do that? Most confusing.

[Former Member]

Hi Stuart,

Can you share your ICM trace file entries here ?

Regards,

Sanjeev

[Former Member]

I think I have found the root of the problem.

Another program had already grabbed port 8080 before the SAP ICM starts up. I thought I had uninstalled that software, but some remnants of it must be lying around still grabbikng port 8080. It seems the SAP ICM tries it's configured port 8080, fails, falls back to 80, fails, then tries 1080 and succeeds. Must be a hardcoded thing.

I switch to a different port and it looks ok now.

Thanks

[former_member185954]

Hi,

HTTP protocol default port is 80, however alternatively 8080 is also considered as HTTP port, the Internet has evolved on UNIX , in UNIX all port numbers below 1023 are considered as restricted ones, so to facilitate anonymous access they probably came up with HTTP - Alt port number 8080, why specifically 8080... well it is simply because actual HTTP port number is 80! and the new one would be easy to remember if it was 2 times 80.

http://www.grc.com/port_8080.htm

Check the above link for the same, the site also describes many ports, you can check for yourself about the background.

Port 1080 is meant for providing SOCKS...

SOCKS is a system that allows multiple machines to share a common Internet connection.

Many products support SOCKS. A typical product for home users is WinGate. WinGate is installed on a single machine that contains the actual Internet connection. All the other machines within the home connect to the Internet through the machine running WinGate.

http://www.iss.net/security_center/advice/Intrusions/2003017/default.htm

Check the above link for more details.

Hope that helps

Regards,

Siddhesh