What is the difference between a Generic content package and Standard content package?

Esprida LiveControl offers to types of digital content packages: Standard and Generic. What’s the difference?

Generic Content Package
• Used exclusively for the distribution of files or folders to a device through the Esprida LiveControl Agent.

• Simpler to use: The user does not need to have any programing skills to create and distribute the content package. Esprida LiveControl will build the Install, Activate, Deactivate and Uninstall scripts required for the content package.

• Requires the user to enter the destination path for the file or folder when the content package is being uploaded.

• The distribution of the files or folders occurs immediately upon transfer of the files to the device. A generic content package does not run the Activation script and therefore the user will not be required to enter an activation time for the content package like occurs with a standard content package.

• The Deactivation script is never run.
• The Uninstall script will be executed when the content package is ‘Detached’ (Devices Module) or the device is removed from the content schedule (Digital Content module). The Uninstall script will not remove the files or folders that were distributed in the content package. The Uninstall script only removes the content package from the path were is was downloaded and sends a signal to the Esprida LiveControl Server that the package was removed.

Standard Content Package
• The most flexible method for delivering content to a device through the Esprida LiveControl Agent. If it can be done in a script it can be accomplished through a properly coded content package.

• Requires some experience with scripting languages such as VBS, Windows batch files, Linux shell scripting, Perl scripting etc. The user must create the 4 required scripts that will be run for the content package Install, Activate, Deactivate and Uninstall sequences.

• The user has completed control over what actions will occur on the device during Install, Activate, Deactivate and Uninstall sequences.

Can I use environment variables in the path for a Generic content package?
Yes. Environment variables are supported in the path for a generic content package. The path format is:

%Environment_Variable%/folder1/folder2

Why can’t I see my device when I’m trying to assign a Digital Content schedule to it?

There are two possible reasons why a device will not appear when trying to assign a Content Package schedule to it.

  1. A device can only be assigned a Content Package through one schedule. If you don’t see your device in the list of available devices when assigning your schedule, the device must already be assigned the Content Package through another schedule for that package
  2. A Content Package developed for the Windows platform cannot be distributed to a Linux device or vice versa. The target platform for the Content Package can be seen in the top of the left pane on the Select Target Devices page. Check the platform for the device to see if it matches the content package platform.

How do I assign a Schedule to a device?

From the Digital Content Module, click the radio button beside the desired Content Package, then click the View Schedule button. The displayed page will show any existing digital content schedules associated with this content package. Select the radio button beside the schedule to be assigned and click the Assign to Devices button. This will display the Select Target Devices page. From here:

  • Navigate to the organization for the device(s) that the schedule will be assigned to
  • Check the box beside each device that will be assigned to the schedule
  • Click the Finish button

How do I Create a Schedule for a Digital Content Package?

From the Digital Content Module, click the radio button beside the desired Content Package, then click the View Schedule button. The displayed page will show any existing digital content schedules associated with this content package. To create a new schedule:

  • Click on Create a new schedule.
  • Provide a Schedule name and description appropriate for the schedule (optional)
  • Set the Start Distribution On Date if you wish the package to be distributed at a time later then immediately
  • Select and set the Window Transfer file between times to transfer the package during a specific window of time.
  • After selecting the Next button you will be able to set activation and deactivation times.
  • The next screen will allow you to review your choices. After clicking the Finish button a screen will be displayed indicating that the Schedule was successfully created.
  • Click on Digital Content Module again to go back to the Digital Content main page. Once there, click the radio button beside the Content Package and click the View Schedule button This will display the list of created Schedules including the one just created.

How do I upload a Digital Content Package to the Server?

An Easy way is through a Generic Package upload. From the Digital Content Module:

  • Click on Upload a new Content Package.
  • Select the organization name and category and provide a Content Package name, your name as the author and a short description of what the content package does
  • Select the Generic Package Upload check box
  • In the Deploy Path field, enter the full destination path where the file or folder will be copied on the target device(s)
  • Select the platform the content package will be deployed on (i.e. Windows or Linux) and then click the Next button
  • Select the file or folder from your local computer that you wish to distribute
  • When a message is displayed showing a successful upload click the Next button
  • A review page showing the choices made during this process will be displayed. If correct click the Next button to continue the Package Creation process
  • When the content package has been successfully created click on the Digital Content Module again to display the complete list of content packages associated with your organization including your newly created content package.