cancel
Showing results for 
Search instead for 
Did you mean: 

Web services standard SAP Web App Server questions

Former Member
0 Kudos

I'm trying to get a better understanding of how WAS handles web services, ie BSPs, protocols, and ports. This is for my more network and basis oriented brethren as I'm only an "app server guy". Plaese note that these are NOT J2EE questions:

1. SE80 controller view folder for the BSP application.

a) The URL field: is it getting populated during the installation or dynamically whenever the particular service protocol (HTTP and/or HTTPS) is active?

b) Transfer options - HTTPS selection - will it overwrite the URL protocol in the URL field below?

2. RZ10 instance profile.

a) icm/HTTPS/verify_client - 0 parameter, should it force the HTTP service not to get activated when SMICM is refreshed?

b) Is there another parameter that forces the service protocal inactive on the instance?

c) What is the single, if any, parameter that controls which protocol is defaulted for all BSP applications, if more than one protocol and port is open? Can it be overwritten? If so, where?

3. SICF logon customization for BSP.

In the security requirements on the service data tab:

a) Logon procedure - will selecting option button change or bypass a service protocol?

b) Security requirements - will selecting SSL option force HTTPS service protocol?

c) Basic authentication - will selecting Internet User change the selection of HTTPS service protocol?

4. SMICM service protocols and ports.

a) If there are multiple ports open what determines which one is selected to serve pages, is it the lowest port number in the given protocol? Is it the HTTP protocol before HTTPS?

5. General questions:

a) Is WAS using any other ports than those already active within SMICM?

b) Are some port numbers preferred to any other? I mean those above 1000.

c) Can an internal FQDN be used as icm/host_name_full parameter, e.g. myserver.home.home (ie one not ending with .com, .org., etc.)?

Thanks for any tips as I plan to use them to point the finger back at my "network guys" as they keep blaming WAS is the rotten apple in their infrastructure

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

closing this really old question (6 years old)