W-15100389-flowDesigEOL-Mule44-dm

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-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/flow-component.adoc

@@ -8,13 +8,13 @@ endif::[]
 
 toc::[]
 
-//Anypoint Studio, Design Center connector
+
 [[short_description]]
 Flow and Subflow scopes are components for grouping together a sequence of other
 Core components and operations (provided by connectors and modules) to help
 automate integration processes. The Flow component is fundamental to a
 Mule app. Because all Mule apps must contain at least one flow, Anypoint
-Studio and Flow Designer automatically provide the first Flow component in
+Studio automatically provides the first Flow component in
 your Mule app.
 
 A Mule app can contain additional flows and subflows, as this example shows:

modules/ROOT/pages/index.adoc

@@ -16,7 +16,7 @@ connectivity instead of point-to-point integrations. Mule applications provide
 functionality for message routing, data mapping, orchestration, reliability,
 security, and scalability.
 
-Anypoint Studio and Flow Designer support Mule application development.
+Anypoint Studio supports Mule application development.
 
 == Mule Domains
 

modules/ROOT/pages/migration-connectors-database.adoc

@@ -221,7 +221,7 @@ Microsoft SQL Server, MySQL, Derby, Oracle configurations require a driver.
 ----
 
 WARNING: Because of the new Mule 4 ClassLoading mechanism, this dependency must be declared as a Shared Library to be
-exported to the DB Connector. Using Studio or Flow Designer, this will be automatically configured.
+exported to the DB Connector. Using Studio, this will be automatically configured.
 
 //TODO LINK TO HOW TO ADD A SHARED LIBRARY OR THE USER WON'T NEVER REALIZE HOW TO DO IT
 

modules/ROOT/pages/migration-connectors-xml.adoc

@@ -250,7 +250,7 @@ This validator will raise an `XML-MODULE:SCHEMA_NOT_HONOURED` error.
 
 == Installing the XML Module
 
-To use the XML module, simply add it to your application using the Studio palette or Flow Designer card, or add the following dependency in your `pom.xml` file:
+To use the XML module, simply add it to your application using the Studio palette, or add the following dependency in your `pom.xml` file:
 
 [source,xml,linenums]
 ----

modules/ROOT/pages/mule-app-dev.adoc

@@ -158,18 +158,15 @@ providing cryptographic and other capabilities, such as FIPS compliance.
 == Development Environments
 
 You can develop a Mule application using
-xref:studio::index.adoc[Anypoint Studio] (an Eclipse-based IDE),
-xref:design-center::about-designing-a-mule-application.adoc[Flow Designer]
-(a cloud-based application in Design Center, on Anypoint Platform),
-or, if you are an advanced developer, in your own IDE.
+xref:studio::index.adoc[Anypoint Studio] (an Eclipse-based IDE), or, if you are an advanced developer, in your own IDE.
 
 For example, in Studio, you build and design a Mule application in a project
 that contains one or more XML-based files. A Mule project supports all the
 dependencies required for development. The
 xref:studio::index.adoc#package-explorer[Package Explorer] view in Studio
 provides access to the project folders and files that make up a Mule project.
 Studio provides a design-time environment in which you can also build, run, and test
-your Mule application. Flow Designer supports a cloud-based version of a Mule project.
+your Mule application.
 
 [[version]]
 == Mule Versioning

modules/ROOT/pages/mule-app-tutorial.adoc

@@ -3,7 +3,7 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-Most integrations require a change to the structure of data as it moves from source to destination. Within a Mule app, you can use the drag-n-drop interface of the Transform Message component to map data from one field or format to another, or you can write mappings by hand within DataWeave scripts. You typically build Mule apps in Studio or Design Center, but you can even write Mule app configurations by hand in XML. This tutorial uses Studio.
+Most integrations require a change to the structure of data as it moves from source to destination. Within a Mule app, you can use the drag-n-drop interface of the Transform Message component to map data from one field or format to another, or you can write mappings by hand within DataWeave scripts. You typically build Mule apps in Studio, but you can even write Mule app configurations by hand in XML. This tutorial uses Studio.
 
 Using a small data set and a training API available on Exchange, you'll create a project and define the transformation mapping from the API into a different structure and protocol. You'll use the drag-n-drop and also see the xref:dataweave.adoc[DataWeave] code that defines the transformation. After completing this tutorial, you'll be ready to create your own data mappings.