BassemE/mulesoft-documentation-embeddings huggingface dataset:
SAP S/4HANA SOAP Connector 2.6 XML and Maven Support | MuleSoft Documentation
# SAP S/4HANA SOAP Connector 2.6 XML and Maven Support
If you manually code a Mule app in XML either from the Anypoint Studio XML editor or from a text editor, you can get access to the connector in your app by adding reference statements to your XML Mule flow and in the Apache Maven POM file.
You can avoid the manual process described in this topic by using Studio. When you install the connector in Anypoint Studio, Studio automatically populates the XML code with the connector’s namespace and schema location, and adds a dependency to the pom.xml file.  
---  
## Add a Namespace for the Connector
Paste the following code inside the `mule` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/s4hana-soap
http://www.mulesoft.org/schema/mule/s4hana-soap/current/mule-s4hana-soap.xsd
```

This example shows how the namespace statements are placed in the XML:
```
<mule xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
xmlns:s4hana-soap="http://www.mulesoft.org/schema/mule/s4hana-soap"
xmlns:http="http://www.mulesoft.org/schema/mule/http"
xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http
http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/s4hana-soap
http://www.mulesoft.org/schema/mule/s4hana-soap/current/mule-s4hana-soap.xsd
http://www.mulesoft.org/schema/mule/ee/core
http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">
```

## Add a POM File Dependency
The pom.xml Apache Maven file generated by Anypoint Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your POM file to enable access to this connector:
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
 <artifactId>mule-sap-s4hana-soap-cloud-connector</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Verify that the connector `version` corresponds to the one you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `SAP S/4HANA SOAP`.
  4. Click **Dependency Snippets**.


## Next Step
After completing your namespace and pom.xml file, you can try the Examples.
## See Also
MuleSoft Help Center
Missing Feature Error | MuleSoft Documentation
# Missing Feature Error
If you receive a `Missing feature` error when you install Anypoint API Community Manager, ensure that digital experiences (previously known as _communities_) are enabled in your API Community Manager Salesforce organization.
The error looks similar to the following issues:
```
1. Lightning Community Themes(communityThemeDefinitions/acm_template.communityThemeDefinition) Missing feature
Installing this package requires the following feature and its associated permissions: Lightning Community Themes
2. Lightning Community Templates(communityTemplateDefinitions/NTO.communityTemplateDefinition) Missing feature
Installing this package requires the following feature and its associated permissions: Lightning Community Templates
3. Navigation Link Sets(navigationMenus/acm_template_Nav0.navigationMenu) Missing feature
Installing this package requires the following feature and its associated permissions: Navigation Link Sets
```

To fix this error, follow the installation prerequisite steps in Enable Digital Experience.
Diff (dw::util::Diff) | MuleSoft Documentation
# Diff (dw::util::Diff)
This utility module calculates the difference between two values and returns a list of differences.
To use this module, you must import it to your DataWeave code, for example, by adding the line `import * from dw::util::Diff` to the header of your DataWeave script.
## Functions
Name | Description  
---|---  
Returns the structural differences between two values.  
## Types
minBy | MuleSoft Documentation
# minBy
## minBy<T>(@StreamCapable array: Array<T>, criteria: (item: T) -> Comparable): T | Null
Iterates over an array to return the lowest value of comparable elements from it.
The items need to be of the same type. `minBy` returns an error if they are not, and it returns null when the array is empty.
### Parameters
Name | Description  
---|---  
Element in the input array (of type `Number`, `Boolean`, `DateTime`, `LocalDateTime`, `Date`, `LocalTime`, `Time`, or `TimeZone`). Can be referenced with `$`.  
### Example
This example returns the lowest numeric value within objects (key-value pairs) in an array. Notice that it uses `item.a` to select the value of the object. You can also write the same expression like this, using an anonymous parameter: `[ { "a" : 1 }, { "a" : 3 }, { "a" : 2 } ] minBy $.a`
#### Source
```
%dw 2.0
output application/json
---
[ { "a" : 1 }, { "a" : 2 }, { "a" : 3 } ] minBy (item) -> item.a
```

#### Output
### Example
This example gets the latest `DateTime`, `Date`, and `Time` from inputs defined in the variables `myDateTime1` and `myDateTime2`. It also shows that the function returns null on an empty array.
#### Source
```
%dw 2.0
var myDateTime1 = "2017-10-01T22:57:59-03:00"
var myDateTime2 = "2018-10-01T23:57:59-03:00"
output application/json
---
{
 myMinBy: {
  byDateTime: [ myDateTime1, myDateTime2 ] minBy ((item) -> item),
  byDate: [ myDateTime1 as Date, myDateTime2 as Date ] minBy ((item) -> item),
  byTime: [ myDateTime1 as Time, myDateTime2 as Time ] minBy ((item) -> item),
  aBoolean: [ true, false, (0 > 1), (1 > 0) ] minBy $,
  emptyArray: [] minBy ((item) -> item)
 }
}
```

#### Output
```
{
 "myMinBy": {
  "byDateTime": "2017-10-01T22:57:59-03:00",
  "byDate": "2017-10-01",
  "byTime": "22:57:59-03:00",
  "aBoolean": false,
  "emptyArray": null
 }
}
```
Azure Service Bus Connector 3.4 XML and Maven Support | MuleSoft Documentation
# Azure Service Bus Connector 3.4 XML and Maven Support
Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio.
If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML editor or from a text editor, you can get access to the connector in your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
When you install the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location. It also adds a dependency to the `pom.xml` file.
## Add a Namespace for the Connector
Paste the following code inside the `<mule>` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/<connector>
http://www.mulesoft.org/schema/mule/<connector>/current/mule-<connector>.xsd
```

