While deploying chaincode for two organisations in GoLang, a user just installed the chaincode on the peer of Org1 and the peer of Org2.

While deploying chaincode for two organisations in GoLang, a user just installed the chaincode on the peer of Org1 and the peer of Org2.What is the correct next step in the process?He needs to set the PACKAGE_ID value using the following command:<br /> Source./scripts/setPackageID.sh outfileHe needs to set the PACKAGE_ID value using the following command:<br /> Source./set/scripts/PackageID.sh outfile teeHe needs to query for installed packages using the following command:<br /> Peer lifecycle chaincode queryinstllaed 2>&1 | tee outfileHe needs to query for installed packages using the following command:<br /> Peer lifecycle chaincode query installed 2>$1 | outfile tee

While deploying GoLang chaincode in Hyperledger Fabric, which of the following commands will you use to install the chaincode on peer of Org1?Consider that you need to install “myvechicle.tar.gz”.run peer chaincode install myvehicle.tar.gzrun lifecycle install chaincode myvehicle.tar.gzpeer lifecycle chaincode install myvehicle.tar.gzpeer run lifecycle install chaincode myvehicle.tar.gz

A user has created a channel named test1 and added peers to it for the example application "Fabric-Example". Now he wants to deploy the GoLang chaincode named "myVehicle". He has updated the environment variable to configure use of GoLang chaincode using the script "setMyVehicleGolangContext". Now, he wants to package the chaincode for org1 with the script setOrgPeerContext.sh 1.Which of the following commands can he use for that?source ./scripts/setOrgPeerCotext.sh 1<br /> Peer lifecycle package chaincode myvehicle.tar.gaz SET --path $(CC_SRC_PATH) --lang $(CC_RUNTIME_LANGUAGE) –label myvehicle_$(VERSION)source ./script/setOrgPeerContext.sh 1<br /> Peer set --lifecycle --package chaincode myvehicle.tar.gaz --path $(CC_SRC_PATH) --lang $(CC_RUNTIME_LANGUAGE) --label myvehicle_$(VERSION)source ./scripts/setOrgPeerContext.sh 1<br /> Peer lifecycle chaincode package myvehicle.tar.gaz --path $(CC_SRC_PATH) --lang $(CC_RUNTIME_LANGUAGE) --label myvehicle_$(VERSION)source ./script/setOrgPeerContext.sh 1<br /> Peer lifecycle chaincode package myvehicle.tar.gaz SET --path $(CC_SRC_PATH) --language $(CC_RUNTIME_LANG) --label myvehicle_$(VERSION)

While deploying GoLang chaincode in Hyperledger Fabric a user has approved the Chaincode as Org1. Now he is required to verify the commitreadiness in Org1.Which of the commands can he use to do so?peer lifecycle chaincode checkcommitreadiness --channelID --channelName myvehicle --version ${VERSION} --sequence ${VERSION} --OUTPUT binary --init-requiredpeer lifecycle chaincode verifycommitreadiness --channelID --Channlename myvehicle --version ${VERSION} --sequence ${VERSION} --OUTPUT binary --init-requiredpeer lifecycle chaincode checkcommitreadiness --channelID $CHANNEL_NAME --name myvehicle --version ${VERSION} --sequence ${VERSION} --OUTPUT json --init-requiredpeer lifecycle chaincode verifycommitreadiness $CHANNEL_ID --channelID $CHANNEL_NAME --name myvehicle --version ${VERSION} --sequence ${VERSION} --OUTPUT json --init-set

While deploying chaincode for two organisations in GoLang, a user needs to commit the chaincode definition to a channel named myVehicle.What is the correct way of doing so?Consider that we are using the port 7050.He needs to execute the following command:<br /> Peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com -tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA --channelID $CHANNEL_NAME --name myVehicle $PEER_CONN_PARMS --version ${VERSION} --sequence ${version} --init-requiredThe chaincode definition is committed by default after a peer address is set successfully, and the user does not need to do anythingHe needs to execute the following command:<br /> Peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --cafile $ORDERER_CA --channelID $CHANNEL_NAME --name myVehicle $PEER_CONN_PARMS --tls $CORE_PEER_TLS_ENABLED --version ${VERSION} --sequence ${version} --init-requiredHe needs to execute the following command:<br /> Peer lifecycle chaincode commit -p localhost:7050 --ordererTLSHostnameOverride orderer.example.com --cafile $ORDERER_CA -tls $CORE_PEER_TLS_ENABLED --channelID $CHANNEL_NAME --name myVehicle $PEER_CONN_PARMS --version ${VERSION} --sequence ${version} --init-required