Developer Guide

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

Back Next

Creating the Target Definition

In the PowerCenter Designer, create the target and add ports to store properties for running the workflow. You can also add properties to store other

B2B Data Exchange

values that you want to send back from PowerCenter.

The target definition process includes the following steps:

Create the target object.

If you develop a publication workflow, use the DIH__STAGING connection in the target definition. The database target type must match the publication repository database type.

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

Prop_

If you develop a publication workflow, add the required fields that determine the data set to publish.

The following table describes the required fields to add to the target object of a publication:

Parameter	Description
DIH__PUBLICATION_INSTANCE_ID	Required. Identifier of the published data set. Each data set that an application publishes has a unique identifier. The field uses the value from the $$publicationInstanceID workflow parameter.
DIH__PUBLICATION_INSTANCE_DATE	Required. Date and time that the application started publishing the data set. The field uses the value from the $$publicationInstanceDate workflow parameter. The value format depends on the publication repository database type. On an Oracle database, the value must be in the following format: to_date('<DATE>', 'YYYY-MM-DD HH24:MI:SS') On a Microsoft SQL Server database, the value must be in the following format: convert(datetime,'<DATE>',120)

Parameter

Description

DIH__PUBLICATION_INSTANCE_ID

Required. Identifier of the published data set. Each data set that an application publishes has a unique identifier. The field uses the value from the $$publicationInstanceID workflow parameter.

DIH__PUBLICATION_INSTANCE_DATE

Required. Date and time that the application started publishing the data set. The field uses the value from the $$publicationInstanceDate workflow parameter. The value format depends on the publication repository database type.

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

to_date('<DATE>', 'YYYY-MM-DD HH24:MI:SS')

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

convert(datetime,'<DATE>',120)

The following table describes the

B2B Data Exchange

target properties:

Property	Description
DXDataByReference	Required. Determines whether the JMS message that PowerCenter sends back to B2B Data Exchange 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.
DXEventId	Identifier of the event to use in the next workflow. If you do not set the value of this property, the B2B Data Exchange server generates a new event ID for the next workflow.
DXParentEventId	Identifier of the parent event to use in the next workflow. Set the value of this property if you want to send the JMS message to multiple targets with a child event for each target. The B2B Data Exchange then generates a new event ID for the next workflow to use for the child events. If you do not set the value of this property and send the message to multiple targets, all targets inherit the parent event status and you cannot track the status of each child event.
DXStatusName	Name of the event status to assign to the event in B2B Data Exchange after a successful processing.
endpointName	Name of the endpoint to which to route the message after processing.
profileId	Identifier of the profile to which to route the message after processing.
profileName	Name of the profile to which to route the message after processing.
accountName	Name of the account to which to route the message after processing.
partnerName	Name of the partner to which to route the message after processing.
sendToAccount	Determines whether to send the message to a global endpoint or to an endpoint that is associated with an account or a partner. Possible values: True. Sends the message to an endpoint that is associated with an account or a partner. If you set this value, you must set a value for the accountName or partnerName properties. False. Sends the message to a global endpoint.

Rename Saved Search

Table of Contents

Developer Guide

Developer Guide

Creating the Target Definition

Creating the Target Definition