W-15669357 Testing (Duke): Diffing v4.4 and v4.7 only for

CODEOWNERS

@@ -1,2 +1,2 @@
 #GUSINFO:MS CX Engineering,MS CX (DOCS)
-* @dukesphere @mulesoft/team-docs
+* @dmerlob @mulesoft/team-docs

antora.yml

@@ -4,3 +4,6 @@ version: '4.4'
 display_version: '4.4'
 nav:
 - modules/ROOT/nav.adoc
+asciidoc:
+  attributes:
+    supportStatus: extendedSupportVersion

modules/ROOT/nav.adoc

@@ -1,6 +1,6 @@
-.xref:index.adoc[Mule Overview]
+.xref:index.adoc[Mule Runtime]
 * xref:whats-new-in-mule.adoc[What's New in Mule]
-* xref:index.adoc[Mule Overview]
+* xref:index.adoc[Overview]
 ** xref:mule-components.adoc[Mule Components]
 ** xref:about-flows.adoc[Flows and Subflows]
 ** xref:about-mule-configuration.adoc[Mule Configuration File]

modules/ROOT/pages/_partials/mmp-deploy-to-cloudhub-2.adoc

@@ -87,6 +87,20 @@ From the command line in your project's folder, package the application and exec
 mvn clean deploy -DmuleDeploy
 ----
 
+=== Exchange Snapshot Assets
+
+You can also deploy Exchange snapshot assets into CloudHub 2.0. 
+
+By using `SNAPSHOT` version assets in Anypoint Exchange during the development and testing phase, you can avoid incrementing your application's version number for small changes. After your `SNAPSHOT` version application has been overwritten in Anypoint Exchange, you can redeploy your `SNAPSHOT` version application to CloudHub 2.0 via the Mule Maven plugin to deploy the latest changes.
+
+To learn more about publishing snapshot assets to Anypoint Exchange, see xref:exchange::to-publish-assets-maven.adoc#asset-lifecycle-state[Asset Lifecycle State].
+
+[NOTE]
+====
+Each time you update your application's snapshot, redeploy the application to refresh it with the latest snapshot binaries. 
+Because snapshot assets can change after deployment, avoid deploying them into your production environment.
+====
+
 == Redeploy to CloudHub 2.0
 
 To redeploy the application, run the same command as you did to deploy. +
@@ -126,7 +140,7 @@ Example values: `4.3.0`, `4.2.2-hf4` | Yes
 !===
 .2+! `scopeLoggingConfiguration`
 ! `scope` ! The package of the logging library to use.
-! `logLevel` ! The log level. Accepted values: `NONE`, `ERROR`, `WARN`, `INFO`, `DEBUG`, `TRACE`.
+! `logLevel` ! The log level. Accepted values: `INFO`, `DEBUG`, `WARN`, `ERROR`, `FATAL`.
 !===
 
 Configuration example:
@@ -145,7 +159,7 @@ Configuration example:
 ----
 | No
 | `target` | The CloudHub 2.0 target name to deploy the app to. +
-Specify either a shared space or a private space available in your Deployment Target values in CloudHub 2.0. See xref:cloudhub-2::ch2-features.adoc[Features of CloudHub 2.0] for a detailed description on shared and private spaces. Use a value from the xref:cloudhub-2::ch2-architecture.adoc#regions-and-dns-records[list of regions].| Yes
+Specify either a shared space or a private space available in your Deployment Target values in CloudHub 2.0. See xref:cloudhub-2::ch2-features.adoc[Features of CloudHub 2.0] for a detailed description on shared and private spaces. Use a target name value from the xref:cloudhub-2::ch2-architecture.adoc#regions-and-dns-records[list of regions]. For example, `Cloudhub-US-East-1`. | Yes
 | `provider` | Set to `MC`, for CloudHub 2.0. | Yes
 | `environment` | Target Anypoint Platform environment. +
 This value must match an environment configured in your Anypoint Platform account, as shown here: +
@@ -194,6 +208,8 @@ Configuration example:
 ----
 | No
 
+| `pathRewrite` | Supplies the base path expected by the HTTP listener in your application. This value must begin with `/`. This parameter is used only for applications that are deployed to xref:cloudhub-2::ch2-private-space-about.adoc[private space]. | No
+
 |===
 // end::DeploymentReference[]
 
@@ -204,7 +220,8 @@ Configuration example:
 [%header%autowidth.spread,cols=".^a,.^a"]
 |===
 |Parameter | Description
-| `enforceDeployingReplicasAcrossNodes` | Enforces the deployment of replicas across different nodes. The default value is `false`.
+| `enforceDeployingReplicasAcrossNodes` | Enforces the deployment of replicas across different nodes. The default value is `false`. +
+For high availability, set this value to `true`.
 
 Configuration example:
 [source,xml,linenums]
@@ -250,7 +267,7 @@ Configuration example:
 !===
 .3+! `inbound`
 //  ! `pathRewrite` ! TBC.
-  ! `publicURL` ! URL of the deployed application.
+  ! `publicURL` ! URL of the deployed application. You can add multiple comma-separated values.
   ! `lastMileSecurity` ! Enable Last-Mile security to forward HTTPS connections to be decrypted by this application. This requires an SSL certificate to be included in the Mule application, and also requires more CPU resources. The default value is `false`.
   ! `forwardSslSession` ! Enables SSL forwarding during a session. The default value is `false`.
 !===

modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc

@@ -99,6 +99,20 @@ From the command line in your project's folder, package the application and exec
 mvn clean deploy -DmuleDeploy
 ----
 
+=== Exchange Snapshot Assets
+
+You can also deploy Exchange snapshot assets into Runtime Fabric. 
+
+By using `SNAPSHOT` version assets in Anypoint Exchange during the development and testing phase, you can avoid incrementing your application's version number for small changes. After your `SNAPSHOT` version application has been overwritten in Anypoint Exchange, you can redeploy your `SNAPSHOT` version application to Runtime Fabric via the Mule Maven plugin to deploy the latest changes.
+
+To learn more about publishing snapshot assets to Anypoint Exchange, see xref:exchange::to-publish-assets-maven.adoc#asset-lifecycle-state[Asset Lifecycle State].
+
+[NOTE]
+====
+Each time you update your application's snapshot, redeploy the application to refresh it with the latest snapshot binaries. 
+Because snapshot assets can change after deployment, avoid deploying them into your production environment.
+====
+
 == Redeploy to Runtime Fabric
 
 To redeploy the application, run the same command as you did to deploy. +
@@ -230,6 +244,7 @@ Configuration example:
   If a `reserved` configuration is present, ensure that this value is equal or higher.
 .2+! `memory`
   ! `reserved` ! Specifies the amount of memory to allocate for each application replica. The default value is 700 MB.
+  ! `limit` ! Specifies the maximum memory allocated per application replica. If a `reserved` configuration is present, ensure that this value is equal or higher.
 !===
 Configuration example:
 [source,xml,linenums]
@@ -299,6 +314,8 @@ Configuration example:
 
 | `generateDefaultPublicUrl` | When this parameter is set to true, Runtime Fabric generates a public URL for the deployed application.
 
+| `disableAmLogForwarding` | Disables the application-level log forwarding to Anypoint Monitoring. By default, it is set to `false`.
+
 |===
 // end::rtfDeploymentSettingsReference[]
 

modules/ROOT/pages/_partials/nav-app-dev.adoc

@@ -1,6 +1,6 @@
 * xref:mule-app-dev.adoc[Develop Mule Applications]
-** xref:mule-app-dev-hellomule.adoc[Hello Mule Tutorial]
-** xref:mule-app-tutorial.adoc[Mule App Development Tutorial]
+** xref:mule-app-dev-hellomule.adoc[Tutorial: Create a "Hello World" Mule app]
+** xref:mule-app-tutorial.adoc[Tutorial: Create a Mule app that uses the Database Connector and DataWeave]
 ** xref:about-components.adoc[Core Components]
  *** xref:async-scope-reference.adoc[Async Scope]
  *** xref:batch-processing-concept.adoc[]

modules/ROOT/pages/_partials/upgrade-tool.adoc

@@ -5,6 +5,8 @@
 // tag::BeforeYouBegin[]
 
 * xref:release-notes::mule-upgrade-tool/mule-upgrade-tool.adoc[The latest available version of Mule upgrade tool] so that the tool runs with the latest fixes and security enhancements.
++
+Download the Mule upgrade tool from the https://help.mulesoft.com/s/[Help Center^].
 * A currently operational Mule 4 instance in _stopped_ status to prepare for the upgrade.
 +
 For upgrades of Mule versions between 4.1.1 and 4.1.4 with the Mule upgrade tool, you must upgrade from any patch update released after January 20, 2022. Releases of versions 4.1.1 through 4.1.4 _before_ January 20, 2022 are not supported by the tool, and attempts to upgrade them produce an error message stating that the Mule version cannot be upgraded without first upgrading to a supported version (see xref:release-notes::mule-runtime/upgrade-update-mule.adoc[]).
@@ -15,6 +17,7 @@ The Mule upgrade tool requires the full distribution of the Mule runtime. Ensure
 Download Mule runtime distributions from the https://help.mulesoft.com/s/[Help Center^].
 * At least 2 GB of available disk space on the file system and access privileges to install the new Mule distribution.
 * (For Windows environments) The execution policy for Powershell scripts set to *Unrestricted*.
+* If Anypoint Monitoring agent is installed, uninstall it prior to the upgrade.
 // end::BeforeYouBegin[]
 
 // Upgrade Or Update Mule

modules/ROOT/pages/about-classloading-isolation.adoc

@@ -124,7 +124,7 @@ All dependencies (JAR files, for example) declared in the application's `pom.xml
 
 Consider an application that uses Anypoint Connector for Java, and the connector needs to use a class that is part of a JAR dependency declared in the application's `pom.xml` file. However, this is not possible, because the connector's class loader is not able to find that class. To make this class visible to the connector, you must declare the dependency that contains the class as a shared library in the Mule Maven plugin configuration of your application's `pom.xml` file.
 
-If you use Anypoint Studio or Flow Designer to configure a connector that uses external libraries, the dependencies are automatically added as shared libraries. For example, if you add Anypoint Connector for Database to your application and then configure the connection driver using Anypoint Studio, the driver is automatically added as a shared library in your project's `pom.xml` file.
+If you use Anypoint Studio to configure a connector that uses external libraries, the dependencies are automatically added as shared libraries. For example, if you add Anypoint Connector for Database to your application and then configure the connection driver using Anypoint Studio, the driver is automatically added as a shared library in your project's `pom.xml` file.
 
 See xref:mmp-concept.adoc#configure-shared-libraries[Configure Shared Libraries] for configuration instructions.
 

modules/ROOT/pages/about-components.adoc

@@ -8,21 +8,12 @@ building blocks of flows in a Mule app. Core components provide the logic
 for processing a Mule event as it travels in a series of linked steps through
 the app. Examples include the Scheduler, For Each, and Logger components.
 
-* In Studio, Mule components are accessible by clicking *Core* from the Mule palette.
+In Studio, Mule components are accessible by clicking *Core* from the Mule palette.
 +
 image::components-core-studio.png[Core Components in Studio]
 +
 Notice that the components are subdivided into types, including Batch,
 Error Handling, and Flow Control.
-+
-* In Design Center, when you are building a Mule app, you can find Mule
-components listed among *Modules* in the *Select a Component* dialog.
-+
-image::components-core-fd.png[Core Components in Design Center]
-+
-Design Center provides many of the Core components described below. Though the
-Design Center UI does not subdivide components into the types you see in the
-Studio UI, it can help to conceptualize them by those types.
 
 == Batch
 
@@ -55,7 +46,7 @@ data to a new output structure or format.
 
 == Endpoints
 
-Endpoints (sometimes called Sources in Studio or Triggers in Design Center) include 
+Endpoints (sometimes called Sources in Studio) include 
 components that initiate (or trigger) processing in a Mule flow. The 
 xref:scheduler-concept.adoc[Scheduler] is an endpoint. It triggers a flow to start 
 at a configurable interval.

modules/ROOT/pages/about-flows.adoc

@@ -12,7 +12,7 @@ An app can consist of a single flow, or it can break up processing into
 discrete flows and subflows that you add to the app and connect together. Mule
 apps in production environments typically use multiple flows and subflows
 to divide the app into functional modules or for
-<<error_handling, error-handling>> purposes. For example, one flow might
+<<error_handling, error handling>> purposes. For example, one flow might
 receive a record and transform data into a given format that another
 flow processes in some special way.
 
@@ -51,6 +51,7 @@ Because the contents of a subflow replace each Flow Reference component that ref
 
 For example, configuring a batch job inside a subflow causes the application to fail during deployment if the subflow is referenced from more than one Flow Reference component. The application fails to deploy because multiple instances of a batch job with the same job instance ID exist, which is not allowed.
 
+[[error_handling]]
 == Error Handling
 
 Each flow (but not subflow) can have its own error handling. One reason for

modules/ROOT/pages/about-mule-configuration.adoc

@@ -23,8 +23,8 @@ Global settings, such as the default transaction time-out, that apply to the ent
 Configuration Properties, message properties, and system properties.
 * xref:about-flows.adoc[Flows] +
 Combine components to define a message flow.
-* xref:about-components#_endpoints[Sources (Endpoints or Triggers)] +
-Trigger a flow. Sources are sometimes called Endpoints in Studio and Triggers in Flow Designer.
+* xref:about-components#_endpoints[Sources (Endpoints)] +
+Trigger a flow. Sources are sometimes called Endpoints in Studio.
 * xref:connectors::index.adoc[Connectors and Modules Configurations] +
 Declare configurations for any connectors and modules components used.
 * xref:about-components.adoc#_flow_control_routers[Routers] +

modules/ROOT/pages/build-application-from-api.adoc

@@ -76,7 +76,7 @@ Use this method if you want to start a project by either importing an existing R
 . In *API Implementation*, select *Specify API Definition File Location or URL*.
 . In *Location*, do one of the following:
 * If you created an `api.raml` file in Design Center, select *Design Center* . Login to Anypoint Platform if necessary, and select `api.raml`.
-* If you didn’t create a RAML file in Design Center, select *Browse Files* and select the RAML or WSDL file that you created in a text editor. For a WSDL file, select a service and port from the drop-down menus or accept the defaults.
+* If you didn't create a RAML file in Design Center, select *Browse Files* and select the RAML or WSDL file that you created in a text editor. For a WSDL file, select a service and port from the drop-down menus or accept the defaults.
 
 [start=6]
 . Accept the Location default options, and click *Finish*.

modules/ROOT/pages/business-events.adoc

@@ -40,5 +40,5 @@ This practice makes analysis and debugging easier and more intuitive at runtime.
 
 * xref:about-mule-event.adoc[Mule Events]
 * xref:transaction-management.adoc[Transaction Management]
-* xref:business-events-in-components[Configure Default Events Tracking]
+* xref:business-events-in-components.adoc[Configure Default Events Tracking]
 * xref:business-events-custom.adoc[Custom Business Event Component]

modules/ROOT/pages/choosing-the-right-clustering-topology.adoc

@@ -4,7 +4,7 @@ include::_attributes.adoc[]
 endif::[]
 :keywords: deploy, cloudhub, on premises, on premise, clusters
 
-You can deploy Mule in many different topologies. As you build your Mule application, it is important to think critically about how best to architect your application to achieve the desired availability, fault tolerance, and performance characteristics. This page outlines some of the solutions for achieving the right blend of these characteristics through clustering. There is no one correct approach for everyone, and designing your system is both an art and a science. If you need more assistance, MuleSoft Professional Services can help you by reviewing your architecture plan or designing it for you. For more information, http://www.mulesoft.com/contact[contact us].
+You can deploy Mule in many different topologies. As you build your Mule application, it is important to think critically about how best to architect your application to achieve the desired availability, fault tolerance, and performance characteristics. This page outlines some of the solutions for achieving the right blend of these characteristics through clustering when you deploy applications on premises. There is no one correct approach for everyone, and designing your system is both an art and a science. If you need more assistance, MuleSoft Professional Services can help you by reviewing your architecture plan or designing it for you. For more information, http://www.mulesoft.com/contact[contact us].
 
 == About Clustering
 

modules/ROOT/pages/consume-data-from-an-api.adoc

@@ -79,7 +79,7 @@ POST, PUT, and DELETE requests almost always require headers.
 * URI and Query Parameters
 * Error handling
 
-See xref:connectors::http-connector[HTTP Connector documentation] for more information about how to configure the request operation.
+See xref:http-connector::index.adoc#input-sources[HTTP Connector documentation] for more information about how to configure the request operation.
 
 
 === Consume REST API Example

modules/ROOT/pages/creating-and-managing-a-cluster-manually.adoc

@@ -4,7 +4,7 @@ include::_attributes.adoc[]
 endif::[]
 :keywords: cluster, deploy
 
-This page describes manual creation and configuration of a cluster. There are two ways to create and manage clusters:
+There are two ways to create and manage clusters for on-premises deployments:
 
 * Using Runtime Manager
 +
@@ -16,7 +16,12 @@ See xref:runtime-manager::cluster-about.adoc[Clusters] for configuration instruc
 * Do not mix cluster management tools.
 +
 Manual cluster configuration is not synced to Anypoint Runtime Manager, so any change you make in the platform overrides the cluster configuration files. To avoid this scenario, use only one method for creating and managing your clusters: either manual configuration or configuration using Anypoint Runtime Manager.
-* All nodes in a cluster must have the same Mule runtime engine and Runtime Manager agent version. If you are using a cumulative patch release, such as 4.3.0-20210322, all instances of Mule must be the same cumulative patch version.
+* All nodes in a cluster must have the same versions of:
+** Mule runtime engine
++
+If you are using a cumulative patch release, such as 4.3.0-20210322, all instances of Mule must be the same cumulative patch version.
+** Runtime Manager agent version
+** Java
 
 == Creating a Cluster Manually
 
@@ -87,6 +92,11 @@ Quorum feature is only valid for components that use Object Store.
 
 === Object Store Persistence
 
+[NOTE]
+--
+Ensure you set up a centralized JDBC store for the cluster object store persistence. Otherwise, shutting down all cluster nodes causes the content of object stores to be lost, no matter if the persistent setting is enabled on the object store configuration.
+--
+
 You can persistently store JDBC data in a central system that is accessible by all cluster nodes when using Mule runtime engine on-premises.
 
 The following relational database systems are supported:

modules/ROOT/pages/cryptography-jce.adoc

@@ -210,7 +210,7 @@ For example, you can set Content to `#[payload.name]` to decrypt only an encrypt
 | Streaming Strategy a| * <<repeatable-in-memory-stream>>
 * <<repeatable-file-store-stream>>
 * non-repeatable-stream |  +++Configure if repeatable streams should be used and their behavior+++ |  | {nbsp}
-| Cipher a| String |  A raw cipher string in the form "algorithm/mode/padding" according to the Java crypto documentation, for example `AES/CBC/PKCS5Padding`. Note that not all combinations are valid. |  | {nbsp}
+| Cipher a| String |  A raw cipher string in the form "algorithm/mode/padding" according to the Java crypto documentation, for example `AES/CBC/PKCS5Padding`. Note that GCM mode is currently not supported, and not all algorithm/mode/padding combinations are valid. |  | {nbsp}
 | Algorithm a| Enumeration, one of:
 
 ** `AES`
@@ -273,7 +273,7 @@ For example, you can set Content to `#[payload.name]` to encrypt only a variable
 | Streaming Strategy a| * <<repeatable-in-memory-stream>>
 * <<repeatable-file-store-stream>>
 * non-repeatable-stream |  +++Configure if repeatable streams should be used and their behavior+++ |  | {nbsp}
-| Cipher a| String | A raw cipher string in the form "algorithm/mode/padding" according to the Java crypto documentation, for example `AES/CBC/PKCS5Padding`. Note that not all combinations are valid. |  | {nbsp}
+| Cipher a| String | A raw cipher string in the form "algorithm/mode/padding" according to the Java crypto documentation, for example `AES/CBC/PKCS5Padding`. Note that GCM mode is currently not supported, and not all algorithm/mode/padding combinations are valid. |  | {nbsp}
 | Algorithm a| Enumeration, one of:
 
 ** `AES`