Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All

•eu.genesys.* (114)

Package Samples:

• eu.genesys.kernel
• eu.genesys.kernel.messaging
• eu.genesys.kernel.core
• eu.genesys.kernel.agent
• eu.genesys.util
• eu.genesys.util.log
• eu.genesys.util.sql
• eu.genesys.component.generic.console.v2
• eu.genesys.component.sample.agent
• eu.genesys.component.tomcat.agent

Classes:

• ComponentId: This class defines component identifier. Each GeneSyS component must have a unique identifier that is called component id. The structure of component id is as follows componentId = coreId.siteId.agentId coreId is a fixed number that uniquely identifies core of the system (version one supports only a single core, so this feature is for future extension of the system). "0" value corresponds to a default core; siteId is an id uniquely allocated to each site. Off-line mechanism will be used to allocate these ids (e.g. when user registers with GeneSyS Corporation and downloads GeneSyS distribution it ...
• AbstractProducer: Implements all the functionality required to register, start and unregister a producer. Can be used as a base for concrete producer. Subclasses must provide two parameters constructor: String propertiesFile - component propetrties file name String runtimeTitle - producer console title, may cantain copyright information and start a producer with a SimpleProducer and command line parameters. Typical concrete producer should look like this: public MyProducer( String propertiesFile, String runtimeTitle ) { super( propertiesFile, runtimeTitle ); } public static void main( String[] args ) { MyProducer ...
• ServiceManager: An implementing class should manage (combine) together the transport layer ( layer I of the GeneSyS connector), xml parsing/build layer (layer II ) and layer III. It should receives incoming GeneSyS messages from the transport layer, parse them via XmlMessageTransformService and send to MessageService ( layer III ). Also it should perform the reverse activities: builds GeneSyS message from the information coming from MessageService usving XmlMessageTransformService and send it to remote GeneSyS component via TransportService.
• ConsumerConnector: A connector for each agent consuming information. GeneSyS Consumer Connector interface. Consumer connector is an integral part of the GeneSyS consuming agent responsible for providing transport, XML parsing/building, GeneSyS message handling services. Connector incorporates functionality which is common for each GeneSyS consumer. Should be used in conjunction with SimpleConsumer .
• ServiceManagerImpl: Manages (combines) together the transport layer ( layer I of the GeneSyS connector), xml parsing/build layer (layer II ) and layer III. Receives incoming GeneSyS messages from the transport layer, parse them via XmlMessageTransformService and send to MessageService ( layer III ). Also it performs the reverse activities: builds GeneSyS message from the information coming from MessageService using XmlMessageTransformService and send it to the remote GeneSyS component via TransportService.
• ContextAgent: This class implements a simple Tomcat Context Interceptor for Tomcat version 3.1 and 3.2. It's job is to track the number of contexts, containers, servlets, active threads and used memory. This class needs to be registered in Tomcat's server.xml file as a ContextInterceptor. <ContextInterceptor className="dsd.agent.tomcat.ContextAgent"/> TomcatServerQueryHandler and TomcatSystemQueryHandler uses this interceptor to get information about Tomcat.
• Connector: GeneSyS Connector interface. Connector is an integral part of the GeneSyS component responsible for providing transport, XML parsing/building and GeneSyS message handling services. Connector incorporates functionality which is common for each GeneSyS component. Should be used in conjunction with SimpleComponent .
• RequestAgent: This class implements a simple Tomcat Request Interceptor for Tomcat version 3.1 and 3.2. It's in order to get the total hits and the time per operation values. This class needs to be registered in Tomcat's server.xml file as a RequestInterceptor. <RequestInterceptor className="dsd.agent.tomcat.RequestAgent"/> TomcatServerQueryHandler uses this interceptor to get information about Tomcat.
• SimpleComponent: GeneSyS Simple Component interface. Simple component is an integral part of the GeneSyS component responsible for providing component specific functionality (e.g. measurements for monitoring agent, visualisation for console). Should be used in conjunction with Connector .
• SimpleConsumer: GeneSyS Simple Consumer interface. Simple consumer is an integral part of the GeneSyS consuming agent responsible for providing consumer specific functionality (e.g. monitoring data visualisation). Should be used in conjunction with ConsumerConnector .
• ConnectorFactory: This is a factory to get the GeneSyS connectors for the Core, Producer and Consumer. A class implements a Singleton patern so that the only one factory instance is possible. Usage example: ConsumerConnector myConsumerConnector; myConsumerConnector = ConnectorFactory.getInstance().getConsumerConnector();
• Toolkit: Class for constructing an appropriate factories. Usage example: ServiceFactory factory; factory = Toolkit.getServiceFactory(); XmlMessageTransformService xmlTransformService = factory.getXmlMessageTransformService(); TransportService transportSrv = factory.getTransportService();
• AgentConnector: Agent Connector interface. Agent Connector incorporates functionality which is common for each GeneSyS agent. Should be used in conjunction with SimpleAgent .
• AbstractSimpleProducer: Abstract Simple Producer introduces stub implementations of the most methods which SimpleProducer should implement. Can be used as a base for concrete simple producer. Subclasses must provide their own implementation of getMonitoringMessage() and getAgentInformation() methods.
• SimpleAgent: GeneSyS Simple agent interface. Simple agent should implement agent specific functionality. Should be used in conjunction with AgentConnector .
• UnexpectedMessageException: Unexpected GeneSyS message exception. Should be thrown, when received message is of known type, but not expected in current state. E.g. as a response to Query Message received Registration Message. Holds original Java MessageContainer and Java Message.
• UuidGenerator: UUID (Universal Unique Identifier) Generator. Generates string-based key. UUID layout: System.currentTimeMillis() IP address System.idnetityHashCode() Random Number
• SoapTransportService: This class is TransportService interface implementation and represents GeneSyS transport layer ( layer I ). It uses SOAP as a transport. Class implementation issues and possible bugs description goes here.
• SimpleProducer: Simple producing agent. Should be used in conjunction with ProducerConnector .
• ProducerConnector: Producing agent connector. Should be used in conjunction with SimpleProducer .
• GenesysException: GeneSyS Exception. General system-level exception. Should be thrown by connector or by simple component in case of unexpected error (e.g., connector failed to initialize SOAP engine).
• GetAgentInformationMessage: Class description goes here (what the class should do). class usage example can go here Class implementation issues and possible bugs description goes here.
• MessageSendException: Class description goes here (what the class should do). class usage example can go here Class implementation issues and possible bugs description goes here.
• MessageService: This interface represents GeneSyS connector layer III. An implementing class should receive GeneSyS messages, handle them, send GeneSyS messages via the specified MessageSender.

Home | Contact Us | Privacy Policy | Terms of Service