...

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

<distributionManagement>

                        <repository>

             <repository>

                                                              <url></url>

                                    </repository>

 </distributionManagement>     

...

Partner XML configuration file

• Partner can inject their implementation classes to Automatics core using Spring Dependency Injection. 
• Automatics core expects spring configuration file Using Spring DI without modifying Automatics framework classes, we can configure partner-applicationContext.xml file in partner implementation project so that without any changes in framework, DI can be done. Partner implementation classes are injected into core without modifying code to be provided by partner project and it should be available at classpath during test execution.
• All Java API implementations to be injected into should be configured herein partner-applicationContext.xml.
• partner-applicationContext.xml file contains the predefined bean id with respective implementation class and . All beans uses "lazy-init as true, since the instance to be created during runtime and scope is prototype if new instance to be created for each device.

Following are the mandatory or optional instance to be created.

...

Bean Id (Instance to be created)

...

Mandatory or Optional

...

testInitializer

...

Mandatory

...

deviceConnectionProvider

...

Mandatory

...

deviceAccessValidator

...

Mandatory

...

deviceConnectionBasedTrace

...

Mandatory

...

serialConnectionBasedTrace

...

Optional

...

powerProvider

...

Optional

...

deviceProvider

...

Mandatory

...

imageUpgradeProviderFactory

...

Optional

...

serialCommandExecutionProvider

...

Optional

• " set to true so that bean instance will be created on demand only. And, for beans that requires separate instance for each device, property "scope" is set to value "prototype".

...

credentialCryptoProvider

...

Automatics Orchestration - User Manual

...