nJAMS Client for Mule4 extends the nJAMS family with a client software that enables the monitoring of MuleSoft Runtime Engine flow executions.
How does nJAMS Client for Mule4 work?¶
nJAMS Client for Mule4 is a full featured nJAMS Client. nJAMS Client for Mule4 collects execution information from flows of MuleSoft Runtime Engine such as execution times, duration, executed path, recorded input/output data, etc. All this monitoring information from nJAMS Client for Mule4 is provided to nJAMS Server, respectively nJAMS Cloud, where the data can be searched and inspected. A user can query for monitoring data by using nJAMS User Interface. For example, a user can search for a particular flow instance and see details of processing the flow of a MuleSoft Runtime Engine application:
nJAMS Client for Mule4 supports both on-premise and MuleSoft CloudHub deployments.
nJAMS Client for Mule4 interacts with nJAMS nJAMS Server or nJAMS Cloud. If you prefer to run nJAMS on-premise, you will choose to install and maintain an nJAMS Server instance on your local machines. On the other hand, if you already use MuleSoft CloudHub you would probably also want to use nJAMS as a Service and go for nJAMS Cloud. See the different architectures depending on where nJAMS is hosted.
What is required to use nJAMS Client for Mule4?¶
nJAMS Client for Mule4 acts as an extension (bean) to the MuleSoft Runtime Engine and runs inside the same JVM. For this reason nJAMS Client for Mule4 is required to be installed on the same machine, where MuleSoft Runtime Engine is running.
Furthermore, nJAMS Client for Mule4 requires an nJAMS Server instance, respectively an nJAMS Cloud instance.