This example shows how the namespace statements are placed in the `<mule>` XML block:
```
<mule xmlns:azure-service-bus-messaging="http://www.mulesoft.org/schema/mule/azure-service-bus-messaging"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/azure-service-bus-messaging
	http://www.mulesoft.org/schema/mule/azure-service-bus-messaging/current/mule-azure-service-bus-messaging.xsd">
```

## Add a POM File Dependency
The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector:
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule-azure-service-bus-connector</artifactId>
  <version>x.x.x</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Verify that the `<version>` corresponds to the connector you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `azure service bus`.
  4. Select the connector.
  5. Click **Dependency Snippets** near the upper right of the screen.


## Next Step
After completing your namespace and `pom.xml` file, you can try the examples.
## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
LDAP Connector 3.6 | MuleSoft Documentation
# LDAP Connector 3.6
Anypoint Connector for Lightweight Directory Access Protocol (LDAP) is a public standard that facilitates maintenance and access to distributed directories (such as network user privilege information) over an Internet Protocol (IP) network.
LDAP Connector supports both LDAP over SSL and LDAP over TLS.
Many LDAP servers are included in free-use open source projects and packages. The particulars of installing, running, and configuring LDAP servers fall outside the scope of this document.
For information about compatibility and fixed issues, see the LDAP Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The LDAP Connector’s API
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * How to create a Mule app using Anypoint Studio


Before creating an app, you must have:
  * Credentials to access an OpenLDAP instance that supports LDAP v3
  * Anypoint Platform
  * Anypoint Studio version 7.0 or later


## Common Use Cases For the Connector
Common use cases for LDAP Connector include:
  * Adding user accounts to Active Directory
You can add business users to Active Directory groups defined on the base distinguished name (DN).
  * Retrieving user attributes
You can retrieve the basic attributes of a business user such as a user’s e-mail or phone number.


## Connection Types
LDAP connector supports three types of connections:
  * Basic
Communications are not encrypted.
**Note:** If running in an instance configured with mule.security.model=fips140-2, attempting to use a Basic connection will result in an LDAP:SECURITY error.
  * SSL
Communications are encrypted using Secure Sockets Layer (SSL).
  * TLS
Communications are encrypted using Transport Layer Security (TLS).


You can use Basic (username and password) authentication for each of these connection types.
For more information about configuring connection types and authentication, see Using Studio to Configure LDAP Connector.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * LDAP Connector Reference
  * MuleSoft Help Center
NetSuite Connector 11.5 | MuleSoft Documentation
# NetSuite Connector 11.5
Anypoint Connector for NetSuite (NetSuite Connector) synchronizes data and automates business processes between NetSuite and third-party applications, either on-premises or in the cloud. NetSuite provides cloud-based business management software that helps companies manage core business processes, ERP financials, CRM, e-commerce, inventory, and more.
NetSuite Connector provides the following features:
  * SOAP-based integration
