ENT-2174 documentation (#1145)

Links to Bintray to download Corda binaries replaced by mentioning binaries made available to an organization.
This commit is contained in:
szymonsztuka 2018-07-02 15:24:12 +01:00 committed by GitHub
parent 4f0d4b24d3
commit f5a1be38ff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 12 deletions

View File

@ -24,11 +24,10 @@ handling, and ensures the Corda service is run at boot.
``mkdir /opt/corda; chown corda:corda /opt/corda``
3. Download the `Corda jar <https://r3.bintray.com/corda/net/corda/corda/>`_
(under ``/VERSION_NUMBER/corda-VERSION_NUMBER.jar``) and place it in ``/opt/corda``
3. Place the Enterprise Corda JAR ``corda-VERSION_NUMBER.jar`` in ``/opt/corda``
4. (Optional) Download the `Corda webserver jar <http://r3.bintray.com/corda/net/corda/corda-webserver/>`_
(under ``/VERSION_NUMBER/corda-VERSION_NUMBER.jar``) and place it in ``/opt/corda``
4. (Optional) Copy the Corda webserver JAR provided to your organization
(under ``/corda-webserver-VERSION_NUMBER.jar``) and place it in ``/opt/corda``
5. Create a directory called ``cordapps`` in ``/opt/corda`` and save your CorDapp jar file to it. Alternatively, download one of
our `sample CorDapps <https://www.corda.net/samples/>`_ to the ``cordapps`` directory
@ -191,11 +190,11 @@ at boot, and means the Corda service stays running with no users connected to th
* Oracle Java 8. The supported versions are listed in :doc:`getting-set-up`
1. Create a Corda directory and download the Corda jar. Replace ``VERSION_NUMBER`` with the desired version. Here's an
example using PowerShell::
1. Create a Corda directory and copy the Enterprise Corda JAR ``corda-VERSION_NUMBER.jar``.
Replace ``VERSION_NUMBER`` with the desired version. Here's an example using PowerShell::
mkdir C:\Corda
wget http://jcenter.bintray.com/net/corda/corda/VERSION_NUMBER/corda-VERSION_NUMBER.jar -OutFile C:\Corda\corda.jar
copy PATH_TO_CORDA_JAR/corda-VERSION_NUMBER.jar C:\Corda\corda.jar
2. Create a directory called ``cordapps`` in ``C:\Corda\`` and save your CorDapp jar file to it. Alternatively,
download one of our `sample CorDapps <https://www.corda.net/samples/>`_ to the ``cordapps`` directory

View File

@ -7,17 +7,17 @@ Handcrafting a node
-------------------
A node can be created manually by creating a folder that contains the following items:
* The Corda JAR
* The Corda Enterprise JAR
* Can be downloaded from https://r3.bintray.com/corda/net/corda/corda/ (under /VERSION_NUMBER/corda-VERSION_NUMBER.jar)
* The binary ``corda-VERSION_NUMBER.jar`` provided to your organisation.
* A node configuration file entitled ``node.conf``, configured as per :doc:`corda-configuration-file`
* A folder entitled ``cordapps`` containing any CorDapp JARs you want the node to load
* **Optional:** A webserver JAR entitled ``corda-webserver.jar`` that will connect to the node via RPC
* **Optional:** A webserver JAR entitled ``corda-webserver-VERSION_NUMBER.jar`` that will connect to the node via RPC
* The (deprecated) default webserver can be downloaded from http://r3.bintray.com/corda/net/corda/corda-webserver/ (under /VERSION_NUMBER/corda-VERSION_NUMBER.jar)
* The (deprecated) default webserver is available to you for testing and should not be used in a production environment.
* A Spring Boot alternative can be found here: https://github.com/corda/spring-webserver
The remaining files and folders described in :doc:`node-structure` will be generated at runtime.
@ -80,6 +80,8 @@ in the `Kotlin CorDapp Template <https://github.com/corda/cordapp-template-kotli
}
}
Ensure Corda Enterprise binaries are available on your machine as described in :ref:`Getting Set Up <resolve-corda-enterprise-binaries>`.
Running this task will create three nodes in the ``build/nodes`` folder:
* A ``Notary`` node that:

View File

@ -19,7 +19,7 @@ A Corda node has the following structure:
├── logs // The node logs
├── network-parameters // The network parameters automatically downloaded from the network map server
├── node.conf // The node's configuration files
├── persistence.mv.db // The node's database
├── persistence.mv.db // The node's database (present when the node uses the embedded H2 database instance)
└── shell-commands // Custom shell commands defined by the node owner
The node is configured by editing its ``node.conf`` file (see :doc:`corda-configuration-file`). You install CorDapps on