Read this in other languages: 中国語,日本語.

Build Blockchain Insurance Application

This project showcases the use of blockchain in insurance domain for claim processing. In this application, we have four participants, namely insurance, police, repair shop and the shop. Furthermore, each participant will own its own peer node. The insurance peer is the insurance company providing the insurance for the products and it is responsible for processing the claims. Police peer is responsible for verifying the theft claims. Repair shop peer is responsible for repairs of the product while shop peer sells the products to consumer. The value of running this network on the IBM Blockchain Platform is that you can easily customize the network infrastructure as needed, whether that is the location of the nodes, the CPU and RAM of the hardware, the endorsement policy needed to reach consensus, or adding new organizations and members to the network.

Note: This code pattern can either be run locally, or connected to the IBM Blockchain Platform. If you only care about running this pattern locally, please find the local instructions here.

Audience level : Intermediate Developers

When the reader has completed this code pattern, they will understand how to:

• Create a Kubernetes Cluster using the IBM Kubernetes Service
• Create an IBM Blockchain service, and launch the service onto the Kubernetes cluster
• Create a network, including all relevant components, such as Certificate Authority, MSP (Membership Service Providers), peers, orderers, and channels.
• Deploy a packaged smart contract onto the IBM Blockchain Platform by installing and instantiating it on the peers.
• Use the connection profile from IBM Blockchain Platform to create application admins, and submit transactions from our client application.
• Configure a Db2 Federated Server to Access the Blockchain
• Query Blockchain via Zeppelin Notebooks using Db2 and SQL to perform analytics on blockchain transactions.

Application Workflow Diagram

1. The blockchain operator creates a IBM Kubernetes Service cluster (32CPU, 32RAM, 3 workers recommended) and an IBM Blockchain Platform 2.0 service.
2. The IBM Blockchain Platform 2.0 creates a Hyperledger Fabric network on an IBM Kubernetes Service, and the operator installs and instantiates the smart contract on the network.
3. The Node.js application server uses the Fabric SDK to interact with the deployed network on IBM Blockchain Platform 2.0.
4. The React UI uses the Node.js application API to interact and submit transactions to the network.
5. The user interacts with the insurance application web interface to update and query the blockchain ledger and state.

Included Components

• IBM Blockchain Platform V2 Beta gives you total control of your blockchain network with a user interface that can simplify and accelerate your journey to deploy and manage blockchain components on the IBM Cloud Kubernetes Service.
• IBM Cloud Kubernetes Service creates a cluster of compute hosts and deploys highly available containers. A Kubernetes cluster lets you securely manage the resources that you need to quickly deploy, update, and scale applications.

Featured technologies

• Hyperledger Fabric v1.4 is a platform for distributed ledger solutions, underpinned by a modular architecture that delivers high degrees of confidentiality, resiliency, flexibility, and scalability.
• Node.js is an open source, cross-platform JavaScript run-time environment that executes server-side JavaScript code.
• React A declarative, efficient, and flexible JavaScript library for building user interfaces.
• Docker Docker is a computer program that performs operating-system-level virtualization. It was first released in 2013 and is developed by Docker, Inc.

Watch the Video - Multiple Organization and Multiple Peer App Demo #1 - Intro

Watch the Video - IBM Blockchain Tutorial: Multiple Organization and Multiple Peer App Demo #2 - Build Nodes

Watch the Video - Multiple Organization and Multiple Peer App Demo #1 - Intro

Prerequisites

We find that Blockchain can be finicky when it comes to installing Node. We want to share this StackOverflow response - because many times the errors you see with Compose are derived in having installed either the wrong Node version or took an approach that is not supported by Compose:

• IBM Cloud account
• Docker - latest
• Docker Compose - latest
• NPM - latest
• nvm - latest
• Node.js - Node v8.9.x
• Git client - latest
• Python - 2.7.x
• React - 15.6.1

Steps

Steps

To run a local network, you can find steps here

1. Create IBM Cloud services
2. Build a network - Certificate Authority
3. Build a network - Create MSP Definitions
4. Build a network - Create Peers
5. Build a network - Create Orderer
6. Build a network - Create and Join Channel
7. Deploy Insurance Smart Contract on the network
8. Connect application to the network
9. Enroll App Admin Identities
10. Run the application

Important Note: This pattern is more advanced because it uses four organizations. For this reason, you will likely have to get a paid kubernetes cluster to run this pattern on the cloud, since a free cluster will not have the CPU/storage necessary to deploy all of the pods that we need to run this pattern. There are other patterns that leverage a free Kubernetes cluster (and only two organizations), so if you want to try that one out first, go here.

Step 1. Create IBM Cloud services

