Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion modules/ROOT/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@
*** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance]
*** xref:create-instance-task-mcp.adoc[Add a Flex Gateway MCP Server Instance]
*** xref:create-instance-task-a2a.adoc[Add a Flex Gateway A2A Server Instance]
*** xref:create-instance-task-service-mesh.adoc[Add a Service Mesh API Instance]
** 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]
Expand Down
20 changes: 0 additions & 20 deletions modules/ROOT/pages/_partials/api-configuration-tables.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -77,26 +77,6 @@
|===
//end::flex-upstream-a2a[]


//tag::service-mesh-downstream[]
[%header%autowidth.spread,cols="15%,35%,15%,35%"]
|===
| Field Name | Description | Required | Notes
| *Instance label* | Specifies a label for the API. | No | If you have multiple managed instances of the same API, add a label to differentiate each instance from the others.
| *Advanced Options* | | |
| *Consumer endpoint* | Specifies a proxy application's address for consumers to use for sending requests.| No |
| *Client provider* | Specifies a client provider for the API. | Yes | Anypoint Platform acts as the client provider by default. To configure an external client provider, see xref:access-management::managing-api-clients.adoc[Client Providers].
|===
//end::service-mesh-downstream[]

//tag::service-mesh-upstream[]
[%header%autowidth.spread,cols="15%,35%,15%,35%"]
|===
| Field Name | Description | Required | Notes
| *Upstream URL* | The URL to access for the proxy or the API. | No | For example, you can use the URL of your API asset in Exchange.
|===
//end::service-mesh-upstream[]

//tag::mule-app-downstream[]
[%header%autowidth.spread,cols="15%,35%,15%,35%"]
|===
Expand Down
13 changes: 0 additions & 13 deletions modules/ROOT/pages/_partials/task-add-api-instance.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -27,19 +27,6 @@ and secure your APIs.

//end::mule-intro[]

//tag::service-mesh-intro[]
Use Anypoint Service Mesh to extend Anypoint Platform API Management capabilities to your
Istio service mesh through the deployment of a Mule Adapter.

//end::service-mesh-intro[]

//tag::server-intro2[]
The following diagram shows the server instance's upstream and downstream configurations. In this configuration, the downstream service is the service making requests that are completed by the upstream server. These terms represent the direction of dependency, not the direction of information.

image:server-upstream-downstream-config.png[The server instance is deployed on a gateway between the upstream and downstream configuration]

//end::server-intro2[]

//tag::intro2[]

There are three options for adding an API instance:
Expand Down
2 changes: 0 additions & 2 deletions modules/ROOT/pages/add-api-instances.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,5 +11,3 @@ include::partial$task-add-api-instance.adoc[tags=flex-intro]
include::partial$task-add-api-instance.adoc[tags=flex-mcp-intro]
* xref:create-instance-task-a2a.adoc[] +
include::partial$task-add-api-instance.adoc[tags=flex-a2a-intro]
* xref:create-instance-task-service-mesh.adoc[] +
include::partial$task-add-api-instance.adoc[tags=service-mesh-intro]
1 change: 0 additions & 1 deletion modules/ROOT/pages/api-instance-landing-page.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,6 @@ To manage API instances in API Manager:
** xref:create-instance-task-flex.adoc[]
** xref:create-instance-task-mcp.adoc[]
** xref:create-instance-task-a2a.adoc[]
** xref:create-instance-task-service-mesh.adoc[]
. View an API instance's API Summary for information about the instance or to export it:
** xref:find-api-id-task.adoc[] - API Manager generates the apiId of new APIs managed by API Manager for use with Mule 4.
** xref:export-api-latest-task.adoc[] - After creating an API instance, you can export it. This exports the API instance endpoint configuration and Exchange asset relationship. You can then import it into another environment in the same business group to create a new API instance.
Expand Down
42 changes: 0 additions & 42 deletions modules/ROOT/pages/create-instance-task-service-mesh.adoc

This file was deleted.

3 changes: 1 addition & 2 deletions modules/ROOT/pages/edit-api-endpoint-task.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,7 @@ After you create an API instance in API Manager, you can edit the instance's con
For more information about the API endpoint configuration settings, see:

* xref:create-instance-task-flex.adoc[]
* xref:create-instance-task-mule.adoc[]
* xref:create-instance-task-service-mesh.adoc[]
* xref:create-instance-task-mule.adoc[]

To edit an API instance's endpoint:

Expand Down