Rosettanet

[Stayla Casillas]

Afteryou install the connector you can start using the connector. The first step is to create HTTP Listener and Request definitions for the Mule and partner endpoints used for your message exchanges.

Absolute file path or classpath relative to the project /src/main/resources directory for the keystore used for validating and/or signing messages (required when sending or receiving signed messages).

Optional override to force the use of signed messages even when not required by the PIP definition. Leave this value empty to the PIP definition for signing messages, set to NEVER to never sign any messages, or set to ALWAYS to always sign messages.

Optional reference to an object store definition to be used for storing messages awaiting acknowledgment. If not set, the connector always uses the default persistent object store to retain sent messages waiting for acknowledgments or retries. If set, the referenced bean must be an object store configuration to be used instead. See also:What is an object store bean?

Location ID of this organization. If specified, this is included in all messages sent and must be present in all messages received. If not specified, any value present in received messages will be accepted and ignored. Using the location ID also changes the alias used for your key pair in the keystore.

Expected location ID for partner organization. If specified, this will be included in all messages sent and must be present in all messages received. If not specified, any value present in received messages is accepted and ignored. Using the location ID also changes the alias used the partner certificate in the keystore.

Absolute file path or classpath relative to the project /src/main/resources directory for the PIP definition XML file. For one of the standard PIP definitions included in the distribution this takes the form /pipId/version.xml, such as /PIP3A4/V02_02.xml.

The default object store uses the Mule default persistent object store, which means that sent messages may accumulate if not acknowledged, and which may cause retransmissions when you try running again.

When using a persistent object store unacknowledged messages are retained across restarts of the Mule app and are automatically retransmitted when the app restarts (assuming the timeout has expired). All messages are deleted from the object store if the number of retransmissions specified in the PIP definition occurs without an acknowledgment, or after three days time. You can also force unacknowledged messages to be discarded when the Mule app is started by setting the system property:

You can used the supplied PIP configurations as a starting point. These are distributed inside the mule-rosettanet-extension-2.0.0-mule-plugin.jar, which is downloaded by Studio and added to your project under the /target/repository/com/mulesoft/connectors/mule-rosettanet-extension directory and can also be found in the standard MuleSoft enterprise Maven repositories (under group ID com.mulesoft.connectors). Each PIP configuration is in a separate directory (such as PIP3A4) inside the jar. You can copy a PIP directory out of this jar and edit the contents to match your specific needs.

RosettaNet uses X.509 certificates to authenticate messages. RosettaNet connector currently only supports storing certificates (and the private keys used for signing) in JKS-format keystores. You can use various tools such as Portecle for working with keystores and creating keys and certificates.

Anypoint Connector for RosettaNet (RosettaNet Connector) sends and receives RosettaNet messagesusing RNIF 2.00.01. The connector automatically handles send timeouts and retries,and responds to received messages with the appropriate HTTP response orsignal. Users work directly with the RosettaNet message service content as an XML document.

Removed "stale" (outdated) locks from ObjectStore when running on CloudHub, in order to clear situation where the shutdown leaves the locks active. The "Stale" timeout defaults to 180 seconds, but it can be changed by using com.mulesoft.connectors.rosettanet.extension.internal.delivery.DeliveryManager.chLockStaleSeconds property. (SE-13141).

Messages in the Action and Completion source were being accepted, but not triggering the remainder of flow. The connector was running mandatory checks on empty optional elements. Now, empty optional elements in RosettaNet headers are treated the same as missing optional elements. (SE-13123)

3a8082e126