RosettaNet HTTPS Connector

Click the Choose button on the right-hand side. A dialog opens in which you can navigate to the directory in which all the received and generated messages are stored. This directory also stores the file containing all the instance identifiers that have been generated. An instance identifier is a string that uniquely identifies each message in the context of two business partners. The instance identifier is not globally unique; to achieve that the string would need to be created in a highly complex way.

You obtain DUNS numbers from the Dun & Bradstreet Corporation on https://www.dnb.com/de-de/produkte-services/dun-bradstreet/dnb-duns-nummer.

Defines, after how many days the IDs of the RosettaNet messages which are already received are deleted from the file system.

The IDs are stored in an XML file. When sending a very large number of messages, this file can grow so large that the performance is affected. This is why IDs are deleted in regular intervals.

The connector waits actively the given waiting time in seconds before it retries to send the message, default: 30 seconds.

(Input Connector only)

When activated, attachments are stored into variables automatically after reception. For each attachment three variables are created; if there are several attachments, the variables are numbered consecutively starting by null (X):

Activate this option, if you want to carry out error handling in the workflow yourself. If this option is selected, the workflow throws an error that can be treated individually.

If this option is selected, the connector sends a RosettaNet signal message containing the relevant error. The workflow is executed successfully without throwing an error.

A PIP ID, as for example 3A2, consists of the following parts:

For the purpose of checking the validity of the message, a simple comparison of the strings is performed on these fields.

Some business partners agree not to include the last four positions in long version or release designations. If one of the business partners uses a release or version number without the last four positions while the other includes the last four positions, the message would be deemed to be invalid.

The underlying PIP version is to be found in the RosettaNet specification.

For loading the DTD or the XML Schema, which describes the action of the PIP. Additionally, define whether you load a DTD or an XML Schema.

(Output Connector only)

The role names are set out in the specification for each PIP. They are normally to be found in table 3-1 of the PIP specification. E.g., for PIP 3A2 the role name of the sender is Customer and that of the receiver is Product Supplier.

(Output Connector only)

The names are set out in the specification for each PIP. E.g., for PIP 3A2 the values can be found in table 4-1.

(Output Connector only)

The designations for business activities are specified by RosettaNet and laid down for each PIP. They are normally to be found in table 3-1 of the PIP specification. For example, for PIP 3A2, it is Request Price and Availability.

(Output Connector only)

The designations for business actions are specified by RosettaNet and laid down for each PIP. They are normally to be found in table 4-2 of the PIP specification. For example, for PIP 3A2, depending on the action, it is either Price and Availability Request Action or Price and Availability Response Action.

(Output Connector only)

Inserts a reference to the message type into the message. In a message’s service header there is an XML element <GlobalUsageCode>. Depending on your selection in this field, either Test or Production is inserted into this tag. RosettaNet does not specify how a business partner is to proceed with this element. If business partners evaluate the Test or Production string they can decide from the value found whether the message is to go into the production environment or into a test environment, if one is available.