ra:phm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ra:phm [2018/10/05 18:41] koubel |
ra:phm [2018/10/05 18:49] (current) koubel |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * Fuel stations - can have more AVPs | * Fuel stations - can have more AVPs | ||
| - | Data relations | + | ====== Data and relations ====== |
| * FuelStation - important is FSCode | * FuelStation - important is FSCode | ||
| * PHMIdentity - some identity for fueling, mosty by some RFID card, chip card etc. determines the car of vehicle or some external entity for fueling. Important is ChipNumber. | * PHMIdentity - some identity for fueling, mosty by some RFID card, chip card etc. determines the car of vehicle or some external entity for fueling. Important is ChipNumber. | ||
| Line 20: | Line 21: | ||
| - | Data flow: | + | ====== Data Flow, Processing ====== |
| - | * Synchronization - fuel stations, vehicles. | + | |
| - | * Fill the ''PHMTransaction'' table from - GSI software, from excel etc. Import is from many places also from e.g. ''KupsonView'' etc. | + | Synchronization: fuel stations, vehicles, chip numbers, fuel station FSCodes. |
| + | |||
| + | Vehicles are synchronized mostly from customers external data e.g. SAP for SD customer into some tables. Best usage for search vehicles is view ''PHMIdentityVehicleView''. Column ''IdentityTextValue'' is value external customer car identifier for PHM. Same for Drivers with ''PHMIdentityDriverView''. | ||
| + | |||
| + | Transaction processing: | ||
| + | |||
| + | * Filling transaction - fill ''PHMTransaction'' table mostly from GSI software (our software) via KupsonManager. Some times from excel etc. | ||
| * These transactions are then processed via ''TransactionManager'' into transaction data store - ''PHMTransactionDataStore'' table. This is done via service thread ''PHMTransaction''. | * These transactions are then processed via ''TransactionManager'' into transaction data store - ''PHMTransactionDataStore'' table. This is done via service thread ''PHMTransaction''. | ||
| * Web application show data from table ''PHMTransactionDataStore''. | * Web application show data from table ''PHMTransactionDataStore''. | ||
| Line 28: | Line 35: | ||
| When some data from PHMTransactionDataStore are deleted, these can be again recalculated via ''PHMTransaction'' service with TransactionManager. See [[https://protank.visualstudio.com/PD/_workitems/edit/14409|bug]] for more information. | When some data from PHMTransactionDataStore are deleted, these can be again recalculated via ''PHMTransaction'' service with TransactionManager. See [[https://protank.visualstudio.com/PD/_workitems/edit/14409|bug]] for more information. | ||
| - | Processing in ''TransactionManager'' | + | Filling transactions |
| + | |||
| + | On some customers with AVPs, method ''KupsonManager.SynchronizeAllDevices'' - there is both direction synchronization: | ||
| + | |||
| + | * information about AVP devices into our db - ''PHMTransaction'' | ||
| + | * information back to AVPs - mostly chip numbers, cards. | ||
| + | |||
| + | Time intervals for synchronizations are newly defined in db - [[https://protank.visualstudio.com/_git/PD/pullrequest/1409|PR]] | ||
| + | |||
| + | |||
| + | Processing with ''TransactionManager'' | ||
| * reads amount of transaction from ''PHMTransaction'' process these amount in loop | * reads amount of transaction from ''PHMTransaction'' process these amount in loop | ||
| Line 40: | Line 57: | ||
| which is source of identity of the transaction. | which is source of identity of the transaction. | ||
| - | Synchronization: | + | Photos |
| - | + | ||
| - | On some customers with AVPs, method ''KupsonManager.SynchronizeAllDevices'' - there is both direction synchronization: | + | |
| - | + | ||
| - | * information about AVP devices into our db - ''PHMTransaction'' | + | |
| - | * information back to AVPs - mostly chip numbers, cards. | + | |
| - | + | ||
| - | Time intervals for synchronizations are newly defined in db - [[https://protank.visualstudio.com/_git/PD/pullrequest/1409|PR]] | + | |
| - | + | ||
| - | Photos: | + | |
| Transactions has photos made by some cameras on fuel stations. These photos are synced via rsync to APL_Service server (name in Terminals) in shared directory %%\\192.168.148.15\avp\AGROFERT\201801\overphoto\cam_R691_8.jpg%%. These are then synced with some service into db - table ''PHMTransactionPhoto''. | Transactions has photos made by some cameras on fuel stations. These photos are synced via rsync to APL_Service server (name in Terminals) in shared directory %%\\192.168.148.15\avp\AGROFERT\201801\overphoto\cam_R691_8.jpg%%. These are then synced with some service into db - table ''PHMTransactionPhoto''. | ||
| - | |||
| - | Vehicles: | ||
| - | |||
| - | Vehicles are synchronized mostly from customers external data e.g. SAP for SD customer into some tables. Best usage for search vehicles is view ''PHMIdentityVehicleView''. Column ''IdentityTextValue'' is value external customer car identifier for PHM. Same for Drivers with ''PHMIdentityDriverView''. | ||
ra/phm.1538757713.txt.gz · Last modified: 2018/10/05 18:41 by koubel
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
