mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-18 16:05:10 +00:00
bb3ac84e6e
Update balance transfer sample to use the connection profile and node 8. Change-Id: I17c74c6cb23ebe55a8f2bba735d41525ae9e5ab1 Signed-off-by: Bret Harrison <beharrison@nc.rr.com> Signed-off-by: ratnakar <asara.ratnakar@gmail.com>
53 lines
2.2 KiB
YAML
53 lines
2.2 KiB
YAML
---
|
|
#
|
|
# The network connection profile provides client applications the information about the target
|
|
# blockchain network that are necessary for the applications to interact with it. These are all
|
|
# knowledge that must be acquired from out-of-band sources. This file provides such a source.
|
|
#
|
|
name: "balance-transfer-org1"
|
|
|
|
#
|
|
# Any properties with an "x-" prefix will be treated as application-specific, exactly like how naming
|
|
# in HTTP headers or swagger properties work. The SDK will simply ignore these fields and leave
|
|
# them for the applications to process. This is a mechanism for different components of an application
|
|
# to exchange information that are not part of the standard schema described below. In particular,
|
|
# the "x-type" property with the "hlfv1" value example below is used by Hyperledger Composer to
|
|
# determine the type of Fabric networks (v0.6 vs. v1.0) it needs to work with.
|
|
#
|
|
x-type: "hlfv1"
|
|
|
|
#
|
|
# Describe what the target network is/does.
|
|
#
|
|
description: "Balance Transfer Network - client definition for Org1"
|
|
|
|
#
|
|
# Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
|
|
#
|
|
version: "1.0"
|
|
|
|
#
|
|
# The client section is SDK-specific. The sample below is for the node.js SDK
|
|
#
|
|
client:
|
|
# Which organization does this application instance belong to? The value must be the name of an org
|
|
# defined under "organizations"
|
|
organization: Org1
|
|
|
|
# Some SDKs support pluggable KV stores, the properties under "credentialStore"
|
|
# are implementation specific
|
|
credentialStore:
|
|
# [Optional]. Specific to FileKeyValueStore.js or similar implementations in other SDKs. Can be others
|
|
# if using an alternative impl. For instance, CouchDBKeyValueStore.js would require an object
|
|
# here for properties like url, db name, etc.
|
|
path: "./fabric-client-kv-org1"
|
|
|
|
# [Optional]. Specific to the CryptoSuite implementation. Software-based implementations like
|
|
# CryptoSuite_ECDSA_AES.js in node SDK requires a key store. PKCS#11 based implementations does
|
|
# not.
|
|
cryptoStore:
|
|
# Specific to the underlying KeyValueStore that backs the crypto key store.
|
|
path: "/tmp/fabric-client-kv-org1"
|
|
|
|
# [Optional]. Specific to Composer environment
|
|
wallet: wallet-name
|