Transaction Post Workflow Configuration File Schema

This section includes the contents of schema files relating to features of Transaction Post Workflows.

Note Note

You can find the schema NewTransactionWorkflowDef.xsd located under <te>/deployment/common/tpw where <te> is the directory in which you unpacked the SAP TE distribution file.

End of the note.

Structure

Configuration files used to control the processing of transaction postings must conform to the following schema:

Syntax Syntax

	<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				Transaction Workflow Definition schema.
				Copyright 2001 Triversity Inc. All rights reserved.
			</xsd:documentation>
		</xsd:annotation>

End of the code.

The top level element is <transactionWorkflow>. It can contain any number of TransactionPost and NotifiedOfPost sub-elements.

Syntax Syntax

		<xsd:element name="transactionWorkflow" >
			<xsd:complexType>
				<xsd:sequence>
					<xsd:element name="transactionPost" type="TransactionPost" minOccurs="0"
						maxOccurs="unbounded"/>
					<xsd:element name="notifiedOfPost" type="NotifiedOfPost" minOccurs="0"
						maxOccurs="unbounded"/>
				</xsd:sequence>
			</xsd:complexType>
		</xsd:element>

End of the code.

A TransactionPost element defines the processing that should occur for a transaction posting from a specified application. The processing defined in this element is performed synchronously, on the same thread that the originating application used to initiate the process. Extended processing steps can be moved to a different thread (and server node) by use of the PostNotification elements (see below).

Syntax Syntax

		<xsd:complexType name="TransactionPost">
			<xsd:sequence>
				<xsd:element name="immediateStep" type="ImmediateStep" minOccurs="0"
					maxOccurs="unbounded"/>
				<xsd:element name="postNotification" type="PostNotification" minOccurs="0"
					maxOccurs="unbounded"/>
			</xsd:sequence>
			<xsd:attribute name="applicationType" type="xsd:string" use="required"/>
		</xsd:complexType>

End of the code.

A NotifiedOfPost element defines the processing that should occur on receipt of a transaction posting message. There is one NotifiedOfPost element for each possible message identifier. Note that a given transaction posting can be forwarded as a message multiple times, with a different message identifier in each case.

Since processing of this element is initiated on receipt of a message, the processing defined in this element is performed on a separate thread from that used to originally generate the transaction data.

Syntax Syntax

		<xsd:complexType name="NotifiedOfPost">
			<xsd:sequence>
				<xsd:element name="immediateStep" type="ImmediateStep" minOccurs="0"
					maxOccurs="unbounded"/>
				<xsd:element name="postNotification" type="PostNotification" minOccurs="0"
					maxOccurs="unbounded"/>
			</xsd:sequence>
			<xsd:attribute name="messageName" type="xsd:string" use="required"/>
		</xsd:complexType>

End of the code.

An ImmediateStep element defines a single Transaction Post Workflow (TPW) step to be executed as part of the transaction posting process.

Syntax Syntax

		<xsd:complexType name="ImmediateStep">
			<xsd:sequence>
				<xsd:element name="className" type="xsd:string"/>
			</xsd:sequence>
		</xsd:complexType>

End of the code.

A PostNotification element defines the location (server node) to which a transaction posting should be forwarded and the message name to be used to identify the posting. The messageName used here must correspond to the messageName value in a NotifiedOfPost element in the configuration file on the receiving system.

Syntax Syntax

		<xsd:complexType name="PostNotification">
			<xsd:sequence>
				<!-- Valid values for destinationNode are currently HOST and SITE -->
				<xsd:element name="destinationNode" type="xsd:string"/>
				<xsd:element name="messageName" type="xsd:string"/>
			</xsd:sequence>
		</xsd:complexType>
	</xsd:schema>

End of the code.