Distributed Monitoring and Control Mechanism

1
Distributed Monitoring and Control Mechanism

• By Mohammed Abdul Jabbar
• ABB Corporate Research Presentation Datwill
  Switzerland
• September 12th 2002

2
Need to control

• Distributed Architecture
• Use of Third Party Software Modules
• Dependencies between different Modules
• Central Point Control
• Over all state management
• Saving Persistent Information

3
Skyva Control Center

• A central core module that is resides with the
  Agent broker and that has both direct and
  indirect control of the all the skyva modules
  running as a part of skyva solutions. It controls
  generic skyva containers, San Francisco, Skyva
  Containers Running inside SF and others.

4
Agent Broker
Domain Lookup
Application Service Broker
DNS
JMX Web Console RMI Connection Standard Service
Invocation Remote Service Broker
Authentication / Verification
Skyva Control Center
SCC Hook
Licensing Service
SCC Footprint
5
Features 1/4

• Disconnected Operations
• Skyva Containers can run on different hosts. It
  is possible that the a particular agent has gone
  down or is not available for service due to
  network problems. When the skyva container comes
  up again it can retransmit all its service
  information back to the SCC.
• Dynamic Discovery and Update
• All the skyva containers that become a part of
  the Skyva Solutions register their Domains,
  Services and Service Flavors with the SCC. The
  Host Port, Service Information, State Information
  etc are also published with SCC.
• Remote Lookup
• The SCC/DNS combination allows a Skyva Container
  to find the other skyva container and to
  communicate with it.

6
Features 2/4

• Multi-Access / Multi Protocol Support
• SCC poses a web front, a JMX Console, it
  communicates via RMI and in addition to the
  Defaults like SOAP, Local and JMS
• Scalable
• Provided that the network systems are stable and
  bandwith guranteed, there is no limit to the
  number of additional software components that can
  be configured with the SCC

7
Features 3/4

• Specialized Operations
• The SCC also offers specialized that may be
  local to a container itself. I gives a rich UI to
  start / resume / suspend / stop / reload services
  and skyva containers.
• Integration layer for third party software
  modules
• SCC accesses the other containers via a generic
  interface. By default it executes the functions
  of a standard skyva container. But it can be over
  ridden to interact with any third party or
  no-skyva software module that is emulated as
  container
• Handling fail over
• Handles Graceful shutdown and persists the state
  model notifications and other persistent data

8
Features 4/4

• Dependency Model
• It is therefore possible to have a dependency
  graph within a container. Consequently, it is
  possible to have a dependency model across the
  containers. Supports orderly startup and shutdown
• Status Query
• The status Update feature informs the sCC Broker
  Process of the change in state of the service or
  the agent. That the sCC Broker Process has always
  the most current information about the Agent
  Brokers running on that host.
• HeartBeat
• This constantly pings all the registered
  container and updates the status of skyva
  containers.

9
SCC Interaction
Agent Broker
Interface
SCC
SCC Req
Skyva Container
SCC Req
RSB
SSBPort
SCC Footprint
Mbean Server JMX
SCC Req
Third Party
RSB
Skyva Container
SSBPort
10
SCC Foot Print

• Announcing to be Controlled SSBPort
• Respond to SCC service requests
• Actively send Mbean Notifications to SCC on the
  Agent Broker
• Register Domains and Services with the DNS / SCC
• Register new Skyva Containers with Agent Broker

11
Module Dependencies

• Startup Dependency Tree
• Suspend Dependency Tree
• Resume Dependency Tree
• Stop Dependency Tree
• XMI Based
• Activity Service (CORBA Spec)
• ECMA Script Execution
• Replace MLet

12
Dependency Tree
Agent Broker
Planning
Test
GSM
OMAgent
SFDefault
SFContainer