NetSuite Connector 11.0 and later does not support REST-based operations.
  * Generation of NetSuite business objects
  * Different authentication levels
  * Error-handling support


For compatibility information and fixed issues, see the NetSuite Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The NetSuite API
  * Anypoint connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * Creating a Mule app using Anypoint Studio (Studio)


Before creating an app, you must have:
  * Credentials to access NetSuite Web Services
  * Anypoint Studio version 7.3.3 or later


## Common Use Cases for the Connector
  * Quote-to-Cash
Improve cash flow, remove manual order entries, and minimize order errors by leveraging realtime integrations to connect and synchronize data about your customer’s intent to buy from your CRM application, such as Salesforce, into its realization of revenue in NetSuite ERP.
  * Invoice-to-Reconciliation
Automate your Accounts Receivable (A/R) process by automatically applying bank payments against invoices in NetSuite for real-time A/R processing. Streamline accounts payable by automating payment file transfers between NetSuite and your banks.
  * Hire-to-Retire
Build a single view of your employees with realtime synchronization of employee information between Netsuite and your Human Capital Management (HCM) services, such as Workday, Oracle HCM, PeopleSoft, and so on. Automatically trigger employee onboarding processes such as ordering computer equipment, uniforms, system access setup, and so on, while reversing the process upon retirement.


## Authentication types
NetSuite connections use token-based authentication, which uses either a consumer key and token ID or secret pairs to authenticate.
For information about configuring this authentication type, see Using Anypoint Studio to Configure NetSuite Connector.
## Using Exchange Templates and Examples
Anypoint Exchange provides the following templates that you can use as starting points for your apps:
  * Retrieve a List of Customers from NetSuite
  * Salesforce and NetSuite Opportunity Aggrgation


## Next Step
After you complete the prerequisites, you are ready to create your own app and configure the connector using Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * MuleSoft Help Center
About HTTP Connector Migration | MuleSoft Documentation
# About HTTP Connector Migration
The Mule 4 version of Anypoint Connector for HTTP (HTTP Connector) contains the following key differences from the Mule 3 version of the connector:
  * The `http:listener-config` element has a new inner connection element `http:listener-connection`.
  * The `http:request-config` element has a new inner connection element `http:request-connection`.
  * The HTTP body parameter replaces the source parameter in the request and is incorporated into the listener’s response and error response.
  * The HTTP **Listener** source and HTTP **Request** operation return attributes.
  * The HTTP **Request** configuration has the **Enabled Cookie** parameter set to `true` (default).
  * HTTP parsing has been removed because DataWeave now manages special MIME types. Use DataWeave syntax to read and write payloads.
  * The HTTP **Load static resource** operation XML code `static-resource-handler` is renamed to `load-static-resource`.
  * To access HTTP listener and HTTP request attributes, the following DataWeave syntax replaces the Mule Expression Language (MEL) expressions for accessing past properties:
`#[attributes.<parameter>]`
For more information about mapping Mule 3.x MEL expressions to Mule 4 DataWeave expressions, refer to the HTTP Connector XML Reference documentation.
  * The following constructs are removed in Mule 4:
    * Request and response builders, `http:request-builder` and `http:response-builder`
    * Worker threading profile
The request, response, and error-response replace the builders. Using DataWeave expressions eliminates the need for building parameters.


## See Also
  * HTTP Connector XML Reference
  * HTTP Connector Reference
Configure Azure Active Directory Authentication for MS SQL Server using the Database Connector | MuleSoft Documentation
# Configure Azure Active Directory Authentication for MS SQL Server using the Database Connector
Anypoint Connector for Database (Database Connector) enables you to configure Azure Active Directory Authentication for MS SQL Server by setting the `IntegratedSecurity` value in the connection configuration. The following example shows how to configure this value in Anypoint Studio:
  1. In Studio, navigate to the **Global Elements** tab.
  2. Click **Create**.
  3. In the filter box, search `database`.
  4. Select **Database Config**.
  5. Click **OK**.
  6. In the **Database Config** window, for **Connection** , select **MS SQL Server Connection**.
  7. In the **Advanced** tab, set **Connection properties** to **Edit inline**.
  8. Click the green plus sign.
  9. Set **Key** to `Integratedsecurity`.
  10. Set **Value** to `true`.
  11. Click **Finish**.
  12. Complete the remaining connection settings for the database.
  13. Click **OK**.