• Create the IBM Cloud Kubernetes Service. You can find the service in the Catalog. Note that for this code pattern, we need to use the 32CPU, 32GB RAM cluster.

• Once you reach the create a new cluster page you will need to do the following:

  • Choose standard cluster type
  • Fill out cluster name
  • choose Geography: North America
  • Choose Location and availability: Multizone
  • Choose Metro: Dallas
  • Choose Worker nodes: Dallas 10 only
  • Choose Master service endpoint: Both private & public endpoints
  • Choose Default worker pool: 1.12.7 (Stable, Default)
  • Choose Master service endpoint: Both private & public endpoints
  • Choose Flavor 32 Cores 32GB RAM, Ubuntu 18
  • Choose Encrypt local disk Yes
  • Choose Worker nodes 3
  • Click on create cluster. The cluster takes around 15-20 minutes to provision, so please be patient!

• After your kubernetes cluster is up and running, you can deploy your IBM Blockchain Platform V2 Beta on the cluster. The service walks through few steps and finds your cluster on the IBM Cloud to deploy the service on.

• Once the Blockchain Platform is deployed on the Kubernetes cluster, you can launch the console to start operating on your blockchain network.

Step 2. Build a network - Certificate Authority

We will build a network as provided by the IBM Blockchain Platform documentation. This will include creating a channel with a single peer organization with its own MSP and CA (Certificate Authority), and an orderer organization with its own MSP and CA. We will create the respective identities to deploy peers and operate nodes.

• Create your insurance organization CA

  • Click Add Certificate Authority.
  • Click IBM Cloud under Create Certificate Authority and Next.
  • Give it a Display name of Insurance CA.
  • Specify an Admin ID of admin and Admin Secret of adminpw.

• Create your shop organization CA (process is same as shown in gif above)

  • Click Add Certificate Authority.
  • Click IBM Cloud under Create Certificate Authority and Next.
  • Give it a Display name of Shop CA.
  • Specify an Admin ID of admin and Admin Secret of adminpw.

• Create your repair shop organization CA (process is same as shown in gif above)

  • Click Add Certificate Authority.
  • Click IBM Cloud under Create Certificate Authority and Next.
  • Give it a Display name of Repair Shop CA.
  • Specify an Admin ID of admin and Admin Secret of adminpw.

• Create your police organization CA (process is same as shown in gif above)

  • Click Add Certificate Authority.
  • Click IBM Cloud under Create Certificate Authority and Next.
  • Give it a Display name of Police CA.
  • Specify an Admin ID of admin and Admin Secret of adminpw.

• Use your CA to register insurance identities

  • Select the Insurance CA Certificate Authority that we created.
  • First, we will register an admin for our Insurance Organization. Click on the Register User button. Give an Enroll ID of insuranceAdmin, and Enroll Secret of insuranceAdminpw. Click Next. Set the Type for this identity as client and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.
  • We will repeat the process to create an identity of the peer. Click on the Register User button. Give an Enroll ID of insurancePeer, and Enroll Secret of insurancePeerpw. Click Next. Set the Type for this identity as peer and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.

• Use your CA to register shop identities (process is same as shown in gif above)

  • Select the Shop CA Certificate Authority that we created.
  • First, we will register an admin for our Insurance Organization. Click on the Register User button. Give an Enroll ID of shopAdmin, and Enroll Secret of shopAdminpw. Click Next. Set the Type for this identity as client and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.
  • We will repeat the process to create an identity of the peer. Click on the Register User button. Give an Enroll ID of shopPeer, and Enroll Secret of shopPeerpw. Click Next. Set the Type for this identity as peer and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.

• Use your CA to register repair shop identities (process is same as shown in gif above)

  • Select the Repair Shop CA Certificate Authority that we created.
  • First, we will register an admin for our Insurance Organization. Click on the Register User button. Give an Enroll ID of repairShopAdmin, and Enroll Secret of repairShopAdminpw. Click Next. Set the Type for this identity as client and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.
  • We will repeat the process to create an identity of the peer. Click on the Register User button. Give an Enroll ID of repairShopPeer, and Enroll Secret of repairShopPeerpw. Click Next. Set the Type for this identity as peer and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.

• Use your CA to register police shop identities (process is same as shown in gif above)

  • Select the Police CA Certificate Authority that we created.
  • First, we will register an admin for our Insurance Organization. Click on the Register User button. Give an Enroll ID of policeAdmin, and Enroll Secret of policeAdminpw. Click Next. Set the Type for this identity as client and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.
  • We will repeat the process to create an identity of the peer. Click on the Register User button. Give an Enroll ID of policePeer, and Enroll Secret of policePeerpw. Click Next. Set the Type for this identity as peer and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.

Step 3. Build a network - Create MSP Definitions

