Table of Contents

Search

  1. Preface
  2. Introducing B2B Gateway
  3. B2B Gateway administration
  4. Project and asset management
  5. EDI X12 and EDIFACT Messages
  6. Custom files with custom mappings
  7. Inbound Custom Files with Intelligent Structure Discovery
  8. File transfer tasks
  9. Partners
  10. Tracking and Monitoring Events
  11. B2B Gateway REST APIs
  12. Glossary

B2B Gateway

B2B Gateway

Partner inbound properties for custom files with custom mappings

Partner inbound properties for custom files with custom mappings

Use the
Inbound
page of the partner wizard to define the inbound flow for the partner.
The
Inbound
page can include the following properties for custom files with custom mappings:
Connection
The
Connection
area includes the following properties:
Connection Type
Select the type of the connection from where
B2B Gateway
picks up files. You can select the following connection types:
  • Advanced FTP V2
  • Advanced FTPS V2
  • Advanced SFTP V2
  • File Servers (AS2, HTTPS, SFTP)
  • Local Folder/MFT
  • FTP Client
  • SFTP Client
Connection
Connection where
B2B Gateway
creates files for the partner. Applies to the Advanced FTP V2, Advanced FTPS V2, and Advanced SFTP V2 connection types.
You configure connections in
Administrator
. For information about configuring the connections, see the respective connector guides.
File Server User
The file server user name for the partner from whom you receive files. Applies to the file servers connection type.
You create file server users in
Administrator
. For information about creating file server users, see the
Administrator
help.
Host
Host where the files that
B2B Gateway
picks up are located. Applies to the Local Folder/MFT, FTP Client, and SFTP Client connection types.
Port
Port where the files that
B2B Gateway
picks up are located. Applies to the Local Folder/MFT, FTP Client, and SFTP Client connection types.
Source Directory
Path to the directory on the connection from where
B2B Gateway
picks up files. Applies to the Local Folder/MFT, FTP Client, and SFTP Client connection types.
File Pattern
Pattern that defines the names of the files that
B2B Gateway
picks up. The pattern must be a Java regular expression.
For example:
To pick up all files enter
.*
To pick up only files that start with
ab
enter
ab\S.*
After you configure the connection click
Test Connection
to test and validate the connection.
File Pattern
Select the file pattern type to pick up.
After File Pickup
Action that
B2B Gateway
performs on the files after pickup. Applies to the Advanced FTP V2, Advanced FTPS V2, and Advanced SFTP V2 connection types.
Choose one of the following options:
  • Keep Files
    . Keep the files in the source location.
  • Delete Files
    . Delete the files from the source location.
  • Archive Files
    . Moves the files from the source location. Enter the target location in
    Archive Directory
    .
  • Rename Files
    . Rename the files in the source location. Enter a suffix to add to the original file name in
    New File Name Suffix
    .
Delete files on source after pickup
Determines whether or not
B2B Gateway
deletes files after pickup. Selected by default. Applies to the Local Folder/MFT, FTP Client, and FTPS Client connection types.
Pre-Process
Optionally, select a file transfer task to run actions on files that you receive from the partner. Applies to the file servers connection type.
You can select one of the following file transfer tasks:
Name
Description
Decrypt
Decrypts files that the partner uploads to the file server before the files are sent to
B2B Gateway
. For more information, see Decrypt.
Decompress
Decompresses files that the partner uploads to the file server before the files are sent to
B2B Gateway
. For more information, see Decompress.
Processing
The
Processing
area includes the following properties:
  • Inbound Mapping
    . Select an inbound mapping to receive files from the customer.
  • Process-to-Backend Mapping
    . If the target of the mapping is an interface file on the
    B2B Gateway
    document store, optionally, select a mapping to process files from
    B2B Gateway
    to the organization backend system.
    This mapping is used for messages where a process-to-backend mapping is not associated with the message type.
  • Mapping Location
    . Location where
    B2B Gateway
    saves the mapping.
  • Mapping Parameters
    . Lists the parameters of the process-to-backend mapping. You can enter parameter values in the
    Value
    fields.
Schedule
Schedule by which to run the flow. Select one of the following options:
  • Manually or by an external trigger. No schedule. You can run the flow from the
    Explore
    page or from a REST API. You can also run the flow from the Partner wizard.
  • By schedule. Runs the flow according to the defined schedule. Select a schedule from the list.
    To run a flow by a schedule, users need Read and Run permissions for schedules. If permissions are not configured, users cannot see existing schedules. For more information about permissions, see User roles.
  • By file listener. Runs the flow according to the defined file listener rules. Select a file listener from the list. You create file listeners in
    Data Integration
    . For information about creating file listeners, see
    Components
    in the
    Data Integration
    help.

0 COMMENTS

We’d like to hear from you!