BLCN 532 University of the Cumberlands Writing Chaincode Lab Report Now  that you have a running business network, you can write, install, and  run smart c

BLCN 532 University of the Cumberlands Writing Chaincode Lab Report Now  that you have a running business network, you can write, install, and  run smart contracts, called chaincode, to interacts with your  blockchain. Chancode makes up your blockchain application and provides  the only way for users to read from, and append to, the blockchain.
In  this lab you’ll examine several chaincode files, run the sample  chaincode presented in your textbook, and run tests on the chaincode to  assess its functionality. BLCN532 Lab 2
Writing chaincode
V2.0
Introduction
Now that you have a running business network, you can write, install, and run smart contracts, called
chaincode, to interacts with your blockchain. Chancode makes up your blockchain application and
provides the only way for users to read from, and append to, the blockchain.
In this lab you’ll examine several chaincode files, run the sample chaincode presented in your textbook,
and run tests on the chaincode to assess its functionality.
Lab Deliverables:
To complete this lab, you must create a Lab Report file and submit the file in iLearn. The Lab Report file
must be a Microsoft Word format (.docx), and have the filename with the following format:
BLCN532_SECTION_STUDENTID_LASTNAME_FIRSTNAME_Lab02.docx
•
•
•
•
SECTION is the section number of your current course (2 digits)
STUDENTID is your student ID number (with leading zeros)
LASTNAME is your last name
FIRSTNAME is your first name
To get started, create a Microsoft Word document (.docx) with the correct filename for this lab. You’ll
be asked to enter text and paste screenshots into the lab report file.
NOTE: All screenshots MUST be readable. Use the Ubuntu Screen Capture utility (see the lab video.)
Make sure that you label each screenshot (i.e. Step 2.1.3) and provide screenshots in order. For
commands that produce lots of output, I only want to see the last full screen when the command
finishes. Provide FULL screenshots, NOT cropped images.
SECTION 1: Running chaincode
Step 1.1: Launch the sample trade network in development mode
First, you’ll start your sample business network in development mode (note the ‘-d’ option).
1.
2.
3.
4.
5.
6.
7.
8.
Open PowerShell
PS %HOME%> cd vagranthyperledger
PS %HOME%vagrantHyperledger> vagrant up
Login to your Linux VM (userid: vagrant password: vagrant) and open a Terminal window.
$ cd $GOPATH/src/trade-finance-logistics/network
$ ./trade.sh up -d true
$ date
Create a screenshot of the results of steps 5 – 7 and paste it into your Lab Report File.
Step 1.2: Compile the chaincode
Next, you’ll use a different PuTTY connection to compile and run the chaincode.
1. Open a new Terminal window.
NOTE: This is the SECOND Terminal CONNECTION for screenshots in later steps.
2.
3.
4.
5.
$ cd $GOPATH/src/trade-finance-logistics/network
$ docker exec -it chaincode bash
# cd trade_workflow_v1 (Note the new prompt)
# go build
Step 1.3: Run the chaincode
Now you can run the chaincode you just compiled.
1. # export CORE_PEER_ADDRESS=peer:7052
2. # export CORE_CHAINCODE_ID_NAME=tw:0
3. # ./trade_workflow_v1 (This is a server process, so you won’t get a prompt back.)
Step 1.4: Install and run the chaincode on the channel
1. Open a New (3rd) Terminal window.
2. $ cd $GOPATH/src/trade-finance-logistics/network
3. $ docker exec -it cli bash
4. # peer chaincode install -p chaincodedev/chaincode/trade_workflow_v1 -n tw -v 0
5. Create a screenshot (in the current Terminal window) of the results of step 4 and paste it into
your Lab Report File.
6. # peer chaincode instantiate -n tw -v 0 -c ‘{“Args”:
[“init”,”LumberInc”,”LumberBank”,”100000″,”Wooden Toys”,”ToyBank”,”200000″,”Universal
Freight”,”ForestryDepartment”]}’ -C tradechannel
7. # peer chaincode invoke -n tw -c ‘{“Args”: [“requestTrade”,”trade-12”,”50000″,”Wood for
Toys”]}’ -C tradechannel
NOTE: the command in step 7 doesn’t copy-paste well. You’ll just have to type it.
8. Create a screenshot (in the current Terminal window) of the results of step 7 and paste it into
your Lab Report File.
9. # peer chaincode invoke -n tw -c ‘{“Args”: [“getTradeStatus”,”trade-12″]}’ -C tradechannel
10. Create a screenshot (in the current Terminal window) of the results of step 9 and paste it into
your Lab Report File.
11. In the SECOND Terminal window (the one you opened in step 1.2), create a screenshot of the
results of step 9 and paste that screenshot into your Lab Report File.
SECTION 2: Reviewing chaincode source code
Step 2.1:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Open a New Terminal window.
$ cd $GOPATH/src/trade-finance-logistics/chaincode/src/github.com/trade_workflow_v1
nano tradeWorkflow.go
Follow the source code development process in the textbook, starting with the “Creating a
chaincode” section.
Find the Invoke() method in the editor. (Make sure the line starts with “func”.)
Create a screenshot (in the current Terminal window) of the results of step 5 and paste it into
your Lab Report File.
Find the requestTrade() method in the editor. (Make sure the line starts with “func”.)
Create a screenshot (in the current Terminal window) of the results of step 7 and paste it into
your Lab Report File.
Find the getTradeStatus() method in the editor. (Make sure the line starts with “func”.) You
invoked this method in the previous section (Step 1.4.9).
Scroll down to the end of the getTradeStatus() method. You should see the string “Query
Response:” in the next-to-last line in the method. This is the code that prints the trade status.
Create a screenshot (in the current Terminal window) of the results of step 10 and paste it into
your Lab Report File.
Exit nano
Section 3: Testing chaincode
Step 3.1: Test the chaincode
1.
2.
3.
4.
5.
6.
7.
8.
$ cd $GOPATH/src/trade-finance-logistics/chaincode/src/github.com/trade_workflow_v1
nano tradeWorkflow_test.go
Find the method that tests ShipmentInitiation.
Create a screenshot (in the current Terminal window) that shows the other methods (should be
7) the current method invokes to test its functionality. (You can find this information in a
program comment. Comments start with two forward slashes. Look for lines that start with
“//”.) Paste that screenshot into your Lab Report File.
Exit nano
$ go test
$ date
Create a screenshot (in the current Terminal window) of the results of steps 6 and 7 and paste
that screenshot into your Lab Report File.
Section 4: Wrapping up
Now that you have compiled, installed, run, and tested your chaincode, you need to properly shutdown
your business network.
1.
2.
3.
4.
5.
6.
7.
8.
Press CTRL-C in the SECOND Terminal window to return to the # prompt.
Type exit at the # prompt (in all Terminal windows except the first one) to exit docker.
$ ./trade.sh down -d true
Exit from your Linux sessions
$ exit
In Windows PowerShell, shut down your Hyperledger virtual machine:
PS %HOME%vagrantHyperledger> vagrant halt
Create a snapshot (NOT A SCREENSHOT) of your Ubuntu VM in VirtualBox. This allows you to
easily restore to this point if you ever need to “undo” subsequent steps and return to a known
point.
You should have 10 screenshots in your Lab Report File. Save your file and submit it in iLearn as a file
attachment for the Lab 2 assignment.
Congratulations! You have complete lab 2.
BLCN532 Lab 1
Set up your development environment
V2.0
Introduction
This course introduces students to blockchain development for enterprise environments. Before you can
develop software applications, you need to ensue your development environment is in place. That
means you’ll need all the tools and infrastructure installed and configured to support enterprise
blockchain software development projects.
In this lab you’ll set up your own Hyperledger Fabric development environment and install the course
software from the textbook. When you finish this lab, you’ll have a working development environment
and will be ready to start running and modifying blockchain applications.
The instructions in your textbook are for Mac and Linux computers. However, there is no guarantee that
your installation of MacOS or Linux is completely compatible with the environment in which the
commands from the textbook work properly. For that reason, I STRONGLY SUGGEST that you acquire an
Ubuntu 16.04 Virtual Machine (VM) for your labs. Using an Ubuntu 16.04 VM will make the labs far
easier to complete.
The instructions in this course’s labs assume that your computer runs the Windows operating system. If
you run MacOS or Linux, you can get Vagrant and VirtualBox for those operating systems and follow the
gist of the “Initial setup for Windows computers”.
Lab Deliverables:
To complete this lab, you must create a Lab Report file and submit the file in iLearn. The Lab Report file
must be a Microsoft Word format (.docx), and have the filename with the following format:
BLCN532_SECTION_STUDENTID_LASTNAME_FIRSTNAME_Lab01.docx
•
•
•
SECTION is the section number of your current course (2 digits)
STUDENTID is your student ID number (with leading zeros)
LASTNAME is your last name, FIRSTNAME is your first name
To get started, create a Microsoft Word document (.docx) with the correct filename for this lab. You’ll
be asked to enter text and paste screenshots into the lab report file.
NOTE: All screenshots MUST be readable. Use the Ubuntu Screen Capture utility (see the lab video.)
Make sure that you label each screenshot (i.e. Step 2.1.3) and provide screenshots in order. For
commands that produce lots of output, I only want to see the last full screen when the command
finishes. Provide FULL screenshots, NOT cropped images.
SECTION 1: Initial setup for Windows computers (Chapter 3)
Step 1.1: Install Oracle Virtualbox (Windows, Linux, MacOS)
Oracle Virtualbox is an open source virtualization environment that allows you to run multiple virtual
machines and containers on a single personal computer. Virtualbox is free and it is easy to install.
In your favorite web browser, navigate to: https://www.virtualbox.org/ and click the “Download
Virtualbox” button. Click the “Windows hosts” link to download the main installation executable. You
should also click the “All supported platforms” under the “Extension Pack” heading to download extra
software support for devices.
After you download the two files, double click each one to run the install procedure.
Step 1.2: Install Vagrant (Windows, Linux, MacOS)
Vagrant is a free virtual environment management utility. It makes the process of starting, stopping, and
managing virtual machines easier. In your web browser, navigate to https://www.vagrantup.com/ then
click the “Download” button, and click the version of the Windows executable you’d like to install. (Most
of you should select the “64-bit” version.)
Once you download the install program, double-click the file you just downloaded to install Vagrant.
If you want more information on Vagrant and tips on getting the most out of the software, navigate to:
https://www.sitepoint.com/getting-started-vagrant-windows/ .
Step 1.3: Set up your Vagrant project
After installing all the pre-requisite pieces, you need to set up your Vagrant project. A Vagrant project
defines your virtual machine environment and helps you organize your collection of VMs into a group
that is easy to manage.
We’ll use the Windows PowerShell as our Windows command prompt environment. PowerShell is a very
powerful command line interface that is available on all Windows computers.
To launch PowerShell, click the Windows key, type PowerShell, then click the Windows PowerShell
menu entry. The figure below shows a portion of the Windows PowerShell command prompt window.
PowerShell uses your user’s home directory as its starting directory. In my case, C:Usersmicha is my
home directory. For the rest of the lab, I’ll refer to this a %HOME%. Your %HOME% will be different.
1.3.1: Remove existing Vagrant projects
Follow these steps ONLY if you already have a previous Vagrant project you want to remove: (Assume
the project you want to remove is located in the %HOME%vagrantHyperledger directory.)
If you DO NOT have an existing Vagrant project that you need to remove, skip to section 1.3.2.
1. PS %HOME%vagrantHyperledger> vagrant global-status
Note the id of the listed VM(s). You’ll use this id in the next command, in place of xxxxxxx.
2. PS %HOME%vagrant\Hyperledger> vagrant destroy xxxxxxx
3. PS %HOME%vagrant\Hyperledger> vagrant box remove ubuntu/xenial64
1.3.2: Create a new Vagrant project for Hyperledger
Launch PowerShell and enter the following commands: (Don’t type ‘PS %HOME%>’, that’s just the
PowerShell prompt. Just type the characters in bold.)
1.
2.
3.
4.
5.
PS %HOME%> mkdir vagrant
PS %HOME%> cd vagrant
PS %HOME%vagrant> mkdir Hyperledger
PS %HOME%vagrant> cd Hyperledger
PS %HOME%vagrantHyperledger> vagrant init kelly219design/ubuntu-xenial-16.04-guidesktop-base
Make sure that you enter the line above as ONE LINE at the PowerShell prompt
6. Go to the Blackboard site (ucumberlands.blackcoard.com) and login.
7. Navigate to this course (BLCN532) -> Content for this week, Lab01.
a. Download the Vagrantfile file and copy it to the %HOME%vagrantHyperledger
directory. (This will overwrite the Vagrantfile that was already there.)
8. PS %HOME%vagrantHyperledger> vagrant up
NOTE: To stop your VM type vagrant halt in PowerShell
Section 2: Install Pre-requisites (Chapter 3)
Once you have an operating Linux VM, you can start to install the Hyperledger Fabric pre-requisites. In
this section you’ll install all the software and configuration pieces necessary to run the class enterprise
blockchain application in Hyperledger Fabric.
Step 2.1: Install pre-reqs
2.1.1: Install dev tools
1. If you haven’t started your VM, do the following:
a. Open Windows PowerShell, then navigate to your Hyperledger project directory.
b. PS %HOME%vagrantHyperledger> vagrant up
2. Login to your VM using the username: vagrant and password: vagrant
3. Click “Search your computer” (upper left corner icon), then type terminal.
4. Click on the Terminal icon to launch a terminal with a shell prompt.
You type all the following commands in your Linux VM (at the Terminal command prompt.)
Don’t type the ‘$’ character. That is the prompt character of a regular user to remind you that this is a
command you should enter in Linux. When you see a ‘#’ character, that indicates you are in an elevated
privilege shell. And the ‘>’ character indicates you’re in PowerShell. Pay attention to the prompt
characters – they give you valuable information about your current context.
5. $ sudo apt-get update
6. $ sudo apt-get install libltdl-dev
2.1.2: Install Docker-CE
You can find complete Docker-CE instructions/docs at: https://docs.docker.com/install/linux/dockerce/ubuntu/
1. $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add 2. $ sudo add-apt-repository “deb [arch=amd64] https://download.docker.com/linux/ubuntu
$(lsb_release -cs) stable”
Make sure that you enter the line above as ONE LINE in Linux
3. $ sudo apt-get update
4. $ sudo apt-get install docker-ce docker-ce-cli containerd.io
2.1.3: Install Docker compose
1. $ sudo curl -L “https://github.com/docker/compose/releases/download/1.23.2/dockercompose-$(uname -s)-$(uname -m)” -o /usr/local/bin/docker-compose
2. $ sudo chmod +x /usr/local/bin/docker-compose
3. $ docker-compose version
4. $ date
5. Create a screenshot of the results of steps 1 – 4 and paste it into your Lab Report File.
2.1.4: Install business network pre-reqs
1.
2.
3.
4.
5.
$ curl -O https://hyperledger.github.io/composer/latest/prereqs-ubuntu.sh
$ chmod u+x prereqs-ubuntu.sh
$ ./prereqs-ubuntu.sh
$ date
Create a screenshot of the results of steps 1 – 4 and paste it into your Lab Report File.
>>> Logout (use the gear icon in the upper right corner) and log back in before continuing.
2.1.5: Install GO language
The next step is to install the GO programming language. You’ll use GO to write and modify source code
files for the class blockchain application.
1.
2.
3.
4.
5.
$ sudo apt-get update
$ wget https://dl.google.com/go/go1.12.1.linux-amd64.tar.gz
$ tar xvf go1.12.1.linux-amd64.tar.gz
$ nano ~/.profile
In the nano editor, add the following 2 lines after the last line in the file:
export GOPATH=$HOME/go
export PATH=$PATH:$GOPATH/bin
6.
7.
8.
9.
10.
Save your file and exit nano
$ source .profile
$ go version
$ date
Create a screenshot of the results of steps 1 – 9 and paste it into your Lab Report File.
Step 2.2: Install source code and set up business network
In this step you download and install the class application source code and set up the business network.
2.2.1: Forking and Cloning the trade-finance-logistics repository
1. In a browser (in Windows) go to: https://github.com/HyperledgerHandsOn/trade-financelogistics
2. Sign up or log in
3. Click Fork
You type all the following commands in your Linux VM (at the command prompt.)
4.
5.
6.
7.
8.
9.
10.
11.
$ cd $GOPATH/src
$ git clone https://github.com/YOUR_GIT_ID/trade-finance-logistics.git
$ cd $GOPATH/src
$ mkdir -p github.com/hyperledger
$ cd github.com/hyperledger
$ git clone https://github.com/hyperledger/fabric.git -b release-1.1
$ cd fabric
EDIT FILES *****
a. $ nano Makefile
b. Find the line starts with CHAINTOOL_RELEASE (hint: use CTRL W to search)
c. Change the line you just found to this: CHAINTOOL_RELEASE=1.1.3
d. Find the line that starts with CHAINTOOL_URL (hint: use CRTL W to search)
e. Change the line you just found to this: CHAINTOOL_URL ?=
https://hyperledger.jfrog.io/hyperledger/fabric-maven/org/hyperledger/fabricchaintool/$(CHAINTOOL_RELEASE)/fabric-chaintool-$(CHAINTOOL_RELEASE).jar
NOTE: The line above should be on a SINGLE LONG LINE (don’t break up the line into multiple lines)
f.
g.
h.
i.
j.
Save the file (hint: use CRTL O to write the file)
Exit the nano editor (hint: use CTRL X to exit)
$ nano images/javaenv/Dockerfile.in
Find the line that starts with && curl -fsSL https://nexus.hyperledger.org
Change the line you just found to this: && curl -fsSL
https://repo1.maven.org/maven2/org/apache/maven/apachemaven/$MAVEN_VERSION/apache-maven-$MAVEN_VERSION-bin.tar.gz
NOTE: The line above should be on a SINGLE LONG LINE (don’t break up the line into multiple lines)
k. Save the file (hint: use CRTL O to write the file)
l. Exit the nano editor (hint: use CTRL X to exit)
12.
13.
14.
15.
16.
17.
18.
$ make docker
$ make configtxgen cryptogen
$ git clone https://github.com/hyperledger/fabric-ca.git
$ cd fabric-ca
$ make docker
$ date
Create a screenshot of the results of steps 1 – 17 and paste it into your Lab Report File.
2.2.2: Generate network cryptographic material
1. $ cd $GOPATH/src/trade-finance-logistics/network
2. $ nano ~/.profile
change last line to this (all on 1 line, not 2):
export
PATH=$PATH:$GOPATH/bin:$GOPATH/src/github.com/hyperledger/fabric/build/bin:$GOPATH/
src/github.com/hyperledger/fabric/build/docker/bin
3.
4.
5.
6.
7.
Save file and exit nano
$ source ~/.profile
$ cryptogen generate –config=./crypto-config.yaml
$ date
Create a screenshot of the results of steps 1 – 6 and paste it into your Lab Report File.
2.2.3: Generate channel artifacts
1.
2.
3.
4.
5.
6.
7.
8.
9.
$ cd $GOPATH/src/trade-finance-logistics/network
Execute the follow commands OR run the trade.sh script (AFTER step 9)
$ mkdir -p channel-artifacts
$ configtxgen -profile FourOrgsTradeOrdererGenesis -outputBlock ./channelartifacts/genesis.block
$ configtxgen -profile FourOrgsTradeChannel -outputCreateChannelTx ./channelartifacts/channel.tx -channelID tradechannel
$ configtxgen -profile FourOrgsTradeChannel -outputAnchorPeersUpdate ./channelartifacts/ExporterOrgMSPanchors.tx -channelID tradechannel -asOrg ExporterOrgMSP
$ configtxgen -profile FourOrgsTradeChannel -outputAnchorPeersUpdate ./channelartifacts/ImporterOrgMSPanchors.tx -channelID tradechannel -asOrg ImporterOrgMSP
$ configtxgen -profile FourOrgsTradeChannel -outputAnchorPeersUpdate ./channelartifacts/CarrierOrgMSPanchors.tx -channelID tradechannel -asOrg CarrierOrgMSP
$ configtxgen -profile FourOrgsTradeChannel -outputAnchorPeersUpdate ./channelartifacts/RegulatorOrgMSPanchors.tx -channelID tradechannel -asOrg RegulatorOrgMSP
OR (Instead of typing the commands above, the author provides a script to do it all)
1. $ ./trade.sh generate -c tradechannel
Troubleshooting hel…
Purchase answer to see full
attachment