Configure main channel

Each member should run the following command in its Cloud9 terminal to update the configtx.yaml channel configuration file.

Now that the chaincode has been thoroughly tested with local unit tests, it’s time to install it on member peer nodes and test it in its native Fabric environment. After installing it on each member’s peer node, one member will instantiate the chaincode, at which point it will be possible for any member to invoke the chaincode to update different products as they progress through the supply chain.

First we need to update the existing channel configuration to create a shared channel that all members belong to.

cd
cat <<EOT > configtx.yaml
Organizations:
  - &Retailer
    Name: $RETAILERID
    ID: $RETAILERID
    MSPDir: /opt/home/retailer-admin-msp
    AnchorPeers:
      - Host:
        Port:
  - &Supplier
      Name: $SUPPLIERID
      ID: $SUPPLIERID
      MSPDir: /opt/home/supplier-admin-msp
      AnchorPeers:
        - Host:
          Port:
Capabilities:
  Channel: &ChannelCapabilities
    V1_4_3: true
    V1_3: false
    V1_1: false
  Application: &ApplicationCapabilities
    V1_4_2: true
    V1_3: false
    V1_2: false
    V1_1: false
Application: &ApplicationDefaults
  Organizations:
  Capabilities:
    <<: *ApplicationCapabilities
Profiles:
  MainChannel:
    Consortium: AWSSystemConsortium
    Application:
      <<: *ApplicationDefaults
      Organizations:
        - *Retailer
        - *Supplier
EOT