Key Capabilities
- Pan-European e-invoicing and e-procurement network integration using AS4-based four-corner model architecture
- Universal Business Language (UBL) format support with automatic message routing based on party identifiers
- SMP integration for dynamic endpoint discovery with certificate-based encryption and digital signatures
Overview
A Peppol connection is configured in two places. Configure the Peppol Profiles page with a local party identifier and a private certificate. Then configure individual Peppol connectors with connection settings specific to a single trading partner. When an input file is processed by a Peppol connector, it is packaged and sent to the specified trading partner. When Arc receives a file over Peppol, it attempts to route the file to a specific Peppol connector. The application uses the Peppol party identifiers in the Peppol message to determine which Peppol connector should receive the file. When a file is routed to a Peppol connector, that file is placed in the connector’s Transactions tab, and is passed along to the next connected connector in the flow (when there is one).Prerequisites
Before you can configure and use the Peppol connector, you must complete the following:- Go to https://Peppol.org/ to register and complete the certification to become a Peppol access point.
- Register with an external SMP (Service Metadata Publisher). You must either register with an existing SMP or host your own.
Profile Configuration
The Peppol Profile must be configured before connections can be established with individual Peppol connectors. Click Profiles on the navbar, then click the Peppol tab.Peppol Profile Tab
Personal Id
Settings for identifying the local profile.Personal Certificate
Settings related to the private decryption and signature certificate.Application URLs
Settings and displayed values related to accessing Arc from the public web.Connector Configuration
Once you configure the global Peppol profile settings, create and configure individual Peppol connectors for each trading partner on the Flows page.Settings Tab
Configuration
Advanced Settings
Advanced Tab
Other Settings
Settings not included in the previous categories.Proxy Settings
These are a collection of settings that identify and authenticate to the proxy through which the connection should be routed. By default, this section uses the global settings on the Proxy Settings portion of the Security Settings page. Clear the checkbox to supply settings specific to your connector.
| Setting | Description |
|---|---|
| Proxy Type | The protocol used by a proxy-based firewall. |
| Proxy Host | The name or IP address of a proxy-based firewall. |
| Proxy Port | The TCP port for a proxy-based firewall. |
| Proxy User | The user name to use to authenticate with a proxy-based firewall. |
| Proxy Password | A password used to authenticate to a proxy-based firewall. |
| Authentication Scheme | Leave the default None or choose from one of the following authentication schemes: Basic, Digest, Proprietary, or NTLM. |
Logging
Settings that govern the creation and storage of logs.
| Setting | Description |
|---|---|
| Log Level | The verbosity of logs generated by the connector. When you request support, set this to Debug. |
| Log Subfolder Scheme | Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance. |
| Log Messages | Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab. |
Miscellaneous
Miscellaneous settings are for specific use cases.
| Setting | Description |
|---|---|
| Other Settings | Enables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings. |
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Performance
Settings related to the allocation of resources to the connector.
| Setting | Description |
|---|---|
| Max Workers | The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
| Max Files | The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
Alerts Tab
SLAs Tab
Transactions Tab
This tab lists all messages associated with the connector. Use the search bar to find specific messages, or click the funnel icon to apply a filter. You can filter by time, message direction, and/or status.Sending Documents
When sending documents, the following occurs:- The connector uses the Peppol Id to look up the metadata (such as the endpoint and certificates) for the partner that has that ID.
- The receiver defined in the Standard Business Document Header (SBDH) of the outbound message must match the Peppol Id of the connector where the message being sent.
- You can configure the SBDH using an XML Map connector when it is connected as the input to a Peppol connector.
- The metadata that is returned from the lookup is used by the connector to send the document to the partner.
Receiving Documents
When receiving documents, the steps described in Sending happen in reverse:- Your partner’s Peppol AP looks up the metadata details that you provided to the SMP you registered with.
- That metadata is used by your partner’s Peppol AP to send you the message(s). When a message reaches Arc, the engine looks at the sender Peppol Id defined in the message SBDH, then routes the message to the Peppol connector that is configured with that Peppol Id.