The UAF agent handles communication between Operations Console and a RAP component.
The installation of each RAP component (publisher, subscriber, or data store) includes a UAF agent. When a UAF agent starts, it registers with the JINI server.
The Operations Console queries the JINI server to discover where on the network agents are running and which RAP component the agent manages.
The Operations Console issues commands to UAF agents through the services RMI ports or the listening ports. You must provide a unique listening port for each publisher, subscriber, RAPCache, or RAPStore you install.
Each publisher and subscriber has an administration channel that listens on a specific port. When Operations Console issues commands to UAF agents through the services RMI ports, the UAF agent receives the request and contacts its RAP component through the administration listening port. The RAP component sends a response through the UAF agent back to Operations Console.