In the **Configuration XML** editor, the `key="integratedsecurity` configuration looks like this:
```
<db:config name="Database_Config1" doc:name="Database Config" >
		<db:my-sql-connection >
			<db:connection-properties >
				<db:connection-property key="integratedsecurity" value="true" />
			</db:connection-properties>
		</db:my-sql-connection>
	</db:config>
```

## See Also
  * Database Connector Reference
  * MuleSoft Help Center
Delete Folder | MuleSoft Documentation
# Delete Folder
Use this action step to delete a folder and all its content.
## Properties
  * **Common**
See Common Properties for a description.
  * **Folder Operations Settings**
    * **Directory Path**
Path to the directory that contains the folder to delete.
    * **Force error if folder does not exist**
Causes the workflow to enter an error state and stop its execution if the folder does not exist.
    * **Only delete if folder is empty**
Causes the workflow to enter an error state and stop its execution if the folder exists but it’s not empty.


## Inbound Variables
  * **Force error if folder does not exist**
  * **Only delete if folder is empty**
  * **Directory Path**


## Outbound Variables
  * **Directory Path**


## See Also
  *
Clear Screen | MuleSoft Documentation
# Clear Screen
This action step will try to clear any open window from the screen. First, it will try to stop these processes: _SAPlogon.exe_ , _cmd.exe_ , and _SAPfewgsrv.exe_. Next, it will try to kill all windows that have the state _Visible_ (this may also include minimized windows!), except for any MuleSoft-related windows and the _System Shell_ , which includes the _Desktop_ and the _Task Bar_.
It is good practice to use a _Clear screen_ at the beginning of each _Workflow_. This will provide a clean state to run the _Workflow_ in without disturbances and thus improve _Workflow_ reliability.
In draft mode, the Clear Screen action step is disabled. No windows are closed. After testing the Workflow using the Run Workflowt (F7) button, a yellow warning appears on the Workbench.
## Properties
  * **Action in case of failure** Define, what should be done if _Clear screen_ failed. Available actions are: _Make screenshot_ , _Make screenshot and write log_ , _Make reboot,_ and _Minimize windows_
  * **Action in case of success** Define what the Workflow should do if _Clear screen_ was successful. Available follow-up actions are: _Do nothing_ or _Write log_
Microsoft Dynamics 365 Connector 2.6 XML and Maven Support | MuleSoft Documentation
# Microsoft Dynamics 365 Connector 2.6 XML and Maven Support
If you manually code a Mule app in XML either from the Anypoint Studio XML editor or from a text editor, you can get access to the Microsoft Dynamics 365 Connector in your app by adding reference statements to your XML Mule flow and in the Apache Maven pom.xml file.
You can avoid the manual process described in this topic by using Studio. When you install Microsoft Dynamics 365 Connector in Anypoint Studio, Studio automatically populates the XML code with the Microsoft Dynamics 365 Connector namespace and schema location, and adds a dependency to the pom.xml file.  
---  
## Add a Namespace for the Connector
Paste the following code inside the `mule` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/microsoft-dynamics-365
http://www.mulesoft.org/schema/mule/microsoft-dynamics-365/current/mule-microsoft-dynamics-365.xsd
```

This example shows how the namespace statements are placed in the XML:
```
<mule xmlns:$2="http://www.mulesoft.org/schema/mule/$2"
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:file="http://www.mulesoft.org/schema/mule/file"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/file
	http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
	http://www.mulesoft.org/schema/mule/ee/core
	http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
	http://www.mulesoft.org/schema/mule/$2
	http://www.mulesoft.org/schema/mule/$2/current/mule-$2.xsd">
