Using BizTalk to implement RosettaNet business-to-business so easy
A vmi-hub-to-Business project has recently been completed, using the RosettaNet 2.0 standard with a brand, OEM, and supplier. A total of 4 messages exchanged, 4B2,3B2,4B2 pod,4c1, plainly, is to send and receive these data;
Project Environment
BizTalk Accelerator for RosettaNet does not use the latest BizTalk version because the customer is already in use, so it is done in the existing environment.
Let's talk about how to configure RosettaNet
- Exchange Certificate
RosettaNet the use and import of certificates in business-to-business is not detailed here, it is recommended that the server-side certificate (SSL certificate for IIS) and decryption/verification use the same certificate
- Configure Partner
Configuration Partner/home Organization, this part of the configuration is also very brief, the key is the name and Gbi two fields to fill in the correct.
- Configure Process Configuration
Define the processing rules for each PIP. Below we need to use the 3B2,4B2,4C1,0A1
Each PIP code is standard and you may not know how to fill out the first time you do the project
All of the above can be found through https://www.rosettanet.org/RosettaNet-Standards/Standards-Library/PIP-Directory, which are standard definitions
- Configure Agreement
The role of OA1 agreement is to return a 0a1 message to the other when the PIP process is processed.
Home role If you choose Initiator as the sender, responder indicates the receiver
Ports all fill in each other's URL
The other basic defaults are all right.
The above configuration is still very simple
How the process calls the RosettaNet API
It is only necessary to execute the submitrnif.submitmessage method in the process, but before executing this method, you must execute the following code, which is defined in the header of the XML string. Messages that should be RosettaNet are validated by a DTD, so you must add
RosettaNet Troubleshooting
- UNP. SCON. VALERR:A failure occurred while validating the service content.
Error number:2005
description:a failure occurred while validating the service content.
To verify that the Playload content is consistent with the DTD definition, the RosettaNet accelerator is strictly performing XML schema validation and will report the above error if one node does not conform
- UNP. SHDR. VALERR:A failure occurred while validating the service header.
Please check that the playload/serviceheade of the process configuration and messages are consistent
- "Bad Request" OR "Time Out"
Both sides check whether the certificate is imported correctly, especially for self-issued certificates, the other party needs to import the root certificate into the trusted directory, if the other side is Linux or other OS, you need to follow the appropriate action
- Error CODE:UNP. MESG. Dcrypterr
Check configuration is persistent confidentiality Required generally choose none on it, do not rule out the other party will choose Palyload
There is also the case that acknowledgement of receipt\non-repudiation Required also needs to be defined by both sides
Operations Tools
Test phase unavoidable message resend, do a message resend the tool, you can choose to send the error message again resend, in the original LOB application source code based on a choice to send a failed message again resend
Source code for download
Hope that the first use of BizTalk RosettaNet Business-to-business project can provide some help, of course, there are questions can also leave a message oh
Using BizTalk to implement RosettaNet business-to-business so easy