4 -1 - Information Builders
TIBCO iWay Service ManagerService Manager and Blockchain SolutionsDevelopment GuideVersion 8.0 and HigherMarch 2021DN3502252.0321Copyright 2021. TIBCO Software Inc. All Rights Reserved.
Contents1. Introducing Blockchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5What is a Blockchain? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Supported Blockchains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Blockchain Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6How can iWay Service Manager Integrate With My Blockchain Application? . . . . . . . . . . . . . . . . . . . .7Hyperledger Fabric Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Channel Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Transaction Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Synchronous Posting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Asynchronous Posting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Query Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Query Block Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Fabric Listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132. Hyperledger Fabric Component Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Hyperledger Fabric Channel Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Hyperledger Fabric Transaction Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Hyperledger Fabric Query Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Hyperledger Fabric Query Block Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Hyperledger Fabric Key History Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Hyperledger Fabric Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423. Using the Fabric Wizard to Create a Fabric Agent Skin . . . . . . . . . . . . . . . . . . . . . . . . . . 45Fabric Wizard Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Original Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46The Template (“Fabric Skinner”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Accesing the Fabric Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Understanding the Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Agent Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Output Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Agent Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Agent Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Agent Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Service Manager and Blockchain Solutions Development Guide3
ContentsAgent Comment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Fabric Channel Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Operation Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Number of Parms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Defining Additional Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Parm (Parameter) Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Group Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Default Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584. Blockchain Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Understanding the Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Synchronous Posting Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Asynchronous Posting Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Sample SWIFT MT101 Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Original SWIFT MT101 Message (Request for Transfer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Transformed SWIFT MT101 Message (XML Format). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67A. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .734
Chapter1Introducing BlockchainThis chapter provides an introduction to blockchain and an overview of integrating iWayService Manager (iSM) with blockchain applications.In this chapter:What is a Blockchain?Blockchain PrerequisitesHow can iWay Service Manager Integrate With My Blockchain Application?Hyperledger Fabric ComponentsWhat is a Blockchain?A blockchain is a distributed record of transactions validated and stored at multiple peerlocations in a network. The records form a consensus of replicated, shared, and synchronizedinformation. For example, the debits and credits applied to a bank's accounts might be storedin the blockchain. The ledger (blockchain) is not the record of the accounts themselves, butrather the changes in account position.The records stored in the blockchain are immutable, providing a high level of security andintegrity. Each record is chained to the prior record, hashed, and encrypted. The records form achain of transactions from the initial transaction to the most current. The records areduplicated among the peers in the network, and available to any authorized party for viewing.The result is a horizontal (peer storage) and vertical (historic chain) mesh that is virtuallytamper proof. This results in a high level of trust, transparency, and reliability.Once an item is recorded, it is irrefutable proof that this event occurred at a specific time anddate, and (perhaps) between specific counterparties. The use of blockchains solves theproblem of transferring value between parties (or entities) without the need to rely on a thirdintermediating party.In the enterprise business world, a private blockchain provides a basis for non-repudiation andautomates many of the existing labor-intensive processes required to settle transactions.Blockchains can reduce transaction and back office costs, the complexity of cross-enterprisebusiness processes, fraud, and inefficiencies in the business to free up capital.Service Manager and Blockchain Solutions Development Guide5
Blockchain PrerequisitesBlockchains can also take advantage of smart contracts. Smart contracts are self-executingcontracts or agreements that are represented as software that can automatically triggeractions under certain conditions, such as when payments are made (or missed).Smart contracts are implemented in chaincode, which implements the application in the peers.The peers run this code, and at a future point, validates the transaction to determine, forexample, whether an asset should or should not be transferred.In iWay Version 8, support for private blockchain maximizes the advantages of this modernapproach to transaction interchange and non-repudiable storage.Supported BlockchainsiWay Service Manager (iSM) supports Hyperledger Fabric Permissioned or Private Blockchain(e.g. business applications). This type of blockchain requires users to be authorized to gainaccess (be invited) into the blockchain and limits the number of people who are grantedaccess to maintain privacy of transactions. These are the only blockchain types currentlysupported by iSM.Note: There are also Permissionless or Public Blockchain (e.g. Bitcoin). This type ofblockchain can be accessed by anyone and anyone can read/write to the blockchain. Currently,iSM does not address permissionless blockchain applications.Blockchain PrerequisitesBefore you continue, ensure that you have the following components installed on theplatform(s) on which you will be integrating iWay Service Manager (iSM) with your blockchain:iSM Version 8.0 or higher.Hyperledger Fabric Version 1.0.1 or higher.You can download Hyperledger Fabric from the following /releaseA chaincode that is appropriate to your application.6
1. Introducing BlockchainHow can iWay Service Manager Integrate With My Blockchain Application?The blockchain workflow provides participants end-to-end visibility based on their level ofpermission. Detailed visibility of the workflow process is enhanced with real time exchange ofevents and documents.Service Manager and Blockchain Solutions Development Guide7
How can iWay Service Manager Integrate With My Blockchain Application?This level of detail and transparency helps reduce fraud and errors, reduces the time requiredto complete the workflow, and improves the management of the workflow.Note, the read on the specific peer in this diagram is only intended for illustration purposes.There is no inherent quality of the “local peer”.Confederation of Applications8
1. Introducing BlockchainThe blockchain in an actual usage scenario, provides a desired transaction record consistentlyacross multiple parties that are interested in that information. Each member can be assuredthat all parties view the same information, although they may use this information for their ownrequirements. You can imagine this as the above diagram, but with access to the peers fallinginto a sector of application interest. The application-level data appropriate to that specificsector of interest may vary based on the specific purpose of the application, although allaccept their input from the consistent blockchain data. The blockchain itself is the ledger ofactivity.iSM works with and alongside your Hyperledger Fabric-based applications. Incorporating iSMinto the blockchain workflow reduces process development cost and time as well as providingfor faster implementation. iSM graphically builds your process flow and provides full integrationand configuration via adaptors. The in-process flow query offers transaction intelligence andthe ability to print logical reports.iSM listeners provide input message protocols through dedicated event listeners.Services help handle payloads and the Fabric facility offers services to support several meansof posting transactions. iWay Service Manager (iSM) utilizes the following types of services topost to the blockchain:Transaction Service. Executes a transaction on a blockchain in the Hyperledger Fabric. Thisservice supports synchronous and asynchronous posting. For more information, seeTransaction Service on page 10.Query Service. Executes a read-only query in the Hyperledger Fabric. For more information,see Query Service on page 13.Query Block Service. Queries the Hyperledger Fabric for a specific block and returns thisblock. For more information, see Query Block Service on page 13.Hyperledger Fabric ComponentsThe Hyperledger Fabric facility in iWay Service Manager (iSM) includes access to the Fabricsystem, posting services, and query services. For more detailed information on thesecomponents, see Hyperledger Fabric Component Reference on page 15.Channel ProviderConnection to the Hyperledger Fabric system is handled through a Channel provider. Thisprovider is responsible for securing the connection and connection recovery. Separate Channelproviders, each with a unique name or properties, can be defined as required. The posting andquery services must be configured to refer to an available Channel provider.Service Manager and Blockchain Solutions Development Guide9
Hyperledger Fabric ComponentsFor more information and an example, see Hyperledger Fabric Channel Provider on page 15.Transaction ServiceThe Transaction service invokes chaincode (embedded logic that encodes rules for specifictypes of network transactions) to execute a transaction on a blockchain in the HyperledgerFabric. It starts by sending a transaction proposal request to all the configured peers. Ifenough proposal responses are successful (and not too many have failed), then thetransaction is sent to the configured Orderers. The Transaction service can be configured intwo modes:Synchronous PostingAsynchronous PostingFor more information and several examples, see Hyperledger Fabric Transaction Service onpage 18.Synchronous PostingSynchronous posting sends the transaction proposal to the peers, evaluates the response,and then sends the proposal responses to the Orderer. Synchronous posting requires aresponse from the Orderer in order for the process flow to proceed. The subsequent portion ofthe flow will be aware of the resultant success or rejection of the posted transaction.The following is an outline of the synchronous posting process:Runs in the process flow (pflow) as part of its logic.iSM standard pflow services and transformers form the payload (transaction).The posting service (under the covers) handles the two-way communication within thenetwork peers.Posts the transaction to multiple peers.Peer chaincode validates the transaction against the smart contract.Chaincode sends results back to the posting service.iSM internal logic can perform first level validation of results (allows performanceimprovements).Upon validation by iSM, the peer results are sent to the Orderer.10
1. Introducing BlockchainFabric's OrdererEnsures the network is consistent and has ultimate control of the network.Posting Service (the last step)Makes results available to the flow and lets the flow continue.Asynchronous PostingAsynchronous posting to the blockchain enables the posting flow to proceed without waiting forthe response from the Orderer, which provides an advantage. This enables the application toproceed and handle results of the post at a later time.The asynchronous post service, like the synchronous post service, uses the Fabric provider toreach the Hyperledger system.The Orderer sends the new block to the peer, the peer writes the new block, and then sendsan event to all the parties that have registered with its event hub. Standard iSM Internal Queueoperation presents these response messages to a process flow configured on the queue; thatprocess flow handles both success and failure responses from the Orderer. If, however, youelect to shortcut error handling by configuring the posting service to perform basic validation ofpeer responses, these early rejections will not be sent to the internal queue as they have notyet reached the Orderer.The following is an outline of the asynchronous posting process:Runs in the process flow (pflow) as part of its logic.iSM standard pflow services and transformers form the payload (transaction).The posting service (under the covers) handles the two-way communication within thenetwork peers.Posts the transaction to multiple peers.Peer chaincode validates the transaction against the smart contract.Chaincode sends results back to the posting service.iSM internal logic can perform first level validation of results (allows performanceimprovements).Upon validation by iSM, the peer results are sent to the Orderer.Service Manager and Blockchain Solutions Development Guide11
Hyperledger Fabric ComponentsLater in time.Fabric's OrdererEnsures the transaction across the networked peers is consistent.Has ultimate control of the network.Emits an event to be trapped by iSM.iSM Fabric Asynchronous Response HandlerThe Hyperledger Fabric listener receives the event from the event hub, formats it in XMLor JSON, and sends it to an iSM Internal Queue for handling.The following diagram illustrates how iSM posts a unique iSM TID (Transaction ID) along withapplication data for that transaction within a block.The result of the selected query is returned to iSM from the blockchain for transactionanalysis.Understanding the Internal QueueStandard configuration of the Internal Queue is described in the iWay Cross-Channel ServicesGuide. The only caveat is that you must not enable inhibit mode for the Internal Queue.Instead, iWay recommends configuring the Internal Queue to send a passivation throttlemessage to the posting channel should a high water mark be reached.See the iWay Cross-Channel Services Guide for more information on configuring an InternalQueue, including the use of persistence to prevent loss of messages in the event that theserver is shut down before all response messages have been handled.The service offers specific asynchronous component configuration, including the name of theInternal Queue to receive the response. The Internal Queue listener can use configured routingservices to select the proper flow for the specific message, or can use a single flow thatdifferentiates the messages within the flow.12
1. Introducing BlockchainThe message that reaches the Internal Queue for processing includes the time of posting, theparameters of the posting service, the name of the posting service, and so on. The responseflow runs under the same iSM Transaction ID (TID) as that of the posting flow.Query ServiceThis service invokes chaincode to make a read-only query in the Hyperledger Fabric. Theservice sends a query proposal request to all the configured peers, then it extracts theresponse payload from the first successful proposal response. The payload is a singleByteString value, but it can also be parsed by the service in XML or JSON, assuming thechaincode produced the result in this format.For more information and an example, see Hyperledger Fabric Query Service on page 26.Query Block ServiceThis service queries the Hyperledger Fabric for a specific block and returns it. The searchcriteria can be a block number, a block hash or a Transaction ID. The result is a BlockInforesponse encoded in an XML or JSON parsed tree.For more information and an example, see Hyperledger Fabric Query Block Service on page29.Fabric ListenerThe Hyperledger Fabric listener connects to the event hubs and listens for block events. Thelistener returns the BlockEvent encoded in an XML or JSON parsed tree. In the HyperledgerFabric, a BlockEvent is an abbreviated view of a BlockInfo with the TxReadWriteSetInfo missingbut the event hub origin added. If necessary, the complete BlockInfo can be retrieved byBlockNumber later in a process flow with the help of the Hyperledger Fabric Query BlockService.This listener does not interact with the asynchronous post requests, which are fielded by theprovider and handed off to the configured Internal Queue.For more information and an example, see Hyperledger Fabric Listener on page 42.Service Manager and Blockchain Solutions Development Guide13
Hyperledger Fabric Components14
Chapter2Hyperledger Fabric ComponentReferenceThis chapter provides a reference for predefined Hyperledger Fabric components that areavailable in iWay Service Manager (iSM).In this chapter:Hyperledger Fabric Channel ProviderHyperledger Fabric Transaction ServiceHyperledger Fabric Query ServiceHyperledger Fabric Query Block ServiceHyperledger Fabric Key History ServiceHyperledger Fabric ListenerHyperledger Fabric Channel ProviderDescription:The Hyperledger Fabric Channel provider holds the configuration to reconstruct a HyperledgerFabric Channel on the client side. Other components can refer to the provider by name to gainaccess to the Channel. For example, Hyperledger Fabric Services use the Channel to executetransactions or make queries, and the Hyperledger Fabric listener uses the Channel to listenfor events coming from the event hubs. Multiple components can share the same providersafely.This provider can be created within the server tab of the console by clicking on the FabricChannel Provider link in the left menu.Parameters:The following tables list and describe the parameters for the Hyperledger Fabric Channelprovider.Service Manager and Blockchain Solutions Development Guide15
Hyperledger Fabric Channel ProviderUserParameterDescriptionUser NameThe user must have been previously registered and enrolled in fabricca (or an equivalent member service).MSPIDMembership service provider identifier.EnrollmentCertificatePath to the enrollment certificate for that user, see:Enrollment PrivateKey FABRIC CA CLIENT HOME/msp/signcerts/cert.pemPath to the enrollment private key in PEM format for that user, see: FABRIC CA CLIENT HOME/msp/keystore/key.pemThe User group of parameters define the user credentials. The MSPID is chosen when the useris registered with Fabric CA (Certificate Authority), or an equivalent member service. The MSPIDis usually an organization name, such that all users of a single organization share the sameMSPID. The certificate and private key are generated when the user is enrolled. The providerrequires the certificate and private key to be stored in PEM files. This is the same formatproduced by the command line utility fabric-ca-client when enrolling a user.FabricParameterDescriptionChannel NameThe name of the channel.Peer EndpointsComma separated list of peer definitions in the form peerName@url.For example:peer0@grpc://host:7051Orderer EndpointsComma separated list of orderer definitions in the formordererName@url. For example:orderer0@grpc://localhost:705016
2. Hyperledger Fabric Component ReferenceFabricParameterEvent HubEndpointsDescriptionComma separated list of event hub definitions in the formeventHubName@url. For example:peer0@grpc://localhost:7053Transaction WaitTimeTransaction wait time, which uses the format of [xxh][xxm]xx[s].For example, 1m30s is 90 seconds.The Fabric group of parameters define the channel. If a list of endpoints becomes large, itmight be more convenient to store it in a file and load it with the FILE(filepath) function. In thiscase, each endpoint can appear on a separate line. Inside the file, a line starting with the #character is a comment and is ignored to the end of line.Example:The following example shows the parameter values that are used to reconstruct the channel inthe End2endIT sample of the Hyperledger Fabric Java SDK. Replace host.com with the actualhost name.ParameterValueUser Nameuser1MSPIDOrg1MSPEnrollment Certificateuser1/cert.pemEnrollment Private Keyuser1/key.pemChannel NamefooPeer Endpointspeer0@grpc://host.com:7051Orderer Endpointsorderer0@grpc://host.com:7050Event Hub Endpointspeer0@grpc://host.com:7053Service Manager and Blockchain Solutions Development Guide17
Hyperledger Fabric Transaction ServiceParameterValueTransaction Wait Time20In the example above, the file path user1/cert.pem must point to a file that contains theenrollment certificate for user1 as generated by the Membership Services Provider (i.e. fabricca). This is a sample enrollment certificate file:-----BEGIN KL/gb3 j5fBfSe3A2TEwP igCD893awKgVgBAjQvp2XUq/Fn2SVC3IcrLNjtblaD piFjAKBggqhkjOPQQDAgNIADBFAiEArZi gu56MY/VoKhXUOAhQ3qI8EO7KjduZEKi C3LA 8CIDLcPlnFzuZ2jNnF GiSAA2BE6qc8kd0YHWNSnf8GrEd-----END CERTIFICATE-----In the example above, the file path user1/key.pem must point to a file that contains the privatekey for user1 as generated by the Membership Services Provider (for example, fabric-ca). Thefollowing is a sample private key file:-----BEGIN EC PRIVATE KEY----MHcCAQEEIHMjJth72UerCb2S6UH2IyDcF7T4ZszKeA9 UUt5CvhixIx7iCdJulQi1NWMcufPvuQ6Zt2aAxBKghk2aMov Bvf6Pl8F9J7cDZMTA/w -----END EC PRIVATE KEY-----Hyperledger Fabric Transaction ion:This service invokes chaincode to execute a transaction on a blockchain in the HyperledgerFabric. It starts by sending a transaction proposal request to all the configured peers. Ifenough proposal responses are successful (and not too many have failed), then thetransaction is sent to the configured Orderers.18
2. Hyperledger Fabric Component ReferenceIn synchronous mode, the service waits for the transaction event from the configured eventhubs to make sure the transaction was committed to the blockchain. In asynchronous mode,the service returns immediately because a message is sent to an internal queue when theevent finally arrives. An internal queue listener must be configured to read that internal queueto continue processing after the confirmation event.The TransactionID is stored in the Special Register (SREG) named fabric.TransactionID. Uponerror, the output is an error document. When successful in synchronous mode, the outputdocument can be the input document, the chaincode return value, or the TransactionEvent.When successful in asynchronous mode, the output document is the input document.Parameters:The following tables list and describe the parameters for the Hyperledger Fabric Transactionservice.MainFabric Channel ProviderThe name of the configured Hyperledger Fabric Channelprovider.Chaincode NameThe name of the chaincode to call.Chaincode PathThe path of the chaincode to call.Chaincode VersionThe version of the chaincode to call.Minimum SuccessfulProposalsMinimum number of successful proposals required to sendthe transaction to the Orderers.Maximum Failed ProposalsMaximum number of failed proposals tolerated. Thetransaction will not be sent to the Orderers if there are morefailed proposals.ReturnDetermines the contents of the output document. Ignored ifasynchronous mode is selected.In the Main group of parameters, the service refers to the Fabric Channel Provider by name togain access to the reconstructed Channel. The chaincode name, path and version aredetermined when the chaincode is installed. The path is similar to a namespace and is notrelated to a path in the file system. The chaincode must already be installed before calling theHyperledger Fabric Transaction service.Service Manager and Blockchain Solutions Development Guide19
Hyperledger Fabric Transaction ServiceThe Hyperledger Fabric Transaction service has a simple acceptance criterion to decide if thetransaction is sent to the Orderers to be committed to the blockchain. There must be aminimum number of successful proposals and the number of failed proposals cannot exceed amaximum. This simple criterion is used by the service as an optimization. It does not have tobe perfect. The real endorsement policy is evaluated by the Orderers when creating the block.The Return parameter determines the contents of the output document in synchronous mode.The output document can be the input document, the chaincode return value, or theTransactionEvent, The chaincode return value is a ByteString, which can be parsed in dif
Hyperledger Fabric Components The Hyperledger Fabric facility in iWay Service Manager (iSM) includes access to the Fabric system, posting services, and query services. For more detailed information on these components, see Hyperledger Fabric Component Reference on page 15. Channel Provider Connection to the Hyperledger Fabric system is handled .
Bathroom - Ceramic tiles, builders selected colour board range not exceeding 22 SQM WC/Powder Room - Ceramic tile, builders selected colour board range not exceeding 22 SQM Laundry - Ceramic tiles, builders selected colour board range not exceeding 22 SQM Ensuite - Ceramic tiles, builders
Page 1 Builders FRAMEWORK JUNE 2016 June 16, 5:00 Need more info? Click link to the FABA website: FABAVA.COM Volume 11, Issue 6 A publication of the Fredericksburg Area Builders Framework
warranty does not extend or alter the Builder's responsibilities. Bonded Builders Warranty Group 1500 Kings Highway, Port Charlotte, Florida 33980 Phone: 800-749-0381 * Fax: 941-743-0534 www.bondedbuilders.com BONDED BUILDERS WARRANTY GROUP (800-749-0381) AND BONDED BUILDERS INSURANCE SERVICES (877-219-9519)
Fortress met with deck builders, and it quickly became clear the market needs a steel system that is affordable, looks and assembles like wood, and is easy to install. To answer these requests, we introduced Evolution by Fortress Framing, a steel system designed by deck builders, for deck builders. 1 Our Story 3 Wood to Steel 4 Why Evolution?
Apr 09, 2019 · Chaudhary Khaleeq-uz-Zaman Road, Clifton, Block 8, Karachi. FM 1700 Mr. Muhammad Anis Mr. Saqib 31. Abu Zar Hashmi Builders & Developers Shop No. 1, H.No. R-3 ST-34 Sector. L1, Baba Morh, North Karachi FM 1933 Mr. Muhammad Suleman Mr. Farrukh 32. ACACIA Builders & Developers ACACIA Res
A site specific exemption to the City's Zoning By-law in 1992 allows a builders' supply yard to operate at 555 Dupont Street. A builders' supply yard means a yard for the . builders' supply yard. North: tennis club and Loblaws parking lot. . not permitt
Architectural Hardware. Leading Manufacturer of High Quality Builders Hardware in Canada Since 1978 Untitled-7 1 4/9/09 7:42:43 AM. Contents Canadian Builders Hardware Mfg. Inc. 71 SheffieldStreet, Toronto, Ontario M6M 3E9 Tel: 416-243-1166 Fax: 416-243-3352 1 ProductDescription Page Contents 1 NumericalIndex 2-3
STATEMENT OF THE CASE . On March 20, 2014 Petitioner G. & G. Builders, Inc. ("Builders") filed a Complaint in the Circuit Court of Cabell County against Respondents Randie
