Skip navigation

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.


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.



C:\Users\Stefan>java -version

openjdk version "1.8.0_232"

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

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


C:\Users\Stefan>echo %JAVA_HOME%





[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


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.



# optional but recommended

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

mkdir /opt/aurea

vi ./


Insert this as the content of the








Then run these shell commands:


chmod +x CXMonitor_Management_Server_Enterprise_2020_R1_LNX.bin

./CXMonitor_Management_Server_Enterprise_2020_R1_LNX.bin -f


# optional but recommended

chown -R aurea:aurea /opt/aurea

Windows: file content:







Then run:

./CXMonitor_Management_Server_Enterprise_2020_R1_LNX.exe -f


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/ (alternative is /opt/aurea/monitor/DefaultProfile/bin/ and add these lines:



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



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




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




Aurea Messenger:\aurea\Messenger\MQ10.0\lib/*.jar

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









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 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

Today, I wanted to remind you about Adobe’s plan to “end- of-life” Flash.  On December 31st of this year, Adobe will officially stop supporting and distributing Adobe Flash. Subsequently, all major browsers (including Internet Explorer, Microsoft Edge, Firefox, Google Chrome and others) will discontinue and block Adobe Flash from being used effectively ending an era of internet technology .


What does this mean for your Aurea products?

Previous versions of Aurea Process and Aurea Monitor depend on Adobe Flash for specific capabilities in the user interface.  Adobe Flash is a core component in the UI in the existing versions that most of you have deployed and are using today.  Due to the end-of-life of Flash these capabilities will no longer work in most browsers and will not continue to be supported by Aurea.

Aurea Process
If you’ve already upgraded to the Aurea Process 2020.1 release, Flash has been completely removed,replacing the components with identical, non-Flash based capabilities.

If you haven’t upgraded to Aurea Process 2020.1 yet, our Professional Services team offers a Standard Upgrade package that can get you on the latest, non-Flash version quickly and affordably. The package upgrades the installation components and up to 10 applications deployed on your platform in a non-production environment. Additionally we will provide you with a playbook for promoting the environment to production. Finally, it also includes 30 days of post migration support.

Aurea Monitor

Currently, Adobe Flash powers the user interface that allows you to visually walk through a particular flow to the root cause analysis in Aurea Monitor. It is also used for other features including flow maps and dashboards.

In the next Aurea Monitor release coming later this year, Adobe Flash will be completely removed however, the upgrade is not a drop in replacement.  There have been architectural changes in the product that will require the Agents and the Intermediaries to be installed in a slightly different manner.

Read more about the changes to Aurea Monitor architecture here

While it is not a difficult upgrade, it will require preparation and several new steps you may not be familiar with. For most Aurea Monitor customers, we recommend a Standard Upgrade package to make the entire process simple and seamless.


Our Standard Package  allows you to quickly upgrade from any Monitor version (2013 or later) to the latest release, Aurea Professional Services will help you upgrade one Management Server and up to 20 Monitor Agents in a non-production environment.  Once successful, you simply promote it into your production environment.


The standard package also includes 30 days of post-migration support to help customers make the upgrade as smooth as possible. 


Contact Us to learn more about Upgrade Assistance


With nearly half the year behind us, it’s time to start planning. The sooner we help you upgrade to the new version, the less risk you incur by still being dependent on Adobe Flash.