Merge pull request #499 from mulesoft/apim-flex-gateway-v1-4-gr

Apim flex gateway v1 4 gr

Author: glenn-rodgers-sf

modules/ROOT/nav.adoc

@@ -50,6 +50,7 @@
  ** xref:enable-https-mule3-proxies.adoc[Enable HTTPS in Mule 3.x API Proxies]
   ** 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]

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

@@ -47,7 +47,7 @@ to manage your API.
 .. Enter a *Proxy app name*.
 
 * **Runtime Fabric:** Select Runtime Fabric if you want to deploy API Proxies to a Mule runtime engine that is managed on Runtime Fabric.
-See xref:runtime-fabric::proxy-deploy-runtime-fabric[Deploying API Proxies to Runtime Fabric] for more information.
+See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies to Runtime Fabric] for more information.
 .. Select a target from the list.
 .. Select the **Runtime version**.
 .. Enter a *Proxy app name*.
@@ -147,6 +147,10 @@ If you upload an OAS API specification to an API proxy version 1.0 or earlier, y
 . If you plan to have xref:building-https-proxy.adoc[HTTPS] communications, specify a TLS Context.
 . Click *Next*.
 //end::tls[]
+//tag::configure-endpoint[]
+. xref:api-manager::configure-api-task.adoc[Configure the endpoint].
+. Click *Next*.
+//end::configure-endpoint[]
 //tag::last-steps-heading[]
 
 [[review_save_and_deploy]]

modules/ROOT/pages/add-api-alert-task.adoc

@@ -1,19 +1,22 @@
-= Add API Alerts
+= Add API Alerts for Mule Gateway or Service Mesh
 ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-To track and manage APIs, you can add one or more API alerts to your API instances. Add different xref:using-api-alerts.adoc[types of alerts] based on your requirements.
+To track and manage APIs, you can add one or more API alerts to your API instances. Add different xref:using-api-alerts.adoc[types of alerts] based on your requirements. 
 
-[NOTE]
-====
-Alerts cannot be added to API instances protected by xref:automated-policies-landing-page.adoc[automated policies].
-====
+For APIs using Mule Gateway or Service Mesh as their runtime, follow the steps in this tutorial to add alerts to your APIs. 
+
+You cannot add Policy Violation alerts to xref:automated-policies-landing-page.adoc[automated policies].
+
+NOTE: This tutorial is for Mule Gateway and Service Mesh runtimes. To add alerts to APIs using Flex Gateway as their runtime, see xref:gateway::flex-use-api-alerts.adoc[Add API Alerts for Flex Gateway].
 
-To add an API alert:
+[[mule-gateway]]
+== 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 pane, select *Alerts* > *Add alert*.
+. 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*.
 . Specify the alert options:
 * *Name*: 
 +
@@ -28,16 +31,21 @@ You can delete an alert anytime if not required.
 Select a severity for the alert, for example, *Info*.
 * *Alert type*: 
 +
-Select the type of alert to create, (for example, *Request Count*) and provide appropriate alert configuration values.
+Select the type of alert to create, (for example, *Request Count*) and provide appropriate alert configuration values. For information about alert types, see xref:using-api-alerts.adoc#api-alerts[API Alerts].
 +
 [TIP]
 ====
 In the *For at least* and *consecutive period(s) of* fields, enter a value in the range of 1 - 999999999 to specify the time interval as a https://www.techopedia.com/definition/869/sliding-window[sliding window^].
 ====
 
 . Select *Recipients*.
-. Select *Create Alert*.
++
+Specify what emails receive the email notification.
+
+. Click *Create Alert*.
+
 
 == See Also
 
 * xref:using-api-alerts.adoc[Review Alerts Concepts]
+* xref:gateway::flex-use-api-alerts.adoc[Add API Alerts for Flex Gateway]

modules/ROOT/pages/configure-api-task.adoc

@@ -14,11 +14,13 @@ Not all options are available depending on the runtime as well as the API.
 | *API 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.
 | *Implementation URI* | The URL to access for the proxy or the API. It must end with a /. | Yes|  For example, you can use the URL of your API asset in Exchange. 
 | *Consumer endpoint* | Specifies a proxy application's address for consumers to use for sending requests.| No |
-| *Proxy version* | Specifies the version of the proxy to use for the endpoint.| No |
 | *Base path* | Specifies the URL prefix for all API paths, relative to the host root. It must start with a leading slash /. | No | 
-| **Advanced Options** |  |  |
 | *Scheme* | Specifies whether to use HTTP or HTTPS. | Yes | If you select HTTPS, specify a TLS context for inbound traffic.
+| *TLS Context for inbound traffic* | Specifies the TLS Context used for the inbound traffic of HTTPS APIs. | No | xref:gateway::flex-conn-tls-config.adoc[Configure a TLS Context for Flex Gateway] before adding a TLS Context to your API.
 | *Port* | Specifies the number to use if the displayed port is incorrect. | No | Port can be shared between API instances over the same Target as long as the Base paths are different. Only available on Flex 1.2.0+.
+| *Client provider* | Specifies a client provider for the API. | No | 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]. 
+| **Advanced Options** |  |  |
+| *TLS Context for outbound traffic* | Specifies the TLS Context used for the outbound traffic. | No | xref:gateway::flex-conn-tls-config.adoc[Configure a TLS Context for Flex Gateway] before adding a TLS Context to your API.
 |===
 
 == Configure an API Instance on Service Mesh Options

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

@@ -14,17 +14,17 @@ the sandbox environment, and you want to promote it to the current or production
 * *Import API from zip file:* Select this option if you have exported an API Instance from a different Anypoint Platform
 instance.
 
