Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/Design/Messaging"
< OSEE
(→Messages) |
|||
| Line 1: | Line 1: | ||
=Messaging System Design Notes= | =Messaging System Design Notes= | ||
| − | + | == 10/20/09 == | |
| − | ==What is the broker topology== | + | ===What is the broker topology=== |
network of brokers, host1 + host2 + host3, we need to make sure ote can function w/o the DB layer available... so i want to make sure we can run with a network of brokers, and it has to be easily configurable so that platforms not using the persistence layer can function. Potentially in some cases we launch an embedded broker. | network of brokers, host1 + host2 + host3, we need to make sure ote can function w/o the DB layer available... so i want to make sure we can run with a network of brokers, and it has to be easily configurable so that platforms not using the persistence layer can function. Potentially in some cases we launch an embedded broker. | ||
| − | ==What are the topics/queue names, what are their functions, and how do we use them== | + | ===What are the topics/queue names, what are their functions, and how do we use them=== |
| − | ===CONSIDERATIONS:=== | + | ====CONSIDERATIONS:==== |
#queue - used for app server commands - it gets removed by the first consumer to get it, so if there are multiple subscribers only one will act upon the message. | #queue - used for app server commands - it gets removed by the first consumer to get it, so if there are multiple subscribers only one will act upon the message. | ||
#topic - used for status - broadcast - pubsub | #topic - used for status - broadcast - pubsub | ||
| − | ==Messages== | + | ===Messages=== |
| − | ====queue:OSEE.persistence.createBranch==== | + | =====queue:OSEE.persistence.createBranch===== |
*subscribers: appServers | *subscribers: appServers | ||
*publishers: oseeClients | *publishers: oseeClients | ||
| − | ====topic:OSEE.persistence.newBranch==== | + | =====topic:OSEE.persistence.newBranch===== |
*subscribers: oseeClients | *subscribers: oseeClients | ||
*publishers: appServers | *publishers: appServers | ||
| − | ====topic:OSEE.OTE.station.global.statusRequest==== | + | =====topic:OSEE.OTE.station.global.statusRequest===== |
*subscribers: oteTestServers | *subscribers: oteTestServers | ||
*publishers: oteTestClients | *publishers: oteTestClients | ||
*purpose: sent by test clients to find out information about available test servers, i.e. who exists, in what configuration, current state (connected clients, etc..) | *purpose: sent by test clients to find out information about available test servers, i.e. who exists, in what configuration, current state (connected clients, etc..) | ||
| − | ====topic:OSEE.OTE.station.global.statusResponse==== | + | =====topic:OSEE.OTE.station.global.statusResponse===== |
*subscribers: oteTestClients | *subscribers: oteTestClients | ||
*publishers: oteTestServers | *publishers: oteTestServers | ||
*purpose: the response message to a 'OSEE.OTE.station.global.statusRequest', contains configuration and state information of a test server | *purpose: the response message to a 'OSEE.OTE.station.global.statusRequest', contains configuration and state information of a test server | ||
| − | ====topic:OSEE.OTE.station.<station_name>.<station_id>.status==== | + | =====topic:OSEE.OTE.station.<station_name>.<station_id>.status===== |
*subscribers: connected-oteTestClients | *subscribers: connected-oteTestClients | ||
*publishers: specific-oteTestServers | *publishers: specific-oteTestServers | ||
*purpose: update of current state, errors, test point, current command, etc... | *purpose: update of current state, errors, test point, current command, etc... | ||
| − | ====topic:OSEE.OTE.station.<station_name>.<station_id>.command==== | + | =====topic:OSEE.OTE.station.<station_name>.<station_id>.command===== |
*subscribers: specific-oteTestServers | *subscribers: specific-oteTestServers | ||
*publishers: connected-oteTestClients | *publishers: connected-oteTestClients | ||
*purpose: command the ote environment to do something | *purpose: command the ote environment to do something | ||
| − | ====topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.command==== | + | =====topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.command===== |
*subscribers: specific-oteTestServers | *subscribers: specific-oteTestServers | ||
*publishers: connected-oteTestClients | *publishers: connected-oteTestClients | ||
*purpose: command a model to do something | *purpose: command a model to do something | ||
| − | ====topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.status==== | + | =====topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.status===== |
*subscribers: connected-oteTestClients | *subscribers: connected-oteTestClients | ||
*publishers: specific-oteTestServers | *publishers: specific-oteTestServers | ||
*purpose: update of current state, errors, test point, current command, etc... | *purpose: update of current state, errors, test point, current command, etc... | ||
| + | |||
| + | [[Category:OSEE]][[Category:Design]][[Category:Messaging System]] | ||
Revision as of 15:13, 20 October 2009
Contents
- 1 Messaging System Design Notes
- 1.1 10/20/09
- 1.1.1 What is the broker topology
- 1.1.2 What are the topics/queue names, what are their functions, and how do we use them
- 1.1.3 Messages
- 1.1.3.1 queue:OSEE.persistence.createBranch
- 1.1.3.2 topic:OSEE.persistence.newBranch
- 1.1.3.3 topic:OSEE.OTE.station.global.statusRequest
- 1.1.3.4 topic:OSEE.OTE.station.global.statusResponse
- 1.1.3.5 topic:OSEE.OTE.station.<station_name>.<station_id>.status
- 1.1.3.6 topic:OSEE.OTE.station.<station_name>.<station_id>.command
- 1.1.3.7 topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.command
- 1.1.3.8 topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.status
- 1.1 10/20/09
Messaging System Design Notes
10/20/09
What is the broker topology
network of brokers, host1 + host2 + host3, we need to make sure ote can function w/o the DB layer available... so i want to make sure we can run with a network of brokers, and it has to be easily configurable so that platforms not using the persistence layer can function. Potentially in some cases we launch an embedded broker.
What are the topics/queue names, what are their functions, and how do we use them
CONSIDERATIONS:
- queue - used for app server commands - it gets removed by the first consumer to get it, so if there are multiple subscribers only one will act upon the message.
- topic - used for status - broadcast - pubsub
Messages
queue:OSEE.persistence.createBranch
- subscribers: appServers
- publishers: oseeClients
topic:OSEE.persistence.newBranch
- subscribers: oseeClients
- publishers: appServers
topic:OSEE.OTE.station.global.statusRequest
- subscribers: oteTestServers
- publishers: oteTestClients
- purpose: sent by test clients to find out information about available test servers, i.e. who exists, in what configuration, current state (connected clients, etc..)
topic:OSEE.OTE.station.global.statusResponse
- subscribers: oteTestClients
- publishers: oteTestServers
- purpose: the response message to a 'OSEE.OTE.station.global.statusRequest', contains configuration and state information of a test server
topic:OSEE.OTE.station.<station_name>.<station_id>.status
- subscribers: connected-oteTestClients
- publishers: specific-oteTestServers
- purpose: update of current state, errors, test point, current command, etc...
topic:OSEE.OTE.station.<station_name>.<station_id>.command
- subscribers: specific-oteTestServers
- publishers: connected-oteTestClients
- purpose: command the ote environment to do something
topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.command
- subscribers: specific-oteTestServers
- publishers: connected-oteTestClients
- purpose: command a model to do something
topic:OSEE.OTE.station.<station_name>.<station_id>.<model>.status
- subscribers: connected-oteTestClients
- publishers: specific-oteTestServers
- purpose: update of current state, errors, test point, current command, etc...