|Re: Handling system bundle updates using SimpleConfigurator and ConfigApplier [message #805471 is a reply to message #800332]
||Thu, 23 February 2012 20:17
| Terran Gilman
Registered: July 2009
I've done some additional research into how the p2 UI manages the update process. From what I can tell, there are some additional utility APIs that we missed in our original effort; namely ProvisioningSession and ProfileChangeOperation.|
I am going to be trying a new approach that uses these classes instead of dealing with the low level p2 APIs. The only thing I don't see in these APIs is some type of cumulative profile change operation. The three subclasses I've found, install, uninstall, and update, handle single or sets of changes that fall into the same category. However, the life cycle we're looking to support requires the ability for a mixed operation.
Change requests will be queued up based on actions taken in the web ui. However, an administrator subsequently needs to initiate a maintenance request at which time any queued requests should be executed. These changes could include installs, updates, and/or removals simultaneously. Is there an existing operation for this type of action or should I create a new subclass using the core of the existing subclasses?
Additional: Can I just execute several install, update, or uninstall operations serially and then apply the entire change set at the end instead of creating a new subclass?
[Updated on: Thu, 23 February 2012 21:24]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02194 seconds