• Create the insurance MSP definition

  • Navigate to the Organizations tab in the left navigation and click Create MSP definition.
  • Enter the MSP Display name as Insurance MSP and an MSP ID of insurancemsp.
  • Under Root Certificate Authority details, specify the peer CA that we created Insurance CA as the root CA for the organization.
  • Give the Enroll ID and Enroll secret for your organization admin, insuranceAdmin and insuranceAdminpw. Then, give the Identity name, Insurance Admin.
  • Click the Generate button to enroll this identity as the admin of your organization and export the identity to the wallet. Click Export to export the admin certificates to your file system. Finally click Create MSP definition.

• Create the shop MSP definition (same process as shown in gif above)

  • Navigate to the Organizations tab in the left navigation and click Create MSP definition.
  • Enter the MSP Display name as Shop MSP and an MSP ID of shopmsp.
  • Under Root Certificate Authority details, specify the peer CA that we created Shop CA as the root CA for the organization.
  • Give the Enroll ID and Enroll secret for your organization admin, shopAdmin and shopAdminpw. Then, give the Identity name, Shop Admin.
  • Click the Generate button to enroll this identity as the admin of your organization and export the identity to the wallet. Click Export to export the admin certificates to your file system. Finally click Create MSP definition.

• Create the repair shop MSP definition (same process as shown in gif above)

  • Navigate to the Organizations tab in the left navigation and click Create MSP definition.
  • Enter the MSP Display name as Repair Shop MSP and an MSP ID of repairshopmsp.
  • Under Root Certificate Authority details, specify the peer CA that we created Shop CA as the root CA for the organization.
  • Give the Enroll ID and Enroll secret for your organization admin, repairShopAdmin and repairShopAdminpw. Then, give the Identity name, Repair Shop Admin.
  • Click the Generate button to enroll this identity as the admin of your organization and export the identity to the wallet. Click Export to export the admin certificates to your file system. Finally click Create MSP definition.

• Create the police MSP definition (same process as shown in gif above)

  • Navigate to the Organizations tab in the left navigation and click Create MSP definition.
  • Enter the MSP Display name as Police MSP and an MSP ID of policemsp.
  • Under Root Certificate Authority details, specify the peer CA that we created Shop CA as the root CA for the organization.
  • Give the Enroll ID and Enroll secret for your organization admin, policeAdmin and policeAdminpw. Then, give the Identity name, Police Admin.
  • Click the Generate button to enroll this identity as the admin of your organization and export the identity to the wallet. Click Export to export the admin certificates to your file system. Finally click Create MSP definition.

Step 4. Build a network - Create Peers

• Create an insurance peer
  • On the Nodes page, click Add peer.
  • Click IBM Cloud under Create a new peer and Next.
  • Give your peer a Display name of Insurance Peer.
  • On the next screen, select Insurance CA as your Certificate Authority. Then, give the Enroll ID and Enroll secret for the peer identity that you created for your peer, insurancePeer, and insurancePeerpw. Then, select the Administrator Certificate (from MSP), Insurance MSP, from the drop-down list and click Next.
  • Give the TLS Enroll ID, admin, and TLS Enroll secret, adminpw, the same values are the Enroll ID and Enroll secret that you gave when creating the CA. Leave the TLS CSR hostname blank.
  • The last side panel will ask you to Associate an identity and make it the admin of your peer. Select your peer admin identity Insurance Admin.
  • Review the summary and click Submit.

• Create a shop peer (same process as shown in gif above)

  • On the Nodes page, click Add peer.
  • Click IBM Cloud under Create a new peer and Next.
  • Give your peer a Display name of Shop Peer.
  • On the next screen, select Shop CA as your Certificate Authority. Then, give the Enroll ID and Enroll secret for the peer identity that you created for your peer, shopPeer, and shopPeerpw. Then, select the Administrator Certificate (from MSP), Shop MSP, from the drop-down list and click Next.
  • Give the TLS Enroll ID, admin, and TLS Enroll secret, adminpw, the same values are the Enroll ID and Enroll secret that you gave when creating the CA. Leave the TLS CSR hostname blank.
  • The last side panel will ask you to Associate an identity and make it the admin of your peer. Select your peer admin identity Shop Admin.
  • Review the summary and click Submit.

• Create a repair shop peer (same process as shown in gif above)

  • On the Nodes page, click Add peer.
  • Click IBM Cloud under Create a new peer and Next.
  • Give your peer a Display name of Repair Shop Peer.
  • On the next screen, select Repair Shop CA as your Certificate Authority. Then, give the Enroll ID and Enroll secret for the peer identity that you created for your peer, repairShopPeer, and repairShopPeerpw. Then, select the Administrator Certificate (from MSP), Shop MSP, from the drop-down list and click Next.
  • Give the TLS Enroll ID, admin, and TLS Enroll secret, adminpw, the same values are the Enroll ID and Enroll secret that you gave when creating the CA. Leave the TLS CSR hostname blank.
  • The last side panel will ask you to Associate an identity and make it the admin of your peer. Select your peer admin identity Repair Shop Admin.
  • Review the summary and click Submit.

