Skip to main content

Setup with Locally Built Dockerized Weaver Components

In this document, we detail the steps using which you can bring up networks using the default configuration settings and by fetching pre-built Weaver interoperation modules, SDK libraries, and relay docker image, drivers docker images from GitHub Package repositories. To customize these settings (e.g., hostnames, ports), refer to the Advanced Configuration page.

Notes
All components are run within Docker containers, except client applications.

Follow the instructions below to build and run components followed by interoperation flows. These instructions have been tested on Ubuntu Linux (bash shell) and Mac OS. In general, they should work on any system and shell as long as the various dependencies have been installed and configured.

Prerequisites​

Software​

Before starting, make sure you have the following software installed on your host machine:

  • Curl: install using package manager, like apt on Debian/Ubuntu Linux

  • Git: sample instructions

  • Docker: sample instructions (Latest version)

  • Docker-Compose: sample instructions (Version 2 or higher)

  • Golang: sample instructions (Version 1.20 or higher)

  • Java (JDK and JRE): sample instructions (Version 8)

  • Node.js and NPM: sample instructions (Version 16 Supported)

  • Yarn: sample instructions

  • Protoc (Protobuf compiler): Golang should already be installed and configured.

    • Default method: Run the following with sudo if necessary. This will install both the protobuf compiler and the Go code generator plugins.

      apt-get install protobuf-compiler
      go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
      go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.4.0

    • If the above method installs an older version of protoc (check using protoc --version), say below 3.12.x, you should download pre-compiled binaries instead. (With an older version, you may see errors while attempting to launch and setup the Fabric networks).

      sudo apt-get remove protobuf-compiler
      curl -LO https://github.com/protocolbuffers/protobuf/releases/download/v3.15.6/protoc-3.15.6-linux-x86_64.zip
      sudo apt-get install unzip
      unzip protoc-3.15.6-linux-x86_64.zip -d <some-folder-path>
      export PATH="$PATH:<some-folder-path>/bin"
      go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
      go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.4.0
      Notes
      The last version we tested with was 3.15.6, but you should check the above link to find the most current version before running the above steps.
      The latest version of protoc-gen-go-grpc that works with the Fabric test networks we will run below is v1.4.0, which is why that version is hardcoded here.

Credentials​

Make sure you have an SSH or GPG key registered in https://github.com to allow seamless cloning of repositories (at present, various setup scripts clone repositories using the https:// prefix but this may change to git@ in the future).

Getting the Code and Documentation​

Clone the weaver-dlt-interoperability repository. The code to get a basic test network up and running and test data-sharing interoperation flows lies in the subfolder tests/network-setups, which should be your starting point, though the setups will rely on other parts of the repository, as you will find out in the instructions given on this page.

Common Structures​

The common/protos folder contains structure definitions in the protobuf format that are used by all the different components. The various common/protos-* folders are meant to contain compiled protobufs (in different languages).

To compile the protobufs for JavaScript, do the following:

  • Navigate to the common/protos-js folder.
  • Run the following command:
    make build

To compile the protobufs for Golang, do the following:

  • Navigate to the common/protos-go folder.
  • Run the following command:
    make build

To compile the protobufs for Java, do the following:

  • Navigate to the common/protos-java-kt folder.
  • Run the following command:
    make build

To compile the protobufs for Solidity, do the following:

  • Navigate to the common/protos-sol folder.
  • Run the following command:
    make build

To compile the protobufs for Rust, do the following:

  • Navigate to the common/protos-rs folder.
  • Run the following command:
    make build

Securing Components​

Notes
The relays and drivers corresponding to the different test networks you will encounter below can be run with or without TLS enabled. But the default files used in the demonstrations assume that either all relays and drivers are TLS-enabled or none are. Therefore, you should determine at the outset whether or not you wish to run the entire set of components in TLS-enabled mode, and select appropriate commands in the provided instructions.

Hyperledger Fabric Components​

