• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

API Design for support tool : new to Java

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have a requirement to design API for a support tool for support team.

It should be a web application , with following information:

-Display the current status of the feed (healthcheck status and what time the last live message was received)
-Display the time that the last message was received for a given competition.
-Display a pageable, searchable, list of all competitions that are supplied by the football super feed
-For any selected competition, display a pageable, searchable list of all matches within that competition, ordered by date or team
-For any selected match, display a pageable, searchable list of all messages within that match, ordered by timestamp or team
-For any selected message, display the status details of that message:
Message routing status indicating whether the message was routed to any topics (SUCCESS if routed ok, or FAIL if sent to unprocessed queue)
The details of any error if the status was FAIL
The time that the message was received
The time that the message routing completed (and how long it took)
-For any selected message, display the contents of that message:
The message header 'source' value e.g. footballsuper
The message header 'feed' value e.g. IR1 or ECS1
The message header 'version' value e.g. 1.0.0
The message header 'type' value e.g. master or update
The message header 'book' value e.g. SD
The message header 'mnem' value e.g. FM
The message header 'category' value e.g. FB
The message header 'organiser' value e.g. FIFA or UEFA or MAJOR_EUROPE
The message header 'competiton' value and a text description of the code e.g. IG_WC (World cup)
The message header 'name' value representing the event type e.g. goal or corner
The message header 'id' value
The message header 'timestamp' value
The message header 'generationTime' value
The message header 'expiry' value
The full XML content of the message
-For any selected message, display the routing details of that message
The Rule id of the rule that was used to route this message
The rule definition
The topic names that this message was routed to
The packages which will receive a message
The customers that are subscribed to at least one of these packages (these are the customers who should have received the message)
-Display the subscription history showing when subscriptions were updated
-Display the rules history showing when broker rules were updated

I don't want the actual coding. Just the design as to what classes and interfaces roughly would be required to start with. Please help.
 
drifter
Posts: 1364
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What part are you stuck on? What have you come up with?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic