The installation of each Sybase RAP component (publisher, subscriber or data store) includes a UAF agent. The UAF agent handles communication between Operations Console and a Sybase RAP component. When a UAF agent starts, it registers with the JINI server as illustrated in the following figure.
The Operations Console queries the JINI server to discover where on the network agents are running and which RAP component the agent manages as illustrated in the following figure.
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 as illustrated in the following figure.
Each publisher and subscriber has an administration channel listening on a specific port. When the Operations Console issues commands to UAF agents through the services RMI ports, the UAF agent accepts the request and contacts its Sybase RAP component through the administration listening port. The Sybase RAP component sends a response through the UAF agent back to Operations Console. You must identify an Administration Listening Port for each publisher and subscriber. Each port number must be unique.
