Merge branch 'W-13734629-apig-apim-internal-doc-br-bsj' into W-14222043-Cloudhub-2.0-Proxy-KL

Author: glenn-rodgers-sf

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

@@ -96,7 +96,9 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
 * Click **Select API from Exchange** if you have an API shared with you through Exchange that you want to manage.
 [arabic]
 .. Click the API from the list under **Select API**. You can search for a specific API if needed.
-.. Update the *Asset type*, *API version*, and *Asset version* if needed.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
++
+For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
 
 * Click **Create new API**:
@@ -113,7 +115,9 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
 Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
 ** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
 
-.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
++
+For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
 . Click *Next*.
 //end::asset-type-options-flex[]
@@ -131,7 +135,9 @@ Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are
 Upload a WSDL file for your SOAP API or add the link to the file. +
 This option is not available for Flex Gateway runtime at this time.
 
-.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
++
+For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
 . Click *Next*.
 //end::asset-type-options[]
@@ -143,7 +149,9 @@ This option is not available for Flex Gateway runtime at this time.
 +
 NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the exception of the callback feature. To work around this issue, handle the callback outside of the Mule runtime engine domain or use an OAS 3.0 specification that does not use callbacks.
 
-.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
++
+For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
 .. View the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[]
 . Click *Next*.
 //end::raml-oas[]
@@ -152,7 +160,7 @@ NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the ex
 //tag::soap[]
 .. Select **SOAP API** as the **Asset type**.
 .. Select either *Upload a WSDL* or *Use an external link* as the method.
-.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
+.. Update the *Asset type*, *API version*, and *Asset version* if needed.
 . Click *Next*.
 //end::soap[]
 

modules/ROOT/pages/latest-overview-concept.adoc

@@ -66,11 +66,11 @@ The endpoint must have a tracking registration status of *Active* for governance
 +
 ** *API Summary*
 +
-For details, see xref:api-instance-landing-page.adoc[Manage API Instance].
+For details, see xref:api-instance-landing-page.adoc[].
 +
 ** *Alerts*
 +
-For details, see xref:using-api-alerts.adoc[Review Alerts Concepts].
+For details, see xref:using-api-alerts.adoc[].
 ** *Contracts*
 +
 For details, see xref:api-contracts-landing-page.adoc[Client Applications and Contracts].
@@ -79,13 +79,13 @@ For details, see xref:api-contracts-landing-page.adoc[Client Applications and Co
 For details, see xref:policies-landing-page.adoc[Policies].
 ** *SLA Tiers*
 +
-For details, see xref:defining-sla-tiers.adoc[Review SLA Tiers Concepts].
+For details, see xref:defining-sla-tiers.adoc[].
 ** *Settings*
 +
-For details, see xref:edit-api-endpoint-task.adoc[Edit an API Instance].
+For details, see xref:edit-api-endpoint-task.adoc[].
 ** *Governance Report*
 +
-For details, see xref:instance-governance.adoc[Governance Conformance Status].
+For details, see xref:instance-governance.adoc[].
 
 . The percentage of API requests that resulted in errors (in the past 24 hours).
 +

modules/ROOT/pages/manage-versions-instances-concept.adoc

@@ -3,16 +3,16 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-In Anypoint Exchange (Exchange), you can add, delete, and deprecate API versions, also known as _Exchange assets_. An API version in Exchange can have its own RAML file, API portal, and URL. For more information on how to manage API versions in Exchange, see xref:exchange::manage-versions.adoc[Manage Versions].
+After you publish new version details for an API definition to Exchange, you must update the *Asset version* of your deployed API instances in API Manager to reflect the changes.
 
-After you publish new version details for an API definition to Exchange, you must change the version of your API instance in API Manager if you want the instance to reflect the latest version. For more information on API instances, see xref:api-instance-landing-page.adoc[API Instance].
+For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
 
 To change the asset version of an API instance:
 
-. Navigate to *Anypoint Platform* > *API Manager*.
-. In *API Administration*, click the name of the API instance whose version you want to manage.
+. Navigate to *Anypoint Platform* > *API Manager*. 
+. In *API Administration*, click the name of the API instance for which you want to change the version.
 . Select *Actions* > *Change API specification*.
-. In *Asset version*, Select *latest*. 
+. In *Asset version*, select your desired version. 
 . Click *Change*.
 
 == See Also