github.com/hechain20/hechain@v0.0.0-20220316014945-b544036ba106/docs/source/capability_requirements.rst (about) 1 Defining capability requirements 2 ================================ 3 4 .. note:: This topic describes a network that does not use a "system channel", a 5 channel that the ordering service is bootstrapped with and the ordering 6 service exclusively controls. Since the release of v2.3, using a system 7 channel is now considered the legacy process as compared to the process 8 to :doc:`create_channel/create_channel_participation`. For a version of this topic that 9 includes information about the system channel, check out 10 `Capability requirements <https://hyperledger-fabric.readthedocs.io/en/release-2.2/capability_requirements.html>`_ from the v2.2 documentation. 11 12 As discussed in :doc:`capabilities_concept`, capability requirements are defined 13 per channel in the channel configuration (found in the channel’s most recent 14 configuration block). The channel configuration contains three locations, each 15 of which defines a capability of a different type. 16 17 +------------------+-----------------------------------+----------------------------------------------------+ 18 | Capability Type | Canonical Path | JSON Path | 19 +==================+===================================+====================================================+ 20 | Channel | /Channel/Capabilities | .channel_group.values.Capabilities | 21 +------------------+-----------------------------------+----------------------------------------------------+ 22 | Orderer | /Channel/Orderer/Capabilities | .channel_group.groups.Orderer.values.Capabilities | 23 +------------------+-----------------------------------+----------------------------------------------------+ 24 | Application | /Channel/Application/Capabilities | .channel_group.groups.Application.values. | 25 | | | Capabilities | 26 +------------------+-----------------------------------+----------------------------------------------------+ 27 28 Setting Capabilities 29 -------------------- 30 31 Capabilities are set as part of the channel configuration (either as part of the 32 initial configuration -- which we'll talk about in a moment -- or as part of a 33 reconfiguration). 34 35 .. note:: For more information about how to update a channel configuration, check 36 out :doc:`config_update`. 37 38 Capabilities in an Initial Configuration 39 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 40 41 In the ``configtx.yaml`` file distributed in the ``config`` directory of the release 42 artifacts, there is a ``Capabilities`` section which enumerates the possible capabilities 43 for each capability type (Channel, Orderer, and Application). 44 45 Note that there is a ``Capabilities`` section defined at the root level (for the channel 46 capabilities), and at the Orderer level (for orderer capabilities). 47 48 .. Licensed under Creative Commons Attribution 4.0 International License 49 https://creativecommons.org/licenses/by/4.0/