Automatic PowerCenter Mappings and Workflows

• •Batch workflow. Scheduled batch workflow that the Data Integration Hub triggers to process the data.
• •Data processing session. Session with transformations that extract the data from the publication source or write the data to the subscription target. The session also includes a mapping, source and target objects.
• •Reporting session. Session that sends and receives notifications about the publication or subscription process. This session updates the publication or subscription events after processing. The session also includes a mapping, source and target objects.
• •Metadata folders in the PowerCenter repository. The folders contain workflow, mapping, and session information. A separate folder contains publication or subscription metadata. When you create an automatic publication mapping, PowerCenter creates subscription source shortcuts based on the publication target.

Automatic PowerCenter Mappings and Workflows Rules and Guidelines

• •Data Integration Hub creates PowerCenter entities for each automatic mapping. Each PowerCenter entity name starts with the prefix DIH__. Do not manually change or delete the PowerCenter entities.
• •You cannot use high precision processing in PowerCenter to run automatic mappings. To use high precision, use a custom mapping.
• •Do not manually change or delete tables in the publication repository that store data sets from publications with automatic mappings.
• •Automatic mappings run with the DIH__STAGING and the DIH__REPO PowerCenter connections. To prevent publication or subscription failure, do not change or delete the connections.
• •When you publish varbinary or nvarchar datatypes from a Microsoft SQL Server database source, PowerCenter converts the data size limit to a fixed size of 100 MB. If you create a subscription with an automatic mapping that writes the published data to a Microsoft SQL Server database target, you must change the data size limit to MAX when you create the target tables before you run the subscription workflow.
• •When you use tables from a default schema to publish from a relational database or to subscribe to a relational database, the schema name is not persistent.
• •When you use tables from a non default schema to publish from a relational database or to subscribe to a relational database, the schema name is persistent.
• •Schema names are saved in the Mapping tab of the PowerCenter session in the following locations:
• - For publications, the schema name is saved in the Source properties in the Owner Name field.
• - For subscriptions, the schema name is saved in the Target properties in the Target Name Prefix field.

Automatic PowerCenter Mappings and Workflows Logs

Publication workflow logs

The PowerCenter Integration Service creates publication workflows with the following settings:

Parameter	Value
Save Workflow Log By	Runs
Save Workflow Log for These Runs	$PMWorkflowLogCount

The value of $PMWorkflowLogCount in the PowerCenter Integration Service determines the number of logs that the Integration Service creates for each workflow run.

Publication session logs

The PowerCenter Integration Service creates publication workflow sessions with the following settings:

Parameter	Value
Save Session Log By	Runs
Save Session Log for These Runs	$PMSessionLogCount

The value of $PMSessionLogCount in the PowerCenter Integration Service determines the number of logs that the Integration Service creates for each session run.

Subscription logs

The PowerCenter Integration Service creates subscription workflows with a concurrent run set. The number of logs is unlimited with timestamps.