• Create a police peer (same process as shown in gif above)

  • On the Nodes page, click Add peer.
  • Click IBM Cloud under Create a new peer and Next.
  • Give your peer a Display name of Police Peer.
  • On the next screen, select Police CA as your Certificate Authority. Then, give the Enroll ID and Enroll secret for the peer identity that you created for your peer, policePeer, and policePeerpw. Then, select the Administrator Certificate (from MSP), Shop MSP, from the drop-down list and click Next.
  • Give the TLS Enroll ID, admin, and TLS Enroll secret, adminpw, the same values are the Enroll ID and Enroll secret that you gave when creating the CA. Leave the TLS CSR hostname blank.
  • The last side panel will ask you to Associate an identity and make it the admin of your peer. Select your peer admin identity Police Admin.
  • Review the summary and click Submit.

Step 5. Build a network - Create Orderer

• Create your orderer organization CA

  • Click Add Certificate Authority.
  • Click IBM Cloud under Create Certificate Authority and Next.
  • Give it a unique Display name of Orderer CA.
  • Specify an Admin ID of admin and Admin Secret of adminpw.

• Use your CA to register orderer and orderer admin identities (shown in gif above)

  • In the Nodes tab, select the Orderer CA Certificate Authority that we created.
  • First, we will register an admin for our organization. Click on the Register User button. Give an Enroll ID of ordereradmin, and Enroll Secret of ordereradminpw. Click Next. Set the Type for this identity as client and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.
  • We will repeat the process to create an identity of the orderer. Click on the Register User button. Give an Enroll ID of orderer1, and Enroll Secret of orderer1pw. Click Next. Set the Type for this identity as peer and select org1 from the affiliated organizations drop-down list. We will leave the Maximum enrollments and Add Attributes fields blank.

• Create the orderer organization MSP definition

  • Navigate to the Organizations tab in the left navigation and click Create MSP definition.
  • Enter the MSP Display name as Orderer MSP and an MSP ID of orderermsp.
  • Under Root Certificate Authority details, specify the peer CA that we created Orderer CA as the root CA for the organization.
  • Give the Enroll ID and Enroll secret for your organization admin, ordereradmin and ordereradminpw. Then, give the Identity name, Orderer Admin.
  • Click the Generate button to enroll this identity as the admin of your organization and export the identity to the wallet. Click Export to export the admin certificates to your file system. Finally click Create MSP definition.

• Create an orderer

  • On the Nodes page, click Add orderer.
  • Click IBM Cloud and proceed with Next.
  • Give your peer a Display name of Orderer.
  • On the next screen, select Orderer CA as your Certificate Authority. Then, give the Enroll ID and Enroll secret for the peer identity that you created for your orderer, orderer1, and orderer1pw. Then, select the Administrator Certificate (from MSP), Orderer MSP, from the drop-down list and click Next.
  • Give the TLS Enroll ID, admin, and TLS Enroll secret, adminpw, the same values are the Enroll ID and Enroll secret that you gave when creating the CA. Leave the TLS CSR hostname blank.
  • The last side panel will ask to Associate an identity and make it the admin of your peer. Select your peer admin identity Orderer Admin.
  • Review the summary and click Submit.

• Add organizations as Consortium Member on the orderer to transact

  • Navigate to the Nodes tab, and click on the Orderer that we created.
  • Under Consortium Members, click Add organization.
  • From the drop-down list, select Insurance MSP.
  • Click Submit.
  • Repeat the same steps, but add Shop MSP, Repair Shop MSP, and Police MSP as well.

Step 6. Build a network - Create and Join Channel

• Create the channel

  • Navigate to the Channels tab in the left navigation.
  • Click Create channel.
  • Give the channel a name, mychannel.
  • Select the orderer you created, Orderer from the orderers drop-down list.
  • Select the MSP identifying the organization of the channel creator from the drop-down list. This should be Insurance MSP (insurancemsp).
  • Associate available identity as Insurance Admin.
  • Click Add next to the insurance organization. Make the insurance organization an Operator.
  • Click Add next to the shop organization. Make the shop organization an Operator.
  • Click Add next to the repair shop organization. Make the repair shop organization an Operator.
  • Click Add next to the police organization. Make the insurance organpoliceization an Operator.
  • Click Create.

