Developer Guide

10.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1

Back Next

Creating the Source Definition for a Subscription Workflow

Creating the Source Definition
for a Subscription Workflow

In the PowerCenter Designer, create the source and define the source properties

of a subscription workflow. When you develop a publication workflow, you define the source based on the application from which you want to publish data

The source definition process includes the following steps:

Create the source object.

Set the source connection to DIH__STAGING. You create a source based on the topic structure from the publication repository. You can copy the source from the publication metadata folder in the PowerCenter repository.

Add ports to the source object. Add port information as properties in the JMS Message Property Columns tab of the source definition. By default, the port properties have the prefix

Prop_

Add variables to filter the published data to consume. For example, you can select to consume data from a specific table in the publication repository.

Add the required fields that determine the data set to consume. You can define multiple data sets to consume, similar to an aggregated or a compound subscription with an automatic mapping.

The following table describes the fields to add to the source object of a subscription workflow:

Field	Description
DIH__PUBLICATION_INSTANCE_ID	Required. Identifiers of one or more published data sets in a comma-separated list. Each data set that an application publishes has a unique identifier. To filter the data to consume, use the value from the $$<topicName>__PublicationInstanceIDs workflow parameter. The parameter datatype must be number(19) if you write to an Oracle database target or number(19,0) if you write to a Microsoft SQL Server database target.
DIH__PUBLICATION_INSTANCE_DATE	Date and time that each application started publishing the data sets, in a comma-separated list. If you use database partitions, you can filter the data to consume by using the value from the $$<topic_name>__PublicationInstanceDatesSQL workflow parameter. The value format depends on the publication repository database type. On an Oracle database, the datatype must be date and the value must be in the following format: YYYY-MM-DD HH24:MI:SS On a Microsoft SQL Server database, the datatype must be datetime and the value must be in the following format: yyyy-mm-dd hh:mi:ss (24h) If you want to filter the data to consume with a different transformation, you can use the $$<topic_name>__PublicationInstanceDates parameter instead.

Field

Description

DIH__PUBLICATION_INSTANCE_ID

Required. Identifiers of one or more published data sets in a comma-separated list. Each data set that an application publishes has a unique identifier. To filter the data to consume, use the value from the

$$<topicName>__PublicationInstanceIDs

workflow parameter.

The parameter datatype must be number(19) if you write to an Oracle database target or number(19,0) if you write to a Microsoft SQL Server database target.

DIH__PUBLICATION_INSTANCE_DATE

Date and time that each application started publishing the data sets, in a comma-separated list. If you use database partitions, you can filter the data to consume by using the value from the

$$<topic_name>__PublicationInstanceDatesSQL

workflow parameter. The value format depends on the publication repository database type.

On an Oracle database, the datatype must be date and the value must be in the following format:

YYYY-MM-DD HH24:MI:SS

On a Microsoft SQL Server database, the datatype must be datetime and the value must be in the following format:

yyyy-mm-dd hh:mi:ss (24h)

If you want to filter the data to consume with a different transformation, you can use the

$$<topic_name>__PublicationInstanceDates

parameter instead.

You can filter data to consume in the Source Filter attribute of the Source Qualifier transformation in subscription workflow. The following example shows the field syntax to filter by ID and date range in a single line:

MY_TABLE.DIH__PUBLICATION_INSTANCE_ID in ($$myTopic__PublicationInstanceIDs)
AND MY_TABLE.DIH__PUBLICATION_INSTANCE_DATE in ($$myTopic__PublicationInstanceDatesSQL)

The following table describes the

B2B Data Exchange

source properties:

Property	Description
accountName	Name of the account for which the B2B Data Exchange server sets the port that the workflow uses to process the event. The property value can be null if you use a global profile.
accountNumber	Number of the account for which the B2B Data Exchange server sets the port that the workflow uses to process the event. The property value must be a string. The property value can be null if you use a global profile.
application	Name of the application for which the B2B Data Exchange server sets the port that the workflow uses to process the event.
dataByReference	Determines whether the JMS message that B2B Data Exchange sends to PowerCenter contains a document reference. Possible values: True. The JMS message contains a reference to a document that is stored in the B2B Data Exchange document store. False. The JMS message contains the actual document data.
eventId	Identifier of the associated event for the documents that the workflow processes.
isEventReprocessed	Determines if the associated event is reprocessed.
partnerName	Name of the partner for which the B2B Data Exchange server sets the port that the workflow uses to process the event. The property value can be null if you use a global profile.
partnerId	Identifier of the partner for which the B2B Data Exchange server sets the port that the workflow uses to process the event. The property value can be null if you use a global profile.
profileId	Identifier of the profile for which the B2B Data Exchange server sets the port that the workflow uses to process the event.
profileName	Name of the profile for which the B2B Data Exchange server sets the port that the workflow uses to process the event.
DXSentEventId	List of identifiers for the events that triggered the event monitor. Available when a regular delivery or a batch delivery event monitor triggers the workflow.
DXMonitorId	Identifier for the event monitor that triggered the workflow. Available when a regular delivery or a batch delivery event monitor triggers the workflow.
DXMonitorName	Name of the event monitor that triggered the workflow. Available when a regular delivery or a batch delivery event monitor triggers the workflow.
DXUser	Name of the user that received the monitor notification. Available when a regular delivery event monitor triggers the workflow.

Rename Saved Search

Table of Contents

Developer Guide

Developer Guide

Creating the Source Definition for a Subscription Workflow

Creating the Source Definition for a Subscription Workflow

Creating the Source Definition
for a Subscription Workflow