Deploy chaincode

First, develop, test, and package your chaincode in a Hyperledger Fabric development environment:

• For more information about chaincode development, see Chaincode for Developers.

• After the chaincode passes testing, package it using the peer chaincode package command. When packaging, include the required dependencies. For a Go chaincode, use the following steps to place the dependency files in the vendor directory:

  1. Install the govendor tool.

     go get -u -v github.com/kardianos/govendor

  2. Go to the chaincode project directory and initialize the vendor directory.

     govendor init

  3. Automatically move the dependency packages used by the project from GOPATH to the vendor directory.

     govendor add +external

• For more information about the packaging command, see peer chaincode command. Note the following:

  1. When you package a Go chaincode, the -p parameter must specify the relative path of the directory that contains the main package of the chaincode under $GOPATH/src. When you package a Java chaincode, the -p parameter must specify the Java project directory. When you package a Node.js chaincode, the -p parameter must specify the root directory of the Node.js project that contains the package.json file. Do not use a relative path format such as "./xxx" for the -p parameter.

  2. If the chaincode language is Go, you can omit the -l option. If the chaincode language is Node.js or Java, you must specify the -l node or -l java parameter.

  3. If the chaincode initialization method does not require input parameters, you can omit the -c option.

  4. Do not add the -i or -S options.

• The following example packages the Go chaincode source code from the $GOPATH/src/github.com/hyperledger/fabric/examples/chaincode/go/example02 directory into a file named ccpack.out. The chaincode is named mycc and its version is 1.0.

  peer chaincode package ccpack.out -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/example02/cmd -c '{"Args":["init","a","100","b","200"]}' -v 1.0

  Download peer:

• Mac: hyperledger-fabric-darwin-amd64-1.4.5.tar.gz

• Linux: hyperledger-fabric-linux-amd64-1.4.5.tar.gz

Deploying a new chaincode involves the following three steps. For information about how to upgrade an existing chaincode in a channel, see Upgrade chaincode:

1. Upload the chaincode

2. Install the chaincode

3. Instantiate the chaincode

Upload the chaincode

1. Log on to the Alibaba Cloud BaaS console.

2. On the Overview page, in the My Organizations area, find the target organization and click its name.

3. Click the Chaincodes tab.

4. Click Upload Chaincode.

5. In the dialog box that appears, upload the chaincode that you packaged in the development environment. For more information about how to package the chaincode, see the preceding section.

6. Select the channel to which you want to deploy the chaincode. If you are deploying a new chaincode, ensure that its name does not conflict with any existing chaincode in the channel.

7. Enter an endorsement policy.

   For example: OR ('Org1MSP.peer','Org2MSP.peer') indicates that an endorsement from either of the two organizations in the channel is required. AND ('Org1MSP.peer','Org2MSP.peer') indicates that endorsements from both organizations in the channel are required.

8. Click OK.

   After the chaincode is uploaded, it appears in the list on the Chaincodes tab. The chaincode name in the Chaincode column and the version number in the Version column are the ones you specified when you packaged the chaincode locally.

Install the chaincode

Prerequisites

You have uploaded the chaincode.

Procedure

1. Log on to the Alibaba Cloud BaaS console.

2. On the Overview page, in the My Organizations area, find the target organization and click its name.

3. Click the Chaincodes tab.

4. Find the chaincode that you want to install and in the Actions column, click Install to install the chaincode in the current organization.

   

   After the installation is complete, the Installation Status changes from Not Installed to Installed, and Install in the Actions column changes to Instantiate.

5. If the endorsement policy that you set when uploading the chaincode requires endorsements from multiple organizations, you must also install the chaincode in those organizations.

Instantiate the chaincode

Prerequisites

You have uploaded and installed the chaincode.

Procedure

1. Log on to the Alibaba Cloud BaaS console.

2. On the Overview page, in the My Organizations area, find the target organization and click its name.

3. Click the Chaincodes tab.

4. Find the chaincode that you want to instantiate and in the Actions column, click Instantiate.

5. In the dialog box that appears, the system automatically displays the endorsement policy that you entered when you uploaded the chaincode. You can either keep this policy or specify a new one.

   For example: OR ('Org1MSP.peer','Org2MSP.peer') indicates that an endorsement from either of the two organizations in the channel is required. AND ('Org1MSP.peer','Org2MSP.peer') indicates that endorsements from both organizations in the channel are required.

6. In the dialog box, click Advanced. In the Private Data Collection Configurations input box, enter the JSON definition for your chaincode's private data collection. If your chaincode does not use the private data feature, you can skip this step.

   The following is an example of a JSON definition for a private data collection: [{"name": "collectionName", "policy": "OR('Org1MSP.peer')", "memberOnlyRead": false, "requiredPeerCount": 0, "maxPeerCount": 3, "blockToLive": 0}]. This definition indicates that the chaincode uses a private data namespace named collectionName, and only nodes of organization Org1 can access the private data in this namespace.

   Note that once the name and blockToLive of a private data collection are set, you cannot modify these values during an upgrade. For more information, see Using Private Data in Fabric.

7. Click Instantiate.

   

   This operation takes several seconds to several minutes, depending on the complexity of the chaincode dependencies. After the operation is successful, the Channel Status changes from Not Instantiated to Running, and the value in the Actions column becomes empty.

Next steps

You can now create a user and access the blockchain network through an SDK.