Install and configure Decision Insight

Introduction

This section presents how to set up a Decision Insight node and configure Prebuilt Dashboards on it.

Install Decision Insight

Configure Decision Insight

  • Before the first start of the platform, choose an application start date, e.g 2017-01-01T00:00:00.000+01:00
  • Update or set the following properties in the platform  conf/platform.properties  file: 
conf/platform.properties
#update the following properties :
com.systar.titanium.initialPeriodValidTimeEnd=[application-start-date-chosen-above]
com.systar.calcium.totalPartitions=16
com.systar.titanium.memtable.globalMaxSize=4G
com.systar.titanium.memtable.individualMaxSize=256M
 
#add the following properties :
com.systar.krypton.scheduler.collector.defaultComputingRhythm.scalar=5
com.systar.krypton.scheduler.collector.defaultComputingRhythm.unit=minutes
com.systar.krypton.scheduler.collector.defaultComputingLag.scalar=30
com.systar.krypton.scheduler.collector.defaultComputingLag.unit=seconds

JVM memory

If the JVM memory XMX is equal or less than 4Gb, you must modify the memory space use by titanium(globalMaxSize).  For example for xmx=4G, in conf/platform.properties the property would be com.systar.titanium.memtable.globalMaxSize=2G


  • Update the JVM memory size in conf/jvm.conf. Please see the sizing guide to use the correct XMX size. Example for 16Gb entering these values in conf/jvm.conf :
conf/jvm.conf
-Xms16G
-Xmx16G
  • Start the platform
  • Download the Prebuilt Dashboards application package from the marketplace.

  • Unzip the dowloaded file
  • In Decision Insight Settings > Platform > Applications > Import the application appx and properties.xml files, using the password 'admin' for import. At this step, set the application import date to the application start date chosen above:


  • In ADI Settings > Data Integration > 
    • In space 04-API-Integration >  Properties, update APPLICATION_START_DATE with the value chosen above

    • Configure the same APPLICATION_START_DATE in space 05-API-Initializer



    • In Platform management > Current Activity, wait until the platform CPU Usage is down to a few percent. This allows time for all pre computings to bootstrap and computings to become LIVE.
    • In space 04-API-Integration > Routes, make sure the route "collectAndProcessEvents" is started. 

    • Create the keystore and trustore for TLS communication with the Filebeat agents. For more information see How to generate keys and certificates files for TLS mutual authentication?. Decision Insight keystore and truststore must be in PKCS12 or JKS format.
    • In HOME > Data Integration > APPLICATION DATA INTEGRATION > ENDPOINTS > Connectors : sslContextParameters, check that the connector information below are present

SSL connector parameters
Name sslContextParameters
Class name com.systar.aluminium.engine.impl.util.SSLContextParameters

keyManagers class: org.apache.camel.util.jsee.keyManagersParameters


keyPassword {{keyStore_password}}

keyStore Class: org.apache.camel.util.jsee.KeyStoreParameters


password {{keyStore_password}}


resource {{keyStore_filePath}}
cipherSuitesList TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

trustManagers class: org.apache.camel.jsee.TrustManagersParameters


keyStore Class: org.apache.camel.util.jsee.KeyStoreParameters


password {{trustStore_password}}


resource {{trustStore_filePath}}
secureSocketProtocolsList TLSv1.2

serverParameters class: org.apache.camel.jsee.SSLContextServerParameters


clientAuthentication REQUIRE


    • In HOME > Data Integration > APPLICATION DATA INTEGRATION > TRANSFORMATIONS > Routes:

Route must use secure lumberjacks uri

the uri in route : collectAndProcessEvents (normally on line 5) must be :  <from uri="lumberjacks:0.0.0.0:5044?sslContextParameters=#sslContextParameters"/>

To use #sslContextParameters : the name of the SSL connector

If you estimate that your network is secure enough and you estimate that you can use an non-secure connection, you can uncomment the uri (line 4) <from uri="lumberjack:0.0.0.0:5044"/>  and comment the secure uri (line 5) <!-- <from uri="lumberjacks:0.0.0.0:5044?sslContextParameters=#sslContextParameters"/> -->


    • In  HOME > Data Integration > APPLICATION DATA INTEGRATION > TRANSFORMATIONS > Properties, add the correct file paths and passwords of the trustStore and the keyStore for Filebeat SSL connection (Lumberjack).

Properties for the SSL connector
keyStore_filePath /path-to-DI-install/DecisionInsight/security/keyStore.jks
keyStore_password ****************
trustStore_filePath /path-to-DI-install/DecisionInsight/security/trustStore.jks
trustStore_password ***************

Set up automated data purge

It is recommended to activate automated data purge to remove old data when they are no longer used.

In the context of the Prebuilt Dashboards for example, setting a retention period for transactions and transaction legs to 1 month allows you to release disk space on a regular basis.

For more information, see Purge data in the Axway Decision Insight product documentation.

Upgrade the Prebuilt dashboards

You have to consider the following elements before performing an upgrade:

  • All custom application items (such as data integration routes and mappings, model entities and attributes, dashboards, indicators) are not guaranteed to be kept after an application upgrade. It is not recommended to perform an upgrade on an application that has already been customized to fit with specific purposes.It is safe to assume that any customization done to the application will not be kept after an upgrade.
  • For safety reasons, create a manual checkpoint using a meaningful comment as described here.

You can perform an upgrade of the Prebuilt Dashboards application by downloading and importing its latest version, as described in the previous section. You might need to upgrade Decision Insight as described in the Axway Decision Insight product documentation. For more information, see Upgrade.


Related Links