This tutorial covers how to replace data models in Interactive Reporting documents using Impact Manager.
This tutorial covers the following topics:
|Importing Replacement Data Models|
|Updating Data Models with Impact Manager|
Click icon to show all screenshots
Note: Alternatively, you can click an individual icon (or image) associated with each step to view (or hide) the screenshot associated with that step.
This tutorial covers how to use Impact Manager in Workspace to update Interactive Reporting data models. In OBEs 1 through 5 in this series, you learned to create data models in Interactive Reporting Studio to accommodate various database changes. Now you are ready to import the final updated data model into Workspace and replace old data models with this new version.
You created an Interactive Reporting document named BMV Datamodel.bqy, which you plan to use to update data models in Workspace. You first need to import the document into Workspace. Next, you need to synchronize metadata to ensure that all Workspace content is harvested. Lastly, you need to configure Impact Manager to replace the data models in Sales1.bqy, Sales2.bqy, and Sales3.bqy with the updated data model in BMV Datamodel.bqy.
Before starting this tutorial, you should:
|1.||Complete the first four OBEs in this series.|
Import Bookmart Sample Database.oce into Workspace. In Configuration and Management Console (CMC), configure Interactive Reporting Data Access Service to connect to the Bookmart data in Oracle. You created the OCE in OBE 2: Accommodating Database Table and Column Name Changes.
Import Interactive Reporting documents ( Sales1.bqy, Sales2.bqy, and Sales3.bqy) that contain old data models into Workspace at the root directory level. Associate all Query sections with Bookmart Sample Database.oce.
|4.||Have available BMV Datamodel.bqy, which you last updated in OBE 4: Accommodating Deleted Columns in Databases.|
BMV Datamodel.bqy accommodates all database changes. In order for Impact Manager to use this data model, you must import the document into Workspace.
To import BMV Datamodel.bqy into Workspace, perform the following steps:
Log on to Workspace:
a) In a browser window, enter the URL for Workspace, which is http://localhost:19000/workspace.
b) In the User Name and Password boxes, enter the user name and password, and click Log On.
c) Access the Explore module.
In the View pane, right-click the Root directory, and select Import > File.
The General properties page is displayed.
Browse to and select BMV Datamodel.bqy, and click Next.
The Interactive Reporting Properties page is displayed.
For the Query section, select Bookmart Sample Database.oce and Defaults, and click Finish.
BMV Datamodels.bqy is imported into Workspace.
In this topic, you synchronize metadata in Workspace. This operation enables you to harvest new documents that have not yet been harvested or that have changed since the documents were last harvested. Documents in Workspace that were opened, modified, and resaved are also harvested. You can harvest immediately or by schedule (date and time).
To synchronize metadata:
In Workspace, select Navigate > Impact Manager > Synchronize Metadata.
Under Synchronize Options, select a scheduling option, and click Submit.
In this example, "Run now" is selected so that the synchronization runs immediately. If you select Schedule, you also need to select a date and time.
You update harvested data models in Workspace to reflect changes in underlying databases. When you update, you complete the following tasks:
1. Decide whether to provide update parameters interactively or through a task definition file. Task definition files are text files that you import into Workspace. They contain one line for each document to be transformed.
2. Optional: Select an original data model to be updated. Do this only if you want the system to find the set of update candidate documents that contain an instance of the selected data model. That is, you want all documents that contain the same topics as the selected replacement data model.
3. Select a replacement data model to replace the appropriate data models found in the update candidate documents.
4. Select update candidates. The system searches for data models that match the required criteria. You then select one or more of the documents that you want to update.
5. Schedule the update request. Transformation requests can run in the background or during off-peak hours.
To update data models in Sales1.bqy, Sales2.bqy, and Sales3.bqy, perform the following steps:
In Workspace, select Navigate > Impact Manager> Update Data Models.
The Specify Data Models page is displayed.
Under Task Description, enter a name for the task; for example, Update Sales Documents.
Select Specify documents and data models interactively.
Select Match the full data model.
Click Browse, and select a file that contains the original data model; for example, Sales1.bqy.
Select the original data model; for example, DataModel (Query).
Click Browse, and select the replacement data model file; for example, BMV Datamodel.bqy.
From the list, select the replacement data model; for example, DataModel (Query).
The Candidates page is displayed, and the sales documents are listed.
Select Sales1.bqy, Sales2.bqy, and Sales3.bqy, and click Next.
The Scheduling page is displayed.
Select a scheduling option, and click Finish.
In this example, the Run now option is selected.
A message is displayed that the update task is submitted.
|13.||In the Explore module, right-click Sales1.bqy, and select Open As > Interactive Reporting Web Client. |
View the data model.
The updated data model is displayed in the Query section.
You successfully configured Impact Manager to replace the data models in Sales1.bqy, Sales2.bqy, and Sales3.bqy.
In this lesson, you learned how to perform these tasks:
|Import replacement data models into Workspace|
|Synchronize metadata in Workspace|
|Update data models with Impact Manager|
To learn more about Impact Manager, you can refer to other OBEs in this series on the OTN Web site:
|OBE 1: Harvesting Meta Data in Documents|
|OBE 2: Accommodating Database Table and Column Name Changes|
|OBE 3: Accommodating Denormalization of Database Tables|
|OBE 4: Accommodating Deleted Columns in Databases|
|OBE 5: Identifying Impacted Documents|
|OBE 6: Replacing Data Models in Impacted Documents (Currently displayed)|