Merge branch 'v2.x' into W-12976976-CH2-deployment-location-gr

Author: glenn-rodgers-sf

modules/ROOT/assets/image-source-files/api-instance-summary.graffle

@@ -1,5 +1,6 @@
 .xref:index.adoc[API Manager]
 * xref:latest-overview-concept.adoc[Anypoint API Manager]
+* xref:api-manager-release-notes.adoc[Release Notes]
 * xref:getting-started-proxy.adoc[Get Started with Managing an API]
 * xref:api-instance-landing-page.adoc[Manage API Instances]
  ** xref:create-instance-task.adoc[Add an API Instance]
@@ -8,6 +9,7 @@
  ** 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]
+ ** xref:edit-api-endpoint-task.adoc[Edit an API Instance Endpoint]
  ** xref:deprecate-api-latest-task.adoc[Deprecate an API Instance]
  ** xref:delete-api-task.adoc[Delete an API Instance]
  ** xref:manage-versions-instances-concept.adoc[Manage API Versions and Instances]
@@ -31,6 +33,7 @@
  ** xref:hash-client-credentials.adoc[Configure Credential Hashing for Mule 4]
  ** xref:migrate-client-apps.adoc[Migrate Client Applications]
  ** xref:datagraph-viewing-application-contracts.adoc[View Client Applications with Anypoint Datagraph Contracts]
+ ** xref:manage-client-apps-connected-apps-concept.adoc[Create Client Applications with Connected Apps]
 * xref:environments-concept.adoc[Manage Environments]
  ** xref:switch-environment-task.adoc[Switch Environments]
  ** xref:environment-permission-task.adoc[Grant Permission to Access an Environment]
@@ -51,11 +54,11 @@
   ** xref:proxy-mule3-elements.adoc[Filter Mule Headers in Mule 3.x API Proxies]
  ** xref:proxy-domain-support.adoc[Automatic Domain Support for Mule 4 API Proxies]
 * xref:manage-policies-overview.adoc[Policies]
-* xref:analytics-landing-page.adoc[View Analytics]
- ** xref:viewing-api-analytics.adoc[Review Analytics Usage]
- ** xref:analytics-chart.adoc[Review Analytics Charts Usage]
- ** xref:analytics-event-api.adoc[Review Analytics Event API]
- ** xref:analytics-event-forward.adoc[Review Analytics Event Forwarding]
+* xref:analytics-landing-page.adoc[View Mule API Analytics]
+ ** xref:viewing-api-analytics.adoc[Review Mule API Analytics Usage]
+ ** xref:analytics-chart.adoc[Review Mule API Analytics Charts Usage]
+ ** xref:analytics-event-api.adoc[Review Mule API Analytics Event API]
+ ** xref:analytics-event-forward.adoc[Review Mule API Analytics Event Forwarding]
 * xref:mule-oauth-provider-landing-page.adoc[Mule OAuth 2.0 Provider]
  ** xref:about-configure-api-for-oauth.adoc[OAuth 2.0 Policy Prerequisites]
  ** xref:external-oauth-2.0-token-validation-policy.adoc[OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider]

modules/ROOT/assets/image-source-files/connected-app-client-apps.graffle

@@ -12,7 +12,8 @@
 [[select_proxy_type]]
 = Select a Proxy Type
 
-. In API Manager, click *Add API* and select *Add new API*.
+. Navigate to *Anypoint Platform* > *API Manager*. 
+. In *API Administration*, click *Add API* and select *Add new API*.
 . Select *Mule Gateway* as your runtime.
 . Select *Deploy a proxy application* for *Proxy type*.
 //end::first-steps[]
@@ -168,7 +169,7 @@ If you upload an OAS API specification to an API proxy version 1.0 or earlier, y
 //tag::last-steps[]
 
 . Review your selections and edit them if necessary.
-. If you are ready to deploy, click **Save & Deploy**. Otherwise, you can select **Save**, to save the API Instance
+. If you are ready to deploy, click **Save & Deploy**. Otherwise, you can select **Save**, to save the API instance
 and deploy it at a later time.
 +
 // end::last-steps[]

modules/ROOT/assets/images/api-instance-summary.png

@@ -11,12 +11,12 @@ You must have the Organization Administrator privileges of the root organization
 
 To obtain the credentials of a client application:
 
-. From the left navigation pane in Anypoint Platform, click *Management Center* > *API Manager*.
-. On the left navigation in API Manager, click *Client Applications*.
+. Go to *Anypoint Platform* > *API Manager*.
+. Click *Client Applications*.
 . From the details pane, click the application for which you want to view the client credentials.
 +
