Data Flows

This topic provides data flows rules created to perform certain actions during file processing.

Data flows are rules created to perform certain actions during file processing. The Data Flows menu is used data flows for document handling and MFT transactions. MFT flows are defined using regular expressions, while document handling flows are processed using type tree maps in IBM Sterling B2B Integrator.

The following actions are available in the Data Flows menu:

Action	Description
Create Rule	Used to create process rules for performing certain functions during file processing. Rules are created by building an IBM Sterling B2B Integrator business process. The process becomes available in PCM once it is deployed in IBM Sterling B2B Integrator. New rules are created by selecting a business process, naming the rule, and providing property names.
Manage Rule	This action provides the ability to search for, edit, and delete rules. Note: Only those rules that are not leveraged in any data flows may be deleted.
Build Data Flow	Used to create a file processing data flow for either MFT or document handling (EDI, flat file, XML, etc.) transactions. Flows are created by selecting the flow direction – inbound or outbound and the file handling type – MFT or document type. Multiple inbound and/or outbound data flows can be created for a partner or application.

Action

Description

Create Rule

Used to create process rules for performing certain functions during file processing. Rules are created by building an IBM Sterling B2B Integrator business process. The process becomes available in PCM once it is deployed in IBM Sterling B2B Integrator. New rules are created by selecting a business process, naming the rule, and providing property names.

Manage Rule

This action provides the ability to search for, edit, and delete rules.

Note: Only those rules that are not leveraged in any data flows may be deleted.

Build Data Flow

Used to create a file processing data flow for either MFT or document handling (EDI, flat file, XML, etc.) transactions. Flows are created by selecting the flow direction – inbound or outbound and the file handling type – MFT or document type.

Multiple inbound and/or outbound data flows can be created for a partner or application.

In an MFT data flow, the file is processed according to the naming convention of the file. When building an MFT flow, provide the document properties, then click Add.

In document handling flows, the file is processed based parameters such as sender ID, receiver ID, and document type.

The following table lists and describes business rules that are pre-installed with PCM:

PCM Rule	Rule Definition
Append_CRLF	Adds a line feed to the end of each line in the file.
CHAR_REPLACE	Replaces a specified character in the file.
Compression	Compresses the file.
DeEnvelope	Performs de-enveloping operation on the file.
DeferredEnvelope	Envelopes files in batches at particular intervals.
DestFileArchive	Archives the file following the translation process. When this rule is used, the file is visible in file transfer search results.
DocPriority	Sets document priority.
DocumentationExtraction	Splits batched files.
Drop Process	Drops the output file in a specified location.
EdifactEnvelope	Creates EDIFACT envelopes.
Edifact_Deenvelope	Validates envelopes for inbound EDIFACT files.
EmailDocSend	Sends an email with the document attached.
Email Notification	Sends email alerts.
Encode	Converts a file from one character encoding to another.
Encrypt	Encrypts file.
Envelope	Adds envelopes to transmitted files (EDI).
FileRename	Renames file based on a name pattern.
ITXADeEnvelope	Invokes IBM Transformation Extender Advanced, De-Envelope process.
IXTADeenvAndTranslate	Executes IBM Transformation Extender Advanced, De-Envelope and calls IBM Transformation Extender Translation Map.
ITXADeferredEnvelope	Executes IBM Transformation Extender Deferred Advanced and calls Envelope service.
ITXAEnvelopeCreate	Executes IBM Transformation Extender Advanced and creates envelopes.
ITXAImmediateEnvelope	Executes IBM Transformation Extender Advanced and calls Immediate Envelope service.
ITXATranslate	Executes IBM Transformation Extender Advanced and calls Translation service.
Multidrop	Perform drop to multiple connections.
MultiSAPALEDelivery	Delivers idocs to SAP.
Pattern_Rename	Handles pattern-based file renaming options.
PGPDecrypt	Decrypts files.
ReleaseObjects	Releases specified values.
RemoveCRLF	Converts and unstreamed file to a streamed file by removing the line feed from the end of each line.
S3Rule	Drops file in Amazon Web Services (AWS) S3 location.
SAPALEDelivery	Calls SAP ALE adapter to deliver idocs to SAP system.
SAPOutboundALE	SAP ALE rule leveraged for outbound ALE integration.
SAPTranslate_Envelope_mode	Translates EDI files, adds envelopes, and sends status codes to SAP for outbound docs.
SAPlinDelivery	Delivers idoc status to SAP.
SourceFileArchive	Archives input files. Files processed by this rule are visible in file transfer search results.
Translation	Executes IBM Sterling B2B Integrator map.
Wait Service	Instructs the system to wait for a period of time before proceeding to the next step in the process.
Zip	Zip the files.

When a partner-to-application relationship is selected, the actions summarized in the table below are available. Refer to the data flow report to identify which partner-to-application relationships have the associated data flows:

Action	Description
Copy Data Flow	Used to search for a data flow and copy inbound/outbound data flows to a new partner-application relationship.
Add from Multiple Flows	Used to build a data flow for a new partner-application relationship from multiple existing partner-application data flows.
Delete Data Flow	Delete the entire data flow for a partner-application relationship.

PGP Key Manager

The PGP Key Manager can be used to upload Public Key into the Native PGP Server within Sterling B2B Integrator.

Menus accessible for PGP Key Manager:

Create: Select the Partner/Application for which the PGP Key is required, and then upload the Key by specifying a Key Name.
Note: The Key File must be in ASCII format. Binary format is not supported.
Manage: Search for Keys based on Name, Partner/Application, or Key ID. The keys can also be downloaded.