When Private Process send an cXML to BC Interior Server, Special Characters are transformed
Article ID: KB0079631
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | 6.4.0, 7.0.0 |
Description
Private Process is sending the right character using UTF-8 encoding but BC transforms this character and the transaction throws a transaction exception:
Transaction terminated - Document parsing error: Request sending to trading partner failed validation : Parsing error: in document System ID:file:///D:/Appls/tibconew/bc/6.4/An entity determined to be in a certain encoding must not contain sequences illegal in that encoding. [Line: 57, Column: 77]
For example:
Interior Server sends:
<Name xml:lang="ES">TAMSA - Tubos de Acero de México S.A.</Name>
and BC receives/transforms the value:
<Name xml:lang="ES"><![CDATA[TAMSA - Tubos de Acero de México S.A.]]></Name>
Transaction terminated - Document parsing error: Request sending to trading partner failed validation : Parsing error: in document System ID:file:///D:/Appls/tibconew/bc/6.4/An entity determined to be in a certain encoding must not contain sequences illegal in that encoding. [Line: 57, Column: 77]
For example:
Interior Server sends:
<Name xml:lang="ES">TAMSA - Tubos de Acero de México S.A.</Name>
and BC receives/transforms the value:
<Name xml:lang="ES"><![CDATA[TAMSA - Tubos de Acero de México S.A.]]></Name>
Issue/Introduction
Getting "Transaction terminated - Document parsing" error
Environment
Windows and Linux environment
Resolution
BusinessConnect does not recognize the encoding of the message received from the private process.
To resolve this error:
Add "java.property.file.encoding=utf-8" property in all deployed .tra files under TIBCO_HOME\domain\<domain_name>\application\BusinessConnect and restart all engines.
To resolve this error:
Add "java.property.file.encoding=utf-8" property in all deployed .tra files under TIBCO_HOME\domain\<domain_name>\application\BusinessConnect and restart all engines.
Feedback
Yes
No
Powered by
