Merge pull request #13 from oracle-devrel/iot

Iot

Author: martatolosa

IoTSonnenUploader/DigitalTwin/AnalyticsDBAccess.txt

@@ -25,7 +25,6 @@ export IDCS_DOMAIN_NAME=<the name of your IDCS instance, e.g. iotdomain or Defau
 export IDCS_IOT_GROUP_NAME=<the name of the IDCS group you created, this could be the same one you used for ORDS if you've set that up>
 export OCI_TENANCY_OCID=`oci iam compartment list --query 'data[?contains("compartment-id", \`.tenancy\`)]."compartment-id" | [0]' --raw-output`
 
-export OCI_TENANCY_OCID=`oci iam compartment list --query 'data[?contains("compartment-id", \`.tenancy\`)]."compartment-id" | [0]' --raw-output`
 
 
 oci iot domain configure-direct-data-access --iot-domain-id $IOT_DOMAIN_OCID --db-allow-listed-identity-group-names '["'$OCI_TENANCY_OCID':'$IDCS_DOMAIN_NAME'/'$IDCS_IOT_GROUP_NAME'", "'$OCI_TENANCY_OCID':OracleIdentityCloudService/Domain_Specialists"]'  --wait-for-state SUCCEEDED --wait-for-state FAILED

IoTSonnenUploader/DigitalTwin/Instructions.txt

@@ -298,7 +298,7 @@ While it's running look at the output and check that the CommandDemoPlaceholder
 oci iot digital-twin-instance get-content  --digital-twin-instance-id $DIGITAL_TWIN_INSTANCE_OCID | jq -r '.data'
 
 Let's upload the command to the IOT service
-oci iot digital-twin-instance invoke-raw-json-command --digital-twin-instance-id $DIGITAL_TWIN_INSTANCE_OCID --request-endpoint house/sonnencommand/tims --request-data '{"commandIdentifier": "SET_PLACEHOLDER", "data":"I am another placeholder"}' --request-data-content-type application/json --request-duration PT10M --response-duration PT10M --response-endpoint house/sonnencommandresponse/tims
+oci iot digital-twin-instance invoke-raw-json-command --digital-twin-instance-id $DIGITAL_TWIN_INSTANCE_OCID --request-endpoint house/sonnencommand/$DEVICE_ID --request-data '{"commandIdentifier": "SET_PLACEHOLDER", "data":"I am another placeholder"}' --request-data-content-type application/json --request-duration PT10M --response-duration PT10M --response-endpoint house/sonnencommandresponse/$DEVICE_ID
 
 you will see the client receive the command and process it and send the response, you can also check the database contents using SQL developer :
 select * from RAW_COMMAND_DATA order by time_created desc

IoTSonnenUploader/DigitalTwin/ORDSDataAccess.txt

@@ -13,6 +13,9 @@ export IOT_ORDS_OAUTH_ID=<Client id from OAUTH Integrated application config pag
 export IOT_ORDS_OAUTH_SECRET=<Client secret from OAUTH Integrated application config page - shown at step 18/19>
 export IOT_IDENTITY_DOMAIN_HOST=<From the identity details at step 31>
 
+#assuming the above all worked then you can configure the IoT to use the IDCS
+oci iot domain configure-ords-data-access --iot-domain-id $IOT_DOMAIN_OCID --db-allowed-identity-domain-host $IOT_IDENTITY_DOMAIN_HOST   --wait-for-state SUCCEEDED --wait-for-state FAILED
+
 # this uses the above to get the token and so on
 export IOT_IDENTITY_DOMAIN_HOST_SHORT=`echo $IOT_IDENTITY_DOMAIN_HOST | tr '.' ' ' | awk '{print $1}'`
 export IOT_IDENTITY_DOMAIN_URL=https://$IOT_IDENTITY_DOMAIN_HOST:443/oauth2/v1/token

IoTSonnenUploader/pom.xml

@@ -138,6 +138,11 @@ SOFTWARE. -->
 			<artifactId>lombok</artifactId>
 			<!--<version>${lombok.version}</version>-->
 		</dependency>
+		<dependency>
+			<groupId>com.oracle.demos.experiential.addons</groupId>
+			<artifactId>gamevideouriuploader</artifactId>
+			<version>0.2.4</version>
+		</dependency>
   </dependencies>
   <build>
     <plugins>