1.How does the statement ‘Single point of Integration’ suits the data integrator?
DI combines both batch data movement and management with caching to provide a single data integration platform for information management from any information source and for any information use
2.State and explain the key function of data integrator.
Loading data: Loading ERP or Enterprise application data into an operational datastore and update in batch-time
Routing request: Creates information requests to a DW or ERP system using complex rules
Applying transaction: DI can apply data changes in a variety of data formats and any custom format.
3.State and explain various data integrator components.
Designer: Is development interface that allows creating, testing and manually executing jobs that load a DW. Function performed is data mapping, transformation and control logic.
Repository: Set of tables that hold user-created and predefined system objects, metadata, transformation etc.
Local repository: Used to store definitions of DI obj and source/target metadata.
Central repository: Used to support multi-user development. Provides a shared obj library.
Service: Starts Job Server when the system is restarted.
Component: Job Server:
Includes: Administrator: Includes scheduling, starting& stopping real-time services, managing adapters etc.
Metadata Reporting: Provides browser based reports on Enterprise metadata stored in the DI repository.
5.Explain the process of running a job from designer.
The Designer tells job server to run the job. The job server then gets the job from associated repository and starts an engine to process the job.
6.Explain job server and engine.
when jobs are executed, the DI engine starts the data movement engine that integrates data from heterogeneous sources, performs complex data transformations and manages extraction and transactions in the ETL process.
7.State the various function of administrator.
Scheduling, monitoring & executing batch job. Managing User.
Configuring, starting and stopping real-time service.
Configuring and managing adapters
8.What are the various analyses present with Data Integrator and BO Enterprise?
Datastore analysis: Use reports to see whether the following BI reports uses data from tables that are contained in Business Views, Crystal Reports, and Universe etc.
Dependency analysis: Search specific objects in repository and understand whether they impact or are impacted by other DI or BO universe or reports.
Universe analysis: View universe class and object lineage
Business view analysis: View data sources for Business Views in the CMS
Report analysis: View data sources for reports in the CMS
9.State and explain the various management tools in data integrator.
Repository Manager: Allows creating, upgrading and checking the versions of local and central repositories.
Server Manager: Allows adding, deleting or editing properties of Job Server
10.Name some common DI Objects
Projects, Jobs, Work flows, Data flows, Scripts, Transforms
11.Distinguish between single-use objects and reusable objects
Single-use objects: > Appear only as components of other objects
> Cannot be copied
> operate only in the context in which they are created.
Reusable objects: > has a single definition
> All calls to the object refer to that definition.
> If the definition of the object is changed in one place then the change is reflected in all other called objects
12.How can the behavior of various objects be changed?
Options: Control the obj
Properties: Describe the obj
Classes: the obj are of two classes: Single-use, Reusable.
13.State relationships between work flow and data flow.
A work flow is incorporation of several data flows into a coherent flow of work for an entire job.
A data flow is the process by which source data is transformed into target data
14.State the common characteristics of a project
They are listed in the local obj library,Only one project can be open at a time,They cannot be shared among multiple users.
15.State and explain various phases of DI development process.
Design: Define objects & build diagrams that instruct DI in data movement requirements.
Test: Here DI is used to test the execution of application. Can test for errors & trace flow of execution.
Production: set up a schedule in DI to run the application as a job. Whenever can return to design phase.