products:profilemanager
Differences
This shows you the differences between two versions of the page.
|
products:profilemanager [2008/04/06 11:42] andreas created |
products:profilemanager [2023/11/19 22:46] (current) |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== ProfileManager ====== | ====== ProfileManager ====== | ||
| + | |||
| ===== System Overview ===== | ===== System Overview ===== | ||
| Line 18: | Line 19: | ||
| The previous paragraph has explained that iNEWS stores the profile of a user into the Windows registry. The iNEWS client can also be forced to load the profile of a user from the registry. The ProfileManager basically works with these two iNEWS features. To get a users profile the profile information can be exported from the Windows registry after the user closed the iNEWS client. The profile information can be saved somewhere else and if the same user wants to log in again she can chose one of the previously saved profiles available. After the user chose a profile the ProfileManager writes this profile into the Windows registry and forces iNEWS to start using the profile from the registry. | The previous paragraph has explained that iNEWS stores the profile of a user into the Windows registry. The iNEWS client can also be forced to load the profile of a user from the registry. The ProfileManager basically works with these two iNEWS features. To get a users profile the profile information can be exported from the Windows registry after the user closed the iNEWS client. The profile information can be saved somewhere else and if the same user wants to log in again she can chose one of the previously saved profiles available. After the user chose a profile the ProfileManager writes this profile into the Windows registry and forces iNEWS to start using the profile from the registry. | ||
| + | |||
| + | {{products:profilemanager-lifecycle.jpg|}} | ||
| To store the profile after it has been exported from the Windows registry the ProfileManager uses the iNEWS database itself. The ProfileManager expects the home directory of the user to have a profiles queue. Each story in this queue is expected to be a profile. | To store the profile after it has been exported from the Windows registry the ProfileManager uses the iNEWS database itself. The ProfileManager expects the home directory of the user to have a profiles queue. Each story in this queue is expected to be a profile. | ||
| Line 53: | Line 56: | ||
| * Initial version | * Initial version | ||
| + | |||
| Line 59: | Line 63: | ||
| Some of the following links are restricted to specific users. Read the overview on page [[:welcome|Welcome]] who has which permissions. | Some of the following links are restricted to specific users. Read the overview on page [[:welcome|Welcome]] who has which permissions. | ||
| - | [[bugs-features:profilemananger|Bugs & Features]] | + | [[bugs-features:profilemanager|Bugs & Features]] |
| [[downloads:profilemanager|Downloads ProfileManager 2.0 and higher]] | [[downloads:profilemanager|Downloads ProfileManager 2.0 and higher]] | ||
products/profilemanager.1207482166.txt.gz ยท Last modified: 2023/11/19 22:45 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
