W 11585544 update studio version 6.5

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.
 

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.

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.

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.

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].

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.

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]

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.

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.
 

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.

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]

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]

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]

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]

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]

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]

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]

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_*

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]

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*"]
 |===

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.

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:

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.

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]

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*.

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

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].

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.

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.
 

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.
 

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.

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.
 

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.

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.

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.

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].

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.

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.
 

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.

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.

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.

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]

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]

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.