Merge branch 'master' of https://github.com/mulesoft/mulesoft-docs

Author: Sean Osterberg

index.adoc

@@ -9,4 +9,4 @@ Welcome to the new MuleSoft documentation site. The following pages help you sta
 
 == Making a Contribution
 
-MuleSoft welcomes community contributions to our documentation! To make a contribution, simply click any page’s "Edit on GitHub" link, which takes you to the source page on GitHub. To provide your change as a Git pull request, *first* accept our contributor’s agreement so that we can acknowledge your contribution. The repository’s link:https://github.com/mulesoft/mulesoft-docs/blob/master/README.adoc[readme file] provides more information about how you can make a positive difference in improving MuleSoft documentation, and be recognized for your contribution.
+MuleSoft welcomes community contributions to our documentation! To make a contribution, simply click any page’s "Edit on GitHub" link, which takes you to the source page on GitHub. To provide your change as a Git pull request, *first* accept our link:http://www.mulesoft.org/legal/contributor-agreement.html[contributor’s agreement] so that we can acknowledge your contribution. The repository’s link:https://github.com/mulesoft/mulesoft-docs/blob/master/README.adoc[readme file] provides more information about how you can make a positive difference in improving MuleSoft documentation, and be recognized for your contribution.

mule-agent/v/1.1.1/index.adoc

@@ -1,11 +1,7 @@
 = The Mule Agent
 :keywords: agent, mule, esb, servers, monitor, notifications, external systems, third party, get status, metrics
 
-*_Enterprise Edition_*
-
-*_Mule 3.7.0_*
-
-*_Agent version 1.1.0_*
+*_Enterprise Edition_*, *_Mule 3.7.0_*
 
 The Mule agent is a plugin extension for Mule which exposes the Mule API. Using the Mule agent, you can monitor and control your Mule ESB servers by calling APIs from external systems, and/or have Mule publish its own data to external systems. The agent has many features, including:
 
@@ -23,18 +19,14 @@ Additionally, MuleSoft provides several open source agent modules. These are pro
 * https://github.com/mulesoft/mule-agent-modules[Agent modules (general)]
 * https://github.com/mulesoft/mule-agent-modules/tree/master/mule-agent-monitoring-publishers[JMX publisher modules]
 
-[cols=",",]
-|===
-|image:information.png[information] |The Mule agent is only available for Mule Enterprise Edition (EE). Currently, the Mule agent supports Mule 3.6.0 or later.
-
-|===
-
+[NOTE]
+The Mule agent is only available for Mule Enterprise Edition (EE). Currently, the Mule agent supports Mule 3.6.0 or later.
 
 == Assumptions
 
 The pages listed below assume that you have the current version of Mule Enterprise already installed. Download it from the http://www.mulesoft.com/support-login[customer portal] if you need to upgrade to this version.
 
-Additionally, it is assumed that your enterprise license is current. Please see http://www.mulesoft.org/documentation/display/current/Installing+an+Enterprise+License[Installing an Enterprise License] for information on obtaining and installing an enterprise license.
+Additionally, it is assumed that your enterprise license is current. Please see link:mule-user-guide/v/3.7/installing-an-enterprise-license[Installing an Enterprise License] for information on obtaining and installing an enterprise license.
 
 == Mule Agent Documentation Pages
 

mule-user-guide/v/3.7/_images/query+params.png renamed to mule-user-guide/v/3.7/_images/query_params.png

@@ -42,36 +42,48 @@ When writing Mule projects in XML, the HTTP Connector can work in one of two way
 
 To instance the connector as an HTTP Listener Connector, add the following XML tag at the start of a flow:
 
-`<``http:listener` `config-ref``=``"HTTP_Listener_Configuration"` `path``=``"/"``/>`
+[source,xml]
+----
+<http:listener config-ref="HTTP_Listener_Configuration" path="/" />
+----
 
 This element must reference a global configuration element of the following type:
 
-`<http:listener-config` `name``=``"HTTP_Listener_Configuration"` `host``=``"localhost"` `port``=``"8081"``/>`
+[source,xml]
+----
+<http:listener-config name="HTTP_Listener_Configuration" host="localhost" port="8081" />
+----
 
 To instance the connector as an HTTP Listener Connector, add the following XML tag in any part of a flow:
 
- `<``http:request` `config-ref``=``"HTTP_Request_Configuration"` `path``=``"/"` `method``=``"GET"``/>`
+[source,xml]
+----
+<http:request config-ref="HTTP_Request_Configuration" path="/" method="GET" />
+----
 
 This element must reference a global configuration element of the following type:
 
 
-[source,xml, linenums]
+[source,xml]
 ----
 <http:request-config name="HTTP_Request_Configuration" host="example.com" port="8081"/>
 ----
 
 
 == See Also
 
-* See a link:/developer.mulesoft.com/docs/display/current/HTTP+Connector+Reference[full Reference] of the available XML configurable options in this connector
+* See the link:/mule-user-guide/v/3.7/http-connector-reference[full Reference] for the available XML configurable options in this connector.
 =======
-`<``http:request-config` `name``=``"HTTP_Request_Configuration"` `host``=``"example.com"` `port``=``"8081"``/>`
 
+[source,xml]
+----
+<http:request-config name="HTTP_Request_Configuration" host="example.com" port="8081" />
+----
 ....
 ------
 
 [TIP]
-To migrate a project that users instances of the old http://www.mulesoft.org/documentation/display/current/HTTP+Transport+Reference[HTTP endpoint-based Connector] to the new HTTP operation-based Connector, see link:/mule-user-guide/v/3.7/migrating-to-the-new-http-connector[Migrating to the New HTTP Connector]. The old HTTP endpoint-based Connector still does work with Mule 3.6 Runtime, but it's deprecated and will be eventually removed.
+To migrate a project that uses instances of the old link:/mule-user-guide/v/3.7/http-transport-reference[HTTP endpoint-based connector] to the new HTTP operation-based connector, see link:/mule-user-guide/v/3.7/migrating-to-the-new-http-connector[Migrating to the New HTTP Connector]. The old HTTP endpoint-based Connector still works with Mule 3.6 Runtime, but it's deprecated and will eventually be removed.
 
 [TIP]
 You can edit the log4j2 configuration file to make the logging of the HTTP connector's activity a lot more verbose, if you need to. See link:/mule-user-guide/v/3.7/logging-in-mule[Logging in Mule] for instructions.