Your web app will be represented on an HP device as a button on the device's front panel. The button information provided to the device will include: the button's icon, the web app's browser shortcut (url and optional device credentials), and optional directives to send device metadata to your web app when your web app is initially loaded by the embedded web browser.
The button information and other information describing your web app (for simplicity, we will simply call this an app) intended for use with any HP device must be specially packaged, submitted to HP for verification and validation (VAV), and finally signed by HP before it can be installed on a device. Once signed, you can distribute it yourself or you can choose or have HP publish it into a global app repository visible to any managed print service provider.
To publish an app, you will need to create a developer publishing account on the HP App Center. HP recommends creating only one publishing account for your company, to be shared by all developers responsible for publishing your company's apps. When signing up, please read the App Center terms and conditions carefully.
(Note: This page is intended only as a brief guide. For detailed instructions on using App Center, please see the App Center Manual.)
To publish an app, follow these steps (which will be explained in detail below):
- Package your app as an HPK and test it on a device with the HPK tool
- Register and upload your HPK on App Center
- In the App Center, submit your app to start the VAV process
- If your app fails VAV, make the recommended changes and resubmit
- Publish your app
- Manage your published app
The following diagram describes the publishing process at a very high level. Please see the App Center Manual for details.
Step 1. Package Your App as an HPK
Any app intended for use on any HP device must be specially packaged into an HPK file. The SDK contains an HPKTool for this purpose. A HPK file includes your web app's button information and other app-related information. The HPKTool will also allow you to test the installation of your unsigned HPK on devices. See the HPKTool User Guide for more information.
On devices where the jetAdvantage Link Platform is enabled, the device will use a new package management API which verifies HPK file signatures. During development, you can turn off the signature verification by enabling LDB Mode. See the Link Platform page for details.
On devices where the Link Platform is unsupported or disabled, the HPKTool will use legacy (OXPd) APIs to install your button information. The legacy API does not perform HPK file signature validation.
Step 2: Register and Upload on App Center
To register and upload your app on App Center, follow these steps:
A. In the Apps view, Click Register new app
B. Click Browse and pick your HPK file
C. Complete the app and VAV information form
Step 3: Submit Your App for VAV
Not that your HPK is uploaded, you can submit it to HP for VAV. Follow these steps:
A. Submit your app to request VAV
B. See how many of your requested apps are in each VAV stage
C. Respond to HP notifications and queries
D. View the current VAV status of each requested app
Step 4: If your app fails VAV
If your app fails VAV, you will be notified in App Center and will be provided with a list of required fixes.
Step 5: Publish Your App
When your app passes VAV, HP will sign it. You may download and distribute the signed HPK to any managed print service provider for installation using any fleet management tool connected to HP's JetAdvantage Management cloud.
At your request, HP will also publish it into our global repository where it can be viewed and installed by anyone through a fleet management App Gallery view (using any fleet management tool connected to HP's JetAdvantage Management cloud) or through a front panel App Gallery view (HP Connected cloud).
Step 6. Manage Your Published App
You can manage your published app as follows:
- Edit your app's information (changes will be reflected in the App Gallery views)
- Publish your app to the global repository
- Stop publishing your app to the global repository (it will be removed from the global repository, but will remain visible in your account view)
- Remove your app from the system (your app will be removed from the global repository, all information about it will be archived, and it will no longer be visible in your account view)