Can I launch a fully functional corda network for a static set of participants without configuring Trust root , NetworkMap or identityManager.
Does a dev setup require any other config apart from Nodes/Notaries?
Corda has the Network Bootstrapper tool which can be used to set-up a static test network for development purposes.
The tool is in fact integrated into the Corda Gradle plugin and it allows you to quickly deploy a test network using simple Gradle commands with some config defined in your Gradle build file.
All our samples also follow the approach of using the static test network.
Refer here to know how to run a Cordapp using test deployment: https://docs.corda.net/docs/corda-os/4.4/tutorial-cordapp.html
Related
I have made a simple project in Corda. My project has 4 nodes including notary and also SpringBoot APIs in the clients folders. I don't know how to deploy my project to the server. I saw the Corda docs but that tutorial was for a single node. So, my question is how to deploy the Corda project with Multiple nodes on the Server and also the SpringBoot APIs. Can anyone help me with this?
There are actually some good youtube videos on this (from me!).
You can find that here: https://www.youtube.com/watch?v=NtVbkUCSt7s
There's other videos there for GCP and Azure as well.
Essentially you need to make sure that your corda node config's p2pAddress specifies the IP address of the machine in your cloud provider of choice.
I deployed a corda node to corda testnet and I built my sample coded cordapp and copied the jars to the corda node cordapp folder and ran the node and It loaded the workflow (Workflow Cordapp : Template Flows) jar but not the contract (CorDapp Template Contract) jar. The node also is running in production mode. When I do POST requests to the node. It shows error
I configured the contract build.gradle file and turn the signing to false.
This is the node error and the logs:
I believe Devman is correct, in this case, you can't just build cordapps on your local machine and then try to use them for the Corda testnet without some additional changes. You'll need to build and sign your apps with the production keys.
There are a few things you'll have to do with local machine configuration and networking.
Here's the corda docs page on the topic: https://docs.corda.net/docs/corda-os/4.4/deploy-locally.html
Basically I want some advice on designing integration test suite for QA using Cucumber BDD in a microservice-integration application environment.
Should QA maintain a separate code base and github repository for their test suite or its better to have the code residing inside each applications code base?
I am building an integration testsuite using cucumber BDD to test an enterprise applications platform. Each application in this platform has many microservices(built in springboot) and integration apps(Apache camel and fuse). Currently I have the test suite built for each project in the eclipse IDE(in the sense each micro service and integration app has its own code base in src/main folder and I have cucumber tests for each of them in the corresponding src/test folder). But I see these as system test rather than integration tests. When an app is deployed only its tests will be triggered in jenkins pipeline and cant run tests for a dependent app or service from its domain due to access restrictions.
So what I am thinking is let QA team create and maintain a separate test application for their tests in a standalone repository rather than maintaining in each application level for integration tests and integrate it in Jenkins pipeline and trigger the features needed for each app using proper cucumber tags after deployment of the main app. Any suggestions are welcome.
Can anyone provide insights of using Jenkins for automating deployment under controlled and uncontrolled enviroments. We have different environments - dev/qa/uat/prod and currently we are using batch files that call msbuild/nant scripts to deploy on web and DB servers (web farm). Developers only have access to dev/qa and production support will deploy on uat/prod. Prod. support will get the source code from SVN tag folder and run the batch file to deploy the application.
By using Jenkins, is it possible to eliminate the step of prod. support team getting the script from SVN by running the jobs using their credentials via url. And what is the general practice using source control and CI tool for deploying applications.
My recommendation is to reserve Jenkins for just building the software. That way the user of Jenkins only have access to development and perhaps QA systems.
To decouple the build system from the process that deploys the software I recommend the use of a binary repository manager like:
Nexus
Artifactory
Archiva
In that way deployment scripts could retrieve any version of a previous build. The use of a repository manager would enable your QA team to certify a release prior to it's deployment onto production.
Finally, consider one of the emerging deployment automation tools. Tools like Chef, Puppet, Rundeck can be used to further version control the configuration of your infrastructure.
We are trying to automate our tests but we have some problems.
Our solution has 7 projects, one of them is WCF server and one of them is Windows Forms project. Others are helper projects.
We created a test plan and test cases. We runned our test cases with action recording and converted manual tests to Coded UI test. After that, we assoiciate our coded ui test with test case.
We defined a new build. This new build deploys WCF server to IIS and transform app.config and copy client application files to a folder.
We setted up test controller and test agent at same build machine.
I wonder what need we to do to automate our build and test?
How our build trig automated test?
Because of VMWare infrastructure we can't use Lab Management.
I solved this problem myself.
I used msdeploy to deploy WCF service
I created a database project and used VSDBCMD tool
I installed test controller and test agent my build server
I created test settings for automated tests and configured to use this agent
I attached my coded ui test with test case
Then it is ok :)