Original Message:
Sent: 11/9/2021 8:07:00 AM
From: GENARO NIETO FERNANDEZ
Subject: RE: Java SOAR Messaging engine connection
I have created a repository.
This is a work in progress. Just code for testing the integration. I know, there are credentials in the code, but while that is not a good practice, those are just valid for my own local instance of Resilient.
------------------------------
GENARO NIETO FERNANDEZ
------------------------------
Original Message:
Sent: Mon November 08, 2021 12:28 PM
From: Leonardo Kenji Shikida
Subject: Java SOAR Messaging engine connection
I am interested in your solution. Do you think you can share it in a GIT or something like that?
TIA
Leo
leoks@br.ibm.com
------------------------------
[]
Leonardo Kenji Shikida
------------------------------
Original Message:
Sent: Mon November 08, 2021 09:29 AM
From: GENARO NIETO FERNANDEZ
Subject: Java SOAR Messaging engine connection
Hi group (again)!
I just solved the issue. A stupid bug in the code.
So, now I am capable of sending information to a queue from Resilient and read that information in my Java code.
If anyone is interested in the solution, just let me know.
Next Step: receiving notifications when an incident has not been solved in time.
Thanks!
------------------------------
GENARO NIETO FERNANDEZ
Original Message:
Sent: Mon November 08, 2021 09:01 AM
From: GENARO NIETO FERNANDEZ
Subject: Java SOAR Messaging engine connection
Thanks!
Today I almost managed to solve the problem. Yes, I found somewhere that the queues are called action+org+name. The problem was I tried to write on that queue (in order to have something to read). And it seems no one is allowed to write.
I have modified a rule so that incident information is sent when created. Now I receive this warning in my Java console:
WARN | Received a message on a connection which is not yet started. Have you forgotten to call Connection.start()? Connection: ActiveMQConnection
So, the information arrives but it seems I am having a coding issue with Java. I am using ActiveMQ. ActiveMQ, which I had not used previously, probably is not required if using plain JMS (I am not sure as I have not indicated STOMP in the connection URL). So I am now wondering why I am receiving that warning as I have started the connection. Well, I think so.
Saludos / Best regards
| Genaro Nieto Fernández | | |
| IBM Corporate Security Architect | | Telf.: (34) 91.397.6611 |
| IBM CHQ | eMail: genaro@es.ibm.com |
| | | |
| | | |
Salvo indicado de otro modo más arriba / Unless stated otherwise above:
International Business Machines, S.A.
Santa Hortensia, 26-28, 28002 Madrid
Registro Mercantil de Madrid; Folio 1; Tomo 1525; Hoja M-28146
CIF A28-010791