• Join your peer to the channel

  • Click Join channel to launch the side panels.
  • Select your Orderer and click Next.
  • Enter the name of the channel you just created. mychannel and click Next.
  • Select which peers you want to join the channel, click Insurance Peer, Shop Peer, Repair Shop Peer, and Police Peer.
  • Click Submit.

• Add anchor peers to the channel

  • In order to communicate between organizations, we need to enroll anchor peers.
  • From the channels tab, click on the channel you have created, mychannel.
  • From the channel overview page, click on channel details. Scroll all the way down until you see Anchor peers.
  • Click Add anchor peer and add the Insurance, Police, Repair Shop, and Shop peers.
  • Select which peers you want to join the channel, click Insurance Peer, Shop Peer, Repair Shop Peer, and Police Peer.
  • Click Add anchor peer.
  • If all went well, your channel Anchor peers should look like below:

Step 7. Deploy Insurance Smart Contract on the network

• Install a smart contract

• Clone the repository:

  git clone https://github.com/IBM/build-blockchain-insurance-app

  • Click the Smart contracts tab to install the smart contract.
  • Click Install smart contract to upload the insurance smart contract package file.
  • Click on Add file and find your packaged smart contract. It is the file in the build-blockchain-insurance-app/chaincodePackage directory.
  • Once the contract is uploaded, click Install.

• Instantiate smart contract

  • On the smart contracts tab, find the smart contract from the list installed on your peers and click Instantiate from the overflow menu on the right side of the row.
  • On the side panel that opens, select the channel, mychannel to instantiate the smart contract on. Click Next.
  • Select the organization members to be included in the policy, insurancemsp, shopmsp, repairshopmsp, policemsp. Click Next.
  • Give Function name of Init and leave Arguments blank.
  • Click Instantiate.

Step 8. Connect application to the network

• Connect with sdk through connection profile

  • Under the Instantiated Smart Contract, click on Connect with SDK from the overflow menu on the right side of the row.
  • Choose from the dropdown for MSP for connection, insurancemsp.
  • Choose from Certificate Authority dropdown, Insurance CA.
  • Download the connection profile by scrolling down and clicking Download Connection Profile. This will download the connection json which we will use soon to establish connection.
  • You can click Close once the download completes.

• Create insurance application admin

  • Go to the Nodes tab on the left bar, and under Certificate Authorities, choose your Insurance CA.
  • Click on Register user.
  • Give an Enroll ID and Enroll Secret to administer your application users, insuranceApp-admin and insuranceApp-adminpw.
  • Choose client as Type and any organization for affiliation. We can pick org1 to be consistent.
  • You can leave the Maximum enrollments blank.
  • Under Attributes, click on Add attribute. Give attribute as hf.Registrar.Roles = *. This will allow this identity to act as registrar and issues identities for our app. Click Add-attribute.
  • Click Register.

• Create shop application admin (same process as shown above in the gif)

  • Go to the Nodes tab on the left bar, and under Certificate Authorities, choose your Shop CA.
  • Click on Register user.
  • Give an Enroll ID and Enroll Secret to administer your application users, shopApp-admin and shopApp-adminpw.
  • Choose client as Type and any organization for affiliation. We can pick org1 to be consistent.
  • You can leave the Maximum enrollments blank.
  • Under Attributes, click on Add attribute. Give attribute as hf.Registrar.Roles = *. This will allow this identity to act as registrar and issues identities for our app. Click Add-attribute.
  • Click Register.

• Create repair shop application admin (same process as shown above in the gif)

  • Go to the Nodes tab on the left bar, and under Certificate Authorities, choose your Shop CA.
  • Click on Register user.
  • Give an Enroll ID and Enroll Secret to administer your application users, repairShopApp-admin and repairShopApp-adminpw.
  • Choose client as Type and any organization for affiliation. We can pick org1 to be consistent.
  • You can leave the Maximum enrollments blank.
  • Under Attributes, click on Add attribute. Give attribute as hf.Registrar.Roles = *. This will allow this identity to act as registrar and issues identities for our app. Click Add-attribute.
  • Click Register.

• Create police application admin (same process as shown above in the gif)

  • Go to the Nodes tab on the left bar, and under Certificate Authorities, choose your Shop CA.
  • Click on Register user.
  • Give an Enroll ID and Enroll Secret to administer your application users, policeApp-admin and policeApp-adminpw.
  • Choose client as Type and any organization for affiliation. We can pick org1 to be consistent.
  • You can leave the Maximum enrollments blank.
  • Under Attributes, click on Add attribute. Give attribute as hf.Registrar.Roles = *. This will allow this identity to act as registrar and issues identities for our app. Click Add-attribute.
  • Click Register.

Update application connection

• Copy the connection profile you downloaded into the web/www/blockchain directory.
• Copy and paste everything in the connection profile, and overwrite the ibpConnection.json.

