Mulesoft AnypointMQ Configuration

Effortlessly integrate your enterprise systems by configuring the Nodinite Pickup Logging Service to fetch JSON Log Events directly from your Mulesoft AnypointMQ queues. This guide walks you through secure, scalable, and reliable log event collection, ensuring your business-critical data is always available for analysis and compliance.

• ✅ Seamless integration with Mulesoft AnypointMQ
• ✅ Secure and reliable Log Event collection
• ✅ Scalable setup for enterprise environments
• ✅ Long-term storage and compliance-ready

The diagram above illustrates how the Pickup Service interacts with AnypointMQ queues, processes messages, and stores them in the Nodinite Log Database. Invalid messages are routed to the Dead Letter Queue for further review.

Configuring Access to an Anypoint MQ Queue

To configure this card to fetch messages from an Anypoint MQ queue, click the AnypointMQ tab in the Remote Configuration.

1. Enable the configuration by checking the Enabled box.
2. Provide a clear Display Name and Description to identify the purpose.
3. Enter your Username and Password or enable Use Connected App for OAuth-based access.
   • If using OAuth, fill in Client ID and Client Secret.
4. Specify the Queue name you want to consume messages from.
5. (Optional) Set a Dead Letter Queue to capture failed messages.
6. Adjust the Active Consumers value to control the number of concurrent consumers.
7. (Optional) Enable Protected, Is EU Panel, or Use Configuration DB based on your security and data location needs.

Once configured, the system will start polling the queue and logging events according to your settings.

Anypoint MQ Source Configuration Fields

AnypointMQs (versions <7.1.x)

Note

This section applies to versions <7.1.x. Later versions include a Remote Configuration feature that allows configuration via the Nodinite web interface (Web Client).

The AnypointMQs section lets you manage all Mulesoft AnypointMQ sources for your log events.

You configure these sources in the Settings.json file, which uses JSON format. The default path is:

C:\Program Files\Nodinite\Logging Agent - Pickup Service\Settings.json

{
  ...
  "AnypointMQs": [
                      {
      "Enabled": true,
      "LogAPI": "http://localhost/Nodinite/Dev/LogAPI/",
      "UseConfigurationDatabase": false,
      "ConfigurationDatabaseConnectionString": null,
      "ActiveConsumers": 1,
      "Username": "nodinite-reader",
      "Password":"1337",
      "Environment": "prod",
      "EnvironmentId" : "f7a16b7b-1337-4cb5-93ba-1e5289f707ec",
      "OrganizationId": "75ec82b6-f930-4ea2-1337-7c56ee24c9d3",
      "UseConnectedApp": true,
      "IsEuPanel": false,
      "ClientId": "9186414a9dc4dfc94c4ccf670d25e4e",
      "ClientSecret": "replaceme",
      "RegionId": "eu-west-1",
      "Queue": "LogEvents",
      "DeadLetterQueue": "LogEvents.dlq",
       "ReplaceRules": [
        {
          "Name": "Fix Endpoint real customer id to {customerId}",
          "ReplaceName": false,
          "ReplaceUri": true,
          "Pattern": "/([0-9]{4,})$",
          "Group1Value": "{customerId}"
        }]
    }]
  ...                      
}

AnypointMQs is an array of AnypointMQ queue configurations. Each entry defines how the Log Agent connects to and processes messages from a specific AnypointMQ queue. This setup ensures your Nodinite JSON Log Events are reliably collected and managed.

Important

You must restart the Nodinite Pickup Logging Service for configuration changes to take effect.

Next Step

Configure

Related Topics

• JSON Log Event
• Replace Rules