P4 Provider Service
P4 Provider Service provides the implementation of the SAP specific P4 protocol for communication between Java remote objects. This protocol is an alternative of the standard Java RMI protocol for Java-to-Java remote communication.
P4 Provider Service
consists of two parts. One of the parts runs on the Java dispatcher. It
accepts requests from the remote clients and has the responsibility to
dispatch them to the appropriate cluster element, where the implementation of
the remote object resides. For the purpose, the P4 Provider Service uses the
J2EE Engine Load Balancing System. For more information about the load
balancing system, see
Load Balancing by the
Java Dispatcher in the Architecture Manual.
The second part of the P4 Provider Service runs on the server processes. This part contains the implementation of the P4RemoteObject broker and is responsible for executing methods on the implementation of the remote object and returning the results.
You can customize the P4 Provider Service by:
● Managing the Underlying Transport Layers
The service also provides Runtime Information about active remote objects and brokers.
See also:
P4 Provider Service properties reference
Accessing Components – for more information about changing the P4 Provider Service properties.