Skip to content
- Hyperledger Fabric Using Composer
- Introduction
- What is Hyperledger?
- Distributed Ledger Technology & its Challenges
- Hyperledger & Distributed Ledger Technology
- Hyperledger Fabric & Composer Concepts
- Hyperledger Fabric : A DLT for Business Applications
- Hyperledger Fabric : DLT for Business
- Assets, Chaincode & Ledger
- Assets, Chaincode and Transactions
- Permissioned Network, Members & Membership Service Provider
- Permissioned Network, Member & Membership Services
- Nodes and Channels
- Hyperledger Fabric Composer Overview
- Pre-Requisites for Fabric development
- Development Machine Specifications & IDE
- Composer Dev Tools Installation
- Exercise: Validate the Composer Development Environment
- Linux/Ubuntu & AWS: Setup of Fabric Development on Local & Cloud VM
- Fabric Under the Hood (Concepts & Terminology)
- Ledger Implementation
- Dev Environment Walkthrough: Peer & CouchDB setup
- Ledger Implementation
- Peers Nodes : Anchors and Endorsers
- Anchor Peers & Endorsing Peers
- Clients Node: Endorsement Policies
- Client Peer & Endorsing Policies
- Orderer Nodes
- Membership Service Provider & Certification Authority
- Dev Environment Walkthrough: Orderer and CA Server
- Chaincode Development
- Using Composer Tools for Application Development & Administration
- Fabric Composer Playground
- Composer Playground
- Yeoman Hyperledger Generators
- Yo Generators
- Participant Roles and Business Network Cards
- Participant Roles and Business Network Cards
- Composer CLI Tool – Deploying a Network Application
- Composer CLI Tool – Network Application Management
- Exercise: Create & Deploy Network Application
- REST Server Overview
- REST Server Security
- Skeleton Angular Application using Yo
- Composer SDK Overview
- Business Network Application Modelling
- Case Study: ACME Airlines
- Modeling Language Files | Namespace
- Defining the Resources
- Support for Object Orientation
- Modeling Arrays
- Registries & Relationship between Resources
- Arrays, Registries & Relationships
- Adding the field Validations
- Field validations
- Resource Registries & Identities +Exercise
- Modeling the Transactions
- Exercise: Fix the code for generating the FlightId
- Exercise: Add a set of aircraft queries
- Managing identities for Network Applications
- Access Control Language (Part 1 of 2) Simple Rules
- Exercise: Simple Rule for ACMENetworkAdmin
- Access Control Language (Part 2 of 2) Conditional Rules
- Exercise: Conditional Rule for ACMEPersonnel
- Composer SDK / API : Coding the Client Apps
- Business Network Card
Management
- Business Network Connection
Class
- Write a utility to create |
delete test data for ACME Airline Model
- Composer SDK / API : Coding the Transaction Processors
- Embedded Runtime for Testing
- Crash course in Mocha and Chai
- Writing Unit Test Cases for Network Applications
- Runtime API for Transaction Processing Functions
- Exercise: Define the Aircraft Assignment Transaction
- Query invocation in Transaction Processing Functions
- Implementing Programmatic Access Control
- Emitting events and Integrating with external systems
- Developing Front End Applications for Network Applications
- Application Design Patterns
- Application Architecture
Patterns
- Securing the REST server with
Authentication Strategy
- Walkthrough: Applying OAuth2.0
Authentication Strategy to REST Server
- Working of Multi User Enabled
REST Server
- Walkthrough – REST Server Multi
User mode
- Create the Design Blueprint for
the Fabric Application UI