Build & Deploy Your Applet Via Core App with built-in Applet

Have more questions? Submit a request

This provisioning is mandatory for any device running on the free Device Plan Open; optionally, this process is also available for any device under any other plan.

Core App with built-in Applet allows you to compile a native application with your Applet into a single package. This way, once you install the bundled package, your Applet immediately starts up and the device is Auto-Verified in your account.  

Prerequisites

  • Develop, build and upload your Applet to signageOS using signageOS CLI (Read more here)

Steps for building and deploying Core App with built-in Applet

  1. Generate Core App with built-in Applet from the Applet detail for any supported device
  2. (Optional) Upload the generated package to your server
  3. Install from provisioning link (or your own server) to devices
  4. Auto-Verification of the device

1. Generate your Core App with your built-in Applet

  1. Navigate to Box to the Applet section:
  2. Open the detail page of your Applet and click Device-app Builder
  3. Go to the Build tab and find the platform you want the Core Apps to be built for
  4. Click the Build button and wait for the process to finish (it might take up to 20 minutes)
  5. Once the building process is done, continue to [3] Install from the provisioning link
  6. (Optional) Download the zip files and continue with the next step

applet_builder_1.png

applet_builder_2.png

2. (Optional) Upload the generated package to your server

This step is optional. If you do not want to host the bundled package on your own server, continue to [3] Install from the provisioning link.

For your convenience, signageOS provides you with free temporary hosting for your Core app with a built-in Applet on 9900.io and 0099.io domains. You can use the generated URL for provisioning the device of your choice.

Both domains are owned and managed by signageOS.

At this point, the Core App with built-in Applet is generated and you can download the package by clicking on the Download link:

mceclip0.png

As a result, a ZIP package will be downloaded.

  1. The *.zip you download from the Box includes all necessary files required by each platform for installation and provisioning.

    build-open-core-apps.pngzip_app_structure.gif
  2. Unzip the zip package and upload all files and folders to your server with no modification. Always keep all files and folder structure unchanged.
  3. Make sure that files are available within the devices' network.

Always upload the whole structure to your server! In case you miss any file or change folder structure, the installation process will not work.

We recommend using Amazon S3 or Azure Blob Storage as your static servers.

If your files are uploaded to your server, continue with the following step.

3. Install from the provisioning link (or your own server)

It's recommended to use the provisioning links provided by signageOS on the 0099.io and 9900.io domains. If there is a need for using your server, make sure you uploaded all files and folders.

  1. Note down your provisioning links:mceclip1.png
  2. Follow the standard provisioning guide for each respective platform

Anytime the provisioning guide mentions any Core App URL use YOUR server URL where you uploaded your apps instead of the generic signageOS URL

4. Auto-Verification of the device

Any device on which you install Core App with built-in Applet is automatically verified and provisioned into your signageOS account. The device will appear under the same Organization as the Applet.

Important notes related to this type of provisioning

Reference folder structure for all platform types

If you download all Core Apps with your built-in Applet, you will get set of .zip files for each platform:build-open-core-apps.png

Once unpacked, you will get the following list of ready-to-be-installed files:build-open-core-apps-extracted.png

Tizen-specific installation URL

Always copy all folders and files to your static server including *.wgt AND sssp_config.xml files.

Correct URL for Tizen URL Launcher
Always point the URL Launcher in the Tizen display to the FOLDER where is located the *.wgt file:
https://my-super-cms/tizen-app

Never put the file itself to the URL Launcher address. Example below is INCORRECT:
~https://my-super-cms/tizen-app/my-tizen-app.wgt~

Test that the URL will work
To test your URL will work properly, access your server from browser and try to get the sssp_config.xml file.

Example of such URL is: https://t.signageos.io/sssp_config.xml.

If your sssp_config.xml file is NOT reachable on the network, the app installation on Tizen will NOT work!

tizen_installation_url.png

Was this article helpful?
0 out of 0 found this helpful
Share