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.| Setting | Description |
|---|---|
| Connector Id | The static, unique identifier for the connector. |
| Connector Type | Displays the connector name and a description of what it does. |
| Connector Description | An optional field to provide a free-form description of the connector and its role in the flow. |
| Direction | Whether the connector is handling PIP messages that were received or PIP messages that need to be sent. |
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.| Setting | Description |
|---|---|
| PIP Code | Identifies the standard business process associated with this message. |
| PIP Version | Identifies the version of the PIP standard. |
| Business Activity Identifier | Identifies a specific business activity. This code is found in table 3.2 of a PIP specification document. |
| Global Business Action Code | Identifies a specific business action. This code is found in table 4.2 of a PIP specification document. |
| From Role | The role initiating a business document exchange. |
| From Service | The service from which a message is being sent. |
| To Role | The role receiving the document in a business document exchange. |
| To Service | The service to which a message is being sent. |
| Test Indicator | Whether the message exchange is in test mode or production mode. |
Advanced Tab
Advanced Settings
Settings not included in the previous categories.| Setting | Description |
|---|---|
| Processing Delay | The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting. |
| Strict Schema Validation | Whether the connector should validate the PIP against the DTD file and perform additional schema validation checks. |
| Local File Scheme | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see Macros. |
Message
Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.| Setting | Description |
|---|---|
| Send | Whether messages arriving at the connector are automatically processed. |