Daemon - remoteAgentEditor

 

Description

Creates and maintains an RMI server object that allows agents to be manipulated. The server object provides RMI clients with the following capabilities:

Note: The RMI registry application, rmiregistry, must be running before this agent is started in order for the remote agent editor service to be available. Essentially, this means the RMI registry should be started before PAM is started. The rmiregistry application is a core part of the Sun Java Runtime Environment.

Configuration Variables

remoteObjectName
The name under which the remote object is registered in the RMI registry. Clients query the RMI naming service -- a function provided by rmiregistry -- for the object by this name. 

How it works

Implemented as an asynchronous agent, this daemon responds to four calls from the PAM executive, startService, stopService, pauseService, and resumeService.

When the method, startService, is called by the executive, four steps are performed. First, the java.rmi.registry.LocateRegistry class is queried for a reference to a Registry object. Second, the object that implements the remote agent editor's interfaces is instantiated. Third, a reference to the executive is provided to the remote server object. Last, the registry is directed to bind the remote server object with the name stored in the remoteObjectName configuration variable.

When the method, stopService(), is called by the executive, the registry is directed to unbind the remote server object's name from its database.

Currently, the methods, pauseService and resumeService, do nothing.

Sample checkpoint definition:

(remoteAgentEditor remoteAgentEditor1 (enabled true)
       (remoteObjectName remoteAgentEditor)
       (schedule weekly)(lastUpdateLong 1))
  •  

  • First Available: Build 37

    Revised 16 June 1998