Skip to content

Commit 9915210

Browse files
Edits
1 parent d896033 commit 9915210

4 files changed

Lines changed: 15 additions & 8 deletions

File tree

modules/ROOT/nav.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@
77
*** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance]
88
*** xref:create-instance-task-mule.adoc[Add a Mule Gateway API Instance]
99
*** xref:create-instance-task-service-mesh.adoc[Add a Service Mesh API Instance]
10-
*** xref:manage-exchange-api-task.adoc[Add an API Instance on a Self-Managed Server]
1110
** xref:find-api-id-task.adoc[Obtain an API Instance ID]
1211
** xref:export-api-latest-task.adoc[Export an API Instance]
1312
** xref:access-developer-portal-task.adoc[Access the Developer Portal]

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

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,14 +72,22 @@ CloudHub proxy includes a CPU with 0.1 vCores and a memory of 500 MB, by default
7272
... Select the *Version* for Mule runtime.
7373
... Select the *Java version*.
7474
.. Enter a *Proxy app name*.
75-
* *Hybrid:* Select Hybrid if you have a Mule runtime running on an on-premises server that you want to use.
75+
76+
* *Hybrid:* Select Hybrid if you want to use a Mule runtime running on an on-premises server that is registered in Runtime Manager.
7677
See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manager] for more information.
7778
+
79+
.. Select a target from the list or click **Add server**.
80+
.. Enter a *Proxy app name*.
81+
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[].
83+
+
7884
[NOTE]
79-
--
80-
If you are running an API with a self-managed server, use the xref:manage-exchange-api-task.adoc[classic API creation flows]
81-
to manage your API.
82-
--
85+
====
86+
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:
87+
88+
. 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].
90+
====
8391
+
8492
.. Select a target from the list or click **Add server**.
8593
.. Enter a *Proxy app name*.

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,5 +9,3 @@ include::partial$task-add-api-instance.adoc[tags=flex-intro]
99
include::partial$task-add-api-instance.adoc[tags=mule-intro]
1010
* xref:create-instance-task-service-mesh.adoc[] +
1111
include::partial$task-add-api-instance.adoc[tags=service-mesh-intro]
12-
* xref:manage-exchange-api-task.adoc[] +
13-
Use a Hybrid deployment type to add API instances to self-managed servers.

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ ifndef::env-site,env-github[]
33
include::_attributes.adoc[]
44
endif::[]
55
:product: mule
6+
:page-aliases: manage-exchange-api-task.adoc
7+
68

79
include::partial$task-add-api-instance.adoc[tags=intro1;mule-intro;intro2]
810

0 commit comments

Comments
 (0)