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 outbound properties for custom files with Intelligent Structure Discovery

Partner outbound properties for custom files with Intelligent Structure Discovery

Use the
Outbound
page of the partner wizard to define the outbound flow for the partner.
The
Outbound
page can include the following properties for custom files with Intelligent Structure Discovery:
Copy Details from Inbound
Populates the fields in the
Outbound
page with the details that you entered in the
Inbound
page. You then edit the fields in the
Outbound
page as required. Applies to the File Servers, Local Folder/MFT, FTP Client, and SFTP Client connection types.
Connection
The
Connection
area includes the following properties:
Connection Type
Select the type of the connection where
B2B Gateway
creates the files for the partner. You can select the following connection types:
  • Advanced FTP V2
  • Advanced FTPS V2
  • Advanced SFTP V2
  • AS2 Client
  • File Servers (HTTPS, SFTP)
  • Local Folder/MFT
Connection
Connection where
B2B Gateway
creates files for the partner. Applies to the Advanced FTP V2, Advanced FTPS V2, Advanced SFTP V2, and AS2 Client 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
B2B Gateway
creates the files. Applies to the Local Folder/MFT, FTP Client, and SFTP Client connection types.
Port
Port where
B2B Gateway
creates the files. Applies to the Local Folder/MFT, FTP Client, and SFTP Client connection types.
Target Directory
Path to the directory on the connection where
B2B Gateway
creates the files.
Pattern Type
Select the file name pattern type to create.
Pattern Type
Select the file name pattern type to create.
File Pattern
Select the outbound acknowledgment file name pattern.
For example:
($eventId).edi
The patterns are not case sensitive. For more information about the file patterns that you can use in the outbound flow definition, see File Patterns.
Post-Process
Applies to the file servers connection type. Optionally, select a file transfer task to run actions on files that you send to the partner. You can select one of the following file transfer tasks:
Name
Description
Encrypt
Encrypts files that you send to the partner before they are upload to the file server. For more information, see Encrypt.
Compress
Compresses files that you send to the partner before they are upload to the file server. For more information, see Compress.
Processing
The
Processing
area includes the following properties:
  • Process-from-Backend Mapping
    . Reads outgoing data from the backend system and writes it to the
    B2B Gateway
    document store.
  • Outbound Mapping
    . Optional outbound mapping that reads the files from the gateway and sends them to the partner.
  • Mapping Location
    . Location where
    B2B Gateway
    saves the mapping.
  • Mapping Parameters
    . Lists the parameters of the process-from-backend mapping. You can enter parameter values in the
    Value
    fields.
    If required, you can temporarily override the values that you define here by defining different values in the Run Partner REST API and running the flow with the API. For more information, see Run Partner REST API.
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!