P. 1
Understanding the Repository Overview

Understanding the Repository Overview

|Views: 457|Likes:
Published by ypraju

More info:

Published by: ypraju on Dec 22, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

09/22/2010

pdf

text

original

Understanding the Repository Overview

By PenchalaRaju.Yanamala The PowerCenter repository is a relational database managed by the Repository Service. The repository consists of database tables that store metadata. Metadata describes different types of objects, such as mappings and transformations, that you can create or modify using the PowerCenter Client tools. The Integration Service uses repository objects to extract, transform, and load data. The repository also stores information such as permissions for users. All repository clients access the repository database tables through the Repository Service. The Repository Service protects metadata in the repository by managing repository connections and using object-locking to ensure object consistency. The Repository Service also notifies you when another user modifies or deletes repository objects that you are using. Each Repository Service manages a single repository database. You can configure a Repository Service to run on multiple machines, or nodes, in the domain. Each instance running on a node is called a Repository Service process. This process accesses the database tables and performs most repository-related tasks. The Repository Service uses native drivers to communicate with the repository database. PowerCenter Client tools and the Integration Service communicate with the Repository Service over TCP/IP. When a repository client connects to the repository, it connects directly to the Repository Service process. You administer the repository using the Repository Manager client tool, the PowerCenter Administration Console, and the pmrep and infacmd command line programs. You can connect to and manage multiple repositories. A repository domain is a group of repositories in the PowerCenter Client. Repository domains share metadata through a special type of repository called a global repository. When you configure shared folders in a repository, you can share the objects in the folder with other repositories in the repository domain. You share objects to reuse metadata. Note: A repository domain is different from a PowerCenter domain, which is the primary unit of administration for the PowerCenter environment. For more information about repository domains, see PowerCenter Repository Domains. For more information about PowerCenter domains, see the PowerCenter Administrator Guide. If you have the team-based development option, you can enable the repository for version control. You can store multiple versions of objects in a versioned repository. You can also perform change-management tasks such as version comparison, change tracking, labeling, and deployment. Repository Architecture

The PowerCenter repository resides in a relational database. The repository database tables contain the instructions required to extract, transform, and load data. Repository clients access the repository database tables through the Repository Service. A repository client is any PowerCenter component that connects to the repository. The Repository Service manages repository metadata transaction requests from repository clients. Each Repository Service manages a single repository. The Repository Service uses object-locking to ensure the consistency of metadata in the repository. A Repository Service process is a multi-threaded process that fetches, inserts, and updates metadata in the repository database tables. A Repository Service process is an instance of the Repository Service that runs on a particular machine, or node. The Repository Service accepts client metadata transaction requests from the following PowerCenter components: PowerCenter Client tools. Use the Designer to create and store mapping metadata in the repository. Use the Workflow Manager to store workflow metadata and connection object information in the repository. Use the Workflow Monitor to retrieve workflow run status information and session logs written by the Integration Service. Use the Repository Manager to organize and secure metadata by creating folders. You can manage the repository from the PowerCenter Administration Console. pmrep and infacmd. Use pmrep to perform repository metadata administration tasks, such as listing repository objects. Use infacmd to perform service-related functions, such as creating or removing a Repository Service. Integration Service. When you start the Integration Service, it connects to the repository to schedule workflows. When you run a workflow, the Integration Service retrieves workflow task and mapping metadata from the repository. During the workflow run, the Integration Service writes workflow status information to the repository.

The following process describes how a repository client connects to the repository database: The repository client sends a repository connection request to the master gateway node, which is the entry point to the domain. This is node B in the 1.diagram. The Service Manager sends back the host name and port number of the node running the Repository Service. In the diagram, the Repository Service is running on node A. If you have the high availability option, you can configure 2.the Repository Service to run on a backup node. The repository client establishes a link with the Repository Service process on 3.node A. This communication occurs over TCP/IP. The Repository Service process communicates with the repository database 4.and performs repository metadata transactions for the client. Version Control If you have the team-based development option, you can enable version control for the repository. A versioned repository stores multiple versions of an object. Each version is a separate object with unique properties. PowerCenter version control features allow you to efficiently develop, test, and deploy metadata into production. During development, you can perform the following change management tasks to create and manage multiple versions of objects in the repository: Check out and check in versioned objects. You can check out and reserve an object you want to edit, and check in the object when you are ready to create a new version of the object in the repository. Compare objects. The Repository Manager, Workflow Manager, and Designer

allow you to compare two repository objects of the same type to identify differences between them. The PowerCenter Client tools allow you to compare objects across open folders and repositories. You can also compare different versions of the same object. Track changes to an object. You can view an object history that includes all versions of the object. You can also compare any version of the object in the history to any other version. You can see the changes made to an object over time. Delete or purge a version. You can delete an object so that it no long appears in the PowerCenter Client. However, you continue to store deleted objects in the repository. If you decide later that you need a deleted object, you can recover it from the repository. When you purge an object version, you permanently remove it from the repository. Use global objects such as queries, deployment groups, and labels to group versioned objects. Object queries, deployment groups, and labels are global objects that exist at the repository level. When you group versioned objects, you can associate multiple objects into logical categories. For example, you can create a deployment group that contains references to objects from multiple folders across the repository.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->