I always ask me where the upk materials are stored, for example, screen shots, packages, web pages, etc, but I always forget it.
In fact, the folder path storing above materials is defined by yourself when you create UPK profile. One UPK installation can have a lot of profiles. The profile in UPK is similar with the mechanism of the user in operating system. Every profile can have its own development configuration, library and source document path.
When you add a new profile, you can specify the folder path for this profile in you OS. You can also specify a share folder in your file server. It helps you on backup and source code control.
Oracle suggests this folder has more than 600MB space, as UPK development source code is a little bigger. Because UPK records your every screen dumps and action with your additional explanations.
You can still change this folder path in the future days through “Edit Profile”. UPK will move all your development documents from old folder to new folder.
UPK stands for “User Productivity Kit”. It’s an Oracle product which help user/customer develop, manage and publish elearning materials or project documents.
Generally, UPK has two installation mode, single developer mode and multi-user server/client mode.
For multiple user installation, you can backup and recovery your UPK configuration and development source code from server client.
For single developer installation, you need to user Export/Import function to fulfill backup and recovery requirement.
1. Select the folder or document you want to backup. If you want to backup all documents, select “/” root folder.
2. Go to menu -> Tools -> Export -> Documents…
3. Enter backup file name. The backup file is a zip file with extension name .odarc.
4. Select the option “Export my selection and related documents”
5. Click “Export”
The backup file will be a zip file with extension name .odarc. I suggest to define a name convention like “user name_profile name_backup date.odarc”.
As similar as export steps, use “Import” function above “Export” in Tools menu.
1. Root module (highest level) is always ignored to publish, even though it may be linked with pages.
2. If topic has not been recorded with any screen dump, it will be ignored to publish, even though it may be linked with pages.
3. If section is at leaf level and it is not linked with any pages, it will be ignored to publish.
4. If section is not at leaf level and it is not linked with any pages, it will be published normally. But if its child section/topic should not be published against rule 2&3, it will be ignored to publish as well as its child.