ABAP Communicator Service 

Purpose

This service notifies the Web AS dispatcher about the J2EE Engine cluster state. During the J2EE Engine startup the service that runs on the dispatcher element waits for the Java Startup and Control Framework to start all J2EE Engine services and then informs the Web AS dispatcher that all services are in an ACTIVE status. It also sends the HTTP port through which the HTTP Provider service waits for requests. During the system runtime the ABAP Communicator service running on the dispatcher element receives information from the HTTP Provider Service when the HTTP port is changed.

The ABAP Communicator service that runs on the server element is responsible for logging the process IDs. During server startup the ABAP Communicator takes the process IDs and writes them in a file, previously specified in Visual Administrator with the PIDsLogFileName property. It then maintains the properties information up-to-date and waits for a SOFTSHUTDOWN command from the dispatcher.

When all J2EE Engine services are down (stopped) the ABAP Communicator service running on the dispatcher element sends an INACTIVE state to the Web AS dispatcher.

 

See also:

Starting and Stopping of the J2EE Engine

ABAP Communicator Service Properties

ABAP Communicator Service Shell Command Group