Add images

en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup-with-km-separated.md

@@ -42,7 +42,7 @@ Given below are the API-M nodes you can have in a distributed deployment.
     </tr>
 </table>
 
-
+<a href="{{base_path}}/assets/img/setup-and-install/deployment-km.png"><img src="{{base_path}}/assets/img/setup-and-install/deployment-km.png" width="100%"></a>
 
 {!includes/deploy/steps-to-deploy-apim-in-a-distributed-setup-with-km-separation.md!}
 

en/docs/install-and-setup/setup/distributed-deployment/product-profiles.md

@@ -45,6 +45,12 @@ Listed below are the startup commands for starting each of the API-M profiles.
         </td>
         <td><pre><code>-Dprofile=traffic-manager</code></pre></td>
     </tr>
+    <tr>
+        <td>
+            Key Manager Profile
+        </td>
+        <td><pre><code>-Dprofile=api-key-manager-node</code></pre></td>
+    </tr>
 </table>
 
 

en/docs/install-and-setup/setup/distributed-deployment/understanding-the-distributed-deployment-of-wso2-api-m.md

@@ -41,6 +41,14 @@ Listed below are the different profiles available in WSO2 API Manager.
             Only starts the Traffic Manager component.
         </td>
     </tr>
+    <tr>
+        <td>
+            Key Manager Profile
+        </td>
+        <td>
+            Only starts the Key Manager component.
+        </td>
+    </tr>
 </table>
 
 ## Databases used by API-M profiles
@@ -79,6 +87,12 @@ database</strong></p>
 <td>Used</td>
 <td>Used</td>
 
+</tr>
+
+<tr class="even">
+<td><p><strong>Key Manager profile</strong></p></td>
+<td><p>Used</p></td>
+<td><p>Used</p></td>
 </tr>
 </tbody>
 </table>
@@ -161,6 +175,8 @@ The following diagram depicts how the Control Plane, Traffic Manager, and Gatewa
 
 The following diagram depicts how the Control Plane, Key Manager, and Gateway profiles communicate in a distributed deployment setup. It also depicts the database connections of each node. Separating the Key Manager component from the Control Plane may be necessary if there are deployment complexities in your environment. For example, if there is a high number of token generation calls, it might be required to scale the Key Manager component. In such cases, separating the Key Manager from the Control Plane allows for independent scaling.To learn how to configure this deployment, refer [configuring a distributed API-M deployment]({{base_path}}/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup-with-km-separated).
 
+[![Distributed deployment]({{base_path}}/assets/img/setup-and-install/distributed-deployment-km.png){: style="width:78%"}]({{base_path}}/assets/img/setup-and-install/distributed-deployment-km.png)
+
 ## What's Next?
 
 -   Find out more about [running API-M profiles]({{base_path}}/install-and-setup/setup/distributed-deployment/product-profiles).