Update profile info in create a channel doc

Signed-off-by: Amrit Prakash <amritdevil1st@gmail.com>
hyperledger · Apr 3, 2024 · efd76c8 · efd76c8
1 parent e084587
commit efd76c8
Show file tree

Hide file tree

Showing 2 changed files with 25 additions and 11 deletions.
diff --git a/docs/source/create_channel/create_channel_config.md b/docs/source/create_channel/create_channel_config.md
@@ -140,13 +140,20 @@ The test network uses the default policies provided by Fabric, which require tha
 
 The `configtxgen` tool reads the channel profiles in the **Profiles** section to build a channel configuration. Each profile uses YAML syntax to gather data from other sections of the file. The `configtxgen` tool uses this configuration to create a genesis block for joining orderers to a new channel via the channel participation API. To learn more about YAML syntax, [Wikipedia](https://en.wikipedia.org/wiki/YAML) provides a good place to get started.
 
-The `configtx.yaml` used by the test network contains one channel profile `ChannelUsingRaft`.
-The `ChannelUsingRaft` profile is used by the test network to create application channels:
+The `configtx.yaml` used by the test network contains one channel profile `TwoOrgsApplicationGenesis`.
+The `TwoOrgsApplicationGenesis` profile is used by the test network to create application channels:
 ```yaml
 ChannelUsingRaft:
   <<: *ChannelDefaults
   Orderer:
     <<: *OrdererDefaults
+    OrdererType: etcdraft
+    EtcdRaft:
+      Consenters:
+        - Host: orderer.example.com
+          Port: 7050
+          ClientTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
+          ServerTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
     Organizations:
       - *OrdererOrg
     Capabilities: *OrdererCapabilities

diff --git a/docs/source/create_channel/create_channel_test_net.md b/docs/source/create_channel/create_channel_test_net.md
@@ -100,16 +100,23 @@ This `configtx.yaml` file contains the following information that we will use to
     ChannelUsingRaft:
         <<: *ChannelDefaults
         Orderer:
-            <<: *OrdererDefaults
-            Organizations:
-                - *OrdererOrg
-            Capabilities: *OrdererCapabilities
+        <<: *OrdererDefaults
+        OrdererType: etcdraft
+        EtcdRaft:
+            Consenters:
+            - Host: orderer.example.com
+                Port: 7050
+                ClientTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
+                ServerTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
+        Organizations:
+            - *OrdererOrg
+        Capabilities: *OrdererCapabilities
         Application:
-            <<: *ApplicationDefaults
-            Organizations:
-                - *Org1
-                - *Org2
-            Capabilities: *ApplicationCapabilities
+        <<: *ApplicationDefaults
+        Organizations:
+            - *Org1
+            - *Org2
+        Capabilities: *ApplicationCapabilities
     ```
 
 The profile includes both peer organizations, `Org1` and `Org2` as well as the ordering organization `OrdererOrg`. Additional ordering nodes and ordering organizations can be added or removed from the consenter set at a later time using a channel update transaction.