Académique Documents
Professionnel Documents
Culture Documents
1. PowerCenter Domain
2. PowerCenter Repository
3. Administration Console
4. PowerCenter Client
5. Repository Service
6. Integration Service
PowerCenter Domain
A domain is the primary unit for management and administration of services in
PowerCenter. Node, Service Manager and Application Services are components of a
domain.
Node
Node is the logical representation of a machine in a domain. The machine in which the
PowerCenter is installed acts as a Domain and also as a primary node. We can add other
machines as nodes in the domain and configure the nodes to run application services such
as the Integration Service or Repository Service. All service requests from other nodes in
the domain go through the primary node also called as master gateway.
The Service Manager
The Service Manager runs on each node within a domain and is responsible for starting
and running the application services. The Service Manager performs the following
functions,
Application services
The services that essentially perform data movement, connect to different data sources
and manage data are called Application services, they are namely Repository Service,
Integration Service, Web Services Hub, SAPBW Service, Reporting Service and
Metadata Manager Service. The application services run on each node based on the way
we configure the node and the application service
Domain Configuration
Some of the configurations for a domain involves assigning host name, port numbers to
the nodes, setting up Resilience Timeout values, providing connection information of
metadata Database, SMTP details etc. All the Configuration information for a domain is
stored in a set of relational database tables within the repository. Some of the global
properties that are applicable for Application Services like Maximum Restart Attempts,
Dispatch Mode as Round Robin/Metric Based/Adaptive etc are configured under
Domain Configuration
2. PowerCenter Repository
The PowerCenter Repository is one of best metadata storage among all ETL products.
The repository is sufficiently normalized to store metadata at a very detail level; which in
turn means the Updates to the repository are very quick and the overall Team-based
Development is smooth. The repository data structure is also useful for the users to do
analysis and reporting.
Accessibility to the repository through MX views and SDK kit extends the repositories
capability from a simple storage of technical data to a database for analysis of the ETL
metadata.
PowerCenter Repository is a collection of 355 tables which can be created on any major
relational database. The kinds of information that are stored in the repository are,
1.
2.
3.
4.
5.
source data itself is to be understood. Source Analyzer also allows us to define our own
Source data definition.
Warehouse Designer:
Allows us to import target table definitions which could be Relational databases, flat files,
XML and COBOL files. We can also create target definitions manually and can group them
into folders. There is an option to create the tables physically in the database that we do not
have in source analyzer. Warehouse designer doesnt allow creating two tables with same
name even if the columns names under them vary or they are from different
databases/schemas.
Transformation Developer:
Transformations like Filters, Lookups, Expressions etc that have scope to be re-used are
developed in this pane. Alternatively Transformations developed in Mapping Designer can
also be reused by checking the optionre-use and by that it would be displayed under
Transformation Developer folders.
Mapping Designer:
This is the place where we actually depict our ETL process; we bring in source definitions,
target definitions, transformations like filter, lookup, aggregate and develop a logical ETL
program. In this place it is only a logical program because the actual data load can be done
only by creating a session and workflow.
Mapplet Designer:
We create a set of transformations to be used and re-used across mappings
Workflow Manager : In the Workflow Manager, we define a set of instructions called a
workflow to execute mappings we build in the Designer. Generally, a workflow contains a session
and any other task we may want to perform when we run a session. Tasks can include a session,
email notification, or scheduling information.
A set of tasks grouped together becomes worklet. After we create a workflow, we run the
workflow in the Workflow Manager and monitor it in the Workflow Monitor. Workflow Manager has
following three window panes,Task Developer, Create tasks we want to accomplish in the
workflow. Worklet Designer, Create a worklet in the Worklet Designer. A worklet is an object that
groups a set of tasks. A worklet is similar to a workflow, but without scheduling information. You
can nest worklets inside a workflow. Workflow Designer, Create a workflow by connecting tasks
with links in the Workflow Designer. We can also create tasks in the Workflow Designer as you
develop the workflow. The ODBC connection details are defined in Workflow Manager
Connections Menu .
Workflow Monitor : We can monitor workflows and tasks in the Workflow Monitor. We can
view details about a workflow or task in Gantt Chart view or Task view. We can run, stop, abort,
and resume workflows from the Workflow Monitor. We can view sessions and workflow log events
in the Workflow Monitor Log Viewer.
The Workflow Monitor displays workflows that have run at least once. The Workflow Monitor
continuously receives information from the Integration Service and Repository Service. It also
fetches information from the repository to display historic information.
The Workflow Monitor consists of the following windows:
Navigator window Displays monitored repositories, servers, and repositories
objects.
Output window Displays messages from the Integration Service and Repository
Service.
Time window Displays progress of workflow runs.
Gantt chart view Displays details about workflow runs in chronological format.
Task view Displays details about workflow runs in a report format.
Repository Manager
We can navigate through multiple folders and repositories and perform basic repository tasks
with the Repository Manager. We use the Repository Manager to complete the following tasks:
2. Add and connect to a repository, we can add repositories to the Navigator window
and client registry and then connect to the repositories.
3. Work with PowerCenter domain and repository connections, we can edit or remove
domain connection information. We can connect to one repository or multiple
repositories. We can export repository connection information from the client registry to a
file. We can import the file on a different machine and add the repository connection
information to the client registry.
4. Change your password. We can change the password for our user account.
5. Search for repository objects or keywords. We can search for repository objects
containing specified text. If we add keywords to target definitions, use a keyword to
search for a target definition.
6. View objects dependencies. Before we remove or change an object, we can view
dependencies to see the impact on other objects.
7. Compare repository objects. In the Repository Manager, wecan compare two
repository objects of the same type to identify differences between the objects.
8. Truncate session and workflow log entries. we can truncate the list of session and
workflow logs that the Integration Service writes to the repository. we can truncate all
logs, or truncate all logs older than a specified date.
5. Repository Service
As we already discussed about metadata repository, now we discuss a
separate,multi-threaded process that retrieves, inserts and updates metadata in the
repository database tables, it is Repository Service.
Repository service manages connections to the PowerCenter repository from
PowerCenter client applications like Desinger, Workflow Manager, Monitor, Repository
manager, console and integration service. Repository service is responsible for
ensuring the consistency of metdata in the repository.
Creation & Properties:
Use the PowerCenter Administration Console Navigator window to create a Repository
Service. The properties needed to create are,
Service Name name of the service like rep_SalesPerformanceDev
Location Domain and folder where the service is created
License license service name
Node, Primary Node & Backup Nodes Node on which the service process runs
CodePage The Repository Service uses the character set encoded in the repository
code page when writing data to the repository
Database type & details Type of database, username, pwd, connect string and
tablespacename
The above properties are sufficient to create a repository service, however we can
take a look at following features which are important for better performance and
maintenance.
General Properties
> OperatingMode: Values are Normal and Exclusive. Use Exclusive mode to perform
administrative tasks like enabling version control or promoting local to global
repository
> EnableVersionControl: Creates a versioned repository
Node Assignments: High availability option is licensed feature which allows us to
choose Primary & Backup nodes for continuous running of the repository service.
Under normal licenses would see only only Node to select from
Database Properties
> DatabaseArrayOperationSize: Number of rows to fetch each time an array database
operation is issued, such as insert or fetch. Default is 100
> DatabasePoolSize:Maximum number of connections to the repository database that
the Repository Service can establish. If the Repository Service tries to establish more
connections than specified for DatabasePoolSize, it times out the connection attempt
after the number of seconds specified for DatabaseConnectionTimeout
Advanced Properties
> CommentsRequiredFor Checkin: Requires users to add comments when checking in
repository objects.
> Error Severity Level: Level of error messages written to the Repository Service log.
Specify one of the following message levels: Fatal, Error, Warning, Info, Trace &
Debug
> EnableRepAgentCaching:Enables repository agent caching. Repository agent
caching provides optimal performance of the repository when you run workflows.
When you enable repository agent caching, the Repository Service ppository. we can
truncate all logs, or truncate all logs older than a specified date.
5. Repository Service
As we already discussed about metadata repository, now we discuss a
separate,multi-threaded process that retrieves, inserts and updates metadata in the
repository database tables, it is Repository Service.
Repository service manages connections to the PowerCenter repository from
PowerCenter client applications like Desinger, Workflow Manager, Monitor, Repository
manager, console and integration service. Repository service is responsible for
ensuring the consistency of metdata in the repository.
Creation & Properties:
Use the PowerCenter Administration Console Navigator window to create a Repository
Service. The properties needed to create are,
Service Name name of the service like rep_SalesPerformanceDev
The main three components of Integration Service which enable data movement are,
6.2
Load Balancer
The Load Balancer dispatches tasks to achieve optimal performance. It dispatches tasks
to a single node or across the nodes in a grid after performing a sequence of steps. Before
understanding these steps we have to know about Resources, Resource Provision
Thresholds, Dispatch mode and Service levels
1. The Load Balancer verifies which nodes are currently running and enabled
2. The Load Balancer identifies nodes that have the PowerCenter resources required
by the tasks in the workflow
3. The Load Balancer verifies that the resource provision thresholds on each
candidate node are not exceeded. If dispatching the task causes a threshold to be
exceeded, the Load Balancer places the task in the dispatch queue, and it
dispatches the task later
4. The Load Balancer selects a node based on the dispatch mode
1.
2.
3.
4.