Configuring the Connection between Analytics On-Premises and AAKE

To use your Analytics on-premises installation with Automic Automation Kubernetes Edition, you have to follow the steps below before migrating your Automic Automation system to the Automic Automation Kubernetes Edition:

1. Upgrade your Analytics on-premises installation to the relevant version. For more information, see Upgrading the Analytics Backend/IA Agent.

2. Define where the new Automic Web Interface in the AAKE cluster can find the Analytics backend (IA Agent) once it is deployed.

   To do so, use the values.yaml file to set the UC_BACKEND_API_KEY and UC_BACKEND_ENDPOINT environment variables. You find these values in the plugin.properties file located in the Tomcat\webapps\awi\config\webui-plugin-analytics folder in your on-premises Analytics directory.

3. Update the INI file of the Analytics backend / IA Agent (ucxedda.ini) accordingly.

   Since the TLS/SSL Agents and in AAKE establish a connection to an Ingress / HTTPS load balancer and not the JCP directly, you have to make sure the Analytics backend / IA Agent can reach the load balancer in AAKE. For more information, see Connecting to AWI, the JCP and REST Processes Using an Ingress.

More information:

• Preparing the Ingress and TLS/SSL Certificates

• Connecting to AWI, the JCP and REST Processes Using an Ingress

• Container-Based Installation - Automic Automation Kubernetes Edition

• Analytics in the Migration Context

See also:

• Preparing for the Container-Based Installation

• Container-Based Installation - Automic Automation Kubernetes Edition

• Configuring Container-Based Systems