RosettaNet Connector 2.1 Reference | MuleSoft Documentation
# RosettaNet Connector 2.1 Reference
Anypoint Connector for RosettaNet (Rosettanet Connector) provides B2B functionality that uses the RosettaNet Information Framework (RNIF) for the information exchange of RosettaNet Partner Interface Process (PIP) messages.
Release Notes: RosettaNet Connector Release Notes
## Configurations
Configuration for RosettaNet Connector.
### Parameters
Name | Type | Description | Default Value | Required  
---|---|---|---|---  
Name of this configuration. Connectors reference the configuration with this name.  
**Global HTTP Listener** |  Reference to the global HTTP Listener definition for the service endpoint used by the partner for action and signal messages.  
**Service Endpoint Path** |  Service endpoint path, appended to the base path of HTTP Listener.  
**Global HTTP Request** |  Global HTTP request definition for the partner service endpoint. This value is used when sending action and signal messages.  
**Request Endpoint Path** |  Partner endpoint path, appended to the base path on an HTTP request.  
**Keystore path** |  Keystore that contains trusted partner certificates and the connector’s private signing key and certificate (JKS format).  
**Keystore access password** |  Access password for the keystore.  
**Signing key password** |  Private signing key password (required if signing action and signal messages).  
**Override message signing** |  Enumeration, one of:
  * ALWAYS
  * NEVER

|  Turns message signing on or off. Setting this value to `ALWAYS` overrides the signing configured by the PIP definition.  
**Global usage code** |  Enumeration, one of:
  * Production

|  Whether to operate in test mode or production mode.  
Object store reference |  Object Store |  Object store configuration reference:
  * If specified, the connector uses the referenced object store configuration to retain sent messages for acknowledgments and retries.
  * If not specified, the connector uses the default persistent object store to retain sent messages for acknowledgments and retries.

  
**Mule DUNS identifier** |  DUNS business identifier for the organization.  
Mule location identifier |  Location identifier for the organization:
  * If specified, this value is included in all sent messages and verified in all received messages.
  * If not specified, no value is sent, and received values are ignored.

  
**Partner DUNS identifier** |  Expected DUNS business identifier for the partner organization.  
**Partner location identifier** |  Expected location identifier for the partner organization.
  * If specified, this value is included in all sent messages and verified in all received messages.
  * If not specified, no value is sent and received values are ignored.

  
**Role in PIP** |  Enumeration, one of:
  * INITIATOR
  * RESPONDER

|  Connector’s role in the PIP.  
**PIP definition path** |  PIP file path.  
**Expiration Policy** |  Expiration Policy |  Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. Mule purges the instances as appropriate.  
## Sources
  *   * Completion source


### Action source
`<rosetta:action-source>`
#### Parameters
Name | Type | Description | Default Value | Required  
---|---|---|---|---  
**Configuration** |  Name of the configuration to use.  
**Primary Node Only** |  Determines whether to execute this source on only the primary node when running Mule instances in a cluster.  
**Streaming Strategy** | 
  * Repeatable In Memory Stream
  * Repeatable File Store Stream
  * Non-repeatable Stream

|  Configures how Mule processes streams. By default, Mule uses repeatable streams.  
**Redelivery Policy** |  Redelivery Policy |  Configures a policy for processing the redelivery of the same message.  
#### Output
Attributes Type |  Message Attributes  
---|---  
#### For Configurations
  * Configurations


### Completion source
`<rosetta:completion-source>`
#### Parameters
Name | Type | Description | Default Value | Required  
---|---|---|---|---  
**Configuration** |  Name of the configuration to use.  
**Primary Node Only** |  Whether this source should be executed only on the primary node when running in a cluster.  
**Redelivery Policy** |  Redelivery Policy |  Configures a policy for processing the redelivery of the same message.  
#### Output
Attributes Type |  Message Attributes  
---|---  
#### For Configurations
  * Configurations


## Operations
  * 

### Send Action
`<rosetta:send-action>`
Transmits the relevant electronic document to a trading partner.
#### Parameters
Name | Type | Description | Default Value | Required  
---|---|---|---|---  
**Configuration** |  Name of the configuration to use.  
**Initiating action** |  Reply Attributes |  Lists the reply attributes to send inside the Service header in the MIME message.  
Contents of the business document being exchanged between trading partners.  
**Streaming Strategy** | 
  * Repeatable In Memory Stream
  * Repeatable File Store Stream
  * Non-repeatable Stream

|  Configures how Mule processes streams. By default, Mule uses repeatable streams.  
**Target Variable** |  Name of the variable that stores the operation’s output.  
**Target Value** |  Expression that evaluates the operation’s output. The outcome of the expression is stored in the **Target Variable** field.  
#### Output
Attributes Type |  Message Attributes  
---|---  
#### For Configurations
  * Configurations


#### Throws
  * ROSETTA:WRITE
  * ROSETTA:CONFIGURATION
  * ROSETTA:PARSE
  * ROSETTA:UNKNOWN


## Object Types
### Completion
Completion status and details for the **Completion source** source.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Completion Code** |  Enumeration, one of:
  * SUCCESS
  * FAILURE
  * EXCEPTION

|  Type of completion for the action message. Valid values are:
  * SUCCESS: An acknowledgment signal was received from the partner.
  * EXCEPTION: An exception signal was received from the partner.
  * FAILURE: No response signal was received from the partner after the number of transmission attempts defined in the PIP configuration.

  
