Create & assign an app profile

Prerequisites

To run this tutorial, you must have a Platform 6 account.

About App Profiles

You need to have an application profile for each application you want to package.

Packaging an app is not mandatory. You may well create an app on one instance, then import all service items to another instance (leveraging the export/import features offered by Platform 6 or thanks to P6 Sync). Now, if you want to distribute your app to a large set of instances, and/or are willing to leverage the various benefits coming with a packaged app (pre-install and post-install scripts, bundled resources, app configuration, etc…), then packaging your app is the way to go.

Once created, the app profile needs to be assigned to the instance(s) on which the app is developed. Having an app profile assigned to an instance will allow you to:

• Tag the service items you create with the related application key
• Package the app, once your development work is finalized

Create an App Profile

App Profiles are created using the CLI utility: p6cmd using a combination of keygen and appaction create options

You will be required to provide an application key (no spaces allowed) and its name in English. Optionally, you can provide your app name in other languages.
We advise you also provide a logo for your app; it is not required, but so much nicer!

Assign an App Profile

An app profile must be assigned to one of your instances if you want to use it. To do this is simple and requires you attaching the profile file (.app) generated by p6cmd to the root node of your instances organisational tree

Note

You will probably need to be an instance admin to perform this operation

Warning

When assigned or unassigned, there is a delay of 6 minutes (defined in P6Auth) before the app is visible to select in the Platform6 Portal.

Edit an App Profile

Editing an app profile is simply the process of regenerating the app profile with p6cmd using the original public/private keys

nce you have made regenerated the .app file simply replace the one you attached to the root of your org tree

Warning

It is essential you use the same public/private keys generated originally using -keygen and the same app.published.id It is good practice to specify a app.published.id each time you generate an app profile otherwise a GUID will be used.