```

## Add a POM File Dependency
The Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your pom.xml file to enable access to the connector.
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
 <artifactId>mule-microsoft-dynamics365-connector</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.
To obtain the most up-to-date `pom.xml` file information, access the connector in Anypoint Exchange and click **Dependency Snippets**.
## Next Step
After completing your namespace and `pom.xml` file, you can try the Examples.
## See Also
  * MuleSoft Help Center
SFTP Connector XML and Maven Support | MuleSoft Documentation
# SFTP Connector XML and Maven Support
Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio.
If you manually code a Mule runtime engine (Mule) app in XML, either from the Anypoint Studio XML editor or from a text editor, you can get access to the connector in your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
When you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location. It also adds a dependency to the `pom.xml` file.
## Add a Namespace for the Connector
Paste the following code inside the `<mule>` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/sftp
http://www.mulesoft.org/schema/mule/sftp /current/mule-sftp .xsd
```

This example shows how the namespace statements are placed in the `<mule>` XML block:
```
<mule xmlns:sftp ="http://www.mulesoft.org/schema/mule/sftp "
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:file="http://www.mulesoft.org/schema/mule/file"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/file
	http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
	http://www.mulesoft.org/schema/mule/ee/core
	http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
	http://www.mulesoft.org/schema/mule/sftp
	http://www.mulesoft.org/schema/mule/sftp/current/mule-sftp.xsd">
```

## Add a POM File Dependency
The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector:
```
<dependency>
 <groupId>org.mule.connectors</groupId>
 <artifactId>mule-sftp-connector</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `sftp connector`.
  4. Select the connector.
  5. Click **Dependency Snippets** near the upper right of the screen.


## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
MongoDB Connector 6.3 XML and Maven Support | MuleSoft Documentation
# MongoDB Connector 6.3 XML and Maven Support
If you manually code a Mule app in XML either from the Anypoint Studio XML editor or from a text editor, you can get access to Anypoint Connector for MongoDB (MongoDB Connector) in your app by adding reference statements to your XML Mule flow and in the Apache Maven `pom.xml` file.
You can avoid the manual process described in this topic by using Studio. When you install MongoDB Connector in Studio, Studio automatically populates the XML code with the MongoDB Connector namespace and schema location, and adds a dependency to the `pom.xml` file.
## Add a Namespace for the Connector
Paste the following inside the `<mule>` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/mongodb
http://www.mulesoft.org/schema/mule/mongodb/current/mule-mongo.xsd
```

This example shows how the namespace statements are placed in the <mule> XML block:
```
<mule xmlns:mongodb="http://www.mulesoft.org/schema/mule/mongodb"
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:file="http://www.mulesoft.org/schema/mule/file"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/file
	http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
	http://www.mulesoft.org/schema/mule/ee/core
	http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
	http://www.mulesoft.org/schema/mule/mongodb
	http://www.mulesoft.org/schema/mule/mongodb/current/mule-mongo.xsd">
```

## Add a POM File Dependency
The `pom.xml` Maven file generated by Studio contains dependencies for a Mule app. When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector:
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
 <artifactId>mule-mongodb-connector</artifactId>
 <version>6.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

To obtain the most up-to-date `pom.xml` file information, access the connector in Anypoint Exchange and click **Dependency Snippets**. Replace `6.x.x` in the `<version>` element with your MongoDB version.
## Next Steps
After completing your namespace and `pom.xml` file, you can try the MongoDB Examples.
## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
JMS Connector Examples | MuleSoft Documentation
# JMS Connector Examples
To fully benefit from using Anypoint Connector for JMS (JMS Connector), see the following examples of configuring the connector operations:
  * Configure an ActiveMQ Connection Configure JMS Connector to connect to ActiveMQ.
  * Manage Message Acknowledgements Configure JMS Connector to manage different acknowledgment configurations, such as automatic acknowledgment on success, immediate acknowledgment, and manual acknowledgment.
  * Listen for New Messages Configure the **On New Message** source to listen for new messages as they arrive to the destination.
  * Publish New Messages Configure the **Publish** operation to create a new message and send it to the specified destination.
  * Consume Messages Configure the **Consume** operation to consume a message at any given time in the flow, from any given destination.
  * Publish Messages and Listen for Replies Configure the **Publish consume** operation to publish a message to any destination, and then wait for a reply on a different destination.
  * Publish and Consume Messages Within Flows Configure the **Publish consume** operation to publish and consume messages within two flows, and use a correlation ID to ensure that the incoming messages are replies to a specific outgoing message.
  * Manage Transactions Configure JMS Connector to execute a series of operations that are performed only when the transaction is committed.
  * Configure Topic Subscription Configure topics subscriptions in JMS Connector to control how subscriptions behave regarding consumers connections and also how these consumers interact with each other.
  * Configure XA Transactions Configure XA transactions using the **XA Connection Pool** and the **Transaction Type** fields.


## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
Aggregators Module 1.1 | MuleSoft Documentation
# Aggregators Module 1.1
For compatibility information and fixed issues, see the Aggregator Module Release Notes.
Aggregators Module contains different types of aggregators that use a specified configuration to both store and release values. An _aggregator scope_ is a component that collects those values until a specified condition is met, when it then executes a processor’s chain of components, with the list of aggregated elements as the payload.
The basic aggregator configuration consists of the definition of the value to aggregate (extracted from the message through an expression evaluation), a condition that defines when the aggregation is considered complete, and a processor chain that executes once that condition is met.
Aggregators are pass-through routers. The same data that an aggregator scope receives is processed by the components that follow the aggregator scope. The only modification is variable propagation if any variables are set during the execution of any of the aggregation routes.
## Before You Begin
To use this module, you must be familiar with:
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * Creating a Mule app using Anypoint Studio (Studio)


Before creating an app, you must have to Anypoint Platform and Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * MuleSoft Help Center
Use Anypoint CLI | MuleSoft Documentation
# Use Anypoint CLI
An Anypoint Platform CLI call has the following form:
```
$ anypoint-cli [params] [command]
```

## exit
```
> exit [options]
```

This command exits Anypoint Platform CLI.
This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.
If you choose not to pass a command, Anypoint Platform CLI runs in interactive mode. If you choose to pass a specific command and there is an error, the application exits and returns a description of the issue.
The Anypoint Platform CLI provides three default options:
  * The `--help` option displays usage information of the command.
  * The `-o` or `--output` option lets you specify the command’s output to the defined format. Supported values are `table`, `text`, and `json`. Defaults to `text` for non-interactive mode and `table` for interactive sessions.
  * The `-f` or `--fields` option allows you to define which fields to output. You can pass the `--fields` option after a command to get a list of all possible fields to output.
Checking System Parameters | MuleSoft Documentation
# Checking System Parameters
Some system parameters in _Windows_ significantly affect how the screen image is displayed. For example, turning _ClearType_ (a font smoothing algorithm built into _Windows_) on or off affects the rendering of almost all displayed text – this includes browsers, applications, system dialogs, menu bars, etc.
As you can see, there is a big difference between the display of text when _ClearType_ is on or off. Our image search algorithm always compares a "_Pattern image_ " to what is visible on the screen during execution. Now imagine you capture a _Pattern image_ containing text on a system where _ClearType_ is enabled (i.e. the left part of the picture above), but then execute the _Workflow_ on a system where _ClearType_ is disabled. The _MuleSoft_ image search algorithm compares the left-hand image to the right-hand one and, although it still finds the image, the match precision will be very low.
Aside from _ClearType_ , the image search is also affected by the "Menu drop shadow" setting and the DPI setting.
The display parameters on the system used to create a _Workflow_ should always be identical to the parameters on the system where the workflow is executed!
You should also turn off any settings or programs that may disrupt the _Workflow_ during execution due to unexpected behavior, such as displaying sudden pop-up windows. Common causes of sudden _Workflow_ failures are automatic updates to _Windows_ and other programs you have installed.
You should always configure your agent systems to show no unexpected behavior such as sudden pop-ups, screensavers, or similar.
## Recommended Systems Settings
  * Disable screen saver
  * Turn off all power option properties
  * Disable automatic _Windows_ updates
  * Disable _ClearType_
  * Disable menu drop shadow effects
  * Set desktop scaling to _100%_


