Key Capabilities
- RosettaNet PIP service header generation and validation for B2B messaging
- Integration with RNIF for complete messaging workflows with configurable PIP codes, versions, and business activities
- DTD-based schema validation for strict PIP specification compliance
Overview
When receiving a PIP message over RNIF, a PIP connector validates the PIP service headers against the settings configured for the connector. These settings include the PIP Code, PIP Version, and so on. After validation, the PIP message payload is processed into the Transactions tab for this connector, and passed along to the next connector in the flow. When generating PIP messages, a PIP connector adds service headers from the settings configured for the connector. Once these service headers are applied, the resulting file in the Transactions tab can be passed to a RosettaNet connector for transport to the trading partner. PIP connectors do not generate acknowledgments. Acknowledgments are handled by the RosettaNet connector.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Connector Configuration
Settings related to the core operation of the connector.PIP Settings
Settings related to the service headers of PIP messages. When sending messages, these settings are applied as service headers in the resulting message. When receiving messages, these settings are used to validate the incoming document.Advanced Tab
Advanced Settings
Settings not included in the previous categories.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. |