Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • File transfers effected by the JADE Client should be subject to monitoring in the same way as the current JADE JITL job.
  • More Monitors such as as IBM Tivoli, HP OVO, IBM WS Message, Broker should be supported.
  • SNMP should be supported.

Proposed Solution

  • Start from the feature JobScheduler Monitoring Interface
    • add monitoring capabilities for the file transfer history as reported by the JADE Background Service
  • Implement interfaces for popular Monitoring Systems
    • IBM Tivoli Monitoring: this should be feasible by a client command line tool and therefore be available with the JobScheduler Monitoring Interface.
    • HP OVO: to be clarified if a command line tool exists.
    • IBM WS Message Broker (MQ): to be clarified if a message queue interface were required or a command line tool were sufficient.
  • SNMP Interface
    • architecture

...

    • SNMP could be supported via a separate process that integrates with the JobScheduler Monitoring interface.
      • the overall availability of jobs can be reported
      • in case of job errors respective messages are sent to an SNMP server.

 

Show If
groupsos-members

Anchor
transfer_speed_restriction
transfer_speed_restriction
Transfer speed restrictions

...

Starting situation

  • JADE uses all the available bandwith for a transfer and leaves it to the network administration to manage rules for bandwidth usage.
  • JADE should be configurable for use of bandwidth, e.g. in slow networks

Proposed Solution

  • tbd

...