Step 9. Enroll App Admin Identities

• Enroll insurnaceApp-admin

  • First, navigate to the web/www/blockchain directory.

    cd web/www/blockchain/

  • Open the config.json file, and update the caName with the URL of the insurance certificate authority from your ibpConnection.json file. Save the file.

  • Run the enrollAdmin.js script

    node enrollAdmin.js

  • You should see the following in the terminal:

    msg: Successfully enrolled admin user insuranceApp-admin and imported it into the wallet

• Enroll shopApp-admin

  • First, change the appAdmin, appAdminSecret, and caName properties in your config.json file, so that it looks something like this (your caName should be different than mine):

    {
        "connection_file": "ibpConnection.json",
        "appAdmin": "shopApp-admin",
        "appAdminSecret": "shopApp-adminpw",
        "orgMSPID": "shopmsp",
        "caName": "https://fa707c454921423c80ec3c3c38d7545c-caf2e287.horeainsurancetest.us-south.containers.appdomain.cloud:7054",
        "userName": "shopUser",
        "gatewayDiscovery": { "enabled": true, "asLocalhost": false }
    }

  • To find the other CA urls, you will need to click on the Nodes tab in IBM Blockchain Platform, then on the Shop CA, and on the settings cog icon at the top of the page. That will take you to the certificate authority settings, as shown in the picture below, and you can copy that endpoint URL into your config.json caName field.

• Run the enrollAdmin.js script

  node enrollAdmin.js

• You should see the following in the terminal:

  msg: Successfully enrolled admin user shopApp-admin and imported it into the wallet

• Enroll repairShopApp-admin (same process as shown in gif above)

  • First, change the appAdmin, appAdminSecret, and caName properties in your config.json file, so that it looks something like this (your caName should be different than mine):

    {
        "connection_file": "ibpConnection.json",
        "appAdmin": "repairShopApp-admin",
        "appAdminSecret": "repairShopApp-adminpw",
        "orgMSPID": "repairshopmsp",
        "caName": "https://fa707c454921423c80ec3c3c38d7545c-caf2e287.horeainsurancetest.us-south.containers.appdomain.cloud:7054",
        "userName": "repairUser",
        "gatewayDiscovery": { "enabled": true, "asLocalhost": false }
    }

  • Run the enrollAdmin.js script

    node enrollAdmin.js

  • You should see the following in the terminal:

    msg: Successfully enrolled admin user repairShopApp-admin and imported it into the wallet

• Enroll policeApp-admin (same process as shown in gif above)

  • First, change the appAdmin, appAdminSecret, and caName properties in your config.json file, so that it looks something like this (your caName should be different than mine):

    {
        "connection_file": "ibpConnection.json",
        "appAdmin": "policeApp-admin",
        "appAdminSecret": "policeApp-adminpw",
        "orgMSPID": "policemsp",
        "caName": "https://fa707c454921423c80ec3c3c38d7545c-caf2e287.horeainsurancetest.us-south.containers.appdomain.cloud:7054",
        "userName": "policeUser",
        "gatewayDiscovery": { "enabled": true, "asLocalhost": false }
    }

  • Run the enrollAdmin.js script

    node enrollAdmin.js

  • You should see the following in the terminal:

    msg: Successfully enrolled admin user policeApp-admin and imported it into the wallet

Step 10. Run the application

Navigate to the root directory of the project:

cd IBM-db2-blockchain-insurance-application

Login using your docker hub credentials.

docker login

Run the build script to download and create docker images for the orderer, insurance-peer, police-peer, shop-peer, repairshop-peer, web application and certificate authorities for each peer. This will run for a few minutes.

For Mac user:

cd IBM-db2-blockchain-insurance-application
./build_mac.sh

For Ubuntu user:

cd IBM-db2-blockchain-insurance-application
./build_ubuntu.sh

You should see the following output on console:

Creating db2-fabric ...
Creating repairshop-ca ...
Creating insurance-ca ...
Creating shop-ca ...
Creating police-ca ...
Creating orderer0 ...
Creating repairshop-ca
Creating insurance-ca
Creating police-ca
Creating shop-ca
Creating orderer0 ... done
Creating insurance-peer ...
Creating insurance-peer ... done
Creating shop-peer ...
Creating shop-peer ... done
Creating repairshop-peer ...
Creating repairshop-peer ... done
Creating web ...
Creating police-peer ...
Creating web
Creating police-peer ... done
Creating db2-fabric ... done

Wait for few minutes for application to install and instantiate the chaincode on network

Check the status of installation using command:

docker logs web

On completion, you should see the following output on console:

> [email protected] serve /app
> cross-env NODE_ENV=production&&node ./bin/server

