Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Key Points

  1. solution concepts - apps, services


References

Reference_description_with_linked_URLs_______________________Notes______________________________________________________________






m BAF - Hyperledger Automation FrameworkSimple Supply Chain app model in BAF example







Key Concepts




Potential Value Opportunities


SCS >> Simple Supply Chain for Logistics tracking 

track shipments from source to retail using QR codes on products, containers

BVA

  1. provenance, traceability, visibility on delays, low-cost operations,


included use cases

org enrollments

user enrollments

products

qr code tags

receipts

shipments

scrap


excluded use cases

order mgt

billing mgt

payment mgt

inventory mgt


II >> integration interfaces

order manager

quote manager

inventory manager 

billing manager

routing manager

bill of materials manager


All integration services provide 2 way SCMT - state change management tracking using SLT


STS >> Smart Trust Services for VCE, AQM - VTC - Verifiable Trust Certificates - when trust is the product


apply to any industry setting

see Carbon offsets etc


AQM - asset quality management


STS - Smart Trust Services: deliver trusted outcomes


Modern Platform ODP supports VCE , DAN, STS


automation of trust chain services real-time using BSC - Better Smart Contracts 

generate trust chains

custodial wallet services

custodial identity, signer services

custodial asset services

interfaces for providers, 

asset references to related std versions on compliance



SLT >> Smart Ledger Technology - PTSCM - persistent transaction state change mgt for any transaction scope

Key Features & Value Propositions

  1. Borrows concepts from Distirbuted Data Servcies, Blockchain, STS
  2. Not limited to a blockchain implementation in anyway
  3. Can use STS for trust verification optionally
  4. Operates as a service via API or agent
  5. Provides interfaces for extension services
  6. Configuration by file or variables
  7. Segregates roles for transaction sources and consumers
  8. Supports listeners for consumer services optionally
  9. Defines control blocks for faster processing on transaction apply or undo
  10. Provides search filters by time, by block, by transaction ID, by attributes or combinations of criteria
  11. Provides accurate time series transaction state change tracking for any transaction services  ( SQL, NOSQL, API,  RPC etc )
  12. Optionally tracks post transaction state, pre and post transaction state or state changes only
  13. Platform independent service
  14. Can run asynchronously minimizing performance impacts of transactions
  15. Provides  listeners for reactive event management
  16. Can be used to recover transactions 
  17. Idempotent transactions repeated create the same state footprint except for timestamps, status and origin
  18. SCM life cycle for transactions - transaction request > route > notifications ( synch and asynch ) > execution > commit  > notifications ( synch and asynch ) > finalization >  notifications ( synch and asynch ) 
    1. asynch processing can be done as parallel thread, callback, state db change updates, SSE ( server sent events )



VSC >> Virtual Smart Contact - a smarter smart contract

Key Features

  1. Provides more options than traditional Smart Contracts
  2. As a logical contract service, it can map to multiple execution processes:  smart contracts, API, gRPC etc
  3. Platform independent
  4. Defines interfaces for extensions
  5. Executes via API, gRPC or local process
  6. Can be assembled easily into data mesh networks using the DSL
  7. Overcomes the problems with DLT Smart Contract oracles


GACS >> Governance Automated Compliance Service = STEAR

STEAR - search, track, escalate, audit, remediate

monitor data events


included use cases

org enrollments

team enrollments

user enrollments

register data sources

define data events

define data event actions

monitor data events

set data alerts

notify data alerts

escalate data alerts

remediate data alerts

audit reports



excluded use cases




Service Work Tracker


track contract workers on job tickets


included use cases

org enrollments

team enrollments

user enrollments

manage jobs

offer job tickets

bid job tickets

accept bid

schedule job ticket

logon job ticket

logoff job ticket

close job ticket

audit reports



excluded use cases






Potential Challenges



Candidate Solutions




Meetings



tg200409 initial view of app


-------------------------------
tg200409     initial view of app


tc 1.4.x 
svn
jdk 8

dev, test, prod cfgs only file name different

q> what objects other than java, html, css is in app ??

q.is grails an option ?? 

tc migration issues list 

i> shared folder gone in later versions 
i> global object - rad generated for each page --- 
    allows generic data for every page ( global data scope )

h> many pages all ref the global data ( memcache ? )
h> servlet calls form class .. page name > servlet > form class
h> form class drives each page and each is unique

a> create 2 page model in grails w gradle / github
    move to modern hibernate in grails 
a> test birt on jdk11 / grails / tomcat or openliberty
a> use mysql db

q> do java modules add any value???

h> updates only in 2 towergrove jars
h> obsolete eclipse birt classes used .. can migrate w grails 
h> tgreport is tower grove birt code 
h> eclipse luna
h> tgfcore is main app

i> get old versions of code
i> create projects and import app


s0> grab a subset of the app to test ... Richard to send memory stick w app infra and mysql export
s1> run your app local using mysql 
s2> run birt in app or separate if needed






Step-by-step guide for Example



sample code block

sample code block
 



Recommended Next Steps



  • No labels