Configuration Cnode


Post-installation

  • Open the web landing page by typing hostname/IP address of the Cnode in a browser. Via the page, you can get access to Alertflex management console or admin UI for ActiveMQ, MISP, Payara AS.

For login to Alertflex management console use default user admin, password was set in env.sh file.

../_images/main-page.png
  • In the management console select “Settings/Project/Edit/Scope”, view “Licence Agreement” and enable “Alerts Management”.

../_images/project-enable.png
  • Download SSL certificate for Alertlex collector (altprobe).

../_images/project-ssl.png
  • Copy value of parameter Project-ref, it also will be required during the installation of Alertflex collector.

../_images/project-id.png
  • For enabling of MISP feeds, login to MISP admin console via web landing page (default user admin@admin.test, password admin).

../_images/misp-feeds.png
  • In Alertflex management console open “Settings/Integrations/CTI” panel and select checkbox “Enable IOC check”

../_images/misp-config.png
  • Reboot Linux system or restart Payara server (see paragraph “Troubleshooting” below how to restart Payara AS)

  • Now, Central node should be ready for service and you can start the installation of collectors (altprobe)


Increase the AS Payara JVM heap size

By default, Payara AS uses 512 MB of memory for JVM heap. This size of memory isn’t enough for the production deployment of Alertflex. If your computer/virtual machine has more than 4 Gb memory, you can change JVM heap size via Payara AS admin console or by commands:

../_images/payara-jvm.png
./asadmin
create-jvm-options '-Xms3g'
create-jvm-options '-Xmx3g'
delete-jvm-options '-Xmx512m'
restart-domain domain1

Troubleshooting

  • Open ActiveMQ console (default user admin, password was set in env.sh file). Check messages in Queues panel, the amount of Messages Enqueued should be equal to the amount Messages Dequeued.

../_images/activemq.png
  • Reload Alertflex applications if required

../_images/payara-reload.png