/app/app/static/js
Server running on port: 3000
Default channel not found, attempting creation...
Successfully created a new default channel.
Joining peers to the default channel.
Chaincode is not installed, attempting installation...
Base container image present.
info: [packager/Golang.js]: packaging GOLANG from bcins
info: [packager/Golang.js]: packaging GOLANG from bcins
info: [packager/Golang.js]: packaging GOLANG from bcins
info: [packager/Golang.js]: packaging GOLANG from bcins
Successfully installed chaincode on the default channel.
Successfully instantiated chaincode on all peers.

Setting up Db2 instance

In order to setup Db2 we will be using the zeppelin-notebook container, where Apache Zeppelin is setup and running, which is a web-based notebook that enables interactive data analytics. We will configure Apache Zeppelin to connect to Db2 instance.

We need to make sure the db2-fabric container is up and running. The container runs a lightweight community edition of Db2. You can execute docker logs db2-fabric to see the progress and status of the Db2 instance. You can keep executing this command to get the latest information for this container until you see:

(*) All databases are now active. (*) Setup has completed.

Once the installation is done, Lets setup the Db2 instance that was just created. To setup we need to exec inside the db2-fabric. For this run:

docker exec -it db2-fabric bash

You can then execute a setup script that sets some environment variables for DB2 and logging details. We then stop and start the database manager to pull in the latest configuration details. To do this run the following:

su - db2inst1 -c '/db2-container/setup-instance.sh' && su - db2inst1 -c 'db2stop' && su - db2inst1 -c 'db2start'

Sample Blockchain Insurance App Walkthrough

Use the link http://localhost:3000 to load the web application in browser.

The home page shows the participants (Peers) in the network. You can see that there is an Insurance, Repair Shop, Police and Shop Peer implemented. They are the participants of the network.

Imagine being a consumer (hereinafter called “Biker”) that wants to buy a phone, bike or Ski. By clicking on the “Go to the shop” section, you will be redirected to the shop (shop peer) that offers you the following products.

You can see the three products offered by the shop(s) now. In addition, you have insurance contracts available for them. In our scenario, you are an outdoor sport enthusiast who wants to buy a new Bike. Therefore, you’ll click on the Bike Shop section.

In this section, you are viewing the different bikes available in the store. You can select within four different Bikes. By clicking on next you’ll be forwarded to the next page which will ask for the customer’s personal data.

You have the choice between different insurance contracts that feature different coverage as well as terms and conditions. You are required to type-in your personal data and select a start and end date of the contract. Since there is a trend of short-term or event-driven contracts in the insurance industry you have the chance to select the duration of the contract on a daily basis. The daily price of the insurance contract is being calculated by a formula that had been defined in the chaincode. By clicking on next you will be forwarded to a screen that summarizes your purchase and shows you the total sum.

The application will show you the total sum of your purchase. By clicking on “order” you agree to the terms and conditions and close the deal (signing of the contract). In addition, you’ll receive a unique username and password. The login credentials will be used once you file a claim. A block is being written to the Blockchain.

note You can see the block by clicking on the black arrow on the bottom-right.

At this point, you should be able to go into your IBM Blockchain Platform console, click on the channels, and then be able to see the contract_create block being added.

For additional steps on how to file more claims, and use the rest of the application, please go here.

Congratulations! You've successfully connection your React app to the IBM Blockchain Platform! Now each time you submit transactions with the UI, they will be logged by the blockchain service.

Configure a Federated Server to Access the Blockchain

To learn about Db2 federated server please follow go here

To setup the Db2 federated server, execute the following script in the db2-fabric container:

docker exec -it db2-fabric bash
su - db2inst1 -c "db2 connect to testdb && db2 -tvf /samples/insurance-setup.sql"

The SQL file located in the ./db2-fabric/db2-container/samples directory titled insurance-setup.sql contains details on how the server is created.

Manage Interpreter Settings in Zeppelin Notebook

Zeppelin notebook uses Db2 federated server and SQL to run queries on the blockchain network. We need to configure zeppelin interpreter details and specify Db2 connection parameters. Zeppelin Interpreter is the plug-in which enable zeppelin user to use a specific language/data-processing-backend. Navigate to http://localhost:8080 where the zeppelin-notebook is running.

Select Interpreter from top right corner of the Anonymous user. We need to modify jdbc and sh settings.

Search jdbc from the text box and modify the following details:

default.driver  -->  com.ibm.db2.jcc.DB2Driver
default.url --> jdbc:db2://db2-fabric:50000/testdb
default.user --> db2inst1
default.password --> password

1. db2 is the relational database we are using
2. db2-fabric is the name of the docker container that db2 is running on
3. 50000 is the open port we will be accessing
4. testdb is the name of the database that we want to connect to

Search for sh from the text box and modify the following details:

