sample-blockchain-vehicle-lifecycle icon indicating copy to clipboard operation
sample-blockchain-vehicle-lifecycle copied to clipboard

This sample illustrates how IBM ODM can be used with HyperLedger Fabric and Composer to implement rule-based Smart Contracts

Results 16 sample-blockchain-vehicle-lifecycle issues
Sort by recently updated
recently updated
newest added

Current version of the code sample assume all peers are running when deploying a given version of the rules. There is nothing that initializes the odm-runtime with latest version of...

Pull Request Link: #20. Link to the article : [article](https://www.ibm.com/developerworks/library/mw-1708-mery-blockchain/1708-mery.html) - [[ CATEGORY ]] : [[ ELEMENT ]] - Smart contracts : Second picture show "Odm-deployer". Should be modified to...

covering synchronization and rule lifecycle. Illustrate governance and collaboration on the smart contract rules. Illustrate how to deploy from Decision Center (generating the ruleapp in a given location and apply...

For instance if deployment failed because odm-deployer is not reachable or RES is down, the deployment transaction should be rolled-back. We need to ensure all nodes are at the same...

Set-up an instance of RES per instance of peers - support HA: if a peer/RES goes down, the second one take over - need to map ports so that Smart...

change IsSuspiciousTransferDecisionService to a concept when Composer supports serialization of a Concept as a root

https://github.com/hyperledger/composer-sample-networks/tree/master/packages/vehicle-lifecycle-network. See inheritance of Person

does not work if the deployXom transaction is rolled-back. The side effect made on the RES is not rolled-back and further execution will use the new version of the XOM...

As an alternative to using the Blockchain by sending deployXom and deployRuleapp transactions