I found the guideline to deploy Hyperledger Fabric to "Azure Hyperledger Single Member Blockchain" here but I can't deploy my Composer network.
I don't found any guideline to do it.
Does anyone have the same problem with me?
Thanks!
cool. Next, go ahead and install Hyperledger Composer and its tooling, see doc link here -> https://hyperledger.github.io/composer//installing/development-tools.html
It describes all of the pre-requisites you need to set up on your Development VM (that interacts with your Fabric network).
You'll then need to gather the names or IP addresses of your Fabric nodes like CA, orderer etc. and you will provide that information to the connection profiles https://hyperledger.github.io/composer/reference/connectionprofile.html you define, as part of your business network card creation https://hyperledger.github.io/composer//managing/id-cards-playground - this is so that your Admins and Composer participants can connect/deploy/update/interact with the runtime Fabric network and configured nodes, that you have configured on Azure.
best wishes !
Related
I'm was trying to deploy my code to a device with XAR, but I only find solutions that I've to be in the same network...
Is it possible to deploy to a device with XAR which is not in my network? I want to be at the office and try to deploy and connect to a PLC in a factory...
As with anything networking related, this is possible but will require a great deal of assistance from your company IT Team.
All that is needed to allow for deployment from one network to another is the ADS network ports opened for communication as detailed in Infosys. If you cannot gain access to the factory network for external connection then you will need to work through another solution.
On Playground (macOS) I have one network card admin#perishable-network and I can connect to the business network. However the network card is not visible in directory /Users//.composer/cards. Instead I can see PeerAdmin#hlfv1 there.
Another problem is that I get an error running composer-rest-server using PeerAdmin#hlfv1: No business network has been specified for this connection
I'm guessing on playground you created the business network on the Web Browser Connection which means all cards for that business network will be held in your browser local storage not on your file system. Also that business network is running inside your browser, not in a real fabric so you cannot interact with it any other way except through playground (for example you cannot try to connect the rest server to it).
You cannot use PeerAdmin#hlfv1 with the rest server. This is a fabric network card (ie you use it to perform fabric level activities such as install, start, upgrade) not a business network card. You need a business network card (one that has been associated with a business network) in order for the rest server to connect and discover the specific business network in order to generate the rest api.
I am getting a connection refused error while trying to deploy a new business network on the Hyperledger Composer playground which is running locally on the environment. The environment is behind the corporate proxy and I have setup both the proxies (http and https) in the system.
The exact error is mentioned below:
{"error":
{"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect","address":"151.101.0.162","port":443}}
I have followed the links given below to setup the Hyperledger Fabric and the corresponding docker containers.
https://hyperledger.github.io/composer/installing/development-tools.html
https://hyperledger.github.io/composer/tutorials/developer-guide.html
At the end of the setup, I notice that there are five docker containers running in the system -
composer, peer0.org1.example.com, orderer.example.com, ca.org1.example.com and couchdb
When I follow the developer guide and try deploying the new business network on the Online BlueMix Composer Playground platform, it works. I was able to see the transactions, commodities and etc for the sample example application.
However, I notice the above error when I tried deploying the new business network on the local composer playground.
The development environment on which the Composer and the fabric is hosted are Ubuntu 14.04, python 2.7, node v6.11.0, npm5.0.4, docker-compose v1.13.0.
Can somebody kindly suggest a workaround / direct me to certain links to resolve this problem?
I was wondering if since the 0.15.0 release and switching to cards someone has figured out how to access the same network both locally via the CLI and in the Playground and with the same Fabric runtime.
So far, I have been able to install my network's runtime, start and ping it on the Playground's fabric after creating PeerAdmin card using the script that came with Playground.
However, importing the newly deployed network's admin card fails in the Playground. If, however, I deploy the network via the Playground, export the admin card, download/import the admin card from the Playground and then try to composer ping it, it just sits there timing out after a while. This is MacOS High Sierra. So what gives and what can be done?
Thanks much!
If I understood your issue correctly, this is how you can solve it:
Create your business network in Playground
Export business network card from Playground (download button on card) which produces {nameOfUser}.card file.
Now you transfer this card to wherever you have installed fabric/playground
Run command: composer card import -f {nameOfUser}.card
Now your business card should appear under location {usersHome}/.composer/cards/user#network-name
Inside /cards folder, you should see 2 folders. One is "PeerAdmin" which was created if you followed setup and another one is your imported one
Copy connection.json from "PeerAdmin" to your new card and replace it. (this is most important step)
Run command: composer-rest-server and use as network card: user#network-name - folder that you copied
With all this steps I successfully created and ran server. Now you can access it on port IP:3000/explorer
You can share the Business Network Cards between Playground and the CLI. However it can be a bit more difficult if you are running Playground in a Docker Container.
With the CLI you connect to your Fabric servers on localhost and Docker deals with the Port fowarding into the Containers for the Fabric.
The Fabric Containers (and the Playground if you start it in a container) connect with eachother on 'fake' addresses managed by docker-compose e.g. orderer.example.com:7050
So if you start composer-playground using the CLI any Card you export will have localhost as the addresses of Fabric servers and other CLI commands will be able to utilise it. If however you are using Playground in a container the Card will use the fake addresses and you will not be able to connect from the CLI straightaway.
I assume you are using Playground in a Container and hence having the problem. If you find the connection.json in a location similar to: ~/.composer/cards/admin#*xxxxxx*/connection.json and edit the addresses of the fabric server to be localhost you should be able to use the CLI as expected.
I have tried to find many way that if I can use Laravel Forge with my existing dedicated hosting server based on cPanel/WHO or Do I need to purchase a package from Digital Ocean or Amazon Web Service? But Could not get enough information on that.
I need make sure before I purchase Forge.
Forge allows you to instantly create virtual machines using existing cloud providers like digital ocean. Your own virtual machine or dedicated machine therefor is not supported.
This is an old post, therefore this is updated answer. Yes you can install Forge on your own dedicated server. It should also work with previusly installed cpanel/... but some extra configuration will probably be needed.