You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Automatics - Introduction

Automatics is a test setup for verifying RDK builds. It can be integrated with CI flow to validate new changes checked in by user. Also, user can trigger automated tests against given RDK builds.

Hence, Automatics helps in faster release of RDK builds by validating builds using automated test execution. The results of test execution can be viewed from results page of Automatics.

Automatics Setup

Setup details will guide the user to setup Automatics system in their environment.  It includes following details.

  • Setup details of Automatics Orchestration
  • Setup for Automatics Core
  • Configuration of Jenkins jobs for test execution
  • Setup details of Automatics Property

Automatics Orchestration

Software Requirement

  • JDK 1.7
  • MySql 5.0.6
  • Tomcat 7.0.92
  • Maven 3

Mysql Configuration           

  • Create database with name ‘automatics’.
  • Execute the script 'Automatics_DB.sql' that is available with Orchestration source at 'automatics\resources\'. Now the Automatics tables are created with basic configuration data.

WAR Generation

  • Pull the latest Automatics Orchestration tool project from the repository (rdk/tools/automatics) with branch “rdk-next”.
  • After taking the pull, do “mvn clean install” then war file will be generated and will be present inside Automatics/release/Automatics-v0.1/ folder inside the project.
  • Rename war to Automatics.war.

War Deployment

  • Copy the Automatics.war file to the apache-tomcat/webapps folder.
  • Copy the restartTMR.sh file which is inside Automatics/config to apache-tomcat/bin folder.
  • Copy “hibernate.cfg.xml”(inside Automatics/config folder) and “log4j.properties”(inside Automatics) files to any specific location,
  • Update “hibernate.cfg.xml” with database user name and password. And the password updating in "hibernate.cfg.xml” should be Base64 encoded. And, the DB name should be 'automatics'.
  • Add the following params to JAVA_OPTS inside apache-tomcat/bin/catalina.sh file   

-DAutomatics -DhibernateUI.config.file = {path to hibernate config file} -DloggerUI.properties.file = {path to log properties file} 

  • Create empty files childUI.jmd and mainUI.jmd in apache-tomcat/bin/. This is required by orchestration for job scheduling.
  • Navigate to apache-tomcat/bin directory and start the server by executing command.

./startup.sh

  • To verify the server logs, navigate to logs directory (apache-tomcat/logs) under tomcat. 
    • catalina.out - server start up logs
    • automatics_{time_stamp} - Automatics logs
    • traces/trace_automatics_{time_stamp} - Automatics trace logs
  • To stop the server type ./shutdown.sh.



Automatics Core


Automatics Generic Tests


Automatics Properties


Automatics Partner Implementation


Automatics Orchestration - User Manual




  • No labels