shell.command.timeout.millisecs --> 600000

This will ensure that we won’t receive a timeout when executing a datagenerator job.

Db2 jar dependency

Also add the location of Db2 JDBC driver artifact under Dependencies. Add /opt/zeppelin/notebook/db2jcc.jar in the text field and save.

Generate Transactions on the Blockchain

Navigate to zeppelin UI using http://localhost:8080. Before we can analyze the Blockchain, we must first create a notebook and generate some demo data. Import notebook by clicking import note from zeppelin home page and upload the json file from your repository in location zeppelin-notebook/notebook/Blockchain Demo.json

Open the notebook by clicking the uploaded notebook from the home page. The first cell has command that identifies the private key used to connect to the Blockchain app and will set this in the properties file.

We have bundled together a data generator written in Java, and the next command will run the data generator job.

java -cp /opt/zeppelin/notebook/fabric-datagen-dependencies-1.0-DATAGEN.jar com.ibm.federation.datagen.GenerateTransactions --config-file=/opt/zeppelin/notebook/insurance.properties --datagen-type=insurance --flows=5 --attempts=100 --channel-name=default --chaincode-name=bcins seed-concurrent --threads=2

This data generator is compatible with other Blockchain applications so we must specify the type of blockchain to use. In this case, datagen-type should be set to insurance.

Flows refers to the various paths a customer can take based off the events that occur during the purchase of a product.

From the Hyperledger Docs, A channel is defined as a private “subnet” of communication between two or more specific network members and we had configured the channel name to be default.

The chaincode name is defined as bcins

To generate transactions, select the first cell and click the play icon on the top right of the cell. Youc an then see transactions being generated on the blockchain by vieweing the Block explorer in the web app. There will be 50 transaction generated with 5 flows and this will take around 2 minutes to complete.

With valid transactions being generated on the Blockchain, we can now query the Blockchain.

Query Blockchain via Zeppelin Notebooks using SQL

With configuration of the Federation server completed and transactions generated, we can now focus on analyzing the Blockchain. From the data analysts persona who works for insurance organization, we can anticipate 3 lines of business who would be interested in exploring different kinds of business insights from this network.

Insurance Sales Reporting focuses on analyzing the amount. Some insights can be:

1. How many Contract were sold and over what period of time?
2. What’s the policy purchase distribution over various dates/months?
3. How much Revenue has been generated by selling policies in total or quarters?

Insurance Claim Analysis. Some insights can be:

1. How many claims were filed for each product?
2. What is the exposure for each product?

Insurance Risk Analysis. Some insights can be:

1. What is the comparison between revenue vs claims paid?
2. Are there any fraud claims that cannot be verified by police or theft?

We can start off by doing some basic exploration of data to see what we are dealing with.

Using the nickname nn_tx we had created for accessing transactions as local tables, we can execute a select * to get an understanding on this table.

Some noticeable columns to point out are

ID: 
BLOCK_ORDINAL:
ORDINAL:
CHANNEL_ID:
CREATION_TIME:
CREATOR_MSPID
CREATOR_CERT
IS_VALID
VALIDATION_CODE
IS_TRANSACTION
SIGNATURE
CHAINCODE_ID:
ENDORSEMENT_CODE:
ARGS_COUNT:

In this blockchain application, there are three argument columns that we can use.

ARG_0 stores
ARG_1 stores
ARG_2 stores the business logic and is the most useful column that we can leverage

Here is an example of a JSON Payload with business details:

{
   “contract_type_uuid":"17d773dc-2624-4c22-a478-87544dd0a17f",
   "username":"[email protected]",
   "password":"",
   "first_name":"Colin",
   "last_name":"Bell",
   "item":{
      "id":1,
      "brand":"Apple",
      "model":"6",
      "price":630,
      "serial_no":"ZE5YYL"
   },
   "start_date":"2018-12-11T19:54:29.168Z",
   "end_date":"2018-12-23T01:40:20.736Z",
   "uuid":"3163b36c-0629-4974-bfbd-bdcb09f90a26"
}

For each insight there is a query you can run in the respective cell of the zeppelin notebook you have uploaded, to get the insight details.

Additional resources

Following is a list of additional blockchain resources:

• Fundamentals of IBM Blockchain
• Hyperledger Fabric Documentation
• Hyperledger Fabric code on GitHub

Troubleshooting

• Run clean.sh to remove the docker images and containers for the insurance network.

./clean.sh

License

This code pattern is licensed under the Apache Software License, Version 2. Separate third party code objects invoked within this code pattern are licensed by their respective providers pursuant to their own separate licenses. Contributions are subject to the Developer Certificate of Origin, Version 1.1 (DCO) and the Apache Software License, Version 2.

Apache Software License (ASL) FAQ