In my previous blog I explained the new architecture of Aurea Monitor.

As you can imagine the architectural changes also impact the installation and basic configuration of the product.

 

From an installation perspective, there are four components:

 

  • Database
  • JMS Server
  • Management Server
  • Launcher (Agent/Intermediary)


Let’s go through them one by one and guide you through the installation process.

Note that I will install everything on localhost.

Therefore please pay attention to hostnames, usernames, and passwords when you follow this.


Database:

Aurea Monitor requires an RDBMS (MSSQL or Oracle) to persist the statistical data. The Derby database option is only supported for basic testing and does not work well under load.

A fast database will ensure a responsive Management Server user interface.

Ensure you have a database setup and ready.

During the Management Server setup tables and other database objects will be created.


JMS Server:

The communication between the Agent/Intermediary and the Management Server is done via JMS. You have the choice between three supported and certified JMS implementations:

 

  • Aurea Messenger / Sonic
  • Software AG Universal Messenger
  • ActiveMQ

 

Usually, the load on these JMS servers is very low and you can run them together with the Management Server.

 

For Aurea Messenger (Sonic):

If you have Aurea Messenger in place then it is recommended to simply run another broker instance (does not have to be CAA).

If you prefer a dedicated install, then follow the installation guide to install the domain manager.

To keep it simple and given the low volume you can point the Management Server to the management broker itself.

In any case, it is required to adjust the maximum temporary queue size to e.g. 10000KB.

 

For ActiveMQ: Download it and follow the instructions to install and run it.

 

For Software AG UM: Follow the Software AG product installation instructions.



Management Server:

Your database and your JMS provider should be up and running and reachable from the server that will host the Aurea Monitor Management Server.

 

First, verify that you have Java 8 on your PATH and that it is a supported version. The easiest way to do this is on the command line (shell). Also, ensure that JAVA_HOME is set.

 

Windows:

C:\Users\Stefan>java -version

openjdk version "1.8.0_232"

OpenJDK Runtime Environment Corretto-8.232.09.1 (build 1.8.0_232-b09)

OpenJDK 64-Bit Server VM Corretto-8.232.09.1 (build 25.232-b09, mixed mode)

 

C:\Users\Stefan>echo %JAVA_HOME%

C:\java\jdk

 

Linux:

 

[root@centos7-box /]# java -version

java version "1.8.0_191"

Java(TM) SE Runtime Environment (build 1.8.0_191-b12)

Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

[root@centos7-box /]# echo $JAVA_HOME

/usr/java/default


We certify with Amazon Corretto 8.

Adjust your path and installed Java version as needed (e.g. set JAVA_HOME and add %JAVA_HOME%\bin to the PATH).

 

I usually recommend using the silent installer to install the product. Mainly as it gives you a reproducible way of installing/scripting.

Therefore this is what I will explain here.Of course, we also ship a GUI installer.



Linux:

 

# optional but recommended

useradd --no-create-home --shell /bin/false aurea

mkdir /opt/aurea

vi ./install.properties

 

Insert this as the content of the install.properties:

 

INSTALLER_UI=silent

debug.mode=true

debug.file=/tmp/AureaMonitor/server_install.log

USER_INSTALL_DIR=/opt/aurea/monitor

lgserver.jetty=true

docs.all.docs=true

 

Then run these shell commands:

 

chmod +x CXMonitor_Management_Server_Enterprise_2020_R1_LNX.bin

./CXMonitor_Management_Server_Enterprise_2020_R1_LNX.bin -f install.properties

 

# optional but recommended

chown -R aurea:aurea /opt/aurea



Windows:

 

Install.properties file content:

INSTALLER_UI=silent

debug.mode=true

debug.file=D:/temp/server_install.log

USER_INSTALL_DIR=D:\\aurea\\MonitorServer

lgserver.jetty=true

docs.all.docs=true

 

Then run:

./CXMonitor_Management_Server_Enterprise_2020_R1_LNX.exe -f install.properties

 

After running the silent installer you should have Monitor Server installed.

You can verify that the DefaultProfile has been created:

 

Linux: /opt/aurea/monitor/DefaultProfile

Windows: D:\aurea\MonitorServer\DefaultProfile

 

DO NOT start the Monitor Server yet!

The reason is that the initial profile creation will otherwise not automatically take the JMS settings into account which we will add now.

If you did already, no worries.

You can manually add them or contact Aurea Support to assist.

 

Next, we have to tell the Monitor Server where our JMS provider is located and where the JMS client JAR files are.

 

Linux: Create/Edit /opt/aurea/monitor/common/scripts/post-custom.sh (alternative is /opt/aurea/monitor/DefaultProfile/bin/env.sh) and add these lines:

 

ActiveMQ:

actional_append_cp /opt/activemq/activemq-all-5.11.1.jar

