Blockchain SDK integration with network API call method supports Fabric network.
If the application system has a relatively high call frequency, it is required to directly use Blockchain SDK to connect with the blockchain network, which has higher performance compared with TencentCloud API call method.
In addition to supporting the community edition of Blockchain SDK (Java, NodeJS, Golang), TBaaS has customized the community edition Blockchain SDK for Golang and Java versions (tbaas-fabric-sdk-go and tbaas-fabric-sdk-java), simplifying the process of connecting application systems to the blockchain network.
1. Get the Network Name and Access Address
1. Log in to TBaaS Console, select Fabric > Blockchain Network in the left sidebar.
2. On the Blockchain Network page, select the network you want to view and click Manage to enter the network overview page.
3. In the Network Basic Information module, find the network name and access address, and fill in the relevant fields of network name and url in the configuration file. As shown below:
2. Obtain MSP and Organization Name
1. In the Organization and Node tab, select Network Organization.
2. Find the current organization information and fill in the relevant fields of MSP in the configuration file; extract the part on the left of ., such as org-251005746, and fill in the relevant fields of organization name in the configuration file. As shown below:
3. Obtain Node Name
1. In the Organization and Node tab, select Node Management.
2. Find the node list of the current organization, select a node and copy the node name, then fill it in the field about node name in the configuration file. As shown below:
4. Deploy Contract
1. In the Contract Management tab, click Create Contract.
2. In Create Contract, fill in the following basic information:
contract name: fill in mycc
contract version: fill in v1.0
Select contract language: Select Go
upload the contract compressed package
3. Click installation, and choose a peer node.
4. Click contract instantiation, and wait for the contract status to update to "instantiated".
5. Certificate Application Process
1. Go to the OpenSSL official website, download OpenSSL, and configure the installation.
2. Download the ecccsr tool. After decompressing it, execute sh ecccsr.sh. This command will generate the following four files:
user_ecc_sign.key: It corresponds to the private key of the user certificate, needs to be securely stored, and can be used in SDK.
user_ecc_sign.csr: Used to apply for a user certificate on the TBaaS Console.
user_ecc_tls.key: It is the private key corresponding to the user's TLS certificate, requires secure storage, and can be used in SDK.
user_ecc_tls.csr: Used to apply for a user TLS certificate on the TBaaS Console.
3. In the Certificate Management interface, add a certificate application, complete the certificate identifier, and upload user_ecc_sign.csr and user_ecc_tls.csr. As shown below:
4. After a successful application, you can click to download the corresponding certificate. The compressed package contains the following files:
ca.crt: organization root certificate
user_sign.crt: user certificate
user_tls.crt: User TLS certificate
5. Place three certificates (ca.crt, user_sign.crt, user_tls.crt) and two private keys (user_ecc_sign.key, user_ecc_tls.key) in the corresponding SDK certificate directory and replace them. Modify the corresponding path in the SDK configuration file config.yml.
6. Using the SDK
6.1 tbaas-fabric-sdk-go
1. Download and enter tbaas-fabric-sdk-go, then enter the tbaas-fabric-sdk-go/fabric-sdk-demo directory.
2. Modify configFile, mspId, username, channelName, and contractName in the main.go example code accordingly. The example is as follows:
const(
configFile ="config/config.yaml"
// Organization MSPID
mspId ="org-251005746.fabric-5x6wdaow3q"
// userName
username ="test"
// Channel name
channelName ="channel-9xjcb2"
// contract name
contractName ="gotest"
)
3. Update the related content in the yml configuration file.
version: 1.0.0
client:
# The organization used by default by the client
organization: org-251005746
logging:
# sdk log level
level: info
tlsCerts:
client:
# user TLS private key path
key:
path: config/test/user_ecc_tls.key
# User TLS certificate path
cert:
path: config/test/user_tls.crt
# Channel information
channels:
# Channel name
channel-9xjcb2:
# peer node list
peers:
# peer node name
peer1-org-251005746.fabric-5x6wdaow3q:
# orderer node list
orderers:
- orderer1-org-251005746.fabric-5x6wdaow3q
# Organization information
organizations:
# organization name
org-251005746:
# Organization mspId, format is ${orgName}.${clusterId}, where orgName is the organization name and clusterId is the network ID
# Configuration for multi-organization endorsement as follows. The first three items should be configured as PeerName of other endorsement organizations. urlSubstitutionExp is consistent with that of the orderer.
