IGEL App Creator Portal
Requirements
UMS 12.04 or higher
IGEL OS 12.5 or higher
Account at the IGEL Customer Portal
Login to the IGEL App Creator Portal
Click Login.
Use your IGEL credentials (the same credentials as in the IGEL Customer Portal or the IGEL App Portal)
The landing page of the App Creator Program is shown.
Every time the page refreshes, all data is cleared and a new isolated session is created in the backend.
The App Creator Program Components
Download Code Signing Certificate
Here you can download the Code Signing Certificate which you will upload to the UMS and assign to the devices later on.
Download build logs
Here you can download an igelpkg.log
for troubleshooting purposes.
User Profile
Here you can find your user details.
Creating the App in the IGEL App Creator Portal
Providing the Recipe
Click on the field Upload Package and clone a Git repository or upload a downloaded App recipe zip file.
For information on how to get a Git repository or an app recipe zip file, see the following links:
Choose the file you want to upload and click Open.
The file name and size appear under the Upload Package field.
Click Upload.
The recipe is uploaded and unzipped.
Providing the Binaries
If the recipe needs an App Binary, the same steps can be taken in the Provide Binaries section. If there is no need to upload binaries, you can go ahead and click Create (upper right corner).
Binary Archives Must Be Put Into a Zip File Before Uploading
If you want to upload one or more binary archives, you must put them into a zip file first, even if there is only one binary archive.
Example: To upload the binary archive mybinary.tar.gz
to the App Creator portal, you must first put this file into a zip file, although it is already an archive file. The same is true for other archive formats, e.g. mybinary.deb
.
The contents of the outer zip file can have the following formats:
.tgz
.gz
.zip
.deb
.bz2
Background: The App Creator Portal expects a zip file with one or more binary archives inside and performs a corresponding unzipping routine.
In the notice dialog, click Acknowledge to proceed.
The build process starts.
Once the build process is finished, click Download in the lower left corner.
Once downloaded, the uploaded data will be removed after 9 seconds.
You can now download the log file via the Download build logs button.
The certificate can be downloaded via the Download Code Signing Certificate button.
The certificate and the app can now be uploaded to the UMS and assigned to the devices.
As a customer, you have ONE Customer App Signing Certificate; you do not need to roll out the same certificate every time.