Merge pull request #578 from mulesoft/W-16972662-self-managed-server-fa

W-16972662-self-managed-server-fa

Author: failup

modules/ROOT/nav.adoc

@@ -7,7 +7,6 @@
  *** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance]
  *** xref:create-instance-task-mule.adoc[Add a Mule Gateway API Instance]
  *** xref:create-instance-task-service-mesh.adoc[Add a Service Mesh API Instance]
- *** xref:manage-exchange-api-task.adoc[Add an API Instance on a Self-Managed Server]
  ** xref:find-api-id-task.adoc[Obtain an API Instance ID]
  ** xref:export-api-latest-task.adoc[Export an API Instance]
  ** xref:access-developer-portal-task.adoc[Access the Developer Portal]

modules/ROOT/pages/_partials/task-add-api-instance.adoc

@@ -72,18 +72,22 @@ CloudHub proxy includes a CPU with 0.1 vCores and a memory of 500 MB, by default
 ... Select the *Version* for Mule runtime.
 ... Select the *Java version*.
 .. Enter a *Proxy app name*.
-* *Hybrid:* Select Hybrid if you have a Mule runtime running on an on-premises server that you want to use.
-See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manager] for more information.
+
+* *Hybrid:* Select this option if you want to use a Mule runtime instance running on an on-premises server that is registered in Runtime Manager.
 +
-[NOTE]
---
-If you are running an API with a self-managed server, use the xref:manage-exchange-api-task.adoc[classic API creation flows]
-to manage your API.
---
+See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manager] for more information.
 +
 .. Select a target from the list or click **Add server**.
 .. Enter a *Proxy app name*.
 
+* *Self-managed Server:* Select this option if you want to create a JAR file to deploy an API proxy to a Mule runtime instance running on an on-premises server that is not registered in Runtime Manager. For more information, see xref:mule-runtime::mule-deployment-model.adoc[].
+====
+Deploying an API proxy to a self-managed server in API Manager doesn’t deploy the proxy to your on-premises server. After you deploy the proxy in API Manager, deploy the proxy to your on-premises server:
+. xref:download-proxy-task.adoc[Download your new API proxy JAR file].
+. xref:mule-runtime::deploy-on-premises.adoc[Deploy the JAR file to your on-premises server].
+====
+
+
 * **Runtime Fabric:** Select Runtime Fabric if you want to deploy API Proxies to a Mule runtime engine that is managed on Runtime Fabric.
 See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies to Runtime Fabric] for more information.
 .. Select a target from the list.

modules/ROOT/pages/add-api-instances.adoc

@@ -9,5 +9,3 @@ include::partial$task-add-api-instance.adoc[tags=flex-intro]
 include::partial$task-add-api-instance.adoc[tags=mule-intro]
 * xref:create-instance-task-service-mesh.adoc[] +
 include::partial$task-add-api-instance.adoc[tags=service-mesh-intro]
-* xref:manage-exchange-api-task.adoc[] +
-Use a Hybrid deployment type to add API instances to self-managed servers.

modules/ROOT/pages/create-instance-task-mule.adoc

@@ -3,6 +3,7 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 :product: mule
+:page-aliases: manage-exchange-api-task.adoc
 
 include::partial$task-add-api-instance.adoc[tags=intro1;mule-intro;intro2]