11. Provisioning View: New Features

(Home)     Previous     Next


1. Deploment of User Application to another Driver Set

The Provisioning view now supports importing a user application driver from one driver set and deploying it to another driver set. This wasn't possible in previous milestones since the Provisioning view didn't support import of runtime configuration objects that weren't editable or viewable in Designer. Examples of runtime configuration objects are proxy definitions, service definitions, etc. At least the containers for these objects are needed in order for the User Application driver to function.

By default, import of a User Application driver will import the runtime configuration objects and prompt whether the runtime configuration objects should be deployed when deploying the User Application. However, it is possible to change this behaviour using the new Import/Deploy preference pane for Provisioning objects.

2. Provisioning View automatically opened

The Provisioning view is now automatically opened when a User Application driver is created or imported. You can turn this off by changing a preference of the Provisioning preference page.

3. Provisioning Preferences

Import and deploy related preferences have been moved from the Provisioning preference page to the new Import/Deploy preference page. The Provisioning preference page now contains a tab for updating the User Application driver configuration file. You can use this tab if for example you have received a driver configuration file with some more appropriate default content or with additional language support.

3.1. Import/Deploy Preferences

The new Import/Deploy preference page allows you to customize part of the import and deployment of provisioning objects. The import content allows you to specify whether to delete a local object during import if the corresponding object has been deleted in the identity vault. Furthermore, you can specify whether to import the runtime configuration objects when a User Application driver or application is imported.



The deploy content makes it possible to deploy objects with validation errors and to turn on/off whether you want to be prompted for deployment of the runtime configuration objects.


4. Integration with Main Menu

The Provisioning view is integrated with the new Live menu in the main menu. For example, if the Directory Abstraction Layer object is selected in the Provisioning view, you can now use Live -> Import to import all Directory Abstraction Layer objects.


Other Enhancements & Bug Fixes
  1. Make Provisioning View more visible - Click here for details...
  2. It should be possible to export multiple objects to file - Click here for details...
  3. Export to file (on Linux) doesn't add file extension - Click here for details...


(Home)     Previous     Next