## Checking the System Parameters
The menu item _View_ → _Show System Parameters_ opens an overview over the most important settings of your system.
Settings marked with a green circle can be left this way.
Settings marked with a red circle should be changed.
With the **Refresh** button you can check if setting changes have led to an optimization of the status.
Using Coverage in Studio | MuleSoft Documentation
# Using Coverage in Studio
Anypoint Studio 
You can run a coverage report from Anypoint Studio.
The following configurations apply only when you execute your MUnit tests in Studio. They do not apply when running tests from Maven in a CI/CD environment. To run coverage reports from Maven see Maven Configuration for Coverage.
## Enable Coverage Reports in Anypoint Studio
You can see which flows, and which percentage of event processors in those flows the test covers by clicking on the Coverage button:
The Overall Coverage value represents the percentage of the Mule application event processors that the MUnit test executes.
You can click **Generate Report** to get the report that details the flows and event processors in the Mule configuration files that are included in the MUnit test.
Column | Description  
---|---  
Name of the Mule configuration file  
Number of flows inside the Mule configuration file  
Percentage of your application in a configuration file A percentage of the overall number of event processors in the documentation and the number of event processors in the Mule configuration file  
Percentage of event processors in the Mule configuration file that the MUnit test executes  
Additionally, you can click on each **Resource** to get a more specific and granular report of the Event Processors executed in that resource:
Column | Description  
---|---  
Name of the container  
Type of the container  
**Covered Processors** |  Processors inside the container that are executed during the MUnit test  
Total amount of processors inside the container  
Percentage of the event processors inside the container executed in the MUnit test  
## Disable Coverage Reports
If you choose so, you can disable the coverage calculation from your project run configuration so you test your flow without a coverage report.
Right-click **Package Explorer** and choose **Run As** > **Run Configurations**. Select your MUnit run configuration file to access your suite configuration, and deselect the **Run coverage** option in your coverage settings.
## Exclude XML Files from MUnit Coverage Report
You can exclude one or more XML files from an MUnit Coverage report when testing your application. For example, you can exclude a third-party XML file that does not comply with your quality standards to improve your final report score.
  1. Go to the flow to change.
  2. Click **Run** > **Run Configuration**.
  3. Click the name of your project.
  4. In the **Ignored files** section, click **Add**.
  5. Type the name of the XML file to exclude from the Coverage report and click **OK**.
  6. Click **Apply** and **Run**.


## See Also
  * Maven Configuration for Coverage
XML Module XML and Maven Support | MuleSoft Documentation
# XML Module XML and Maven Support
Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio.
If you manually code a Mule runtime engine (Mule) app in XML, either from the Anypoint Studio XML editor or from a text editor, you can get access to the connector in your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
When you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location. It also adds a dependency to the `pom.xml` file.
## Add a Namespace for the Connector
Paste the following code inside the `<mule>` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/xml-module
http://www.mulesoft.org/schema/mule/xml-module/current/mule-xml-module.xsd
```

This example shows how the namespace statements are placed in the `<mule>` XML block:
```
<mule xmlns:<connector>="http://www.mulesoft.org/schema/mule/xml-module"
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:file="http://www.mulesoft.org/schema/mule/file"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/file
	http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
	http://www.mulesoft.org/schema/mule/ee/core
	http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
	http://www.mulesoft.org/schema/mule/xml-module
	http://www.mulesoft.org/schema/mule/xml-module/current/mule-xml-module.xsd">
```

## Add a POM File Dependency
The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector:
```
<dependency>
 <groupId>org.mule.modules</groupId>
 <artifactId>mule-xml-module</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `xml module`.
  4. Select the connector.
  5. Click **Dependency Snippets** near the upper right of the screen.


## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
ServiceNow Connector 6.17 XML and Maven Support | MuleSoft Documentation
# ServiceNow Connector 6.17 XML and Maven Support
Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio:
  * If you manually code a Mule runtime engine (Mule) app in XML, either from the Anypoint Studio XML editor or from a text editor, you can access the connector from your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
  * If you add the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file.


## Add a Namespace for the Connector
Paste the following code inside the `mule` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/servicenow
http://www.mulesoft.org/schema/mule/servicenow/current/mule-servicenow.xsd
```

This example shows how the namespace statements are placed in the XML:
```
<mule xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:servicenow="http://www.mulesoft.org/schema/mule/servicenow"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/servicenow
	http://www.mulesoft.org/schema/mule/servicenow/current/mule-servicenow.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd">