-When you are promoting or importing an API Instance, you will not have options to alter the configuration. However,
-when you add a new API Instance, you will need to configure the endpoint as well as other settings.
+When you are promoting or importing an API Instance, you do not have options to alter the configuration. However,
+when you add a new API Instance, you need to xref:configure-api-task.adoc[configure the endpoint] as well as other settings.
 
 == Add a New API
 
 . Log in to Anypoint Platform.
 . In the navigation bar or the Anypoint Platform page, click *API Manager*.
 . Click *Add API* and select *Add new API*.
 . Select and configure your runtime from the following options:
-Flex Gateway:: Select Flex Gateway for any APIs that need a flexible, performant API gateway
-that will work with distributed and microservices environments and fit into your CI/CD environments.
+Flex Gateway:: Select Flex Gateway for any APIs that need a flexible and performant API gateway
+that works with distributed and microservices environments and fits into your CI/CD environments.
 +
 Choose the connected Flex Gateway you have installed and registered from the list under *Select a gateway*.
 +
@@ -52,11 +52,11 @@ include::partial$task-configure-proxy.adoc[tags=target-type-bullet;target-type]
 Service Mesh:: Select Service Mesh to extend Anypoint Platform API Management capabilities to your
 Istio service mesh through the deployment of a Mule Adapter.
 +
-NOTE: After adding the API on Anypoint Platform, you will need to bind it to a service using the Anypoint Service Mesh client. See xref:service-mesh::configure-service-mesh.adoc#methods-for-configuring-anypoint-service-mesh[Methods for Configuring Anypoint Service Mesh] for more information.
+NOTE: After adding the API on Anypoint Platform, you need to bind it to a service using the Anypoint Service Mesh client. See xref:service-mesh::configure-service-mesh.adoc#methods-for-configuring-anypoint-service-mesh[Methods for Configuring Anypoint Service Mesh] for more information.
 +
 . Click *Next*.
 +
-include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;configure-endpoint;last-steps,leveloffset=+2]
 
 
 == Promote API from Environment

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

@@ -3,9 +3,9 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-You manage Anypoint DataGraph in API Manager. The DataGraph Administration page for a particular environment appears only after you have added at least one API schema to that environment's unified schema.
+You manage Anypoint DataGraph in API Manager. The DataGraph Administration page for a given environment appears only after you have added at least one API schema to that environment's unified schema.
 
-As an Anypoint DataGraph administrator:
+Both Anypoint DataGraph administrators and contributors can:
 
 * Use the xref:datagraph-settings.adoc[Anypoint DataGraph Administration settings] to select environments, view and edit the GraphQL endpoint of a unified schema, configure policies, and configure client providers.
 

modules/ROOT/pages/manage-policies-overview.adoc

@@ -0,0 +1,54 @@
+= Gateway Policies in API Manager
+ifndef::env-site,env-github[]
+include::_attributes.adoc[]
+endif::[]
+:imagesdir: ../assets/images
+:page-aliases: 
+
+From API Manager, you can apply policies to APIs in Flex Gateway Connected Mode or in Mule Gateway.
+
+Policies enable you to enforce regulations to help manage security, control traffic, and improve adaptability of your APIs. For example, a policy can control authentication, access, allotted consumption, and service level access (SLA).
+
+With policies, you can implement these regulations with no modification to the code implementation. 
+
+Because the policies are implemented by the Gateway, policies are documented in the xref:gateway-home::gateway-overview.adoc[Gateway documentation]. For more information, see the xref:policies::policies-overview.adoc[Policy documentation] or use the links in the following sections.
+
+== Policies Included in Flex Gateway and Mule Gateway
+
+* xref:policies::policies-included-directory.adoc[Included Policies Directory]
+
+== Applying Policies in Flex Gateway Connected Mode and in Mule Gateway
+
+* xref:policies::policies-included-apply.adoc[Apply an Included Policy]
+
+== See Also
+
+* xref:policies::policies-included-reorder.adoc[]
+* xref:policies::policies-policy-categories.adoc[Policy Categories]
+* xref:policies::policies-compare-versions.adoc[Comparison of Mule 3 and Mule 4 Policies]
+* xref:policies::policies-flex-dataweave-support.adoc[DataWeave Support in Flex Gateway Policies]
+* xref:policies::policies-automated-overview.adoc[Automated Policies]
+* xref:policies::policies-resource-level-overview.adoc[Resource-Level Policies]
+* xref:policies::policies-custom-overview.adoc[Custom Policies]
+
+
+
+// You can apply policies to any HTTP-based APIs, such as:
+
+// An APIkit project
+
+// For example, deploy the APIkit project to Anypoint Platform using API Autodiscovery, and then apply a policy.
+
+// An API running on CloudHub
+
+// Design an API on Anypoint Platform, configure a proxy for Cloudhub, and apply a policy.
+
+// An API running on Anypoint Runtime Fabric
+
+// Design an API on Anypoint Platform, configure a proxy for Runtime Fabric, and apply a policy.
+
+// An API deployed to a private or cloud-based Mule runtime engine (Mule) 3.8.x or later
+
+// You can apply a policy to any API implemented in Anypoint Platform, as long as the API is exposed through an HTTP listener. You can also apply a policy to APIs not implemented in Anypoint Platform by deploying a proxy application to control how and when a received request is forwarded to its implementation endpoint. Anypoint API Manager supports RAML, HTTP, or SOAP-based proxies.
+
+// When applying a policy with SLA, you can set an API alert to notify you when an API request violates that policy. By default, a policy applies to the entire API, filtering traffic requests to every resource and method. You can configure this to provide resource-level granularity if needed.