ActiveMQ

Integration with ActiveMQ queue.

Messaging and Conferencing · ActiveMQ

Details

IDActiveMQ
ProviderOpen Source
CategoryMessaging and Conferencing
From Version5.0.0
Docker Imagedemisto/py3-tools:1.0.0.10404775
Supported ModulesAgentix XSIAM

README

Overview


Integration with ActiveMQ.
This integration uses ActiveMQ STOMP protocol, that must be enabled (usually port 61613 by default) in order to work.
Fetch incidents is based on using Durable Topic Subscribers, in order to fetch messages, and convert to Cortex XSOAR incidents.

Use Cases


  • Send messages to queue or topic
  • Read messages from queue or topic
  • Fetch messages from queue or topic and create incidents in Cortex XSOAR per message

Configure ActiveMQ in Cortex


Parameter Description Required
hostname Server IP Address (e.g., 192.168.0.1) True
port Port False
proxy Use system proxy settings False
client-id Client ID False
credentials Username False
client_cert Client certificate (.pem) False
client_key Client certificate key (.key) False
root_ca Root Certificate False
subscription-id Subscription ID False
isFetch Fetch incidents False
incidentType Incident type False
topic-name Topic Name (for subscription) False
queue_name Queue Name (for subscription) False

Fetched Incidents Data


Returns the messages in the queue or topic. Creates incidents in Cortex XSOAR and populate the incident details field
with the message content.

Commands


You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.

  1. activemq-send
  2. activemq-subscribe

1. activemq-send


Sends a message to the specified destination.

Base Command

activemq-send

Input
Argument Name Description Required
destination The message destination. For example, a message queue in the format: “/queue/test”, or a message topic. Required
body The content of the message to send. Required
headers The customer headers for the message, in the format: {XCorrelationId: uid, nosotros generamos XReplyTo demisto:es:connectors, XType com.elevenpaths.sandas.ra.connector.CreateTicketConnectorRequest, XVersion : “3.0”, persistent : True} Optional
Context Output

There is no context output for this command.

Command Example

!activemq-send destination="/topic/demisto-test" body="send the message to topic"

!activemq-send destination="/queue/demisto-test" body="send the message to queue"

Human Readable Output

Message sent to ActiveMQ destination: /topic/demisto-test with transaction ID: 69726a84-ee17-4db5-a6da-5171da9986d3

activemq-subscribe


Subscribes to and reads messages from a topic or queue. Must provide either queue-name or topic-name. You can’t provide both.

Base Command

activemq-subscribe

Input
Argument Name Description Required
subscription-id The subscription unique identifier. Required
topic-name The topic to subscribe to. Optional
queue-name The queue to subscribe to. Optional
Context Output

There is no context output for this command.

Command Example

!activemq-subscribe subscription-id=1 topic-name=demisto-test

Human Readable Output

send to topic message

Configuration parameters

  • hostname — Server IP Address (e.g., 192.168.0.1) (required)
  • port — Port
  • client-id — Client ID
  • credentials — ---------------------------- Basic Authentication ---------------------------- Username
  • client_cert — --------------------- Certificate Authentication --------------------- Client certificate (.pem)
  • client_key — Client certificate key (.key)
  • root_ca — Root Certificate
  • subscription-id — ---------------------------- Fetch Incidents ---------------------------- Subscription ID
  • isFetch — Fetch incidents
  • incidentType — Incident type
  • incidentFetchInterval — Incidents Fetch Interval
  • topic-name — Topic Name (for subscription)
  • queue_name — Queue Name (for subscription)

Commands (2)

  • activemq-send

    Sends a message to the specified destination.

  • activemq-subscribe

    Subscribes to and reads messages from a topic or queue. Must provide either queue-name or topic-name. You can't provide both.

category: Messaging and Conferencing
provider: Open Source
sectionorder:
- Connect
- Collect
commonfields:
  id: ActiveMQ
  version: -1
configuration:
- display: Server IP Address (e.g., 192.168.0.1)
  name: hostname
  required: true
  type: 0
  section: Connect
- defaultvalue: '61613'
  display: Port
  name: port
  type: 0
  required: false
  section: Connect
- defaultvalue: Demisto
  display: Client ID
  name: client-id
  type: 0
  required: false
  section: Connect
- display: '---------------------------- Basic Authentication ----------------------------                         Username'
  name: credentials
  type: 9
  required: false
  section: Connect
- display: '--------------------- Certificate Authentication ---------------------                         Client certificate (.pem)'
  name: client_cert
  type: 14
  required: false
  section: Connect
- display: Client certificate key (.key)
  name: client_key
  type: 14
  required: false
  section: Connect
- display: Root Certificate
  name: root_ca
  type: 12
  required: false
  section: Connect
- defaultvalue: '1'
  display: '---------------------------- Fetch Incidents ----------------------------                         Subscription ID'
  name: subscription-id
  type: 0
  required: false
  section: Connect
- display: Fetch incidents
  name: isFetch
  type: 8
  required: false
  section: Collect
- display: Incident type
  name: incidentType
  type: 13
  required: false
  section: Collect
- display: Incidents Fetch Interval
  name: incidentFetchInterval
  defaultvalue: '1'
  required: false
  type: 19
  section: Collect
  advanced: true
- display: Topic Name (for subscription)
  name: topic-name
  type: 0
  required: false
  section: Collect
- display: Queue Name (for subscription)
  name: queue_name
  type: 0
  required: false
  section: Collect
description: Integration with ActiveMQ queue.
display: ActiveMQ
name: ActiveMQ
script:
  commands:
  - arguments:
    - description: ' The message destination. For example, a message queue in the format: "/queue/test", or a message topic. '
      name: destination
      required: true
    - description: The content of the message to send.
      name: body
      required: true
    - description: 'The customer headers for the message, in the format: {XCorrelationId: uid, nosotros generamos XReplyTo demisto:es:connectors, XType com.elevenpaths.sandas.ra.connector.CreateTicketConnectorRequest, XVersion : "3.0", persistent : True}.'
      name: headers
    description: Sends a message to the specified destination.
    name: activemq-send
  - arguments:
    - defaultValue: '1'
      description: The subscription unique identifier.
      name: subscription-id
      required: true
    - description: The topic to subscribe to.
      name: topic-name
    - description: The queue to subscribe to.
      name: queue-name
    description: Subscribes to and reads messages from a topic or queue. Must provide either queue-name or topic-name. You can't provide both.
    name: activemq-subscribe
  dockerimage: demisto/py3-tools:1.0.0.10404775
  isfetch: true
  runonce: false
  script: '-'
  subtype: python3
  type: python
fromversion: 5.0.0
tests:
- No tests (auto formatted)