Development

Overview

Background

The MPS History (MpsHist) is a software system for storing MPS History Messages in an RDB.

Thesaurus

• LP: link processor

Requirements

Use Cases

1. User must figure out what's going on with MPS (performance statistics).
   • Author: snorum
   • Reason: Our mission.

1. User must search and do analysis on messages.
   • Author: snorum
   • Reason: For diagnostics.

1. User must be able to register with LP over UDP at 0.2 Hz.
   • Author: snorum
   • Reason: Zero configuration, dynamic change.

1. User must be notified when MpsHist fails.
   • Author: snorum
   • Reason: Mission-critical.

1. User must find out about internal state of MpsHist.
   • Author: snorum
   • Reason: Prevent failure.

1. User must switch from one MpsHist to another.
   • Author: snorum
   • Reason: Prevent loss of messages.

1. User must be able to change default parameters at start-up.
   • Author: snorum
   • Reason: optimization

1. User must be able to access all info messages.
   • Author: snorum
   • Reason: diagnostics

1. User must be able to specify path to ConfigDB.
   • Author: snorum
   • Reason: changes in the hardware.

Functional Specification

1. MpsHS must capture all messages.
   • Origin: Use Case #1
   • How to test: All accepted messages must be in the database.

1. MpsHS must write all messages to RDB.
   • Origin: Use Case #2
   • How to test: All accepted messages must be in the database.

1. MpsHs must send notification messages to LP
   • Origin: Use Case #3
   • How to test: Get messages from LP.

1. MpsHs must run several copies of itself.
   • Origin: Use Case #
   • How to test: Have 2 of them running.

Constraints

• Messages are streamed at up to 1MB/sec.
• MpsHS must support Oracle RDB.
• LP is a time-critical VME IOC (2.8 msecs).
• LP might not be busy for a while, so no timeouts must be introduced.
• Connect only to 1 MpsHist at a time.

Design

• Use WaitFreeWriteQueue for repository.
• Send a datagram to a host name of LP on port 30000.
  • 2 byte header: protocol version 1, message type: notification 2
  • 2 bytes for port number
• Java server port from 30001 - 30009

Comments

• Open to possibility of sending messages directly from LP to RDB.

User's Guide

Programmer's Guide

References

Administration

Task lists and schedules, spreadsheets etc.