This topic describes how to manage the pixel-perfect report components in the folders. It includes setting permissions, downloading and uploading reports and folders, and moving report components in the catalog.
The BI Publisher folders store the reports, data models, and style templates, that you create.
You and every other user have their own personal folders, My Folders. Reports in personal folders can only be accessed by the user who created and saved the content into the folder. You can add subfolders to My Folders to organize the content in the way that's most logical to you.
Note:
The information in this chapter applies to installations of BI Publisher that aren't integrated with the Oracle Business Intelligence Enterprise Edition.
You can also save reports in shared folders where other users or groups can access them. User permissions determine which folders are available to which users. Permissions are assigned at the object-level and determine who can view, edit, and schedule reports within that folder. Your administrator creates and maintains the shared folder structure.
Each reporting component has an identifying icon and lists the creation and modification information. Next to each item is a list of actions you can take.
The following reporting components are shown in the catalog:
Folders
Reports
Data Models
Style Templates
Sub Templates
You can create a subfolder within your My Folder or, if you've the required permissions, you can create a shared system folder.
You can perform tasks such as edit, copy, paste, rename, download, and set permission on catalog objects.
You can perform tasks on objects in multiple ways such as:
By using the links next to the object.
By using the catalog toolbar.
By selecting the object and choosing the task from the Tasks region.
The image shows the Catalog page.
Your access to these actions depends on the permissions granted to you by your administrator.
The download feature of the BI Publisher catalog enables you to bundle and download multi-component objects such as reports in an archive file. You can then use the upload feature to unarchive the data to another location in the catalog.
The ability to download and upload catalog objects enables you to transfer objects across environments. For example, you can use this feature to transfer BI Publisher objects from a development environment to a production environment.
Extensions for Archived Objects table lists the file extensions that BI Publisher assigns to each type of archived object when downloaded.
Catalog Object | Extension Assigned to Downloaded Files |
---|---|
Data Model |
.xdmz |
Folder |
.xdrz |
Report |
.xdoz |
Style Template |
.xssz |
Subtemplate |
.xsbz |
If BI Publisher is integrated with the Oracle Business Intelligence Enterprise Edition, then use the archive and unarchive features of the Oracle BI Presentation Catalog to perform this function.
When you move, cut, rename, or delete a Data Model, a Sub Template, or a Style Template that's used as a resource for a report, the references to the resource are broken and the report can't run as expected.
For example, if you've a report that was created with a data model that resides in a folder called My Data Models, and you move the data model to another folder, the report can't run because the report definition is expecting to find the data model in the My Data Models folder.
If moving a resource object is unavoidable, then you must edit each report that references the object to refer to the object in its new location.
Export and import catalog translation files function enables administrators to export an XLIFF file that contains the translation strings.
For users with administrator privileges, the catalog toolbar includes the Export XLIFF and Import XLIFF function.
This function enables administrators to export an XLIFF file that contains the translation strings the selected catalog object or group of objects. The XLIFF strings can then be translated to the desired target language. After the XLIFF file is translated, the administrator can import the XLIFF file back to the catalog and assign it the appropriate locale.