Reporting Server > Using the Adapter for Hyperledger Fabric > Configuring the Adapter for Hyperledger Fabric

Configuring the Adapter for Hyperledger Fabric

How to:

Reference:

Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish.

Procedure: How to Configure an Adapter

  1. From the Web Console sidebar, click Connect to Data.

    or

    From the Data Management Console, expand the Adapters folder.

    In the DMC, the Adapters folder opens. In the Web Console, the Adapters page opens showing your configured adapters.

  2. In the Web Console, click the New Datasource button on the menu bar and find the adapter on the page or, in the DMC, expand the Available folder if it is not already expanded.
    On the Web Console, you can select a category of adapter from the drop-down list or use the search option (magnifying glass) to search for specific characters.
  3. In the DMC, expand the appropriate group folder and the specific adapter folder. The group folder is described in the connection attributes reference.
  4. Right-click the adapter name and/or version and select Configure.

    The Add Adapter to Configuration pane opens.

  5. Enter values for the parameters required by the adapter, as described in the chapter for the specific adapter you want to configure.
  6. Click Configure. The configured adapter is added to the Adapters list in the DMC resources tree or the Configured list in the Web Console.
    In the Web Console, the adapter remains on the Available Adapters list with an asterisk to indicate that at least one connection has been configured. You can configure additional connections from either the Configured or Available list by right-clicking the adapter and clicking Add Connection.

Reference: Connection Attributes for the Adapter for Hyperledger Fabric

The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.

Connection Name

Is the logical name used to identify this set of connection attributes. The default is CON01.

PEERDEF

Is the endorser endpoint (the URL of the endorsing peer, in gRPC format).

The function of an endorsing peer is to endorse a transaction before it is committed for a particular chaincode. Every chaincode can specify an endorsement policy that may refer to a set of endorsing peers. The policy defines the necessary and sufficient conditions for a valid transaction endorsement. For example: 

PeerAdmin@grpc://lnxx64hl2.ibi.com:7051
ORDERERDEF

Is the orderer endpoint (the URL of the ordering service node, in gRPC format).

The event hub is responsible for asynchronous processing of blockchain events. For example:

peer0@grpc://lnxx64hl2.ibi.com:7053
EVENTHUBDEF

Is the event hub peer endpoint (URL of peers that form the event hub, in gRPC format).

The orderers form the ordering service, a communication fabric that provides delivery guarantees. For example:

orderer@grpc://lnxx64hl2.ibi.com:7050
CHANNEL_ID

Is the channel name.

A channel is a private blockchain overlay that allows for data isolation and confidentiality. A channel-specific ledger is shared across the peers in the channel, and transacting parties must be properly authenticated to a channel in order to interact with it. For example: 

mychannel
CHAINCODE_ID

Is the chaincode identifier.

A chaincode is software, running on a ledger, to encode assets and the transaction instructions (business logic) for modifying the assets. For example: 

fabcar
PEER_ID

Is the member (user) name.

A member is a legally separate entity that owns a unique root certificate for the network. Network components such as peer nodes and application clients will be linked to a member. For example: 

PeerAdmin
ORG_ID

Is the Membership Service Provider (MSP) Identifier.

The Membership Service Provider (MSP) refers to an abstract component of the system that provides credentials to clients and peers for them to participate in a Hyperledger Fabric network. Clients use these credentials to authenticate their transactions, and peers use these credentials to authenticate transaction processing results (endorsements). For example: 

Org1MSP
CERT_LOC

Is the path to the enrollment certificate (ECert).

The ECert must have been signed by one of the Certificate Authorities (CAs) the blockchain network has been configured to trust. An enrolled user (having a signing key and ECert) can conduct chaincode instantiations, transactions, and queries with the channel. For example: 

/qas/fabric_sdk100_sample/cert_car.pem
PKEY_LOC

Is the path to the private key.

/qas/fabric_sdk100_sample/key_car.pem
IBI_CLASSPATH

Are additional Java Class directories or full path names that will be available for Java Services. For example:

C:\directory\filename1.jar
C:\directory\filename2.jar

 WebFOCUS

Feedback