Skip to content

Commit 6958e51

Browse files
Update task-add-api-instance.adoc
1 parent 07f3a65 commit 6958e51

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,14 @@ See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manag
7979
.. Select a target from the list or click **Add server**.
8080
.. Enter a *Proxy app name*.
8181
82-
* *Self-managed Server:* Select self-managed server if you want to create a JAR file to deploy an API proxy to a Mule runtime running on an on-premises server that is not registered in Runtime Manager. For more information, see xref:runtime-manager::mule-deployment-model.adoc[].
82+
* *Self-managed Server:* Select self-managed server if you want to create a JAR file to deploy an API proxy to a Mule runtime running on an on-premises server that is not registered in Runtime Manager. For more information, see xref:mule-runtime::mule-deployment-model.adoc[].
8383
+
8484
[NOTE]
8585
====
8686
Deploying an API proxy to a self-managed server in API Manager, does not deploy the proxy to your on-premise server. After you deploy the proxy in API Manager, to deploy the proxy to your on-premise server:
8787
8888
. xref:download-proxy-task.adoc[Download your new API proxy JAR file].
89-
. xref:deploy-on-premises.adoc[Deploy the JAR file to your on-premise server].
89+
. xref:mule-runtime::deploy-on-premises.adoc[Deploy the JAR file to your on-premise server].
9090
====
9191
+
9292
.. Select a target from the list or click **Add server**.

0 commit comments

Comments
 (0)