Privately and publicly releasing the version

Privately released versions are only available in the "Library" section of your own hub. Released versions are available in the "Library" section for consumers (other hubs) of your app.

Requirements

• The version has been created and all required files related to the version have been uploaded.
• Your hub information (described in the "Requirements" subsection) is provided to the Industrial Edge Support.

Procedure

1. Click the drop-down list under the "Status" column and select "Private release".

   

   A warning message is displayed.

   

   The uploaded files are displayed and will be used for the version you want to privately release.

2. Check again your provided information.
   To privately release your version, it is mandatory to upload the correct files.

3. When the information are correct, privately release the version by clicking "Ok".
   The "Preparing for private release" status and a progress bar is displayed.
   The system checks your version information through extracting the uploaded app files. In detail, the system checks the following:

   • App binary and version: The app binary must contain the same version as the version that you have entered during the creation of the version.
   • App ID: The app ID is generated by the app export tool, for example the IE App Publisher, and is stored in the detail.json file. When it is the first version to release privately, the system accepts the "product_id" value and stores it along with the version. For upcoming versions, you have to provide app files which contain the same "product_id" value as your previous versions. Otherwise, the system rejects the private release. If the private release is rejected, the version is reverted to the "Created" status and the rejection reason is displayed. Also, an email will be sent to the respective user.

   Also by activating the version, a request is sent to the App Signing Service to sign unsigned app versions. In the background, the App Signing Service creates certificates to display the authenticity of the app. If the authenticity of the app is given, the version will be signed.

4. Wait until the version privately release is completed.
   This process may take up to 5 minutes, the progress is displayed via the progress bar.
   When the private release has failed, you receive an according notification.
   When the private release inclusive app signing was successful, the version status displays "Privately released". Once the version has been signed, the app provider is verified by Industrial Edge and the version is marked with the icon.
   You can also download the *.app file and check the signed certificates in the "digests.p7s" folder.
   After private release of the version, you can do the following via the corresponding icons under the "Actions" column:

   • Transfer the version to an IEM instance
   • Delete version

   You can use activated app versions only within the same hub.

5. If the version is tested successfully and if you want to prepare releasing the device application to the global IE Marketplace, click the drop-down list under the "Status" column and select "Public release". Released app versions can also be used by other hubs.
   Again a warning message is displayed.

6. Check again your provided information.

7. To release the version, click "Ok".
   Once the version is released, the version status displays "Publicly released".

   

If you have released several app versions of the same app, always the latest semantic version is available for customers.