Skip to content

Commit 66bb95e

Browse files
Merge branch 'v2.x' into W-16439901-ASM-EOL-gr
2 parents 1d0aa6f + 5b8a75a commit 66bb95e

10 files changed

Lines changed: 47 additions & 15 deletions

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
* @marinasasso @mulesoft/team-docs
1+
* @failup @mulesoft/team-docs
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
:page-notice-banner-message: Mule API Analytics is scheduled for End of Life on November 30, 2024. Use <a href="https://docs.mulesoft.com/monitoring/">Anypoint Monitoring</a> instead. Contact your MuleSoft account representative for more information.

modules/ROOT/pages/analytics-chart.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
= Reviewing API Manager Mule API Analytics Charts Usage
2+
include::partial$analytics-eol.adoc[]
23
ifndef::env-site,env-github[]
34
include::_attributes.adoc[]
45
endif::[]

modules/ROOT/pages/analytics-event-api.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
= Reviewing Mule API Analytics Event API
2+
include::partial$analytics-eol.adoc[]
23
ifndef::env-site,env-github[]
34
include::_attributes.adoc[]
45
endif::[]

modules/ROOT/pages/analytics-event-forward.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
= Reviewing Mule API Analytics Event Forwarding
2+
include::partial$analytics-eol.adoc[]
23
ifndef::env-site,env-github[]
34
include::_attributes.adoc[]
45
endif::[]

modules/ROOT/pages/analytics-landing-page.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
= Mule API Analytics
2+
include::partial$analytics-eol.adoc[]
23
ifndef::env-site,env-github[]
34
include::_attributes.adoc[]
45
endif::[]

modules/ROOT/pages/configure-multiple-credential-providers.adoc

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ endif::[]
66

77
You can use multiple client providers, to help you enforce security and regulations in your business organization. These client providers, such as, OpenAM and PingFederate, enable you to secure your operational data, such as client credentials and access tokens.
88

9-
You can use an Anypoint Platform native client provider (default) or configure an external client provider. To assign separate client providers for different organizations and environments, you must first enable client applications to be authorized using OAuth for the client providers that you want to implement in your organization.
9+
You can use an Anypoint Platform native client provider (default), configure an external client provider, or use both the Anypoint Platform native client provider with the external client provider. To assign separate client providers for different organizations and environments, you must first enable client applications to be authorized using OAuth for the client providers that you want to implement in your organization.
1010

1111
API Manager 2.2.14 introduces multiple client identity provider (IdP) support, enabling your environment to use either the default Anypoint Platform native client IdP or one or more external client IdPs.
1212

@@ -55,6 +55,8 @@ To secure your APIs, create one external client provider per environment. Assign
5555

5656
Avoid using the same IdP in production and nonproduction environments. You can use the same IdP in multiple production environments or in multiple nonproduction environments.
5757

58+
If you configure multiple client providers, both the native Anypoint Platform client provider and any external client providers can be used in the same environment.
59+
5860
Before implementing multiple client providers, see the <<guidelines,guidelines>>.
5961

6062
[[guidelines]]
@@ -73,18 +75,13 @@ You can then reassign the appropriate external client provider for that API.
7375
+
7476
** Existing APIs in that environment continue to use the native Anypoint Platform client provider.
7577
** New APIs use the new external IdP.
76-
* You can use either the default native Anypoint Platform client provider or one or more external client providers.
78+
* You can use either the default native Anypoint Platform client provider and one or more external client providers.
7779
+
78-
After you assign an external client provider to an API, you can return to using the default native Anypoint Platform client provider by removing every provider from the environment in which the API belongs.
80+
There is no need to disable an external provider to use the native Anypoint Platform provider.
7981
* If you remove a client provider from an environment, all existing APIs and client applications using that client provider continue to work.
8082
* If you delete a client provider from the root organization, all existing APIs and client applications using that client provider default to the native Anypoint Platform client provider.
8183
+
8284
Even though contracts remain intact, policies that authorize against that provider fail because the configuration is deleted.
83-
* An API created in an environment with an assigned external client provider always uses the external client provider, not the native Anypoint Platform client provider. The following describes one workaround:
84-
+
85-
. Disable the external client provider for that environment.
86-
. Create an API that uses the native Anypoint Platform client provider.
87-
. Re-enable the external client provider.
8885

8986
== Tasks for Implementing Multiple Client Providers Based on Roles
9087

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,9 @@ Before adding additional routes, enter an optional *Route label* for clarity.
6060

6161
You can add additional routes by clicking *Add Route*, and you can delete routes by clicking the *Trash Can* icon (image:trash-can-icon.png[2%,2%]). If only one route is defined, you cannot delete that route.
6262

63+
=== Limits
64+
65+
include::partial$api-manager-limits.adoc[]
6366

6467
==== Route Rules
6568

modules/ROOT/pages/limits.adoc

Lines changed: 32 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,40 @@
22
ifndef::env-site,env-github[]
33
include::_attributes.adoc[]
44
endif::[]
5-
:keywords: api, instance, manager
5+
:keywords: api, instance, manager, limits
6+
7+
== API Group Limits
68

79
API Manager limits the number of features allowed for each business group.
810

9-
== API Group Limits
11+
[%header%autowidth.spread,cols="a,>.<a,a"]
12+
|===
13+
| Limit | Value | Notes
14+
| API Groups per business group
15+
| 1200
16+
|
17+
| API Group Versions per business group
18+
| 1200
19+
|
20+
| API Group Instances per business group
21+
| 2000
22+
|
23+
|===
24+
25+
== Upstream Service Limits
1026

11-
Each business group can have a maximum of:
27+
API Manager limits the number of upstream services you can expose through a single consumer endpoint.
1228

13-
* 1200 API Groups
14-
* 1200 API Group Versions
15-
* 2000 API Group Instances
29+
[%header%autowidth.spread,cols="a,>.<a,a"]
30+
|===
31+
| Limit | Value | Notes
32+
| Upstreams per API
33+
| 50
34+
|
35+
| Routes per API
36+
| 50
37+
|
38+
| Upstreams per route
39+
| 10
40+
|
41+
|===

modules/ROOT/pages/viewing-api-analytics.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
= Reviewing Mule API Analytics Usage
2+
include::partial$analytics-eol.adoc[]
23
ifndef::env-site,env-github[]
34
include::_attributes.adoc[]
45
endif::[]

0 commit comments

Comments
 (0)