Repository navigation
FAQ
Anypoint Studio comes pre-bundled with a Java 8 (and as of 2020, Java 11) build. We recommended using the pre-bundled version instead of a local JDK. If you must use a local JDK, please try the following:
- https://docs.mulesoft.com/studio/7.5/change-jdk-for-studio
- https://support.mulesoft.com/s/article/Studio-7-does-not-recognise-correct-JDK-location-on-Windows
Ensure that you have the MarkLogic MuleSoft Connector installed, ideally from Anypoint Exchange, or alternatively from a version you've compiled from source. Updating the dependency in your Mule application pom.xml file will usually reset functionality. If not, you may have to remove the project from your workspace and then import the project into your workspace again if you imported initially before the connector was installed.
Look in your Package Explorer for a file called automation-credentials.properties. This is the MuleSoft convention for storing external properties as constants, such as usernames, passwords, host names, ports, etc. It's even used to configure the filesystem output location, such as ${config.fileOutputPath}.
This could be several things, but most commonly it's related to the required authentication credentials not getting passed, as covered in the previous question. See also the Best Practices, Demo Applications, or Example Flows Wiki pages to determine usage patterns and conventions preparing input and output from the MarkLogic Connector operations.
If you experience an issue not related to the automation credentials usage, please contact us.
I'm a developer making changes to the Connector, but I do not see them reflected in Anypoint Studio.
The best rule of thumb when actively developing on the connector is to provide an incremental, "one up" snapshot pom.xml <version> change on the project before your Maven build. For example, instead of the default 1.1.1, use 1.1.1-SNAPSHOT-1. For each subsequent change, increment the -1 to -2, etc.
Then, after a successful Maven build, update the version of the connector in your Mule application pom.xml dependency. Specifying the incremented version pulls the connector jar from your Maven repository.
Do you have a good reference/tutorial for developing a MuleSoft Connector? Or for finding info to help troubleshoot Mule applications in general?
There are several good developer-centric blogs covering how to get started, and it's even covered here in the Wiki under Building and Scaffolding the Connector.
- https://www.redpill-linpro.com/techblog/2018/02/02/mule-4-sdk-custom-connector.html
- https://dzone.com/articles/how-to-create-a-custom-connector-in-new-mule-sdk-4
The key thing to keep in mind is the MarkLogic Connector has only ever targeted Mule version 4.x and higher. No plans exist to support the Connector on Mule 3.x. Please ignore any contents referring to Mule 3.x, also known as "DevKit", as Mule 4.x is total re-write compared to 3.x.
Mule 4 was released in 2018, and there isn't quite as much community documentation built up around Mule 4 just yet. The best rule of thumb is to target your Google searches to "Mule 4", and restrict the search to contents within the last year or two.