**Exception Detail** |  Exception Detail |  Details of the received exception signal. Present if the completion code is `EXCEPTION`.  
Received MIME signal message provided to the application in support of signed acknowledgment signals. Present if the completion code is `SUCCESS` or `EXCEPTION`.  
### Exception Detail
Details of the received exception signal.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Exception Code** |  Error code.  
**Exception Error Description** |  Error description.  
**Exception Component Code** |  Code that identifies the transaction for which the error occurred.  
**Exception Type** |  Error category.  
### Expiration Policy
Configures an expiration policy strategy.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Max Idle Time** |  Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.  
Enumeration, one of:
  * NANOSECONDS
  * MICROSECONDS
  * MILLISECONDS
  * SECONDS
  * MINUTES
  * HOURS
**Exception Detail** |  Exception Detail |  Details of the received exception signal. Present if the completion code is `EXCEPTION`.  
Received MIME signal message provided to the application in support of signed acknowledgment signals. Present if the completion code is `SUCCESS` or `EXCEPTION`.  
### Exception Detail
Details of the received exception signal.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Exception Code** |  Error code.  
**Exception Error Description** |  Error description.  
**Exception Component Code** |  Code that identifies the transaction for which the error occurred.  
**Exception Type** |  Error category.  
### Expiration Policy
Configures an expiration policy strategy.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Max Idle Time** |  Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.  
Enumeration, one of:
  * NANOSECONDS
  * MICROSECONDS
  * MILLISECONDS
  * SECONDS
  * MINUTES
  * HOURS

|  A time unit that qualifies **Max Idle Time**.  
### Message Attributes
Output of the **Action source** source, **Completion source** source, or **Send Action** operation.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Message Id** |  Unique identifier of the message.  
**Partner Business Id** |  Unique identifier of the trading partner.  
**Partner Location Id** |  Identifier that represents the trading partner’s location.  
**Reply Attributes** |  Reply Attributes |  Identifier values used when generating an action message in reply to another action. The **Action source** source sets this value.  
MIME action or signal message, including the signature, if signing is used. The app supplies this value to support non-repudiation.  
**Acknowledge Data** |  MIME acknowledgment signal returned to the sender, including the signature, if signing is used. The **Action source** source sets this value.  
### Non-repeatable Stream
Disables the repeatable stream functionality and uses non-repeatable streams to have less performance overhead, memory use, and cost.
### Reconnect
Configures a standard reconnection strategy, which specifies how often to reconnect and how many reconnection attempts the connector source or operation can make.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
Frequency | How often in milliseconds to reconnect.  
How many reconnection attempts to make.  
blocking | If `false`, the reconnection strategy runs in a separate, non-blocking thread.  
### Reconnect Forever
Configures a forever reconnection strategy by which the connector source or operation attempts to reconnect at a specified frequency for as long as the Mule app runs.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
Frequency | How often in milliseconds to reconnect.  
blocking | If false, the reconnection strategy runs in a separate, non-blocking thread.  
### Redelivery Policy
Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Max Redelivery Count** |  Maximum number of times that a message can be redelivered and processed unsuccessfully before triggering a `process-failed-message`.  
**Use Secure Hash** |  Whether to use a secure hash algorithm to identify a redelivered message.  
**Message Digest Algorithm** |  Secure hashing algorithm to use if **Use Secure Hash** is `true`. If the payload of the message is a Java object, Mule ignores this value and returns the value that the payload’s `hashCode()` returned.  
**Id Expression** |  One or more expressions that determine when a message was redelivered. This property can be set only if **Use Secure Hash** is `false`.  
**Object Store** |  Object Store |  Configures the object store that stores the redelivery counter for each message.  
### Repeatable File Store Stream
Configures the repeatable file-store streaming strategy by which Mule keeps a portion of the stream content in memory. If the stream content is larger than the configured buffer size, Mule backs up the buffer’s content to disk and then clears the memory.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Max In Memory Size** |  Maximum amount of memory that the stream can use for data. If the amount of memory exceeds this value, Mule buffers the content to disk. To optimize performance:
  * Configure a larger buffer size to avoid the number of times Mule needs to write the buffer on disk. This increases performance, but it also limits the number of concurrent requests your application can process, because it requires additional memory.
  * Configure a smaller buffer size to decrease memory load at the expense of response time.

  
**Buffer Unit** |  Enumeration, one of: |  Unit for **Max In Memory Size**.  
### Repeatable In Memory Stream
Configures the in-memory streaming strategy by which the request fails if the data exceeds the maximum buffer size. Always run performance tests to find the optimal buffer size for your specific use case.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Initial Buffer Size** |  Initial amount of memory to allocate to the data stream. If the streamed data exceeds this value, the buffer expands by **Buffer Size Increment** , with an upper limit of **Max Buffer Size** value.  
**Buffer Size Increment** |  Amount by which the buffer size expands if it exceeds its initial size. Setting a value of `0` or lower specifies that the buffer can’t expand.  
**Max Buffer Size** |  Maximum size of the buffer. If the buffer size exceeds this value, Mule raises a `STREAM_MAXIMUM_SIZE_EXCEEDED` error. A value of less than or equal to `0` means no limit.  
**Buffer Unit** |  Enumeration, one of: |  Unit for the **Initial Buffer Size** , **Buffer Size Increment** , and **Max Buffer Size** fields.  
### Reply Attributes
Configures the values used when generating an action message in reply to another action.
Field | Type | Description | Default Value | Required  
---|---|---|---|---  
**Message Id** |  Identifier of the message associated with the reponse.  
Identifier that indicates the type of respone.  
**Pip Instance Id** |  Identifier associated with an instance of a PIP.  
## See Also
  * Anypoint Connectors Overview
  * MuleSoft Help Center