Using the sequence of instructions below, you can start two separate Fabric networks, each with a single channel and application contract (chaincode). You can also start an interoperation contract, a relay and a driver acting on behalf of each network. You can build a Fabric CLI tool with which you can initialize both networks' ledgers with access control policies, foreign networks' security groups (i.e., membership providers' certificate chains), and some sample key-value pairs that can be shared during subsequent interoperation flows.

Fabric Interoperation Node SDK​

A client-layer library (companion to hyperledger/fabric-sdk-node) is defined in the sdks/fabric/interoperation-node-sdk folder. This contains functions for Fabric Gateway-based applications to exercise interoperation capabilities via relays and also several utility/helper functions. The Fabric-CLI tool, which we will use later, depends on this library.

To build the library, do the following:

  • Navigate to the sdks/fabric/interoperation-node-sdk folder.
  • Run the following command:
    make build-local

Fabric Network​

The code for this lies in the tests/network-setups folder.

This folder contains code to create and launch networks network1 and network2 of identical specifications:

  • Network: 1 peer, 1 peer CA, 1 ordering service node, 1 ordering service CA
  • Single channel named mychannel
  • One of the following contracts deployed on mychannel, the choice depending on the interoperability mode you wish to test:
    • simplestate (Data Sharing): supports simple transactions (Create, Read, Update, Delete) involving storage and lookup of <key, value> pairs.
    • simplestatewithacl (Data Sharing): identical to simplestate but with extra security features to ensure that the Weaver infrastructure cannot be bypassed by a malicious client of the network.
    • simpleasset (Asset Exchange): supports creation, modification, transfer, and deletion, as well as locking, unlocking, and claiming, of simple bonds and tokens (examples of non-fungible and fungible assets respectively).
    • simpleassetandinterop (Asset Exchange): identical to simpleasset but where the locking, unlocking, and claiming logic is imported as a library in the chaincode rather than available in the common Fabric Interoperation Chaincode (a Weaver component).
    • simpleassettransfer (Asset Exchange or Asset Transfer): augmentation of simpleasset with asset pledging, claiming, and reclaiming features for cross-network transfers.
Notes
For new users, we recommend testing the Data Sharing feature first with the simplestate contract. To test the other modes, you can simply tear down the Fabric networks and restart them with the appropriate chaincodes installed.

Follow the instructions below to build and launch the networks:

  • Navigate to the tests/network-setups/fabric/dev folder.
  • To spin up both network1 and network2 with the interoperation chaincode and the default simplestate chaincode installed, run:
    make start-interop-local
  • To launch the networks with a different application chaincode from the above list, run:
    make start-interop-local CHAINCODE_NAME=<chaincode-name>
  • To launch the networks with 2 organizations, each with a peer (this will enable more variation and experimentation, which you can attempt after testing interoperation protocols across basic network configurations), run:
    make start-interop-local PROFILE="2-nodes"
Notes
If you do not wish to test Fabric-Fabric interoperation, you can choose to launch only one of the two networks along with its interoperation chaincode. For network1, run make start-interop-network1-local, and for network2, run make start-interop-network2-local
If you wish to enable end-to-end confidentiality by default in the interoperation modules that are deployed during network launch, set the environment variable E2E_CONFIDENTIALITY to true in the command line as follows: E2E_CONFIDENTIALITY=true make start-interop-local

For more information, refer to the associated README.

Troubleshooting Tips:

  • If you see any errors during the launches, re-check the prerequisites (software installations and credentials). Ensure your network connection is working. As a safe bet, you can retry after cleanup: kill and remove all Docker containers and associated volumes.
  • If protoc or protoc-gen-go throws an error, reinstall protoc, protoc-gen-go, and protoc-gen-go-grpc using suggestions made in the Prerequisites section above.

Fabric Relay​

The relay is a module acting on behalf of a network, enabling interoperation flows with other networks by communicating with their relays. The code for this lies in the core/relay folder. Navigate to the core/relay folder.

Building Relay Image​

To build the docker image for relay, run:

make build-server-local

Deployment​

  • The docker-compose.yaml in this folder is minimally configured with default values. To modify it for use with the Fabric testnets, run:
    make convert-compose-method2
  • The .env.n1 and .env.n1.tls files in the docker/testnet-envs directory contain environment variables used by the network1 relay at startup and runtime. Edit either of these files (depending on whether you wish to start the relay with or without TLS), and update the following value:
    DOCKER_IMAGE_NAME=weaver-relay-server
  • Repeat the above step for .env.n2 or .env.n2.tls in docker/testnet-envs directory, which contain environment variables for the network2 relay.
  • To deploy the relay server for network1 without TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.n1'
    Instead, to deploy the relay server with TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.n1.tls'
  • To deploy the relay server for network2 without TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.n2'
    Instead, to deploy the relay server with TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.n2.tls'
  • After launching the relay(s), you can revert the docker-compose.yaml changes by running:
    make convert-compose-method1

For more information, see the relay-docker README.

Fabric Driver​

A driver is a DLT-specific plugin invoked by the relay while channelling external data queries to the local peer network and collecting a response with proofs. The Fabric driver is built as a Fabric client application on the fabric-network NPM package. The code for this lies in the core/drivers/fabric-driver folder. Navigate to the core/drivers/fabric-driver folder.

Building​

To build the fabric-driver image, run:

make build-image-local

Deployment​

Use the following steps to run Fabric drivers in Docker containers:

  • The .env.n1 and .env.n1.tls files in the docker-testnet-envs directory contain environment variables used by the network1 driver at startup and runtime. Edit either of these files (depending on whether you wish to start the relay with or without TLS) as follows:
    • Replace <PATH-TO-WEAVER> with the absolute path of the weaver-dlt-interoperability clone folder.
    • Update the following value:
      DOCKER_IMAGE_NAME=weaver-fabric-driver
  • Repeat the above steps for .env.n2 or .env.n2.tls in docker-testnet-envs directory, which contain environment variables for the network2 driver.
  • To deploy the Fabric driver for network1 without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.n1' NETWORK_NAME=$(grep NETWORK_NAME docker-testnet-envs/.env.n1 | cut -d '=' -f 2)
    Instead, to deploy the driver with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.n1.tls' NETWORK_NAME=$(grep NETWORK_NAME docker-testnet-envs/.env.n1.tls | cut -d '=' -f 2)
  • To deploy the Fabric driver for network2 without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.n2' NETWORK_NAME=$(grep NETWORK_NAME docker-testnet-envs/.env.n2 | cut -d '=' -f 2)
    Instead, to deploy the driver with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.n2.tls' NETWORK_NAME=$(grep NETWORK_NAME docker-testnet-envs/.env.n2.tls | cut -d '=' -f 2)

Fabric IIN Agent​

IIN Agent is a client of a member of a DLT network or security domain with special permissions to update security domain identities and configurations on the ledger via the network's interoperation module. The code for this lies in the core/identity-management/iin-agent folder. Navigate to the core/identity-management/iin-agent folder.

Building​

To build the IIN Agent image, run:

make build-image-local

Deployment​

Use the following steps to run Fabric IIN Agents in Docker containers:

  • The .env.n1.org1 and .env.n1.org1.tls files in the docker-testnet/envs directory contain environment variables used by the iin-agent of org1 of network1 at startup and runtime. Edit either of these files (depending on whether you wish to start the relay with or without TLS) as follows:
    • Replace <PATH-TO-WEAVER> with the absolute path of the weaver-dlt-interoperability clone folder.
    • Update the following value:
      DOCKER_IMAGE_NAME=weaver-iin-agent
    • If Fabric network was started with 1 org, and IIN Agents are to be started with TLS enabled, update the DNS_CONFIG_PATH variable as:
      DNS_CONFIG_PATH=./docker-testnet/configs/dnsconfig-tls.json
    • If Fabric network was started with 2 orgs, and IIN Agents are to be started without TLS, update the DNS_CONFIG_PATH variable as
      DNS_CONFIG_PATH=./docker-testnet/configs/dnsconfig-2-nodes.json
    • If Fabric network was started with 2 orgs and IIN Agents are to be started with TLS enabled, update the DNS_CONFIG_PATH variable as:
      DNS_CONFIG_PATH=./docker-testnet/configs/dnsconfig-tls-2-nodes.json
  • Repeat the above steps for all other environment variable files (depending upon whether tls is enabled) in docker-testnet/envs directory.
  • To deploy the Fabric IIN Agent for org1 of network1 without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n1.org1' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n1.org1 | cut -d '=' -f 2)
    Instead, to deploy the IIN Agent with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n1.org1.tls' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n1.org1.tls | cut -d '=' -f 2)
  • To deploy the Fabric IIN Agent for org2 of network1 without TLS (only required if Fabric network was started with 2 orgs), run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n1.org2' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n1.org2 | cut -d '=' -f 2)
    Instead, to deploy the IIN Agent with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n1.org2.tls' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n1.org2.tls | cut -d '=' -f 2)
  • To deploy the Fabric IIN Agent for org1 of network2 without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n2.org1' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n2.org1 | cut -d '=' -f 2)
    Instead, to deploy the IIN Agent with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n2.org1.tls' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n2.org1.tls | cut -d '=' -f 2)
  • To deploy the Fabric IIN Agent for org2 of network2 without TLS (only required if Fabric network was started with 2 orgs), run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n2.org2' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n2.org2 | cut -d '=' -f 2)
    Instead, to deploy the IIN Agent with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet/envs/.env.n2.org2.tls' DLT_SPECIFIC_DIR=$(grep DLT_SPECIFIC_DIR docker-testnet/envs/.env.n2.org2.tls | cut -d '=' -f 2)

Fabric Client (Application)​

The CLI is used to interact with a Fabric network, configure it and run chaincode transactions to record data on the channel ledger or query data. It is also used to interact with remote networks through the relay in order to trigger an interoperation flow for data request and acceptance.

The fabric-cli Node.js source code is located in the samples/fabric/fabric-cli folder and the Golang source code in the samples/fabric/go-cli folder.

Prerequisites​

If you are using a Linux system, make sure that lib64 is installed.

Notes
For the Node.js version of the fabric-cli, the setup and running instructions below were tested with all Node.js versions from v11.14.0 to v14.17.3.

Installation​

You can install fabric-cli as follows (for both the Node.js and Golang versions):

  • Navigate to the samples/fabric/fabric-cli folder (for the Node.js version) or the samples/fabric/go-cli folder (for the Golang version).
  • Run the following to install dependencies (for the Node.js version) or the executable (for the Golang version):
    make build-local
  • Use the fabric-cli executable in the bin folder for subsequent actions.

Corda Components​

Using the sequence of instructions below, you can start a Corda network and run an application CorDapp on it. You can also run an interoperation CorDapp, a relay and a driver acting on behalf of the network. You can initialize the network's vault with access control policies, foreign networks' security groups (i.e., membership providers' certificate chains), and some sample state values that can be shared during subsequent interoperation flows.

Interoperation CorDapp​

The interoperation CorDapp is deployed to run as part of any Corda application flow that involves cross-network interoperation.

Build the interoperation CorDapp as follows:

  • Navigate to the core/network/corda-interop-app folder.
  • Run the following to create the JAR files on which other Corda network components will depend on:
    make build-local

Corda Interoperation SDK​

A client-layer library is defined in the sdks/corda folder. This contains functions for Corda based client applications to exercise interoperation capabilities via relays and also several utility/helper functions. The Corda Client tool, which we will use later, depends on this library.

To build the library, do the following:

  • Navigate to the sdks/corda folder.
  • Run the following command (make sure there is no github.properties file present in the directory):
    make build

Corda Simple Application and Client (Application)​

This is a simple CorDapp that maintains a state of type SimpleState, which is a set of key-value pairs (of strings). The code for this lies in the samples/corda/corda-simple-application folder.

Build the corda-simple-application CorDapp as follows:

  • Navigate to the samples/corda/corda-simple-application folder.
  • Run the following:
    make build-local

Corda Network​

The Corda networks' code lies in the tests/network-setups/corda folder. You can launch two separate Corda networks, namely Corda_Network and Corda_Network2. Each network runs the samples/corda/corda-simple-application CorDapp by default, which maintains a state named SimpleState containing a set of key-value pairs (of strings).

Follow the instructions below to build and launch both networks:

  • Navigate to the tests/network-setups/corda folder.
  • To spin up the Corda networks with the Interoperation CorDapps:
    • Each consisting of 1 node and a notary (for data-transfer), run:
      make start-local
    • Each consisting of 2 nodes and a notary (for asset-exchange/transfer), run:
      make start-local PROFILE="2-nodes"
    • Each consisting of 3 nodes and a notary (for asset-exchange/transfer), run:
      make start-local PROFILE="3-nodes"
Notes
If you do not wish to test Corda-Corda interoperation, you can choose to launch only one of the two networks along with its interoperation CorDapp. For Corda_Network, run make start-network1-local, and for Corda_Network2, run make start-network2-local.

You should see the following message in the terminal:

Waiting for network node services to start

The Corda nodes and notary may take a while (several minutes on memory-constrained systems) to start. If they start up successfully, you should something like the following for each network, though the number of node entries will depend on the profile you used to start the network with (replace <network-name> with Corda_Network or Corda_Network2):

PartyA node services started for network <network-name>
PartyB node services started for network <network-name>
PartyC node services started for network <network-name>
Notary node services started for network <network-name>

Corda Relay​

Navigate to the core/relay folder. Refer here to build the relay image if not already built. Now run a relay for Corda_Network and/or Corda_Network2 in Docker container as follows:

  • The docker-compose.yaml in this folder is minimally configured with default values. To modify it for use with the Fabric testnets, run:
    make convert-compose-method2
  • The .env.corda and .env.corda.tls files in the docker/testnet-envs directory contain environment variables used by the Corda_Network relay at startup and runtime. Edit either of these files (depending on whether you wish to start the relay with or without TLS), and update the following value:
    DOCKER_IMAGE_NAME=weaver-relay-server
  • Repeat the above step for .env.corda2 or .env.corda2.tls in docker/testnet-envs directory, which contain environment variables for the Corda_Network2 relay.
  • To deploy the relay server for Corda_Network without TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.corda'
    Instead, to deploy the relay server with TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.corda.tls'
  • To deploy the relay server for Corda_Network2 without TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.corda2'
    Instead, to deploy the relay server with TLS, run:
    make start-server COMPOSE_ARG='--env-file docker/testnet-envs/.env.corda2.tls'
  • After launching the relay(s), you can revert the docker-compose.yaml changes by running:
    make convert-compose-method1

Corda Driver​

Navigate to the core/drivers/corda-driver folder.

Building​

To build the corda driver docker image, run:

make image-local

Deployment​

Use the following steps to run Corda drivers in Docker containers:

  • The .env.corda and .env.corda.tls files in the docker-testnet-envs directory contain environment variables used by the Corda_Network driver at startup and runtime. Edit either of these files (depending on whether you wish to start the relay with or without TLS) to update the following value:
    DOCKER_IMAGE_NAME=weaver-corda-driver
  • Repeat the above steps for .env.corda2 or .env.corda2.tls in docker-testnet-envs directory, which contain environment variables for the Corda_Network2 driver.
  • To deploy the Corda driver for Corda_Network without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda'
    Instead, to deploy the driver with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda.tls'
    If the driver starts successfully, it should log the following message when you run docker logs corda-driver-Corda_Network:
    Corda driver gRPC server started. Listening on port 9099
  • To deploy the Corda driver for Corda_Network2 without TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda2'
    Instead, to deploy the driver with TLS, run:
    make deploy COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda2.tls'
    If the driver starts successfully, it should log the following message when you run docker logs corda-driver-Corda_Network2:
    Corda driver gRPC server started. Listening on port 9098

Tear Down the Setup​

Bring down the various components as follows (Navigate to the root folder of your clone of the Weaver repository):

Relay​

To bring down the relays (for all 3 networks), run:

cd core/relay
make convert-compose-method2
make stop COMPOSE_ARG='--env-file .env.n1'
make stop COMPOSE_ARG='--env-file .env.n2'
make stop COMPOSE_ARG='--env-file .env.corda'
make stop COMPOSE_ARG='--env-file .env.corda2'
make convert-compose-method1
cd -

Fabric Driver​

To bring down the fabric drivers (for both networks), run:

cd core/drivers/fabric-driver
make stop COMPOSE_ARG='--env-file .env.n1'
make stop COMPOSE_ARG='--env-file .env.n2'
cd -

Corda Driver​

To bring down the corda driver, run:

cd core/drivers/corda-driver
make stop COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda'
make stop COMPOSE_ARG='--env-file docker-testnet-envs/.env.corda2'
cd -

Corda Network​

To bring down the Corda network:

cd tests/network-setups/corda
make clean
cd -

Fabric Network​

To bring down both of the Fabric networks along with weaver components:

cd tests/network-setups/fabric/dev
make clean
cd -