Setting up HTTP Provider Service to Accept Incoming Requests 

Use

If you want the HTTP Provider Service to accept incoming requests, you have to specify several properties that the system uses when opening the server sockets that carry out the client-server communication. These include:

·        The TCP port number on which HTTP Provider Service listens to for incoming HTTP requests.

·        The size of the queue of indications of incoming connections. If the queue is full and an indication of connection comes, the connection is refused by HTTP Provider Service.

·        The IP address that HTTP Provider Service uses to bind all incoming requests to. This property makes sense only when connecting to a host that has multiple addresses configured.

·        The number of threads that work simultaneously and process the indications of incoming connections from the queue.

You can configure more than one HTTP and SSL port to be opened. You must just provide the necessary entries as a value of the Ports property as described by the procedure below.

Procedure

Use the Visual Administrator tool to perform this configuration task:

...

       1.      Open the Properties tab of the HTTP Provider Service running on the dispatcher.

       2.      Edit the Ports property. The value of this property is a list of separate ports’ configurations, each contained within brackets. For example, the default value of this property contains two port configurations: (Port:50000,Type:http) and (Port:50001, Type:ssl).

Each port configuration can contain the following attributes:

...

Attribute Name	Value
Port:	Specifies the port number. To determine the proper values for the HTTP and SSL ports, refer to the J2EE Engine Ports.
Type:	Specifies the type of the port. It can be http or ssl.
SocketQueue:	Specifies the length of the queue of indications of incoming connections.
BindAddress:	Specifies an IP address to bind all incoming connections to this address only. If the value is an empty string, connections will be accepted on any of the local addresses configured.
AcceptingThreadsCount:	Changes the default value of the number of threads that listen to the server socket for incoming connections. The value of the property must be an integer number. We recommend that you do not change the default value of this property. It is estimated to be optimal for a system with default configuration.

Only the Port: and the Type: attributes are mandatory for a valid port configuration. If you do not explicitly specify the rest of the attributes, their default values are assumed. They are: SocketQueue:200, BindAddress:<an empty string>, and AcceptingThreadsCount:10.

To apply these changes, choose  (Save Properties).

Result

You now have basically configured your HTTP Provider Service running on the Java dispatcher to forward incoming HTTP requests to the appropriate server modules (HTTP Provider Service, and Web Container Service if the request is directed to a J2EE web application). If you want to further fine-tune your HTTP Provider Service, proceed with the setup of your virtual hosts.

Once you have configured the ports, the information about the first HTTP and the first SSL ports (exactly as they appear in the value of the Ports property of the HTTP Provider Service) is sent to the message server and the ICM. This information is required by the SAP Web Dispatcher for load balancing. For more information about the topic, see Load Balancing Between Many Java Instances in the Architecture Manual. The ICM requires this information in order to redirect requests to the J2EE Engine. For more information about the communication protocol between ICM and Java Dispatcher, see Communication Between the ICM and J2EE Engine.