actional_sys_prop always.recreate.initial.settings true

actional_sys_prop ConnectionFactoryExt activemq.js

actional_sys_prop com.actional.jms.ext.activemq.url failover:tcp://localhost:61616

#actional_sys_prop com.actional.jms.ext.activemq.username <username>

#actional_sys_prop com.actional.jms.ext.activemq.password <password>

actional_sys_prop com.actional.destPrefix actional.Test

ACTIONAL_JAVA_MAXMEMORY=10240

 

Aurea Messenger:

actional_append_cp /opt/aurea/messenger/MQ10.0/lib/mfcontext.jar

actional_append_cp /opt/aurea/messenger/MQ10.0/lib/sonic_Crypto.jar

actional_append_cp /opt/aurea/messenger/MQ10.0/lib/sonic_Client.jar

actional_append_cp /opt/aurea/messenger/MQ10.0/lib/sonic_XA.jar

actional_append_cp /opt/aurea/messenger/MQ10.0/lib/mgmt_client.jar

actional_sys_prop always.recreate.initial.settings true

actional_sys_prop ConnectionFactoryExt sonicmq.js

actional_sys_prop com.actional.jms.ext.sonicmq.url tcp://localhost:2506

actional_sys_prop com.actional.jms.ext.sonicmq.username Administrator

actional_sys_prop com.actional.jms.ext.sonicmq.password Administrator

actional_sys_prop com.actional.jms.ext.sonicmq.initialConnectTimeout 60

actional_sys_prop com.actional.jms.ext.sonicmq.faultTolerant true

actional_sys_prop com.actional.jms.ext.sonicmq.faultTolerantReconnectTimeout 60

actional_sys_prop com.actional.jms.ext.sonicmq.pingInterval 30

actional_sys_prop com.actional.jms.ext.sonicmq.socketConnectTimeout 10000

actional_sys_prop com.actional.destPrefix actional.Test

ACTIONAL_JAVA_MAXMEMORY=10240



Windows:

 

Create/Edit the D:\aurea\MonitorServer\common\scripts\post-custom.conf, see example content below:

 

ActiveMQ:

append.java.classpath=C:\java\activemq\activemq-all-5.11.1.jar

system.property.com.actional.jms.ext.activemq.url=failover:tcp://localhost:61616

#system.property.com.actional.jms.ext.activemq.username=<username>

#system.property.com.actional.jms.ext.activemq.password=<password>

system.property.ConnectionFactoryExt=activemq.js

system.property.com.actional.destPrefix=actional.Test

system.property.always.recreate.initial.settings=true

 

Aurea Messenger:

append.java.classpath=D:\aurea\Messenger\MQ10.0\lib/*.jar

system.property.ConnectionFactoryExt=sonicmq.js

system.property.com.actional.jms.ext.sonicmq.url=tcp://localhost:2506

system.property.com.actional.jms.ext.sonicmq.username=Administrator

system.property.com.actional.jms.ext.sonicmq.password=Administrator

system.property.com.actional.jms.ext.sonicmq.initialConnectTimeout=60

system.property.com.actional.jms.ext.sonicmq.faultTolerant=true

system.property.com.actional.jms.ext.sonicmq.faultTolerantReconnectTimeout=60

system.property.com.actional.jms.ext.sonicmq.pingInterval=30

system.property.com.actional.jms.ext.sonicmq.socketConnectTimeout=5000

#system.property.com.actional.destPrefix=actional.Test

system.property.always.recreate.initial.settings=true



Once you are done with this you can finally start the Aurea Monitor Server.

 

Windows:

D:\aurea\MonitorServer\DefaultProfile\bin\StartCXMonitorServer.cmd

 

Linux:

/opt/aurea/monitor/DefaultProfile/bin/StartCXMonitorServer.sh

 

 

Open a browser and navigate to: http://localhost:4040/lgserver

Press START and follow the wizard instructions:

 

 

After you provided the license and defined username/password for the admin account, the database connection can be configured.

You can also configure the database later (via http://localhost:4040/lgserver/admin/configure/logging_db_list.jsp)  and leave it as ‘none’ for now.

 

With this, the basic setup of the Management Server is completed.

 

Launcher:

 

Launcher profiles can now be configured on the server side in order to launch an Agent/Intermediary.

The launcher itself is a 5MB zip file that you can extract on the target machine, or you simply run it as Docker container.

You only have to adjust the configuration.json to point it to the profile you want to use.

 

An Agent profile will save interceptors locally and allow you also to define SDK system properties as part of the profile. This also impacts how you instrument a system and reference interceptor JARs.


An Intermediary profile defines which provisioning packages to load. These packages contain the configuration definitions for service groups to load.

 

In my next post, I will explain how to migrate a 10.x Intermediary configuration to 11.x