Page History

...

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

Execution Environment

• OS - Linux
• Jenkins

Automatics Orchestration

Software Requirement

• JDK 1.8
• MySql 5.0.6
• Tomcat 7.0.92
• Maven 3Linux

Mysql Configuration           

...

• Click on Add New User
  • Enter Preferred User Id: “guest”
  • Enter the user name: “guest”
  • Enter email: guest@automatics.com
  • Select user group: GUEST
• Click on Add New User Group
  • Enter User Group name: GUEST_1
• Click on Delete User Group
  • Select the User Group, you want to delete and click on Delete
• Click on User Group Module Access
  • Select the User Group and click on Fetch Access Rights.
  • Select the access right checkbox of the Module Name, you want to provide access.
  • Click on Save.

Automatics Core

Software Requirement

• JDK 1.8
• Maven 3

Setup

• Pull the Automatics Core project from the repository (rdk/tools/automatics/automatics-core) with branch (“rdk-next”)
• In pom.xml and update the url in distributionManagement with the respective artifact repository url in the place as mentioned below. Automatics core is required to be deployed to partner's repository. Partner implementation project requires core to be added as maven dependency for using its APIs.

...

This project contains the generic test cases which will be executed by Automatics. The automation id and manual id in automated tests should be matching with the automation Id and manual Id present in Automatics orchestration. During test execution the execution status of each test step will be updated to Automatics orchestration. And, at the end final execution status will be updated to Automatics.

Software Requirement

• JDK 1.8
• Maven 3

Set up

• Pull the latest AutomaticsGeneric Test project from the repository (rdk/tools/automatics/generic-automation-tests) with branch (“rdk-next”).
• Update pom.xml with partner project as a dependency.
• Merge the changes so that it will be available during tests execution.

...

• Launch {protocol}// {host:port}/AutomaticsProps/deviceProps.
• User will be redirected to device json page, where it contains the device model based configuration.
• To edit device properties, user has to update the file device_config.json deployed in tomcat server at path apache-tomcat/webapps/automatics/

Software Requirement

• JDK 1.8
• Tomcat 7.0.92
• Maven 3

Setup

• Clone AutomaticsProps project from the repository (rdk/tools/automatics/automatics-props) with branch (“rdk-next”).
• Execute “mvn clean install”, and war file will be generated at target directory.
• Copy automaticsProps.war file to apache-tomcat/webapps directory
• Create a directory named “back_up”, in apache-tomcat and place the sample “automatics.properties” file.  When ever user edits automatics properties, a backup file will be generated inside this directory.
• Create a directory “automatics” inside apache-tomcat/webapps.
• Copy “automatics.properties”, "device_config.json" and “config.properties” from automatics-props\src
• Configure“config.properties” with username and password required for Automatics Properties UI login.
•  Start the server using command ./startup.sh.

...

Automatics performs test execution in Jenkins. User can view the status of Jenkins execution from Job Manager page of Automatics. The final execution status will be updated back to Automatics.

Set up

Steps to be taken care during Jenkins configuration

...