I have defined a Business Network, installed and deployed it on my local machine. I have also create a local REST server for testing. When I am submitting transactions through API calls, they are reflected in the REST server (which I can verify through GET requests on the same APIs) but not being reflected in the Composer Playground 'All Transactions'. Where am I going wrong ?
Composer-playground only provide easy access to the hyperledger network.
So, if you made the transaction REST-API, than you can see the same transaction in local playground also and vice-versa.
So, check that you connected to same business-network in playgroud.
Run composer-playground command, connect to network installed, that's it.
Related
Till now I was running the Composer REST Server (Blockchain) locally on the local host server. Now this server has got some post APIs configured which needs to be triggered by my main server already hosted on Heroku(Cloud Service).
So the flow of architecture is like my Android App calls Heroku Server which in turn has to call the Composer REST Server (which is running locally on my machine).
Hence I need to host the composer REST Server on a free tier cloud service. Although its a Node JS Server but it's package.json is weird and I am not able to find any resource which specifies how to take the Composer Online.
Please help!
Is your underlying Fabric is running in Docker Containers?
Assuming that it is, you can run your Composer REST Server in a container too. There is an example of this in the composer documentation for Multi-User mode which makes it look a little more complex, but the import piece is getting the Card in the container. There is also a Tutorial in the composer documentation again for multi user mode.
I have created an application using "Hyperledger Composer"
https://hyperledger.github.io/composer/tutorials/developer-guide.html
Its working fine on my local machine and I am able to access REST API's over local network.
I would like to setup real network. What I mean is multiple hosts and peers. I have been trying to figure out steps/guideline to setup a real fabric v1 network and deploy application on it, but haven't had any luck yet.
My Questions are
What are the steps of deploying real Fabric 1.0 network with multiple hosts, peers?
How to deploy application in real network (once its setup)?
Appreciate any direction here.
If you have a couple of linux VMs with ssh keys configured so you can ssh without prompting for a password you may try https://github.com/yacovm/fabricDeployment
I implemented hyperledger composer tutorial and create a simple business network definition and deploy it on through composer and implement it's rest API's through composer-rest-server. Now I want to add one more peer to it on a different local machine which can access blockchain I created previously, so my question is How can I achieve that a different peer node (another local machine) connected to blockchain I created in the composer tutorial?
you can check the S/Overflow link provided by Ahmed Nasser relating to adding your peer to an existing Fabric network.
Once you have your Fabric network up and running, and all of your network configuration / resolution / docker configuration tested and working, you can come to Composer to define the connection info, such as adding additional peers (and therefore create the requisite business network cards that contain that info).
This single organisation tutorial can give you an idea of what's involved - it builds upon a Fabric network that was already created (a simple, one-peer Fabric blockchain Dev environment) ..see here -> https://hyperledger.github.io/composer/tutorials/deploy-to-fabric-single-org.html
It obviously refers to 'localhost' in this scenario - obviously, you are creating something on an IP network, so you will need IP addresses/ host resolution as appropriate.
I want to connect docusign locally to my application. How it can be done? How can I setup the DocuSign Connect feature while I am developing locally on my laptop? Please guide me with detailed steps.
You're going to have to have your network forward an externally accessible url to your localbox.
Since Connect is a service hosted at DocuSign and requires a valid endpoint to send data to, and if RequireAcknowledgement is enabled, you'll have to send data back to the service as well.
I don't know how to begin on the following. I will explain with the picture below what i want to do.
Like you so you have 2 parts. The local part and the azure part. The azure part is my part. The local network could be a customer, ....
What i went to do is running a service on the pc's and send that data to the local server/gateway. But how can i detect to what server it needs to connect. I don't install any service on the local pc's, that does the customer itself. But i don't want that he needs to do configuration. Just like they install the server/gateway part.
I will run a webservice on azure that gets information from the server/gateway on the local network. So thats no problem. On azure there are some other application that will process the messages.
Also how can you send some message back to the local network? When you say on azure ping the other local computer on the network. You should send a message to the server/gateway on your local network. But how?
So i have 2 questions(see above for more information):
Connecting from the clients to the server/gateway
Send some information back to the local netwerk
You can use Virtual Network, Azure Connect to create a "connection" or "hybrid cloud" between the PCs and the Azure cloud. However, if you are talking about web based/simple messaging and the PCs have internet connectivity why not just route the messages through a secure (SSL/TLS) connection to the cloud?
For broadcasting/push-type notifications, please look at SignalR (http://signalr.net/). Microsoft is making that part of the ASP.NET platform: http://channel9.msdn.com/Events/Build/2012/3-034
It has some real nice functionality like gracefully, falling back on multiple mechanisms if advanced things like WebSockets are not supported by the server/client. This is an ideal solution and super scalable, since it is server based and very light on the client.
If you need to connect only one or more services running on you local network and make them available publicly via azure cloud.
The most straight forward solution i found was to use the services bus. Its require nearly no modification to you business network.