Professional Documents
Culture Documents
Code Pages
Command Line Programs
Data Analyzer (PowerAnalyzer)
Data Profiling
Data Stencil (Visio Client for PowerCenter)
Domains
Integration Service
Metadata Manager (SuperGlue)
Repository and Repository Service
Transformations and Caches
Unstructured Data
Web Services Provider
Workflow Monitor
XML
PowerCenter Connects
PowerExchange Client for PowerCenter
1. Code Pages
PowerCenter 8.1.1 supports the following code pages:
IBM833
IBM 834
IBM850
IBM933
Alert. Added commands for the following actions: subscribe to, remove from, list or update SMTP options,
and list alert users.
Domain. Added commands related to service levels and domain options.
Folder. Added commands for the following actions: create, get info about, list, move, move objects between,
remove, and update.
Node. Added commands for the following actions: get node name, list node options, and switch to gateway or
worker node.
Service. Added commands for the following actions: list nodes assigned to service, list services, and create
or update SAP BW Service.
User. Added commands for the following actions: add, create, remove users, or reset password.
4. Data Profiling
Partitioning. We can create multiple partitions for profile sessions containing source-level and column-level
functions.
Data Profiling Data Analyzer reports. We can view the Join Complexity Evaluation and Intersource Structure
Analysis Data Profiling reports through Data Analyzer. We can use the new Data Analyzer Intersource
Function Statistics composite report and Intersource Function Metadata report to view profile statistics for
intersource functions.
6. Domains
6.1. Alerts
Subscribe to alerts. We can subscribe to alerts to receive email notification about node events such as node failure or
a master gateway election. When we subscribe to alerts, we receive notifications for all domains and services we
have permission on.
6.2. Users
Set permissions by user. We can view and edit permissions and privileges for each user on the
Administration tab. We can assign multiple permissions to a user when we add a user account or edit the
permissions.
Status added to each log event. The User Activity Monitoring report shows the status of each log event. The
report indicates whether each log event succeeded or failed.
Operating mode. We can run the Integration Service in safe mode to limit access to the Integration Service
during deployment or maintenance. We can enable the Integration Service in safe mode and we can
configure the Integration Service to run in safe mode on failover.
Resource provision thresholds. We can configure resource provision thresholds for each node in a grid to
cause the Load Balancer to consider or eliminate a node for the dispatch of a task. We can define the
Maximum CPU Run Queue Length and Maximum Memory % thresholds in addition to Maximum Processes.
Dispatch mode. We can configure the way the Load Balancer dispatches tasks by setting the dispatch mode
for the domain. We can choose round-robin, metric-based, or adaptive dispatch mode.
Service levels. The Load Balancer uses service levels to determine the order in which to dispatch tasks from
the dispatch queue. We create service levels in the Administration Console. When we configure a workflow,
we assign a service level to the workflow.
Section Scope
[Global] Parameters and variables defined in this section apply to all Integration Services and
Integration Service processes in the domain, plus all workflows, worklets, and sessions.
[Service:Integratio Parameters and variables defined in this section apply to the named Integration Service,
n_Service_name] plus all workflows, worklets, and sessions the service runs.
[Service:Integratio Parameters and variables defined in this section apply to the Integration Service that runs
n_Service_name.ND:n on the named node (the Integration Service process), plus all workflows, worklets, and
ode_name] sessions the service process runs.
The parameters and variables we define in these sections apply when we run a workflow or session that uses the
parameter file.
Expanded support for parameters and variables. We can use parameters and variables in the following places:
6.8. Performance
Pushdown optimization. We can push transformation logic to the source or target database when the Lookup
transformation contains a lookup override. To perform source-side, target-side, or full pushdown optimization
for a session containing lookup overrides, configure the session for pushdown optimization and select a
pushdown option that allows us to create views. We can also use full pushdown optimization when we use
the target loading option to treat source rows as delete.
Sorter transformation. The Sorter transformation has been enhanced to use a more compact format which
will significantly reduce the temporary disk space necessary to sort large a data set that does not fit into in-
memory sort. In addition, the sort algorithm is improved to significantly reduce sort time.
6.10. Targets
Generate flat file targets by transaction. We can generate a separate flat file target each time the Integration Service
starts a new transaction. We can dynamically name each file. To generate a separate output file for each transaction,
we add a FileName port to the flat file target definition. When we connect the FileName port in the mapping, the
Integration Service writes a target file at each commit. The Integration Service uses the FileName port value to name
the output file. We can generate output files from source-based or user-defined commits.
7.1. Administration
Authentication. We can use LDAP for Metadata Manager on JBoss Application Server, WebLogic Application
Server, or WebSphere Application Server.
Clustering. We can use clusters for the Metadata Manager application on JBoss Application Server,
WebLogic Application Server, or WebSphere Application Server. We use clusters to distribute the Metadata
Manager application load across multiple machines. Clustering may increase performance when the
application has a large number of concurrent users.
Secure Sockets Layer (SSL). We can configure Metadata Manager to use the SSL protocol to provide a
secure and authentic connection between the Metadata Manager server and a web browser client.
7.2. Installation
Sybase ASE. We can install the Metadata Manager Warehouse and PowerCenter repository for Metadata Manager
on Sybase ASE.
7.3. Utilities
EAR Repackager utility. The EAR Repackager utility extracts files from and repackages customized files to
the Metadata Manager EAR file. We may need to customize files in the Metadata Manager EAR file to
customize the Metadata Manager images, color schemes, style sheets, or configuration files.
License Update utility. The License Update utility updates the Metadata Manager license. We may need to
update an existing license with a new license key to extend the expiration date.
Repository Backup utility. The Repository Backup utility backs up and recovers a Metadata Manager
repository.
DWH – PC8 New Features & Enhancements Page 5 of 7
WK: 1 - Day: 6.1
Update System Accounts utility. The Update System Accounts utility modifies the user name and password
for the Metadata Manager system administrator and system daemon.
7.4. XConnects
Business Objects XConnect. The Business Objects XConnect extracts metadata from Business Objects XI.
PowerCenter XConnect. We can configure the PowerCenter XConnect to capture information about flat file
sources, lookups, and targets that are specified in parameters files. We can view the flat files in data lineage
and where-used analysis.
Cancel auto-reconnect. In the Designer, Workflow Manager, and Repository Manager, we can temporarily
disable PowerCenter Client resilience to prevent the client from attempting to reestablish a repository
connection during the resilience timeout period. We cancel automatic reconnection if we do not want to wait
for the 180-second resilience timeout period to expire.
Purge object versions. We can purge object versions from the repository or folder. We can purge versions of
all deleted objects or objects deleted before a specified end time. We can also purge specified versions of
active objects based on a cutoff time. We specify the versions by designating the number of checked-in
versions to keep, by setting a purge cutoff time, or both. We can preview the purge results to verify that the
purge criteria produce the expected results. We can also save the purge results to an output file.
http://<hostname>:<portnum>/PowerCenter
http://<hostname>:<portnum>/wsh
13. XML
XML foreign key column names. We can configure the Designer to prefix generated foreign key columns with the
name of the XML view and the name of the primary key column.
Each secure daemon instance authorizes a set of trusted users. The secure daemon allows a client transport
to connect if the client presents valid identification as an authorized user.