RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
If you already have an existing setup of Automatics you can follow the steps in this page for upgrading the software's Automatics Technology Stack - Upgrade
Please note that even though the recommended version of Orchestration is JDK17, it is reverse compatible with JDK11 also. So code also be compiled with JDK11. Follow Steps below to install Java
...
17 on CentOS/linux.
...
Code Block | ||
---|---|---|
| ||
sudo yum -y update |
...
Code Block | ||
---|---|---|
| ||
sudo yum install java-17-openjdk |
...
Code Block | ||
---|---|---|
| ||
java -version |
Sample output:
...
This Scriptless Service uses the Automatics Orchestration database, so for the scriptless service server to start UP it should have access to Automatics Orchestration and the below mentioned tables should be available in that database.
...
Check whether the base URLs of Automatics Orchestration and Scriptless Service application is added to the database. If not added, add it using 'AUTOMATICS_BASE_URL' and 'MICROSERVICE_URL' as the config names in master_config table.
AUTOMATICS_BASE_URL | Base URL of Automatics Orchestration Application |
MICROSERVICE_URL | Base URL of Scriptless Service |
Copy the rackdataservice-1
.0
.0
.jar
of Rackdataservice Scriptless Service to a folder in VM. Create a empty folder with the name as 'logs' outside the folder that contains the Rackdataservice jar file using the command mkdir logs. Run the below command inside the folder that contains the Rackdataservice jar file to bring the Scriptless Service up in the server.
Code Block |
---|
nohup java -XX:+UseSerialGC -Dlog4j2.formatMsgNoLookups=true -jar rackdataservice-1.0.0.jar > logfile.log 2>&1 & |
...