diff --git a/modules/ROOT/pages/add-another-output-transform-studio-task.adoc b/modules/ROOT/pages/add-another-output-transform-studio-task.adoc index 0032eb4f..5c0284fa 100644 --- a/modules/ROOT/pages/add-another-output-transform-studio-task.adoc +++ b/modules/ROOT/pages/add-another-output-transform-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::add-another-output-transform-studio-task.adoc +:page-aliases: 6.x@studio::add-another-output-transform-studio-task.adoc A single Transform Message component can give shape to several different parts of the output (example: the payload, a flow variable, a property). Each different output part must be defined in a separate DataWeave code, written out in a separate tab of the Transform pane. For example: if one tab defines the payload, and another an outbound property, these are both parts of the same output Mule message. diff --git a/modules/ROOT/pages/adding-community-runtime.adoc b/modules/ROOT/pages/adding-community-runtime.adoc index 1bacdce7..f4bf3955 100644 --- a/modules/ROOT/pages/adding-community-runtime.adoc +++ b/modules/ROOT/pages/adding-community-runtime.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::adding-community-runtime.adoc +:page-aliases: 6.x@studio::adding-community-runtime.adoc :keywords: installing, community runtime, enterprise, ee, ce, open source *Anypoint Studio* comes bundled with an embedded Enterprise runtime with a 30-day Enterprise trial license. You can install newer or earlier versions of the Mule runtime, whether Enterprise or Community versions. diff --git a/modules/ROOT/pages/adding-source-attachments-to-studio.adoc b/modules/ROOT/pages/adding-source-attachments-to-studio.adoc index a64f6554..146bca19 100644 --- a/modules/ROOT/pages/adding-source-attachments-to-studio.adoc +++ b/modules/ROOT/pages/adding-source-attachments-to-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::adding-source-attachments-to-studio.adoc +:page-aliases: 6.x@studio::adding-source-attachments-to-studio.adoc :keywords: debug, source code, source files, importing sources, debugging, troubleshooting, source, stack trace Often when troubleshooting applications you may stumble upon the need to step through third party code, which often lacks source files. This is no different in Anypoint Studio regarding code living inside Mule in any of its flavors. This document will walk you through how this applies to Studio and how it works. diff --git a/modules/ROOT/pages/anypoint-studio-features.adoc b/modules/ROOT/pages/anypoint-studio-features.adoc index 4ddff9b2..e36dfeee 100644 --- a/modules/ROOT/pages/anypoint-studio-features.adoc +++ b/modules/ROOT/pages/anypoint-studio-features.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::anypoint-studio-features.adoc +:page-aliases: 6.x@studio::anypoint-studio-features.adoc :keywords: anypoint, studio, eclipse, visual editor, XML editor Anypoint Studio, MuleSoft's Eclipse-based integration development environment, offers a wealth of features for building, debugging and testing Mule applications and more. diff --git a/modules/ROOT/pages/api-sync-reference.adoc b/modules/ROOT/pages/api-sync-reference.adoc index c82f35ff..eedf4e6b 100644 --- a/modules/ROOT/pages/api-sync-reference.adoc +++ b/modules/ROOT/pages/api-sync-reference.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::api-sync-reference.adoc +:page-aliases: 6.x@studio::api-sync-reference.adoc :keywords: api, anypoint platform, sync, api sync In API Sync View, you pull, push, and compare your API definition in Anypoint Studio and xref:1.x@api-manager::designing-your-api.adoc[API Designer]. diff --git a/modules/ROOT/pages/basic-studio-tutorial.adoc b/modules/ROOT/pages/basic-studio-tutorial.adoc index 73dad659..4d5b438b 100644 --- a/modules/ROOT/pages/basic-studio-tutorial.adoc +++ b/modules/ROOT/pages/basic-studio-tutorial.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::basic-studio-tutorial.adoc +:page-aliases: 6.x@studio::basic-studio-tutorial.adoc :keywords: studio, tutorial, request, response, http, listener, config Walk through this tutorial to learn how to use Anypoint Studio to build a simple HTTP request-response application. diff --git a/modules/ROOT/pages/building-a-mapping-flow-in-the-graphical-mapping-editor.adoc b/modules/ROOT/pages/building-a-mapping-flow-in-the-graphical-mapping-editor.adoc index 7a69e0e9..27620933 100644 --- a/modules/ROOT/pages/building-a-mapping-flow-in-the-graphical-mapping-editor.adoc +++ b/modules/ROOT/pages/building-a-mapping-flow-in-the-graphical-mapping-editor.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::building-a-mapping-flow-in-the-graphical-mapping-editor.adoc +:page-aliases: 6.x@studio::building-a-mapping-flow-in-the-graphical-mapping-editor.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/building-a-mule-application-with-maven-in-studio.adoc b/modules/ROOT/pages/building-a-mule-application-with-maven-in-studio.adoc index 5411d523..f601cbce 100644 --- a/modules/ROOT/pages/building-a-mule-application-with-maven-in-studio.adoc +++ b/modules/ROOT/pages/building-a-mule-application-with-maven-in-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::building-a-mule-application-with-maven-in-studio.adoc +:page-aliases: 6.x@studio::building-a-mule-application-with-maven-in-studio.adoc :keywords: connectors, anypoint, studio, maven This guide walks you through creating a Mavenized Mule Application project from scratch. It covers providing the project with unit tests, maintaining its POM file, then building and deploying the project. diff --git a/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc b/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc index e31fbdbb..a9d1ab63 100644 --- a/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc +++ b/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::change-target-output-transformation-studio-task.adoc +:page-aliases: 6.x@studio::change-target-output-transformation-studio-task.adoc By default, the Transform Message component outputs to the message payload. You can change this target, so that the result of your transformation populates another part of the output such as a property or variable. diff --git a/modules/ROOT/pages/changing-runtimes-in-studio.adoc b/modules/ROOT/pages/changing-runtimes-in-studio.adoc index 97d8354f..cc597cb8 100644 --- a/modules/ROOT/pages/changing-runtimes-in-studio.adoc +++ b/modules/ROOT/pages/changing-runtimes-in-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::changing-runtimes-in-studio.adoc +:page-aliases: 6.x@studio::changing-runtimes-in-studio.adoc :keywords: runtimes, community edition, enterprise edition, anypoint, studio, deploy When creating a new Mule Project, Studio prompts you to select a runtime; this decision is not irreversible, as the project runtime can be modified at any time. For example, you may want to change a project's runtime to take advantage of improvements that are added to new versions of Mule. Keep in mind, however, that some runtimes may be only deployable to CloudHub, and some require an Enterprise license. diff --git a/modules/ROOT/pages/choosing-mel-or-ctl2-as-scripting-engine.adoc b/modules/ROOT/pages/choosing-mel-or-ctl2-as-scripting-engine.adoc index 73bfdd9e..dd846f11 100644 --- a/modules/ROOT/pages/choosing-mel-or-ctl2-as-scripting-engine.adoc +++ b/modules/ROOT/pages/choosing-mel-or-ctl2-as-scripting-engine.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::choosing-mel-or-ctl2-as-scripting-engine.adoc +:page-aliases: 6.x@studio::choosing-mel-or-ctl2-as-scripting-engine.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-concepts.adoc b/modules/ROOT/pages/datamapper-concepts.adoc index 7fb88ee8..a2ac84ee 100644 --- a/modules/ROOT/pages/datamapper-concepts.adoc +++ b/modules/ROOT/pages/datamapper-concepts.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-concepts.adoc +:page-aliases: 6.x@studio::datamapper-concepts.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-examples.adoc b/modules/ROOT/pages/datamapper-examples.adoc index c5874734..cf17131d 100644 --- a/modules/ROOT/pages/datamapper-examples.adoc +++ b/modules/ROOT/pages/datamapper-examples.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-examples.adoc +:page-aliases: 6.x@studio::datamapper-examples.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-fixed-width-input-format.adoc b/modules/ROOT/pages/datamapper-fixed-width-input-format.adoc index 27cc5e9c..628a835a 100644 --- a/modules/ROOT/pages/datamapper-fixed-width-input-format.adoc +++ b/modules/ROOT/pages/datamapper-fixed-width-input-format.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-fixed-width-input-format.adoc +:page-aliases: 6.x@studio::datamapper-fixed-width-input-format.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc b/modules/ROOT/pages/datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc index b19766aa..a7620196 100644 --- a/modules/ROOT/pages/datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc +++ b/modules/ROOT/pages/datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc +:page-aliases: 6.x@studio::datamapper-flat-to-structured-and-structured-to-flat-mapping.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-input-error-policy-for-bad-input-data.adoc b/modules/ROOT/pages/datamapper-input-error-policy-for-bad-input-data.adoc index fade62e5..5966439a 100644 --- a/modules/ROOT/pages/datamapper-input-error-policy-for-bad-input-data.adoc +++ b/modules/ROOT/pages/datamapper-input-error-policy-for-bad-input-data.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-input-error-policy-for-bad-input-data.adoc +:page-aliases: 6.x@studio::datamapper-input-error-policy-for-bad-input-data.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-supplemental-topics.adoc b/modules/ROOT/pages/datamapper-supplemental-topics.adoc index 5329765d..e8f208ba 100644 --- a/modules/ROOT/pages/datamapper-supplemental-topics.adoc +++ b/modules/ROOT/pages/datamapper-supplemental-topics.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-supplemental-topics.adoc +:page-aliases: 6.x@studio::datamapper-supplemental-topics.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datamapper-user-guide-and-reference.adoc b/modules/ROOT/pages/datamapper-user-guide-and-reference.adoc index b116d09b..8da1dbc2 100644 --- a/modules/ROOT/pages/datamapper-user-guide-and-reference.adoc +++ b/modules/ROOT/pages/datamapper-user-guide-and-reference.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-user-guide-and-reference.adoc +:page-aliases: 6.x@studio::datamapper-user-guide-and-reference.adoc :keywords: datamapper *_Enterprise, CloudHub_* diff --git a/modules/ROOT/pages/datamapper-visual-reference.adoc b/modules/ROOT/pages/datamapper-visual-reference.adoc index 6434be97..29a640cf 100644 --- a/modules/ROOT/pages/datamapper-visual-reference.adoc +++ b/modules/ROOT/pages/datamapper-visual-reference.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datamapper-visual-reference.adoc +:page-aliases: 6.x@studio::datamapper-visual-reference.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/datasense-enabled-connectors.adoc b/modules/ROOT/pages/datasense-enabled-connectors.adoc index 50ee3113..4580b80e 100644 --- a/modules/ROOT/pages/datasense-enabled-connectors.adoc +++ b/modules/ROOT/pages/datasense-enabled-connectors.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datasense-enabled-connectors.adoc +:page-aliases: 6.x@studio::datasense-enabled-connectors.adoc [cols="2*"] |=== diff --git a/modules/ROOT/pages/datasense-query-editor.adoc b/modules/ROOT/pages/datasense-query-editor.adoc index 3a324fa8..f2cd7652 100644 --- a/modules/ROOT/pages/datasense-query-editor.adoc +++ b/modules/ROOT/pages/datasense-query-editor.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datasense-query-editor.adoc +:page-aliases: 6.x@studio::datasense-query-editor.adoc :keywords: anypoint studio, datasense, metadata, meta data, query metadata, dsql, data sense query language The *Query Editor* in Studio allows you to query and retrieve complex data structures that you can use when designing your application. Using xref:datasense.adoc[DataSense] on an Anypoint Connector which supports query functionality, the Query Editor can automatically acquire metadata from remote application, discovering which data types and fields are available to query. The Query Editor displays the available data types and fields in a graphical menu. You select the ones you want to query. diff --git a/modules/ROOT/pages/datasense-query-language.adoc b/modules/ROOT/pages/datasense-query-language.adoc index 626fd2fc..ab9cb184 100644 --- a/modules/ROOT/pages/datasense-query-language.adoc +++ b/modules/ROOT/pages/datasense-query-language.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datasense-query-language.adoc +:page-aliases: 6.x@studio::datasense-query-language.adoc :keywords: anypoint studio, esb, datasense, metadata, meta data, query metadata, dsql, data sense query language In Anypoint Connectors which support the query functionality, the xref:datasense-query-editor.adoc[DataSense Query Editor] allows you to easily query and retrieve complex data stored in a remote application. To define your query, you can proceed in one of two ways: diff --git a/modules/ROOT/pages/datasense.adoc b/modules/ROOT/pages/datasense.adoc index 3cb6f5b6..52619194 100644 --- a/modules/ROOT/pages/datasense.adoc +++ b/modules/ROOT/pages/datasense.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::datasense.adoc +:page-aliases: 6.x@studio::datasense.adoc :keywords: anypoint studio, datasense, metadata, meta data, query metadata, dsql, data sense query language *DataSense* uses message metadata to facilitate application design. With this functionality, Anypoint Studio proactively acquires information such as data type and structure, in order to prescribe how to accurately map or use this data in your application. diff --git a/modules/ROOT/pages/defining-datamapper-input-and-output-metadata.adoc b/modules/ROOT/pages/defining-datamapper-input-and-output-metadata.adoc index cf475129..c3124f1a 100644 --- a/modules/ROOT/pages/defining-datamapper-input-and-output-metadata.adoc +++ b/modules/ROOT/pages/defining-datamapper-input-and-output-metadata.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::defining-datamapper-input-and-output-metadata.adoc +:page-aliases: 6.x@studio::defining-datamapper-input-and-output-metadata.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/defining-metadata-using-edit-fields.adoc b/modules/ROOT/pages/defining-metadata-using-edit-fields.adoc index e3f3394a..37794b69 100644 --- a/modules/ROOT/pages/defining-metadata-using-edit-fields.adoc +++ b/modules/ROOT/pages/defining-metadata-using-edit-fields.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::defining-metadata-using-edit-fields.adoc +:page-aliases: 6.x@studio::defining-metadata-using-edit-fields.adoc :keywords: anypoint studio, datasense, metadata, meta data, query metadata, dsql, data sense query language When defining or updating input and output metadata for the different data types supported by Anypoint DataMapper, you use one of several very similar editors to create the structure and define fields, elements and attributes. Any of these editors is opened by selecting *Edit Structure*. diff --git a/modules/ROOT/pages/defining-metadata.adoc b/modules/ROOT/pages/defining-metadata.adoc index a8dcef07..7bdcb3ee 100644 --- a/modules/ROOT/pages/defining-metadata.adoc +++ b/modules/ROOT/pages/defining-metadata.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::defining-metadata.adoc +:page-aliases: 6.x@studio::defining-metadata.adoc :keywords: studio, anypoint, esb, transform, transformer, format, aggregate, rename, split, filter convert, xml, json, csv, pojo, java object, metadata, dataweave, data weave, datamapper, dwl, dfl, dw, output structure, input structure, map, mapping == Overview diff --git a/modules/ROOT/pages/deploy-more-than-one-application.adoc b/modules/ROOT/pages/deploy-more-than-one-application.adoc index 6921d2f3..f3e734f2 100644 --- a/modules/ROOT/pages/deploy-more-than-one-application.adoc +++ b/modules/ROOT/pages/deploy-more-than-one-application.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::deploy-more-than-one-application.adoc +:page-aliases: 6.x@studio::deploy-more-than-one-application.adoc :keywords: deploy studio parallel deployment Anypoint Studio allows you to deploy more than one application into the same Mule instance through xref:3.8@mule-runtime::application-deployment.adoc#deploying-applications-in-parallel[parallel deployment]. diff --git a/modules/ROOT/pages/enabling-maven-support-for-a-studio-project.adoc b/modules/ROOT/pages/enabling-maven-support-for-a-studio-project.adoc index dc506d91..86abdfc7 100644 --- a/modules/ROOT/pages/enabling-maven-support-for-a-studio-project.adoc +++ b/modules/ROOT/pages/enabling-maven-support-for-a-studio-project.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::enabling-maven-support-for-a-studio-project.adoc +:page-aliases: 6.x@studio::enabling-maven-support-for-a-studio-project.adoc :keywords: anypoint studio, maven You may wish to take a Mule project that was already created in Anypoint Studio and add http://maven.apache.org/[Maven] functionality to it. Maven can make your project more easily shareable with other developers as it takes care of its dependencies and helps automate your project's build process. diff --git a/modules/ROOT/pages/exchange-integration.adoc b/modules/ROOT/pages/exchange-integration.adoc index 3bb46a0a..33fbdd4e 100644 --- a/modules/ROOT/pages/exchange-integration.adoc +++ b/modules/ROOT/pages/exchange-integration.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::exchange-integration.adoc +:page-aliases: 6.x@studio::exchange-integration.adoc Anypoint Studio 6.4 allows you to connect to Exchange 2.0 to publish your project as a new asset. diff --git a/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc b/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc index 233f1a10..8b2450e4 100644 --- a/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc +++ b/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::graphically-construct-mapping-studio-task.adoc +:page-aliases: 6.x@studio::graphically-construct-mapping-studio-task.adoc Through the graphical UI of the Transform Message component you can do the tasks below. When doing each, the necessary lines are added to the DataWeave code to describe the action. diff --git a/modules/ROOT/pages/hardware-and-software-requirements.adoc b/modules/ROOT/pages/hardware-and-software-requirements.adoc index 3c1293d1..bb8090c3 100644 --- a/modules/ROOT/pages/hardware-and-software-requirements.adoc +++ b/modules/ROOT/pages/hardware-and-software-requirements.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::hardware-and-software-requirements.adoc +:page-aliases: 6.x@studio::hardware-and-software-requirements.adoc :keywords: mule, requirements, os, jdk, installation, jre This page lists the hardware, operating systems, Java, and other requirements for running MuleSoft products. diff --git a/modules/ROOT/pages/import-api-def-dc.adoc b/modules/ROOT/pages/import-api-def-dc.adoc index e3c7b0cd..bec3fb1f 100644 --- a/modules/ROOT/pages/import-api-def-dc.adoc +++ b/modules/ROOT/pages/import-api-def-dc.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::import-api-def-dc.adoc +:page-aliases: 6.x@studio::import-api-def-dc.adoc Anypoint Studio 6.3 and later allow you to import an API Definition from Design Center and implement it either into a new Mule Project, or an existing one. diff --git a/modules/ROOT/pages/import-asset-exchange-task.adoc b/modules/ROOT/pages/import-asset-exchange-task.adoc index 9427a8bd..32731860 100644 --- a/modules/ROOT/pages/import-asset-exchange-task.adoc +++ b/modules/ROOT/pages/import-asset-exchange-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::import-asset-exchange-task.adoc +:page-aliases: 6.x@studio::import-asset-exchange-task.adoc . Click the Exchange icon in the Studio taskbar image:exchange-integration-adc09.png[]. . Click Log In on the top right corner of your screen and provide your Anypoint Platform credentials. diff --git a/modules/ROOT/pages/importing-a-maven-project-into-studio.adoc b/modules/ROOT/pages/importing-a-maven-project-into-studio.adoc index 45ece040..3042a8f3 100644 --- a/modules/ROOT/pages/importing-a-maven-project-into-studio.adoc +++ b/modules/ROOT/pages/importing-a-maven-project-into-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::importing-a-maven-project-into-studio.adoc +:page-aliases: 6.x@studio::importing-a-maven-project-into-studio.adoc :keywords: anypoint studio, maven, import maven If you have a Mule project that was built using https://maven.apache.org/[Maven] outside Anypoint Studio, you can still import it into Studio and continue to work on it with the benefits of the Studio IDE. diff --git a/modules/ROOT/pages/importing-and-exporting-in-studio.adoc b/modules/ROOT/pages/importing-and-exporting-in-studio.adoc index 7d78d19e..83342705 100644 --- a/modules/ROOT/pages/importing-and-exporting-in-studio.adoc +++ b/modules/ROOT/pages/importing-and-exporting-in-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::importing-and-exporting-in-studio.adoc +:page-aliases: 6.x@studio::importing-and-exporting-in-studio.adoc :keywords: anypoint studio, import project, export project, share project, download project Anypoint Studio supports the ability to import and export your projects or various project elements. The sections that follow outline the procedures to import or export information pertaining to your Studio projects. Because Studio is Eclipse-based, keep in mind that among the import/export options, there are way to import or export projects that are not tailored for Mule projects, and which are not recommended for use. diff --git a/modules/ROOT/pages/including-the-datamapper-plugin.adoc b/modules/ROOT/pages/including-the-datamapper-plugin.adoc index 32a074cc..a8fecc87 100644 --- a/modules/ROOT/pages/including-the-datamapper-plugin.adoc +++ b/modules/ROOT/pages/including-the-datamapper-plugin.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::including-the-datamapper-plugin.adoc +:page-aliases: 6.x@studio::including-the-datamapper-plugin.adoc :keywords: datamapper, migration DataMapper is deprecated as of Mule runtime 3.7.0 and superseded by the xref:transform-message-component-concept-studio.adoc[Transform Message Component]. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 4537e6af..68dc8f65 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::index.adoc +:page-aliases: 6.x@studio::index.adoc :keywords: studio, IDE, development, eclipse, anypoint, visual editor, XML editor Anypoint Studio is MuleSoft's Eclipse-based integration development environment for designing and testing Mule applications. You can deploy the application and run it on your Mule server. diff --git a/modules/ROOT/pages/input-output-structure-transformation-studio-task.adoc b/modules/ROOT/pages/input-output-structure-transformation-studio-task.adoc index 49702b34..c6492cbf 100644 --- a/modules/ROOT/pages/input-output-structure-transformation-studio-task.adoc +++ b/modules/ROOT/pages/input-output-structure-transformation-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::input-output-structure-transformation-studio-task.adoc +:page-aliases: 6.x@studio::input-output-structure-transformation-studio-task.adoc To use the graphical view and construct mappings via drag and drop, the Transform Message component first needs information about what fields are available for dragging and dropping onto. diff --git a/modules/ROOT/pages/install-studio-gw.adoc b/modules/ROOT/pages/install-studio-gw.adoc index 84616071..ff1569a5 100644 --- a/modules/ROOT/pages/install-studio-gw.adoc +++ b/modules/ROOT/pages/install-studio-gw.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::install-studio-gw.adoc +:page-aliases: 6.x@studio::install-studio-gw.adoc :keywords: gateway, studio To develop an API using Anypoint Studio 6.0 for deployment to Anypoint Platform, you no longer need to install and configure API Gateway Runtime because Anypoint Studio with Mule 3.8.0 Runtime includes all of the API Gateway Runtime capabilities. diff --git a/modules/ROOT/pages/installing-extensions.adoc b/modules/ROOT/pages/installing-extensions.adoc index 86f9c9c6..73eb5dc4 100644 --- a/modules/ROOT/pages/installing-extensions.adoc +++ b/modules/ROOT/pages/installing-extensions.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::installing-extensions.adoc +:page-aliases: 6.x@studio::installing-extensions.adoc :keywords: mule, esb, studio, extensions, install extensions, extend, download new software Beyond the out-of-the-box functionality included in the Studio and Mule distributions, various *plugins*, *modules*, *connectors*, and *runtimes for Studio* are made available by download. diff --git a/modules/ROOT/pages/keyboard-shortcuts-in-studio.adoc b/modules/ROOT/pages/keyboard-shortcuts-in-studio.adoc index 23c24114..2e85ea2c 100644 --- a/modules/ROOT/pages/keyboard-shortcuts-in-studio.adoc +++ b/modules/ROOT/pages/keyboard-shortcuts-in-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::keyboard-shortcuts-in-studio.adoc +:page-aliases: 6.x@studio::keyboard-shortcuts-in-studio.adoc :keywords: studio, shortcuts, hot keys To help you be more efficient when using Anypoint Studio, there are a series of keyboard shortcuts you can use any time you're in the application to trigger specific actions. diff --git a/modules/ROOT/pages/mapping-elements-inside-lists.adoc b/modules/ROOT/pages/mapping-elements-inside-lists.adoc index 256e4539..f8d8115e 100644 --- a/modules/ROOT/pages/mapping-elements-inside-lists.adoc +++ b/modules/ROOT/pages/mapping-elements-inside-lists.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::mapping-elements-inside-lists.adoc +:page-aliases: 6.x@studio::mapping-elements-inside-lists.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/mapping-flow-input-and-output-properties.adoc b/modules/ROOT/pages/mapping-flow-input-and-output-properties.adoc index 0852181e..f638c91b 100644 --- a/modules/ROOT/pages/mapping-flow-input-and-output-properties.adoc +++ b/modules/ROOT/pages/mapping-flow-input-and-output-properties.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::mapping-flow-input-and-output-properties.adoc +:page-aliases: 6.x@studio::mapping-flow-input-and-output-properties.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/maven-support-in-anypoint-studio.adoc b/modules/ROOT/pages/maven-support-in-anypoint-studio.adoc index 9ec8d625..366b3352 100644 --- a/modules/ROOT/pages/maven-support-in-anypoint-studio.adoc +++ b/modules/ROOT/pages/maven-support-in-anypoint-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::maven-support-in-anypoint-studio.adoc +:page-aliases: 6.x@studio::maven-support-in-anypoint-studio.adoc :keywords: studio, maven, esb, version control, dependencies, libraries The following sections describe how to enable or disable Maven support for your projects in Anypoint Studio. diff --git a/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc b/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc index cc1b8741..067b5222 100644 --- a/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc +++ b/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::move-transformations-separate-file-studio-task.adoc +:page-aliases: 6.x@studio::move-transformations-separate-file-studio-task.adoc By default, the DataWeave code from a Transform Message component is expressed inline within your Mule XML file. You can instead keep each in a separate file ( `.dwl` ) and have your XML reference them. These files are packaged with your Mule application when built. diff --git a/modules/ROOT/pages/pojo-class-bindings-and-factory-classes.adoc b/modules/ROOT/pages/pojo-class-bindings-and-factory-classes.adoc index 5190281a..e17be5c7 100644 --- a/modules/ROOT/pages/pojo-class-bindings-and-factory-classes.adoc +++ b/modules/ROOT/pages/pojo-class-bindings-and-factory-classes.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::pojo-class-bindings-and-factory-classes.adoc +:page-aliases: 6.x@studio::pojo-class-bindings-and-factory-classes.adoc :keywords: anypoint studio, esb, java classes, java bindings, factory classes Anypoint DataMapper allows you to map an interface or abstract class as a POJO. *Binding*, in this case, refers to linking your POJO (which can be an interface or abstract class) to a concrete class. Thus, when instantiating your POJO, Mule uses the concrete class you specified. diff --git a/modules/ROOT/pages/preparing-a-gitignore-file.adoc b/modules/ROOT/pages/preparing-a-gitignore-file.adoc index 370f9bd2..e5356c3e 100644 --- a/modules/ROOT/pages/preparing-a-gitignore-file.adoc +++ b/modules/ROOT/pages/preparing-a-gitignore-file.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::preparing-a-gitignore-file.adoc, using-subversion-with-studio.adoc +:page-aliases: 6.x@studio::preparing-a-gitignore-file.adoc, using-subversion-with-studio.adoc :keywords: anypoint studio, esb, git, github, gitignore, versioning [NOTE] diff --git a/modules/ROOT/pages/preview-transformation-output-studio-task.adoc b/modules/ROOT/pages/preview-transformation-output-studio-task.adoc index 6b6659a6..b2d68efc 100644 --- a/modules/ROOT/pages/preview-transformation-output-studio-task.adoc +++ b/modules/ROOT/pages/preview-transformation-output-studio-task.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::preview-transformation-output-studio-task.adoc +:page-aliases: 6.x@studio::preview-transformation-output-studio-task.adoc You can provide sample input data to your Transform Message component to see how the transformation affects it. You don't need to deploy your project to use this feature. A sample output is updated in real time as you make changes both to the sample input and the transformation. diff --git a/modules/ROOT/pages/previewing-datamapper-results-on-sample-data.adoc b/modules/ROOT/pages/previewing-datamapper-results-on-sample-data.adoc index 0e952f47..b8af5d09 100644 --- a/modules/ROOT/pages/previewing-datamapper-results-on-sample-data.adoc +++ b/modules/ROOT/pages/previewing-datamapper-results-on-sample-data.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::previewing-datamapper-results-on-sample-data.adoc +:page-aliases: 6.x@studio::previewing-datamapper-results-on-sample-data.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/raml-1-0-data-types-support.adoc b/modules/ROOT/pages/raml-1-0-data-types-support.adoc index 69ff1373..8861bc4e 100644 --- a/modules/ROOT/pages/raml-1-0-data-types-support.adoc +++ b/modules/ROOT/pages/raml-1-0-data-types-support.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::raml-1-0-data-types-support.adoc +:page-aliases: 6.x@studio::raml-1-0-data-types-support.adoc Datasense now supports https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#raml-data-types[RAML 1.0 data types], and can parse this information to be displayed in the xref:using-the-datasense-explorer.adoc[DataSense explorer]. diff --git a/modules/ROOT/pages/setting-up-your-development-environment.adoc b/modules/ROOT/pages/setting-up-your-development-environment.adoc index be7f5e49..1bb04afb 100644 --- a/modules/ROOT/pages/setting-up-your-development-environment.adoc +++ b/modules/ROOT/pages/setting-up-your-development-environment.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::setting-up-your-development-environment.adoc +:page-aliases: 6.x@studio::setting-up-your-development-environment.adoc Setting up a proper development environment is crucial for a successful use of the Mule Runtime. + The following document outlines the steps to be taken before any significant use of Anypoint Studio, Mule, and our Cloud Solutions. diff --git a/modules/ROOT/pages/starting-the-runtime-in-cluster-mode-in-studio.adoc b/modules/ROOT/pages/starting-the-runtime-in-cluster-mode-in-studio.adoc index 816f6989..9974d468 100644 --- a/modules/ROOT/pages/starting-the-runtime-in-cluster-mode-in-studio.adoc +++ b/modules/ROOT/pages/starting-the-runtime-in-cluster-mode-in-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::starting-the-runtime-in-cluster-mode-in-studio.adoc +:page-aliases: 6.x@studio::starting-the-runtime-in-cluster-mode-in-studio.adoc :keywords: mule, deploy, launch, run, anypoint studio, cluster Anypoint Studio allows you to specify that the Mule runtime should start in cluster mode for specific applications. Running an application with this setting enabled causes it to run as if it were on a one-node cluster. This allows you to test for any discrepancies in the application's behavior between the clustered and the standalone modes. diff --git a/modules/ROOT/pages/streaming-data-processing-with-datamapper.adoc b/modules/ROOT/pages/streaming-data-processing-with-datamapper.adoc index 0d4f5c14..9a6465b0 100644 --- a/modules/ROOT/pages/streaming-data-processing-with-datamapper.adoc +++ b/modules/ROOT/pages/streaming-data-processing-with-datamapper.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::streaming-data-processing-with-datamapper.adoc +:page-aliases: 6.x@studio::streaming-data-processing-with-datamapper.adoc :keywords: datamapper Especially useful when working with large datasets, Anypoint DataMapper supports streaming data input and output. For example, when reading information from a very large input file, you can use streaming you avoid having DataMapper load the whole file into memory. Instead, DataMapper works as a pipeline: it sequentially reads the file and store the data in a cache, performs data mapping, sends the output to the next transformer, empties the cache, then begins again. Using this procedure, DataMapper can parse a 500 MB CSV file using only about 75 MB of RAM, resulting in significant improvements in performance and resources utilization. diff --git a/modules/ROOT/pages/studio-in-eclipse.adoc b/modules/ROOT/pages/studio-in-eclipse.adoc index c045ee42..ef174d23 100644 --- a/modules/ROOT/pages/studio-in-eclipse.adoc +++ b/modules/ROOT/pages/studio-in-eclipse.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::studio-in-eclipse.adoc +:page-aliases: 6.x@studio::studio-in-eclipse.adoc :keywords: mule, esb, anypoint studio, studio, eclipse plug-in As an Eclipse-based IDE, Anypoint Studio has adopted many of the functionalities Eclipse has to offer. However, you don't need to download a new IDE in order to take advantages of all that Studio provides. If you are already an Eclipse user, you can simply download and install *Studio as an Eclipse plug-in*. diff --git a/modules/ROOT/pages/studio-policy-editor.adoc b/modules/ROOT/pages/studio-policy-editor.adoc index 9dd54196..d936d4dd 100644 --- a/modules/ROOT/pages/studio-policy-editor.adoc +++ b/modules/ROOT/pages/studio-policy-editor.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::studio-policy-editor.adoc +:page-aliases: 6.x@studio::studio-policy-editor.adoc Studio 6.1 (and newer versions of 6.x) grants you the ability to create a *policy project*, under which you can group your *custom API policies* and apply them to your local Studio deployments. This way, you can compose, debug, and test custom API policies within Studio, using an editor that fully supports and validates custom API policies design. diff --git a/modules/ROOT/pages/studio-update-sites.adoc b/modules/ROOT/pages/studio-update-sites.adoc index 3df41f41..dd2aa87a 100644 --- a/modules/ROOT/pages/studio-update-sites.adoc +++ b/modules/ROOT/pages/studio-update-sites.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::studio-update-sites.adoc +:page-aliases: 6.x@studio::studio-update-sites.adoc :keywords: mule, esb, studio, anypoint studio, update sites, updates, extensions, plug-ins, plugins, download Update sites in Anypoint Studio are used to update or install Studio, Mule, connectors or other useful development tools. See how to access and find update sites from Studio. diff --git a/modules/ROOT/pages/studio-visual-debugger.adoc b/modules/ROOT/pages/studio-visual-debugger.adoc index d05c9013..45a6ab89 100644 --- a/modules/ROOT/pages/studio-visual-debugger.adoc +++ b/modules/ROOT/pages/studio-visual-debugger.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::studio-visual-debugger.adoc +:page-aliases: 6.x@studio::studio-visual-debugger.adoc :keywords: mule, esb, studio, anypoint studio, debug, debugger, break points, breakpoints Studio *Visual Debugger* allows you to run your application in Debug mode, stopping execution to check the contents of a message at previously-specified building blocks. diff --git a/modules/ROOT/pages/testing-connections.adoc b/modules/ROOT/pages/testing-connections.adoc index 90d37135..d244aa84 100644 --- a/modules/ROOT/pages/testing-connections.adoc +++ b/modules/ROOT/pages/testing-connections.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::testing-connections.adoc +:page-aliases: 6.x@studio::testing-connections.adoc This functionality enables you to test connections to external resources. As you model your application in Studio, you have the opportunity, when configuring connectors, to test the functionality of its connection to a Web service. diff --git a/modules/ROOT/pages/tips-transform-message-ui-studio.adoc b/modules/ROOT/pages/tips-transform-message-ui-studio.adoc index 5b109bed..c9e92a9e 100644 --- a/modules/ROOT/pages/tips-transform-message-ui-studio.adoc +++ b/modules/ROOT/pages/tips-transform-message-ui-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::tips-transform-message-ui-studio.adoc +:page-aliases: 6.x@studio::tips-transform-message-ui-studio.adoc * Before creating your mapping, configure everything else on the flow so that the input and output is known. diff --git a/modules/ROOT/pages/to-download-and-install-studio-lx.adoc b/modules/ROOT/pages/to-download-and-install-studio-lx.adoc index ec2f4a1d..640f0311 100644 --- a/modules/ROOT/pages/to-download-and-install-studio-lx.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio-lx.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::to-download-and-install-studio-lx.adoc +:page-aliases: 6.x@studio::to-download-and-install-studio-lx.adoc == Prerequisites diff --git a/modules/ROOT/pages/to-download-and-install-studio-ox.adoc b/modules/ROOT/pages/to-download-and-install-studio-ox.adoc index dbee4fcd..29ec90ae 100644 --- a/modules/ROOT/pages/to-download-and-install-studio-ox.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio-ox.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::to-download-and-install-studio-ox.adoc +:page-aliases: 6.x@studio::to-download-and-install-studio-ox.adoc == Prerequisites diff --git a/modules/ROOT/pages/to-download-and-install-studio-wx.adoc b/modules/ROOT/pages/to-download-and-install-studio-wx.adoc index 5d718485..e8735b7f 100644 --- a/modules/ROOT/pages/to-download-and-install-studio-wx.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio-wx.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::to-download-and-install-studio-wx.adoc, jdk-requirement-lnx-workflow.adoc, jdk-requirement-wx-workflow.adoc, jdk-requirement-xos-workflow.adoc, studio-configure-vm-task-lnx.adoc, studio-configure-vm-task-unx.adoc, studio-configure-vm-task-wx.adoc, faq-jdk-requirement.adoc +:page-aliases: 6.x@studio::to-download-and-install-studio-wx.adoc, jdk-requirement-lnx-workflow.adoc, jdk-requirement-wx-workflow.adoc, jdk-requirement-xos-workflow.adoc, studio-configure-vm-task-lnx.adoc, studio-configure-vm-task-unx.adoc, studio-configure-vm-task-wx.adoc, faq-jdk-requirement.adoc == Prerequisites diff --git a/modules/ROOT/pages/to-download-and-install-studio.adoc b/modules/ROOT/pages/to-download-and-install-studio.adoc index dfdace54..6aace81a 100644 --- a/modules/ROOT/pages/to-download-and-install-studio.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::to-download-and-install-studio.adoc, download-and-launch-anypoint-studio.adoc +:page-aliases: 6.x@studio::to-download-and-install-studio.adoc, download-and-launch-anypoint-studio.adoc To download and install Anypoint Studio, follow the instructions based on your operating system: diff --git a/modules/ROOT/pages/transform-message-component-concept-studio.adoc b/modules/ROOT/pages/transform-message-component-concept-studio.adoc index 1640fd84..38b24a73 100644 --- a/modules/ROOT/pages/transform-message-component-concept-studio.adoc +++ b/modules/ROOT/pages/transform-message-component-concept-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::transform-message-component-concept-studio.adoc +:page-aliases: 6.x@studio::transform-message-component-concept-studio.adoc :keywords: studio, anypoint, esb, transform, transformer, format, aggregate, rename, split, filter convert, xml, json, csv, pojo, java object, metadata, dataweave, data weave, datamapper, dwl, dfl, dw, output structure, input structure, map, mapping The Transform Message component carries out transformations over the input data it receives. You can explicitly write out a transformation in DataWeave language, or you can use the UI to build it implicitly through dragging and dropping elements. diff --git a/modules/ROOT/pages/troubleshooting-studio.adoc b/modules/ROOT/pages/troubleshooting-studio.adoc index 40826fef..d83556f5 100644 --- a/modules/ROOT/pages/troubleshooting-studio.adoc +++ b/modules/ROOT/pages/troubleshooting-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::troubleshooting-studio.adoc +:page-aliases: 6.x@studio::troubleshooting-studio.adoc Anypoint Studio uses your system's default layout engine to render content in its Web UI. + If you are experiencing issues visualizing web content such as the Runtime Manager UI when deploying an application to Anypoint Platform, or Exchange when browsing assets for your project, you need to configure Anypoint Studio to use a *Mozilla/XULRunner* runtime environment as its underlying renderer for the Web UI. diff --git a/modules/ROOT/pages/updating-metadata-in-an-existing-mapping.adoc b/modules/ROOT/pages/updating-metadata-in-an-existing-mapping.adoc index e906e3e8..fc9293fc 100644 --- a/modules/ROOT/pages/updating-metadata-in-an-existing-mapping.adoc +++ b/modules/ROOT/pages/updating-metadata-in-an-existing-mapping.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::updating-metadata-in-an-existing-mapping.adoc +:page-aliases: 6.x@studio::updating-metadata-in-an-existing-mapping.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/using-datamapper-lookup-tables.adoc b/modules/ROOT/pages/using-datamapper-lookup-tables.adoc index 6d6053b8..34967d31 100644 --- a/modules/ROOT/pages/using-datamapper-lookup-tables.adoc +++ b/modules/ROOT/pages/using-datamapper-lookup-tables.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::using-datamapper-lookup-tables.adoc +:page-aliases: 6.x@studio::using-datamapper-lookup-tables.adoc :keywords: datamapper [NOTE] diff --git a/modules/ROOT/pages/using-maven-in-anypoint-studio.adoc b/modules/ROOT/pages/using-maven-in-anypoint-studio.adoc index b237f8c3..f35bf040 100644 --- a/modules/ROOT/pages/using-maven-in-anypoint-studio.adoc +++ b/modules/ROOT/pages/using-maven-in-anypoint-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::using-maven-in-anypoint-studio.adoc +:page-aliases: 6.x@studio::using-maven-in-anypoint-studio.adoc :keywords: studio, maven, esb, version control, dependencies, libraries The pages in this section describe Maven integration with Anypoint Studio, including building applications, importing Maven projects or "mavenizing" existing projects. diff --git a/modules/ROOT/pages/using-perceptive-flow-design.adoc b/modules/ROOT/pages/using-perceptive-flow-design.adoc index 19b332a6..a4a546bd 100644 --- a/modules/ROOT/pages/using-perceptive-flow-design.adoc +++ b/modules/ROOT/pages/using-perceptive-flow-design.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::using-perceptive-flow-design.adoc +:page-aliases: 6.x@studio::using-perceptive-flow-design.adoc :keywords: datamapper Building upon the certainty that connection testing establishes, Mule takes one more step to make designing your application easier with *Perceptive Flow Design*. If you model a flow to include an Anypoint Connector, preceded or followed by a xref:3.8@mule-runtime::dataweave.adoc[Transform Message component], Mule uses the working connection to the resource to retrieve metadata about message payload and properties. Capturing the data type and structure that a resource employs, Mule feeds that data into the xref:3.8@mule-runtime::dataweave.adoc[Transform Message component] thereby informing the component of the expected input or output. This functionality facilitates mapping of data from one data format and structure to another. diff --git a/modules/ROOT/pages/using-the-datasense-explorer.adoc b/modules/ROOT/pages/using-the-datasense-explorer.adoc index d658dfd2..995fee9f 100644 --- a/modules/ROOT/pages/using-the-datasense-explorer.adoc +++ b/modules/ROOT/pages/using-the-datasense-explorer.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::using-the-datasense-explorer.adoc +:page-aliases: 6.x@studio::using-the-datasense-explorer.adoc :keywords: anypoint studio, studio, mule esb, datasense, metadata, meta data Anypoint Studio includes a *DataSense Explorer* that surfaces information about the Mule message as it passes through your flow. The DataSense explorer lists information about the message payload, flow variables, session variables, inbound properties, and outbound properties of your message, relative to the building block you currently have selected on the canvas. diff --git a/modules/ROOT/pages/workflow-create-mapping-ui-studio.adoc b/modules/ROOT/pages/workflow-create-mapping-ui-studio.adoc index f1aa7e41..fe23f020 100644 --- a/modules/ROOT/pages/workflow-create-mapping-ui-studio.adoc +++ b/modules/ROOT/pages/workflow-create-mapping-ui-studio.adoc @@ -2,7 +2,7 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5@studio::workflow-create-mapping-ui-studio.adoc +:page-aliases: 6.x@studio::workflow-create-mapping-ui-studio.adoc . xref:input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation] Provide expected input and required output structures.