RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Details are available in the below links,
For a partner to upgrade Automatics to support scriptless executions need to be done as mentioned below.
For a partner to upgrade the 3.0 support in Automatics orchestration Please follow below steps.
Scriptless Service provide the support of API to required for new UI pages added for scriptless automation in Automatics. Hence setting up microservice is an integral part of upgradation
Refer Automatics 3.0 Scriptless Service Setup for more details on setting up microservice.
Generic 3.0 APIS are defined in Automatics Core , RDKV-Utils(applicable for rdkv executions) and RDKB-Utils(applicable for rdkb executions). hence latest code of mentioned projects need to be deployed to the articrafts.
Refer Jenkins Deployment Jobs for more details on how to create deployment jobs for the mentioned projects.
Utlity Parser jobs need to be triggered for Automatics core , scriptless-automation , RDKV-utils (for RDKV executions) or RDKB-utills (for RDKB executions) to scan the 3.0 API details defined in the mentioned projects and updated to Automatics.
Refer Automatics 3.0 Utility Parser Jobs for more details on how to create individual parser jobs for mentioned projects .
Add the base URLs of Automatics Orchestration and Scriptless Service application in database, which will help in the communication between one and another. Use 'AUTOMATICS_BASE_URL' and 'MICROSERVICE_URL' as the config names for adding the base URLs of orchestration and microservice in master_config table.
AUTOMATICS_BASE_URL | Base URL of Automatics Orchestration Application |
MICROSERVICE_URL | Base URL of Scriptless Service |
Update below parameters to Automatics properties these urls need to be defined to support 3.0 Executions
predefined_ds_bulk_url= <Scriptless Service Bsse Url>/addBulkPredefinedEntries
service.base.url=<Scriptless Service Base URL>