</mule>
```

## Add a POM File Dependency
The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector:
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
 <artifactId>mule-servicenow-connector</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `serviceNow`.
  4. Select the connector.
  5. Click **Dependency Snippets** near the upper right of the screen.


## Next Step
After completing your namespace and `pom.xml` file, you can try the Examples.
## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
Implicit Configurations | MuleSoft Documentation
# Implicit Configurations
Some configurations can be classified as implicit. A configuration can be used implicitly when none of its parameters are required. For example, suppose a `myConfig` configuration object which has a required parameter `param1`:
```
<example:my-config name="myConfig" param1="required value" />
<flow>
	<example:operation config-ref="myConfig" />
</flow>
```

Now suppose that the bar parameter were to turn optional instead:
```
<example:my-config name="myConfig" />
<flow>
	<example:operation config-ref="myFoo" />
</flow>
```

In this case, the entire my-config element (and subsequent config-ref) are redundant because they have no real effect. In these cases, implicit configurations can be used:
```
<flow>
	<example:operation />
</flow>
```

Because `my-config` does not have required parameters, the SDK can create an implicit instance in which all parameters are automatically assigned to their default values. The implicit configuration is either static or dynamic depending on its parameter’s default values. If any of those default values is an expression, then the implicit configuration is dynamic.
Using an expression as a default value violates the best practice of the position independence.   
---  
## Mixing Implicit and Explicit Configurations
You can use implicit and explicit configurations in tandem:
```
<flow>
	<example:operation />
	<example:operation config-ref="myConfig" />
</flow>
```

Only one implicit `config` is created per configuration type. If two operations try to use implicit configurations of the same type, each uses the exact same instance:   
---  
```
<flow>
	<example:operation />
	<example:operation />
	<!-- Both operations use the same config instance -->
</flow>
```

## Forcing Explicit Configurations
Available since version 1.3.
There are cases in which you might want to force configurations to always be explicit, even if they contain no required parameters. Usually, such requirements revolve around clarity and usability concerns.
Use the `@NoImplicit` annotation to instruct the SDK to never build implicit instances of a given configuration type:
```
@Extension(name="example")
@NoImplicit
@Operations(ExampleOperations.class)
public class ExampleModule {
	@Parameter
	@Optional
	public String bar;

}
```

You can also use this annotation if your configuration has been externalized into a separate class:
```
@Extension(name="example")
@Configurations(MyConfiguration.class)
public class ExampleModule {
}
@Configuration(name="myConfig")
@NoImplicit
@Operations(ExampleOperations.class)
public class MyConfiguration {
	@Parameter
	@Optional
	public String bar;

}
```
Getting Started with Anypoint MQ | MuleSoft Documentation
# Getting Started with Anypoint MQ
Follow these high-level steps to configure and use Anypoint MQ:
  1. Make sure you have a paid Anypoint Platform package or subscription with the Anypoint MQ integration add-on.
Contact your account team for information.
After purchasing Anypoint MQ, wait one hour for Anypoint MQ to become available in Anypoint Platform.
  2. Set up your environment and access permissions.
  3. Configure a connected app to get an ID and secret to configure Anypoint Connector for MQ (Anypoint MQ Connector).
  4. Configure a queue, message exchange, or a FIFO queue.
  5. Send messages to a queue or message exchange.
  6. Get messages from a queue.
  7. In Anypoint Studio, configure Anypoint MQ Connector in your Mule app:
    1. Install Anypoint MQ Connector using Anypoint Exchange.
    2. Create a new Mule project with required building blocks, such as an Anypoint Connector for HTTP (HTTP Connector), Anypoint MQ Connector, Set Payload, and a Logger.
    3. Configure Anypoint MQ Connector and provide the ID and secret of the connected app.
    4. Set the Anypoint MQ Connector operation to publish or consume messages, or to accept (ACK) or not accept (NACK) a message.
    5. Deploy the Mule app.
  8. Test the queue:
    1. Use a REST client such as `curl` or Postman to send or receive a message.
Anypoint MQ sends the string as a message to the queue or message exchange you specified.
    2. View your message in a browser or the Studio console.


## See Also
  * Anypoint MQ Tutorial
  * Anypoint MQ Connectors
  *   * Anypoint MQ Release Notes
  * Anypoint MQ Audit Logging