-The client ID and client secret credentials for the selected application appear on the right of the window. 
-. Alternatively, if you need to obtain only the client ID of the registered client application, select the correct version of the API and click *Contracts* from the left navigation. 
+The client ID and client secret credentials for the selected application appear in the window. 
+. Alternatively, if you need to obtain only the client ID of the registered client application, select the correct version of the API and click *Contracts*. 
 +
 As an Application Owner, if you do not have access to API Manager, you can view the xref:exchange::about-my-applications.adoc[application credentials] in Exchange.
 . To view the details, click the specific API contract. 

modules/ROOT/assets/images/connected-app-client-apps.png

@@ -14,10 +14,9 @@ Before you access an asset portal, ensure that you meet one of the following con
 
 To access an asset portal:
 
-. Log in to Anypoint Platform.
-. In the navigation bar or the Anypoint Platform page, click *API Manager*.
-. On the API Administration dashboard, click the API instance name that you want to access.
-. From the top-right corner on the API instance page, click *View API in Exchange*.
+. Navigate to *Anypoint Platform* > *API Manager*.
+. In *API Administration*, click the name of the API instance that you want to access.
+. Click *Actions* and select *View API in Exchange*.
 +
 The portal for the selected asset is displayed in an Exchange window. You can also share and make the xref:exchange::about-portals.adoc[portal public] in Anypoint Exchange.
 

modules/ROOT/nav.adoc

@@ -15,8 +15,9 @@ NOTE: This tutorial is for Mule Gateway and Service Mesh runtimes. To add alerts
 == Add API Alerts for Mule Gateway or Service Mesh
 To add an API alert to a Mule Gateway or Service Mesh API:
 
-. Navigate to *API Manager > API Administration* and click the API instance for which you want to add an alert.
-. From the left navigation panel, click *Alerts > Add alert*.
+. Navigate to *Anypoint Platform* > *API Manager*.
+. In *API Administration*, click the API instance to which to add an alert.
+. Click *Alerts* > *Add alert*.
 . Specify the alert options:
 * *Name*: 
 +

modules/ROOT/pages/_partials/task-configure-proxy.adoc

@@ -1,15 +1,15 @@
-= Reviewing API Manager Analytics Charts Usage
+= Reviewing API Manager Mule API Analytics Charts Usage
 ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-API Analytics provides a summary in chart form of requests, top apps, and latency for 1 hour, 3 hours, 1 day, 7 days, or 1 month. This data is available for 30 days. To view the Analytics chart, in API Manager, click the instance name of a deployed API.
+Mule API Analytics provides a summary in chart form of requests, top apps, and latency for 1 hour, 3 hours, 1 day, 7 days, or 1 month. This data is available for 30 days. To view the Mule API Analytics chart, in API Manager, click the instance name of a deployed API.
 
-*Note:* To view Analytics charts, users need View APIs Configuration permission. See xref:environment-permission-task.adoc[To Set Permissions].
+*Note:* To view Mule API Analytics charts, users need `View APIs Configuration` permission. See xref:environment-permission-task.adoc[To Set Permissions].
 
 == Reviewing Requests Summary Chart
 
-The requests summary chart lists the total number of requests to your API by the duration you choose. The chart shows the HTTP status codes specified by W3C. For example:
+The requests summary chart lists the total number of requests to your API instance by the duration you choose. The chart shows the HTTP status codes specified by W3C. For example:
 
 image::request-analytics.png["Summary chart of the total number of requests for June 1, 2017, shown by one hour duration."]
 
@@ -21,7 +21,7 @@ Graph lines are provided for:
 
 == Reviewing Top Apps Summary Chart
 
-The top apps summary chart lists the number of requests made to the API by each application for the top 5 applications calling that API. Each color represents one of the top 5 applications accessing the API. The y-axis plots the number of calls made to the API.
+The top apps summary chart lists the number of requests made to the API instance by each application for the top 5 applications calling that API instance. Each color represents one of the top 5 applications accessing the API. The y-axis plots the number of calls made to the API instance.
 
 The graph lists the number of requests over the duration you select, for example:
 
@@ -37,9 +37,9 @@ image::performance-analytics.png["A latency summary chart showing the average la
 
 == Including Policy Violations in Charts
 
-*Note:* Users must have the View Policies permission set to view policies or edit a Policy Violation alert.
+*Note:* Users must have the `View Policies` permission set to view policies or edit a Policy Violation alert.
 
-Enable or disable the tracking of policy violations by checking the Include Policy Violations checkbox on an Analytics chart screen. The chart shows traffic rejected, or not rejected, by a policy.
+Enable or disable the tracking of policy violations by checking the Include Policy Violations checkbox on an Mule API Analytics chart screen. The chart shows traffic rejected, or not rejected, by a policy.
 
 image::policy-violations-dashboard.png["An analytics chart screen with the Include Policy Violations checkbox indicated with a callout."]