Home › Discussions › Questions & Answers › Mass Migration from BI Publisher/ECC/Polaris
Mass Migration from BI Publisher/ECC/Polaris
Customer · · Questions & Answers · 7 replies
We want to use Blitz Report to pull real-time data from Oracle Enterprise Command Center (ECC) datasets, bypassing the ECC server limitations for large exports. How can I mass import these ECC datasets using an API?
7 replies
To mass import ECC dataset queries, you utilize the PL/SQL procedure `XXEN_API.IMPORT_ECC_DATASET` . This API takes the `p_dataset_key` as input, which identifies the specific ECC data set . An example script, `mass_import_ecc_reports.sql`, is available to automatically import all available ECC queries into Blitz Report . This allows users to access ECC data of unlimited size in a real-time Excel environment .
We also have numerous custom BI Publisher reports that we want to convert. Is there a similar API for mass importing them?
Yes, custom BI Publisher reports are imported using the PL/SQL procedure `XXEN_API.IMPORT_CONCURRENT_PROGRAM` . This function requires the `p_application_short_name` and `p_concurrent_program_name` as parameters . You can use the example script `mass_import_bi_publisher_reports.sql` to import all custom BI Publisher reports where the data source starts with `XX%` . This same `IMPORT_CONCURRENT_PROGRAM` API is also used for migrating Excel4apps Reports Wand reports .
We are migrating reports from Polaris Reporting Workbench (RWB). Does the RWB import process consolidate reports like the Discoverer Folder import does?
Yes, the Polaris Reporting Workbench import process is designed to consolidate reports based on the underlying database views . If multiple RWB reports are based on the same views, they are consolidated into a single Blitz Report . The RWB report-specific column selections are then imported as individual Blitz Report templates associated with the consolidated report .
When importing Polaris RWB reports using the API, how do I control the view expansion setting?
The Polaris RWB import API, `IMPORT_REPORTING_WORKBENCH`, includes the parameter `p_expand_view_sqls` . This parameter accepts values like ‘none’, ‘all’, or ‘custom’ . Setting it to ‘custom’ ensures expansion only for views starting with `XX%` or custom application short names . Views referencing Polaris RWB objects starting with `XXRX%` will be expanded regardless of this setting .
- You must be logged in to reply to this post.
Sign in with LinkedIn or Google to take part.